Model-Driven App purpose-built for Norwegian aquaculture operations. Biological data management, regulatory compliance, and D365 write-back — in a single unified interface.
🖥 Open Application MockupClick a section to expand its pages and capabilities.
All biological data is owned by Dataverse. D365 financial/logistics data is accessed read-only via Virtual Entities.
Virtual Entities expose live D365 F&O data in AquaMonitor MDA without copying data to Dataverse. Read-only, always current.
| Flow ID | Flow Name | Trigger | Action |
|---|---|---|---|
| AQUA-FLOW-001 | Lice Reporting to BarentsWatch | Weekly lice count finalized in nha_licecount | HTTP POST to BarentsWatch Lusedata API |
| AQUA-FLOW-002 | Terapiregister Submission | Treatment Order status = Completed | POST to Mattilsynet Terapiregister API |
| AQUA-FLOW-003 | Harvest Declaration — Fiskeridirektoratet | Harvest Event finalized + certified | POST to Landings-og sluttseddel-register API |
| AQUA-FLOW-004 | Altinn Biomass Reporting | Monthly close (1st of month) | POST to Altinn bistand skjema via Maskinporten |
| AQUA-FLOW-005 | D365 Mortality Cost Posting | Daily mortality journal confirmed | D365 OData POST → InventJournalEntity |
| AQUA-FLOW-006 | D365 Feed Consumption Posting | IoT feed event batch (hourly) | D365 OData POST → InventJournalEntity |
| AQUA-FLOW-007 | Harvest PO Release | Harvest BPF Stage 6 — Regulatory Approved | D365 OData POST → ProdProductionOrderReleaseEntity |
| AQUA-FLOW-008 | BarentsWatch Zone Lice Alert | nha_licecount Adult Female > 0.5 | Teams alert + create nha_envalert + email Mattilsynet |
Every harvest must complete all 7 stages sequentially. Stage 3 performs an automated withdrawal-period check against nha_withdrawal. Stage 6 triggers the D365 Production Order release.
Explore which D365 modules are configured, how AKVA IoT feeds into the platform, and how Power BI analytics are embedded.