Consultancy for renewable energy in the built environment
Consultancy for renewable energy in the built environment Proposal for Solar Keymark database approach and IT services Gerard van Amerongen v. AConsult 1
Revision Solar Keymark database • Binding together 4 SCF projects: – 5 C 6. 1 DATABASE_SKI • Include ‘datasheet’ data and make accessible – 7 C 04 Label-DB • New Solar Keymark service: – make available Er. P relevant data – Add systems (partly) composed of SK certified components (e. g. Er. P) – 8 C 06. 1 Add-Value_v. AC • Make data accessible for product databases, design tools (third party access) – SCF 9 Database-fup • Extend 5 C 6. 1 DATABASE_SKI to systems, tanks and controls • Keep in mind the findings of SKN ‘management table’ 2
Implementation • Implement primary database structure – Copy datasheet data into new structure – Develop and implement the public database user interface – Develop and implement the data input structure certification bodies • Contact ‘third parties’ for access – Design ‘API’ for access – Draft agreements for access (for approval by SKN) – Implement • Implement secondary database element on Er. P data – Approval of SKN and promotion • Copy actions for systems and tanks (controls? ) 3
Solar Keymark database • Common approach of all projects – Aim at added value for the Solar Keymark clients – Define the database as the centre and surround with IT services • SKN managed and third party • Target groups – Business to business: • checking licenses • sharing product specifications (e. g. procurement) • Access for third party databases (e. g. product database) – Governmental organisations: • Check specifications for support schemes, Er. P surveillance – Installers composing Er. P packages 4
Solar Keymark database - IT infra-structure- Certiciation bodies: • • License holders: add by upload datasheet revise by upload revised datasheet • • add/revise Er. P system Download Er. P documentation Solar Keymark database General public: • Select SK product see specifications • Get Er. P data + product fiche License holders: • Link to relevant parts of database Third party access: • • • Product data site Design tools Package label tools 5
Collector Direct access through clients website link Database main structure - Public user interface List: license holders List: collector names Details: one collector Systems List: license holders List: system names Details: one system System Er. P List: brands M L List: solar devices Tank Control Details: Er. P data XL Qnonsol: Qaux ηcol Tank label 6 XXL
From Solar Keymark database Overlap SK system SK collector SK controller SK tank Sol. Cal Er. P entrance Er. P documentation Full set of Er. P data Composition from different sources Controller Tank Pump From system supplier: Full set of Er. P data - Qnonsol (4 x) & Qaux - ηcol + Tank label Er. P documentation - Technical document - Product fiche 7
Remarks on Er. P business • Full set of Er. P data can be made available only for: solar water heaters (SOLICS) – For SOLCAL and space (combi) heaters additional data is required • Proposed solution: – Enter new ‘class’ of systems, populated with (license holders) additional data (e. g. pumps, number of collectors, …) – Add (if needed) SOLCAL calculation • Not needed for DST tested systems and space heating purposes – Make Er. P data for packages available to the public and third party • E. g. enter Qnonsol / Qaux in VDI product database or Label. Pack. A+ • Skip Sol. Cal calculations! • Solar Keymark: only documentation (Er. P specifications) – For package composing: use Label. Pack. A+ or another likewise tool (VDI) 8
Management requirements database • Responsible for data integrity of database – Following the SKN internal regulations • Responsible for data input from certification bodies – Expertise required on Solar Keymark and standards – Goal: within 1 year of implementation new database structure: CB enter the data directly • Database manager supervises the process • Manage third party access – Propose agreements with third parties for access to database (for SKN) – Distribute API’s for that purpose • Helpdesk for CB input, public access and third party access • Keep database and user interfaces up to date – Formulate proposals for improvements (to the SKN) 9
Points to decide upon • Create a working group (volunteers? ) • Purpose of the public user interface – Check licences and read specifications, or – List products with performance data (facilitate: ‘pick the best’) • This means that Solar Keymark supports ‘ranking’ of certifified products • ‘All are good, but some are better’ • Data input options: – The database manager receives the datasheet and enters that in the database (current) – Certification bodies upload the full datasheet – Test laboratories enter the test data & certification bodies enter certification data • An SCF project aimed at the design of this user interface is required 10
For your attention 11
- Slides: 11