Making and Delivery the Wine

With information from tank number 2, we wish to:

Explain how our wines are made, packaged, sold and shipped. We document how much wine we currently have, where our wines are currently stored, and in what conditions.
To do this, we create a didactic flowchart diagram which explains the processes of making, packaging, and shipping wines. This is similar to our "daily log" for grape growing, but with less emphasis on the temporal element of the process. In other words, we are more concerned with explaining and exposing the processes, and less interested in how these relate to the calendar year and the seasons, especially considering that some of the processes will continue over several years for each wine. For these reasons, we call this element of the project "The Flowchart" instead of "The Daily Log"
But to insure the traceability of our wines, we also incorporate a dashboard, allowing visitors to view the current state of our wines: how much wine do we have, where are the wines (in the tank, or in storage), and in what condition are they in (temperature, humidity, etc.)
Finally, as a way of tracking our progress we incorporate a runbook to document the different processes, and integrate with our inventory management for handling stock and materials locations.

The Flowchart

Req ID	P	Definition	Owner	Notes

Req ID	P	Definition	Notes
2.1.1	1	The Flowchart should have views for winemaking, from harvest to bottling to delivery to the consumer.	Mike needs to provide the detail and description of each of the steps.
2.1.2	1	The Flowchart should describe the manufacturing of the following packaging elements: (bottle, box and divider, labels, stopper, capsule)	Mike needs to provide the detail and description of each of the steps.
2.1.3	1	The Flowchart should describe the delivery / distribution process, including exports outside of Argentina, INV certification, OIA certification, etc. Basically, everything that happens to bottles from time they leave Winelock to customers (distributors, importers, consumers).	Mica can provide the details of each of these steps.
2.1.4	1	The flowchart should describe the winecoin process from purchase to cash-out.	Emiliano can provide the details of each of these steps (see section 5.4).
2.1.5	1	The flowchart should describe an extended timeline, from the beginning of the universe, to the time of filling a glass of wine, explaining everything that went into creating the terroir, ending with a description of how this glass of wine can, or might, create thoughts in the drinker.	This could be a horizontal timeline, versus a vertical timeline for the previous three elements. Mike will provide the key historical and future elements to be included in the extended timeline.
2.1.6	1	The flowchart must be localized in the following languages: English, Spanish, with a documented procedure for adding support for additional languages (documented in the project Wiki).

The Runbook

These are the functional requirements for the wine making and delivery runbook.
The Runbook is the platform where activities performed in the winery and the logistical processes are documented.
We document these activities so that we can:

Analyze the amount of time spent required for each task
Compare the different timing of activities from one vintage to the next
Provide a didactic description (text and video) of wine making and logistical tasks
Trace the movement of our wines from one point to the next (tank->bottle->cold storage->distributor->retailer->consumer)

Req ID	P	Definition	Owner	Notes

Req ID	P	Definition	Notes
2.2.1	1	The Runbook entry (ticket) must include the following fields for each task: Name (fixed set of tasks) Description (steps 1...n, and video description) stakeholder (oenologist, logistician) Tools Chemicals Used (and amount) Start Time Finish Time Location (tank, warehouse, pallet, sales outlet) Priority (optional) Note (observations)	The tools, chemicals and farmers are finite lists. Name is a drop down list. Description is fixed to the name of the task. All other fields are user selectable.
2.2.2	1	The oneologist and logistician must be able to create a new ticket, review and update an existing ticket, and delete a ticket both from a smartphone app (android?) and web application.
2.2.3	1	Tickets should be chosen from a defined and finite number of task entries, selected from winery and logistical logs. (Dropdown)
2.2.4	2	The runbook "Tools" data shoud be extracted from a fixed database with the following fields: Name Description Image Serial Number Last Maintenance date Storage locations Value	This information will be useful for creating a tool inventory and calculating asset values. We might use the ERP inventory db for this?
2.2.5	1	The "Chemicals" data should be extracted from a fixed inventory database with the following fields: Product Name Product Description Product amount in stock	This will allow us to determine data, such as: Total amount applied from year-to-year (May 6-May 5)
2.2.6	1	Chemicals used during each ticket should be subtracted from the inventory automatically.	For example, when a farmer uses 2Kg of Copper, this needs to be subtracted from the copper stock in the chemicals inventory.
2.2.7	1	Logistics stakeholders (i.e. Mike, Mica) should be able to assign, delete, and update tasks to a queue for the group of oenologists to execute. Tasks should be assignable to begin at a future date and/or included in a queue.
2.2.8	1	The Runbook entries (all fields) must be localized in the following languages: English, Spanish, with a documented procedure for adding support for additional languages (documented in the project Wiki).

The Dashboard

Req ID	P	Definition	Owner	Notes

Req ID	P	Definition	Notes
2.3.1	1	The dashboard user must be able to select the vintage.
2.3.2	1	The dashboard should report the amount of wine for the vintage in litres (if it is still in the winery) or bottles, once it has been packaged.
2.3.3	1	The dashboard should indicate the locations of the wine, indicating the amounts. The locations include: winelock, winery, Buenos Aires depot, India depot, etc.
2.3.4	1	The dashboard should indicate the conditions of the wine in the winery, including, temperature and TBD.	Ask Patricio/Otto about other data to be collected for wine in the winery.
2.3.5	1	The dashboard should indicate, for Winelock, the temperature and humidity of the stocks, and a video feed.	The data available here will be determined by the winelock service widget.