These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Weather Station / Advisory
- Data model and import order
The tables behind Weather Station / Advisory
Weather Station / Advisory ships with 10 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.
- Tables
- 10
- Features
- 6
- Change it
- Add fields and tables in Proto
How the model is organised
Farms and organizations:
Organizations, Farms, team members, Users. Organizations carry time zone and Currency; farms and team members belong to one organization and are Active Yes or No.
Field operations:
Field operations. Status runs Draft, Planned, Review, Authorized, Completed, or Cancelled, with a Revision on every change and an Owner from team members.
Weather observations:
Weather observations. Station, observed at, rainfall inches and alert threshold against a parent operation; Status runs Draft, Submitted, Approved, Rejected, Completed.
Professional review:
Review decisions. Decision Approve, Reject or Return with Reason, source revision and Reviewer.
Agronomy evidence and attachments:
Agronomy evidence, record attachments. Numbered evidence lines with unit, source and quality flag; files with Visibility Internal or Shared.
Operation receipts:
Operation receipts. Operation key, Action, expected revision and result state Pending, Completed, Failed or needs review.
Every table, by feature
- Farms and organizations4
- Field operations4
- Weather observations4
- Professional review3
- Agronomy evidence and attachments4
- Operation receipts2
- Organizations
Operating organizations that own farms, stations and field operations.
- Farms
Client farms and ranches receiving advisories and field operations.
Linked to Organizations - Team members
Staff membership linking an authenticated platform user to an organization and role.
Linked to Organizations, Users - Users
Users
Linked to Users
- Field operations
Planned and executed field work such as spray schedules and pest interventions.
Linked to Organizations, Team members, Farms - Farms
Client farms and ranches receiving advisories and field operations.
Linked to Organizations - Team members
Staff membership linking an authenticated platform user to an organization and role.
Linked to Organizations, Users - Organizations
Operating organizations that own farms, stations and field operations.
- Weather observations
Station weather readings and advisory revisions supporting a reviewed advisory.
Linked to Field operations, Organizations - Field operations
Planned and executed field work such as spray schedules and pest interventions.
Linked to Organizations, Team members, Farms - Agronomy evidence
Measured evidence lines captured against a field operation, with source and unit.
Linked to Field operations - Organizations
Operating organizations that own farms, stations and field operations.
- Review decisions
Independent professional review decisions recorded against a field operation revision.
Linked to Field operations, Team members - Field operations
Planned and executed field work such as spray schedules and pest interventions.
Linked to Organizations, Team members, Farms - Team members
Staff membership linking an authenticated platform user to an organization and role.
Linked to Organizations, Users
- Agronomy evidence
Measured evidence lines captured against a field operation, with source and unit.
Linked to Field operations - Record attachments
Files attached to a field operation with visibility and evidence type.
Linked to Field operations, Team members - Field operations
Planned and executed field work such as spray schedules and pest interventions.
Linked to Organizations, Team members, Farms - Team members
Staff membership linking an authenticated platform user to an organization and role.
Linked to Organizations, Users
- Operation receipts
Idempotent receipts for guarded workflow commands, with stable operation keys.
Linked to Field operations - Field operations
Planned and executed field work such as spray schedules and pest interventions.
Linked to Organizations, Team members, Farms
Keys and references
A farm and a team member each reference one organization; a team member also references one user. A field operation references its organization, its owner and the client farm in Counterparty. Weather observations, evidence lines, attachments, review decisions and receipts each reference one field operation as Parent. Review decisions and attachments also reference a team member as Reviewer or uploaded by.
Import farms by their Code and organizations by theirs, never by display name. Keep evidence line numbers and revisions as they were recorded. Keep each operation key unique.
Migration order
- Load Organizations with time zone and Currency, then Users.
- Load team members linked to their organization and user, then Farms with Code, contact, address and eligibility note.
- Load open field operations at Draft, Planned, Review or Authorized with their owner, farm and current Revision.
- Load agronomy evidence lines and record attachments for those operations, then open weather observations.
- Load review decisions for operations already in Review or Authorized, keeping source revision.
- Reconcile open operations and decisions with the source, test permissions and replay the exception cases before the next spray window.
Set up Weather Station / Advisory your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.