FAQ’s for TIBCO Upgrade Project

Questions

Digital Certs     EMMA     Performance Testing     Test and Cutover     Webforms     SMART Metering  Licences

Digital Certs
1 Each market participant is responsible for purchasing of digital certs  “as per guidelines provided”   –  how/when will these guidelines be provided?
EMMA
1 Where will the EMMA Installation & Deployment  workshops be held?  How long will each workshop last? Do attendees need to be present in person or will there be a Webex option?
2 What is included in the EMMA code release, does this include Webforms?
3 Will there be any changes to the underlying (Oracle) database schema for the supplier TIBCO (EMMA)? And what impact will this have on any reports running off it currently?
4 In the “New EMMA configs” (large option) there is one server in the DMZ and one interior server. So in this setup will the DMZ server be the file server (folder structure) and the internal one the application server?
5 What is the advantage and purpose of having a DMZ server in the set up?
6 Will the Oracle Software be provided?
7 What is the preferred Remote Access Client?
8 Can you explain the requirement for 7 user licences to the Oracle machine?
9 With regards to the requirement for the 4 static external IP address:
a. Can you explain why 2 IP’s are required for each environment?
b. Is there any possibility that rather than IP based these could become DNS based?
10 There will be 2 EMMA’s running on parallel, one for performance testing and another for IPT. Which of the two EMMA’s is envisaged to become the suppliers new production EMMA or is that left to the supplier to decide?
11 On the install of the EMMA’s by Capita, for a suppliers DR EMMA’s, will they be included in the installs to be carried out by Capita, putting any testing aside for the moment?
12 Who “owns” the EMMA server (and is responsible for the software licences)?
13 Can you tell me the purpose of the database component of the EMMA configuration?
14 Port Numbers. In relation to the list of port numbers and associated parameters what significance do these have?
15 IP Addresses. Can the existing static IP addresses be used within the new Setup?
16 In the new TIBCO solution at what stage, and in what circumstances, will the 601MM and 602MM be generated?
Performance Testing
1 Who will be required to participate in the Performance Testing exercise scheduled to run 21/9/2015 to 9/10/2015?
2 What level of resource would you expect might be required from a market participant during Performance Testing ?
3 Are you bundling the EMMA performance testing with current volumes with the Smart volumes testing together, or allowing suppliers to only opt for the performance testing on the current volumes?
Test & Cutover Preparation Workshop
1 Where will the Test & Cutover workshop  be held?  How long will the workshop last? Do attendees need to be present in person or will there be a Webex option?
Webforms
1 Where will the Webforms Functional training be held?  How long will the training last? Do attendees need to be present in person or will there be a Webex option?
SMART Metering
1 What part will Suppliers have in Smart Metering Testing?
Licences
1 Do Suppliers have to purchase TIBCO software licences?

Answers

Digital Certs
Q1 Each market participant is responsible for purchasing of digital certs “as per guidelines provided” – how/when will these guidelines be provided? Back to top
A1 These guidelines will be provided w/ending 3rd July.
EMMA
Q1 Where will the EMMA Installation & Deployment workshops be held? How long will each workshop last? Do attendees need to be present in person or will there be a Webex option? Back to top
A1 It is expected that these workshops will be held in the City North Hotel (M1) and each one will last approximately half a day. A Webex session will be set up.
Q2 What is included in the EMMA code release, does this include Webforms? Back to top
A2 The EMMA Code Release includes TIBCO and Webforms code and configuration as required.
Q3 Will there be any changes to the underlying (Oracle) database schema for the supplier TIBCO (EMMA)? And what impact will this have on any reports running off it currently? Back to top
A3 Yes, the underlying Oracle schema will change and there are no similarities with the current schema so existing reports will need to be updated. However, we can share the DDL files at a later stage after some test phases have been completed.
Q4 In the “New EMMA configs” (large option) there is one server in the DMZ and one interior server. So in this setup will the DMZ server be the file server (folder structure) and the internal one the application server? Back to top
A4 In the new EMMA configuration for Suppliers with larger message volumes it is proposed that the interior server will act as the XML file store and the DMZ server will act simply as a gateway server to the EMMA application. This would be regarded as a more secure approach.
Q5  What is the advantage and purpose of having a DMZ server in the set up? Back to top
A5 The main advantages of splitting the DMZ and TIBCO App components as suggested are:
a)      It would be considered a more secure approach (generally speaking) to store the market messages on the internal network.
b)      It provides a more flexible solution for scaling – the gateway (DMZ) server is quite a lightweight component that is unlikely to outgrow itself whereas, in the event of a Supplier having to scale to meet increased message volumes/sizes, having the App server separated from the DMZ component would allow the Supplier to scale this component either vertically – more CPU, RAM – or horizontally by adding another App server.
Q6 Will the Oracle Software be provided? Back to top
A6 The purchase/provision of Oracle software is the responsibility of the Supplier, as is currently the case. The Oracle database scripts will be provided by the project.
Q7 What is the preferred Remote Access Client? Back to top
A7 As per the current preference – suggested options here are WebEx, Lync or TeamViewer.
Q8 Can you explain the requirement for 7 user licences to the Oracle machine? Back to top
A8 There are a number of built-in user licenses required by the EMMA TIBCO and Webforms applications themselves, i.e. to allow them connect to the database and there is also provision (out of 7) for an additional 2 Webforms users. Oracle licensing is complicated but one condition is that any individual user of the system (i.e. Webforms) will require a Named User License. This would be the case currently too.
Q9 With regards to the requirement for the 4 static external IP address:
a. Can you explain why 2 IP’s are required for each environment?
b. Is there any possibility that rather than IP based these could become DNS based?
Back to top
A9 The large EMMA must expose a Gateway server URL which contains a static external IP address.  As there are PROD and TEST environments, this means a total of 2 IP addresses for the external Gateway Service. The second IP address per environment is a spare and is not mandatory. DNS hostnames cannot be used as the HUB does not have access to an external DNS service.
Q10 There will be 2 EMMA’s running on parallel, one for performance testing and another for IPT. Which of the two EMMA’s is envisaged to become the suppliers new production EMMA or is that left to the supplier to decide? Back to top
A10 The EMMA being used for IPT will become the production EMMA for Suppliers. There will be a clean down activity that will be executed by Capita during the period after IPT and prior to Cutover.
Q11 On the install of the EMMA’s by Capita, for a suppliers DR EMMA’s, will they be included in the installs to be carried out by Capita, putting any testing aside for the moment? Back to top
A11 No, the install process will only setup the suppliers production and test EMMA.
Q12 Who “owns” the EMMA server (and is responsible for the software licences)? Back to top
A12 The EMMA server is owned and  managed by the Supplier, as per the current solution, licensing of all non TIBCO components is the responsibility of the supplier.
Q13 Can you tell me the purpose of the database component of the EMMA configuration? Back to top
A13 The underlying (TIBCO) technology utilised in the EMMA solution requires the ability to hold and store information as part of its capacity to process market messages, as such this requires the use of a database.  The database will be used to store the information during transit back and forth to the Hub and additionally will be used to record its transient status during this process.

In other words the current EMMA solution  uses a database which keeps the records of all inbound and outbound processing of the market messages. From the user perspective, database may not be visible, as file transfers are done via Windows Explorer, however it is crucial to have a database in the EMMA solution. The new solution will also need a database for the same purpose.

Q14 Port Numbers. In relation to the list of port numbers and associated parameters what significance do these have? Back to top
A14 The port number provided will be needed by the EMMA sserver, and those ports  need to be kept open as part of the server build/commissioning activitytest.
Q15 IP Addresses. Can the existing static IP addresses be used within the new Setup? Back to top
A15 No the existing IP address cannot be used as part of the new solution.  There will be a period of time when the new solution needs to be in place and the current solution will still be in operation.  Once the current solution is no longer in use that IP address will be avaiable for the market Participant to use elsewhere.
Q16 IP Addresses. Can the existing static IP addresses be used within the new Setup? Back to top
A16 601 Messages & Outbound Message Validation

In the new TIBCO solution, a 601 message will be generated for any message from EMMA to HUB that fails validation.  Validation is performed at two locations:

(A) At the EMMA itself, basic validation is applied before sending the message to Hub – this is the precheck

(B) At the HUB, full schema validation of the message is applied.

In both scenarios outlined, a 601 message will be generated.

Scenario A

When the message is picked up from the Outbound folder for processing, a small number of precheck validations are execute – these relate primarily to routing and  to confirmation the header is properly constructed and includes MPRN and MpBusRef (where mandatory) ) In the event of a precheck failure in the EMMA, the EMMA creates a 601 file in the INBOUND and ARCHIVE folders. It also moves the original MM file from OUTBOUND folder to INVALID folder.

The  601 MESSAGE details are saved in the database. Both MM and 601 messages are viewable through the search functionality.  Note these messages never reach the Hub.  The 601 is generated in real time so the Market Participant will have visibility of the error almost immediately.

Scenario B

The new process with central validation at the Hub means the a 601 will be issued from Hub to EMMA should the message fail validation.  This is where full schema validation takes place.  Note that detailed error messages explaining the field which caused validation to fail will be included in these 601s in the error description.

The 601 message will be generated and automatically sent to a Market Participant should their message fail validation at the Hub.  This message will arrive to the Inbound folder as per any message from Hub to EMMA and is viewable through the Search functionality (and message details are saved to the database and the payload will exist as a file on the file system). It also moves MM file from OUTBOUND to INVALID folder.

Messages sent from EMMA to HUB will be marked with a status of PENDING at send time.  Once the message has been processed at the HUB it will generate a response to EMMA, and EMMA will update the message from PENDING to the appropriate status.  If it passed validation it will be updated to COMPLETED.  If it failed validation and a 601 was issued, the original message will be updated to a status of 601_COMPLETED.

RECEIVED –> PROCESSED –> PENDING –> INVALID –> RECEIVED –> 601_COMPLETED

The 601 is generated in real time so the Market Participant will have visibility of the error very soon after sending.

Market Participants may want to consider an adjustment to their ‘failed validation’ processes to handle this approach for example automated processing of 601 messages received.

602 Messages

The 602 is a daily summary of all messages and is a market message that will be created every morning and will accurately reflect the total number of messages that were sent/received to/from each Market Participant from 03:00:00 am to 02:59:59 am on that day. This message will arrive to the Inbound folder as per any message from Hub to EMMA and is viewable through the Search functionality (and message details are saved to the database and the payload will exist as a file on the file system). Functionally, this process has not changed. It will only include successful messages and hence anything generating a 601 will not appear on the report. Market Participants may want to consider an adjustment to their ‘602 reconciliation’ processes based on the state model outlined above

Performance Testing
Q1 Who will be required to participate in the Performance Testing exercise scheduled to run 21/9/2015 to 9/10/2015 Back to top
A1 A number of larger suppliers will be invited to Participate in Performance testing
Q2 What level of resource would you expect might be required from a market participant during Performance Testing ? Back to top
A2 If you are invited and agree to take part the involvement for the Supplier is expected to be for a 1-2 week period during the Performance Testing window. The project will aim to minimise the impact on Suppliers.
Q3 Are you bundling the EMMA performance testing with current volumes with the Smart volumes testing together, or allowing suppliers to only opt for the performance testing on the current volumes? Back to top
A3 Smart Meter Messages will be sent from HUB to Suppliers as part of the overall project testing (including performance). However there is no expectation for Suppliers to send any Smart Meter Messages (or responses to these messages) back to HUB or process the Smart Meter messages. At this time  (due in part to the planned commencement date of Smart Metering) the EMMA Specs provided are not designed to meet the processing requirements of Smart Meter message volumes (both to and from the Hub). However to reflect the expected increased volume of messages such as 017 and 010 in the Smart meter market, Suppliers can choose to put additional volumes of inbound messages, and we can consider those as part of stress testing.
Test & Cutover Preparation Workshop
Q1 Where will the Test & Cutover workshop be held? How long will the workshop last? Do attendees need to be present in person or will there be a Webex option? Back to top
A1 It is expected that these workshops will be held in the City North Hotel (M1) and each one will last approximately half a day. A Webex session will be set up.
Webforms
Q1 Where will the Webforms Functional training be held?  How long will the training last? Do attendees need to be present in person or will there be a Webex option? Back to top
A1 It is expected that these workshops will be held in the City North Hotel (M1) and each one will last approximately half a day. A Webex session will be set up.
SMART Metering
Q1 What part will Suppliers have in Smart Metering Testing? Back to top
A1 As part of Performance Testing where we hope to involve only the larget Suppliers in the market(s) in terms of message volumes, we will generate test Smart Metering messages and pass them between the new Hub and Large Suppliers’ new test EMMAs to check what impact their might be on the Comms links and the new EMMA specs. We aim to automate this testing and it’s scope will be contained to only the TIBCO elements (i.e. not Suppliers’ back-end systems) and so their will be minimal input from Suppliers required. We will be contacting those Suppliers separately on this point.
Licences
Q1 Do Suppliers have to purchase TIBCO software licences? Back to top
A1 No, the project will provide Suppliers with licenced copies of the required TIBCO software and new IBM Webforms software. The TIBCO and IBM EMMA software will be made available to download in advance of Capita performing the EMMA installations.