MODIS Screens User Guide for ETR and ACER REMIT. Market Operation Data Interface System Market Participant Screens General Screens

Transcription

1 MODIS Screens User Guide for ETR and ACER REMIT Market Operation Data Interface System Market Participant Screens General Screens MODIS User Guide Screens V0 18 Page 1 of 33

2 Contents 1 Purpose MODIS screen navigation Scope of MODIS User Guide and Screens document General Screens for all Users Market Participants Screens ETR MODIS screens Welcome page Login page ETR Homepage Market Participants ETR MODIS reports screen Selecting an Article Navigation and Selecting method of entering data Option 1: Manually enter data for reports Screens for Market Participant Manual Entry A7.1a Planned Unavailability of Consumption Unit A7.1b Changes in Actual Availability of Consumption Unit A15.1a Changes in Actual Availability of Consumption Unit A15.1b Changes in Actual Availability of Generation Unit A15.1c Planned Unavailability Of Production Unit A15.1d Changes in Actual Unavailability of Production Unit ACER REMIT - Capacity Changes, Multiple Outage Profiling and Other Market Information Option 2: Upload XML data file (e.g. A7.1a) Automated Data Entry, Drop Down lists and Field types Error Messages Confirmation screen for data entry or file upload Viewing submitted reports Viewing Acknowledgements ETR MODIS Logout...31 Appendix A: Document Information...32 MODIS User Guide Screens V0 18 Page 2 of 33

3 1 Purpose The purpose of this document is to provide an overview of the MODIS user interface and screens for European Transparency Regulation (ETR) and Regulation on Wholesale Energy Markets Integrity and Transparency ACER REMIT. A detailed description of the main screens is provided along with functionality, validation and navigational notes. 2 MODIS screen navigation This graphic shows the overall navigation for MODIS screens. Figure 2: ETR MODIS Screen Navigation (Source: ETR - MODIS Systems Detailed Application Design v1.2.doc Figure 10, Page 31) See section 5.2 for Navigation and Selecting method of entering data MODIS User Guide Screens V0 18 Page 3 of 33

4 3 Scope of MODIS User Guide and Screens document This document describes the MODIS screens that Market Participant and National Grid users would access. These are the following screens: 3.1 General Screens for all Users Welcome Screen Login Page Home Page Submitted Reports Confirmation Screen Logout Screen Upload Method Manual upload screen 3.2 Market Participants Screens A7.1a A7.1b A15.1a A15.1b A15.1c A15.1d REMIT MODIS User Guide Screens V0 18 Page 4 of 33

5 4 ETR MODIS screens 4.1 Welcome page The Welcome page is the first screen for MODIS that users would access via the provided web address. Figure 4.1: ETR MODIS Welcome Page - The welcome page has a box for content provided by National Grid. This contains background information on ETR, MODIS and other relevant information. Details are provided by National Grid. MODIS User Guide Screens V0 18 Page 5 of 33

6 4.2 Login page - The user Login page Figure 4.2: Login page for MODIS. Pressing the login button on the top right of the Welcome page will take users to the login credentials screen as per Figure. 4.2 MODIS Login page - Users will enter their credentials in the username and password fields. - Once correct user details are entered, clicking the login button will take user to the MODIS homepage. If incorrect login details, an error message should appear saying Failed login attempt, try again with the correct username and password. MODIS User Guide Screens V0 18 Page 6 of 33

7 4.3 ETR Homepage The MODIS Home Page Figure 4.3. The MODIS Home Page After successfully logging in to MODIS, users will be able to access the MODIS Home Page as per Figure. 4. All users, i.e. Market Participants and Internal National Grid users will be presented with a similar screen. - Please note that the home screen news content information will be provided by the National Grid business. The content will be user specific, i.e. different for NG users and Market Participants. Content can only be updated by Application Support. - The menu choices will be dependent on the user group of the logged-in user - Logged in User name is provided on top left of the screen Left Menu Buttons: 1) Submit Report: This link will take users to the ETR report entry screen depending on the following: - If login credentials as per Fig 4.2 are that of a Market Participant, then clicking on this button will take you to ETR report screen for Market Participants. - If login credentials as per Fig 4.2 are that of an internal NG user, then clicking on this button will take you to ETR report screen for National Grid users. 2) View Reports This button will take users to the processed reports screen Top Right Menu: 1) Logout Link Pressing this link (top right) will take all users to the Logout confirmation screen. Please note that Market Participants are requested to use Menu buttons to navigate between MODIS pages. The use of the browser back button functionality is not supported by MODIS. MODIS User Guide Screens V0 18 Page 7 of 33

8 5 Market Participants ETR MODIS reports screen This screen is for the selection for all reports that require submission by Market Participants only. Please note that the following screen examples in this section will be for Article 7.1a and that the same logic will apply to all other articles as stated in Table 1 below. The following Articles, as captured in the sidebar of the screen (see below), relate to Market Participant Reports Table 1: Market Participant Articles Article Article Description Reference A7.1a Planned Unavailability of Consumption Unit A7.1b Actual Availability of Consumption Unit A15.1a Planned Unavailability Of Generation Unit A15.1b Actual Availability Of Generation Unit A15.1c Planned Unavailability Of Production Unit A15.1d Actual Unavailability Of Production Unit REMIT Information on Outages of Generation and Consumption Units 5.1 Selecting an Article Once a Market Participant user clicks on the Submit Report menu option as on Figure.4.3, the following screen should be presented. Figure 5.1: ETR MODIS Market Participants report selection screen - Market Participants can select the relevant article for which they wish to submit data from the sidebar. - Please note that the sidebar only displays the Article reference (as per Figure. 5.1). The full title of the Article is not displayed in the sidebar. - Once a Report is selected and opened, that report remains highlighted in the menu. - A Logout button is provided on top right of the screen. - The home button will return users to the MODIS homepage as per Figure MODIS User Guide Screens V0 18 Page 8 of 33

9 5.2 Navigation and Selecting method of entering data Once a Market Participant clicks on the relevant article they will be presented with the following screens (see Figure 5.2 ) Figures 5.2 Select the Method of providing the chosen report - A radio button is provided which allows users to select the method they wish to use to submit relevant MODIS report data. o Option 1 is Manually enter data for reports. Clicking on this radio button will take users to a manual report data entry screen. o Option 2 is Upload XML data file. Clicking on this radio button will take users to a file upload screen. Navigation - If users click on the wrong article they can click on the correct article in the sidebar. - A Logout button is provided on top right of the screen. - The home button will return users to the ETR homepage as per Figure Please note that it is only the Article reference title that changes. This means that all articles as per Table 1 have the option to enter data via Option 1 or Option 2 as discussed above. MODIS User Guide Screens V0 18 Page 9 of 33

10 5.3 Option 1: Manually enter data for reports Note: This example is for Article 7.1a and the same procedure will apply to all other Market Participant screens as stated in Table 1. An alternative submission method is to upload a file and this method is described in a later section. Figure. 5.3 Manual data entry for a report For Market Participant (MP) Manual Entry screens, there are four sections to each screen, 1) Document Header, 2) Time series class, 3) Series Period, and Point Class 4) Reason class. Please note than sections 2-4 are all grouped together within screen functionality. 1) Document header section - Fields assigned as Auto will be automatically populated. These fields have been grouped together for ease of functionality. - All fields must be fully populated before MP users can progress on to the Time Series Class section. - If all document header fields have not been populated, the Time Series section will not be active. 2) Time Series Class, Series Period Class & Point Class and Reason Class - Auto-populated fields have been grouped together - All users need to fill in all required fields within the time series, series period class & point class and Reason Class. - Fields within the bottom half of the screen, i.e. Time series, Series Period Class & Point Class and Reason Class are all filled within a tab structure. - Only once all the fields within the bottom half of the screen are filled can a user press the Add Time Series button. Doing this will allow a new tab to be created. - Please note that a report can have multiple tabs yet only one document header. - Users can press Submit at the bottom of the screen to submit a report or press Cancel if they wish to clear the data. Pressing the Cancel button returns the users to a screen as per Fig If a user presses the Submit button without providing valid data in all required fields an error screen will be returned identifying the fields in error - The first time series tab does not have a delete tab button but all tabs thereafter allow MP users to delete an existing tab if a mistake has been made or a user accidently pressed the add new time series button. - The active tab will be blue in colour and all other tabs will be in grey to show which is the active tab. MODIS User Guide Screens V0 18 Page 10 of 33

11 6 Screens for Market Participant Manual Entry This section provides screenshots for all Market Participant Manual Data Entry reports. 6.1 A7.1a Planned Unavailability of Consumption Unit Figure 6.1: Manual Data Entry Screen (A7.1a) 6.2 A7.1b Changes in Actual Availability of Consumption Unit Figure 6.2: Manual Data Entry Screen (A7.1b) MODIS User Guide Screens V0 18 Page 11 of 33

12 6.3 A15.1a Changes in Actual Availability of Consumption Unit Figure 6.3: Manual Data Entry Screen (A15.1a) 6.4 A15.1b Changes in Actual Availability of Generation Unit Figure 6.4: Manual Data Entry Screen (A15.1b) MODIS User Guide Screens V0 18 Page 12 of 33

13 6.5 A15.1c Planned Unavailability Of Production Unit Figure 6.5: Manual Data Entry Screen (A15.1c) 6.6 A15.1d Changes in Actual Unavailability of Production Unit Figure 6.6: Manual Data Entry Screen (A15.1d) MODIS User Guide Screens V0 18 Page 13 of 33

14 6.7 ACER REMIT - Capacity Changes, Multiple Outage Profiling and Other Market Information As part of P329 changes, Market Participants can submit REMIT information either for Unavailability of Electricity or Other Market Information as shown in Figure: Figure 6.7.1: Choose between REMIT Message Types 1. Unavailability of Electricity along with Outage Profile Information When a Market Participant selects Unavailability of Electricity option on a screen, the Market Participant will be redirected to a screen for submitting Unavailability of Electricity information along with outage profile segment as shown in Figure Figure 6.7.2: Screen to enter Unavailability of Electricity To add outage profile segment information to the Unavailability of Electricity message type, click on the Outage Profile Segment tab highlighted in red in the Figure The Market Participant can submit upto 200 outage profile segments for each message type. The number of rows for outage profile segment is defaulted to 1 on the screen; however, the Market Participant can enter number of outage profile segments to be added and click on Add Outage Segment button, as highlighted in blue in the Figure The Market Participant can also remove outage profile segments by selecting the rows to removed and clicking on the button Delete Selected Outage Segment as highlighted in yellow in the MODIS User Guide Screens V0 18 Page 14 of 33

15 Figure The number of rows to be displayed on the screen can be controlled by selecting value from a dropdown as highlighted in black in Figure and Market Participant can navigate between the pages using navigation button. Note: The submission of outage profile segment is optional. Figure: : Outage Profile Segment 2. Other Market Information When a Market Participant selects Other Market Information option on a screen, the Market Participant will be redirected to a screen for submitting Other Market Information information along with outage profile segment as shown in Figure Figure 6.7.3: Screen to enter Other Market Information To add outage profile segment information to the Other Market Information message type, click on the Outage Profile Segment tab highlighted in red in the Figure The Market Participant can submit upto 200 outage profile segments for each message type. The number of rows for outage profile segment is defaulted to 1 on the screen; however, the Market Participant can enter number of outage profile segments to be added and click on Add Outage Segment button, as highlighted in blue in the Figure The Market Participant can also remove outage profile segments by selecting the rows to be removed and clicking on the button Delete Selected Outage Segment as highlighted in yellow in the Figure The number of rows to be displayed on the screen can be controlled by selecting value from dropdown as highlighted in black in Figure and Market Participant can navigate between the pages using navigation button. Note: The submission of outage profile segment is optional. MODIS User Guide Screens V0 18 Page 15 of 33

16 Figure: : Outage Profile Segment 3. ACER REMIT Fields acceptable criteria Ref Title Mandatory Description 1 Version Yes 2 mrid Yes 3 revisionnumber Yes 4 DocumentType Yes The value must be defaulted to 2 The acceptable pattern would be <MP EIC Code>- NGET-RMT-<Sequence number> MP EIC code must be 16 characters long Sequence number must be 8 digits long. Can accept up to 999 revisions starting with 1 The value must be defaulted to REMIT_document 5 Sender_MarketParticipantID Yes A valid EIC code of sender 6 Sender_MarketParticipantRol e Yes Market Participant role can range between A01 and A39 7 Receiver_MarketParticipantI D Yes A valid EIC code of receiver 8 Receiver_MarketParticipantR ole Yes Market Participant role can range between A01 and A39 9 CreatedDateTime Yes 10 MessageHeading Yes Date and time of submitting REMIT report in GMT time zone and UTC format. A free text entry field with maximum 150 characters. MODIS User Guide Screens V0 18 Page 16 of 33

17 11 EventType Yes 12 UnavailabilityType Yes 13 Participant_MarketParticipant ID Yes Any single value from given options: 1. Production unavailability 2. Transmission unavailability 3. Consumption unavailability 4. Other unavailability Any single value from given options: 1. Planned 2. Unplanned Maximum of 8 characters GS1 a standard for use with global location numbers or barcodes for any product sold. (13 characters long) 14 Participant_ACERRegistratio ncode Yes LEI Legal Entity Identifier (20 characters long) Example: WSGIIZCXF1P572 BIC Business Identifier Code (11 characters long) Example: TBNFFR43PAR ACER Code 12 characters long Example: A DK EIC code 16 characters long 15 AssetId Yes 16 AssetType No 17 AffectedUnit Yes 18 AffectedUnitEIC No A free text entry field with maximum 18 characters. Any single value from given options: 1. Production 2. Consumption 3. Transmission 4. Distribution Maximum of 50 character string Valid EIC code of unit affected which is 16 characters long MODIS User Guide Screens V0 18 Page 17 of 33

18 19 AffectedArea No 20 BiddingZone Yes 21 FuelType No 22 NormalCapacity Yes 23 AvailableCapacity Yes Any value from given options: N, B1, B2, B3, B4, B5, B6, B7, B8, B9, B10, B11. B12, B13, B14, B15, B16, B17 For submission on BMRS, the Bidding zone will always be GB and where relevant, participants currently use 10YGB A for submission European Transparency Regulation Data (543/2013) Any single value from given options: 1. Biomass 2. Fossil Brown coal/lignite 3. Fossil Coal-derived gas 4. Fossil Gas 5. Fossil Hard coal 6. Fossil Oil 7. Fossil Oil shale 8. Fossil Peat 9. Geothermal 10. Hydro Pumped Storage 11. Hydro Run-of-river and poundage 12. Hydro Water Reservoir 13. Marine 14. Nuclear 15. Other renewable 16. Solar 17. Waste 18. Wind Offshore 19. Wind Onshore 20. Other A numeric value (representative of MW capacity) which also accepts decimals up to 3 decimal places. A numeric value (representative of MW capacity) which also accepts decimals up to 3 decimal places. MODIS User Guide Screens V0 18 Page 18 of 33

19 24 UnavailableCapacity Yes 25 EventStatus Yes 26 EventStart Yes 27 EventEnd Yes 28 OutageProfileSegment.Start No 29 OutageProfileSegment.End No A numeric value (representative of MW capacity) which also accepts decimals up to 3 decimal places. Any single value from given options: 1. Active 2. Dismissed 3. Inactive Date and time in GMT time zone and UTC format. Date and time in GMT time zone and UTC format. Date and time in GMT time zone and UTC format. Date and time in GMT time zone and UTC format. 30 OutageProfileSegment.Capa city No A numeric value (representative of MW capacity) which also accepts decimals up to 3 decimal places. 31 DurationUncertainty No 32 Cause Yes 33 RelatedInformation No A free text entry field with maximum 50 characters. A free text entry field with maximum 500 characters. A free text entry field with maximum 500 characters. 4. ACER REMIT Error Messages Field level validations Field Name Validation Type Messages Sender Market Participant Role Mandatory Message Heading Mandatory Length Validation Sender Market Participant Role is required. Message Heading is required Message Heading: Up to 150 characters are allowed. Event Type Mandatory Event Type is required. Market Participant ID Mandatory Market Participant ID is required. MODIS User Guide Screens V0 18 Page 19 of 33

20 Asset ID Length Validation Mandatory Pattern Market Participant ID: Up to 8 characters are allowed. Asset ID is required. Asset ID: Invalid format, please use alphanumeric letters A-Z, digits 0-9 or - (max 18 characters). Affected Unit Mandatory Affected Unit is required. Affected Unit EIC Normal Capacity Available Capacity Format Mandatory Regex Pattern Mandatory Regex Pattern Affected Unit EIC: Invalid format, please use alphanumeric letters A-Z, digits 0-9 or - (max 16 characters). Normal Capacity is required. Normal Capacity: Invalid format, please enter numeric value (max 3 decimal places). Available Capacity is required. Available Capacity: Invalid format, please enter numeric value (max 3 decimal places). Event Status Mandatory Event Status is required. Event Start Mandatory Event Start date and time are required. Event End Mandatory Event End date and time are required. Duration Uncertainty Cause Related Information Length Validation Mandatory Length Validation Length Validation Duration Uncertainty: Only up to 50 characters can be entered. Cause is required. Cause: Only up to 500 characters can be entered. Related Information: Only up to 500 characters can be entered. Unavailability Type Mandatory Unavailability Type is required. ACER Registration Code Unavailable Capacity Outage Segment Start Outage Segment End Mandatory Regex Pattern Mandatory Regex Pattern In case of Mandatory In case of Mandatory ACER Registration Code is required. ACER Registration Code: Invalid format, please enter valid value (EIC (recommended), BIC, LEI, GS1 or ACER Code). Unavailable Capacity is required (MW). Unavailable Capacity: Invalid format, please enter numeric value (max 3 decimal places). In Segment Count <x,x,x> : Outage Segment Start date and time are required. In Segment Count <x,x,x> : Outage Segment End date and time are required. MODIS User Guide Screens V0 18 Page 20 of 33

21 Available Capacity Event End Date and Time must not be less than or equal to Event Start Date and Time The outage profile segment start date and time for the given Event must be greater than or equal to Event Start date/time The outage profile segment end date and time for the given event must be less than or equal to Event End date/time. The outage profile segment start date and time for the given Event must not be greater than or equal to Event End date and time. The outage profile segment end date and time for the given Event must not be less than or equal to Event Start date and time Outage Segment Start and End Date validation All fields required for Outage Profile Tab Outage Segment Start and End Date validation Outage segment start date and time and available capacity Outage segment end date and time and available capacity In case of Mandatory Pattern Outage segment end date/time < Outage segment start date/time All Mandatory fields Mandatory fields Mandatory fields Outage Segment End and Available Capacity validation In Segment Count <x,x,x> : Available Capacity is required. In Segment Count <x,x,x>: Available Capacity: Please enter numeric value (max 3 decimal places). The event end date and time must be greater than event start date and time. In Segment Count <x,x,x>: The outage profile segment start date and time must be greater than or equal to event start date and time. In Segment Count <x,x,x>: The outage profile segment end date and time must be less than or equal to event end date and time. In Segment Count <x,x,x>: The outage profile segment start date and time must be less than event end date and time. In Segment Count <x,x,x>: The outage profile segment end date and time must be greater than event start date and time. In Segment Count <x,x,x>: The outage profile segment end date and time must be greater than outage profile segment start date and time. In Segment Count <x,x,x>: Outage Segment Start date and time, Outage Segment End date and time and Available Capacity are required. In Segment Count <x>: Outage Segment Start date and time and Outage Segment End date and time are required. In Segment Count <x> : Outage Segment Start date and time and Available Capacity are required. In Segment Count <x>: Outage Segment End date and time and Available Capacity are required. MODIS User Guide Screens V0 18 Page 21 of 33

22 Bidding Zone Pattern Bidding Zone: Invalid format, please enter a 16 character string meeting the following criteria - the first two characters have to be digits between 0 and 9, the next (third) character has to be a letter - either X,Y,Z,T,W or V, and the other 13 characters can be any characters (including hyphens). Server side validation During the submission of the ACER REMIT data the following additional validations will be applied with the following messages shown on the screen (where manual input is used) or within an acknowledgement file (where any other method of submission is used). Action On successful submission of REMIT Report On unsuccessful submission of REMIT Report When "Number of Outage Segments to be Added" is left blank or invalid value is entered. When total number of outage segments exceeds 200. When a delete button is clicked without selecting the Outage Profile Segments to delete. When user clicks on submit button. Messages Report successfully submitted. Operation failed. Please enter valid Number of Outage Segments to be added. Only 200 Outage Profile Segments can be added. Please select Outage Profile Segments which you want to delete. Do you wish to submit the data? File upload functionality messages Action When a correct REMIT report is uploaded On error while reading a file. When MODIS couldn t upload file due to some other error. When file which doesn t have.xml extension is uploaded Messages Upload successful File File Name was successfully uploaded and sent for processing Upload unsuccessful Unable to create local file copy of the report content. Upload unsuccessful Unexpected exception occurred. FileName' Invalid Type. MODIS User Guide Screens V0 18 Page 22 of 33

23 Negative Acknowledgements Following the submission of the ACER REMIT data via (File upload, sftp or Web Services) the following negative acknowledgements may be communicated to the Market Participants subject to appropriate validation. Scenario When a duplicate REMIT report is submitted When the submitted REMIT XML is not as per the XSD standard When a MP is not allowed to send report for the affected unit or BMU. When incorrect receivers MRID is sent or incorrect senders Role or incorrect receivers role is sent inside XML. Reason Code A02 A02 A02 A02 Message File is not unique: Entry for mrid and revision number already exists. XML is not valid, XSD validation failed BMU Validation failed. Participant not allowed to submit for this BMU. Incorrect Sender or Receiver mrid or Incorrect Sender or Receiver role. MODIS User Guide Screens V0 18 Page 23 of 33

24 7 Option 2: Upload XML data file (e.g. A7.1a) Market Participants may upload an XML file (Option 2) rather than manually entering data as per Option 1 (discussed above). This will be done by selecting the second radio button as per Figure.8.1 Figure. 8.1: Manual XML upload option - Clicking on the relevant article will bring the screen as per Figure.8.1. Note that where it says A7.1a Planned Unavailability of Consumption Unit in this example, this will be replaced by the actual title of the article as discussed above. - Users will click on the radio button, Upload XML data file to be directed to the upload screen as per Figure MP users should upload by searching for the relevant file via the browse button - Once file path is entered in the field, users can press Submit which would then lead to the confirmation screen. Please note that the upload process does not include the validation process. - Pressing Cancel would return users to the previous screen, i.e. Figure Note: As part of P329 release, the XML format to upload REMIT information has changed. Figure 8:2 Upload screen for XML files MODIS User Guide Screens V0 18 Page 24 of 33

25 Figure 8:3 Upload screen for XML files window to browse for selected file - As per Figure. 8.2 users can select to upload a file and Figure. 8.3, users can browse and submit the relevant file on to the system. - The screen s header will adapt depending on the article reference user has previously clicked. - A Cancel button is provided on the screen, in case user would like to return to previous screen - The Home button will allow users to return to the Market Participants homepage as per Figure Submitting a file will take users to the confirmation screen as per Figure Automated Data Entry, Drop Down lists and Field types Some fields are automatically completed depending on the logged in users organisation. (E.g. Sender Market Participant mrid), the selected article number (e.g. Document mrid) Some fields are completed by selecting from a drop down list of contextually specific choices, e.g. Reason Code Figure 9.1: Drop Down List Some Free Text fields can be completed with any un-validated text E.g. Reason Text MODIS User Guide Screens V0 18 Page 25 of 33

26 Figure 9.2: Free Text Date and Time fields have a selection drop down. Click on the required date and slide the pointers to the required Hours and Minutes Figure 9.3: Data and Time entry MODIS User Guide Screens V0 18 Page 26 of 33

27 9 Error Messages If a user presses the Submit button without providing valid data in all of the required fields an error screen will be returned identifying the fields in error. This is shown as a list at the top of the screen with 1] An explanation of the valid data that is required and 2] Highlighted fields where valid data is still required. An example of a screen submitted with errors and the related error messages is depicted below. Figure 10: ETR MODIS Error Messages Please note: Please send all REMIT messages using the latest P329 REMIT XSD. If Market Participants send files using the non-p329 XSD, MODIS will not validate them and no negative acknowledgements will be sent back. MODIS User Guide Screens V0 18 Page 27 of 33

28 10 Confirmation screen for data entry or file upload - When Market Participants submit either a manual report or an XML file, the system will present the following screen, see Figure.11 - Clicking YES, submits the report and returns users to the ETR homepage as per Figure.4 - Clicking NO, returns the users to the previous screen, i.e. either the Manual entry screens as per Section or per Section as discussed within this document. Figure 11: Confirmation Screen MODIS User Guide Screens V0 18 Page 28 of 33

29 11 Viewing submitted reports Details of any reports that have been submitted, either via manual data entry or manual file upload, can be viewed through the View Submitted Reports Page accessed from ETR MODIS homepage as per Figure Figure 12.1: ETR MODIS Homepage - Clicking on View Reports will take users to a separate screen, which will show all reports that have been submitted. - N.B only report status will be shown and actual report information will not be available as per Figure Figure 12.2: View Reports ETR MODIS screen There are filters provided to allow users to view a specifc set of submitted reports Filters are as follows: - Report name: Users can specify all or part of the name of the report - Article: Users can select the Article identity - Username/Company: Users can select the company name/user - Run Date and Time: Users can select the beginning and end of a range - File status: Users can select reports by file status, i.e. Received, Processed, Sent, Acknowledgement Received, Acknowledgement Processed, Acknowledgement Sent, Batch, etc - Once users have specified the filters, they then press Search to view relevant reports - Clicking on Reset, clears the filters - The logout button will lead users to the logout page - The home button will return users to the Homepage, Fig 4.3. MODIS User Guide Screens V0 18 Page 29 of 33

30 12 Viewing Acknowledgements Details of any Acknowledgements, either via manual data entry or manual file upload, can be viewed through the Acknowledgements Page accessed from ETR MODIS homepage as per Figure Figure 13.1 The Acknowledgement menu Once selected, the file can be viewed Figure 13.2 A view of an Acknowledgement MODIS User Guide Screens V0 18 Page 30 of 33

31 13 ETR MODIS Logout Figure 14: Logout confirmation screen - When users click the Logout button on any screen, they will be presented with a screen as per Figure Clicking cancel will return user to the previous screen - Clicking logout will return users to the ETR MODIS welcome page as per Figure. 4.1 MODIS User Guide Screens V0 18 Page 31 of 33

32 Appendix A: Document Information Author: Pete Talbot Distribution: See review form for recommendations. Name Position Reason for Distribution Richard Price NG Business Lead Fit for business Melanie Jackson NG Business Analyst Fit for requirements Kakul Jain Project Manager Review Richard Price NG Business Lead Fit for business Rituraj Saikia IS Business Analyst Fit for requirements Sanjeev IS Project Manager Approval Gopalakrishnan Muslim Jagani IS Solution Architect Review Document Amendment History: Version Date Changed by Remarks th Nov 2014 Initial draft 0.13 (MP) 13 th May 2015 Pete Talbot Updated to MODIS (MP) 13 th July 2015 Pete Talbot Updated from NG review comments and revised screens Feb-2017 Ninad Jagtap Updated the REMIT screen as part of P329 project requirements Mar-2017 Ninad Jagtap Added REMIT messages and field descriptions May-2017 Ninad Jagtap Updated line for xml file upload functionality as requested by business to Once file path is entered in the field, users can press Submit which would then lead to the confirmation screen. Please note that the upload process does not include the validation process Jun-2017 Ninad Jagtap Added message Please note: Please send all REMIT messages using the latest P329 REMIT XSD. If Market Participants send files using the non-p329 XSD, MODIS will not validate them and no negative acknowledgements will be sent back. under section 9. Added note on page 7 for browser back button functionality. Updated error message for Bidding zone. Document Location IBM MODIS Connections Document References Title ETR Mapping (MODIS) 1.0.xls ETR Functional Design v1.0 P329 ACER REMIT BRD ACER REMIT Detailed-Application-Design- V1.1 ACER REMIT-Functional-Design-V1.1 Document Location MODIS Connections MODIS Connections RemitConsultation/Shared%20Documents/For ms/allitems.aspx RemitConsultation/Shared%20Documents/For ms/allitems.aspx RemitConsultation/Shared%20Documents/For ms/allitems.aspx MODIS User Guide Screens V0 18 Page 32 of 33

33 Template Change History Owner/Author: IS EPO AMENDMENTS Issue Date Change Details Oct 2007 Initial release Paper Copies are Uncontrolled MODIS User Guide Screens V0 18 Page 33 of 33