Modules 10, 11, 12 (maybe in others too): the code includes notes directly taken from e­mails. I guess this kind of background information, assumptions, etc. could be
placed as part of the written content that one can access through the different links in the ‘Source’ column. The people communicating this information, e.g. George Ekama, should have a reference somewhere (who he is, his position and where).

Add warnings:

fSus (raw: 0% to 10%. with primary settler: 0% to 15%)
fSup (raw: 8% to 25%. with primary settler: 0% to 10%)
difference_NOr_NOx (in denitrification) < 5%

About the construction materials, the user could be given some advice on what to do if the WWTP is larger than 21000 m3/day. In the report the Girona WWTP data are described for large plants, but it does not seem to have been implemented?

Done in the tool only but not in ecospold

According to the report, the Warning sign in the wastewater composition is expected to re­ calculate if you change some of the parameters like COD, etc. However, this did not work when I tried.

Overall it is visible, you did lot of work. But the user friendliness is still missing. Consider, that people have to be able to use the tool without any class or introduction from us. The user needs to always understand what is she/he looking at and what should she/he do.

Home page: I would really recommend to include an introduction page, where you describe (in as simple and clear way as possible) what the tool is and what it does and how it can be used. Describe also the individual steps of the procedure: 1) Simplified data entry; the first step of creating a dataset on treatment of wastewater is to enter the composition of the wastewater which should be treated …. The home page should also include link to the report in a very visible way. At this point if you access the tool you simple do not know what to do.

I can see, that you included a lot of instructions in the report. It would be good to consider incorporating some of it directly in the tool.

Please consider renaming the “Web parts”. I would expect something like “Steps of dataset generation”.

Please include clear explanation for every step of the dataset generation process. For example when the user enters the Multiple plant simulation site … what is it? What does it do? What is the user expected to do? Consider including short paragraph with explanation.

Please include somewhere a mention on what to do with the ecoSpold2 file …. that the ecoSpold2 file is actually xml format of a file and it can be either opened in the ecoeditor, worked on using Python or imported into excel.

Modules implemented; again here you have to be very clear on what does this part represent. You should clearly say, that this is an additional information the user can have a look at, but does not have to if she/he wants to simply generate a dataset. It is great, that even the links to the specific parts of the code are available, but it should be very clear what is this information for.

I assume, that you will remove some things at the end, which are present in the tool at the moment. For example the “See all TO DO items”.

Other things; will this part stay as it is also for the users? It seems to me some of these things could be included in the “Modules implemented”. Fractionation is, for example, in both places.

Other things; Documents section does not work at the moment.

On the IT side of things; is there some documentation on the web tool architecture?

Issue from April 20 2018

A new input "NOx" (g/m3) with default value as "0 g/m3" could be included.

NOx is a calculated variable, but it is possible in some cases that there is NOx in the influent

USE THIS TEXT

The generated datasets are in the ecoSpold2 format (.xml). This type of files can be either opened in the ecoEditor (freeware published by ecoinvent), imported into MS Excel, imported into LCA software tools which support import of ecoSpold2 format, opened using XML editor or processed using different types of programming languages (e.g. Python).

AND NO LONGER THIS TEXT

The ecoSpold file(s) can be downloaded. To submit the datasets to ecoinvent:
Make sure you have installed the ecoEditor freeware and created an account (Menu → Extras → Account management → Register data provider account)
Open the ecoSpold2 files in the ecoEditor.
Manually revise the datasets to make sure the fields are correctly filled out. A list of fields to be especially attentive to is given in the methodological report, section 8.3.
Use ecoEditor to "validate" the datasets (Menu → File → Validate). This will carry out mass balances and make sure all expected fields are filled out.
Submit the datasets for an external validation (Menu → File → Submit Datasets for Validation). Routines on the ecoinvent server will ensure that the dataset can indeed "fit" in the database.
Once successful with the previous steps, the datasets can be submitted for review (Menu → File → Submit Datasets for Review). Editors from the ecoinvent editorial board will then review the datasets to make sure they are ok for submission.

Note that if the wastewater treatment datasets were generated in order to have treatment datasets for some other activity, the wastewater treatment datasets should be submitted at the same time or before the other activity, but not after.

influent, effluent calculations and C balance

TBD

USE THIS TEXT
The main purpose of the ecoinvent wastewater treatment tool is to generate datasets representing treatment of wastewater with specific composition using specific type of treatment. For more detailed information on the type of methodology used behind this tool, please see the Methodological Report (see the link below).

This tool has been developed within the SRI project and is accessible for free to everybody.

Depending on the context, datasets are generated for the treatment of the wastewater in wastewater treatment plants (WWTP) and for wastewater that is directly discharged to the environment. For the treated fraction, the tool calculates the life cycle inventory of a WWTP (or a set of WWTP) with and without the input of the wastewater for which the datasets are generated, and bases the wastewater-specific life cycle inventory on the difference between the two simulations.

The steps for using the tool are:
1) Data entry: Enter information about the wastewater of interest: the nature and location of its source, its contamination levels, etc.
2) Calculation dashboard: Enter or modify the data on the wastewater treatment plants where the wastewater is being treated. The tool will calculate life cycle inventories for the WWTP operating with and without the input of the wastewater.
3) Generate datasets: The model outputs are converted into datasets, downloadable in ecoSpold2 format.

** AND NO LONGER THIS TEXT**
The ecoinvent wastewater tool was developed to generate ecoinvent-compliant datasets for wastewater that is discharged to the sewer system. It is useful both for data providers that need to supply datasets on the fate of wastewater from the activity they are submitting data for, and for LCA modellers specifically interested in wastewater treatment.

Depending on the context, datasets are generated for the treatment of the wastewater in wastewater treatment plants (WWTP) and for wastewater that is directly discharged to the environment. For the treated fraction, the tool calculates the life cycle inventory of a WWTP (or a set of WWTP) with and without the input of the wastewater for which the datasets are generated, and bases the wastewater-specific life cycle inventory on the difference between the two simulations.

The steps for using the tool are:
Data entry: Enter information about the wastewater of interest: the nature and location of its source, its contamination levels, etc.
Calculation dashboard: Enter or modify the data on the wastewater treatment plants where the wastewater is being treated. The tool will calculate life cycle inventories for the WWTP operating with and without the input of the wastewater.
Generate datasets: The model outputs are converted into datasets, downloadable in ecoSpold format.

The datasets can then be submitted to ecoinvent for inclusion in the database. To do so, the ecoSpold files should be opened in the ecoEditor, checked, and then submitted directly via the ecoEditor.

It is a formula that depends only on the flowrate (Q)

For example: in Complete-Mix AS for BOD removal with Nitrification

The simulation gives an estimate of dewatering polymer under ‘Chemicals (5)’, but I haven’t seen any background information or code for this calculation?

The section ‘4. Ecospold output file generation’, which output is this feature using in order to generate the spold file, if I have been calculating LCIs in both multiple plant model and single plant model?

The ‘Simplified data entry’: is this menu useful for both simulations of single plants and multiple plants? In point 6 it looks like it is only relevant for multiple plant simulation. The user should be given instructions.

https://prqv.vps.infomaniak.com/ecoinvent/docs/gabor-doka-tool/

I created spold files and successfully imported them to Ecoeditor. While using the model the user is not warned of the direct discharge data set that is created together with the one for treatment. This is a bit strange unless you have read the manual where this is explained. I think the tool should inform of this as well.

iSS composition can be calculated as O+Si+Al+Fe+Ca+Na+K+Mg.

the percentages are in 'sludge_composition.js'

George provided this info April 16 2018

1. The section ‘Documents’ seems to have a broken link.

2. In the section ‘Fractionation’, the footnote “Note: Implementing it here separately will make it easier later to integrate with the rest of the code”. Is this a note for the user? If I was a user I would not know what to make of it.

3. Section ‘Influent default data by country’: not clear what this information is. Does the user need to modify these data?

4. ‘Summary of terms’: I miss other abbreviations such as RAS, OTR... also, since the list is long, it could be ordered in alphabetical order.

5. ‘BOD removal (simple example) M&EA 4th (p. 707)’: why is this example here. Isn’t this the same example shown in ‘Modules implemented’, in modules 1, 2, etc.?