Solution Definition Document

Hey @h.niesing,

Could you have a look at the process we’ve formulated before, we think step 1 and 2 are only applicable for ‘Challenge working groups’ while solutions should go through the whole process. I think the document you’ve made needs to be the answer to all the points in ’3 Definition’, and step 3 is making your document together, of the process:

http://score.partners/process/3-definition.html

Thanks,

Boris

Linking to the input we promised here

Following are the elements we think are to be added to the ‘work plans’. We believe these would improve forming a picture and decision making for partners.

Challenge + solutions working groups

• Role/kind of intended contribution of each partner org: code / replication / just feedback / just passive following
• Members of working group: the actual persons, each committing to contribute to the work of the working group
  • Name
  • Organisation
  • Function in organisation
  • Role in working group (esp. external, ‘non-SCORE’ people invited to working group)
• Is Bax leading the working group (we think this is a good way to quickly set up working groups in kickstart mode) or has the lead been handed over by one of the partners?

Just solution working groups

• If existing solution: pre-analysis of solution
  • Title
  • What does it do?
  • Where is the live demo?
  • To what extent is it now modular? Which components are reusable? Which are not, or only available by buying license/buying from supplier/etc.?
  • Where is the code? Is it publicy open source? Is it based on public open source but not public? If it’s not open source, under which open license will it be shared in SCORE?
  • Which open data does it use? Which formats? Does it ingest open data? Does it generate open data? If not at the moment, how does the SCORE version of it will ingest/generate open data?
• If new solution: same questions about how it is intended to be
• Current backlog, general outline (especially roadmap items that are linked to the earlier questions on modularity, open source, open data)
• Part(s) of that backlog that the leading city aims to co-develop in SCORE
• Open source health (current health, intended health boost thanks to SCORE)

An example by @pjppauwels

1. Check je huis
2. An interactive form and visual webtool to get more insights in the state of your house, what you can do to improve it and an overview on what grants are there to help you financially.
3. You can find a Dutch version on https://klimaat.stad.gent/checkjehuis/?q=check-je-huis
4. It isn’t modular, it’s a plug n play web application based on Symfony 2.8 using a fixed data set, but I does have a few plugins. It for example links to our solar and roof maps that are in fact different applications. The data used is static, but localised so you would need to have your own data to have relevant output.
5. Code on: https://github.com/StadGent/Check-Je-Huis under an GPL3 license.
6. It uses open data from Eandis, the energy company to generate averages for people that don’t know their exact usage and grant data from both the city as well as 3rd party organisations. The results are not send back to the environment agency, so it does not generate data (yet).