Field, tunnel, house, row, or gutter
Use the physical unit where work is assigned and results are measured.
Gros.farm for berry production
One production system for every berry crop cycle
Run berries in the field, tunnels, greenhouses, substrate systems, or indoor facilities without losing the differences between them. Connect varieties, crop stages, recurring work, harvest waves, quality, and the actual production environment.
01
Varieties and planting lots
02
Field, tunnel, and protected systems
03
Repeated harvest waves
04
Yield and quality by cycle
Production format matters
The same berry crop behaves differently in each system
A tunnel, greenhouse gutter, open-field row, and indoor rack have different operating units and environmental context. The farm registry should reflect the real production layout.
Variety, source, density, and date
Keep lot and establishment data with the active crop cycle.
Stage, observations, and crop load
Follow flowering, fruit development, picking waves, and plant condition.
Output and quality by wave
Compare harvest waves within the same crop and production format.
Farm registry
Model the operation before you measure it
Keep facilities, production areas, active crops or lots, and growing cycles in one structure. The registry gives tasks, observations, metrics, and analytics a shared place and production context.
Explore the farm registry
Berry crop stages
Follow development from establishment to the final picking wave
Configure the stages for the crop type, planting material, production system, and farm practice. Keep target ranges and work tied to the active stage.
- 01
Establish
Record plants, source lot, density, location, and actual planting date.
- 02
Develop
Track plant growth, canopy work, rooting, and recurring care.
- 03
Flower
Follow flowering progression, pollination context, and crop observations.
- 04
Set fruit
Record fruit development, load, irrigation, and protection work.
- 05
Harvest waves
Coordinate picking, labor, output, and quality across repeated dates.
- 06
Close cycle
Review the complete result before archiving or renewing the crop cycle.
Cultivation plans
The farm’s production standard—adapted to the real site
A cultivation plan can hold stages, target ranges, recurring work, recipes, photoperiod, and other production parameters. Templates are starting points, not universal recommendations: review every plan for the crop, facility, equipment, and production objective.
Explore digital crop plansDaily berry operations
Keep crop work specific to the row, variety, and stage
Scouting, pruning, runner removal, irrigation checks, protection, picking, and grading should carry the exact place and crop context.
Record plant and fruit observations
Use photos, comments, manual values, and connected climate data where available.
Plan labor around picking readiness
Assign the correct production area, expected window, and handling instruction.
Keep grade with the harvest wave
Separate total output from marketable quality and rejected product.
Turn an observation into a task
Keep the issue, assignee, deadline, and completion status in the crop history.
Work stays connected to production
Tasks carry the facility, growing cycle, cultivation-plan stage, date, priority, instruction, and assignee—not just a title and deadline.
Explore tasks and team →Monitoring and crop observations
Keep the biological event beside the operating data
Add manual observations, key dates, photos, comments, and available automatic or calculated values to the active growing cycle. A shorter, consistently updated monitoring set is more useful than a large table the team cannot maintain.
Production analytics
Compare varieties, cycles, and formats at the right grain
Do not combine tunnel, field, and greenhouse results without their context. Use comparable production units, cycles, and harvest definitions.
Flowering and harvest dates
Compare stage timing by variety and production format.
Yield by wave and cycle
Review both the curve and the total result.
Marketable share and grade
Keep quality categories consistent across the comparison.
Clear control boundary
Production management above reliable local automation
Gros.farm does not replace PLCs, controllers, SCADA, or local safety scenarios. The local layer remains responsible for physical operation and safe autonomous control.
Operate and protect equipment
Pumps, valves, ventilation, lighting, dosing, interlocks, and emergency scenarios.
Connect the crop plan and result
Stages, targets, schedules, tasks, data history, analytics, and supported configuration exchange.
Fit the production model
Adapt Gros.farm to the growing system
The platform remains shared, while the registry, stages, tasks, and metrics follow the actual production environment.
Rows and seasonal plantings
Weather windows, field work, protection, repeated harvest, and quality.
Protected berry production
Crop stages, climate context, irrigation, crop work, and picking waves.
Gutters, racks, and controlled cycles
Batches, recipes, pH and EC context, lighting where relevant, and output.
GFAi with farm context
Compare berry cycles with the production format attached
GFAi can help find gaps and comparable histories, but a detected association is not proof that one factor caused a crop result.
It does not replace the grower, agronomist, technologist, or controls engineer responsible for the decision.
Questions to investigate
- Which harvest waves had the highest marketable share for this variety?
- How did stage timing differ between tunnel and open-field cycles?
- What observations are missing before we compare irrigation changes?
Start with one working production contour
Prove the daily workflow before scaling the farm
You do not need to digitize every site, crop, and integration at once. Start with one active cycle that the team can keep current.
- 01
Add one production area
Choose a field block, tunnel, greenhouse zone, or substrate row.
- 02
Add the active berry cycle
Record variety, plant source, stage, and the next recurring operations.
- 03
Follow one harvest wave
Assign work and record timing, output, quality, and observations.
Related production systems
Explore another sector
Protected cultivationGreenhouse farms
Connect crop stages, climate targets, irrigation, crop work, observations, and harvest results by greenhouse block.
Open-field productionOpen-field vegetables
Coordinate fields, crop plans, weather-sensitive work, crop protection records, harvest waves, and field results.
Perennial cropsOrchards and vineyards
Keep blocks, rows, varieties, phenology, scouting, crop protection, irrigation work, yield, and quality in one perennial history.
Propagation and planting materialPlant nurseries
Track plant lots, provenance, locations, transplants, recurring care, grading, losses, and readiness for sale or transfer.
Questions before setup
What to know about this sector solution
Can Gros.farm handle both open-field and protected berries?
Yes. Use separate production areas and cycles so each format keeps its own structure, stage logic, observations, and results.
Can we track several harvest waves?
Yes. Harvest dates, output, and quality can be recorded across the active cycle and reviewed with other production events.
Do we need sensors to begin?
No. The registry, cultivation plan, tasks, manual observations, and harvest records can be used first. Add data sources later when they support a defined decision.
Does the system recommend a universal berry recipe?
No. Plans and target ranges must be adapted to the crop, variety, planting material, production format, equipment, and farm practice.
Field, tunnel, greenhouse, or indoor
Build one connected production history
Manage berry varieties, crop cycles, harvest waves, quality, tasks, and observations across different production formats.