Slides from the 2nd Technical Meeting of the Slope Project

1. Project SLOPE
1
WP 1– Definition of requirements and
system analysis

2. WP1. Definition of Requirements
and System Architecture
Mikkeli
02-04 July 2014
•Task 1.1 - Users and System requirements – ITENE
• Partners: GRAPHITECH, CNR, KESLA, COAST, MHG, BOKU, FLY, GRE, TRE
• Task 1.2 Hardware and equipment definition – KESLA -> GRAPHITECH
• Partners: CNR, COAST, MHG, BOKU, FLY, GRE, ITENE
• Task 1.3 Human Machine Interface (HMI) definition – GRAPHITECH
• Partners: KESLA, MHG, GRE, TRE, ITENE
• Task 1.4 Mountainous Forest inventory data model definition – CNR
• Partners: GRAPHITECH, COAST, MHG, BOKU, FLY, GRE, TRE
• Task 1.5 - System Architecture - MHG
• Partners: GRAPHITECH, FLY, TRE, ITENE

3. WP1. Objectives
Mikkeli
02-04 July 2014
• Identify the users and specifically their needs and
requirements.
• Define processes
• Detail the data and metadata model covering the use of
SLOPE
• Define the hardware, equipment, sensors and mobile
devices
• Define the Human Machine Interface requirements
• Define the system architecture to be used
• Define the technical requirements

4. WP1 Orginal timeline andWP1
situation– M01-M06
January February March April May June
ITENE: 100%
Task 1.1: D1.01
Users
Requirements
Report
KESLA: 80%
Task 1.2: D1.04
Technical
Requirements
Report
Project
meeting in
Mikkeli
GRAPHITECH: 80%
Task 1.3: D1.02
Human
Machine
Interface
CNR: 80%
Task 1.4: D1.03
Data and Meta
Data model
Report
MHG: 60%
Task 1.5: D1.05
System
Architecture
Specifications
Mikkeli
02-04 July 2014

5. WP1 And how did it go… M01-M09
Jan Feb Mar Apr May Jun Jul Aug Sep
ITENE:
Task 1.1: D1.01
Users
Requirements
Report
Project
meeting in
Mikkeli
GRAPHITECH:
Task 1.3: D1.02
Human
Machine
Interface
MHG:
Task 1.5: D1.05
System Architecture
Specifications
Mikkeli
02-04 July 2014
CNR:
Task 1.4: D1.03
Data and Meta
Data model
Report
KESLA
GRAPHITECH :
Task 1.2: D1.04
Technical
Requirements
Report

6. Kick-off Meeting
8-9/jan/2014
WP1 Deliverables
• D1.01 Users Requirements Report
• Specifies user requirements, roles, groups and use cases
• D1.04 Technical Requirements Report
• Specifies hardware and technical requirements for the
hardware that shall be used in the project.
• D1.02 Human Machine Interface
• Specifies user interfaces that will be in slope platform
• D1.03 Data and Meta Data model Report
• Specifies the data and meta data that will be in slope
platform
• D1.05 System Architecture Specifications
• Sepcifies technical architecture of the platform (high level
specification). Describes partner applications and
technologies.

7. Kick-off Meeting
8-9/jan/2014
WP1 Problems
• One partner (Kesla) left from consortium. Kesla was Task 1.2
leader and contributor in many WP1 tasks.
• Feedback and communication delays affected deliverable
finalization on time

8. Kick-off Meeting
8-9/jan/2014
WP1 Summary
• All deliverables can be found from 04_Final_Deliverables folder
on Dropbox
• All deliverables finalized correctly
• Objectives reached
• WP1 was late but finalized correctly
Thank you! Let’s move to task leader presentations…

24. TASK 1.4
Mountainous Forest inventory
data model definition
Work Package 1: Definition of requirements and
system analysis

25. Work Package 1: Definition of Requirements and
System Analysis
Starting : January 2014
Ending: June 2014
Objectives
• Identify the targeted users and specifically their needs and requirements.
• Define state of the art processes for planning, managing and assessing harvesting
operations and supply chains in mountainous areas.
• Define a comprehensive set of information to support the implementation of more
timely decisions, and improve the quality of decisions
• Detail the data and metadata model covering the use of SLOPE
• Define the hardware, equipment, sensors and mobile devices to be used
• Define the HMI requirements, especially for the on-field devices and machines
• Define and document the system architecture to be used
• Define the project technicalities and technical requirements such as use case special
conditions

26. Task 1.4: Mountainous Forest inventory
data model definition
Task Leader: CNR
Task Partecipants: Graphitech, Coastway, MHG Systems, BOKU, Flyby, Greifenberg,Treemetrics
Deliverable D1.03:
Data and Metadata Model Report: This report provides details of the Data and Metadata model defined to
conceptualize the SLOPE Forest Information system.
Delivery Date= June 2014
Estimated person Month= 13.50
Task Leader 1 2 3 4 5 6 7 8 9 10 11 1
2
1 Definition of requirements and System analysis MHG
1.1 Users and System requirements Itene
1.2 Hardware and equipment definition Kesla
1.3 Human Machine Interface definition Graphitech
1.4 Mountainous Forest Inventory data model
definition
CNR
1.5 System Architecture MHG

27. Task 1.4:Schedule
Task Leader: CNR
Task Partecipants: Graphitech, Coastway, MHG Systems, BOKU, Flyby, Greifenberg,Treemetrics
Objective: The objective of Task 1.4 is to define the required information for the FIS data
population.
In the Report D1.03 , available data sets as well as required additional data, to be acquired
by the SLOPE modules, are defined.
The definition of the different data formats and relevant standards is also included, in
order to support data merging and harmonization.
Steps
19/05 First version release
23/06 Second version release
30/06 Third version/first issue
30/07 Revision of document reviewed
22/09 Completed and Validated Deliverable Document

28. Task 1.4:TOC
1 Introduction
2 Data formats and standards
3 Integrated models
4 Overview of existing databases/services
5 Required information to populate the Forest Inventory System
Annex A: TABLES OF DATASETS FOR FIS POPULATION
Annex B: TABLES OF DATA ON FOREST PRODUCTION QUALITY AND AVAILABILITY
Annex C: TABLES OF DATA DERIVED FROM THE FIS

29. Spatial data
Analysing the SLOPE requirements, several
typologies of spatial data are related to the forest
information system. We can include: forest and
trees features, land parcels, road network and
landing areas sawmills positions, elevation and
slope of a certain region etc. How these
information would be geometrically represented
and in relation to this, how they will be modelled
according to acquisition system used to retrieve
the information?
In SLOPE project we will have different source of
geographic information and each of these
produce different typologies of spatial data,
which after a processing step will generate new
spatial data.

30. Spectral data
Several typologies of spectral data are
related to the forest information system.
We can include (relating to the
characterization scale): forest features,
single tree characteristics, log quality,
early ring properties, sub structural
morphology of wood cell wall.
Various sources affect the spectral data
representation.
Different spectral analysis methods are
covered in this section: spectroscopy for
the analysis of wood chemical-physical
properties, hyperspectral imaging of
wood, hyperspectral imaging of forest.

31. Data collected by the harvesting
machines
Relevant variables, representing the
characteristics of the harvesting system in the
SLOPE scenario, will be measured with
transducers/sensors. Some of the measured
variables aim at monitoring machine’s
parameters, enabling security, energy-saving,
real-time control and automation functionalities.
Some machine’s parameters will be also
correlated to quality indices of the harvested
material (e.g. cutting quality index).
Another series of data are those collected by the
sensors to determine parameters related to the
wooden material characteristics (i.e. data from
NIR and hyperspectral sensors, data from stress
wave tests) or to measure geometrical features of
the logs.

32. Overview of existing
databases/services
• EU forest datasets
• Datasets available in the SLOPE pilot areas
ITALY–TrentoProvince
AUSTRIA–Salzburg

33. Required information to populate the
FIS
to develop an interactive system for
cableway positioning simulation (CwPT)
to assist tree marking – forestry
measurements estimations (TMT)
to define technology layers (harvest
parameters) (TLT)
to support novel inventory data
content (IDC)

34. Annex A:
TABLES OF DATASETS FOR FIS POPULATION

35. Annex A:
TABLES OF DATASETS FOR FIS POPULATION
TABLE A.1: FOREST
TABLE A.2: INFRASTRUCTURES AND BUILDINGS
TABLE A.3: HYDROGRAPHY
TABLE A.4: RISK FACTORS
TABLE A.5: COMMUNICATION

36. Annex B: TABLES OF DATA ON FOREST
PRODUCTION QUALITY AND AVAILABILITY

37. Annex C:
TABLES OF DATA DERIVED FROMTHE FIS
TABLE C.1- HARVESTING OPERATIONS
TABLE C.2- ASSORTMENTS
TABLE C.3- INFRASTRUCTURE CONDITIONS
TABLE C.4- PERFORMANCE INDICATORS
OF THE SUPPLY CHAIN

38. Conclusions
Report D1.03 is a reference for the implementation of:
D2.01 Remote Sensing data and analysis
D2.02 UAV data and analysis
D2.03 TLS data and analysis
D2.04 the Harvest simulation tool
D2.05 the Road and logistic simulation module
Data and metadata model defined in the D1.03 will be the base for the implementation of
the mountainous forest information system database (WP5)
The report D1.03 defines also data acquired by means of non-destructive or semi-
destructive testing techniques, for the multi-sensor characterization of the harvested
material. A prerequisite for this is the definition of the technical characteristics of the
hardware/sensors instrumenting the harvesting machines (Task 1.2 – D1.04).

39. 2° Meeting
July/2014
Thanks to:
CONTRIBUTORS and REVIEWERS:
Juan de Dios Diaz (ITENE)
Barbara Hinterstoisser (BOKU)
Enda Keane (Treemetrics)
Martin Kühmaier (BOKU)
Andrea Masini (Flyby)
Enda Nolan (Coastway)
David O’ Reilly (Coastway)
Gianni Picchi (CNR)
Federico Prandi (Graphitech)
Anna Sandak (CNR)
Jakub Sandak (CNR)
Veli-Matti Plosila (MHG)

40. SLOPEIntegrated proceSsing and controL systems fOr sustainable forest
Production in mountain arEas
Kick-off Meeting
8-9/jan/2014
Deliverable Number D.1.04
Technical Requirement Report
WP 1 – Definition of requirements and system analysis
Task 1.2 – Hardware and equipment definition

41. Kick-off Meeting
8-9/jan/2014
Typical Supply Chain

42. Kick-off Meeting
8-9/jan/2014
SLOPE supply chain
Forest stand
Cable corridor Landing Road
Location
Processes
Hardware
Forest survey Marking Felling
Extracting Processing Transporting
Satellite images
UAV
TLS
RFID
Chain saw
GPS
Tower yarder
Carriage
Excavator
Harvester head
Control system
Analysis
equipment
(sensors)
Truck
RFID
GPS
Tracking
RFID, NFC, UHF, GPS etc.
Location
Processes
Hardware
Tracking
RFID, NFC, UHF, GPS etc.

43. Kick-off Meeting
8-9/jan/2014
Data flow
Data flow between
SLOPE system
components

44. Kick-off Meeting
8-9/jan/2014
Tree marking and tagging
UHF technology has
been identified as
the most adapted to
the SLOPE project
requirements, due
mainly to the low
cost (passive tags)
and long reading
range (4-5 meters).
There are some changes?

45. Kick-off Meeting
8-9/jan/2014
Tree marking and tagging
Some lacks in the definition of the
portable devices for in forest
operation:
• Need of a portable reader?
• Bluetooth communication with
tablet devices?
• Need enanched GPS location?

46. Kick-off Meeting
8-9/jan/2014
Tree marking and tagging
These portable
readers has been
identified for the
activities on the
landing area, can be
used also in the
forest activities?.

47. Kick-off Meeting
8-9/jan/2014
Processor Head

48. Kick-off Meeting
8-9/jan/2014
1. The new actuator bar for
scanners scanning the
cross section of log
2. Chain sawing module for
sensing cutting forces and
optimization of the cross-
cut
3. Feed power sensor
4. Camera/3D vision sensor
5. Colour camera(s) scanning
side of the log
6. Ultrasound stress wave
velocity scanner
7. RFID reading system
8. Data fusion/control unit
Processor Head

49. Kick-off Meeting
8-9/jan/2014
CableWay and Self Propelled
Carriage
Description of the
hardaware, the needed
improvment related to
SLOPE project have to be
defined.

50. Kick-off Meeting
8-9/jan/2014
SmartTruck Hardware Specifications

51. Kick-off Meeting
8-9/jan/2014
Not completely solved issues
Portble devices for on-field operation
and for hervesting operation.
Black-box

52. WP1T1.5 - System Architecture
Task leader: MHG
Deliverable: D1.05 System Architecture Specifications
Designed delivery time: M6
Deliverable status: Ready
Delivery time: 24th September 2014
San Michele all’Adige
19 -21 January 2015

53. T1.5 Objectives
San Michele all’Adige
19 -21 January 2015
• Design the technology specification of the system
architecture
• Specify applications and technologies to be used
• Specify design principles
• Design model and interfaces for application
integrations in different integration levels
• Design deployment platform

54. T1.5 Deliverable in brief
San Michele all’Adige
19 -21 January 2015
• Describes each partner’s applications and
technologies
• What current applications/systems can do
• What technologies they use
• How we can integrate them to the SLOPE
platform
• SLOPE platform integrates services and
technologies from MHG, Graphitech, Flyby &
Treemetrics.

55. T1.5 Deliverable in brief
San Michele all’Adige
19 -21 January 2015
• Specifies design principles are used in the SLOPE
platform architecture
• Service oriented architecture
• With SOA we can loosely integrate very
different systems together
• With minimum modifications to exisisting
codebases

56. T1.5 Deliverable in brief
San Michele all’Adige
19 -21 January 2015
• Specifies integration technologies and components
to be used on this platform
• Liferay -> Presentation level integration
(different ways to integrate)
• Web Services (SOAP/REST) for service level
integration
• GeoServer -> spatial data from SLOPE FIS
database

57. T1.5 Deliverable in brief
San Michele all’Adige
19 -21 January 2015
• Specifies integration technologies and components
to be used on this platform
• Liferay -> Presentation level integration
(different ways to integrate)
• Web Services (SOAP/REST) for service level
integration
• GeoServer -> spatial data from SLOPE FIS
database

58. T1.5 Deliverable in brief
San Michele all’Adige
19 -21 January 2015
• Specifies deployment platform
• Use neutral, scalable cloud service for
deployment (not inside any partner’s secure
infrastructure)
• This helps to open access for every partner that
needs
• Jelastic PaaS-platform is good option for
deployment (MHG will test this)

59. San Michele all’Adige
19 -21 January 2015
System Architecture Overview

60. San Michele all’Adige
19 -21 January 2015
Component Diagram

61. San Michele all’Adige
19 -21 January 2015
Summary
• Deliverable can be found from 04_Final_Deliverables folder
• Specified system architecture is good base for SLOPE FIS development
• System architecture specification should be updated (if needed)when
implementation processes goes further
Thank you!