Potential application
What is growing where and how is each block or tree changing?
Living plantation record
Build a permissioned, date-stamped record of locations, observations, visits and harvest history for recurring review.
A proposed pilot workflow, not a customer result or evidence of a deployed combined system. Data availability, integrations and operating suitability must be confirmed.
Discuss a pilotConnected workflow
From observations to a reviewed decision.
- Map and reference
- Date the observations
- Connect the history
- Review changes
- 01
Establish locations and references
Agree block boundaries and mapping references, then a method for assigning and checking tree IDs. Persistent identity across visits is an AgriSense development direction, not a verified current capability.
- 02
Capture dated observations
Gather available imagery, field observations, sensor readings and soil-test results. Record collection dates, locations, methods and provenance so observations can be interpreted in context.
- 03
Connect visits and harvest history
Explore a living digital record in AgriSense 2.0 that brings visits, approved activity and harvest history into review. Data exchange, identity reconciliation and access controls must be agreed and verified for the pilot.
- 04
Review changes and gaps
Managers and agronomists compare records over time, identify missing or inconsistent observations and decide where another visit or test is needed.
Supported decisions
What people could decide.
- Where are crop locations or records incomplete?
- Which blocks or trees need a fresh observation?
- Which changes should an agronomist investigate?
Proposed measures
What a pilot should check.
- Location and ID consistency across visits
- Coverage, completeness and age of records
- Traceability of observations, tests and harvest history
- Ability to retrieve comparable dated records
Evidence needed to assess value
Use checked map references, dated source records and explicit missing-data flags. A record’s usefulness depends on its coverage, identity consistency and provenance, not merely the presence of a map.
Scope and limitations
A living digital record is the proposed application. A full predictive or simulation digital twin is a future possibility requiring further implementation and crop-specific validation, not a deployed claim.
AgriSense sensor connections, persistent tree identity, treatment-record integration and predictive support remain directions requiring implementation and field validation. Spectral indices support inspection; people approve treatment. LIBS is a separate concept, not an operational AgriSense input.