Page Comparison

1.1.1

1

The daily log should have three views available for visitors: daily, monthly, and yearly.

Ideally, this could be circular or spiraling.

1.1.2

1

From the log, the user should be able to visualize the tasks that were executed on each day, and open the Runbook entry for each by selecting the task.

1.1.3

1

The yearly view of the log should present tasks as relevant to the different stages of the grape growing season.

For example...

1.1.4

1

The daily log should present data in the three views (daily, monthly, and yearly) for:
Temperature (max and min) – daily only. Subsoil humidity (.5m, 1m, and 2m) – daily only Solar irradiance totals (daily, weekly, monthly totals)

Much of the data will be collected using Reiner Van der Lee's VINDUINO. (this needs a separate requirement ID section).

1.1.5

2

Users should be able to visualize differences from one year to the next, of multiple years.

One example:
{+}http://www.subaru.com/csr/environment.html#!/2012/05/28+

1.1.6

1

The log should have a field indicating the last time the daily log was updated.

1.1.7

1

These tasks should be extracted by the content management system (Magnolia) from the runbook ticketing platform (Jira) and represented in the different views (calendars).

1.1.8

1

The daily log must be localized in the following languages: English, Spanish, with a documented procedure for adding support for additional languages (documented in the project Wiki).

1.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)

• Farmer

  Tools

  Chemicals Used (and amount)

  Start Time

  Finish Time

  Start Location (row, claro, plant) - End Location (row, claro, plant)

  Note (observations)

SMF

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.

1.2.2

1

The Farmer 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.

Mr. Sinatra

Use a ticketing platform like Jira?

1.2.3

1

Tickets should be chosen from a defined and finite number of task entries, selected from historic vineyard logs. (Dropdown)

Mike Barrow

Created from the list from existing bitácora entries.

1.2.4

1

The tool used by the Farmer to create, review, update, and delete tickets must be in Spanish.

Mr. Sinatra

1.2.5

1

Tasks should be mapped, both textually and visually, to indicate location by row, claro, plant, giving the farmer the option to input start location and end location, with an option for ALL for each of the three categories of row, claro, plant. This should be agile and simple for farmers to use.

Mr. Sinatra

Tasks only need to be mapped textually for data entry (when creating/modifying the ticket), but visually for reports for end users.

1.2.6

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

Mr. Sinatra

This information will be useful for creating a tool inventory and calculating asset values.

We might use the ERP inventory db for this?

1.2.7

1

The "Chemicals" data should be extracted from a fixed inventory database with the following fields:

Product Name
Product Description
Product amount in stock

Mr. Sinatra

This will allow us to determine data, such as: Total amount applied from year-to-year (May 6-May 5)

1.2.8

1

Chemicals used during each ticket should be subtracted from the inventory automatically.

Mr. Sinatra

For example, when a farmer uses 2Kg of Copper, this needs to be subtracted from the copper stock in the chemicals inventory.

1.2.9

1

Logistics stakeholders (i.e. Mike, Mica) should be able to assign, delete, and update tasks to a queue for the group of farmers (Santos and Yolanda) to execute. Tasks should be assignable to begin at a future date and/or included in a queue.

Mr. Sinatra

1.2.10

1

The Runbook entries (all fields) must be localized in English and Spanish, with a documented procedure for adding support for additional languages (documented in the project Wiki).

Mr. Sinatra