FIZZ Network is the ideal solution for sensory or consumer test facilities, when the booths are equipped with networked computers.
Each tasting booth is equipped with a PC linked to the FIZZ supervisor through a network. The judges answer on screen using a mouse and the data are collected directly through the network during the session.
FIZZ Network includes the same design and data computation tools as all other FIZZ solutions. Furthermore, the sessions are identical to those in FIZZ Portable and FIZZ Web.
Everything is done in FIZZ Network for an optimal use of your sensory room:
- Modular test execution
- Allocation of different tests to different booths
- Multiple tests launched consecutively or chosen by the judge
- Stopping and restarting session for missing panelists
- Detailed supervision of the test progress
- Recovery after incident
- FIZZ_Network 2,50MB
Answering a test
The session may also include before the test itself a page containing the tray number and asking the panelist to go and take this tray. This allows preparing in advance the trays containing the samples (if the type of samples allows it), and the session can run more freely, without requiring staff to serve the panelists.
Conversely, if the trays are put in the booths in advance, the taster can be asked which one he has been given to evaluate.
The judge the gets the different screens that have been built into the session, with various questions asked. To answer he clicks on the checkboxes (triangle test, multiple choice questions, or category scales for example), on the line scales, the buttons...
When text input is required in your session (password, free comments...), a simplified keyboard may be displayed on screen. The use of the keyboard is not required, except for long comment input.
When the judge has finished answering, a thank you screen is typically displayed, and the test can then restart automatically in the booth to allow an other judge to answer it.
Modular session execution
The basic operation is simply to start the same test in all booths, but many more possibilities are available:
Different sessions allocated to sets of booths
When starting a session, the operator chooses the booths in which he wants to run it. He may later start other sessions in the remaining booths. Several sessions may thus be run independently in different booths.
Up to 20 different sessions may also be started together in multiple sessions mode:
- The different sessions to be done by the panelist can simply be chained: after he has finished a test his next test is presented. Optionally the operator can let the judge decide to stop between tests and come again later to continue his tests.
- The panelist can be given the choice between the tests he has to do, and the session he chooses is started. When he's finished with this test, he chooses among the remaining tests. Obviously if the panelist has only one session to do, it is started without proposing a choice.
A session may be stopped by the operator when the panelists present have finished, and even if not all panelists came. The operator chooses which booths are to be stopped.
The session may be run again later to allow more panelists to come and do their session.
Terminal (booth) status
You see what happens in each terminal:
- identification of the panelist once he is identified,
- phase of the session (identification or test itself)
- current session,
- screen currently displayed,
- product currently being evaluated in monadic tests,
- help requested,
For each session that is currently running, you get:
- the number of panelists expected,
- the number of answers already present when the session was started,
- the number of panelists having finished since this startup,
- the total number of panelists having finished the session (total of the two previous numbers),
- the number of judges currently answering the session,
- the detail of the names of the panelists having logged in to the session. The names of those that did not log in yet could allow you to ring them up to press them to come.
Session per booth
This table shows for each of the sessions that is currently running on which booths it has been started and how many tasters have logged in to the session for each booth.
Recovery after incident
To guard against any problem and avoid data losses during sessions, FIZZ provides a session resume possibility, which allows restarting easily the session at the exact point where the interruption occurred.