Single Electricity Market

Size: px
Start display at page:

Download "Single Electricity Market"

Transcription

1 Single Electricity Market SEM R2.0.0 INTRA-DAY TRADING MARKET TRIAL APPROACH COPYRIGHT NOTICE All rights reserved. This entire publication is subject to the laws of copyright. This publication may not be reproduced or transmitted in any form or by any means, electronic or manual, including photocopying without the prior written permission of EirGrid plc and SONI Limited. DOCUMENT DISCLAIMER Every care and precaution is taken to ensure the accuracy of the information provided herein but such information is provided without warranties express, implied or otherwise howsoever arising and EirGrid plc and SONI Limited to the fullest extent permitted by law shall not be liable for any inaccuracies, errors, omissions or misleading information contained herein. Page 1 of 30

2 Table of Contents 1 Introduction Purpose Audience Scope Document Structure Market Trial Approach Introduction Objectives Principles Approach Deliverables Assumptions Market Trial Scope Introduction Market Trial Stages Market Trial Cycles, Scenarios and Scripts Market Trial Scope Market Trial Acceptance Criteria Market Trial Management and Control Introduction Organisation of Market Trial Workstream Market Trial Reporting and Communication Market Trial Scheduling Market Trial Data Market Trial Environments Configuration Management Release Management Defect Management Market Trial Acceptance Roles and Responsibilities Introduction SEM R2.0.0 Project Team SEMO IT Market Participants Responsibility Matrix...29 Page 2 of 30

3 Document History Version Date Author Comment February 2012 SEMO Initial version Distribution List Organisation All SEM Stakeholders NIAUR CER Source / Reference Documents Document Name Document Reference Page 3 of 30

4 1 INTRODUCTION 1.1 PURPOSE This document outlines the overall approach for the Market Trial phase of the Intra-Day Trading SEM R2.0.0 release, scheduled for deployment on July 20 th 2012, subject to successful completion of testing. This document describes the test cycles and scenarios that will be used for the Market Trial phase. Market Trial will require the active participation of all Market Participants. The purpose of this document is to: Define the overall approach that will be adopted for Market Trial; Outline the Market Trial deliverables that will be produced prior, during and following Market Trial; Define the Market Trial entry and exit criteria; Define the scope of Market Trial, including a description of all test cycles and associated scenarios that will be performed in Market Trial; Identify the roles and responsibilities of the various parties involved in Market Trial; Outline the overall management controls and procedures that will be adopted during Market Trial; and Set out the Market Trial plan for the test activities. This document does not include activities to test Market Participants (MPs) own internal systems. 1.2 AUDIENCE The target audience for this Market Trial document is the SEM Intra-Day Trading Project including, EirGrid, SONI, TSOs, the Moyle IA, the EWIC IA, MDPs, SEMO and the Market Participants. 1.3 SCOPE This document outlines the overall approach for conducting and managing Market Trial activities and defines the roles and responsibilities of the various parties involved in testing. In addition, this document outlines the scope of those activities as well as the deliverables to be produced prior to, during and following testing. It should be noted that detailed Market Trial scenarios and scripts as well as a detailed Market Trial work-plan are not within the scope of this document. These will be documented as separate deliverables. 1.4 DOCUMENT STRUCTURE Following this introduction, the remainder of this document is structured as follows: Section 2 Market Trial Approach, sets out the overall approach and principles to be adopted by the Intra-Day Trading SEM R2.0.0 Project Team for Market Trial and outlines the key objectives of Market Trial. It also details the various deliverables that will be produced to support Market Trial activities; Page 4 of 30

5 Section 3 Market Trial Scope, describes the scope of each of the Market Trial stages and explains the overall approach to be adopted for the development of test documentation (e.g., test cycles, scenarios and scripts). In addition, it provides a description of the test cycles and scenarios that will be used in Market Trial and outlines the acceptance criteria for Market Trial. Finally, it explains how Market Trial will be performed; Section 4 Market Trial Management and Control, describes the key management activities, controls and procedures that will be used to manage and support Market Trial; Section 5 Roles and Responsibilities, describes the roles and responsibilities of the various parties involved in Market Trial. Page 5 of 30

6 2 MARKET TRIAL APPROACH 2.1 INTRODUCTION This section sets out the overall approach and principles to be adopted by the Intra-Day Trading SEM R2.0.0 Project Team for Market Trial and outlines the key objectives of Market Trial. Furthermore, it details the various deliverables that will be produced to support Market Trial activities. 2.2 OBJECTIVES The key objectives of Market Trial are as follows: Provide a controlled environment for Market Participants, TSOs, the IA and the MDPs to test new Intra-Day Trading SEM R2.0.0 functional and technical changes and to verify that these changes have had no adverse impact on existing functionality; Demonstrate that the Central Market Systems and interfaces utilised by the Market Participants are operating (functionally and technically) as intended for real market operations; and Provide assurance that SEMO delivers its obligations under the Trading and Settlement Code. 2.3 PRINCIPLES The overall approach to performing Market Trial will be guided by the following high-level principles: Clearly defined roles and responsibilities; Clearly defined, structured approach to test planning, preparation and execution; Efficient co-ordination and management of testing; Tests prioritised by criticality and coverage; Structured communication process to report Market Trial progress; Pragmatic solutions where necessary to address any inconsistencies between systems and processes to minimise any potential delays to the release; Market Trial will be independent from other test phases (e.g. System Integration Test) by having a specific set of entry and exit criteria which must be met before testing can commence or conclude successfully; and Required resource skills will be specified as early as possible during Market Trial planning stage. Page 6 of 30

7 2.4 APPROACH The overall approach to be adopted for Market Trial activities will be as follows: Market Trial Planning and Preparation - Develop Market Trial approach and detailed work-plan; - Define test cycles and scenarios; - Develop test scripts; - Finalise test data requirements; - Ensure that test environments are made available on time for Market Trial; - Ensure that resources are available to carry out tests and report problems. Pre-Market Trial Activities - Populate Central Market Systems with initial data sets required for Market Trial; - Back-up databases following completion of data population; - Ensure that backed-up databases can be easily restored on Central Market Systems; - Ensure that Market Participants can connect to the Central Market Systems. Market Trial Execution - Ensure that test entry criteria are met; - Coordinate and supervise execution; - Capture test evidence; - Address and resolve issues; - Monitor progress of testing against plan; - Report progress and defects to the SEMO management team; the RAs and Market Participants; - Take necessary actions to improve progress and recover lost time; - Record, analyse and facilitate resolution of potential defects; - Re-schedule testing, as necessary; - Ensure that test exit criteria are met. Post Market Test Activities - Back-up and archive Market Trial environments following completion of Market Trial activities; - Produce Market Trial exit report. Market Trial will be conducted in accordance with the schedule published by the SEMO Intra-Day Trading SEM R2.0.0 Project Team. All defects relating to the Central Market Systems that are identified during Market Trial will be logged on the project s test defect management tool and reported to the SEMO management team; the RAs and Market Participants. Defects will be fixed by the responsible parties within the agreed timescales (see Section 4.10 for further details). All fixes, where appropriate, will be tested on a separate test environment prior to being released onto the Market Trial environment for re-testing. Page 7 of 30

8 2.5 DELIVERABLES To support Market Trial activities, a number of key deliverables will be produced by the SEMO Intra-Day Trading SEM R2.0.0 Project Team. These deliverables will include the following: Market Trial Approach: This deliverable sets out the overall approach and principles to be adopted for Market Trial; Market Trial Detailed Work-Plan: This deliverable contains details of the day-to-day Market Trial activities; Market Trial Control Sheet: This deliverable contains a cross-reference of all the test cycles, scenarios and scripts that will be used to perform Market Trial. It lists the test scenarios and scripts that will be used for testing. Market Trial Scripts: This deliverable contains the test scripts that will be used for testing. Each test script will provide detailed step by step procedures for the execution of the tests, including test data requirements and expected results; Market Trial Data: This deliverable contains the data requirements and data sets that will be used for performing the tests. This will be confirmed at the top of each test script; and Market Trial Exit Report: This deliverable summarises the outcome of Market Trial. 2.6 ASSUMPTIONS A number of key assumptions have been made when developing the Market Trial Approach document. These are detailed below: Test entry criteria must be met prior to commencement of Market Trial; Test exit criteria must be met before Market Trial can be accepted as complete; Development of Market Trial deliverables will be the responsibility of the SEMO Intra-Day Trading SEM R2.0.0 Project Team and Market Participants; Overall management of the Market Trial activities will be the responsibility of the SEMO Intra- Day Trading SEM R2.0.0 Project Team; A number of tests (e.g. connectivity test) and initial data set-up activities will be performed prior to the start of Market Trial (i.e. pre-market Trial ) to ensure that the required infrastructure is set-up and functioning as expected; Testing will be conducted against agreed Market Trial scope; Appropriate defect management processes will be in place; Appropriate configuration and release management processes will be in place; Historical production data will be used to execute Market Trial; Market Trial will be based on production data and any sensitive test data will be masked; Market Participants will nominate a single point of contact in order to facilitate co-ordination of Market Trial activities; All Market Participants will be invited to participate in Market Trial. SEMO would strongly recommend Participants to actively engage in Market Trial activities. Page 8 of 30

9 3 MARKET TRIAL SCOPE 3.1 INTRODUCTION This section describes the scope of Market Trial and explains the overall approach to be adopted for the development of the test documentation (test cycles, scenarios and scripts). It also provides a description of the test cycles and associated scenarios that will be used in Market Trial and outlines the Market Trial acceptance criteria. 3.2 MARKET TRIAL STAGES Market Trial will include a number of discrete test scenarios, reflecting the changes to the Central Market Systems post-implementation of the Intra-Day Trading SEM R2.0.0 Release. During the execution phase of Market Trial all test scripts will be performed using the defined test data. Actual results will be documented and compared to the expected results. Any discrepancies between actual and expected results will be analysed and if appropriate, a defect will be raised by the Market Trial lead on the project s defect management tool. Prior to the commencement of Market Trial a schedule will be made available to all Market Participants, detailing the day-to-day test activities. The execution of the test scenarios and associated scripts will be performed by dedicated testers. The specific approach to the execution of each of the Market Trial stages is detailed below. As a general rule, all fixes to defects identified during the first pass of Market Trial will be tested in the subsequent pass. When a problem is identified that prevents the tester from completing a script, the tester will log the problem and continue testing another script. The notable exception to this rule will be for problems that render the entire system unusable (Severity Class 1). In such a case, all testing activities shall be immediately stopped and the impacted parties shall evaluate and correct the defect before testing can resume. 3.3 MARKET TRIAL CYCLES, SCENARIOS AND SCRIPTS Market Trial will comprise a number of test cycles, each of which will comprise a number of test scenarios and associated scripts. These are explained in more detail below: Test Cycle: Test Cycles are logical groupings of the overall functionality and technical areas that will be addressed by Market Trial. Test cycles will be used to facilitate the execution of tests. Each test cycle will contain one or many test scenarios. Test Scenario: Test scenarios are high-level descriptions of the functional and technical areas that will be tested in Market Trial. Each test scenario will contain one or many test scripts. Test Script: A test script details the exact steps that a tester must follow to complete testing and includes details of the data that will be used for that particular test. Page 9 of 30

10 For the purpose of Market Trial, test scripts will be developed in two stages: - Stage 1: The Intra-Day Trading SEM R2.0.0 Project Team will develop test scripts that provide step-by-step process requirements, data requirements and expected results for each scenario. - Stage 2: Market Participants will be expected to develop their own test scripts based on the test scripts provided by SEMO that give instructions specific to the systems and local working procedures they will be using. Page 10 of 30

11 3.4 MARKET TRIAL SCOPE To ensure that the new system changes are tested as comprehensively as possible within the allocated time, an exercise was undertaken to determine the most appropriate test cycles and scenarios for Market Trial. Table 2 provides a description of the test cycles and test scenarios that will be used in Market Trial. The scope of Market Trial will cover new and modified functionality delivered by the Intra-Day Trading SEM R2.0.0 Release. The scope of Market Trial will exclude the testing of internal functionality of Market Participant, TSO and IA systems. The functional changes within approved scope of the Intra-Day Trading SEM R2.0.0 Release which have an impact on Market Participants are as follows: Table 1 Changes Impacting Market Participants Change Ref. Description Impact on Participants Mod_18_10 Trading Change of timing on EA Gate Window. Timing of Bid submissions Mod_18_10 Trading Addition of EA2 Gate Window & Pricing Run. Bid submissions for Type 2 and Type 3 communications. Mod_18_10 Trading Addition of WD1 Gate Window & Pricing Run. Bid submissions for Type 2 and Type 3 communications. Mod_18_10 Trading Additional fields for COD submissions. Bid submissions for Type 2 and Type 3 communications. Mod_18_10 Trading Additional fields for Interconnector submissions. Bid submissions for Type 2 and Type 3 communications. Mod_18_10 Trading Additional fields for VTOD set selection. Set selection for Type 2 and Type 3 communications. Mod_18_10 Reporting Additional 40 new reports. New Reports. Mod_18_10 Reporting 27 Reports have altered fields. Modified Reports. Mod_18_10 Settlements Statements, invoices & settlement reports will include the 3- interconnector units. Modified Statements, Invoices & Settlements Reports. Page 11 of 30

12 Change Ref. Description Impact on Participants CR287 CRM Inclusion of Breach Amount in the Credit Risk Report. Modified Report. Page 12 of 30

13 Table 2 Market Trial Cycles and Scenarios Test Cycle Test Cycle Name Test Cycle Description ID Test Scenario Name Test Scenario Description 1 Technical Interface Connectivity Testing This cycle will test the technical interfacing with the Central Market Systems. 1.1 Connect to the IDT Market Test URL using type Connect to the IDT Market Test URL using type 3 This scenario will verify the correct IDT type 2 client prerequisites. It will also confirm the pilot cert. This scenario will verify the correct IDT type 3 client prerequisites. It will also confirm the pilot cert. 1.3 Reports listing & download This scenario will verify the correct permissions within the IDT test systems. 1.4 File Upload & bid offer submission & query This scenario will verify the new forms player is working correctly. 2 Submission Interface Testing This scenario will test interfaces and processes modified by the release. 2.1 Commercial Offer Interface TestsCOD Submissions This scenario will test COD submissions based on the changes implemented for SEM R2.0.0.This scenario will test IDT modifications in relation to Commercial Offer Data for type 2 and type 3 communications. 2.2 Interconnector SubmissionTechnical Offer Interface Tests This scenario will test Interconnector submissions based on the changes implemented for SEM R2.0.0.This scenario will test IDT modifications in relation to Technical Offer Data for type 2 and type 3 communications. 2.3 Technical Offer ChoiceInterconnector Interface Tests This scenario will test Technical Offer Choice submissions based on the changes implemented for SEM R This scenario will test IDT modifications in relation to Interconnector Data for type 2 and type 3 communications. Page 13 of 30

14 Test Cycle Test Cycle Name Test Cycle Description ID Test Scenario Name Test Scenario Description 2.4 MSP Cancellation Tests This scenario will test the new IDT process of when an MSP Software run is cancelled. 2.5 New Reports This scenario will test any new reports as a result of IDT for type 2 and type 3 communications. 2.6 Updated Reports This scenario will test updates to any existing reports as a result of IDT for type 2 and type 3 communications. 2.7 Settlements Updates Tests This scenario will test any settlement updates as a result of IDT for type 2 and type 3 communications. 3 Report Interface Testing This scenario will test the reports that have been altered as a result of the SEM R Reports with content changes This scenario will test the Report that have content changes as a result of the implementation for SEM R MSP Cancellation Report This scenario will test the cancellation of an MSP software run. 3.3 ACC Report This scenario will test the new ACC Report. 3.4 Excluded Bids Report This scenario will test the new Excluded Bids Report. 4 Settlements Interface Testing This scenario will test the Settlement Interfaces that have been altered as a result of the SEM R PIRS This scenario will test the Settlement PIR reports. 4.2 Participant Statements This scenario will test Participant Statements 4.3 Credit Risk Report This scenario will test the Credit Risk Report. 4.4 Cancelled Reallocation Agreement This scenario will test the CSRA Report Page 14 of 30

15 Test Cycle Test Cycle Name Test Cycle Description ID Test Scenario Name Test Scenario Description 3 End to End testing This scenario will allow the participant to perform testing from bid to bank. 3.1 EA Processing This scenario will cover daily processing activities up to the production of the ex-ante market schedule and associated reports. 3.2 EA2 Processing This scenario will cover daily processing activities up to the production of the EA2 Market Schedule and associated reports. 3.3 WD1 Processing This scenario will cover daily processing activities up the production of the WD1 Market Schedule and associated reports. 3.4 EP1 Processing This scenario will cover daily processing activities up to the production of the EP1 Market Schedule and associated reports. 3.5 EP2 Processing This scenario will cover daily processing activities up to the production of the EP2 Market Schedule and associated reports. 3.6 Weekly Processing This scenario will cover weekly processing activities (e.g. energy settlement) and associated reports. 3.7 Monthly Processing This scenario will cover monthly processing activities (e.g. capacity settlement) and associated reports. 4 Ad Hoc testing This scenario will allow the participant to perform ad hoc tests of any nature for the duration of Ad-hoc testing This test phase has been set aside for Participants to perform any ad-hoc (unscripted) testing they require. Page 15 of 30

16 Test Cycle Test Cycle Name Test Cycle Description ID Test Scenario Name Test Scenario Description this phase. Page 16 of 30

17 3.5 MARKET TRIAL ACCEPTANCE CRITERIA In general, acceptance criteria consist of a set of conditions that must be met before allowing a test phase (e.g., Unit Test, Factory Test, Site Test, etc.) to commence or to end. Acceptance criteria consist of both entry criteria, i.e., the criteria that must be met before a test phase can begin, and exit criteria, i.e., the criteria that must be met before a test phase can be considered complete. Entry criteria for a test phase typically include requirements that all test inputs for that phase have been prepared and that the previous testing phase has been successfully completed. Exit criteria typically include requirements on the number of defects outstanding, and that all tests have been completed and signed-off. Where failure of a test phase to satisfy the defined exit criteria is the cause of schedule delays, it is necessary to carefully consider whether the test phase can be considered complete without all exit criteria being satisfied. Generally, the risks of passing errors from one testing phase to another test phase, or to Production systems, are too great to allow deviation from the predefined exit criteria. In such a case, SEMO IT management approval will be required. For the purposes of Market Trial for the Intra-Day Trading SEM R2.0.0 release, the following entry and exit criteria will apply: Entry Criteria - System Integration Testing of the relevant changes of the Central Market Systems has been successfully completed; - All necessary Market Trial documentation (Test Approach; Detailed Work-Plan; Test Conditions; Test Cycles; Scenarios and Scripts) has been developed and approved; - Market Participants have communicated readiness to begin Market Trial. If a Market Participant is not ready to participate in Market Trial they will have to seek the RAs approval to extend the Market Trial schedule. The RAs will direct SEMO accordingly; - Test data has been prepared; - Support and test execution resources have been allocated to tests and have been made available; and - Dedicated test environments have been set-up. Exit Criteria - Class 1 and 2 defects identified have been corrected and successfully re-tested; - Class 3 and 4 defects identified have been corrected and successfully re-tested, unless a later date correction plan and / or workaround has been agreed by the SEM R2.0.0 Project Team; and - All test results, including supporting evidence have been properly documented, reviewed and signed off. Page 17 of 30

18 4 MARKET TRIAL MANAGEMENT AND CONTROL 4.1 INTRODUCTION This section outlines the key management activities, controls and procedures that will be used to support Market Trial activities. Specifically, this section addresses the following areas: Organisation of Market Trial Workstream; Market Trial Reporting and Communication; Market Trial Scheduling; Market Trial Data; Market Trial Environment; Configuration Management; Release Management; Defect Management; and Market Trial Acceptance. 4.2 ORGANISATION OF MARKET TRIAL WORKSTREAM The overall management of Market Trial will be the responsibility of the Market Trial workstream leads (functional and technical). The roles and responsibilities of the Market Trial leads and the Market Trial team are explained in detail below: Market Trial Leads - Overall planning, management and coordination of all Market Trial activities; - Re-scheduling and re-prioritising tests if necessary; - Liaising with Market Participants; - Chairing daily defect management meetings; - Reviewing and agreeing the classification and resolution of defects; - Recording any defects identified during Market Trial relating to the Central Market Systems on the project s defect management tool; - Reviewing and agreeing the content and timing of any software / hardware releases with SEMO; - Escalating issues when necessary to the SEMO IT Manager; - Monitoring and reporting progress to the SEMO IT Manager; and - Ensuring that all tasks are performed both to quality and timescale. Page 18 of 30

19 Market Trial Workstream Team Overall coordination of Market Trial activities within own application area; Developing test scripts and expected results for one or more test scenarios; Preparing test data for Market Trial; Ensuring that all input documentation required for the tests is available; Checking the prerequisites for the execution of test scripts and ensuring that all required test data has been loaded onto the system; Performing the steps in the test scripts and documenting actual results; Producing supporting test evidence such as screen-prints or any other documentation; Documenting the final status of tests and signing-off the tests; Analysing and resolving where appropriate, test defects; Re-testing defect fixes; and Informing the Market Trial workstream lead of any issues that may affect the schedule or quality of the testing process. Throughout Market Trial, it is envisaged that the Market Trial workstream will be supported by dedicated software vendor resources. Market Participants should also organise and provide their own dedicated vendor support, as required. In addition, it is expected that all Market Participants involved in Market Trial will nominate a single point of contact in order to facilitate the co-ordination of Market Trial preparation activities, the execution of tests and the resolution of any issues arising from Market Trial. The following diagram provides an illustration of the Market Trial workstream structure and its interaction with other project work streams and Market Participants. Figure 2 Market Trial Workstream Structure SEMO General Manager Market Operations Market Development Finance IT Legal SEM R Project SEM R Project Management Market Participants Software Vendors Project Office Functional Workstream Technical Workstream Market Trial Workstream Market Participants Test Co - Ordination Centre ( TCC ) Single Point of Contact ( per Participant ) Page 19 of 30

20 4.3 MARKET TRIAL REPORTING AND COMMUNICATION Testing requires effective communication with all impacted parties. Throughout Market Trial, the Market Trial workstream is expected to work closely with the Market Participants through the establishment of a dedicated centre called the Test Coordination Centre (TCC). The Test Coordination Centre will ensure that test activities are progressed as smoothly as possible. The key responsibilities of the Test Coordination Centre are as follows: Coordinating preparation and execution phases; Developing scenarios and scripts; Monitoring progress; and Managing execution of the test schedule. Market Participants will use the markethelpdesk@sem-o.com address with IDT: Market Trial_ <Query Detail> as the subject title when logging enquiries and issues relating to Market Trial. The key meetings that will be held during the preparation and execution of Market Trial are as follows: Market Trial Consultations SEMO hope to have full involvement of Market Participants in the preparation of the Market Trial phase. There will be several workshops/conference calls arranged to review the Market Trial approach document, Detailed Work plan, Market Trial control sheet, Test Scenario s and scripts and technical requirements. Market Trial Technical Kick-Off meeting (Conference Call) SEMO propose to initiate the Market Trial Technical phase with a conference call on Monday April 23rd, 2012 at 10:00. The conference call details are as follows: Conference Call Number: +353 (01) Participant PIN: The purpose of this meeting is to ensure participants have the correct connection details for Market Trial and to discuss any concerns Market Participants might have. Market Trial Functional Kick-Off meeting (Conference Call) SEMO propose to initiate the Market Trial Functional phase with a conference call on Monday April 30th, 2012 at 10:00. The conference call details are as follows: Conference Call Number: +353 (01) Participant PIN: Page 20 of 30

21 The purpose of this meeting is to ensure participants are set up to commence testing and are aware of the planned test schedule for the week ahead. Daily Meetings / Conference Calls Each day during Market Trial execution, the Market Trial leads and the Market Participants will have a meeting to review issues and defects that were discovered during that day. Depending on their classification, defects will be prioritised for fixing and re-testing. Note that this meeting is not intended to discuss the details of the defects nor how to fix them. The key activities of the daily review meeting are as follows: - Reviewing and classify defects; and - Assigning queries and issues for answers and resolution. End of Market Trial Review At the conclusion of Market Trial, a test exit report will be produced. This report will provide a summary of the Market Trial results and details of any outstanding defects following completion of each of the Market Trial stages. This report will be presented in an end-of-market Trial review meeting and will include plans on how to complete the final set of any outstanding defects. This meeting will be attended by the SEMO IT Manager, the Market Trial leads and the Market Participants. It should be noted that the Market Trial Exit Report will be distributed to all impacted parties prior to this meeting taking place. In addition to the meetings described above other review meetings (as and when required) will be held separately with the Market Participants to discuss and resolve any issues arising from Market Trial. 4.4 MARKET TRIAL SCHEDULING The success of testing depends on the ability to schedule and execute tests effectively. In advance of testing, it is important that the test schedule and scope of tests is clear so that all parties know exactly what needs to be performed every day during the testing period and contention with other work streams or external activities is avoided. The ability to act promptly to deal with defects (errors discovered during testing) and to reschedule tests accordingly, is also key to the successful completion of testing. Parties involved in testing must therefore be flexible to alter their activities when the test schedule changes. The responsibility for producing a detailed work-plan and scheduling the Market Trial activities lies with the Market Trial leads. During the test execution period, the detailed test work-plan will be updated daily to reflect testing progress. This plan will also be used to schedule any re-tests resulting from a test failure. Testing of Market Trial scripts will be scheduled by priority. This will ensure that in the event where tests are not completed within the allocated time, it will be the least critical tests that Page 21 of 30

22 are not performed. Finally, tests will be structured in a way that avoids any conflicts in the performance of those tests. 4.5 MARKET TRIAL DATA To ensure the smooth execution of Market Trial, it is essential that appropriate test data sets are prepared prior to testing. These data sets will be used to either populate the Central Market Systems with initial test data or will be used during the course of testing. Test data sets will cover Market Participants; the TSOs; Meter Data Provider and Interconnector Administrator data. The Intra-Day Trading SEM R2.0.0 Project Team will be responsible for providing Production data up to end of March Testing activities will require historic production data for specific dates to meet the requirements of each test scenario. These dates are confirmed at the top of each Test Script. 4.6 MARKET TRIAL ENVIRONMENTS For the purposes of performing Market Trial, two different physical environments will be managed by the SEMO IT Project Team, each containing a single instance of the Central Market Systems. The first environment, Market Trial Environment, will be used for the execution of Market Trial. The second environment, Staging Environment, will be used to test any fixes prior to these being released onto the Market Trial environment for further retesting. It should be noted that the Market Trial Environment should be configured in a way that allows Market Participants to access these systems. Market Participants are expected to have their own environment(s) to facilitate testing activities of their internal systems, as required. The following diagram provides an illustration of the SEM R2.0.0 Project test environments required for Market Trial: Figure 3 Market Trial Environments In - Scope SEM IDT Project Team Out - Of - Scope SEM IDT Project Team External Parties MT Environments MT Fixes MT Test Environment Market Participant Staging Test Environment Market Trial Environment Market Participant Market Participant Page 22 of 30

23 4.7 CONFIGURATION MANAGEMENT It is expected that both the Intra-Day Trading SEM R2.0.0 Project and Market Participants will have appropriate configuration management processes in place during Market Trial to ensure that testing is conducted against agreed software, hardware and documentation versions. 4.8 RELEASE MANAGEMENT Release management schedules the development, testing and roll-out of new software and hardware versions that are being implemented to correct defects and / or to deliver planned enhancements to software / hardware products. It is expected that both the Intra-Day Trading SEM R2.0.0 Project and Market Participants will have appropriate defect management processes in place during Market Trial. All Market Trial defect fixes will be bundled into groups and released on to the software and / or hardware in a controlled manner. The timing for fix releases will depend on the severity class of the defect. The content and timing of any fix releases relating to the Central Market Systems will be determined by the Market Trial workstream leads. Market Participants will be notified of any fix releases by the Market Trial workstream leads and a re-test schedule will be agreed with the Market Participants, where necessary. 4.9 DEFECT MANAGEMENT Defects are defined as being observed discrepancies between expected and actual test results. Defect management tracks and manages the discovery, classification, resolution, correction and re-test of all defects identified during test execution. This process involves: Recording, reviewing, and prioritising defects; Assigning defects to developers for fixing; Assigning testers to re-test fixes; and Closure of defects. The Market Trial defect management tool will reside on the Intra-Day Trading SEM R2.0.0 Project local network. It should be noted that the defect management tools will not be used to log defects that relate to Market Participants own systems. Once a defect relating to the Central Market Systems has been identified it will be categorised as follows: Page 23 of 30

24 Central Market Systems error: Central Market applications did not execute in accordance with the expected results, i.e., the expected results were correct and the correct data was used for the test but the system is at fault; Interface error: the interface used in the test is at fault; Test script error: the system specification is not correctly reflected in the test script; and Test data error: the data used for the test is incorrect. All Central Market Systems defects identified during testing will be reviewed on a daily basis by the Market Trial leads and the Market Participants. Defects will be resolved within the agreed timescales. Once defects have been resolved, new releases of the software / hardware will be made available for re-testing. In exceptional circumstances, it may be possible to defer the fixing of a defect by implementing a workaround; however, this may increase the risk to the running of the Central Market Systems and as such, should only be viewed as a temporary arrangement with a view of resolving the defect in the long-term. The following figure provides details of the proposed defect management process, whereas the following table provides an explanation of the different defect severity classes and the Service Level Agreements (SLAs) required to: (i) (ii) raising defects and resolving these defects. Page 24 of 30

25 Figure 4 Defect Management Process Market Trial Approach (SEM Release R2.0.0) Daily Defect Management Process Responsible Party End - of - Day Tester (SEM R2.0.0 Project / Market Participants) Perform Test Record Test Issue Perform Re - Test Sign - off Re - Test SEM R2.0.0 Project / Market Participants Review Test Defect(s ) & Record Correction Plan Resolve Defect(s ) in Accordance with Action Plan Market Test Trial Workstream Lead Generate Daily Management Defect Report Review and Agree Defect(s ) Action Plan With Software Vendor Page 25 of 30

26 Table 3 Defect Classification and SLAs Severity Class Severity Explanation Service Level Agreement Raise Defect Defect Resolution Time Class 1 Defects that render the entire system 1 hour As soon as Critical Fault (i.e., all Central Market Systems) possible unusable. All testing activities shall be immediately stopped and the SEM R2.0.0 Project Team or Market Participants, as appropriate, shall evaluate and correct the defect before testing is resumed. Class 2 Defects that render unavailable a critical 1 working day 3 working days Major Fault function of the Central Market Systems. after submitting These include drastic program or defect, or to be system errors, such as application failures, inability to perform data transfers, failure to access databases, agreed by the SEM R2.0.0 Project Team and inability to display information to the user. These types of errors do not permit the testing continuation of the affected function. Testing of the relevant test script shall be immediately stopped and the SEM R2.0.0 Project Team or Market Participants, as appropriate, shall evaluate and correct the defect before testing is resumed. Class 3 Serious Fault Defects that produce erroneous or unexpected results from any material function of the systems but have a low material impact on the Central Market Systems. Testing will continue and the defect will be evaluated and corrected by the SEM R2.0.0 Project Team or Market Participants, as appropriate, within the agreed timescales. 1 working day 5 working days after submitting defect, or to be agreed by the SEM R2.0.0 Project Team. Class 4 This class of defect includes items that 1 working day To be agreed by Minor Fault do not significantly affect the usability of the SEM R2.0.0 the systems, such as an error in text or Project Team view displayed, data presentation, colours, spelling errors or documentation errors (including test scripts). Testing will continue and the defect will be evaluated and corrected Page 26 of 30

27 Severity Class Severity Explanation Service Level Agreement Raise Defect Defect Resolution Time at a time determined by the SEM R2.0.0 Project Team or Market Participants, as appropriate, within the agreed timescales MARKET TRIAL ACCEPTANCE Acceptance of Market Trial is based on the Market Trial exit criteria being met. At the end of Market Trial, a test exit report will be produced providing a summary of the Market Trial results and details of any outstanding defects. This report will form the basis for the acceptance / rejection of Market Trial. The responsibility for accepting / rejecting Market Trial lies with SEMO and the RAs. Once completed, the exit report will be submitted to SEMO and the RAs for review and approval. Sign-off of the exit test report will signify that Market Trial has been completed successfully, and therefore can be brought to a close. Page 27 of 30

28 5 ROLES AND RESPONSIBILITIES 5.1 INTRODUCTION This section describes the roles and responsibilities of the various organisations involved in Market Trial, including Market Participants. The success of Market Trial is highly dependant on the preparations made by a number of key organisations. These are as follows: SEM R2.0.0 Project Team; SEMO IT; Market Participants; TSOs; The IA; MDPs. 5.2 SEM R2.0.0 PROJECT TEAM During and prior to Market Trial, the SEM R2.0.0 Project Team will be responsible for the following activities: Overall management and co-ordination of Market Trial activities; Developing the Market Trial Plan, Detailed Test Work-Plan and Test Exit Report; Defining the Market Trial cycles, scenarios and scripts; Developing test scenarios and scripts; Preparing test data; Undertaking the execution of Market Trial; Resolving where appropriate, defects or problems identified during Market Trial in a timely manner; Participating in meetings to discuss test defects; and Reporting progress to the SEMO IT Manager. 5.3 SEMO IT During and prior to Market Trial, SEMO IT will be responsible for the following activities: Providing dedicated support to the Market Trial workstream throughout testing; Preparing test data and test environments; Maintaining test environments; Resolving where appropriate, defects or issues (e.g., test documentation) identified during Market Trial in a timely manner; Maintaining configuration management of Central Market Systems; Scheduling and carrying out the release of software / hardware changes (Release Management); Providing the necessary IT infrastructure (PCs, internet access and printer) is made available in time for Market Trial; and Accepting Market Trial. Page 28 of 30

29 5.4 MARKET PARTICIPANTS During and prior to Market Trial, the Market Participants will be responsible for the following activities: Mobilising own systems development projects and teams; Providing dedicated support to the Market Trial workstream throughout testing; Designing and developing their own systems to interface with the Central Market Systems; Undertaking internal system testing; Confirming that own systems are ready to take part in Market Trial; Resolving where appropriate, defects or issues (e.g., test documentation) identified during Market Trial in a timely manner; Developing test scripts required for participation in Market Trial, based on the test scripts developed by the Market Trial workstream; Preparing test data required for participation in Market Trial; Undertaking the execution of test scenarios and scripts required for participation in Market Trial; Participating in daily meetings (or as and when required) to discuss test issues; and Resolving where appropriate, defects or issues identified during Market Trial within the agreed timescales. It should be noted that in the event that any of the external parties are unable to participate in Market Trial, this will not prevent Market Test from commencing. 5.5 RESPONSIBILITY MATRIX The following table provides details of the roles and responsibilities of the various parties involved in the Market Trial activities. These responsibilities include: Managing or co-coordinating the activity; Preparing or developing deliverable(s) produced as part of the activity; Reviewing the deliverable(s) produced as part of the activity; Approving or accepting the deliverable(s) produced as part of the activity; Performing the activity; and Being informed of the progress of the activity Page 29 of 30

30 Table 4 Market Trial Roles and Responsibilities Responsibility Manage / Coordinate Prepare / Develop Review Approve / Accept Perform Activity MT Test Approach SEMO SEMO SEMO / MPs SEMO - MT Detailed Work-Plan SEMO SEMO SEMO / MPs SEMO - MT Test Scripts SEMO / MPs SEMO / MPs SEMO / MPs SEMO - MT Data Preparation SEMO SEMO SEMO SEMO - MT Data Loading SEMO SEMO SEMO SEMO SEMO MT Environment Set-up SEMO SEMO SEMO SEMO SEMO MT Execution SEMO SEMO / MPs SEMO / MPs SEMO SEMO / MPs MT Defect Analysis SEMO SEMO SEMO SEMO SEMO MT Defect Fixing SEMO SEMO SEMO SEMO Software Vendors S/W & H/W Releases SEMO SEMO SEMO SEMO SEMO Back-Up and Archive MT Environment SEMO SEMO SEMO SEMO SEMO MT Exit Report SEMO SEMO SEMO SEMO - MT Acceptance SEMO SEMO SEMO SEMO - Page 30 of 30

PRICING & SCHEDULING FREQUENTLY ASKED QUESTIONS

PRICING & SCHEDULING FREQUENTLY ASKED QUESTIONS PRICING & SCHEDULING FREQUENTLY ASKED QUESTIONS CONTENTS What is Pricing & Scheduling?... 3 What is Merit Order?... 3 How does the market run each day?... 4 Introduction... 4 Before the Trading day...

More information

AVEVA Standard Support Service Policy for the AVEVA Product Suite

AVEVA Standard Support Service Policy for the AVEVA Product Suite AVEVA Standard Support Service Policy for the AVEVA Product Suite Issue 4 December 2012 Page 1 of 13 CONTENTS 1 Introduction... 3 1.1 Purpose... 3 1.2 Scope... 3 1.3 Terminology... 4 2 Service Scope...

More information

White Paper On Pilot Method Of ERP Implementation

White Paper On Pilot Method Of ERP Implementation White Paper On Pilot Method Of ERP Implementation Rod Clarke Rod Clarke provides guidance, advice and support to businesses in successfully applying IS/IT in support of their business goals. He brings

More information

Implementation and Customer Services ( ICS") Installation Services Standard Terms and Conditions of Supply. (Effective September 2013)

Implementation and Customer Services ( ICS) Installation Services Standard Terms and Conditions of Supply. (Effective September 2013) Implementation and Customer Services ( ICS") Installation Services Standard Terms and Conditions of Supply 1. General (Effective September 2013) This web page content defines the standard terms and conditions

More information

Oracle Insurance Policy Administration System Quality Assurance Testing Methodology. An Oracle White Paper August 2008

Oracle Insurance Policy Administration System Quality Assurance Testing Methodology. An Oracle White Paper August 2008 Oracle Insurance Policy Administration System Quality Assurance Testing Methodology An Oracle White Paper August 2008 Oracle Insurance Policy Administration System Quality Assurance Testing Methodology

More information

Balancing and Settlement Code BSC PROCEDURE BSCP537. QUALIFICATION PROCESS FOR SVA PARTIES, SVA PARTY AGENTS AND CVA MOAs

Balancing and Settlement Code BSC PROCEDURE BSCP537. QUALIFICATION PROCESS FOR SVA PARTIES, SVA PARTY AGENTS AND CVA MOAs Balancing and Settlement Code BSC PROCEDURE BSCP537 QUALIFICATION PROCESS FOR SVA PARTIES, SVA PARTY AGENTS AND CVA MOAs APPENDIX 3 GUIDANCE NOTES ON COMPLETING THE SAD Version 2.0 Date: 10 September 2007

More information

Applaud Solutions Technical Support Policies

Applaud Solutions Technical Support Policies Applaud Solutions Technical Support Policies Effective Date: 06-May-2011 Overview Unless otherwise stated, these Technical Support Policies apply to technical support for all Applaud Solutions products.

More information

Device Management Module (North America)

Device Management Module (North America) Device Management Module (North America) Part Number: MSFSEU-10 Motorola's device management module is designed to be utilized alongside an existing Motorola Service Center Support Bronze, Service Center

More information

X2 CONNECT NETWORKS SUPPORT SERVICES PRODUCT DEFINITION LEVEL 1, 2 & 3

X2 CONNECT NETWORKS SUPPORT SERVICES PRODUCT DEFINITION LEVEL 1, 2 & 3 X2 CONNECT NETWORKS SUPPORT SERVICES PRODUCT DEFINITION LEVEL 1, 2 & 3 Date : 09/08/06 Issue: 6 This is an unpublished work the copyright in which vests in X2 Connect Limited. All rights reserved. The

More information

BUSINESS CLASS SERVICE FOR LARGE BUSINESS CUSTOMERS SOLUTION DESCRIPTION

BUSINESS CLASS SERVICE FOR LARGE BUSINESS CUSTOMERS SOLUTION DESCRIPTION BUSINESS CLASS SERVICE FOR LARGE BUSINESS CUSTOMERS SOLUTION DESCRIPTION Table of Contents 1. INTRODUCTION 3 2. PROVISIONING 3 3. DEVICE AND ACCESSORY ORDERING 4 4. ACCOUNT DEVELOPMENT 5 5. CUSTOMER AND

More information

The management of testing and test deliverables is detailed in the Test Management procedure (Reference 1).

The management of testing and test deliverables is detailed in the Test Management procedure (Reference 1). Guidance Testing Guidelines Purpose This document provides guidelines for testing changes to the BSC Software, Systems and Processes. It also provides a high level view of test procedures that are followed

More information

SCHEDULE 3. Milestones and Deliverables. Redacted Version

SCHEDULE 3. Milestones and Deliverables. Redacted Version SCHEDULE 3 Milestones and Deliverables Redacted Version This Schedule 3 sets out the Service Provider s obligations in respect of the milestones and deliverables relating to the implementation and operation

More information

OPERATING PROCEDURE IT CHANGE MANAGEMENT PROCEDURES MANUAL. PREPARED BY: AEMO DOCUMENT NO: Enter Document ID VERSION NO: 6.

OPERATING PROCEDURE IT CHANGE MANAGEMENT PROCEDURES MANUAL. PREPARED BY: AEMO DOCUMENT NO: Enter Document ID VERSION NO: 6. OPERATING PROCEDURE IT CHANGE MANAGEMENT PROCEDURES MANUAL PREPARED BY: AEMO DOCUMENT NO: Enter Document ID VERSION NO: 6.6 STATUS FINAL Approvals The undersigned have approved the release of Version 6.6

More information

Lot 1 Service Specification MANAGED SECURITY SERVICES

Lot 1 Service Specification MANAGED SECURITY SERVICES Lot 1 Service Specification MANAGED SECURITY SERVICES Fujitsu Services Limited, 2013 OVERVIEW OF FUJITSU MANAGED SECURITY SERVICES Fujitsu delivers a comprehensive range of information security services

More information

S1200 Technical Support Service Overview

S1200 Technical Support Service Overview S1200 Technical Support Service Overview Nic Chalk March 2015 V1.13 The information contained herein is believed to be accurate at the time of publication, but updates may be posted periodically and without

More information

GMS NETWORK ADVANCED WIRELESS SERVICE PRODUCT SPECIFICATION

GMS NETWORK ADVANCED WIRELESS SERVICE PRODUCT SPECIFICATION GMS NETWORK ADVANCED WIRELESS SERVICE PRODUCT SPECIFICATION 1. INTRODUCTION This document contains product information for the GMS Network Service. If you require more detailed technical information, please

More information

STL Microsoft Dynamics CRM Consulting and Support Services

STL Microsoft Dynamics CRM Consulting and Support Services STL Microsoft Dynamics CRM Consulting and Support Services STL Technologies Equis House Eastern Way Bury St Edmunds Suffolk IP32 7AB Service Description and Pricing Specialist Cloud Services www.stl.co.uk

More information

Technical Support. Technical Support. Customer Manual v1.1

Technical Support. Technical Support. Customer Manual v1.1 Technical Support Customer Manual v1.1 1 How to Contact Transacta Support 1.1 Primary Contact: support@transacta.com.au 1.2 Escalation Telephone Number: +61 (2) 9459 3366 1.3 Hours of Operation 9:00 a.m.

More information

Problem Management Why and how? Author : George Ritchie, Serio Ltd email: george dot- ritchie at- seriosoft.com

Problem Management Why and how? Author : George Ritchie, Serio Ltd email: george dot- ritchie at- seriosoft.com Problem Management Why and how? Author : George Ritchie, Serio Ltd email: george dot- ritchie at- seriosoft.com Page 1 Copyright, trademarks and disclaimers Serio Limited provides you access to this document

More information

Customer Support Policy

Customer Support Policy Customer Support Policy This Customer Support Policy ( Policy ) describes the Support that Invenias provides to Customers that have paid all applicable fees and that are using Licensed Software in a Supported

More information

How To Use Adobe Software For A Business

How To Use Adobe Software For A Business EXHIBIT FOR MANAGED SERVICES (2013V3) This Exhibit for Managed Services, in addition to the General Terms, the OnDemand Exhibit, and any applicable PDM, applies to any Managed Services offering licensed

More information

Adlib Hosting - Service Level Agreement

Adlib Hosting - Service Level Agreement Adlib Hosting - Service Level Agreement June 2014 This service level agreement (SLA) applies to the Adlib Hosting services provided by Axiell ALM Netherlands BV, and includes the activities and facilities

More information

VARONIS SUPPORT PRINCIPLES

VARONIS SUPPORT PRINCIPLES VARONIS SUPPORT PRINCIPLES 1. SUPPORT SERVICES 1.1 Support Services. Throughout the Support Services term (the period for which applicable Support Services fees are paid), Varonis will make available to

More information

Terms and Conditions Website Development

Terms and Conditions Website Development Terms and Conditions Website Development 1. DEFINITIONS The following terms and conditions document is a legal agreement between Embertech Ltd hereafter the Company and Client for the purposes of web site

More information

GIGAMON STANDARD SOFTWARE SUPPORT AND MAINTENANCE AGREEMENT

GIGAMON STANDARD SOFTWARE SUPPORT AND MAINTENANCE AGREEMENT GIGAMON STANDARD SOFTWARE SUPPORT AND MAINTENANCE AGREEMENT This Standard Software Support and Maintenance Agreement ( Agreement ) is between Gigamon Inc. (GIGAMON) and ( Customer ) for the support and

More information

Rekoop Limited Standard Terms of Business

Rekoop Limited Standard Terms of Business Rekoop Limited Standard Terms of Business 1 Copyright 2012, rekoop Limited 1. DEFINITIONS... 3 2. BASIS OF AGREEMENT... 6 3. PROVISION OF THE SOFTWARE AND SERVICES... 6 4. TERM... 6 5. ACCESS AND SECURITY...

More information

We released this document in response to a Freedom of Information request. Over time it may become out of date. Department for Work and Pensions

We released this document in response to a Freedom of Information request. Over time it may become out of date. Department for Work and Pensions We released this document in response to a Freedom of Information request. Over time it may become out of date. Department for Work and Pensions SCHEDULE 2 SERVICES 1 Purpose of this Schedule 1.1 This

More information

Annual Hosting Service Level Agreement

Annual Hosting Service Level Agreement Annual Hosting Service Level Agreement This Agreement (the Agreement ) for AtoM (the Software ) hosting service (the Service ) is entered into between Artefactual Systems Inc. ( Artefactual ) located in

More information

means the charges applied by Ancar B Technologies Limited which recur annually;

means the charges applied by Ancar B Technologies Limited which recur annually; This Service Schedule is supplemental to the Master Service Agreement Net-L1-3. CONTENTS Schedule 1 - DEFINITIONS... 1 Schedule 2 - MANAGED INTERNET ACCESS SERVICE PRODUCT INFORMATION... 3 1 MANAGED INTERNET

More information

Incident Management Policy

Incident Management Policy Incident Management Policy Draft SEC Subsidiary Document DCC Public 01 July 2015 BASELINED VERSION 1 DEFINITIONS Term Black Start CPNI Code of Connection Crisis Management Disaster HMG Incident Party Interested

More information

SYSTEM SOFTWARE AND OR HARDWARE SUPPORT SERVICES (PREMIUM 24x7)

SYSTEM SOFTWARE AND OR HARDWARE SUPPORT SERVICES (PREMIUM 24x7) SYSTEM SOFTWARE AND OR HARDWARE SUPPORT SERVICES (PREMIUM 24x7) These System Software and or Hardware System Support Services terms and conditions ( Terms and Conditions ) apply to any quote, order, order

More information

ASIAN PACIFIC TELECOMMUNICATIONS PTY LTD STANDARD FORM OF AGREEMENT. Schedule 3 Support Services

ASIAN PACIFIC TELECOMMUNICATIONS PTY LTD STANDARD FORM OF AGREEMENT. Schedule 3 Support Services ASIAN PACIFIC TELECOMMUNICATIONS PTY LTD STANDARD FORM OF AGREEMENT Schedule 3 Support Services December 2013 Table of Contents 1. SERVICE SCHEDULE 3 SUPPORT SERVICES... 3 1.1 OVERVIEW... 3 1.2 STANDARD

More information

<Project Name> ACCEPTANCE TEST PLAN <SCOPE OF TEST E.G. SYSTEM TESTING> <BUSINESS UNIT/DIVISION> DEPARTMENT of INFRASTRUCTURE, ENERGY and RESOURCES

<Project Name> ACCEPTANCE TEST PLAN <SCOPE OF TEST E.G. SYSTEM TESTING> <BUSINESS UNIT/DIVISION> DEPARTMENT of INFRASTRUCTURE, ENERGY and RESOURCES DEPARTMENT of INFRASTRUCTURE, ENERGY and RESOURCES ACCEPTANCE TEST PLAN Version - DOCUMENT ACCEPTANCE and RELEASE

More information

GMS NETWORK BASIC PRODUCT SPECIFICATION 1. INTRODUCTION 2. SERVICE DEFINITION. 2.1 Service Overview. GMS Network Basic

GMS NETWORK BASIC PRODUCT SPECIFICATION 1. INTRODUCTION 2. SERVICE DEFINITION. 2.1 Service Overview. GMS Network Basic GMS NETWORK BASIC PRODUCT SPECIFICATION 1. INTRODUCTION This document contains product information for the GMS Network Basic Service. If you require more detailed technical information, please contact

More information

Request for Proposal for implementation of SAP HANA ERP System at MCL, ZAMBIA

Request for Proposal for implementation of SAP HANA ERP System at MCL, ZAMBIA Request for Proposal for implementation of SAP HANA ERP System at MCL, ZAMBIA RFP No. MCL/ZM/IT/001 Date of Issue: 10 th September, 2015 Last date of submission: 17 th October, 2015 Place of Submission:

More information

Communicate: Data Service Level Agreement. Author: Service Date: October 13. Communicate: Data Service Level Agreementv1.

Communicate: Data Service Level Agreement. Author: Service Date: October 13. Communicate: Data Service Level Agreementv1. Communicate: Data Service Level Agreement Author: Service Date: October 13 Communicate: Data Service Level Agreementv1.1 Page 1 of 12 Contents 1. Scope 3 2. Service Definitions 3 3. Service Provision 3

More information

STL Microsoft SharePoint Consulting and Support Services

STL Microsoft SharePoint Consulting and Support Services STL Microsoft SharePoint Consulting and Support Services STL Technologies Equis House Eastern Way Bury St Edmunds Suffolk IP32 7AB Service Description and Pricing Specialist Cloud Services www.stl.co.uk

More information

Service Schedule for BT Website Search Marketing Services

Service Schedule for BT Website Search Marketing Services 1. SERVICE DESCRIPTION Service Overview 1.1 The Service includes the creation and maintenance of a search engine marketing campaign and the construction and hosting of a landing page website as further

More information

Overview Software Assurance is an annual subscription that includes: Technical Support, Maintenance and Software Upgrades.

Overview Software Assurance is an annual subscription that includes: Technical Support, Maintenance and Software Upgrades. Software Maintenance & Support Agreement This agreement ( Support Agreement, Software Assurance, Agreement ) is for the purpose of defining the terms and conditions under which Technical Support, Maintenance

More information

Columbia College Process for Change Management Page 1 of 7

Columbia College Process for Change Management Page 1 of 7 Page 1 of 7 Executive Summary Columbia College's Process for Change Management is designed to provide an orderly and documented method in which changes to the College's computing environment are requested

More information

Incident Management Policy

Incident Management Policy Incident Management Policy Author: DCC Date: 9th May 2014 Page 1 of 10 Contents 1 Incident Management Policy 3 1.1 Incident Management Policy General Provisions 3 1.2 Pre-requisites to log an Incident

More information

System Build 2 Test Plan

System Build 2 Test Plan System Build 2 Test Plan Version 1.0 System Build 2 Test Plan Author s Signature Your signature indicates that this document has been prepared with input from content experts and is in compliance with

More information

National Programme for IT

National Programme for IT National Programme for IT Safer Design Key Clinical Safety Activities Safer Design Clinical Risk Guidance Document Clinical Safety Contents FOREWORD 3 1.0 INTRODUCTION 4 2.0 Overview 5 3.0 DESIGN ACTIVITIES

More information

Service Schedule for BT Website Standard Plus Service

Service Schedule for BT Website Standard Plus Service 1. SERVICE DESCRIPTION Service Overview 1.1 The Service includes the construction and hosting of a business website as further described in this Service Schedule. It does not include the provision of any

More information

A Guide to Categories & SLA Management

A Guide to Categories & SLA Management A Guide to Categories & SLA Management 1. Introduction Calls can be logged quickly and efficiently in SupportDesk using selection Categories within the call screen and these categories can match the conditions

More information

HP Autonomy Software Support Foundation

HP Autonomy Software Support Foundation Data sheet HP Autonomy Software Support Foundation HP Autonomy Software Support provides comprehensive technical support and updates for HP Autonomy Software. Your IT staff can have fast, reliable access

More information

By using the Cloud Service, Customer agrees to be bound by this Agreement. If you do not agree to this Agreement, do not use the Cloud Service.

By using the Cloud Service, Customer agrees to be bound by this Agreement. If you do not agree to this Agreement, do not use the Cloud Service. 1/9 CLOUD SERVICE AGREEMENT (hereinafter Agreement ) 1. THIS AGREEMENT This Cloud Service Agreement ("Agreement") is a binding legal document between Deveo and you, which explains your rights and obligations

More information

Terms and Conditions 1. AGREEMENT / EARLY TERMINATION RIGHT 2. DEFINITIONS

Terms and Conditions 1. AGREEMENT / EARLY TERMINATION RIGHT 2. DEFINITIONS Terms and Conditions 1. AGREEMENT / EARLY TERMINATION RIGHT (a) These terms and conditions, together with the Order Form, contain the entire understanding and agreement between you and us relating to the

More information

To provide a procedure and associated guidelines to facilitate the management of project dependencies.

To provide a procedure and associated guidelines to facilitate the management of project dependencies. Management DEPENDENCY MANAGEMENT Purpose To provide a procedure and associated guidelines to facilitate the management of project dependencies. Overview Dependencies in this Phase are defined as actions,

More information

Rollstone Bank & Trust Business Online Bill Pay Agreement

Rollstone Bank & Trust Business Online Bill Pay Agreement Rollstone Bank & Trust Business Online Bill Pay Agreement By choosing to use the Rollstone Bank & Trust Online Bill Pay, you agree to the terms and conditions in this Agreement. Please read this Agreement

More information

SAMPLE RETURN POLICY

SAMPLE RETURN POLICY DISCLAIMER The sample documents below are provided for general information purposes only. Your use of any of these sample documents is at your own risk, and you should not use any of these sample documents

More information

Support and Service Management Service Description

Support and Service Management Service Description Support and Service Management Service Description Business Productivity Online Suite - Standard Microsoft Exchange Online Standard Microsoft SharePoint Online Standard Microsoft Office Communications

More information

Electronic business conditions of use

Electronic business conditions of use Electronic business conditions of use This document provides Water Corporation s Electronic Business Conditions of Use. These are to be applied to all applications, which are developed for external users

More information

FlexTrac Client Support & Software Maintenance Policies

FlexTrac Client Support & Software Maintenance Policies Supporting the IP Community Powered by TORViC Technologies, Inc. SINCE 1996 [t]: +1.855.997.9933 [f]: +1.302.721.6266 [w]: www.flextrac.com [e]: Info@FlexTrac.com the largest provider of tailored Intellectual

More information

Accelerite Software Support Foundation

Accelerite Software Support Foundation Accelerite Support Foundation Data Sheet September 14 th 2015 Overview Accelerite Support provides comprehensive technical and updates for the Accelerite portfolio, offering fast, reliable access to well-trained

More information

3.0 ACCEPTANCE OF WORK

3.0 ACCEPTANCE OF WORK Terms and Conditions All orders placed with The Web Bureau Ltd. are accepted subject to the following conditions, which shall form the basis of the contract between The Web Bureau Ltd and the customer.

More information

HP Service Manager. Software Version: 9.40 For the supported Windows and Linux operating systems. Processes and Best Practices Guide (Codeless Mode)

HP Service Manager. Software Version: 9.40 For the supported Windows and Linux operating systems. Processes and Best Practices Guide (Codeless Mode) HP Service Manager Software Version: 9.40 For the supported Windows and Linux operating systems Processes and Best Practices Guide (Codeless Mode) Document Release Date: December, 2014 Software Release

More information

PPSADOPTED: OCT. 2012 BACKGROUND POLICY STATEMENT PHYSICAL FACILITIES. PROFESSIONAL PRACTICE STATEMENT Developing a Business Continuity Plan

PPSADOPTED: OCT. 2012 BACKGROUND POLICY STATEMENT PHYSICAL FACILITIES. PROFESSIONAL PRACTICE STATEMENT Developing a Business Continuity Plan PROFESSIONAL PRACTICE STATEMENT Developing a Business Continuity Plan OCT. 2012 PPSADOPTED: What is a professional practice statement? Professional Practice developed by the Association Forum of Chicagoland

More information

HP Change Configuration and Release Management (CCRM) Solution

HP Change Configuration and Release Management (CCRM) Solution HP Change Configuration and Release Management (CCRM) Solution HP Service Manager, HP Release Control, and HP Universal CMDB For the Windows Operating System Software Version: 9.30 Concept Guide Document

More information

Request for Proposal Business & Financial Services Department

Request for Proposal Business & Financial Services Department Request for Proposal Business & Financial Services Department CONTRACT 5118 P Enterprise Project Management Solution Design and Implementation 1. Introduction 1.1 The City of Richmond (the City ) proposes

More information

HP Service Manager. Software Version: 9.34 For the supported Windows and UNIX operating systems. Service Desk help topics for printing

HP Service Manager. Software Version: 9.34 For the supported Windows and UNIX operating systems. Service Desk help topics for printing HP Service Manager Software Version: 9.34 For the supported Windows and UNIX operating systems Service Desk help topics for printing Document Release Date: July 2014 Software Release Date: July 2014 Legal

More information

Statement of Work. LabTech Implementation Bronze. LabTech Software 4110 George Road Suite 200 Tampa, FL 33634

Statement of Work. LabTech Implementation Bronze. LabTech Software 4110 George Road Suite 200 Tampa, FL 33634 Statement of Work LabTech Implementation Bronze LabTech Software 4110 George Road Suite 200 Tampa, FL 33634 US Direct: 813.397.4600 UK: 0844.544.1690 AUS: 3.8652.1797 www.labtechsoftware.com Contents Section

More information

SIS Help Desk Process Version 1.3

SIS Help Desk Process Version 1.3 14 February 2013 Version Control Version Date Author Comments 1.0 23-Sept-2011 Alex Smith Version 1.0 1.1 29-Sept-2011 Alex Smith Clarification of the different Case Status 1.2 26-April-2012 Alex Smith

More information

ADDITIONAL TERMS FOR VIRTUAL VOICE NETWORK SERVICES SCHEDULE 2L

ADDITIONAL TERMS FOR VIRTUAL VOICE NETWORK SERVICES SCHEDULE 2L ADDITIONAL TERMS FOR VIRTUAL VOICE NETWORK SERVICES SCHEDULE 2L CONTENTS 1 Service Description... 3 2 Definitions... 3 3 Virtual Voice Network terms... 4 4 CHARGES... 4 4.1 Charges payable by the... 4

More information

Problem Management Fermilab Process and Procedure

Problem Management Fermilab Process and Procedure Management Fermilab Process and Procedure Prepared for: Fermi National Laboratory June 12, 2009 Page 1 of 42 GENERAL Description Purpose Applicable to Supersedes This document establishes a Management

More information

CAT-MIS Project Management

CAT-MIS Project Management CAT-MIS Project Management Communicat Accounting Transition to Management Information System Project Management Communicat utilises our proven CAT-MIS Project Management method for the implementation of

More information

Dynamics CRM - Support Service Description

Dynamics CRM - Support Service Description Service Description Contents CRM SUPPORT PLANS... 3 SUPPORT DEFINITIONS... 4 Incident Management... 4 Request Fulfilment... 4 Event Management... 4 Service Availability... 4 Response Time... 5 Resolution

More information

Template K Implementation Requirements Instructions for RFP Response RFP #

Template K Implementation Requirements Instructions for RFP Response RFP # Template K Implementation Requirements Instructions for RFP Response Table of Contents 1.0 Project Management Approach... 3 1.1 Program and Project Management... 3 1.2 Change Management Plan... 3 1.3 Relationship

More information

SOFTWARE DEVELOPMENT AGREEMENT

SOFTWARE DEVELOPMENT AGREEMENT SOFTWARE DEVELOPMENT AGREEMENT THIS AGREEMENT dated the day of 20. BETWEEN: AND: ACN of (the Customer ; 1iT Pty Ltd ACN 092 074 247 of 41 Oxford Close West Leederville (the Contractor. BACKGROUND A. The

More information

CAMMS ONLINE SUPPORT PORTAL USER MANUAL

CAMMS ONLINE SUPPORT PORTAL USER MANUAL CAMMS ONLINE SUPPORT PORTAL USER MANUAL September 2014 PREPARED BY CAM Management Solutions Level 17, 45 Grenfell St, Adelaide SA 5000 Telephone: 08 8212 5787 Facsimile: 08-8212-5288 www.cammanagementsolutions.com

More information

Appendix C Department of Information Resources Deliverables-Based Information Technology Services (DBITS) Contract Sample Statement of Work

Appendix C Department of Information Resources Deliverables-Based Information Technology Services (DBITS) Contract Sample Statement of Work Appendix C Department of Information Resources Deliverables-Based Information Technology Services (DBITS) Contract Sample Statement of Work Appendix C STATEMENT OF WORK (SOW) FOR DELIVERABLES-BASED INFORMATION

More information

Maturity Model. March 2006. Version 1.0. P2MM Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce

Maturity Model. March 2006. Version 1.0. P2MM Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce Maturity Model March 2006 Version 1.0 P2MM Version 1.0 The OGC logo is a Registered Trade Mark of the Office of Government Commerce This is a Value Added product which is outside the scope of the HMSO

More information

AGILENT SPECIFICATIONS INFORMATICS SOFTWARE SUPPORT AND SERVICES GOLD-LEVEL

AGILENT SPECIFICATIONS INFORMATICS SOFTWARE SUPPORT AND SERVICES GOLD-LEVEL AGILENT SPECIFICATIONS INFORMATICS SOFTWARE SUPPORT AND SERVICES GOLD-LEVEL The following terms set forth the specifications under which Agilent will provide support and services to customers who are under

More information

Test Plan (a Real Sample) SoftwareTestingHelp.com Live Project Training - OrangeHRM

Test Plan (a Real Sample) SoftwareTestingHelp.com Live Project Training - OrangeHRM www.softwaretestinghelp.com Test Plan (a Real Sample) SoftwareTestingHelp.com Live Project Training - OrangeHRM 2/1/2014 SoftwareTestingHelp.com Name of the tester Note: This is a sample test plan created

More information

Virtual Instruments Corporation. Maintenance and Support Services Supplement. Last updated on November 26, 2013.

Virtual Instruments Corporation. Maintenance and Support Services Supplement. Last updated on November 26, 2013. Virtual Instruments Corporation Maintenance and Support Services Supplement Last updated on November 26, 2013. This Maintenance and Support Services Supplement ( Supplement ) states Virtual Instruments

More information

CRM Support Services Agreement

CRM Support Services Agreement CRM Support Services Agreement Agreement Number: Start Date: Renewal Date: Minimum Term: Points Purchased in Initial Minimum Term: This Agreement sets forth the terms and conditions under which The CRM

More information

HP Service Manager. Service Desk help topics for printing. For the supported Windows and UNIX operating systems. Software Version: 9.

HP Service Manager. Service Desk help topics for printing. For the supported Windows and UNIX operating systems. Software Version: 9. HP Service Manager For the supported Windows and UNIX operating systems Software Version: 9.32 Service Desk help topics for printing Document Release Date: August 2013 Software Release Date: August 2013

More information

ICT SUPPORT SERVICES

ICT SUPPORT SERVICES ICT SUPPORT SERVICES SERVICE LEVEL AGREEMENT 2008 2009 Period of agreement: This document will run from 1st April 2008 to 31 st March 2009 and remains valid until superseded by a revised document. The

More information

Service Integration &

Service Integration & This is a DRAFT document, being published for review & comment The content is therefore subject to change & revision This document is part of the XGOV Strategic SIAM reference set Service Integration &

More information

SCOPE OF SERVICE Hosted Cloud Storage Service: Scope of Service

SCOPE OF SERVICE Hosted Cloud Storage Service: Scope of Service Hosted Cloud Storage Service: Scope of Service 1. Definitions 1.1 For the purposes of this Schedule: Access Account is an End User account with Data Storage requiring authentication via a username and

More information

Software Distribution Reference

Software Distribution Reference www.novell.com/documentation Software Distribution Reference ZENworks 11 Support Pack 3 July 2014 Legal Notices Novell, Inc., makes no representations or warranties with respect to the contents or use

More information

Audit Management. service definition document

Audit Management. service definition document Audit Management service definition document Contents Introduction... 3 Service Description... 3 Features and Benefits... 4 Architecture... 5 Service Delivery... 6 Service Provisioning Time... 7 Service

More information

Module 3 Licensed Software TABLE OF CONTENTS. Version 3.0

Module 3 Licensed Software TABLE OF CONTENTS. Version 3.0 1 Module 3 Licensed Software Version 3.0 TABLE OF CONTENTS 1. AGREED TERMS AND INTERPRETATION... 2 2. LICENCE TERMS... 3 3. SUPPLY OF... 8 4. UPDATES AND NEW RELEASES... 9 5. OPEN SOURCE SOFTWARE... 10

More information

StarterPak: HubSpot and Dynamics CRM Lead and Contact Synchronization

StarterPak: HubSpot and Dynamics CRM Lead and Contact Synchronization StarterPak: HubSpot and Dynamics CRM Lead and Contact Synchronization Version 1.1 2/10/2015 Important Notice No part of this publication may be reproduced, stored in a retrieval system, or transmitted

More information

Commercial Online Banking

Commercial Online Banking These terms form the agreement between us, Metro Bank PLC and you, a business customer and apply to the Commercial Online Banking Service (Commercial Online Banking) provided by us. Commercial Online Banking

More information

ITIL Roles Descriptions

ITIL Roles Descriptions ITIL Roles s Role Process Liaison Incident Analyst Operations Assurance Analyst Infrastructure Solution Architect Problem Manager Problem Owner Change Manager Change Owner CAB Member Release Analyst Test

More information

3.6. Please also note, unless your policy confirms otherwise, the rights under your policy may only be pursued in an English court.

3.6. Please also note, unless your policy confirms otherwise, the rights under your policy may only be pursued in an English court. Terms of business agreement - commercial customers M & N Insurance Service Limited Authorised and regulated by the Financial Conduct Authority No: 305837. Registered Office: 248 Hendon Way London NW4 3NL

More information

NYSED DATA DASHBOARD SOLUTIONS RFP ATTACHMENT 6.4 MAINTENANCE AND SUPPORT SERVICES

NYSED DATA DASHBOARD SOLUTIONS RFP ATTACHMENT 6.4 MAINTENANCE AND SUPPORT SERVICES NYSED DATA DASHBOARD SOLUTIONS RFP ATTACHMENT 6.4 MAINTENANCE AND SUPPORT SERVICES 1. Definitions. The definitions below shall apply to this Schedule. All capitalized terms not otherwise defined herein

More information

Draft Copy. Change Management. Release Date: March 18, 2012. Prepared by: Thomas Bronack

Draft Copy. Change Management. Release Date: March 18, 2012. Prepared by: Thomas Bronack Draft Copy Change Management Release Date: March 18, 2012 Prepared by: Thomas Bronack Section Table of Contents 10. CHANGE MANAGEMENT... 5 10.1. INTRODUCTION TO CHANGE MANAGEMENT... 5 10.1.1. PURPOSE OF

More information

SNAP SURVEYS LTD SNAP PLUS SERVICE LEVEL AGREEMENT

SNAP SURVEYS LTD SNAP PLUS SERVICE LEVEL AGREEMENT SNAP SURVEYS LTD SNAP PLUS SERVICE LEVEL AGREEMENT THE LICENSOR: Snap Surveys Ltd, a company registered in England under number 1672722 whose registered office is at 5 Mead Court, Cooper Road, Thornbury,

More information

SAMPLE. Appendix C. Department of Information Resources. Managed Services for Telecommunications Contract. Sample Statement of Work

SAMPLE. Appendix C. Department of Information Resources. Managed Services for Telecommunications Contract. Sample Statement of Work SAMPLE Appendix C Department of Information Resources Managed Services for Telecommunications Contract Sample Statement of Work ATTACHMENT 1 STATEMENT OF WORK (SOW) FOR Managed Services for Telecommunication

More information

HP Service Manager. Software Version: 9.34 For the supported Windows and UNIX operating systems. Processes and Best Practices Guide

HP Service Manager. Software Version: 9.34 For the supported Windows and UNIX operating systems. Processes and Best Practices Guide HP Service Manager Software Version: 9.34 For the supported Windows and UNIX operating systems Processes and Best Practices Guide Document Release Date: July 2014 Software Release Date: July 2014 Legal

More information

Version 2.0. 7 October 2013 SEM-13-067

Version 2.0. 7 October 2013 SEM-13-067 TRADING & SETTLEMENT CODE HELICOPTER GUIDE TRADING & SETTLEMENT CODE HELICOPTER GUIDE Version 2.0 7 October 2013 SEM-13-067 TABLE OF CONTENTS 1. INTRODUCTION 1 1.1 Purpose 1 1.2 Disclaimer 1 1.3 The TSC

More information

Sure Managed Networks Essential Level Support Service Terms & Conditions

Sure Managed Networks Essential Level Support Service Terms & Conditions Essential Level Support Service Description Sure s Support Service combines traditional maintenance and technical support services to support your Customer Premises Equipment. It enables enhanced service

More information

Technical Standards for Information Security Measures for the Central Government Computer Systems

Technical Standards for Information Security Measures for the Central Government Computer Systems Technical Standards for Information Security Measures for the Central Government Computer Systems April 21, 2011 Established by the Information Security Policy Council Table of Contents Chapter 2.1 General...

More information

AriesoGEO Support Services Terms and Conditions (12x5)

AriesoGEO Support Services Terms and Conditions (12x5) AriesoGEO Support Services Terms and Conditions (12x5) These Standard Support Services terms and conditions ( Terms and Conditions ) apply to any quote, order, order acknowledgment, and invoice, and any

More information

Winshuttle, LLC Technical Support and Maintenance Program

Winshuttle, LLC Technical Support and Maintenance Program Winshuttle, LLC Technical Support and Maintenance Program Overview The Winshuttle Technical Support and Maintenance Program ( Support Program ) is the comprehensive technical support and maintenance service

More information

ThinkPlus Warranty Services Agreement

ThinkPlus Warranty Services Agreement ThinkPlus Warranty Services Agreement IMPORTANT NOTICE Please carefully read the following terms under which Lenovo will provide services to You. We will provide services only if You first accept the terms

More information

Buckeye Brainiacs Support Terms of Service

Buckeye Brainiacs Support Terms of Service Buckeye Brainiacs Support Terms of Service 1. ACKNOWLEDGEMENT AND ACCEPTANCE OF TERMS OF SERVICE The Brainiacs Terms of Service ( Service Terms ) are available to you ( Customer ) at our website www.buckeyecableystem.com

More information

Information Crib Sheet Internet Access Service Agreement

Information Crib Sheet Internet Access Service Agreement Information Crib Sheet Internet Access Service Agreement 1. Definitions and Interpretation This Service Agreement is to be read in conjunction with the Conditions for Communications Services (the Conditions

More information