Page History

...

1. Background
   • Why do we apply support packs? 
     • HR/Payroll year end support packs are released at this time each year and must be applied before the up coming year's Payroll run.
     • This is opportunity to bring other support pack levels up to date
       • SAP recommends that our support pack level be current
     • We become more efficient and more effective organization in testing
2. Some Lessons Learned from 2008
   • Freeze date confusion
   • Communication - Wiki  https://ssit-docs.mit.edu/display/sapscripts/2009+Year+End+SAP+Support+Pack+Project
   • Project go-lives too close to freeze dates
   • Test scripts & Test Plans
3. Teams, roles, responsibilities
   • Business Owners
     • GL Reporting, JV - Magdalene Lee
     • HR/Payroll - Scott Ball
     • HR/Benefits - Judy Raymond
     • Facilities - Lisa St. Croix
     • Stockroom - Tammy Doyle
     • EHS - Laurie Veal
     • Spons. Billing - Doug Levie
     • Gen AR - Donna Cairns
     • Cashiers - Cheryl Whelan
     • Property: Kevin Milligan
     • Fund Centers: Peggie McGrath
     • IST Telecom: Allan Wallace
     • Tech Review: Jim Coyle
     • AP - John Larkin
     • Procurement - Mary Bacci, John Doyle
     • eCAT - John Doyle
     • Travel - John Doyle, Paul Arsenault
     • SMART - Mary Bacci, John Larkin
     • OSP - Steve Dowdy
     • OBO - Rob Slauzis
4. Schedule - Important Dates
   • Now - October - Plan, create master script catalog, improve test scripts, move pending work to production
   • 10/05/2009 - Last date to implement projects until freeze ends on 12/24/2009 (Except Open Enrollment & Union Structures)
   • 10/19/2009 - Production snapshot at end of day - will be used to refresh dev & test environments 
   • 10/22/2009 - Last date to implement support & enhancement changes until freeze ends on 12/24/2009
   • 11/03/2009 - 11/08/2009 Unit Test
   • 11/09/2009 - 11/22/2009 System Integration Test
   • 11/23/2009 - 12/09/2009 User Acceptance Test
   • 12/11/2009 - 12/13/2009 Golive Weekend
   • 12/24/2009   Development Freeze ends
5. Transport Control Procedure
   • New Role of Transport Manager - John Tuttle
   • Support Pack related fixes follow support pack path  = SF2 > SH2 > PS1
   • Wiki MarkupCritical Transports for PS1 fixes = SF2 Critical Transports for PS1 fixes = SF2 >SF5/SH1 > PS1 > \ [support pack path\]  
     • Critical Transports require approval form each of the following 3 groups: Primary Business Owner, SAIS Admin & SAIS QA
   • RT tickets are sent to SAP:: Test Issues queue, email = saptest@help.mit.edu
6. What next?
   • Verify the Business Process Owners List
   • Provide name of tester to your SAIS business support analyst
   • Log on to the Wiki - confirm that you have access and review your test cases
   • Provide names of those who need to be added to the SAPbiz distribution list 
7. Questions?
   • Will the first day for post-freeze transports be rescheduled from  12/24 to 12/23 due to this year's extra holiday closing?
   • Will SIT schedule be segmented into specific date blocks to accommodate dual UAT end to end cycle testing?

...

1. Unit Test Schedule? - SF3 Upgrade will not complete until this evening & SF2 by tomorrow evening or Wednesday morning. - Impact?
   •  Update to SF3 should be completed tonight by 10:00pm.
   • SPAU - generate tonight. 
   • Tomorrow am.  Rich K. will apply SAP notes. Should take 2hrs
     • When can SPAU & action log activities begin? - Other prep. activities? (interfaces, queued data files, etc.)
       • Mods and SPAU also will start Tuesday a.m. and complete by 3:00 pm 
     • How many days are required for UNIT test / from where in the plan do we subtract the time?
       • The project plan's schedule can not be changed. We must complete unit testing by Monday 11/9.
       • SF2 will be available for testing on Wednesday by aproximatly 11:00 am
2. Unit test execution SF2
   • SF3 was offered as an alternative environment to begin unit testing however the prep.(i.e. authorizations), results logging, and issue resolution were reasons to keep unit testing confined to one system.
   • SF2 update should be completed by late Tuesday or early Wednesday (8:00 a.m.)
   • A Check-in with the core team is scheduled for Tuesday at 3:00 to confirm we are on track.
   •  Wednesday a.m. activites for SF2:
     •  Transports from SPAU work, BSI transports ~1hr#* *{*{}The action log will be executed (1 - 2hrs)*
     •  Unit test start - 11am Wednesday (original scheduled to start Tue 8am - planned duration was 5 days has now been cut to 3 days)
       • Consolidated list will be split up by teams.  Each team will update their spreadsheet with Pass/Fail Results
       • Daily updates required - If updated spreadsheets can not be posted to the Wiki daily, a percentage complete should be communicated to the PM and the end of each day. Core team check-in meetings are scheduled for 3:00 PM. on Wed., Thur., & Fri this week. The plan is to test on Saturday unless status for each group is on target to completed on time without weekend testing.
       • Issues/Errors must be logged in the SAP:: Test Issues queue, email = saptest@help.mit.edu.
       • The spreadsheets will be the official test log - Results (pass/fail) and testers name must be filled in for completion of this test phase
3. Time Sheets
   • There is a steering committee mtg this Wednesday
   • We need to stay current with our time allocated to this project
   • confirm that SAIS project team members have project related tasks assigned in Daptive
4. Testers
   • SAIS should have their same authorizations in SF2. Let, Ken know if there are additional authorizations needed.
   • We are looking for the complete list of business testers for UAT and the names of those who would need to be unlocked for SIT.
5. December 24th Institute holiday - was to be the 1st day for resuming normal transports. Can this change to the 23rd?
   •  Freeze will be lifted 12/29 due to institute closing on 12/24. Payroll pension 12/22, Weekly is 12/22 & Monthly 12/23 we will consider transports for the 22nd only if there is a pressing reason.

November 4, 2009 Steering Committee 9-10am W92-240 Riverside

November 9, 2009 Core Team

November  16, 2009 Core Team

November 23, 2009 Core Team

November 30, 2009 Core Team

December 7, 2009 Core Team

...

1. Delay in Development Systems Update - Additional enhancement packs and limited devolpment systems (memory) resources have resulted in a delay in having our devolpment system ready for Unit Testing.
   • Impact - Unit testing has been delayed by 3 1/2 days & it is expected that updates to the production system will require more than a weekend of production outage time.  (possibly Noon, Friday through 9AM Monday) 
   • Mitigation - Unit testing will begin immediatley following the SH2 update and overtime has been scheduled for testers. Key stakeholders are to be contacted regarding the likelihood of additional system downtime. Prerequisite changes to PS1 (such as kernel updates) can be applied the weekend before the go-live weekend. 
2. Progress to date -
   • Test cases have been reviewed, modified and catalogued on the project Wiki.
   • Unit test master list has been completed, review and assigned members of the business teams .
   • Project Kick-offs with SAPbiz & SAIS extended team
   • Open enrollment post freeze transports successfully moved 
3. Budget
4. Risks & Issues
5. Questions?

November 9, 2009 Core Team

1. Unit Testing
   • Status?
   • Issues - Have all issues been logged? Count = 10? Can we catagorize and update status?
   • Transports? Are we okay to use zutreq?
2. SH2 Status - Updates should complete by 9pm tonight 11/9
   • Post upgrade steps (Application Server Updates, ABAP load generations, Database actions, etc.) scheduled for when? completed by?
   • Warehouse Extracts - Tuesday morning estimated schedule?
   • Evaluation of time requirements for scheduling production updates -
3. SIT - Schedule (was 11/10 - 11/22/09)
   • Preparation activities
   • Initial testing and environment set-up - What tasks should be scheduled for 11/10?
   • of users to be unlocked
   • Test Case Catalogs and Results logging
4. Action Log Update - tasks required for refreshed system v. non-refreshed

November  12, 2009 SAPbiz

• Background
  • Why do we do this?  - "Because we have need to!"                                future slogan
    • HR/Payroll year end support packs are released at this time each year and must be applied before the up coming year's Payroll run.
    • This is opportunity to bring other support pack levels up to date
      • SAP recommends that our support pack level be current
    • We become more efficient and more effective organization in testing
  • What's new?
    • The addition of Enhancement Pack 4 & Basis Enhancement Pack 1
      • SAP's new approach to delivering new or enhanced functionality
      • Enhancement packs are a prerequisite to new functionality - Enterprise Learning Product
      • Avoid having to do a separate project that would essentially double the time, cost & effort
      • Risks & Mitigation
  • Lessons learned
    • Freeze date confusion - Production development freeze period (10/5/09 through 12/29/09)
      • December 24th Institute holiday - was to be the 1st day for resuming normal transports. Can this change to the 23rd?
      •  Freeze will be lifted 12/29 due to institute closing on 12/24. Payroll pension 12/22, Weekly is 12/22 & Monthly 12/23 we will consider transports for the 22nd only if there is a pressing reason
    • Communication - Wiki  https://ssit-docs.mit.edu/display/sapscripts/2009+Year+End+SAP+Support+Pack+Project
    • Project go-lives too close to freeze date
    • Test scripts & Test Plans
• Progress to date:
  • SF2 Development Environment Support & Enhancement Packs were applied and pre-processing steps completed on 11/5/09
  • Unit Testing completed on 11/7/09 - Test was more extensive this year due to the inclusion of high activity transactions/programs
  • Issues - 16 logged issues   (status for all issues is either resolved or non-issue)
    • 2 severe - defect is to critical business process that impacts a majority of system users 
    • 5 high - defect is to critical business process that impacts a specific business area or function 
    • 2 medium -defect is to either a non-critical function or alternative processes exist 
    • 7 low - defect may not be attributed to support pack updates and/or can not be reproduced
  • SH2 SIT Environment has been updated as 11/10/09
    • A snapshot of production, as of 10/19/09 was applied to this environment 
    • Data warehouse extracts have been completed
    • Trial balance has been executed 
• Schedule - Next Steps
  • Run Payroll
  • Unlock Testers
  • Begin SIT Testing

• November 2009

November  16, 2009 Core Team

• Progress to date - FI Trial balance, Payroll run and period closing completed in SH2
• Issues 2 issues reported by HR/Payroll
• SIT Schedule
  • Closing schedule?
• Test status reporting & Issue logging
• Cut-over weekend downtime requirements and decisions

November  18, 2009 Steering Committee 4-5pm Downtown Crossing

• Cut-over Weekend Panning
  • Background
    • Application of separate support and enhancement packs together represented a risk = more notes having to be applied over a 2 day weekend may be tight (this strategy has been employed at Lincoln Lab due to the benefit of lowering the cost of repeating this effort if note were applied at different times.)Enhancement Pack 4
    • More accurate projections for down time requirements have been determined after monitoring the actual update times in our staging, development and test environments.
  • System Support Pack Tasks*   *(Go-live plan)
    • In an effort to reduce the system down-time for the go-live week-end, tasks that can be run earlier or during uptime have be identified and scheduled to take place the week before to go-live.  
  • Go-live Weekend Schedule (Calendar)
  • Business Concerns & Mitigation - The possibility of additional down-time during cut-over weekend has be presented to all the SAP business process owners directly as well as at our SAPbiz meeting on 11/12.  The concensus opinion is that if the system must be brought down for additional hours, that Friday is preferred over Monday.    
    • Payroll Timesheets
    • ESS Benefits - Enrollment Display
      • Cobra feed normally scheduled for Friday - could be rescheduled earlier or even by Monday if necessary
      • Access to benefits data will be down but  central office can brepare brio reports to answer questions. 
    • Facilities Work orders - Back-up procedure exists for downtime. Early access requested to generate work lists to start early Monday.
      • Journal Vouchers - Notice required to clear out WF inbox.
  • Questions / Recommendation
  • SIT Issues  
  • *{+}rt queue{+}* (https://help.mit.edu/Search/Results.html?Order=ASC&Query=%20Queue%20%3D%20'SAP%3A%3ATest%20Issues'%20%20AND%20'CF.SAP%3A%3ATest%20Issues.%7BSAP%20Project%20Name%7D'%20LIKE%20'SAP%20Support%20Pack%202009'%20%20AND%20Queue%20%3D%20'SAP%3A%3ATest%20Issues'%20&Rows=&OrderBy=Created&Page=1&Format='%20%20%20%3Cb%3E%3Ca%20href%3D%22%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__id__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3A%23'%2C%0A'%3Cb%3E%3Ca%20href%3D%22%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__Subject__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3ASubject'%2C%0A'__Status__'%2C%0A'__QueueName__'%2C%0A'__OwnerName__'%2C%0A'__Priority__'%2C%0A'__NEWLINE__'%2C%0A''%2C%0A'%3Csmall%3E__Requestors__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__CreatedRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__ToldRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__LastUpdatedRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__TimeLeft__%3C%2Fsmall%3E')

November 23, 2009 Core Team

1. Go-live Weekend Schedule (Calendar)
   • Steering committee has approved a new schedule that will increase the PS1 downtime required for cut-over weekend. System will now be brought down @ 12pm on Friday 12/11 and available @ 6 am Monday 12/14.
   • Communication of the plan currently includes a note to the Assistant Deans, Announcement at SAPbiz, Message to SAIS-SAP....(What other notices need to be published?)

1. #* Additional testing needed to cover the state of PS1 between 12/7/09 thru 12/11/09
2. SIT Status & Schedule
3. Issues
   • *{+}rt queue{+}* (https://help.mit.edu/Search/Results.html?Order=ASC&Query=%20Queue%20%3D%20'SAP%3A%3ATest%20Issues'%20%20AND%20'CF.SAP%3A%3ATest%20Issues.%7BSAP%20Project%20Name%7D'%20LIKE%20'SAP%20Support%20Pack%202009'%20%20AND%20Queue%20%3D%20'SAP%3A%3ATest%20Issues'%20&Rows=&OrderBy=Created&Page=1&Format='%20%20%20%3Cb%3E%3Ca%20href%3D%22%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__id__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3A%23'%2C%0A'%3Cb%3E%3Ca%20href%3D%22%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__Subject__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3ASubject'%2C%0A'__Status__'%2C%0A'__QueueName__'%2C%0A'__OwnerName__'%2C%0A'__Priority__'%2C%0A'__NEWLINE__'%2C%0A''%2C%0A'%3Csmall%3E__Requestors__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__CreatedRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__ToldRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__LastUpdatedRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__TimeLeft__%3C%2Fsmall%3E') What issues did we report and what is the current status for each?
   • We would like to also capture changes & enhancements. What category in RT can we assign to sepparate theses tickets from the real issues?
   • Update test cases (including obsolete, modified or new tests).
   • Add enhancement requests to team lists if you see an opportunity to migrate from custom to standard SAP
     • SAP has provided a list of replacement transactions that we need to consider upgrading to.  
4. UAT Schedule
   • Currently scheduled to begin today and complete 12/09/09
   • Are there any cross module dependencies that need to be coordinated? - both for scheduling and task assignment
   • Testers to be unlocked list as of 11/23/09 9:00am

November 25, 2009 SAPbiz 

• Background
  • Why do we do this?  - "Because we  need to!"
  • HR/Payroll year end support packs are released at this time each year and must be applied before the up coming year's Payroll run.
    • This is opportunity to bring other support pack levels up to date SAP recommends that our support pack level be current
    • We become more efficient and more effective organization in testing
  • What's new?
    • The addition of Enhancement Pack 4 & Basis Enhancement Pack 1
    • SAP's new approach to delivering new or enhanced functionality
    • Enhancement packs are a prerequisite to new functionality - Enterprise Learning Product
    • Avoid having to do a separate project that would essentially double the time, cost & effort
  • Wiki  https://ssit-docs.mit.edu/display/sapscripts/2009+Year+End+SAP+Support+Pack+Project
    • Serves as a central repository for our official test catalogs with test results
    • Project communications and schedules

•  Progress to date
  • System Integration Testing was completed on 12/23/09
  • User Acceptance Testing is now underway and should be completed by December 9, 2009
    • FI closing and related UAT testing is reserved for Dec 8-9 therefore all other testing should be completed by Dec. 7, 2009
  • This testing will take place in the same SAP environment = SH2 "SAP HR-Payroll Testing2"
  • Many users completed their UAT testing during SIT
  • Although testing for your specific business area may be competed, you may still be required to test fixes and/or assist with testing for other areas
  • You are encouraged to use the time between now and Go/No-go to any additional add-hock testing
  • Users have been unlocked by request. If you plan on testing please confirm that you are on the following list
    • Requests to be unlocked should be sent to levie@mit.edu
    • Old transactions may no longer be supported by SAP. Please review the list to see if we have an opportunity to upgrade over the upcoming year.  old transactions
• Issues
  • Link to RT queue: *{+}rt queue{+}* (https://help.mit.edu/Search/Results.html?Order=ASC&Query=%20Queue%20%3D%20'SAP%3A%3ATest%20Issues'%20%20AND%20'CF.SAP%3A%3ATest%20Issues.%7BSAP%20Project%20Name%7D'%20LIKE%20'SAP%20Support%20Pack%202009'%20%20AND%20Queue%20%3D%20'SAP%3A%3ATest%20Issues'%20&Rows=&OrderBy=Created&Page=1&Format='%20%20%20%3Cb%3E%3Ca%20href%3D%22%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__id__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3A%23'%2C%0A'%3Cb%3E%3Ca%20href%3D%22%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__Subject__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3ASubject'%2C%0A'__Status__'%2C%0A'__QueueName__'%2C%0A'__OwnerName__'%2C%0A'__Priority__'%2C%0A'__NEWLINE__'%2C%0A''%2C%0A'%3Csmall%3E__Requestors__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__CreatedRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__ToldRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__LastUpdatedRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__TimeLeft__%3C%2Fsmall%3E')
• Go-live Weekend
  • Steering Committee Meeting was held on 11/18/09
  • System Downtime will be from Friday, December 11th @ Noon through Monday, December 14th @ 6:00am 
  • Validation testing is scheduled for Sunday Dec. 13th between 3:00pm and 7:00pm
  • Go/No-go decision will be made upon completion of validation
• Communication Plan

November 30, 2009 Core Team

• Progress to date
  • SIT completed - test results posted to the wiki
  • UAT underway -Should be completed by Dec. 7th (Dec 8th & 9th reserved for FI closing activities)
    • You may use the same SIT log for posting UAT results. Insert columns for UAT specific data.
    • testers should be unlocked. Please let Ken LeVie know if there is anyone who needs to test that is not on this list: list
    • When UAT testing is completed, users are encouraged to do add-hock testing
    • We also recommend that the list of old transactions be reviewed to see if there is an opportunity to transition to "New" transactions in the upcoming year

SH1 testing - scheduled for this Wednesday 

• Issues- Please make sure that all your logged issues appear on this list and that they are updated with the most current status
  • *{+}rt queue{+}* (https://help.mit.edu/Search/Results.html?Order=ASC&Query=%20Queue%20%3D%20'SAP%3A%3ATest%20Issues'%20%20AND%20'CF.SAP%3A%3ATest%20Issues.%7BSAP%20Project%20Name%7D'%20LIKE%20'SAP%20Support%20Pack%202009'%20%20AND%20Queue%20%3D%20'SAP%3A%3ATest%20Issues'%20&Rows=&OrderBy=Created&Page=1&Format='%20%20%20%3Cb%3E%3Ca%20href%3D%22%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__id__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3A%23'%2C%0A'%3Cb%3E%3Ca%20href%3D%22%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__Subject__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3ASubject'%2C%0A'__Status__'%2C%0A'__QueueName__'%2C%0A'__OwnerName__'%2C%0A'__Priority__'%2C%0A'__NEWLINE__'%2C%0A''%2C%0A'%3Csmall%3E__Requestors__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__CreatedRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__ToldRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__LastUpdatedRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__TimeLeft__%3C%2Fsmall%3E')
• Communication Plan
  • Message will be sent out today regarding SAP updated and the related "down-time" schedule
    • email distribution lists include:To: 'sap-prd-notice@mit.edu'; 'aac-aoquery@mit.edu'; 'itpartners@mit.edu'; 'warehouse@mit.edu'
      Cc: 'sapbiz@mit.edu'; 'is&t@mit.edu'
  •  SAP and Web activities will be down brought down on Friday, Dec. 11th @ 12:00 noon and will remain out until Monday, Dec, 14th @ 6:00am.
  • The Data Warehouse will be available with data extracted from production on Thursday (12/10) evening
  • Other messages and means of communication?

Questions?

December 4, 2009 Emergency Steering Committee 4-5pm W92-240 Riverside

Agenda:

• Discuss the 401k issue  rt ticket
  • 401k catch-up contributions are miscalculating for employees in the period in which they reach the regular contribution limit
• Options for correcting the problem
  1. SAP Provides a fix
     • SAP has released a pilot note for MIT. 
       • Status?
     • Testing is estimated to  take ? days to complete
  2. SAP pulls out the correction that causes the problem
  3. MIT applies only the needed HR/Payroll packs for upcoming year
• Schedule options if we go with a SAP fix
  1. Fix is provided on time to allow us to proceed as scheduled (12/11 - 12/14)
  2. Fix is provided but we need to delay go-live by 1 week (12/18 - 12/21)
  3. Fix is not ready this year - we schedule the go-live the holiday week end (12/25 -12/28) 
     • This plan is to run the impacted jobs before the issue is introduced and fix the issue before the next required job is run the following month
     • Dependent on whether or not the scheduling of Pension Payroll can be move from 12/22 to 12/28 
• Effect on Communication Plan
  1. Go/No-go decision is scheduled for Wednesday 12/9
     • may require postponing until Friday 12/11 (noon) at the latest
  2. SAPbiz 12/9 scheduled sign off on UAT and announcement of Go/No-go

December 7, 2009 Core Team

• Progress to date
  • 401K issue - SAP note applied and successfully tested ever the weekend
  • Pre-update updates this weekend
  • Up-time system updates
  • UAT testing status
• Go/No-go - Is scheduled for this Wednesday
  • Sign-off from Business Owners should take place at SAPbiz 10:30am
  • Steering Committee Meeting to be scheduled later that day - will present  the cut-over plan and a go/no-go decision will be made
• Go-live Cut-over Plan (draft)
  • Update Person(s) Responsible from last years plan
  • Verify dates and times as needed 
  • Add/Subtract tasks as needed - eg. EHS - SAPweb Gateway page message for Supervisor's Injury Report
• Contacts & Communication
  • Finalize list of validation participants along with contact information and test site location
  • Bridge line has been set up 617-452-5208 for up to 18 people thru December 14 
    • Can be used for emergency meetings over the weekend as well has for the Go/No-go on Sunday
  • Voice mail phone has been assigned 617-324-7468
    • A message will be recorded for system update status and validation testing times

December 9, 2009 SAPbiz - Update Project Status and Go-Live Plan

•  Progress to date
  • User acceptance testing - Testing is scheduled to be completed today
    • Users have been locked out of SH2
    • The last 2 days (12/8-12/9) are reserved for FI period closing and related testing
    • Exception = HR/Payroll testing that was delayed due to severe SAP support pack issue
  • Production updates
    • Preliminary System Updates we successfully applied to production this past weekend (12/5)
    • Up- time  production updates are being applied this week
  • Issues *{+}rt queue{+}* (https://help.mit.edu/Search/Results.html?Order=ASC&Query=%20Queue%20%3D%20'SAP%3A%3ATest%20Issues'%20%20AND%20'CF.SAP%3A%3ATest%20Issues.%7BSAP%20Project%20Name%7D'%20LIKE%20'SAP%20Support%20Pack%202009'%20%20AND%20Queue%20%3D%20'SAP%3A%3ATest%20Issues'%20&Rows=&OrderBy=Created&Page=1&Format='%20%20%20%3Cb%3E%3Ca%20href%3D%22%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__id__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3A%23'%2C%0A'%3Cb%3E%3Ca%20href%3D%22%2FTicket%2FDisplay.html%3Fid%3D__id__%22%3E__Subject__%3C%2Fa%3E%3C%2Fb%3E%2FTITLE%3ASubject'%2C%0A'__Status__'%2C%0A'__QueueName__'%2C%0A'__OwnerName__'%2C%0A'__Priority__'%2C%0A'__NEWLINE__'%2C%0A''%2C%0A'%3Csmall%3E__Requestors__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__CreatedRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__ToldRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__LastUpdatedRelative__%3C%2Fsmall%3E'%2C%0A'%3Csmall%3E__TimeLeft__%3C%2Fsmall%3E')
• Project Acceptance
  • Business owners required to accept the results of testing
  • Sign the sheet for your business area at the back of the room
    • Sign the sheet for your business area at the back of the room
  • We require you to say it's ok to move forward and update production this weekend
• Cut-over Plan (draft)
  •  Last Wednesday - an Email was sent and SAPWeb / SAPWebSS messages already in place
  •  Thursday
    • a reminder Email will be sent to community
    • Finalize and publish the go-live plan
    • Review all issues and transports
    • Steering Committee Meeting - Go/No-go decision
  • Friday - The system comes down at 12 noon
    • SAPWeb / SAPWebSS redirect pages are put up
    • SAP dropbox is stopped
    • SAP trial balance reports run and saved
    • Begin applying the support packages to production
  • Sunday - 12 noon production validation begins
    • SAP trial balance reports run and verified by L. Monks
    • SAIS prepares system for validation
    • By 3:00 pm data validation and transaction processing begins
    • By 7:00 pm data validation and transaction processing complete
    • 7:00 pm Go/No-go Conference call
• Communication
  • Email lists: sais-sap@mit.edu; sap-validation-team@mit.edu; sap-upgrade-core@mit.edu
  • Update status telephone number 617-324-7468 will be updated periodically  over the weekend *important note: check this message before you come in on Sunday
  • Conference call number 617-452-5208 will be open all weekend fall call ins

December 10, 2009 Core Team/ Action Log Team Transport / Cutover Plan Review

• Review and reconcile all RT tickets in project queue
• Complete Transport list review
• Validate and complete Go-live plan for Cutover weekend

December 10, 2009 Steering Committee 4-5pm W92-240 Riverside

Agenda:

1. Go / No Go decision
2. Golive plan 12/11-12/13
3. Post-golive support plan 12/14

...