Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Adjust TEKSI water datamodel and project file to fit SIA 405 #324

Open
2 of 4 tasks
cymed opened this issue Jan 9, 2023 · 0 comments
Open
2 of 4 tasks
Assignees

Comments

@cymed
Copy link
Collaborator

cymed commented Jan 9, 2023

General information

Qwat builds it's datamodel on the SIRE model of the canton of Vaud. Its use is therefore limited to infrastructure managers who either need to serve a SIRE gateway or no specific gateway. Users who need to serve the Swiss Standard SIA 405 are therefore hesitant to migrate to Qwat.

Applicant:  Cyril Meder-Graf (Waldburger Ingenieure AG)
Developers: to be defined - different skills needed - maybe cooperation work needed
User group referent: ?
Developments referent: ?
Project Manager: to be defined

Users and administrators needs

  • Qwat users should be able to work with the release 2015 of the SIA datamodels. Cantons and municipalities have started to require release 2015 for new projects and GWP (PGDE) management.
  • Qwat should be able to migrate their existing projects from the current datamodel to the new datamodel based on releases 2015 of the SIA
  • Qwat should be accessible in german

Description of users and administrators feature requirements

  • Qwat should be compatible with SIA405 Water (excluding the bug of hydraulic node and hydraulic strand)
  • The current plugin functionalities should continue to work
  • A valid EPANET Export should still be possible
  • A migration path from the current datamodel should be defined and implemented including QWat and possible user extensions
  • a gateway to SIRE and to SIA405 should be provided

Specific requirements

As there are significant changes to the database structure, it is advisable to define phases:

  1. Adapt database structure to fit SIA405 requirements. In this step, the basic structure should be streamlined with the QGEP conceptual structure
  2. Configure SIA405 import/export and SIRE import/export
  3. Adapt existing Plugins to serve new DB structure
  4. Create gateway for automatic update
  5. Update QGIS model file

Feasibility study

Feasibility, options, alternatives and technical specificities

Risks and constraints

The Norm 405 is currently being overhauled.

Mutualisation

Linked to #741 qgep, #358 qwat_datamodel, #22 TEKSI

Specification and offers ( Developer )

Not shared on Github.

Specifications

Tenders

Not shared on Github.

Timeline / deadlines

Add a detailed timeline

  • 2022: Inclusion in strategic assessment of board

  • 09.01.2023 : First draft in Issues

  • first half 2023 : Validation of User Group

  • Warranty period : to be adressed

Related softwares versions

  • QGIS version: 3.x
  • Database model version:
  • INTERLIS Model version: SIA405_WASSER_2015_LV95

Public issues links :

Helpdesk issues links :

Realisation dates

  • Tender reception date :
  • Tender validation date :

Documentation

Documentation links

  • User manual :
  • Administrator manual :

Development and integration

Link and comments from the developer about the product

  • Deliverable :
  • Recommendations and comments :
  • Future prospects :

Conclusion

Conclusions from applicant, users or admins group

  • Conclusion:
  • Future prospects:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants