1 / 15

Hub Upgrade and Market Release Strategy Overview June 2010

This overview describes the upgrade of the HUB and market release strategy with two versions of MPCC (15.1 and 16.0) to be implemented. It includes details on the IPT process, cutover dates, contingency plans, and market release procedures.

jael
Télécharger la présentation

Hub Upgrade and Market Release Strategy Overview June 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. High level overview of HUB upgrade and market release strategy June 2010

  2. Two Versions of the MPCC • MPCC 15.1 (existing test W2000 machine, but with Schema 8 installed on it) • MPCC 16.0 (new W2003/XP machine with schema 8)

  3. IPT Process

  4. IPT Strategy • To replicate the to-be situation, at least one MP is required to run IPT using MPCC 15.1 and, at the same time, at least one will use MPCC 16.0 This is a change to the process that was briefed at the November IGG

  5. Schema Release • March 19th. Dispatch upgraded schema 8 and two CDs to each MP. • CD1 MPCC 15.1 • CD2 MPCC 16.0

  6. Cutover

  7. By Thursday June 24th - Formal go/no-go confirmation from CER • Friday June 25th • 13.00 - Confirmation from RMDS • 18.00* - Market Participants are asked not to send in any Market Messages after this point • Saturday June 26th • Morning* - Application of changes • Afternoon* - Connectivity testing • All communications will be via RMDS over the cutover weekend * Times subject to validation through dress rehearsals

  8. Contingency/Rollback

  9. Hub Upgrade • Go/No-Go Decision prior to weekend • Hub Upgrade will precede the Market Release • Planned to involve TSO and MP1 in testing the hub upgrade • Therefore will require rollback plans for both their backend systems • On success, apply SAP transports to Central Market System – point of no return

  10. Market Release • Consists of SAP IS-U transports, RMP Extranet changes and MPCC 15.1 upgrade • Any issues with the Market Release will be addressed through fixing forward i.e. application of corrective transport

  11. MPCC 16.0 upgrade • Fallback is to switch production IP back to MPCC 15.1 in the event of a problem with MPCC 16.0

  12. Questions?

More Related