1. HMA Sep 2009 – Slide 1 Daniele Marchionni Elsag Datamat HMA Follow On – Task 4 - Workplan

2. HMA Sep 2009 – Slide 2 Summary  Task 4 Activities  Task 4 Status

3. HMA Sep 2009 – Slide 3 Task 4 – Consortium Organization

4. HMA Sep 2009 – Slide 4 Task 4 – Consortium Organization  Elsag Datamat Project Management Technical Coordination HMA Ordering ICD OGC 06-141 Update Standardization Process Analysis, Design, Development and Validation of the Reference Order Server  Con Terra Support to HMA Ordering ICD OGC 06-141 Update Preparation of ATS & ETS Support to Reference Order Server validation

5. HMA Task 4 – Main Outputs  Promotion of OGC 06-141 Ordering Services for Earth Observation Products V0.9.4 as OGC Standard  Definition of ATS & ETS  Development of a reference implementation (open source software as required by HMA FO). Sep 2009 – Slide 5

6. HMA Ordering ICD (OGC 06-141 ) Overview This specification allows submitting orders of the following types: –Orders for precisely identified EO products, usually derived from a catalogue interaction –Orders for future EO products, derived from the interaction with an SPS EO compliant server –Subscription to EO Products: i.e. the user can adhere to a subscription defined from the EO provider / can perform a bulk order for past products This specification is used in the last step of the normal user workflow (catalogue browsing, future products analysis, ordering), and so it is linked to the specifications used in the previous steps: –“OGC™ Catalogue Services Specification 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products” OGC 06-131, used for accessing the catalogue –OpenGIS® Sensor Planning Service Application Profile for EO Sensors OGC 07- 018, used for interacting with the on-line programming service instance (SPS EO) Sep 2009 – Slide 6

7. HMA Ordering ICD (OGC 06-141 ) Overview  This specification is based on SOAP (V1.1 for HMA implementations) over HTTP POST (Web Service)  Information Model: Order options are modelled using SWE Common, in the same way the SPS EO represents tasking parameters.  Interfaces: This specification foresees a number of operations (7) for the different tasks of the ordering process. The user identity information are carried in the SOAP Header (encrypted and signed) and its format is outside this spec, but it is defined in:  User Management Interfaces for Earth Observation Services OGC 07-118 V0.0.4 Sep 2009 – Slide 7

8. HMA Ordering ICD (OGC 06-141 ) Overview Operations: –GetCapabilities: XML/SOAP encoding; sync / async  Returns service metadata about the server and list of supported collections –GetOptions: XML/SOAP encoding; sync  It returns the possible combinations of options for ordering catalogue products / future products / subscriptions  Options are returned by collection; collection and identifier; SPS:ID –GetQuotation: XML/SOAP encoding; sync / async  It returns the quotation for an order to be submitted  The quotation is returned synchronous / asynchronous / off-line –Submit: XML/SOAP encoding; sync / async  It allows submitting a new order / a previously quoted order  Synchronous process: the server returns just an acknowledge with the order id  Asynchronous process: the server calls the client (SubmitResponse) notifying a change on the order status / order completion Sep 2009 – Slide 8

9. HMA Ordering ICD (OGC 06-141 ) Overview Operations: –GetStatus: XML/SOAP encoding; sync  Order retrieve: returns details about an identified order (typical scenario in case of sync submissions)  Order Search: returns the list of orders matching a simple filter expression (last update, order reference, order status) with different level of details –Cancel: XML/SOAP encoding; sync / async  Allows cancelling a previously submitted order –DescribeResultAccess: XML/SOAP encoding; sync  For orders with on-line delivery  It returns the URLs for accessing the ordered items Sep 2009 – Slide 9

10. HMA Ordering ICD (OGC 06-141 ) – Compliance Testing Testing –It is a fundamental precondition for the evolution and take up of a proposed interface control document (ICD) –It is accomplished based on the guidelines of the OGC “Compliance & Interoperability Testing & Evaluation (CITE)” initiative. A compliance test “package” (as defined in ISO 19105) consists of: –An Abstract Test Suite (ATS) which includes abstract test cases which define all the requirements to be satisfied for conformance –An Executable Test Suite (ETS) which is a computational resource composed of executable test cases implementing the abstract cases as CTL (Compliance Test Language) scripts A test engine will run ETS for execution against implementations under test –adopted by the OGC is an open source web services compliance engine, Test Evaluation And Measurement (TEAM) engine Sep 2009 – Slide 10

11. HMA Ordering ICD (OGC 06-141 ) – Compliance Testing Sep 2009 – Slide 11 Within this project an OGC compliance test package will be developed, containing – Specification of an Abstract Test Suite (ATS) for the Ordering Services (OGC 06-141) – Will be done as defined by the ESA policies defined in the HMA- T phase by IGN – will include about 20-25 test cases structured into different levels and sub-levels. – The ETS provide the abstract ATS-test cases as CTL-scripts The HMA Order ICD Test Suite Technical Note will contain the abstract test suite (ATS) and the executable test suite (ETS)

12. HMA Ordering ICD (OGC 06-141 ) – Compliance Testing Sep 2009 – Slide 12 – Provision of the TEAM Engine (as client) in order to run and test the defined interfaces as defined within the ETS and test execution.  scripts will be executed by the CITE TEAM Engine against a web-accessible version of the reference order server of Elsag Datamat  a plan and a report of the tests is provided – For the development of the ATS and the CTL scripts it is considered and reviewed any existing ATS and test scripts (if available)

13. HMA Ordering ICD (OGC 06-141 ) – Reference Server  A reference order server will be set-up with the following objectives: To provide an implementation of the Candidate Standard as required by the RFC process Demonstrate the updated specification; Support the implementation of ordering clients; Support the implementation of ordering servers.  Since ordering process implies processing, formatting and delivering to the user of the required products, then a fully functional order server would mean a complete ordering handling system for EO products.  The order server that will be provided is a system that will provide to the client an OGC 06-141 compliant interface, but the ordering functionality is accomplished by calling an actual order handling system (MUIS / M2EOS).  The order server that will be provided is the evolution of Ordering & Programming Gateway – OPGW: Implemented in HMA-I (OGC 06-141 V0.9.2 - 27/09/2007; OGC 07-018 V0.9.4 - 07/05/2007) Enhanced in HMA-E (OGC 06-141 V0.9.4 - 05/09/2008; OGC 07-018 V0.9.5 - 19/11/2007; OGC 07-118 V0.0.4; KML for feasibility responses) Works mainly translating HMA input protocols in the corresponding EOLI XML ones (EOLI XML Catalogue V2.8; EOLI XML Order V3.4) Sep 2009 – Slide 13

14. HMA Ordering ICD (OGC 06-141 ) – Reference Server Sep 2009 – Slide 14

15. HMA Ordering ICD (OGC 06-141 ) – Reference Server Sep 2009 – Slide 15

16. HMA Task 4 - Deliverables Sep 2009 – Slide 16 Deliverable ItemPR 01/2010 MTR 05/2010 AR 11/2010 FP 03/2011 Doc File OPGW Software Requirements Specification - SRS (Order Server Requirements Baseline) XXRB OPGW Software Installation Document (Order Server Operation Manual) XXTS OPGW Software Design Document - SDD (Order Server Architectural Design) XXXDDF HMA Ordering ICDXXXTS OPGW Software Validation Testing Specification - SVTS (Order Server Acceptance Test Plan; Traceability of Acceptance tests to Requirements Baseline) XXDJF Order Server Installation PlanX OPGW Acceptance Test ReportsXDJF HMA Order ICD Test Suite Technical Note containing ATS and ETS XXXDJF HMA Order ICD test Suite technical Note containing plan and report of the tests executed with the TEAM engine XDJF OPGW SW DeliveryXDDF

17. HMA Sep 2009 – Slide 17 Task 4 - Status  Started the standardization process: Verified OGC Policies & Procedures Chosen RFC Process for promoting as OGC standard the  OGC 06-141 Ordering Services for Earth Observation Products V0.9.4 Submission Team:  ESA, voting member, primary submitter of the RFC  Elsag Datamat, associate member, editor of the Candidate Standard, in charge of the reference implementation  Con terra, associate member, in charge of ATS / ETS preparation, review of Candidate Standard  EUMETSAT, associate member, interested in implementation

18. HMA Task 4 - Status RFC Package:  Cover letter  Technology Submission Form  Candidate Standard: Signed and sent to OGC on 29/09/2009 Issue Tracker already set-up on the OGC portal under the “Ordering Service for Earth Observation Products SWG” project:  http://portal.opengeospatial.org/?m=projects&a=view&project_ id=325&tab=5 http://portal.opengeospatial.org/?m=projects&a=view&project_ id=325&tab=5 Next Steps:  Prepare the charter  Establish the SWG (by October 2009) Sep 2009 – Slide 18