Maintain the Field Plan
A warehouse, block, nave or bed, should never get deleted, only been modified. The structure of a warehouse, barely every changes. That means, the first creation of the warehouse, block, nave, and beds, stays always in the database. What needs to be maintained, is the content of the beds. The variety changes, and the production status changes. We recommend to NEVER delete a bed, but to always modify the data.
Bed Cycle, renovation management
Each bed has its modification over time. A variety (with its amount of plants and m2) gets replaced for the same, or another variety. We recommend to create a variety called VACIO and ROOTSTOCKS (Natal Briar), to know exactly how long a bed was empty, and to assign yearly field cost only to variety when it was actually in the field. A replacement cycle should be managed as follows.
![](https://manual.unosofbooks.com/~gitbook/image?url=https%3A%2F%2F4099088335-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FBi3aNCeQ0YEBUj1LmkHR%252Fuploads%252F6Vc2zIDkqbfOQctwISEz%252FScreen%2520Shot%25202023-01-09%2520at%252009.06.44.png%3Falt%3Dmedia%26token%3D154bef2f-8a71-4cd2-b5e0-800f8e476517&width=768&dpr=4&quality=100&sign=e13c679c&sv=1)
Modify vs Deleting a Bed
The wrong way to manage a field-plan, is to delete beds and create new one's. That causes that no history data can be related to each-other of a bed. To make this more visible, check out this picture:
![](https://manual.unosofbooks.com/~gitbook/image?url=https%3A%2F%2F4099088335-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FBi3aNCeQ0YEBUj1LmkHR%252Fuploads%252FcfeF0ktiK4joqDnnvfpB%252FScreen%2520Shot%25202023-01-09%2520at%252009.41.09.png%3Falt%3Dmedia%26token%3D177a59db-9531-4533-9664-8e0f1f65ade6&width=768&dpr=4&quality=100&sign=92b5ded7&sv=1)
How can we know, what happened to bed ID 1010,... if that got deleted?
The right way to manage this, is to always modify a bed, to get a related history result that we can report well. To make that more visible, check out this picture:
![](https://manual.unosofbooks.com/~gitbook/image?url=https%3A%2F%2F4099088335-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FBi3aNCeQ0YEBUj1LmkHR%252Fuploads%252FOR2mdCXjeh8KNzNzAuw4%252FScreen%2520Shot%25202023-01-09%2520at%252009.46.34.png%3Falt%3Dmedia%26token%3D6e2d6fcf-dfe8-499d-aab2-7f9e9e104154&width=768&dpr=4&quality=100&sign=2a19badf&sv=1)
Snapshots, Timeframe Calculation of m2 and #plants x variety x block.
UNOSOF is set up to make weekly, every Sunday, a snapshot of the field-plan. A snapshot is like taking a picture of the farm, how many plants, m2 per variety, per block, etc. were there at that given timeframe. With those snapshots, we can calculate the productivity of a variety over a timeframe when the variety truly existed in the field with its m2 and #plants.
If a modification happens in the field- before the automatic snapshot, it's possible to manually add a snapshot after the modification took place. That manual snapshot makes sure that the productivity corresponds with the timeframe of the number of plants and m2 that has been assigned to the variety.
How to take a Snapshot
Load the filed plan using as many filters as possible. Then, click on the Create Snapshot green button.
![](https://manual.unosofbooks.com/~gitbook/image?url=https%3A%2F%2F4099088335-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FBi3aNCeQ0YEBUj1LmkHR%252Fuploads%252FuwAQBanb6nu9KDz4maps%252Fimage.png%3Falt%3Dmedia%26token%3De994e302-840e-419d-9e68-bb79b457f4b8&width=768&dpr=4&quality=100&sign=3034950c&sv=1)
Choose the date of the snapshot and press Save.
![](https://manual.unosofbooks.com/~gitbook/image?url=https%3A%2F%2F4099088335-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FBi3aNCeQ0YEBUj1LmkHR%252Fuploads%252FSTVYVlXpW0DU33x91Rcc%252FScreenshot%25202023-03-13%2520at%252012.39.39.png%3Falt%3Dmedia%26token%3Dc2b0b140-d020-4d03-abf4-a921211e8140&width=768&dpr=4&quality=100&sign=9bd826aa&sv=1)
If the snapshot is taken correctly, the message Success! will pop up on the right botton side of the page.
![](https://manual.unosofbooks.com/~gitbook/image?url=https%3A%2F%2F4099088335-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FBi3aNCeQ0YEBUj1LmkHR%252Fuploads%252FgsdSPMZvrTVLhMWushL2%252FScreenshot%25202023-03-13%2520at%252012.43.19.png%3Falt%3Dmedia%26token%3D9ea3e89e-c871-464e-baa0-f3baf2c379d5&width=768&dpr=4&quality=100&sign=7e66a34&sv=1)
Refresh the page to check the just-created snapshot on the filter History. This filter displays all snapshots taken since the setup of the system.
![](https://manual.unosofbooks.com/~gitbook/image?url=https%3A%2F%2F4099088335-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FBi3aNCeQ0YEBUj1LmkHR%252Fuploads%252FEUkgCCRDmGAZaQbpIajp%252Fimage.png%3Falt%3Dmedia%26token%3Dba74bcdd-a5a8-41c6-91e2-53d462a5e570&width=768&dpr=4&quality=100&sign=9de4037e&sv=1)
Report snapshots
Go go: Warehouse reports, and select Accounting M2 Report. Please select a time frame and data selection (farm, block etc) you wish to report.
![](https://manual.unosofbooks.com/~gitbook/image?url=https%3A%2F%2F4099088335-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FBi3aNCeQ0YEBUj1LmkHR%252Fuploads%252FeJ6iUbfbmH2StZhcNRGb%252FScreen%2520Shot%25202023-01-09%2520at%252010.23.52.png%3Falt%3Dmedia%26token%3De98c40dc-9df6-494a-ab44-cb9acf449579&width=768&dpr=4&quality=100&sign=7eef67c&sv=1)
It's a very nice overview that indicates where and when the changes have been made over time. It's possible to edit history data and review them in this report. As said in the beginning, the size of a block, beds, etc. does not change. So any modification should always result in the same amount of m2 total.
Last updated