Platform
Four products on the same database. Each can be contracted on its own. Together, they use the same information and do not repeat work.
One database, four products
The database brings together, read-only, the systems the operation already uses and the Agnaris Campo records, and checks the data every day. Clima, Perdas and Fornecedor work on top of it. Whoever starts with one product reuses the database in the next.
Agnaris Clima
Rain and calendar turned into operating decisions.
On which days will the rain stop the field, and what should be done before it?
Who it is forSugar mills, fruit farms, dairies and growers who plan cutting, harvest, planting or irrigation around rain.
- History
Before recommending anything, we look at the rain from your rain gauges in previous seasons and the days on which the operation stopped.
- Forecast
Every day, the weather forecast goes into the model and becomes days of stopped operation by farm or front, over the next 7 days.
- Recommendation
Whoever makes the call receives what to do before the rain: where to bring forward cutting or harvest, how much cane to keep available, when to schedule maintenance.
- Data used
- Rain gauges and weather stations of the operation
- Numerical weather forecasts
- Stoppage and production history
- Soil and terrain of each farm
- Deliverables
- Days of stopped operation by farm or front, over the next 7 days
- What to bring forward, hold back or schedule before the rain
| Farm | Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|---|
| Farm 03Hillside, front 1 | 1 | 4 | 19 | 27 | 9 | 2 | 0 |
| Farm 07Floodplain, front 2 | 1 | 5 | 22 | 30 | 12 | 4 | 1 |
| Farm 11Hillside, front 1 | 0 | 3 | 15 | 24 | 8 | 2 | 0 |
| Farm 12Tableland, front 3 | 0 | 2 | 9 | 18 | 5 | 1 | 0 |
| Farm 14Tableland, front 3 | 0 | 2 | 8 | 16 | 4 | 1 | 0 |
- Forecast days with cutting stopped
- 2
- Recommended available cane
- 20 h of crushing
- Suggested cutting order
- Farm 14, 12, 03
Agnaris Perdas
Where the operation loses raw material and sugar, from the field to the plant.
How much is lost between the field and the plant, at what stage and why?
Who it is forPlants that receive raw material from many fronts, lots or routes and need to know where and why they lose quality and product.
- Record
Each load, lot or collection is linked to its area of origin, the time of burning or harvest, transport and arrival.
- Balance
Weighbridge, laboratory and plant bulletin close the account by stage and shift, separating known loss from unaccounted loss.
- Alert
When a front goes past the time limit, a lot loses its grade or a meter stops balancing, the team is notified in the same shift.
- Data used
- Burning, harvest and transport records
- Weighbridge and laboratory
- Plant bulletin and systems
- Map of the source areas
- Deliverables
- Time and quality loss by front, lot or route
- Balance by stage and shift, with the unaccounted loss
- Meters out of calibration and calculated values where there is no measurement
| Load | Farm | Burning | Weighbridge | Time | ATR |
|---|---|---|---|---|---|
| 4471 | Farm 14 | Tue 14:10 | Wed 09:42 | 19 h 32 | 136.8 |
| 4472 | Farm 14 | Tue 14:10 | Wed 10:05 | 19 h 55 | 137.2 |
| 4473 | Farm 09 | Mon 20:30 | Wed 10:48 | 38 h 18 | 131.4 |
| 4474 | Farm 12 | Tue 16:40 | Wed 11:02 | 18 h 22 | 135.9 |
| 4475 | Farm 09 | Mon 20:30 | Wed 11:31 | 39 h 01 | 130.7 |
Front 2 (farm 09): loads more than 36 h past burning. ATR 4% below the other fronts.
Agnaris Campo
Field records on the phone, with or without internet.
What happened on each front today, and at what time?
Who it is forOperations where the weighbridge only records weight, the rain stays in a notebook and the time of burning, harvest or collection never reaches anyone.
- Setup
Farms, fronts, lots, routes and trucks are entered once. Each role sees only what it records.
- Record
In the field, two taps record the burning, cutting, harvest, collection or rain gauge reading, with time and place, even without signal.
- Use
The records reach the database when the signal returns and start feeding the weighbridge, Clima and Perdas.
- Data used
- Field team phones, with or without signal
- List of farms, fronts and blocks
- Rain gauges and trucks of the operation
- Cutting, harvest or collection orders
- Deliverables
- Burning, cutting, harvest and loading with time and place
- Rain gauge readings on the same day
- Data ready for Clima and Perdas
- 07:05 Rain gauge at farm 14: 0 mmSupervisor, front 1 Sent
- 07:12 Rain gauge at farm 2: 18 mmSupervisor, front 2 Sent
- 09:40 Loading at farm 14, front 1Driver, truck 12 Sent
- 13:55 Cutting started in block 21Supervisor, front 3 Waiting for signal
- 14:10 Burning of block 14Supervisor, front 2 Sent
- Records today
- 146
- Waiting for signal
- 1
- Rain gauges read
- 9 of 10
Agnaris Fornecedor
Payment for quality checked load by load.
Does what was paid to each supplier match the weight and quality of what they delivered?
Who it is forGrowers' associations, cooperatives and plants that pay for quality and want an account both sides can check.
- Rules
We register the payment rules in force, such as Consecana, the dairy's table or the packing house's, and the history of each area.
- Checking
Each load, collection or lot is checked: weight, analysis, deductions and amount paid. Anything outside the history is flagged.
- Statement
Each supplier receives a statement with the reason for every amount, and the association follows the flagged analyses.
- Data used
- Weight and analysis of each load or collection
- Payment rules: Consecana, the dairy's or the packing house's table
- Register of suppliers and areas
- Production costs by region
- Deliverables
- Payment checked load by load
- Out-of-range analyses flagged for follow-up
- Simulation of the amount to be received and comparison with cost
| Load | Supplier | Weight | ATR | History | Status |
|---|---|---|---|---|---|
| 8812 | 0398 | 31.2 t | 132.4 | 128 to 136 | Within history |
| 8815 | 0412 | 29.8 t | 112.0 | 126 to 135 | Outside the range |
| 8817 | 0155 | 30.5 t | 129.8 | 125 to 133 | Within history |
| 8820 | 0412 | 30.1 t | 114.6 | 126 to 135 | Outside the range |
| 8824 | 0230 | 28.9 t | 134.1 | 129 to 137 | Within history |
Supplier 0412: 2 analyses below the area's history, with 4 mm of rain in the week. Watch the next sample.
What you need to get started
- History
At least one season of data: crushing or production, stoppages and, if available, rain and quality. A spreadsheet is fine.
- Access
Exports or read access to the systems that hold this data. We change nothing in them.
- One person
Someone from the operation who knows the data and can answer the technical team's questions a few hours a week.
Frequently asked questions
Do I need to replace the systems I already use?
No. Agnaris reads data from the existing systems and works alongside them.
Do I need to install sensors?
Not to start. The diagnostic uses the data the operation already records. If the analysis shows a measurement is missing, we say which one and where.
Does the data stay mine?
Yes. The contract defines where it is stored, who has access and what happens to it when the contract ends, in line with the LGPD (Brazil's General Data Protection Law).
How long until the first deliverable?
The diagnostic with your data takes 4 to 6 weeks, depending on the volume and organization of the information.
How is it priced?
The diagnostic has a fixed price, set by the size of the operation, and is covered by a confidentiality agreement. The implementation proposal comes after it, with the estimated gain and the assumptions used; the price depends on the size of the operation and the products contracted.
Talk to the team
Tell us what your operation produces and what data it already has. The first conversation is with the technical team.