Beruflich Dokumente
Kultur Dokumente
net/publication/309449332
CITATIONS READS
9 2,178
7 authors, including:
Some of the authors of this publication are also working on these related projects:
Advanced Instrumentation for an Intelligent Agriculture: Current Trends and Perspectives View project
All content following this page was uploaded by Dimitrios S. Paraforos on 04 March 2018.
6
http://ifarma.agrostis.gr
330
IFAC AGRICONTROL 2016
326 Dimitris
August 14-17, 2016. Seattle, Washington, USA S. Paraforos et al. / IFAC-PapersOnLine 49-16 (2016) 324–329
Fig. 3. Entity-relationship model of the ifarma FMIS. As an example, all parameters of farms entity are illustrated.
transactions for the farm. All financial transactions are part of the FIspace platform and is used for user
rd
associated with a specific financial season so as profitability authentication and authorization, and (5) any (potential) 3
and cost analysis can be calculated for a given season. Finally party system or service that wants to use the defined ifarma-
the standard values entity is used to define an ordered from a ffa capabilities.
more specific to a more generic range.
2.3 Data security
2.2 Use of FI technologies
In ifarma-ffa the security issue was addressed both from a
In addition to the FMIS, a farm financial analysis (ffa) tool technical and from a business/legal perspective. Technically
was developed based on FI technologies. The ffa is using the wise all data for the ifarma-ffa analysis are stored within an
backend of ifarma FMIS. The combined ifarma-ffa system established, secured, industrial cloud-hosting provider.
architecture and the information exchange is depicted in Fig. Access to the application is secured by virtue of industry
4. The prototype consists of: (1) frontend components, i.e. a standard tools and technologies like FIWARE
set of Wirecloud Widgets that implement the App KeyRock/Keycloak identity management modules. Business
functionality. The Widgets are uploaded/installed in the and legally wise all data under ifarma-ffa are stored and used
Wirecloud GE component instance of the FIspace 7 platform, under the ifarma end-user license agreement (EULA) that
(2) ifarma backend module, i.e. a set of representational state specifically states that the data ownership stays with the
transfer (REST) API services that expose the farm farmer and no other use of the data is possible without the
management and financial analysis capabilities of ifarma, (3) written consent of the owner.
FIspace System and Data Integration (SDI) component that is
used for communication between front- and backend as well 2.4 Graphical user interface of ifarma-ffa
as exposing the backend APIs as FIspace capabilities, (4)
KeyCloak Identity and Access Management (IDM), which is The graphical user interface of the ifarma-ffa is presented in
Fig. 5. As described above, the ifarma-ffa frontend has been
7 developed as a set of interconnected widgets in the
http://www.fispace.eu
331
IFAC AGRICONTROL 2016
August 14-17, 2016. Seattle, Washington,
Dimitris
USA S. Paraforos et al. / IFAC-PapersOnLine 49-16 (2016) 324–329 327
FIspace Platform
KeyCloak
SDI
332
IFAC AGRICONTROL 2016
328 Dimitris
August 14-17, 2016. Seattle, Washington, USA S. Paraforos et al. / IFAC-PapersOnLine 49-16 (2016) 324–329
WireCloud GE. These widgets are described in detail below: Costs: It enables recording of all financial transactions that
are linked with a specific farm. A large number of transaction
Farms: It manages farms and financial seasons. Since the types are predefined in ifarma-ffa: product sales, expenses,
backend of ifarma is used, Farm is the top level entity in goods purchases, land rentals, fuel and maintenance, worker
ifarma-ffa (Fig. 2), where all assets (fields, crops, etc.) are payments, machine value depreciation, etc. The amounts
related with. Financial season is the time period for which the recorded in these transactions are used for the provided
financial analysis is performed. Ifarma-ffa allows the financial analyses.
management of multiple farms for a user/farmer.
Analysis: It shows the results of the analyses performed by
Growings: This widget manages Fields (land parcels) and the ifarma-ffa financial module.
Growings (a crop cultivated in a specific field). The Fields
belong to a Farm but a Growing refers to a specific farm and
2.5 Experimental Farm
season. The Growings are presented in a table format, as a list
or in a visual style format via the utilization of Google
MapsTM plugin, as it is presented in Fig. 5. The ifarma-ffa FMIS was tested on a very common crop in
Germany, i.e. winter wheat (Triticum aestivum L.), and for a
Tasks (Farming activities): This widget is for the time period from 23/09/2014 until 01/08/2015. The winter
management of farming tasks and their required inputs. wheat was cultivated via direct seeding in a 1.6 ha field
ifarma-ffa supports a large number of predefined farming (48.717502°N, 9.182296°E) right after harvesting maize for
tasks for all type of activities such as soil preparation, silage. All tasks, which were performed by the farmer during
seeding and plowing, irrigation, harvesting, fertilizing, etc. this season, were recorded, including the use of each machine
Each of these predefined tasks is preloaded with the required and the utilized inputs such as seeds, pesticides, fertilizers,
inputs (machines, labor work, fertilizers, pesticides, etc.). etc. Furthermore, all the financial transactions that were
related to the crop were available (e.g. fuel procurement,
Standard Values: This widget manages standard values, as a employee payrolls). To test the financial analysis, which is
set of rules defining cost and efficiency of each Input for each performed based only on the standard values, the farmers
Task. The standard values can be used to calculate cost of a were asked to provide their own assessment on typical costs
farming task even when no specific data is provided by the for each performed task in terms of machine and labor.
user.
333
IFAC AGRICONTROL 2016
August 14-17, 2016. Seattle, Washington,
Dimitris
USA S. Paraforos et al. / IFAC-PapersOnLine 49-16 (2016) 324–329 329
334
View publication stats