2nd Technical Meeting - WP1

Project SLOPE1

WP 1 Definition of requirements and system analysis

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

WP1. Objectives


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

WP1 Orginal timeline and WP1 situation M01-M06

January February March April May June

ITENE: 100%Task 1.1: D1.01UsersRequirementsReportKESLA: 80%Task 1.2: D1.04TechnicalRequirementsReport

Project meeting in

Mikkeli

GRAPHITECH: 80%Task 1.3: D1.02HumanMachine Interface

CNR: 80%Task 1.4: D1.03Data and Meta Data modelReportMHG: 60%Task 1.5: D1.05System ArchitectureSpecifications


WP1 And how did it go M01-M09

Jan Feb Mar Apr May Jun Jul Aug Sep

ITENE:Task 1.1: D1.01UsersRequirementsReport

Project meeting in

Mikkeli

GRAPHITECH:Task 1.3: D1.02HumanMachine Interface

MHG:Task 1.5: D1.05System ArchitectureSpecifications


CNR:Task 1.4: D1.03Data and Meta Data modelReport

KESLA GRAPHITECH :Task 1.2: D1.04TechnicalRequirementsReport

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 slopeplatform

D1.05 System Architecture Specifications Sepcifies technical architecture of the platform (high level

specification). Describes partner applications and technologies.


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


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! Lets move to task leader presentations

TASK 1.4Mountainous Forest inventory

data model definition

Work Package 1: Definition of requirements and system analysis

Work Package 1: Definition of Requirements and

System Analysis

Starting : January 2014Ending: 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

Task 1.4: Mountainous Forest inventory data model definition

Task Leader: CNRTask 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 2014Estimated person Month= 13.50

Task Leader 1 2 3 4 5 6 7 8 9 10 11 12

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 modeldefinition

CNR

1.5 System Architecture MHG

Task 1.4:ScheduleTask Leader: CNRTask 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.

Steps19/05 First version release23/06 Second version release30/06 Third version/first issue30/07 Revision of document reviewed22/09 Completed and Validated Deliverable Document

Task 1.4:TOC

1 Introduction2 Data formats and standards3 Integrated models4 Overview of existing databases/services5 Required information to populate the Forest Inventory System

Annex A: TABLES OF DATASETS FOR FIS POPULATIONAnnex B: TABLES OF DATA ON FOREST PRODUCTION QUALITY AND AVAILABILITYAnnex C: TABLES OF DATA DERIVED FROM THE FIS

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.

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.

Data collected by the harvesting machinesRelevant 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 machines parameters, enabling security, energy-saving, real-time control and automation functionalities. Some machines 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.

Overview of existing databases/services

EU forest datasets

Datasets available in the SLOPE pilot areas

ITAL

Y

Tren

to P

rovi

nce

AUST

RIA

Sal

zbur

g

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)

Annex A:TABLES OF DATASETS FOR FIS POPULATION

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

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

Annex C: TABLES OF DATA DERIVED FROM THE FIS

TABLE C.1- HARVESTING OPERATIONS

TABLE C.2- ASSORTMENTS

TABLE C.3- INFRASTRUCTURE CONDITIONS

TABLE C.4- PERFORMANCE INDICATORSOF THE SUPPLY CHAIN

ConclusionsReport D1.03 is a reference for the implementation of:

D2.01 Remote Sensing data and analysisD2.02 UAV data and analysis D2.03 TLS data and analysis

D2.04 the Harvest simulation toolD2.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).

2 Meeting July/2014

Thanks to:

CONTRIBUTORS and REVIEWERS:

Juan de Dios Diaz (ITENE)Barbara Hinterstoisser (BOKU)Enda Keane (Treemetrics)Martin Khmaier (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)

SLOPEIntegrated proceSsing and controL systems fOr sustainable forest Production in mountain arEas


Deliverable Number D.1.04Technical Requirement Report

WP 1 Definition of requirements and system analysisTask 1.2 Hardware and equipment definition


Typical Supply Chain


SLOPE supply chainForest stand

Cable corridor Landing Road

Location

Processes

Hardware

Forest survey Marking Felling

Extracting Processing Transporting

Satellite imagesUAVTLS

RFID Chain sawGPS

Tower yarderCarriage

ExcavatorHarvester headControl system

Analysis equipment (sensors)

TruckRFIDGPS

Tracking

RFID, NFC, UHF, GPS etc.

Location

Processes

Hardware

Tracking

RFID, NFC, UHF, GPS etc.


Data flow

Data flow between SLOPE system

components


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?

Device

Description

Intermec Large Rigid UHF RFID Tag

Rugged encapsulation for harsh environments

Consistent UHF range performance worldwide

Available with Gen 2 and ISO 18000-6B silicon

Confidex Ironside micro

EPC Class1 Gen2 (ISO 18000-6C) compliant passive on-metal tag Read range: up to 5m / 16 ft. Memory:

128bit EPC + 512 bit. Dimensions: 27 x 27 x 5,5 mm

1,06 x 1,06 x 0,22 inch. Ambient temperature: -35C to +85C. -31F to +185F

Confidex Ironside

PC Class1 Gen2 (ISO 18000-6C) compliant passive on-metal tag. Read range: up to 9m / 30 ft. Memory: 128bit EPC + 512bit. Dimensions: 51,5 x 47,5 x 10 mm. 2,03 x 1,87 x 0,39 inch. Ambient temperature: -55C to +105C. -67F to +221F. Peak 1h duration:+125C to +257F



Some lacks in the definition of the portable devices for in forestoperation:

Need of a portable reader?

Bluetooth communication with tablet devices?

Need enanched GPS location?



These portable readers has been identified for the activities on the landing area, can be used also in the forest activities?.

Device

Description

IP30 Handheld RFID Reader

EPCglobal UHF Gen 2, ISO 18000-6b, ISO 18000-6c

RFID Frequency Ranges: 865, 915, and 950 MHz bands, supporting multiple regional configurations

Bluetooth and USB configurations (model dependent)

ATID AT870

13.56 MHz HF and 868 MHz UHF RFID

3.5 touch screen

Windows CE 5.0 operating system.

Dimensions: 146x74x26 mm

Weight: 270-330 g (depending on options)

Protection: IP54

GPRS,

GPS,


Processor Head


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 sensor4. Camera/3D vision sensor5. Colour camera(s) scanning

side of the log6. Ultrasound stress wave

velocity scanner7. RFID reading system8. Data fusion/control unit

Processor Head


Cable Way and Self Propelled Carriage

Description of the hardaware, the neededimprovment related to SLOPE project have to be defined.


Smart Truck Hardware Specifications


Not completely solved issues

Portble devices for on-field operationand for hervesting operation.

Black-box

WP1 T1.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 allAdige19 -21 January 2015

T1.5 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

T1.5 Deliverable in brief


Describes each partners 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.



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



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



Specifies deployment platform Use neutral, scalable cloud service for

deployment (not inside any partners secure infrastructure)

This helps to open access for every partner that needs

Jelastic PaaS-platform is good option for deployment (MHG will test this)


System Architecture Overview


Component Diagram


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!

Project SLOPEWP1. Definition of Requirements and System ArchitectureWP1. ObjectivesWP1 Orginal timeline and WP1 situation M01-M06WP1 And how did it go M01-M09WP1 DeliverablesWP1 ProblemsWP1 SummarySlide Number 9Slide Number 10Slide Number 11Slide Number 12Slide Number 13Slide Number 14Slide Number 15Slide Number 16Slide Number 17Slide Number 18Slide Number 19Slide Number 20Slide Number 21Slide Number 22Slide Number 23TASK 1.4Mountainous Forest inventory data model definition Work Package 1: Definition of Requirements and System AnalysisTask 1.4: Mountainous Forest inventory data model definition Task 1.4:ScheduleTask 1.4:TOCSpatial dataSpectral dataData collected by the harvesting machinesOverview of existing databases/services Required information to populate the FIS Annex A:TABLES OF DATASETS FOR FIS POPULATION Annex A:TABLES OF DATASETS FOR FIS POPULATION Annex B: TABLES OF DATA ON FOREST PRODUCTION QUALITY AND AVAILABILITYAnnex C: TABLES OF DATA DERIVED FROM THE FIS Slide Number 38Slide Number 39 SLOPEIntegrated proceSsing and controL systems fOr sustainable forest Production in mountain arEasTypical Supply ChainSLOPE supply chainData flowTree marking and taggingTree marking and taggingTree marking and taggingProcessor HeadProcessor HeadCable Way and Self Propelled Carriage Smart Truck Hardware Specifications Not completely solved issuesWP1 T1.5 - System ArchitectureT1.5 ObjectivesT1.5 Deliverable in briefT1.5 Deliverable in briefT1.5 Deliverable in briefT1.5 Deliverable in briefT1.5 Deliverable in briefSystem Architecture OverviewComponent DiagramSummary

Education

2nd Technical Meeting - WP1