Versions Compared

Old Version 2

changes.mady.by.user Unknown User (bartd)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (bartd)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.
  • Definition of Enhance Packs
    • SAP's new approach to delivering new or enhanced functionality. Formerly included in support packs.
  • Rationale for including Enhancement Packs in this year's support pack project scope
    • Avoid a separate project to add these enhancement packs
      • $240K IS&T effort
      • Production freeze
      • Business testing, validation
      • Production outage
      • Production validation
      • Literally a repeat of the support pack project
    • Enhancement packs are a pre-requisite to new functionality
      • Required for Enterprise Learning Product - project sponsored by Training Alignment Team, HR, and approved by ASPCC
      • Required for other, newer SAP functionality that will be considered as part of 'Administrative System Roadmap'Details
      • See attachments for details of enhancement pack content for selected areas of potential interest to MIT. Full list is available here Support Documents.
    • MIT Lincoln Lab and other higher ed & research SAP customers following the same strategy
    • Approach recommended by project team, approved by sponsor and steering committee.
  • Risks & Mitigation
    • Enhancement Packs create problems with existing functionality used by MIT
      • Don't use Enhancement pack functionality until after year-end support pack project complete
      • Test all critical functions as part of the support pack project
      • Low probability since we don't use any of the new functionality
    • Production downtime increased increase may be required
      • Preliminary estimate and discussions with Lincoln indicated that additional downtime could fit within normal weekend window.
      • Test the process multiple times before golive
      • Test the process early in the project
      • If longer outage is required, start discussing and planning early in the project
      • Initial test results indicate longer time will be required. Very conservative estimate is ~70 hours (ex: Friday Noon - Monday 9am). Important to plan now, even if the additional time is not ultimately required.
      • Final schedule will be based on additional test results to determine expected time, detailed plans (including cushion for unexpected events, time & schedule to validate, time to back-out & restore if necessary, acceptable risk mitigation, ...) for golive