A request to participate in a competitive procedure with negotiation, aiming at the conclusion of a service contract regarding the improvement of the current software systems of the Association of Issuing Bodies. The service contract consists of three lots that can each be awarded separately. For the different lots, similar award criteria will be used.
Lot 1: Revision of AIB's HUB application software. This could either be upgrading, conversion or renewal. An assessment by supplier and a proposal for a strategy will be part of the invitation to tender.
Lot 2: Hosting of the HUB application for remote access by registries/members,
Lot 3: Maintenance of the HUB software.
To appreciate the background of the service contract, AIB and its intentions are elaborated underneath. Also links to the EECS-framework and AIB's Articles of Association are provided.
About The AIB.
AIB, or the Association of Issuing Bodies, is an association that joins competent bodies that have been appointed by governments to issue certificates providing evidence of the origin of green energy. The AIB is an international non-profit association (AiSBL) under Belgian law.
The purpose of the AIB is to develop, use and promote a standardised system to ensure the reliable operation of international energy certificate schemes: the European Energy Certificate System — 'EECS'. See also: www.aib-net.org
EECS and the Hub application.
The European Energy Certificate System (EECS) offers a framework for creating and transferring electronic documents (EECS Certificates; see link underneath for further explanation). For each megawatt-hour of energy, EECS certifies the quality of its source and/or the method of its production. The EECS Rules ensure that EECS energy certificate systems are reliable, secure and inter-operable — these harmonised standards enable the owners of EECS Certificates to transfer them to other domestic and international account holders.
EECS is based on structures and procedures which ensure the reliable operation of international certificate schemes. These schemes satisfy the criteria of objectivity, non-discrimination, transparency and costs effectiveness, in order to facilitate the international exchange of certificates.
Development in the green energy and GO-world; AIB's Hub developments; role and use of the Hub
The growth in production, use and trade of green energy has been huge during the last few years; and so has the exchange of certificates.
In order to further facilitate the international exchange between of EECS energy certificates, the AIB operates an inter-registry telecommunications Hub. The Hub is used to enable and control the transfer of EECS certificates, and to report on such activity. The Hub was initially set up for a relatively small number of members, each of which operated a certificate ‘registry’. Recently, further members have applied and members have exchanged increasing numbers of certificates with higher frequency of transfer. To be able to cope with future developments, the Hub needs to be updated.
AIB's intentions.
AIB's intentions with the Hub and internal requirements.
The technical quality of the Hub source code may need to be improved. There is also a strong need for functional improvement. However, AIB only intends to apply such amendments once the quality of the code providing the current functionality has been assured.
The Hub: status and a short analysis.
The Hub has been operational now since 2011, and communicates over the Internet with several registries (https). The source code of the Hub is written in several languages. It is not known whether this introduces any operational risks or will hamper future development of the source code; so clean up and restructuring might be required.
An Oracle database management system (DBMS) is used. The version of Oracle is not up-to-date and must either be renewed; or the DBMS itself must be replaced with something other than Oracle.
The Hub is hosted in Europe by the original developer and current maintainer of the software. An upgrade of the environment will be necessary within the next 2 years.
Upgrade or renew the HUB?
AIB prepares for the future. For now the aim is to improve just technical quality, capability, sustainability, security and flexibility to adapt the Hub for more functionalities. An extensive Moscow-list ('Must, Should, Could and Would') is available containing both present and required functionalities. However, the aim of the upgrade or renewal is not to introduce new functionality, but to maintain present functionality for now.
Invited suppliers are required to advise on the ITT options and consequences for both upgrading and renewal. The source code will be made available to suppliers for analysis, in order that they may identify and suggest options.
It is important to AIB that technical security levels are maintained and, where advisable, improved. Both code and hosting must comply with OWASP top ten criteria, and pass the penetration test.
AIB's policy on cooperation with suppliers.
While its members are large transmission system operators, regulators and power exchanges etc., AIB itself is a small international organisation, with only a small (non-technical) office support department. There is no dedicated IT department present within AIB (although it can, of course, draw on the resources of its members to a limited extent). Members of AIB include energy regulators, TSO's and power exchanges.
AIB has therefore outsourced first-line support to a third party, and requires suppliers to take the role of an outsourced IT department, providing high-level services in an effective and efficient way, in liaison with the front-line support organisation. To be able to achieve the desired level of support, a long-term relationship with supplier is required.
The supplier is required to carefully and accurately assess AIB's needs. Services are to be provided efficiently and effectively.
It is AIB's intention to develop, extend and enhance the Hub functionality as well. AIB will require a distinct consulting role from the supplier, providing sound advice.
Suppliers may take a combined role of developer, maintainer and host; or they may tender for individual roles.
Relevant links.
For further information on EECS-rules, please visit:
http://www.aib-net.org/portal/page/portal/AIB_HOME/EECS/EECS_Rules
For further information on AIB's Articles of Association, please visit:
http://www.aib-net.org/portal/page/portal/AIB_HOME/AIB/Governance