Slides from the Mid-term Review Meeting of the Slope Project

1. Mid-term Review
2/Jul/15
Project SLOPE
1
WP 1– Definition of requirements and
system analysis

2. Mid-term Review
2/Jul/15
Project SLOPE
2
T1.1– Users and System requirements
Brussels, July 2th, 2015

3. Mid-term Review
2/Jul/15
Overview
• Status: Completed (100%)
• Length: 3 months (from M1 to M3)
• Involved Partners
• Leader: ITENE
• Participants: GRAPHITECH, CNR, KESLA, COAST, MHG, BOKU,
FLY, GRE, TRE
• Aim: Gather information about user requirements to guide
future developments
• Output: Deliverable D1.01 (Submitted)

4. Mid-term Review
2/Jul/15
Procedure
4
 1. Identifying user groups
 2. Developing functionalities
 3. Creating relation Matrix
 4. Developing questionnaires
 5. Contact with End Users
 6. Anlysis and conclusions

5. Mid-term Review
2/Jul/15
1. Identifying user groups
5
 1. Forest owners
 2. Harvesting contractors
 3. Transport companies
 4. Mill companies
 5. Biomass processing companies
 6. Foresters / specialists

6. Mid-term Review
2/Jul/15
2. Developing functionalities
6

7. Mid-term Review
2/Jul/15
3. Creating relation Matrix
7

8. Mid-term Review
2/Jul/15
4. Developing questionnaires
8

9. Mid-term Review
2/Jul/15
5. Contact with End Users
9
 Forestry related partners identified possible
contacts
 Phone / personal meeting were done to fill in
questionnaires
 Detailed info needed -> detailed questionnaires ->
long time needed to answer them
 Average time per contact in interviews: 30min - 1h

10. Mid-term Review
2/Jul/15
6. Anlysis and conclusions
10
 Total: 23 questionnaires
 Locations: Austria, Italy (Trento), Finland, Ireland

11. Mid-term Review
2/Jul/15
6. Anlysis and conclusions
11
Planning
For selecting a harvesting area, the system should:
Consider cost and demand as a factor to select a harvesting area
Determine the volume of timber available in the harvesting zone
Allow to know the age of trees
Measure tree’s height
Determine slope and roughness of the terrain
Determine accessibility of the zone (road placement…)
For marking a tree, the system should:
Measure dimensions of trees
Determine quality of wood
Register specie and age of trees
Be able of read all this information just before marking a tree
Identify trees unmistakably

12. Mid-term Review
2/Jul/15
Deliverable Index D1.01
12
 All info and results gathered in D1.01

13. Mid-term Review
2/Jul/15
Deliverable Annex
13

14. Mid-term Review
2/Jul/15
Mid-term Review
2/Jul/15
Contact info
Juan de Dios Díaz (juan.diaz@itene.com)
Emilio Gonzalez(egonzalez@itene.com)
Thank you for your attention

15. Mid-term Review
2/Jul/15
Project SLOPE
T1.2– Hardware and equipment definition
Brussels, July 2th, 2015

16. Mid-term Review
2/Jul/15
Overview
• Status: Completed (100%)
• Length: 3 Months (From M1 to M3)
• Involved Partners
• Leader: Graphitech
• Participants: CNR, COAST, MHG, BOKU, FLY, GRE, ITENE
• Aim: define the hardware and machinery specification on a
system requirements basis
• Output: D.1.04 Technical Requirements Report

17. Mid-term Review
2/Jul/15
Goals
The Objective of the task was:
• Define the Hardware and Software equipment including;
• Instruments and tools to collect forest information before
harvesting;
• Instrument and tools to collect timber information during the
harvesting;
• Instrument and tools for resources tracking;

18. Mid-term Review
2/Jul/15
Workflow

19. Mid-term Review
2/Jul/15
Forest Survey
Remote Sensing Information from: satellite, aerial, UAVs and Terrestrial laser Scanning:
Multiresoultion forest survey
Satellite: Large scale (region), several repetion along
time. Cost depending on spatial resolution
Airborne: Medium Scale (depending of altitude) not
suitable for multiple repetion. High cost
UAVs: Small scale (plot) possible multiple repetion,
high resolution. Medium Cost
TLS: Very small scale (portion of plot), Information
not achieved from the above. Time consuming
Medium cost.

20. Mid-term Review
2/Jul/15
Satellite Images
Technical Specifications
Number of Satellites: 5
Orbit Altitude: 630 km in Sun-synchronous orbit
Global Revisit Time: 1 Day
Inclination: 97.8 degrees (solar-synchron)
Ground sampling distance (nadir): 6,5 m
Pixel size (orthorectified): 5 m
Swath Width: 77 km
Sensor Bands
440 – 510 nm (Blue)
520 – 590 nm (Green)
630 – 685 nm (Red)
690 – 730 nm (Red Edge)
760 – 850 nm (Near IR)

21. Mid-term Review
2/Jul/15
UAV
Vehicle
• 96cm wingspan
• Less 0.55kg dry-weight (0.68kg with RGB payload,
0.71kg with NIR payload)
• 45-50 minute flight time
• 40-90 km/h cruise speed
• Up to 45km/h or 12m/s wind resistance
• Up to 3Km radio link
• Up to 12sqkm coverage
• Linear landing
• Image resolution/pixels of 3-30cm
• Autopilot
Payload
• Resolution 16MP
• 35 mm equivalent focal length 24mm
• Flight altitude (4cm/px GSD) 130 m

22. Mid-term Review
2/Jul/15
Workflow
1
2
3
4
5
5
6
6

23. Mid-term Review
2/Jul/15
Trees marking
Tags
Ultra High Frequency RFID tags work at 868-
902MHz. Standard for logistics and storage
applications.
Low cost (passive tags) and long reading range
(4-5 meters).
Reader
Fully integrated handheld UHF RFID
USB/Bluetooth reader

24. Mid-term Review
2/Jul/15
Cableway and Carriage
• Check the weight of the timber
• Read the tags
• Check the presence of operators
below the line
• Open automatically the
electronic chockers
• Communicate with processor
head and with the server and the
black box, transmitting the
current situation, such as
position, working speed, fuel
consumption

25. Mid-term Review
2/Jul/15
Processor Head
Processor model ARBRO 1000 S
• The factors determining the hydraulic demand (the
resistance to advance) are the density/size of
branches and the friction of the knives against the
bark.
• The lower productivity compared to roll processors
is not influent, since the extraction of trees by cable
crane is relatively slow.
• Relatively simple structure and electronics.

26. Mid-term Review
2/Jul/15
Head Processor
1. Machine control
system
2. External control
system Compact
rio + External
industrial pc
3. Actuators direclty
controlled from
machine control
system.
4. External sensors.
1
2
3 4

27. Mid-term Review
2/Jul/15
Head Processor
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
12
3
4
5
6
7

28. Mid-term Review
2/Jul/15
Tracking system
• Option 1 included manual RFID reader and tracking device in trucks,
• Option 2 included fixed RFID reader with tracking device integrated in the truck.

29. Mid-term Review
2/Jul/15
Conclusions
The Achievements of the task are:
• Hardware and Software requirements have been defined;
• The identified resources will be the input for the future
developments during each specific tasks;
• The requirements and hardware sorted out from this deliverable
are the backbone of SLOPE system, however some future
refinements can be needed.
• The left of the responsible partner KESLA has caused a delay on
deliverable submission, however all the adopted remedial
actions have ensured that this had no effect on the other task
activities.

30. Mid-term Review
2/Jul/15
Contact info
Federico Prandi: federico.prandi@graphitech.it
Thank you for your attention

31. Mid-term Review
2/Jul/15
Project SLOPE
T1.3– Human Machine Interface (HMI)
definition
Brussels, July 2nd, 2015

32. Mid-term Review
2/Jul/15
Task Overview
• Status: Completed (100%)
• Length: 3 Months (From M2 to M4)
• 5 Involved Partners
• Leader: GraphiTech
• Participants: MHG, GRE, TRE, ITENE
• Aim: define the user interface for the whole SLOPE system,
including:
• User interface needs
• Web user interface requirements
• In-vehicle and on-field devices interfaces
• Output:
• D.1.02 Human Machine Interface

33. Mid-term Review
2/Jul/15
Process
• State of the art
• User interfaces in forest production
• Analysis of available user interfaces within consortium
• Interface Requirements analysis
• Actors
• Use Cases
• Interfaces definition
• Web client
• Mobile client
• In-vehicle client
• ERP

34. Mid-term Review
2/Jul/15
User Interface Analysis
“Human-Machine Interfaces can be seen as the parts, software or
hardware handling the interaction between humans and machines
[…] Computer can have several different purposes ending in an
open-ended dialog between users and computer.”

35. Mid-term Review
2/Jul/15
User Interface Analysis
Analysis of each available interface and classification against
different types of HMI:
• Direct manipulation interface
• Graphical user interface (GUI)
• Web User interfaces (WUI)
• Command Line Interfaces
• Touch User Interfaces
• Hardware User Interfaces
• Batch Interfaces
• Gesture interfaces
• Intelligent User Interfaces
• Non-Command User interfaces
• Object Oriented User interfaces
• Tangible User Interfaces
• Task-Focused Interfaces
• Text based interfaces
• Zero Input Interfaces

36. Mid-term Review
2/Jul/15
User Interface Analysis
Available interfaces
Graphicaluser
interface
Web-based
interface
Touchuser
interface(Mobile)
Hardware
Interface
BatchInterface
TouchUser
Interface(Vehicle)
IntelligentUser
interface
Direct
Manipulation
Interface
Taskfocused
interface
GestureInterface
Forestry Resource Planning
System (MHG)
V V V
Forest Analysis and
Monitoring (TREE)
V V V V V
Intelligent Harvesting
Heads
V V V
Cable Crane System (GRE) V V V
Geographical Information
System for Environmental
Planning (GRAPHITECH)
V V V V

37. Mid-term Review
2/Jul/15
User Interface Requirements
• From:
• User requirements reports (D.1.1)
• SLOPE reference scenario
• Results:
• Requirements list
• Use cases by actor and interface

38. Mid-term Review
2/Jul/15
User Interface Requirements List
• Selecting and planning harvesting area
• Provide trees information (height, age)
• Provide area information (available timber volume, )
• Determine slope and roughness of the terrain
• Determine accessibility of the zone (road placement, road width, road slope, landing areas…)
• Tree marking
• Register specie and age of trees
• Be able of read all this information just before marking a tree
• Cable Corridors
• Allow the estimation of total amount of timber to be harvested.
• Allow the selection of the intermediate support.
• Cost Estimations
• Show harvesting costs based on user’s planning choices
• Traceability
• Provide location of logs

39. Mid-term Review
2/Jul/15
User Interface Requirements List
• Harvesting monitoring/tree identification
• Show weather conditions and forecast.
• Estimate market demands.
• Obtain values of productivity and statistics of development of harvesting activities (related to the plan).
• Detect unmistakably each tree, accordingly to how it was marked.
• Show tree data before harvesting operation.
• Contingency plans
• Show possible failures or breakages
• Online Purchases
• Register species of trees
• Develop a platform including mentioned characteristics and specifying provenance of logs
• Inventory
• Show logs in different states (standing, ready to be harvested or harvested)
• Show accessibility of the zone (road placement…)
• Show quality of wood

40. Mid-term Review
2/Jul/15
Use cases

41. Mid-term Review
2/Jul/15
Human Machine Interfaces Design
• Based on principle of least astonishment
• human beings can only pay attention to one thing at one time
• exploit users' pre-existing knowledge as a way to minimize the learning
curve
• functionally similar or analogous programs with which your users are
likely to be familiar
• Takes in account a conservative sector like Forestry
• Takes in account already existing consortium platforms

42. Mid-term Review
2/Jul/15
HMI Design - Desktop
• Web based application (HTML5/WebGL Based)
• Easy integration into other systems
• Task based interface
• Analytics
• Operation
• Forest

43. Mid-term Review
2/Jul/15
HMI Design - Desktop
Main Functionalities:
• Analytics: set of tools to retrieve geometrical and geophysical (like slope and soil
components) information about the property and about the places of interest for
determined operation or dataset
• Terrain Providers, Imagery Providers, Measurement, Slope Analysis, Cadastral & Public Data,
Points of Interest, Roads
• Operation: tools to manage different operation related to harvesting and to plan them
in determined temporal interval
• Cableway Planning, Working Area Setup, Felling, Buildings & Terminals, Logistic, Harvest
Tracking, Weather Forecast
• Forest: Tools to inspect the forestry inventory datasets and all the operation related to
forest resource planning.
• Area Selection, Trees Visualization, Virtual Marking, Stem Visualization Tool

44. Mid-term Review
2/Jul/15
HMI Design – Desktop - Analytics
View of the
Ground lidar
scan or images
Inspect datasheet
and forestry
operation chart s of
ana area

45. Mid-term Review
2/Jul/15
HMI Design – Desktop - Operation
Road
construction
and set
property
boundary
Insert in the
scenario all the
structure to plan
the operation

46. Mid-term Review
2/Jul/15
HMI Design - Mobile
Main Functionalities:
• Tree and Forest Inventory: singe tree and area inspection.
• Logs and wood: to obtain the position on the map of all
the logs that have to be harvested.
• Machines: to visualize on the map the area of work and
the evolution of the harvesting and felling procedures
• Virtual Forest: show a simplified version of the forest
developed for the desktop platform
• Layers: Select additional layers to be applied to the map.
• Transportation: to show road and truck fleet movement
• Subset of desktop functionalities
• Exploits mobile device capabilities (e.g. GPS, Camera)
• Tagging support for Forest Operators

47. Mid-term Review
2/Jul/15
HMI Design – In-Vehicle
• Enrich already existing In-Vehicle systems
• Based on:
• TRE RTFI: Harvest Production Monitoring & Control
• In-Vehicle Harvesting Head control system
• PDA or Large screen tablet (10+ inches)
• 3 parts: Map, Function menu, Widget menu
Main Functionalities:
• Map & Function menu: similar to mobile
• Widget menu:
• Quality Index: currently processed log quality
• Operation: to access scheduled operations
• Manage work time: set break intervals, optimize scheduling based on conditions
• Report issue: like failure/breakage, emergency call, etc.
• Work time clock: time left before break
• Climate and weather information: like weather forecast

48. Mid-term Review
2/Jul/15
HMI Design – In-Vehicle
Widget menuReal-time quality index
Function menu
Map

49. Mid-term Review
2/Jul/15
HMI Design – ERP Module
• Separated interconnected views
• 1 unique portal
• Management of log inventory
• Online purchasing/auctions
• For wood buyers/sellers and
sawmills
• One web interface with different
views and modules

50. Mid-term Review
2/Jul/15
Conclusions
• Guidelines for the definition of the SLOPE project interfaces
• Web
• Mobile
• In-vehicle
• Integrated ERP system
• Based on:
• State of the art
• Use cases
• Explicit requirements
• Subject to changes during the integration phase
• User requirements
• Integration testing feedbacks

51. Mid-term Review
2/Jul/15
Contact info
Daniele Magliocchetti: daniele.magliocchetti@graphitech.it
Giulio Panizzoni: giulio.panizzoni@graphitech.it
Thank you for your attention

52. Mid-term Review
2/Jul/15
Project SLOPE
T1.04– Mountainous Forest inventory data
model definition
WP 1 - Definition of requirements and system
analysis
Brussels, July 2th, 2015

53. Mid-term Review
2/Jul/15
Overview
• Status: Completed (100%)
• Length: 4 Months (From M2 to M6)
• Involved Partners
• Leader: CNR
• Participants: GRAPHITECH, COAST, MHG, BOKU, FLY, GRE, TRE
• Aim: To define the required information for the FIS data
population. Define data and metadata model of the FIS
• Output: D.1.03 [M6]

54. Mid-term Review
2/Jul/15
Data formats and standards
Spatial Data
Standards for Openness and Technical Interoperability – INSPIRE
Spectral data
Data collected by the harvesting machines
Sensor standards
Forestry related standards
Automatic Identification and data capture
Standards in Entity Identification
Geographic Standards

55. Mid-term Review
2/Jul/15
Data formats and standards
Spatial Data
several typologies of spatial data
and
different source of geographic information
Spectral Data
spectroscopy for the analysis of wood
chemical-physical properties,
hyperspectral imaging of wood,
hyperspectral imaging of forest.

56. Mid-term Review
2/Jul/15
Data formats and standards
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.

57. Mid-term Review
2/Jul/15
Integrated models
Multisource data
Multiscale data
Multitemporal data
The realization of forest inventories is strongly
related to the harmonization of different data
provided by different sources (different remote
sensing or ground-based measurements) with
different scales (different spatial and temporal
resolutions) and different units. This process
can be performed by means of dedicated
elaborations and databases with geographical
referencing functionalities (GIS).

58. Mid-term Review
2/Jul/15
Overview of existing databases
and services
• EU forest datasets
• Datasets available in the SLOPE pilot areas
ITALY–TrentoProvince
AUSTRIA–Salzburg

59. Mid-term Review
2/Jul/15
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)

60. Mid-term Review
2/Jul/15
Annex A:
TABLES OF DATASETS FOR FIS POPULATION
TABLE A1: FOREST

61. Mid-term Review
2/Jul/15
Annex A:
TABLES OF DATASETS FOR FIS POPULATION
TABLE A 2: INFRASTRUCTURES AND BUILDINGS TABLE A 3: HYDROGRAPHY
TABLE A.5: RISK FACTORS
TABLE A.5: COMMUNICATION

62. Mid-term Review
2/Jul/15
Annex B:TABLES OF DATA ON FOREST
PRODUCTION QUALITY AND AVAILABILITY

63. Mid-term Review
2/Jul/15
Annex C:
TABLES OF DATA DERIVED FROMTHE FIS

64. Mid-term Review
2/Jul/15
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 (T 5.01)
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).

65. Mid-term Review
2/Jul/15
Contact info
Thank you for your attention
Mariapaola Riggio: riggio@ivalsa.cnr.it

66. Mid-term Review
2/Jul/15
Project SLOPE
WP1 T1.5 - System Architecture
Brussels, 2nd July, 2015

67. Mid-term Review
2/Jul/15
Overview
• Status: Completed (100%)
• Length: 11 Months (From M02 to M12)
• Involved Partners
• Leader: MHG
• Participants: GRAPHITECH, FLY, TRE, ITENE
• Aim: Design the technology specification of system architecture
• Output: D.1.05 System architecture specifications

68. Mid-term Review
2/Jul/15
Objectives
• 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

69. Mid-term Review
2/Jul/15
Deliverable in brief
Specify existing applications and technologies
• 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
-> Architecture should support many different
kind of technologies

70. Mid-term Review
2/Jul/15
Deliverable in brief
Specify architecture design model to be used
• Specifies design principles are used in the SLOPE
platform architecture
• Service oriented architecture
• With SOA we can loosely integrate very
different systems together
• Goal is to make integrations with minimum
modifications to exsisting codebases
• Architecture diagrams

71. Mid-term Review
2/Jul/15
Deliverable in brief
Specify integration technologies
• 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

72. Mid-term Review
2/Jul/15
Deliverable in brief
Specify deployment platform for the SLOPE
• Describes the 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 for deployment

73. Mid-term Review
2/Jul/15
System Architecture Overview

74. Mid-term Review
2/Jul/15
Component Diagram

75. Mid-term Review
2/Jul/15
Summary
• Deliverable can be found from SLOPE Dropbox folder
• Feedback and communication delays affected to the delivery time. This didn’t affect
to execution of another tasks.
• All objectives were reached that are in the DOW.
• Deliverable specifies technologies, architecture model, partner applications,
integration patterns and slope deployment platform.
• System architecture specification can be updated during project
• Specified system architecture brings good guidelines/framework for SLOPE FIS
development

76. Mid-term Review
2/Jul/15
Mid-term Review
2/Jul/2015
Contact info
Veli-Matti Plosila veli-matti.plosila@mhgsystems.com
Seppo Huurinainen seppo.huurinainen@mhgsystems.com
Thank you for your attention