Top Banner
G-LIO.NET G-LIO.NET “The logical evolution of LIO” http: // g-lio.jrc.ec.europa.eu / G- LioDotNet 2014 Campaign KO
17

G-LIO.NET

Jan 28, 2016

Download

Documents

kynton

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. What is G-LIO.NET?. // Technical presentation will be avoided this time New version of LioDotNet for 2014 campaign Profiles driven workflow - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: G-LIO.NET

G-LIO.NETG-LIO.NET“The logical evolution of LIO”

http://g-lio.jrc.ec.europa.eu/G-LioDotNet

2014 Campaign KO

Page 2: G-LIO.NET

What is G-LIO.NET?• // Technical presentation will be avoided this time• New version of LioDotNet for 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

2/16

(new colors!)(new colors!)

6th March 2014

Page 3: G-LIO.NET

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

3/166th March 2014

Page 4: G-LIO.NET

Introducing G-LIO.NET - Actors

4/166th March 2014

Page 5: G-LIO.NET

5/166th March 2014

Introducing G-LIO.NET – Actors

Page 6: G-LIO.NET

6/166th March 2014

Introducing G-LIO.NET – WF

Page 7: G-LIO.NET

2. Image Requests definition

6th March 2014

Page 8: G-LIO.NET

2. Image Requests definition

Who? – MS Administrator accountsWhy? – To insert baseline information for future ARsWhen? – At the beginning of each new campaignPeriodicity? – Normally once for campaign; twice if HR autumn/winter requestedTools? – G-LIO.NETIssues? – coherency shape file and IRs (zones, areas), feasibility analysis

8/166th March 2014

Page 9: G-LIO.NET

5. Acceptance of Acquisitions

6th March 2014

Page 10: G-LIO.NET

5. Acceptance of Acquisitions

Who? – Contractor accounts (if Proposed or Retained) and Operator accountsWhy? – To express conformity with the Acquisition(s) uploaded so farWhen? – As soon as a new Acquisition has been uploaded (up to 2 days after 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

10/166th March 2014

Page 11: G-LIO.NET

6. Delivery, Reception and IDQA validation

6th March 2014

Page 12: G-LIO.NET

6. Delivery, Reception and IDQA validation

Who? – Contractor accountsWhy? – To allow Contractors to evaluate the quality of received imagesWhen? – As soon as a new Acquisition has been received (up to 5 working days after

the receipt date)Periodicity? – Several times during the lasting of each window, every time new

images are receivedTools? – G-LIO.NETIssues? – Important to assert the actual covered area for each acquisition, as this

value will be used to check for total zone coverage

12/166th March 2014

Page 13: G-LIO.NET

8. Close Acquisition Requests

6th March 2014

Page 14: G-LIO.NET

8. Close Acquisition RequestsWho? – Operator accountsWhy? – To declare the final status of an Acquisition RequestWhen? – 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 anymorePeriodicity? – Several times during the whole campaign, once for each Acquisition

RequestTools? – G-LIO.NETIssues? – ensure Contractor does not wish an extension before entering

Partially/Accepted or Failed status.

14/166th March 2014

Page 15: G-LIO.NET

15/166th March 2014

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…

Page 16: G-LIO.NET

Let’s play it!(curb your enthusiasm, please)

16/16

‘Trailer’ video

6th March 2014

Page 17: G-LIO.NET

Thank you

SimsEC-IAT team

Thank you

SimsEC-IAT team

Pär Åstrand, Giovanni Di Matteo, Csaba Wirnhardt, Juergen Breunig, Ignacio San-Miguel, Blanka VajsovaPär Åstrand, Giovanni Di Matteo, Csaba Wirnhardt, Juergen Breunig, Ignacio San-Miguel, Blanka Vajsova

simsEC, Digital Earth and Reference Data unit, JRC [email protected]

6th March 2014