CMOS Pro-Forma
MOSL CMOS
© 2015 CGI Group Inc. – All rights reserved
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
CONTROLLED
Information related to aspects of the MOSL CMOS project, intended for distribution either internally in MOSL
or externally to MOSL Members or eligible members affiliated to the Ofwat Open Water programme (for the
avoidance of doubt organisations who hold a relevant licence to operate with Ofwat).
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
i
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Revision History
Version
Status
Date
Description
Author
3.0.0.1
Working
16-03-2016
Initial draft – Class 2
S. Hassan
3.0.0.2
Working
17-03-2016
Updated following review by M. Roberts
S. Hassan
3.0.0.3
Working
17-03-2016
Updated following review by M. Roberts
S. Hassan
3.0.0.4
Working
17-03-2016
Updated following review by M. Roberts and I. Ahmed
S. Hassan
3.0.0.5
Working
18-03-2016
Updated following CGI review
M. Roberts
3.0.0.5
Working
21-03-2016
Updated following MOSL review
M. Roberts
3.1.0.0
Final
21-03-2016
Issued to Market Participants
MOSL
3.2.0.0
Final
31-03-2016
Updates following Market Participant comments
MOSL
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
ii
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Reviewers
Each reviewer acknowledges they have reviewed this document and are in agreement with its content as it
relates to their role in the engagement.
Name
Role
Mattijs van den Hoed
Design Authority
Dale Youngs
Security Manager
Alexander Boers
Environments Manager
Mathew Roberts
PMO Manager
Signature
Date
Owner
The owner is responsible for the creation of this document and acknowledges that this document meets the
quality standards and is ready for final signoff.
Name
Role
Tom Webb
SIT Analyst
Deepak Patel
MOSL Data Lead
Signature
Date
CGI Assurance
The CGI representative acknowledges that the document meets all the requirements and is accurately and
completely fulfills the document objectives as noted in section 1.1, Document Objectives, except as noted and
communicated to the Client.
Name
Role
Richard Brown
Project Manager
Signature
Date
Client Assurance
The Client representative acknowledges that this document accurately fulfills the document objectives as noted
in section 1.1Error! Reference source not found., Document Objectives, except as noted and communicated
to CGI.
Name
Role
John Briggs
Chief Technology Officer
CONTROLLED
Signature
Date
© 2016 CGI GROUP INC
All rights reserved
iii
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Table of contents
1
Introduction_______________________________________________________________________ 1
1.1
Purpose __________________________________________________________________________ 1
1.2
Document references _______________________________________________________________ 1
1.3
Abbreviations _____________________________________________________________________ 1
1.4
Definitions ________________________________________________________________________ 2
1.4.1 Market Participant _________________________________________________________________ 2
2
Process for Enrolment ______________________________________________________________ 3
3
Acquiring Certificates ______________________________________________________________ 4
3.1
Why do we need it _________________________________________________________________ 4
3.2
B2B, CMOS Portal and FTP authentication _____________________________________________ 5
3.3
What is a certificate ________________________________________________________________ 5
3.4
How will Market Participants acquire a certificate _______________________________________ 5
3.5
What does my certificate need to comply to ____________________________________________ 6
3.6
Can I re-use my STS certificates _____________________________________________________ 6
3.8
How many certificates does a Market Participant need? __________________________________ 7
3.9
What do I need to do with my certificates ______________________________________________ 7
3.10 IP address whitelisting ____________________________________________________________ 12
3.11 Who to contact ___________________________________________________________________ 12
4
Procurement Team Master Data _____________________________________________________ 13
4.1
Tariff Data _______________________________________________________________________ 13
4.2
Market Participant details __________________________________________________________ 13
4.3
Contract manager details __________________________________________________________ 15
4.4
System account (Admin user details) ________________________________________________ 16
4.5
Certificate naming convention ______________________________________________________ 16
4.6
IP details ________________________________________________________________________ 18
4.6.1 CMOS Portal and B2B _____________________________________________________________ 19
4.6.2 FTP
19
4.7
Wholesale contract (wholesaler only) – Phase 2 _______________________________________ 19
4.8
Interim supplier opt in/ out – Phase 2 ________________________________________________ 20
4.9
Gap site opt in – Phase 2 ___________________________________________________________ 21
A Appendix A – Pro-forma validation ______________________________________________________ 23
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
iv
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
1
Introduction
1.1 Purpose
The purpose of this document is to provide Market Participants (MP) with an overview of the requirements to
access CMOS (Central Market Operating System) on the pre-production environments using digital certificates.
It will also provide a template for capturing Master Data from Market Participants.
If you have any queries relating to the information provided in this document, or would like someone to provide
further guidance please contact [email protected] and one of the System Ready team will be in touch.
1.2 Document references
A number of supporting document have been published which work in conjunction to this pro-forma. If you
require assistance downloading a copy please contact the MOSL PMO who will be able to support.

Reference

Document

Version

Link
[1]
Certificate Management
0.0.5.1
https://www.mosl.co.uk/events/testspecial-interest-group-8-2-16/
[2]
CSD 0208
20150930
http://www.openwater.org.uk/media/1881/32apostvendormap-appendix2-wrcpart-5-csd0208.pdf
[3]
Market Opening Data Strategy
Final
https://www.mosl.co.uk/wpcontent/uploads/2016/01/MarketOpening-Data-Strategy-200116FINAL-1.pdf
[4]
Download Tariff Upload (XSD)
1.0
https://www.mosl.co.uk/events/testspecial-interest-group-1-3-16/
1.3
Abbreviations
Abbreviation
Description
MP
Market Participant
SI
System Integrator
CMOS
Core Market Operating System
DM
Data Migration
MOSL
Market Operator Services Limited
MST
Market Scenario Testing
SIT
System Integration Test
UAT
User Acceptance Testing
STS
Sector Test System
DL
Data Load
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 1 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
LVI
Low Volume Interface
HVI
High Volume Interface
CA
Certificate Authority
1.4 Definitions
1.4.1 Market Participant
For the purpose of this document, a “Market Participant” refers to either a “Wholesale” or “Retail” water
company, never to both. A wholesale company and its retail arm are considered two separate market
participants.
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 2 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
2
Process for Enrolment
The below process flow describes how information will be transferred between companies and the dependencies on all parties.
Enrolment Process for Market Participants
MOSL
Market
Participants
CGI
Review
completed
pro-forma
Issue
pro-forma
Clarify
requirements
with MOSL
Apply for
certificates
Complete
pro-forma
Install
certificate
Load data into
system
Whitelist IP
Range
Connectivity
Testing
Testing
Create Admin
Account
Note: Any application or connectivity queries should be relayed to the CGI Service Desk, details to be provided by the Service Readiness team at the beginning of
April 2016.
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 3 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
3
Acquiring Certificates
3.1 Why do we need it
Certificates are used within CMOS to authenticate users when they attempt to access the system. They are
used to authenticate both human user access via the CMOS Portal (which provides screens for users to
undertake administration, reporting, ad-hoc query and service management functions) and system access via
the B2B interface (which provides web services for B2B functions).
Certificates are also required for Market Participants to access the FTP (for Data Migration) environment which
will allow them to leave their data files for MOSL to upload into CMOS. The FTP environment will also be used
to collect Data Upload reports relating to the data files that have been uploaded.
The below table shows an overview of each environment and demonstrates where a certificate will be required
for those environments.
Environment
FTP
Purpose/
Usage
File drop &
collection
Comments
Data files drop and collection of
upload reports
Full volume data migration
environment
Data
Data upload
Market
Participant
Sandpit (MPS)
Market Participant
Execution of CMOS transactions
Sandpit
Market
Participant
Role
FTP
Certificate
B2B
Interface
Certificate
CMOS
Portal
Certificate
Wholesaler &
Market Operator
Yes
N/A
N/A
Retailer
N/A
N/A
N/A
Market Operator
N/A
N/A
N/A
Wholesaler &
Retailer
N/A
Yes
Yes
Data Validation
Sandpit
Iterative data uploads; no
certificate required for this period
as this is MOSLs use
Market Operator
N/A
N/A
N/A
Market Entry
Assurance (MEA)
Certificates required for start of
MEA
Wholesaler &
Retailer
N/A
Yes
Yes
User Acceptance
Testing (UAT)**
User acceptance
testing
Users test the software to make
sure it can handle required tasks
in the Live Market scenarios,
certificate required
Wholesaler &
Retailer
N/A
Yes
Yes
Training
Training
Certificate not required at this
time, subject to change
Wholesaler &
Retailer
N/A
N/A
N/A
Market Sector
Testing (MST)
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 4 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
**for the applicable Market Participants
Note: Where a Market Participant has no access to a particular environment it is referred to as “N/A” – i.e. it
means access is not available. It does not mean that access is available without a certificate.
3.2 B2B, CMOS Portal and FTP authentication
For CMOS Portal, validation of the source is established by organisation level certificate. Once the certificates
are validated, username and password are used to establish the identity and authenticate the user via Active
Directory.
For B2B, validation of the identity is established by client certificate which is linked one to one to a Market
Participant’s CMOS Organisation ID. The CMOS system retrieves the account on the basis of the certificate
identity to authenticate the sender for the B2B.
For FTP, validation of the identity is established by client certificate which is linked one to one to a Market
Participant’s CMOS Organisation ID. The CMOS system retrieves the account on the basis of the certificate
identity to authenticate the sender for the FTP.
3.3 What is a certificate
A digital certificate is an online passport which validates a user’s identity, allows a person, system or an
organisation to exchange data securely.
3.4 How will Market Participants acquire a certificate
All Market Participants will be required to acquire certificates for their, and their System Integrators, own use.
A certificate can be purchased from one of the trusted Certificate Authorities (CAs) listed below. Certificate
products from each CA which meet MOSL’s defined requirements are also listed below.
Certificate Authority
Product
From their portal select;
Entrust
Create > SSL/TLS > Standard
GlobalSign
PersonalSign 2 Pro. (Recommendation from GlobalSign that
their ePKI Manager is used which will allow certificate Common
Names to be defined)
Symantec Corporation
Due to issues communicated by the Market Participants MOSL
are no longer recommending this Certificate Authority
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 5 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
3.5 What does my certificate need to comply to
Certificated purchased by the Market Participants need to be compliant with the following requirements;

Issued from a Certificate Authority (CA) as defined in section 3.4

Be compliant with the X.509 standard

Must be a Class 2 Client Certificate (a certificate which validates your organisation)

Must state “client authentication” in the extended key usage and must not state “server authentication”

Must have a validity period of no more than 3 years and not be expired

That the certificates “Common Name” is unique for each certificate provided, refer to section 4.5
See section 1.2 and refer to the Certificate Management document for more details.
In order for a Market Participant to access the system they must share the Public Key of their certificates with
MOSL. This should be sent within this Pro-forma, see section 4.5.
Note: The private key associated with any certificate must not be submitted to MOSL within the Proforma, or at any other time.
3.6 Can I re-use my STS certificates
If you participated with the Sector Test System (STS) and the certification you provided met the criteria set out
in section 3.5 then it is possible to re-use these certificates. If a Market Participant wants to re-use these
certificates please update section 4.5 with the certificate information.
Note: These certificates will be removed from the STS environment so will no longer be available to use
3.7 What to do with my completed pro-forma
All completed pro-formas need to be issued back to MOSL to [email protected]. MOSL have introduced
a Participant Validation stage which will require Market Participant CIOs to authorise appointed members of
their organisation who have the authority to issue a pro-forma. The validation form can be found in appendix
A.
Once MOSL are happy with the completed pro-forma they will issue it to CGI who will check that the certificate
and user information meets the defined requirements. If your certificate is not valid the Participant will be notified
as soon as reasonably possible and a new certificate will be requested. Once a valid certificate is submitted,
MOSL will load this against a Market Participants account within the CMOS system and will be used during the
logon authentication steps.
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 6 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
3.8 How many certificates does a Market Participant need?
The number of certificates required by Market Participants to access the various environments is dependent on
their need to meet the requirements set out in section 3.1. Areas of note:

CMOS Portal: One client certificate required per MP, per environment which can be replicated and
installed across the organisation’s end-user devices.

B2B: One client certificate required per MP, per environment e.g. if a Participant is running independent
test and development environments then a certificate is required for each

FTP: One client certificate required per MP

System Integrators: If partnering with an System Integrators they will require their own certification.
3.9 What do I need to do with my certificates
Once you have received your certificates they need to be installed on to your local machine or business system.
The below screen shots explain where the certificates need to be installed on a local machine, the installation
of a certificate within your backend systems for B2B access will differ for each application;
1. Save the certificate to your computer
2. Open the .pfx file
3. When the Certificate Import Wizard loads follow the below steps;
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 7 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Navigate to where the certificate is stored on your local machine
Enter the password you have been provided
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 8 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Make sure the certificate is installed in your personal store.
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 9 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Press next.
Click Finish. Now open your Browser (Internet Explorer 11 shown as an example) and navigate to the
Internet Options > Content > Certificates. You should see the new imported certificate within your Personal
Store;
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 10 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Double click the certificate to open it. You will be presented with the certificate. It’s important to notice the key
symbol which denotes you have the “private key” installed.
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 11 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
3.10 IP address whitelisting
IP addresses and ranges being used to access CMOS and FTP need to be whitelisted. Following submission
of this document, IP ranges included in section 4 will be added to the whitelist. It is important to note that if
accessing CMOS or FTP through a proxy, the public IP address of the proxy will need to be whitelisted, not the
unique IP of the device.
3.11 Who to contact
It is recommended that the Market Participant speaks with one of the following members of their business who
will be able to provide support in the purchase and installation of the certificates;

IT Manager

Security Architect/Manager

Networking Manage
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 12 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
4
Procurement Team Master Data
The following sections provide templates for entering the required details listed below. The templates detail
fields that are required or optional and include sample entries in italics and blue text to provide a reference.
Master Data provided by each market participant will be pre-loaded into each of the environments from Phase
1 and will consist of:






Tariff data
Market participants’ organisational details
Contact details of the organisation
User administrator details
Certificate details
IP address details
The below components of Master Data will be pre-loaded into the CMOS environments from Phase 2
onwards and are provided by the wholesaler only:



Wholesale contract
Interim supplier opt in/ out
Gap site opt in
4.1 Tariff Data
Tariff Data is one element of Master Data and includes such data items as:



Service Component Tariff Code
Effective Dates
Charge Elements
Tariff Data is expected to be received in XML format and to assist with building this please refer to the Market
Opening Data Strategy document ‘Appendix H – Tariffs XML template’ which will show you an example.
For the structure and validation rules of the Tariff Data fields please see the XSD on the MOSL website which
is located here: https://www.mosl.co.uk/events/test-special-interest-group-1-3-16.
For further guidance on how to populate Wholesaler Tariff Data for each of the service components please see
Appendix A of CSD 0208.
4.2 Market Participant details
Firstly, at a minimum all Market Participants are required to complete the pro-forma. This would allow MOSL to
create an ‘Admin’ account for each Market Participant to access CMOS via the Portal for each pre-production
environment, which in turn would allow Market Participants to create additional users on CMOS for portal
access.
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 13 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Secondly, if Market Participants require access to CMOS via the B2B channel, they will need to provide the
appropriate number of certificates for B2B access within the pro-forma.
Lastly, only Wholesalers are allowed to access the FTP (Data Upload) environment and similar to B2B, they
will need to provide the appropriate number of certificates for FTP access within the pro-forma.
Wholesale and Retail companies are treated as separate Market Participants, therefore separate proformas and certificates are required for each wholesale and each retail participant. Please signify in
the table below which entity of your business it relates to.
Attribute
Required
Value
Notes or sample
Organisation name
Yes
MOSL
Wholesale / Retail
Yes
W or R
Water services (yes/no)
Yes
Yes
Sewerage services (yes/no)
Yes
Yes
Secondary Addressable Object
No
Primary Addressable Object
No
Address Line 1 (street name)
Yes
Address Line 2
No
Address Line 3
No
Address Line 4
No
Address Line 5
Yes
High Holborn
London
(City)
Postcode
Yes
WC1V6BX
Primary contact first name
Yes
John
Primary contact surname
Yes
Smith
Primary contact ttile (Mr/Mrs/Miss)
Yes
Mr
Primary contact department
No
Communications
Primary contact email address
Yes
[email protected]
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 14 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Attribute
Required
Primary contact phone number
Yes
Trading Party Type (D4014)
Yes
Value
Notes or sample
07778 123456
Supplied by Retailers only:
FULL / SELFSUPPLY / TERMINATED
Supplied by Wholesalers only:
Default Return to Sewer (D7051)
Yes
95%
Vacancy Charging Method Water
Supplied by Wholesalers only:
Yes
VWA / VWB / VWC
(D7052)
Vacancy Charging Method Sewerage
Supplied by Wholesalers only:
Yes
VSA / VSB / VSC / VSD / VSE
(D7053)
Supplied by Wholesalers only:
Temporary Disconnection Charging
Method Water (D7054)
Yes
Temporary Disconnection Charging
Method Sewerage (D7055)
Yes
Alternative Tariff Year Start Date
No
TWA / TWB / TWC
Supplied by Wholesalers only:
TSA / TSB / TSC / TSD / TSE
Supplied by Wholesalers only. Only required
if tariff year does not start on the 1st April
ddMmm e.g.01Jul
4.3 Contract manager details
The role of the Contract Manager has been defined as the primary contact for each of the Market Participants
with respect to their interaction with MOSL. Please complete all required fields.
Attribute
Required
Contract manager first name
Yes
John
Contract manager Name
Yes
Smith
Contract manager Title (Mr/Mrs/Miss)
Yes
Mr
Contract manager Email Address
Yes
[email protected]
CONTROLLED
Value
Notes or sample
© 2016 CGI GROUP INC
All rights reserved
Page 15 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Contract manager Phone Number
Yes
07778 123456
Contract manager Department
No
Communications
4.4 System account (Admin user details)
The CMOS system has defined two additional roles covering User and Admin. A User is defined as a member
of the Market Participant who will operate the system on a day to day basis. The Admin role will have the same
functionality as the User but in addition will be to add and change the profile of existing Users and create new
ones via the CMOS Portal.
MOSL will assign one Admin user per organisation, it is up to the Admin to create as many users as they require.
The details listed in this table will be used for all pre-production environments. Please complete all fields.
Role
(Admin)
Email address
Full name
Phone number
Admin
[email protected]
John Smith
07778 123456
Admin
4.5 Certificate naming convention
An X.509 certificate consists of a number of fields. The subject field identifies the entity associated with the
public key stored in the subject public key field. The subject name can be carried in the subject field and/or the
Subject Alternative Name extension.
The Subject field holds the Distinguished Name (DN) of the client to which the certificate belongs. A DN is a
unique name given to an X.500 directory object. It consists of a number of attribute-value pairs called Relative
Distinguished Names (RDNs). The relevant RDNs are:






CN: CommonName
OU: OrganizationalUnit
O: Organization
L: Locality
S: StateOrProvinceName
C: CountryName
All CMOS certificates (Portal, B2B, FTP) are required to follow the below CommonName naming
convention as this forms part of the log in authentication. Naming certificates in this way also makes
it easier to identify the MP and the intended use of the certificate.
Format:
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 16 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
<Instance>_<Market Participant Name>_<Market Participant Type>_<Access Type>_<Serial>
Example 1:
MST_MOSL_MO_Portal_1
Example 2:
MST_ABC Water_WS_B2B_2
Example 3:
FTP_MOSL_MO_FTP_3
Note: Only “Wholesale” Market Participants will be given access to the FTP server, not relevant for Retail.
Common name component
Description
Example 1
Pre-Production Logical Environment or FTP:
FTP, or
TPS, or
<Instance>
MST
MST, or
UAT, or
Training
Company name of market participant:
Wholesale company, or
<Market Participant Name>
MOSL
Retail company, or
Market operator
WS for Wholesale, or
<Market Participant Type>
MO
RT for Retail, or
MO for Market Operator
Portal, or
<Access Type>
Portal
B2B, or
FTP
Certificate Number
e.g. <1> for the first certificate, <2> for the
1
second certificate, <3> for the third certificate
and so on. This simply refers to nth certificate
that has been purchased.
<Serial>
Please complete certification section of the pro-forma below:
Type
(CMOS
CONTROLLED
Environment
Certificate
name
Full name of
person
Phone
number
Email
address
Certificate CER file data in
Base-64 format
© 2016 CGI GROUP INC
All rights reserved
Page 17 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Portal,
B2B, FTP)
responsible for
certificate
-----BEGIN CERTIFICATE-----
CMOS
Portal
MPS
MST_MOSL_
John Smith
MO_Portal_1
07778
123456
John.smith@
mosl.co.uk
MIICLDCCAZWgAwIBAgIQdBkc6O
VPeK9Mot0/VpyZpTANBgkqhkiG9
w0BAQUFADAfMR0wGwYDVQQD
ExRtYXR0aWpzIHZhbiBkZW4gaG
9lZDAeFw0xNDEyMzEyMzAwMDB
aFw0yMDEyMzEyMzAwMDBaMB8
xHTAbBgNVBAMTFG1hdHRpanM
gdmFuIGRlbiBob2VkMIGfMA0GCS
qGSIb3DQEBAQUAA4GNADCBiQ
KBgQDiVsiw3nccn6rT3cSoS0obxM
/tmfHdkwl5HTjGX41QyLgiDyXFXf6
K1xLOoRE7DwDy/ks2Z49RkGzw
WJ+UQYEPFY8IBsjEI8FYt+Z4p5O
Q+nNkCtSpZrNHcBEhNXpGUOW
HwhJim2t1KYv5RyK1ow0CH1DwU
iFeq6BHUP+BFhxMzwIDAQABo2k
wZzATBgNVHSUEDDAKBggrBgE
FBQcDAzBQBgNVHQEESTBHgB
CDa8+h7uApcSxOokjje/ieoSEwHz
EdMBsGA1UEAxMUbWF0dGlqcyB
2YW4gZGVuIGhvZWSCEHQZHOjl
T3ivTKLdP1acmaUwDQYJKoZIhvc
NAQEFBQADgYEAG588hhyOKbW
VrOhjK+3TifrEopcq1PFCZkS9osE1
OcVXUTOYi9VLbXCnTg4vUgNxjN/
F4wgIf3rnGWm+eDr6fUYLMz0dRw
HYmBqne4vo4DoWH1wK1dIY39E
UP5CE3LtigBcr+EVHG2IsTgwPEd
JoeKVsaA+joeci7yl89VNC5bo=
-----END CERTIFICATE-----
CMOS
Portal
B2B
FTP
4.6 IP details
IP details are required for access to,
1. CMOS on all the pre-production environments via Portal and B2B, and
2. FTP server for data uploads via FTP
IP details have been requested separately for both, see below.
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 18 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
4.6.1 CMOS Portal and B2B
Required external IP address details for access to CMOS via Portal and B2B, all fields are required.
IP address or range
Specific - 195.34.200.10
Range – 200.195.64.8 – 200.195.64.29
Specific
Range
4.6.2 FTP
Required external IP address details for access to FTP server via FTP, all fields are required.
IP address or range
Specific - 195.34.200.10
Range – 200.195.64.8 – 200.195.64.29
Specific
Range
4.7 Wholesale contract (wholesaler only) – Phase 2
The Wholesale contract is a bilateral contract between a Wholesaler and a Retailer to deliver Water or
Sewerage services. For every service a separate contract is created by the Wholesaler.
The below information is required for the Wholesale contract from the wholesaler:
Data Item
Description
Example
Wholesaler ID
The ID of the wholesaler, a full list can be
found in the Appendix G of the Market
Opening Data Strategy
SOUTHWEST-W
Retailer ID
The ID of the retailer, a full list can be found
COMMERCIAL-R
in the Appendix G of the Market Opening
Data Strategy
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 19 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Shows the status of the contract, valid
values include:
Status
ACTIVE
ACTIVE
NOMORESPID
This defines what type of service the
contract is for, valid values include:
Service
WATER
WATER
SEWAGE
Effective from Date
The Wholesale contract is current/ongoing
as long as the ‘Effective From date’ is today
11/03/2016
or earlier and the ‘Effective To date‘ is
empty or lies in the future.
Effective to Date
The Wholesale contract is current/ongoing
as long as the ‘Effective From date’ is today
11/03/2017
or earlier and the ‘Effective To date‘ is
empty or lies in the future.
4.8 Interim supplier opt in/ out – Phase 2
To be included in the Interim Supplier Allocation process, the Retailer may choose to Opt In to receive Supply
Points from the exiting Retailer. Similarly, a Retailer may choose to Opt Out from the Interim Supplier Allocation
process. These options are available to Retailers at any time. For every service a separate agreement is
required.
The following information from the wholesaler is required for the interim supplier to opt in/ out from the Interim
Supplier Allocation process:
Data Item
Format/ Valid Value
Description
Example
Wholesaler ID
Text
The ID of the wholesaler, a full list
can be found in the Appendix G of
the Market Opening Data Strategy
SOUTHWEST-W
Retailer ID
Text
The ID of the retailer, a full list can
be found in the Appendix G of the
Market Opening Data Strategy
COMMERCIAL-R
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 20 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Data Item
Format/ Valid Value
Description
OPTIN
Retailer has opted in to the Interim
Supplier Allocation Process
OPTOUT
Retailer not opted in of the Interim
Supplier Allocation Process
INVOLSUS
Retailer suspended due to
alternative action for insolvency
VOLSUS
Retailer voluntarily suspended from
impending Interim Supplier
Allocation Process
WATER
Water service category
SEWERAGE
Sewerage service category
Effective from Date
DD/MM/YYYY
Effective From date must be today
or after today
Effective to Date
DD/MM/YYYY
End of the opt in period (may not be
01/01/2017
empty).
Status
Example
Service
OPTIN
WATER
11/03/2016
4.9 Gap site opt in – Phase 2
To be included in the Gap Site Allocation process, the Retailer may choose to Opt In to receive Supply Points
with connection type Gap Site. For every service a separate agreement is required.
Data Item
Format/ Valid Value
Description
Wholesaler ID
Text
The ID of the wholesaler, a full
list can be found in the Appendix
SOUTHWEST-W
G of the Market Opening Data
Strategy
Retailer ID
Text
The ID of the retailer, a full list
can be found in the Appendix G
of the Market Opening Data
Strategy
REQUESTED
Opt-in request for an gap site
allocation agreement
OPTIN
Confirmed gap site allocation
agreement
REJECTED
Rejected gap site allocation
agreement
Status
CONTROLLED
Example
COMMERCIAL-R
REQUESTED
© 2016 CGI GROUP INC
All rights reserved
Page 21 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
Data Item
Format/ Valid Value
Description
Example
MOSUS
Gap site allocation agreement
suspended by the Market
Operator
INVOLSUS
Gap site allocation agreement
suspended by Market Operator
due to alternative action for
insolvency
WATER
Water service category
WATER
SEWERAGE
Sewerage service category
SEWERAGE
Effective from Date
DD/MM/YYYY
The Effective From date is
prefilled with the date as set by
the parameter
GAP_SITE_PERIOD_START
01/04/2016
Effective to Date
DD/MM/YYYY
End of the gap site period
01/04/2017
Service
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 22 of 13
Data Environment Certification Pro-forma
Version: 2.0.0.4
Date published: 2016/3/31
A Appendix A – Pro-forma validation
CONTROLLED
© 2016 CGI GROUP INC
All rights reserved
Page 23 of 13
CMOS Organisational Validation and Authorised Users
Organisational Validation and Authorised Users
As part of the Class 2 (Organisationally Validated) certificate process, the identity of the organisation requesting
certificates will be validated by the Certificate Authority. This however does not include validating whether the person
requesting the certificate and submitting the pro-forma to MOSL is authorised to do so.
Validating that the person submitting the pro-forma is authorised to do so will be undertaken by MOSL. MOSL will
maintain a list of authorised users. The initial list of authorised users will be submitted by the Chief Information Officer
(CIO) on behalf of the organisation using the pro-forma below. The CIO may then choose to delegate authority for
informing MOSL of subsequent changes to the list of authorised users.
Authorised User pro-forma:
Position
Name
Role
Delegated Authority
Delegated Authority
Authorised
Authorised
Authorised
Please send the completed form to [email protected]
Regards
MOSL
Email
Phone