system vendor testing kick-off - ediel · system vendor testing kick-off ... fingrid will...
TRANSCRIPT
System Vendor
testing
kick-off
Fredrik Södö
5.3.2019
Fredrik SödöFingrid Datahub Oy
5.3.2019Fredrik Södö
Expert
Stakeholder testing and certification
2
Agenda
• 09:00 – 10:00
• Approach to System Vendor testing
• Deployment plan and interface version management
• Support service
• Next steps
• 10:00 – 10:30
• Datahub B2B interface demo
Approach to System Vendor testing
Purpose
• To support System Vendors integrating their solutions to the datahub system
• To ensure the quality of datahub's external functions
5.3.2019Fredrik Södö5
Early testing
The datahub system is not ready when
System vendor testing starts!
all specified functionality will not be available
there will be bugs and malfunctions
the interface specification will change
business logic will change
We do our best to ensure sufficient quality
before deploying new versions
5.3.2019Fredrik Södö6
Enabling testing
• System Vendors are welcome to use the datahub test
environment in parallel with own development
• the solution does not have to be ready when the testing starts
• Fingrid will provide test scenarios before each Stage
• the scenarios are evaluated in workshops before each Stage
• a subset of the scenarios will form the target scope of the Stage
testing
• a subset of the target scope will form the baseline for official
datahub certification later on
• System Vendors are welcome to execute own
scenarios
• Fingrid will define intermediate targets on process level
for monitoring purposes
5.3.2019Fredrik Södö7
Monitoring• Fingrid will monitor progress for each Stage in relation to the
defined scope and intermediate targets
• System Vendors will be asked to report on the target scope
• The target is to achieve visibility of the real status of the System
Vendor readiness
5.3.2019Fredrik Södö9
• For Stage 1 Fingrid and CGI will provide the following structural data
separately for each vendor
• Fictive market parties (DSO's and Balance Suppliers identified by GLN codes)
• Fictive Metering Grid Areas (identified by EIC codes)
• Fictive products that can be used in agreements
(the system does not yet provide an interface for managing product information)
• Users
• CMS users based on data provided by the vendors
• system users for B2B communication
• A GSRN number has to be used as accounting point identification
• A technically correct Personal identity code has to be used as
customer identification
Test data
• The System Vendor testing will be performed in a cloud
environment maintained by CGI
• The environment will contain datahub user information, no
other personal data!
• Use of authentic personal data in System Vendor testing
is strictly prohibited
• Testers should also not use their own personal data
Privacy
Fredrik Södö 5.3.20199
Deployment plan and interface version
management
Overall principles for deployment
5.3.2019Fredrik Södö12
• The datahub system is developed according to an incremental model
• the target is to fix bugs and findings in the next version and to avoid the need of maintaining old versions
• a new version of the datahub system including interface version will be delivered in the beginning of each
Stage testing phase
• Interface version management
• The interface specification that applies for the next version will be published about 1,5 months prior to update
• System Vendors have to adopt to the new interface specification, the datahub project doesn't plan to
maintain several test environments for system vendors operating different interface versions
• new interface versions are not necessary backwards compatible with previous ones
2019
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
testing prep.
System Vendor testing activities 2019
5.3.2019Fredrik Södö13
Vendor testing
Con Stage 1 Stage 1-2 Stage 1-3 Stage 1-4
Stage 1 scenarios
- draft, review, workshops
Stage 2 scenarios
- draft, review, workshops
Stage 3 scenarios
- draft, review, workshops
Stage 4 scenarios
- draft, review, workshops
Contact info, general
planning, on-line meeting
Datahub delivery
Stage 1 dev & test Stage 2 dev & test
Stage 2 AT
Stage 3 dev & test
Stage 3 AT
Stage 4 dev & test
Stage 4 AT
Stage 5 dev & test
testing prep.
Summer vacation
Stage 1 AT testing prep. testing prep. testing prep.
DH-500
DH-600DH-200
DH-800
DH-900
Data interface (DH-1000)
DH-320
DH-330
DH-340
DH-700
DH-110
DH-130
DH-420
DH-810
B2B external interface
DH-120
DH-310
DH-410
Implementation plan for business process
support
05/03/2019Fredrik Södö14
Stage 1 Stage 2
Preparations
M
2018 2020
Nov Dec AugJulJunJan Feb Mar Apr May JanDecNovOctSep Feb Mar
2019
Stage 3 Stage 4 Stage 5
Vendor testing
Support for business processes will be implemented incrementally in five (5) stages according to the
following preliminary plan.
Fingrid will communicate eventual changes as the project proceeds.
Checkpoints 2019
5.3.2019Fredrik Södö15
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Stage 1
interface
spec
Kick-off
meeting
Instructions
for connection
to test env.
Connections
established
Stage 1
scenarios
draft
Stage 2
scenarios
draft
DH-410
DH-120
DH-310
Stage 1
approved
for SV test
Stage 2
interface
spec
Stage 2
approved
for SV test
Stage 3
interface
spec
Stage 3
scenarios
draft
Stage 3
approved
for SV test
Stage 4
scenarios
draft
Stage 4
interface
spec
Stage 5
scenarios
draft
Stage 4
approved
for SV test
DH-110
DH-130
DH-420
DH-810
DH-700DH-320
DH-330
DH-340
Stage 2
updateStage 1
updateStage 3
update
Stage 4
update
Support service
Support and communication
5.3.2019Fredrik Södö17
• Slack will be used for instant messaging
• Fingrid's personnel will follow the testing channel and
respond to questions
• Other members of the System vendor forum are also
welcome to attend the discussion
• A ServiceNow based portal will be established
for incident management and service requests
• defects that are found in the datahub-system
• service requests for technical assistance, e.g. in relation to
connectivity problems and protocol level issues
Next steps
Vendor testing March - April 2019
5.3.2019Fredrik Södö19
Date Activity Description
5.3.2019 Demonstration of the B2B interface Demonstration of the B2B interface (SoapUI). On-line meeting..
21.3.2019 Stage 1 Test scenario workshop 1 The test scenarios are evaluated in physical workshops with System Vendors
XX.3.2019 Stage 1 Test scenario workshop 2 Test scenario evaluation continues (if needed)
21.3.2019 Instructions for connectivity testing Instructions for connectivity testing delivered to System Vendors
Week 13 Agreement of connectivity tests Connectivity tests are agreed on beforehand to ensure a smooth process
Week 14 Connectivity tests Connectivity tests performed with each System Vendor that plans to start testing in April
(continues in weeks 15 and 16 if needed)
Week 15 CMS training + quick guide On-line training in the use of CMS GUI for System Vendors that start testing in April
Week 16 Stage 2 test scenarios published in System Vendor
Forum
Test scenarios on heading level
Week 16 Publication of the message specification for Stage 2 xsd and event-document for Stage 2
Vendor testing program, May – June 2019
5.3.2019Fredrik Södö20
Date Activity Description
8.5.2019 Stage 2 Test scenario workshop 1 The test scenarios are evaluated in physical workshops with System Vendors
XX.5.2019 Stage 2 Test scenario workshop 2 Test scenario evaluation continues (if needed)
Week 19 Target for DH-120 testing
Week 20 Target for DH-410 testing
Week 22 Target for DH-310 testing
Week 24 Stage 3 test scenarios published in System Vendor
Forum
Test scenarios on heading level
Week 26 Publication of the message specification for Stage 3 xsd and event-document for Stage 3
Week 26 Target for DH-110 testing
Week 27 Target for DH-130 testing
Demo
Fingrid Datahub Oy
c/o Fingrid Oyj
Läkkisepäntie 21
00620 Helsinki
PL 530, 00101 Helsinki
Puh. 030 395 5000
Y-tunnus: 2745543-5