EAI IIES Summit and Exhibition
Riva del Garda, Trento Italy 4-6 October, 2012
Food Safety & Autenticity 2012
Brussels, Belgium 18-20 September, 2012
Rome, Italy, 23-27 July 2012
IEEE Symposium and URSI Meeting
Chicago, IL, USA 8-14 July, 2012
QUID Innovation Italy
Milan, Italy 27-28 June, 2012
INSME - INNOBIZ - WTA Hi-tech fair
Daejeon, South Korea 21-25 May 2012
CIBUS 2012
Parma, Italy 7-10 May 2012
SMAU business 2012
Padova, Italy 18-19 April 2012
IEEE International Conference on RFID
Orlando, FL, USA 3-5 April 2012
Anuga FoodTec - F2F at Speakers' Corner
Cologne, Germany 28 March 2012


Path: Home > About > Workplan > Wp2

WP2 Information Modelling and Architecture


It is to be expected that modelling of the information flows necessary to ensure availability of the information required by the business process modelling will be a substantial task, therefore considerable effort has been devoted to this work package. It aims at identify the information flow considering all details of information in the several stages of the food chain, which might be relevant by processing, for retailers and for end users, in order to improve quality, reach higher levels of traceability and more transparency. One main question will be what information is relevant from which point of view (producers, processors, retailers, consumers, health experts, SME, etc.) in order to consider it in the information flow. The ultimate goal is to have the information readily available and in a ready-to-be-understood format at the point of need for each user of the new system. To achieve this, the relevant information needs to be fed into the information chain at some point in order that it can be transported along with the foodstuffs on the RFID tags to the users. Possible "locations" to include the information into the information chain are food producers (i.e. farmers producing grapes, meat, milk etc.), food transporters (i.e. the ones in charge of transport of the primary foodstuffs to the place of food "refining"/"procession"), food processors, food transporters (to point of sale), food retailers / seller. The point of upload of the information that makes the most sense needs to be identified, but in any case, the information needs to be available in a standardized format to enable a its sustainable use. Furthermore protocols, privacy and security requirements will be identified. After having identified and collected all necessary information, the information modelling and architecture will be developed and evaluated as well as then tested in the second project’s phase. This WP will have strong contribution and collaboration with WP 3: systems integration and databases construction, especially in task 3.2: mapping of technology to information model.


Task 2.1. Identification of information flows within business process
This task aims at identifying the detail of and the requirements on the information flow according to the parameters, which should be monitored and transmitted along the food chain and during the business process. This task intends also to identify critical points, which might influence the efficiency of the information flow, like time, resources, duplication of information, etc. In collaboration with WP3 the use of sensor networks and its requirements should be investigated.

Task 2.2. Detail of information flow from WP4-8
This task will work from information produced by task 1 of work packages 4-8. The task seeks to consider all relevant parameters at farm, processing, logistics, distribution, retailers side and consumers, which have been identified within WP 4 to 8, and should be taken into account in the development of the information model. In doing so, this task will contribute to the identification of how the service/solution can fulfil the unmet needs of the identified target users along the food chain.
The relevant information, which will be monitored and recorded during the whole producing process starting at the farm, has to be “translated” if necessary and stored in an adequate format, which can be accessed from system’s users. It will imply activities in the field of food description, applicable expression of measures, unlimited linking of different kinds of information to corresponding relevant parameters, providing overall compatibility of information within the information model.

Task 2.3. Detail of protocol requirement
This task aims at investigating the possibility of integrating existing technology solutions, e.g. the solutionpresented by the EC funded project ASPIRE , in the development of the information model. This investigation implies the exploration of different existing mechanisms for network connectivity, of possibilities for integration into existing networks, of connectivity with mobile devices and of mechanisms for anti-collision in multiple-tags reading (time division multiple access, ALOHA, binary tree schemes, bit by bit, bin-slot). Furthermore, the task aims at defining a mandatory set of rules governing the information and data flow in the RFID system.
Task 2.4. Privacy and security requirements
Considering that traceability systems aim at catch and recognize identifiers in the course of operation, for example recognizing their location and time until the post sale stage (end consumer’s household), one major issue in this project will be to ensure privacy and security fulfilling all related requirements. This task intends to explore different existing techniques to assure privacy of all system users and system’s security. Examples for existing technologies are kill function and clipped tags).They are considered new ways to implement privacy. So, from this point of view they define a technology to obtain that aim: privacy. It is a transformative technology: Enhance the security of personal data, if collected/used.
In order to reach this goal in relation to end consumers, guidelines and rules for administrators and users will be developed (consumer notice, consumer choice, etc.) Regarding the system’s security the use of smart tags, key encryption units, cryptographic protocols as well as closed identification will be investigated. In addition, issues concerning product items authentication will be investigated and levels of security and granularity of the security features will be defined.

Task 2.5. Development of information model and architecture
According to the requirements appointed as outcomes of previous tasks in this work package, an information model will be defined in base to the following points:

  • Data model: analysis and design of the data stored by information systems
  • Architecture: conceptual structure and logical organization
  • Database: structural design of shared information (potential data mining)
  • Software Platform: preferable Open Source tools
  • Hardware requirements for physical allocation of the information system
  • Interface for the central database
  • Indoor production: existing quality assurance system integration to central database
  • Examples for database/central application: Storing e.g. climatic data and alerting systems (Fire,extreme weather, earthquake)

Task 2.6. Evaluation of information model and architecture
Evaluation during system development is designed to ensure that the system meets its intended purpose. Therefore the evaluation process in this task will consider the user needs and the purpose of the information flow, which will be identified along the elaboration of this work package. Scarcely no element is that crucial for the evaluation process of a system than its quality. Examples for quality features of the system, which should be evaluated within this task is learnability, memorability, ease-of-use and efficiency.
The evaluation of the developed and implemented information modelling and architecture would be performed in two stages: firstly, by introducing simulated data coming from an ad-hoc application; and later, by testing jointly to tasks 3.5 and 8.5.to obtain proper feedback in order to complete and improve the implemented model and the architecture.