1 / 15

Overview of Lessons Learnt from Current Services

Overview of Lessons Learnt from Current Services. Andrew Fleming British Antarctic Survey. Aim – summarise users experiences of current ESA EO services Provide first step to improving and redefining the way ESA currently provides its data and services

bonnie
Download Presentation

Overview of Lessons Learnt from Current Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Overview of Lessons Learnt from Current Services Andrew Fleming British Antarctic Survey

  2. Aim – summarise users experiences of current ESA EO services • Provide first step to improving and redefining the way ESA currently provides its data and services • Some recent significant improvements – but potential for much more

  3. Inputs from a broad cross section of the EO community Questionnaires & interviews Users from many application backgrounds – commercial, GSE, science, operations Includes users of many different data types and volumes Issues related to data policy outside of scope

  4. User Service Portals Most use EOLI-SA Mostly for ESA data A lot of positive comments Users want simplicity and intuitive use Access to data Order tracking Up to date information

  5. Interface and GUI • Positive comments • Background server frustrations • AOI selection • More detailed GUI • Access to data • Optional preview imagery • Appropriate fonts • Export search results • User testing

  6. Ordering data Order tracking is insufficient – timely updates and clearer ordering numbers Bulk ordering a necessity into the future Clear picture of existing schedule and immediate information about conflicts Backward compatibility with EOLI-SA versions Up front cost clarification

  7. Delivery • An area where significant improvements were recognised • FTP/Rolling archive options are now widely used • More direct broadcast • Ensure EOLI-SA and the rolling archive are synchronised • Still frequent problems with missing/dupicate/wrong orders – must recognise impact on customers • NRT delivery needs operational levels of support

  8. Interoperability • Scope for improvements between ESA functions • searching, ordering, tracking, notification, data access and helpdesk • Third party mission access seen to be quicker through dedicated systems • Clearer link-up between ordering, costing and quota systems

  9. Data Archive integration

  10. Data Issues • No guidance for users unfamiliar with ESA data types • Easier multi-mission searches • Preview imagery felt to be essential • Easier options for searching data time series

  11. Data Issues • Better SAR data information – specifically related to interferometry applications • Inaccurate Doppler centroid information & missing baseline information • QA / Validation Information not available • Variable use and opinion of toolboxes • Data policy clarity

  12. Invoice and accounting • Clearer information on charges • Invoice information • Billing options

  13. Customer Care • Many positive comments regarding the Helpdesk • However an impression that they are stretched and under resourced • Users always want a faster response! • Proactively distribute issues related to system downtime and outages • Automatic order tracking and more online help might reduce queries

  14. Customer Care • Help function integration

  15. Key outcomes • Users want an easy to use and intuitive service • Incorporating functional search, order, tracking, data access and help services • As much integration as possible • They require clear and up to date information on all aspects • With increased numbers of operational users the demands on these systems will be much greater – no more complacent users • Helpdesk and support functions will need to be properly resourced to enable this

More Related