G-LIO.NET

1. G-LIO.NET G-LIO.NET • “The logical evolution of LIO” • 2014 Campaign KO http://g-lio.jrc.ec.europa.eu/G-LioDotNet G. Di Matteo, 06/03/2014

2. What is G-LIO.NET? • // Technical presentation will be avoided this time • New version of LioDotNetfor 2014 campaign • Profiles driven workflow • More automatic controls on data (dates, upload metadata, coverages status…) • Acquisitions are new delivery units • Monthly invoicing of validated and billable acquisitions (basketification) • Automatic import of feasibility results • Integrated simplified version of the G - QuickLook Browser (G-QLB) • New users’ roles • Improvements in the layout • Starting point for the NG-LIO.NET (new colors!) (new colors!)

3. What is JRC providing? • The G-LIO.NET 1.0 version and all potential bugs fixings (1.0.x versions) • Hosting infrastructure • Operational support • Control over validation of conflicting acquisitions • (Basket management to allow monthly invoicing of acquisitions) • Technical guidance for NG-LIO.NET developments • Documentation

4. Introducing G-LIO.NET - Actors

5. Introducing G-LIO.NET – Actors

6. Introducing G-LIO.NET – WF

7. 2. Image Requests definition

8. 2. Image Requests definition Who? – MS Administrator accounts Why? – To insert baseline information for future ARs When? – At the beginning of each new campaign Periodicity? – Normally once for campaign; twice if HR autumn/winter requested Tools? – G-LIO.NET Issues? – coherency shape file and IRs (zones, areas), feasibility analysis

9. 5. Acceptance of Acquisitions

10. 5. Acceptance of Acquisitions Who? – Contractor accounts (if Proposed or Retained) and Operator accounts Why? – To express conformity with the Acquisition(s) uploaded so far When? – As soon as a new Acquisition has been uploaded (up to 2 daysafter the upload date for Operators, up to 1 day for Contractors) Periodicity? – Several times during the whole campaign, every time a Provider is uploading an Acquisition (Contractor only if Proposed or Retained) Tools? – G-LIO.NET (+G-QLB) Issues? – Important to closely follow the e-mail notifications and to react accordingly with workflow

11. 6.Delivery, Reception and IDQA validation

12. 6.Delivery, Reception and IDQA validation Who? – Contractor accounts Why? – To allow Contractors to evaluate the quality of received images When? – As soon as a new Acquisition has been received (up to 5 workingdaysafter the receipt date) Periodicity? – Several times during the lasting of each window, every time new images are received Tools? – G-LIO.NET Issues? – Important to assert the actual covered area for each acquisition, as this value will be used to check for total zone coverage

13. 8. Close Acquisition Requests

14. 8. Close Acquisition Requests Who? – Operator accounts Why? – To declare the final status of an Acquisition Request When? – Depending on the final status of the AR: • Fully/Accepted -> when the whole Zone area has been covered • Partially/Accepted -> when the window ended and at least one Acquisition has been accepted by Contractor and the whole Zone area has not been covered • Failed -> when the window ended and not acquisition has been accepted • Closed -> in case of issues with the definition of the AR or if Contractor does not need images anymore Periodicity? – Several times during the whole campaign, once for each Acquisition Request Tools? – G-LIO.NET Issues? – ensure Contractor does not wish an extension before entering Partially/Accepted or Failed status.

15. Future G-LIO.NET? • Outsourcing of developments • Framework contractors will provide the NG-LIO.NET (2015 campaign), following JRC technical guidance • …We look forward to it, now the ball is in EUSI and ASTRIUM hands…

16. ‘Trailer’ video • Let’s play it! • (curb your enthusiasm, please)

17. Thank you SimsEC-IAT team Thank you SimsEC-IAT team Pär Åstrand, Giovanni Di Matteo, Csaba Wirnhardt, Juergen Breunig, Ignacio San-Miguel, Blanka Vajsova Pär Åstrand, Giovanni Di Matteo, Csaba Wirnhardt, Juergen Breunig, Ignacio San-Miguel, Blanka Vajsova simsEC, Digital Earth and Reference Data unit, JRC Ispra simsEC-iat@jrc.ec.europa.eu