- Weather - Production Targets - Contingency Plans Harvesting Head Control Interface Production Statistics Machine Parameters Tree Detection & Recognition SLOPE In-Vehicle Interface Machine Monitoring Route Planning Cable Crane Control Risks and Mitigation Actions Technical Meeting 2-4/Jul/2014 Risks: - Integration with existing systems (MHG, TREE) not seamless - Mobile/In-Vehicle interfaces not robust enough for field conditions - User acceptance of new interfaces Mitigation Actions: - Early prototyping and testing with end users - Modular design allowing independent development

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

2. Project SLOPE
2
T 1.1 – User requirements
Mikkeli, July 02th, 2014

3. Scope
3
 This task aimed to:
 Identify users that will use SLOPE tools
 Understand their needs of SLOPE
 Understand the system requirements so it is useful for users
 Status: Finished
 Al information included in “D1.01 user requirements report”
 Finished.
 Partners involved: all
 ITENE (leader), GRAPHITECH, CNR, KESLA, COAST, MHG,
BOKU, FLY, GRE, TRE

4. Deliverable Index
4

5. Revision History
5

6. Process
6
1. Identifying user
groups
2. Defining SLOPE
functionalities
3. Creating
relation matrix
4. Developing
questions from
functionalities
5. Finalised
questionnaires
6. Contacts with
end users
7. Analysis of
results

7. Use Cases
7
 Biomass Processing Companies

8. Number of questionnaires
8
 Total: 23 questionnaires
 Locations: Austria, Italy (Trento), Finland, Ireland

9. Specifications
9
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

10. Specifications
10
 For cable corridors placing, the system should:
 Allow the estimation of total amount of timber to be harvested.
 Consider the slope of the cable.
 Allow the selection of the intermediate support.
 For landing placement determination, the system should:
Measure and locate available extensions for landing.
In order to obtain cost estimations, the system should:
 Calculate costs of harvesting, cable corridor installation and
marking of tress.
 Integrate individual costs related to machine, labour, overhead,
transport, infrastructures costs and others like clearing meadows or
watersides, artificial anchors, locking public roads.

11. Specifications
11
 For planning a forest road, the system should:
 Determine access points to the forest area.
 Estimate the amount of timber available.
 Consider other activities in the forest beneficiaries of the construction.
 Calculate necessary parameters of the road: width, layers, curve radio,
maximum longitudinal slope and maximum transversal slope.
Exploitation
For harvesting monitoring and tree identification, the system should:
 Obtain and predict the weather conditions.
 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.

12. Specifications
12
For define traceability, the system should:
 Determine main characteristics of logs and locate them in the
forest.
 Have a complete traceability system (all stages) or at least extend
traceability to transport activities (outside the forest).
 Update data with a desirable minimum frequency of 10 minutes.
For developing contingency plans, the system should:
 Predict possible failures or breakages
 Obtain and predict the weather conditions.

13. Specifications
13
Information and Sales module
For implementing online purchases, the system should:
 Measure dimensions of logs and humidity
 Determine quality of wood
 Register species of trees
 Develop a platform including mentioned characteristics and specifying
provenance of logs.
For inventory logs, the system should:
 Identify logs in different states (standing, ready to be harvested or harvested)
 Determine accessibility of the zone (road placement…)
 Determine quality of wood
For demand determination, the system should:
 Measure dimensions of logs and humidity
 Determine quality of wood

14. Annex
14

15. Contact info
15
 Juan de Dios Díaz
 juan.diaz@itene.com
 Emilio Gonzalez
 egonzalez@itene.com

16. 16
Thanks for your attention!!!

17. Project SLOPE
17
T 1.2 - Hardware and equipment definition
• Tracking systems (ITENE)
Mikkeli, July 2th, 2014

18. Truck
18
TruckTruck
Commercial RFID Fixed
UHF
Truck with a Control Unit
RS232 /
ethernet
SLOPE FIS SystemGPRS
Need to be programmed to
control reader, to measure
GPS and send data GPRS
In charge: ITENE
Need to be programmed to
receive and store data
In charge: MHG?
Leads WP5 FIS
Development
Commercial Firmware
IF2 from INTERMEC
4 external antennas
Ethernet
Serial Port
ISO 18000-6C
EPC Class 1 Gen 2
12V DC, 30W
4 input, 4 outputs
MCU (rpi)
Ethernet
USB
Serial port (UART)
GPS and GPRS (through
board SIM908)
GPIO
HDMI
512M RAM
BRI commands
XML

19. RFID Reader
19

20. Tree Marking
20
Tree Marking
Commercial RFID
handheld UHF
Smartphone
Base station with wifi
installed in forest
BLUETOOTH
WIFI SLOPE FIS SystemGPRS
Need to be programmed /
developed
In charge: CNR?
Leads 3.1 Tree Marking
Software included
Need an app to be
programmed
In charge: CNR?
Leads 3.1 Tree Marking
GPRS
Need to be programmed to
receive and store data
In charge: MHG?
Leads WP5 FIS
Development
C-qID from CAEN
IP54
USB, Bluetooth
ISO 18000-6C
EPC Class 1 Gen 2
L9 from LG
Bluetooth
NFC (not needed)

21. Crane
21
CraneCrane
Commercial RFID Fixed
UHF
CRANE
RS232 /
Ethernet
SLOPE FIS SystemGPRS
Need to be programmed to
control reader and to
store / send received data
In charge: GRE?
Leads 3.3 intelligent crane
Need to be programmed to
receive and store data
In charge: MHG?
Leads WP5 FIS
Development
Commercial Firmware
IF2 from INTERMEC
4 external antennas
Ethernet
Serial Port
ISO 18000-6C
EPC Class 1 Gen 2
12V DC, 30W
4 input, 4 outputs
BRI commands
XML

22. Processor
22
ProcessorProcessor
Commercial RFID Fixed
UHF
Processor
RS232 /
ethernet
SLOPE FIS SystemGPRS
Need to be programmed to
control reader and to
store / send received data
BRI comands
In charge: GRE?
Need to be programmed to
receive and store data
In charge: MHG?
Leads WP5 FIS
Development
Commercial Firmware
IF2 from INTERMEC
4 external antennas
Ethernet
Serial Port
ISO 18000-6C
EPC Class 1 Gen 2
12V DC, 30W
4 input, 4 outputs
BRI commands
XML

23. SLOPE
Integrated proceSsing and controL systems fOr sustainable forest Production in mountain arEas
Technical Meeting
2-4/Jul/2014
WORK PACKAGE 1: DEFINITION OF
REQUIREMENTS AND SYSTEM ANALYSIS
TASK: 1.3 HUMAN MACHINE INTERFACE (HMI) DEFINITION
THEME:
Integrated processing and Control Systems for
Sustainable Production in Farms and Forests
Duration: 36 Months
Partners: 10
Coordinating institution: Fondazione Graphitech
Coordinator: Dr. Raffaele De Amicis

24. Technical Meeting
2-4/Jul/2014
Agenda
• Tasks Overview
• User Interface Analysis
• User Interface Requirements
• From D.1.1
• Use Cases
• Human Machine Interfaces
• Desktop, Mobile, In-Vehicle
• Risks and Mitigation Actions
• Questions

25. Task Overview
Technical Meeting
2-4/Jul/2014
Start: February 2014
End: April 2014
Leader: GRAPHITECH
Partners: KESLA, MHG, GRE, RTE, ITENE
Define user interface for the whole SLOPE system:
• Specify user interface needs
• Specify web user interface requirements
• Specify user interface in-vehicle and on field devices
The FIS will be accessed and edited using several devices (mobile, web, in-vehicle unit) into different conditions (office planning, on field
harvest operation). Due to these very wide requirements a detailed investigation of the possible interactions and of the design of the
different machine interfaces should be performed specially in terms of views and usability. The aim is to create demos from specified
views, in different conditions and purposes. Particular attention will be paid to the mobile and on vehicle interface for ease of access and
usability into on-field conditions (GRAPHITECH). The mobile and web interface will be designed by MHG and TRE to allow forestry data
analysis and synthesis using charts, diagrams and maps on specific database views.

26. User Interface Analysis
Technical Meeting
2-4/Jul/2014
“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.”

27. User Interface Analysis
Technical Meeting
2-4/Jul/2014
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

28. User Interface Analysis
Technical Meeting
2-4/Jul/2014
Forestry Resource Planning System (MHG)
• Graphical user interface
• Web-based interface
• Touch user interface (Mobile)
Forest Analysis and Monitoring (TREE)
• Graphical User Interface
• Web-based user interface
• Touch User Interface (Mobile)
• Hardware Interface
• Batch Interface
Intelligent Harvesting Heads
• Graphical User interface
• Touch user interface (In-Vehicle)
• Intelligent user interface

29. User Interface Analysis
Technical Meeting
2-4/Jul/2014
Cable Crane System (GRE)
• Direct manipulation interface
• Hardware interface
• Task focused interface
Geographical Information System for Environmental Planning
(GRAPHITECH)
• Graphical User Interface
• Web-based Interface
• Touch User Interface (Mobile)
• Gesture Interface (Mobile)
• Task focused interface

30. User Interface Requirements
Technical Meeting
2-4/Jul/2014
• From user requirements report (D.1.1)
• Requirements list
• From reference SLOPE scenario
• HMI focused Use Case Diagrams
• By End User
• By Desktop/Mobile/In-Vehicle

31. User Interface Requirements
• 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

32. User Interface Requirements
• 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

33. HMI Use Cases – Desktop Forest Op.

34. HMI Use Cases – Desktop Forest Pl.

35. HMI Use Cases – Mobile OnThe Field
Harvesting Operator and Forestry Expert

36. HMI Use Cases – In-Vehicle Cable and
Truck Operators

37. 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 MHG and TREE platforms

38. HMI Design - Desktop
• Web based application (HTML5/WebGL Based or Java Applet)
• Final Technology TBD on T.1.5 System Architecture
• Can be easily included into MHG system as a Life-Ray widget
• TREE integration/connection to be understand
• Needs access to the SLOPE DB

39. HMI Design - Desktop
Menu bar with
common fucntions for
the Slope System like
editing or open/save
the project
Toolbar with the
different typology
of functions
Tools related to the
category of function
selected
Information
Hub. With data
about climate
and weather
Operation
Calendar
3D Area

40. HMI Design - Desktop
Main Functionalities:
• Analytics: set of tools to retrieve geometrical and geophysical (like
slopeness and soil components) information about the property and about
the places of interest for determined operation or dataset
• Operation: tools to manage different operation related to harvesting and to
plan them in determined temporal interval
• Forest: Tools to inspect the forestry inventory datasets and all the operation
related to forest resource planning.

41. HMI Design - Desktop - Analytics
Get information
and graphics
about slopeness
of the terrain
Inspect
Soil/Terrain
information
with graphics
and view on
the map
Boundaries
and Property
infos of the
forest area

42. HMI Design - Desktop - Analytics
Measure,
distances,
areas, etc.

43. HMI Design – Desktop - Analytics
View of the
Ground lidar
scan or images
of a POI
Inspect datasheet
and chart about a
forestry operation
area identified in a
determined point
of interest

44. HMI Design – Desktop - Operation
Road
construction
and set
property
boundary
Add a new
operation to the
scenario by
adding the actors
involved
Insert in the
scenario all the
structure to plan
the operation

45. HMI Design – Desktop - Operation
It’s possible to set up
the cable way
dragging the
component directly
to the map and set
their parameters.
Set all the
parameters of
the cableway
through a
contextual
menu
Retrieve infos
about every
cable line in the
forest area for
the date
selected

46. HMI Design – Desktop -Forest
Inspect resources
information for
standing/harvested tree
or from logs in the
forest area
Possibility to
inspect
information
about single tree
to help a more
accurated virtual
marking Inspect effeclty
physical tagged
tree and marked
virtually tree

47. HMI Design – Desktop - Forest
Information of the tree
to support the marking
decision
Select the mark
typology
to make
Highlight
Selection

48. HMI Design - Mobile
Main Functionalities:
• Subset of desktop functionalities
• Exploits mobile device capabilities (e.g. GPS, Camera)
• 2D (3D/AR modes optional)
• Tagging support for Forest Operators
• Can work in parallel with MHG and TREE mobile systems (Android
OS).

49. HMI Design – Mobile – Forest
Operator

50. HMI Design – In-Vehicle
Main Functionalities:
• Enrich already existing In-Vehicle systems
• Based on:
• TREE RTFI: Harvest Production Monitoring & Control
• In-Vehicle Harvesting Head control system
• Feasibility to be assessed
• To be finalized

51. HMI Design – In-Vehicle
Real-Time Sensor Data
Tree Marked Data
Enriched Map
Quality Index
Estimation
Harvesting Head Control System TREE RTFI

52. Risks and Mitigations
Pending Items
• D.1.2 Human Machine Interfaces To Be Completed
• 75% Completed
• Some Mock-ups Refinements Needed
• Mobile
• In-Vehicle
Remedial Actions
• D.1.2 Human Machine Interfaces Ready by 8.07.14
• Mock-ups revised by 8.07.14

53. Technical Meeting
2-4/Jul/2014
Open Discussion

54. Technical Meeting
2-4/Jul/2014
Thank you for your attention
DANIELE MAGLIOCCHETTI
daniele.magliocchetti@graphitech.it
Fondazione Graphitech
Via Alla Cascata 56C
38123 Trento (ITALY)
Phone: +39 0461.283395
Fax: +39 0461.283398

55. SLOPE WP 1 – Task 1.4
Task leader:
Mariapaola Riggio,
PhD
CNR IVALSA
Mountainous Forest inventory data model defini=on

56. Task 1.4: participants
• CNR (Task Leader)
•Graphitech
• Coastway
• Flyby S.r.l.
•TreeMetrics
•BOKU
•MHG
•Greifenberg

57. Task 1.4: general description
AIMs:
1. Define the required informa=on for the FIS data popula=on
2. Define data and metadata model of the FIS (integraFon of heterogeneous
data)
CNR and BOKU
Conceptualize the
informaFon into a
Forest InformaFon data
model, also considering
current standards and
best pracFce in forest
management
MHG and
Treemetrics
Use resulFng data
and metadata model
as base schema for
the mountainous
forest informaFon
system database.
All the partners
Define the data and
metadata for the specific
field of applicaFon (3D
forest model,
characterizaFon of the forest
and of the forest producFon,
harvesFng process)
ParFcipants Role

58. Task 1.4: delivered output
• Deliverable D1.03 (month 6 – June 2014) :
Data and Metadata Model Report
Report delivered on the 30th of June 2014
Final reviewed version will be issued on the 11th of July2014

59. D1.0.3 / Table ofContents
1
2
3
4
5
6
Introduc=on
Data formats and standards
Integrated models
Overview of exis=ng databases/services
Required informa=on to populate the Forest Inventory System
References
Annex A:
Tables of datasets for FIS popula2on
Annex B:
Tables of data on forest produc2on quality and availability
Annex C:
Tables of data derived from the FIS

60. Chapter 2 :
Data formats and standards
Spa2al Data
Standards for Openness and Technical Interoperability – INSPIRE
Spectral data
Data collected by the harves2ng machines
Sensor standards
Forestry related standards
AutomaEc IdenEficaEon and data capture
Standards in EnEty IdenEficaEon
Geographic Standards

61. Chapter 2 :
Data formats and standards
Spa2al Data
Analysing the SLOPE requirements, several
typologies of spa=al data are related to the
forest informaFon system. We can include: forest
and trees features, land parcels, road network
and landing areas sawmills posiFons, elevaFon
and slope of a certain region etc. How these
informaFon would be geometrically represented
and in relaFon to this, how they will be modelled
according to acquisiFon system used to retrieve
the informaFon?
In SLOPE project we will have different source of
geographic informa=on and each of these
produce different typologies of spaFal data,
which a`er a processing step will generate new
spaFal data.

62. Chapter 2 :
Data formats and standards
Spectral Data
Several typologies of spectral data are
related to the forest informaFon system.
We can include (rela=ng to the
characteriza=on scale): forest features,
single tree characterisFcs, log quality,
early ring properFes, sub structural
morphology of wood cell wall.
Various sources affect the spectral data
representaFon.
Different spectral analysis methods are
covered in this secFon: spectroscopyfor
the analysis of wood chemical-‐physical
properFes, hyperspectral imaging of
wood, hyperspectral imaging of forest.

63. Chapter 2 :
Data formats and standards
Data collected by the harves2ng machines Relevant variables, represenFng the
characterisFcs of the harvesFng 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-‐Fmecontrol and automaFon
funcFonaliFes. Some machine’s parameters will be also correlated to quality indices of
the harvested material (e.g. cudng qualityindex).
Another series of data are those collected by the sensors to determine parameters
related to the wooden material characteris=cs (i.e. data from NIR and hyperspectral
sensors, data from stress wave tests) or to measure geometrical features of the logs.

64. Chapter 3 :
Integrated models
Mul2source data
Mul2scala data
Mul2temporal data
The realizaFon of forest inventories is strongly
related to the harmoniza=on of different data
provided by different sources (different
remote sensing or ground-‐based
measurements) with different scales (different
spaFal and temporal resoluFons) and different
units. This process can be performed by means
of dedicated elaboraFons and databases with
geographical referencing funcFonaliFes (GIS).

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

66. Chapter 5 :
Required information to populate the FIS
to develop an interac2ve system for
cableway posi2oning simula2on (CwPT)
to assist tree marking – forestry
measurements es2ma2ons (TMT)
to define technology layers (harvest
parameters) (TLT)
to support novel inventory data
content (IDC)

67. AnnexA:
TABLESOF DATASETS FOR FIS POPULATION
TABLE A1: FOREST

68. AnnexA:
TABLESOF DATASETS FOR FIS POPULATION
TABLE A 2: INFRASTRUCTURES AND BUILDINGS TABLE A 3: HYDROGRAPHY
TABLE A.5: RISK FACTORS
TABLE A.5: COMMUNICATION

69. Annex B: TABLES OF DATA ON FOREST
PRODUCTION QUALITY ANDAVAILABILITY

70. AnnexC:
TABLESOF DATA DERIVED FROMTHEFIS

71. Conclusions
2° MeeFng
Report D1.03 is a reference for the implementaFon of:
D2.01 Remote Sensing data and analysis
D2.02 UAV data and analysis
D2.03 TLS data and analysis
D2.04 the Harvest simulaFon tool
D2.05 the Road and logisFc simulaFon module
Data and metadata model defined in the D1.03 will be the base for the implementaFon of
the mountainous forest informaFon system database (WP5)
The report D1.03 defines also data acquired by means of non-‐destrucFve or semi-‐
destrucFve tesFng techniques, for the mulF-‐sensorcharacterizaFon of the harvested
material. A prerequisite for this is the definiFon of the technical characterisFcs of the
hardware/sensors instrumenFng the harvesFng machines (Task 1.2 – D1.04).

72. Thanks to:
2° MeeFng
CONTRIBUTORS and REVIEWERS:
Juan de Dios Diaz (ITENE)
Barbara Hinterstoisser (BOKU)
Enda Keane (Treemetrics)
MarFn 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-‐Mad Plosila (MHG)

73. Mariapaola Riggio, PhD
CNR-‐IVALSA
NaFonal Research Council of Italy
Trees and Timber InsFtute
Via Biasi 75, 38010 San Michele all'Adige (TN)
Italy
Tel. +39 0461 660232
Fax. +39 0461 650045
E.mail:riggio@ivalsa.cnr.it
Thanks!

74. Month 6 Meeting
2-4/july/2014
D1.04Technical requirements report
Fleet management systems
Kühmaier M, Holzleitner F
Institute of Forest Engineering
University of Natural Resources and Life Sciences, Vienna
2 July 2014

75. Mikkeli Meeting
2-4/july/2014
WP1 Hardware
Separation of Point Cloud to aid creation of
DEM by classifying ground data from canopy
data

76. The Products
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cm
Pulp
7cm
PulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
• Taper Variation
• Straightness
• Branching
• Rot etc.

77. The Products: General Values
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cm
Pulp
7cm
PulpPulp = €20 per M3
Large Sawlog = €60 per M3
Small Sawlog = €40 per M3

78. The Problem - “The Collision of Interests”
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cm
Pulp
7cm
PulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?

79. Maximise Value
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cm
Pulp
7cm
PulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?

80. Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cm
Pulp
7cm
PulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
3.7mOption 1

81. Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cm
Pulp
7cm
PulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
3.7mOption 1

82. Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cm
Pulp
7cm
PulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
4.3mOption 2

83. Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cm
Pulp
7cm
PulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
4.3mOption 2

84. Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cm
Pulp
7cm
PulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
4.9mOption 3

85. Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cm
Pulp
7cm
PulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
4.9mOption 3

86. Harvester Optimisation

87. Log Quality: Straightness (Sweep), Taper,
Branching ,Rot,

88. Our Offering

89. Forest Mapper - First In The World – Online Forest
Mapping & Analysis - Data Management System

90. Forest Mapper: Automated net area calculation,
stratification and Location for ground sample plots
to be collected
Sample
Plots
Net Area
Stratification
(Inventory
Planning)

91. Terrestrial Laser Scanning Forest Measurement System
(AutoStem Forest)
Automated 3D Forest
Measurement System

92. Trusted and Independent Data

93. Forest Valuation: Online Data

94. Current Forest Value

95. Mobile Field Survey App – Report Sharing -
Interconnectivity

96. Latest Development
• Online Market Place
• 15,000 forest owners
• Irish Farmers Association

97. WP1T1.5 - System Architecture
Task leader: MHG
Deliverable: D1.05 System Architecture Specifications
Designed delivery time: M6
Deliverable status: In progress, 60% ready
Estimated delivery time: 31th July 2014
Situation: Draft is ready. Waiting partner’s input about integrations
and technologies. Interface specifications need to be done. Goal is
to finalize deliverable on July 2014.
Mikkeli
02-04 July 2014

98. T1.5 Objectives
Mikkeli
02-04 July 2014
• Design the technology specification of the system
architecture
• Specify applications and technologies to be used
• Use service oriented architecture design principles
• Design model and interfaces for application
integrations in different integration levels
• Design deployment platform

99. Kick-off Meeting
8-9/jan/2014
T 1.5 Key points of the design
• SLOPE architecture should respect SOA design
• Architecture should use open source technologies
• Partner’s applications should be easily integrated
to the SLOPE platform
• Maximal use of partner’s existing applications and
technologies
• Use flexible and agile integration technologies
• Use standards if available
• Use ready components if available

100. Kick-off Meeting
8-9/jan/2014
System Architecture Overview

101. Kick-off Meeting
8-9/jan/2014
System Architecture Overview

102. Kick-off Meeting
8-9/jan/2014
Presntation level integration
• Use Liferay application integration
strategies described in the
deliverable. Iframe, Web Proxy or
native Portlet integration.
• Publish new applications with
Liferay framework
• Map presentations (with
OpenLayers)

103. Kick-off Meeting
8-9/jan/2014
Example of Liferay integration

104. Kick-off Meeting
8-9/jan/2014
Data and application level level
integration
• Publish all needed interfaces to the
SLOPE FIS Database
• GeoServer for GIS services
• SOAP web services for data
integration implemented with Java
EE patterns.
• All communication should go
through services. No direct
database access.

105. Kick-off Meeting
8-9/jan/2014
Deployment platform
• Use cloud platform for deployment
• Deployment platform should be very
scalable and easy to configure
• SLOPE FIS could easily run for ex. on
Jelastic platform
• With Jelastic we can add more resources
on the fly
• SLOPE FIS can be also deployed to
standard virtual cloud server instance like
Amazon. But it needs more configuration.

106. Kick-off Meeting
8-9/jan/2014
Summary
• Task deliverable will be finalized on July-August 2014
• Deliverable is waiting for partners input
• Designed architecture will be very flexible and easy to understand
Thank you!

107. 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
• 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

108. 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

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

110. WP1Task 1.1 - Users and System
requirements
Task leader: ITENE
Deliverable: D1.01 Users Requirements Report
Designed deliverable time: M3
Deliverable status: Ready
Summary: No big issues. Delay from partner’s input. Finished
correctly. Deliverable can be found from final deliverables folder in
Dropbox.
Mikkeli
02-04 July 2014

111. WP1Task 1.2 - Hardware and
equipment definition
Task leader: KESLA (resigned from consortium on 25th May 2014)
Will be finalized by all partners with GRAPHITECH lead.
Deliverable: D1.04 Technical Requirements Report
Designed deliverable time: M3
Estimated delivery time: 11th July 2014
Deliverable status: In progress
Summary: Very late from the timetable. Task leader left from the
consortium. Anyway deliverable is in pretty good situation.
Partners will finalize this task together.
Mikkeli
02-04 July 2014

112. WP1Task 1.3 - Human Machine
Interface (HMI) definition
Task leader: GRAPHITECH
Deliverable: D1.02 Human Machine Interface
Designed delivery time: M4
Deliverable status: In progress, 80% ready
Estimated delivery time: 7-8 July 2014
Summary: Late but almost ready. 2 months in delay due to initial
lack of feedbacks from some partners.
Mikkeli
02-04 July 2014

113. WP1Task 1.4 - Mountainous Forest
inventory data model definition
Task leader: CNR
Deliverable: D1.03 Data and Meta Data model Report
Designed delivery time: M6
Estimated delivery time: 11th July 2014
Deliverable status: In progress, 80% ready
Summary: Final version will be ready on the 11th of July, after the
meeting in Mikkeli, where some technical issues will be discussed.
It is fundamental to receive feedback of the involved partners in
time.
Mikkeli
02-04 July 2014

114. WP1 1.5 - System Architecture
Task leader: MHG
Deliverable: D1.05 System Architecture Specifications
Designed delivery time: M6
Deliverable status: In progress, 60% ready
Estimated delivery time: 31th July 2014
Summary: Draft is ready. Waiting partner’s input about
integrations and technologies. Goal is to finalize deliverable on July
2014.
Mikkeli
02-04 July 2014

115. Kick-off Meeting
8-9/jan/2014
WP1 Summary
• Will be finished in July 2014
• Partner’s input and active communication is needed to finalize
all tasks correctly!
Thank you! Let’s move to task leader presentations.