1st Technical Meeting - WP1
-
Upload
slope-project -
Category
Education
-
view
174 -
download
0
Transcript of 1st Technical Meeting - WP1
Project SLOPE1
WP 1– Definition of requirements and system analysis
Project SLOPE2
T 1.1 – User requirements
Mikkeli, July 02th, 2014
Scope3
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
Deliverable Index4
Revision History5
Process6
1. Identifying usergroups
2. Defining SLOPE functionalities
3. Creatingrelation matrix
4. Developingquestions fromfunctionalities
5. Finalisedquestionnaires
6. Contacts withend users
7. Analysis of results
Use Cases7
Biomass Processing Companies
Number of questionnaires8
Total: 23 questionnaires
Locations: Austria, Italy (Trento), Finland, Ireland
Specifications9
PlanningFor selecting a harvesting area, the system should:
Consider cost and demand as a factor to select a harvesting areaDetermine the volume of timber available in the harvesting zoneAllow to know the age of treesMeasure tree’s heightDetermine slope and roughness of the terrainDetermine accessibility of the zone (road placement…)
For marking a tree, the system should:Measure dimensions of treesDetermine quality of woodRegister specie and age of treesBe able of read all this information just before marking a treeIdentify trees unmistakably
Specifications10
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.
Specifications11
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.
ExploitationFor 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.
Specifications12
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.
Specifications13
Information and Sales moduleFor 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
Annex14
16
Thanks for your attention!!!
Project SLOPE17
T 1.2 - Hardware and equipment definition
• Tracking systems (ITENE)
Mikkeli, July 2th, 2014
Truck18
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 INTERMEC4 external antennasEthernetSerial PortISO 18000-6CEPC Class 1 Gen 212V DC, 30W4 input, 4 outputs
MCU (rpi)EthernetUSBSerial port (UART)GPS and GPRS (through board SIM908)GPIOHDMI512M RAM
BRI commands
XML
RFID Reader19
Tree Marking20
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 CAENIP54USB, BluetoothISO 18000-6CEPC Class 1 Gen 2
L9 from LG BluetoothNFC (not needed)
Crane21
CraneCrane
Commercial RFID Fixed UHF
CRANERS232 /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 INTERMEC4 external antennasEthernetSerial PortISO 18000-6CEPC Class 1 Gen 212V DC, 30W4 input, 4 outputs
BRI commands
XML
Processor22
ProcessorProcessor
Commercial RFID Fixed UHF
ProcessorRS232 /ethernet
SLOPE FIS SystemGPRS
Need to be programmed to control reader and to
store / send received dataBRI comands
In charge: GRE?
Need to be programmed to receive and store data
In charge: MHG?Leads WP5 FIS Development
Commercial Firmware
IF2 from INTERMEC4 external antennasEthernetSerial PortISO 18000-6CEPC Class 1 Gen 212V DC, 30W4 input, 4 outputs
BRI commands
XML
SLOPEIntegrated proceSsing and controL systems fOr sustainable forest Production in mountain arEas
Technical Meeting 2-4/Jul/2014
WORK PACKAGE 1: DEFINITION OFREQUIREMENTS AND SYSTEM ANALYSIS
TASK: 1.3 HUMAN MACHINE INTERFACE (HMI) DEFINITION
THEME: Integrated processing and Control Systems forSustainable Production in Farms and ForestsDuration: 36 MonthsPartners: 10Coordinating institution: Fondazione GraphitechCoordinator: Dr. Raffaele De Amicis
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
Task Overview
Technical Meeting 2-4/Jul/2014
Start: February 2014End: April 2014Leader: GRAPHITECHPartners: 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.
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.”
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
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
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
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
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
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
HMI Use Cases – Desktop Forest Op.
HMI Use Cases – Desktop Forest Pl.
HMI Use Cases – Mobile On The Field Harvesting Operator and Forestry Expert
HMI Use Cases – In-Vehicle Cable and Truck Operators
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
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
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
HMI Design - Desktop
Main Functionalities:• Analytics: set of tools to retrieve geometrical and geophysical (like
slopeness and soil components) information about the property and aboutthe places of interest for determined operation or dataset
• Operation: tools to manage different operation related to harvesting and toplan them in determined temporal interval
• Forest: Tools to inspect the forestry inventory datasets and all the operationrelated to forest resource planning.
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
HMI Design - Desktop - Analytics
Measure, distances, areas, etc.
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
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
HMI Design – Desktop - Operation
It’s possible to set upthe cable waydragging thecomponent directlyto the map and settheir parameters.
Set all theparameters ofthe cablewaythrough acontextualmenu
Retrieve infos about every cable line in the forest area for the date selected
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
HMI Design – Desktop - Forest
Information of the tree to support the marking decision
Select the marktypologyto make
Highlight Selection
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).
HMI Design – Mobile – Forest Operator
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
HMI Design – In-Vehicle
Real-Time Sensor DataTree Marked Data
Enriched Map
Quality Index Estimation
Harvesting Head Control System TREE RTFI
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
Technical Meeting 2-4/Jul/2014
Open Discussion
Technical Meeting 2-4/Jul/2014
Thank you for your attention
DANIELE MAGLIOCCHETTI
Fondazione GraphitechVia Alla Cascata 56C38123 Trento (ITALY)
Phone: +39 0461.283395Fax: +39 0461.283398
SLOPE WP 1 – Task 1.4
Task leader: Mariapaola Riggio, PhDCNR IVALSA
Mountainous Forest inventory data model defini=on
Task 1.4: participants
• CNR (Task Leader)
•Graphitech
• Coastway
• Flyby S.r.l.
•TreeMetrics
•BOKU
•MHG
•Greifenberg
Task 1.4: general descriptionAIMs:
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 TreemetricsUse resulFng data and metadata modelas base schema for the mountainousforest informaFon system database.
All the partnersDefine the data andmetadata for the specific field of applicaFon (3D forest model, characterizaFon of the forest and of the forest producFon, harvesFng process)
ParFcipants Role
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 July 2014
D1.0.3 / Table ofContents
123456
Introduc=onData formats and standards Integrated modelsOverview of exis=ng databases/servicesRequired informa=on to populate the Forest Inventory System References
Annex A:Tables of datasets for FIS popula2onAnnex B:Tables of data on forest produc2on quality and availabilityAnnex C:Tables of data derived from the FIS
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
Chapter 2 :Data formats and standards
Spa2al DataAnalysing 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.
Chapter 2 :Data formats and standards
Spectral DataSeveral 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 arecovered in this secFon: spectroscopy for the analysis of wood chemical--physical properFes, hyperspectral imaging of wood, hyperspectral imaging of forest.
Chapter 2 :Data formats and standardsData 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’sparameters, enabling security, energy--saving, real--Fme control and automaFon funcFonaliFes. Some machine’s parameters will be also correlated to quality indices of the harvested material (e.g. cudng quality index).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.
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).
Chapter 4 :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
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)
Annex A:TABLES OF DATASETS FOR FIS POPULATION
TABLE A1: FOREST
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
Annex B: TABLES OF DATA ON FOREST
PRODUCTION QUALITY ANDAVAILABILITY
Annex C:TABLES OF DATA DERIVED FROM THE FIS
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 analysisD2.03 TLS data and analysis
D2.04 the Harvest simulaFon toolD2.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--sensor characterizaFon 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).
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)
Mariapaola Riggio, PhD CNR--IVALSANaFonal Research Council of Italy Trees and Timber InsFtuteVia Biasi 75, 38010 San Michele all'Adige (TN) ItalyTel. +39 0461 660232Fax. +39 0461 650045E.mail:[email protected]
Thanks!
Month 6 Meeting 2-4/july/2014
D1.04 Technical requirements report
Fleet management systems
Kühmaier M, Holzleitner FInstitute of Forest EngineeringUniversity of Natural Resources and Life Sciences, Vienna
2 July 2014
Mikkeli Meeting 2-4/july/2014
WP1 Hardware
Separation of Point Cloud to aid creation of DEM by classifying ground data from canopy data
The Products
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cmPulp
7cmPulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
• Taper Variation• Straightness• Branching• Rot etc.
The Products: General Values
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cmPulp
7cmPulpPulp = €20 per M3
Large Sawlog = €60 per M3
Small Sawlog = €40 per M3
The Problem - “The Collision of Interests”
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cmPulp
7cmPulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
Maximise Value
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cmPulp
7cmPulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cmPulp
7cmPulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
3.7mOption 1
Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cmPulp
7cmPulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
3.7mOption 1
Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cmPulp
7cmPulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
4.3mOption 2
Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cmPulp
7cmPulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
4.3mOption 2
Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cmPulp
7cmPulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
4.9mOption 3
Maximise Value: Sawlog Lengths
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
7cm
14cm
16cm
7cm7cmPulp
7cmPulpPulp M3?
Large Sawlog M3?
Small Sawlog M3?
4.9mOption 3
Harvester Optimisation
Log Quality: Straightness (Sweep), Taper, Branching ,Rot,
Our Offering
Forest Mapper - First In The World – Online Forest Mapping & Analysis - Data Management System
Forest Mapper: Automated net area calculation, stratification and Location for ground sample plots to be collected
Sample Plots
Net Area
Stratification
(Inventory Planning)
Terrestrial Laser Scanning Forest Measurement System(AutoStem Forest)
Automated 3D Forest Measurement System
Trusted and Independent Data
Forest Valuation: Online Data
Current Forest Value
Mobile Field Survey App – Report Sharing -Interconnectivity
Latest Development
• Online Market Place• 15,000 forest owners• Irish Farmers Association
WP1 T1.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
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
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
Kick-off Meeting 8-9/jan/2014
System Architecture Overview
Kick-off Meeting 8-9/jan/2014
System Architecture Overview
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)
Kick-off Meeting 8-9/jan/2014
Example of Liferay integration
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.
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.
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!
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
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
WP1 Orginal timeline and WP1 situation– M01-M06
January February March April May June
ITENE:Task 1.1: D1.01UsersRequirementsReportKESLA:Task 1.2: D1.04TechnicalRequirementsReport
Project meeting in
Mikkeli
GRAPHITECH:Task 1.3: D1.02HumanMachine Interface
CNR:Task 1.4: D1.03Data and Meta Data modelReportMHG:Task 1.5: D1.05System ArchitectureSpecifications
Mikkeli 02-04 July 2014
WP1 Task 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
WP1 Task 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
WP1 Task 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
WP1 Task 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
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
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.