01
Canonical boundary
Services and UI work with normalized entities before serializing to FIWARE.
This avoids drift between profiles and makes parity tests practical.
Back home
FIWARE-native
NGSI-v2 first profile
uAgri Studio separates the canonical entity from FIWARE transport so Orion v2 and DEMO share verifiable behavior.
02
Subscriptions
Orion subscriptions feed temporal persistence when the profile supports it.
V2 compatibility is validated with reproducible gates.
03
Temporal stack
QuantumLeap and CrateDB remain an optional profile for historical series.
The UI does not depend on temporal data to render the dossier.
04
Remote-ready
Local and remote profiles are described from safe configuration.
Broker secrets are not exposed to the client.
FIWARE first
Orion retains useful state; heavy artifacts live elsewhere
Intelligence does not turn the Context Broker into a generic database. It publishes derived summaries, relationships and provenance; rasters, COGs and datasets stay in artifact storage.
01A/B/C
Digital Twin
Entities, relationships and temporal observations represent operational reality.
- AgriParcel and canonical geometry
- Operations, sensors and actual harvest
- Multitenant relationships with service path
02D/E
Analytics and external
Providers use fail-closed contracts and mandatory provenance.
- Summarised results and availability states
- Cache with freshness and dataset version
- COGs, tiles and scenes outside Orion
03F/G
Evidence and application
Reports are referenced; ephemeral UI state never pollutes FIWARE.
- Documents, hashes and references
- Plan versions and approved snapshots
- Filters, wizard and preferences as application state
Data flow
Provider → analysis → context
- 01Resolve parcel and CRS
- 02Query and validate provider
- 03Calculate with provenance
- 04Publish summary/relationship to FIWARE