2. Technical Meeting
19-21 Jan 15
Agenda
• Work Package Goals
• Tasks and Roles Overview
• Timeline
• Deliverables
• Task Details
• Risks and Mitigation Actions
• Open Discussion
3. Technical Meeting
19-21 Jan 15
Work Package Goals
“Achieve a complete integration of the different components that are part of
the SLOPE platform”
WP 2 Components
Forest information
collection and analysis
COA,FLY,GT,ITE,TRE
WP 3 Components
Integration of novel
intelligent harvesting systems
CNR,GRE,KES,ITE,MHG
WP 5 Components
Forest information
system development
CNR,TRE,BO
WP6 Integration (All Partners)
SLOPE PLATFORM
4. Technical Meeting
19-21 Jan 15
Work Package Key aspects
• Build a working system
• Ready for pilots and on the field testing
• Based on 3 integration steps
• Technical and Economical Analysis
• Overall solution costs
• Social impacts
• Environmental impacts
T.6.2
T.6.3
T.6.4
6. Technical Meeting
19-21 Jan 15
Timeline & Deliverable & Milestone & Project Meetings
2014 2015 2016
J F M A M J J A S O N D J F M A M J J A S O N D J F M A M J J A S O N D
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
WP 6 System Integration
T.6.1 Definition of the integration steps
T.6.2 First Integration – Forest inventory & harvesting systems
T.6.3 Second integration – Forest management
T.6.4 Third integration -System validation
T.6.5 Scientific coordination
D.6.01 System Integration and Validation Plan
D.6.021 System Integration Report I
D.6.041 SLOPE System Techno-Economic Evaluation Report I
D.6.022 System Integration Report II
D.6.042 SLOPE System Techno-Economic Evaluation Report II
D.6.023 System Integration Report III
D.6.043 SLOPE System Techno-Economic Evaluation Report III
MS04 SLOPE System Integration Planning is completed
MS05 Forest Inventory and Intelligent Harvesting system integration
MS07 Forest Management system integrated
MS09 System testing ending
D.6.03 SLOPE System Field Trials Readiness Assessment Report
7. Technical Meeting
19-21 Jan 15
Deliverables
• D. 6.01 System Integration and Validation Plan (M13)
• Integration and validation procedures and timeline to validate the SLOPE system
• Based on the use cases in WP1
• D.6.03 SLOPE System Field Trials Readiness Assessment Report
• Assessment of the initial user experience and recommendations for the field trials
operations.
• Guidance and system operation manual for the Field Trials operators
8. Technical Meeting
19-21 Jan 15
Deliverables
• D. 6.021 System Integration Report I (M23):
• Integration test and validation concept procedures results
• Assessment of the initial user experience
• Recommendations for field trials operations
• D 6.022 System Integration Report II:
• Integration test and validation concept procedures results (rev. 2)
• Assessment of the initial user experience (rev. 2)
• Recommendations for field trials operations (rev. 2)
• D 6.023 System Integration Report III:
• Integration test and validation concept procedures results (rev. 3)
• Assessment of the initial user experience (rev. 3)
• Recommendations for field trials operations (rev. 3)
9. Technical Meeting
19-21 Jan 15
Deliverables
• D6.041 SLOPE System Techno-Economic Evaluation Report I (M23):
• Analysis of technical and economical aspects of SLOPE system
• Current practices and the potential known alternatives comparison
• Estimation phase
• D6.042 SLOPE System Techno-Economic Evaluation Report II:
• Analysis of technical and economical aspects of SLOPE system
• Current practices and the potential known alternatives comparison
• Preliminary results phase
• D6.043 SLOPE System Techno-Economic Evaluation Report III:
• Analysis of technical and economical aspects of SLOPE system
• Current practices and the potential known alternatives comparison
• Final results phase
12. Technical Meeting
19-21 Jan 15
Task 6.1
Definition of the Integration Steps
• Leader: Graphitech
• Participants: MHG, FLY, ITENE
Objectives
• Define the integration steps
• Define validation concepts
• Functionalities
• Communication
13. Technical Meeting
19-21 Jan 15
Integration Strategy
Waterfall + agile like approach
• 3 major loops of integration and lab validation
• Agile works well with small groups for specific tasks
• 3 big integration steps and 3-4 loops of iterative evolution
• Bug fixing and integration at high frequency
• Parallel support for real use case pilots
T.6.2
T.6.3
T.6.4
14. Technical Meeting
19-21 Jan 15
Integration strategy - 2
For each main integration step:
• Definition of the involved components
• Timeline with integration steps, milestones, telcos, days for
testing
• One testing scenario based on the use case
• Involved actors recognition
• Definition of HW and SW
• Functional requirements
• Non-functional requirements
• Testing approach
15. Technical Meeting
19-21 Jan 15
Involved Components
GeoServer
<<infrastructure>>
PostGIS DB
<<datastore>>XML
File System
<<datastore>>
JDBC
<<requires>>
HTTP
Preprocessing Server
<<infrastructure>>
<<requires>>
<<requires>>
HTTP
2D
Renderer
3D
Renderer
Network
System
Network
System
2D Monitoring planning
3D Harvesting Planning
Menu Interface
<<GUI>>
Menu Interface
<<GUI>>
Interface
Interface
Interface
Interface
Graphitech Services
WebServer
<<infrastructure>>
PostGIS DB
<<datastore>>
<<requires>>
REST
FlyBy Services
FTP Server
<<infrastructure>>
FTP
<<requires>>
Treemetrics Services
SLOPE FIS <<LifeRay>>
Tracking Clients
Web Service
<<infrastructure>>
Forest
information DB
<<datastore>>
JDBC
<<requires>>
REST
XML
Handheld
RFID UHF Reader
<<Device>>
Android
Phone / Tablet
<<Device>>
BT
Truck with control unit
<<Device>>
DB Forest
model View
<<GUI>>
2D Portlet
<<GUI>>
3D Portlet
<<GUI>>
Interface
Interface
Biomass
Manager
<<GUI>>
WSRP
Interface
MHG Services
Web Service
<<infrastructure>>
BiomassDB
<<datastore>>
JDBC
<<requires>>
REST
XML
Surveys Clients <<PCs>>
Aerial
Imageries Client
On-Field Lidar
Scan Client
HTTP
FTP
Web Service
<<infrastructure>>
Forest Information
Model DB
<<datastore>>
JDBC <<requires>>
REST
XML
SLOPE FIS (Hosted By MHG)
Cable Crane / Hervester Head
<<Device>>
16. Technical Meeting
19-21 Jan 15
Timeline
Tentative integration timeline drafted
• Defines integration steps at high level
• One Telco every 2 weeks (eventually increased or reduced)
• One/two testing days per month (incremental report writing)
• One/two days for the reporting of the results
17. Technical Meeting
19-21 Jan 15
Testing scenario definition
• Testing scenario based on the use case
• Involved actors
• HW & SW Requirements
• Functional Requirements
• Non-functional Requirements
• Define a threshold to be reached
18. Technical Meeting
19-21 Jan 15
Testing
• Execute the testing scenario
• Evaluate the functional requirements
• Evaluate the non-functional requirements
• Check the results against a threshold
• Fill a report
• Bugs and other issues to be notified to the partners in charge
19. Technical Meeting
19-21 Jan 15
Deliverables and Expectations
Reports:
• D.6.01 System Integration and Validation Plan (M13)
• Contribution from the involved partners for:
• functional and non functional requirements
• Testing scenarios revision
• Draft reports as deliverable annexes
20. Technical Meeting
19-21 Jan 15
Task 6.2
First Integration: forest inventory &
harvesting systems
• Leader: Graphitech
• Participants: MHG, FLY, TRE, GRE, ITENE
21. Technical Meeting
19-21 Jan 15
Objectives
• Integration between HW providers and SW developer
• Collected data available among HW and SW providers (FIM)
• Communication between HW sensors and RFID tracking
• Estimation of
• Components and operations costs
• Productivity and reliability
22. Technical Meeting
19-21 Jan 15
Deliverables and Expectations
Reports:
• D.6.021 System Integration report 1 (M23)
• Preliminary layout as annex of D.6.01
• D.6.041 System techno economic evaluation report 1
• Preliminary layout as annex of D.6.01
• Integrated working prototype ready to be shown at mid-term
project review
• Collaboration from CNR for a first schema of a system techno-
economic evaluation report
• Regular Telcos on a Monthly basis
• First Telco at Task’s start
23. Technical Meeting
19-21 Jan 15
Risks
• Data Formats
• DB Model (T.1.5 and T.5.1)
• Reduce Harmonization/adaptation
• Images and other data formats
• Unreliable Services
• Hardware interfaces with software
• RFID
• BT
• Inability to reproduce planned test
field/conditions
• Component testing takes time!
24. Technical Meeting
19-21 Jan 15
Mitigating Actions
• Exhaustive System Architecture
• T.1.5 and Parallel Session of Tomorrow
• Exhaustive Requirement analysis
• D.1.1 and D.1.2
• Common data model
• T.1.4
• Communication
• Skype (Small Group, no desktop sharing)
• WebEx (up to 25 persons with desktop sharing)
• Monthly Basis
26. Technical Meeting
19-21 Jan 15
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