Copyright 2011, The NASDAQ OMX Group, Inc. All rights reserved.

Transcription

1 Copyright 2011, The NASDAQ OMX Group, Inc All rights reserved CHANGE MANAGEMENT FINAL 29 NOVEMBER 2012

2 Change Management These Change Management procedures cover the systems: INET Genium INET Genium Consolidated Feed (GCF) Separate procedures cf slide 20 2

3 Change Management Levels Bug Fixes Enhancements Mandatory upgrades System Migrations 3

4 Change Management Level Bug Fixes Type: Bug fix (urgent / normal) Usage: Issues having sufficient impact on market functionality - If the issue has general impact (not limited to a specific member or group of members) it should be published as a Known Limitation on the member site - Depending on the importance of the issue, an IT notice will also be sent detailing actions and implementation dates - NASDAQ OMX goal is to analyze an issue within 24 hours Regarding mandatory upgrades and system migration NASDAQ OMX will set up a separate list that will: be updated as soon as issues are identified contain all cases that t migh have test t or production impact 4

5 Typical Implementation Schedule Bug Fixes Day 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 IT-Notice Web update Specs ISV update Test Production environment 5

6 Change Management Level - Enhancements Type: Functionality enhancements and configurations/reference data changes Usage: Enhancements that are limited in scale and can be easily deployed - Website updated/it notice(s) sent detailing activities and dates for implementation - Time plan from first official notice 2-4 weeks for smaller non-mandatory changes, voluntary services, (normally configuration i changes) 1-3 months for larger non-mandatory protocol changes The enhancements applicable are additional or changed functionality when it comes to protocol changes For INET, enhancements connected to protocol changes will normally be implemented only once a month, at a fixed date, and bundled together with other protocol and configuration changes For Genium INET, enhancements connected to non-mandatory protocol changes bundled together with bug fixes and configuration changes will be implemented in scheduled service releases Examples: - New FIX tags (previous tag kept in parallel) - Min allowed quantity for non-displayed orders (MAQ) 6

7 Typical Implementation Schedule Enhancements Week-3 Week -2 Week -1 Week 0 Week 1 Week 2 Week 3-12 Week 4-13 Consultation/ pre-information Members/ISVs IT-Notice Web update Final Specs Test environment (ISV and Member) Production Time in test environment normally 2-4 weeks dependent on change Example: Tick size change Optional FIX tags 7

8 The Concept of the Monthly Release Schedule (INET only) 8

9 Change Management Level Mandatory Upgrades Type: Upgrades with mandatory changes Usage: New releases, significant functionality/technical mandatory changes, large market model changes Requires testing, ti certification, and launch procedures - Developed, tested and delivered in a project organization - Communication plan, IT Forums, web site updates, training, and other member readiness activities - Production follow-up pperiod after implementation Example: - Major change in matching logics - Mandatory protocol updates 9

10 Typical Implementation Schedule Mandatory Upgrades Month - 2 Month - 1 Month 0 Month 1 Month 2 Month 3 Month 4 Month 5 Month 6 Month 7 Consultation/ pre-information Members/ISVs Test environment (ISV and member) Final version specs IT-Notice Web update Preliminary version specs Member ISV appl certified MWATs (if needed) Production Production follow-up period Example: Mandatory update of protocols 10

11 Change Management Level System Migrations Type: System migrations Usage: Replacing central trading platform, mandatory protocol replacements Requires major testing, certification, and launch procedures - Developed, tested, and delivered in a project organization - Communication plan, IT Forums, web site updates, training, and other member readiness activities - Production follow-up pperiod after implementation Example: - New technical platform - Mandatory protocol replacements 11

12 Typical Implementation Schedule System Migration Month Member consultation period Publication of Market Model and Migration Support Package Publication of draft specifications Publication of final Master Time Schedule Publication of final specifications Reference data download External training offered Test Phase Limited functionality available Freeze config in test environment Full functionality available Certification period Trading platform migration or protocol replacement MWAT period Go-live 12

13 System Migration Phases Member consultation on migration plans - Market participation and Master Time Schedule - Review of proposed market model and draft specifications - Check point of progress before test phase starts Test phase start - Final specifications in place - Stable test environments - Organisation for support complete - External training gplan offered to the market - Regular check points for application development Certification phase - Completed certified ISV applications including NASDAQ OMX applications before MWAT starts - Extended d test environment availability - End to end testing available, including all protocols available MWAT and launch phase - Freeze configuration in test environment - Availability for production connectivity test - Test environment in production mode - Follow up and lessons learned after go-live 13

14 General If testing, internal as well as external, discovers bugs or other faulty behavior, the time plans presented for the four different change levels will be adjusted to meet the standard, predefined time plan NASDAQ OMX goal is to analyze an issue within 24 hours The Known Limitations list should be updated as soon as the problem is identified Reference data - INET will normally be updated from the production system to the test system once a week - Genium INET reference data will be updated d when needed, d and will be communicatied to the market through necessary IT notices 14

15 15 INET Nordics Test System Copyright 2011, The NASDAQ OMX Group, Inc All rights reserved

16 Test System INET OTF NASDAQ OMX offers possibility to use subset of order books to support testing of new functionality NASDAQ OMX provides separate ports for testing of upgraded protocols Mandatory upgrades shall as a general rule be handled using additional OTF setup giving the possibility to test both present and future functionality There may, however, be instances where that will not be the case 16

17 17 Genium INET Nordics Test System Copyright 2011, The NASDAQ OMX Group, Inc All rights reserved

18 Test System Genium INET Normal operations, consists of 2 external environments - Ext1, trading and clearing with GCF feed, current version - Ext3, trading only, extended opening hours with GCF feed, current version Non mandatory releases - External 1 and 3 environments will be upgraded in accordance with normal guidelines (2-6 weeks in advance) - Might include External 2 environment, dependent on impact Mandatory releases with additional test environment - Giving the possibility to test both present and future versions Additional test environment includes clearing and GCF feed but might include limitations depending on other current initiatives Maintenance during office hours according to communicated schedules 18

19 19 Genium Consolidated Feed (GCF) Copyright 2011, The NASDAQ OMX Group, Inc All rights reserved

20 GCF Changes to GCF that require a new release of the TIP procotol are mandatory for those utilising the changes in question It is the sole responsibility of TIP subscribers to ascertain their need for implementing the new TIP release Planned changes to the protocol are published 3 months prior to launch in production If, however, a change to GCF is because of changes in INET or Genium INET, the Change Management procedures for the relevant of those two systems shall be followed NASDAQ OMX will do its utmost to synchronise changes in GCF with the trading systems Updates to the final TIP protocol can occur without streching the production launch date Such updates will be preceded by a consultation with TIP subscribers The ambition is to have all changes available in a test environment at the latest 2 weeks after publication of the protocol Changes are published in the Global Data Products Nordic Weekly Newsletter and through IT Notices Corrections and clarifications to the description in the TIP protocol do not require a new TIP release Such are informed about through an Errata document and published in the Global Data Products Nordic Weekly Newsletter 20