SPS Mandatory IF Development HMAT Phase 2 KO

SPS Mandatory I/F Development HMA-T Phase 2 KO Meeting 2 -3 July 2008, Frascati Ricardo Moyano, DEIMOS Space Reuben Wright, DEIMOS Space Philippe Merigot, SPOT Image Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Ø Objectives Ø ITT and Proposal information • HMA-T team • Work Breakdown Structure • Deliverables • Schedule • DEIMOS SPS • SPOT SPS Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Objectives This project aims at : Ø The implementation of a SPS EO library Ø The implementation, based on this library, of two SPS Profile for Earth Observation (OGC 07 -018) interoperability standards defined within the HMA contract: § SPOT IMAGE SPS EO – optical § DEIMOS SPS EO – radar Ø The full life cycle process for the two software developments, starting from the generation/update of the Requirement Baseline up to the validation of the interface at the development platform. All documentation shall be generated for each development phase following the tailored ECSS standards from the Statement Of Work. Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Proposal Information: HMA-T SPS Team Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Proposal Infromation: WBS Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Proposal Information: List of Deliverables Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Schedule : HMA “short” schedule shall be applied Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Reviews and Payment Plan Milestone % Date KOM 20 T 0 (03/07/08) AR-1 70 T 0 + 7 m (02/02/09) FP 10 T 0 + 18 m (03/06/09) Notes Ø In our proposal, only one travel is foreseen (this one!) Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Proposal Information: SPS development (1/2) SPS is dedicated to the EO Sensor domain complying with specification OGC 07 -018. The operations part of the contract are aimed at: • Determining the request and receive service metadata describing the abilities of the specific server implementation (Get. Capabilities) • Requesting information needed to send Get. Feasibility and Submit requests (Describe. Tasking) • Determining the feasibility of an intended sensor planning request (Get. Feasibility) • Submitting such a request (Submit) • Retrieving information about how and where data (produced by the sensor) can be accessed (Describe. Result. Access) Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Proposal Information: SPS development (2/2) SPOT System connector Deimos CFIbased System Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Proposal Information: Development issues Ø We will need finalised inputs from the SPS Application Profile standardisation. The proposal describes the implementation complying with version 1. 0 of OGC 07 -018. Ø The Requirements and Software specification will follow directly from the Use Cases identified Ø Validation testing must not be confused with conformance testing. Validation shall follow the ECSS approach comprising test case and test procedure specifications. Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Proposal Information: DEIMOS SPS – Technical Approach (1/3) Ø SPS SOAP interface will be developed “Contract first” using Web Service Description Language (http: //www. w 3. org/TR/wsdl). Ø The Java code stubs are then generated via a framework – Axis – this is an Apache project. Ø The SPS I/F shall then be developed, utilising the core library and accessing the existing CFI sensor planning system. Ø SPS I/F server will be deployed on an Apache Tomcat server. No client software deliverable is anticipated. Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Proposal Information: DEIMOS SPS – Technical Approach (2/3) CFI-based System Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Proposal Information: DEIMOS SPS – Technical Approach (3/3) Earth Explorer Mission Software CFI Ø Existing sensor planning library, ie. a COTS to this project. Collection of software functions performing accurate computations of mission related parameters. Ø Computes time segments at which an Earth Explorer satellite, or one of its instruments is in view of various targets. Ø Implemented in C but will be accessed in Java code via a Java Native Interface (JNI). Ø Can simulate a variety of Earth Explorer missions, such as GOCE, Cryo. Sat and Aeolus. We will decide early on in the project the details of the Radar planning system we wish to simulate. Ø Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Proposal Information: SPOT SPS overview SPS Request Spot Image SPS PRM request XML swe. Common Mapping Client SPS PRM Response response Spot Image Programming request XML EO LIB Deserialization System Req validity check swe. Common response Serialization Java objects Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development Proposal Information: SPOT SPS in details Apache Tomcat HTTP Servlet Byte Stream Apache Axis SOAP Framework XML Tree Objects (i. e. DOM) XML Tree Objects SPS Message Deserializer SWE Common Reader SPS Message Serializer SWE Common Writer SPS Message Java Object EO Reader Helper Users, Tasks DB Sensor Params DB Feasibility Studies EO Writer Helper Ground Segment Connector Programming Orders SPS Library Notification System Programming Status Frascati, 2 -3 July 2008 Subscription DB GS Specific Feasibility Report Slide

SPS Mandatory I/F Development SPS Lib : key points Ø Simplify the life of implementer Ø Contains a Low-level module (swe. Common) that can be reused by other WS Ø Improve Interoperability Frascati, 2 -3 July 2008 Slide

SPS Mandatory I/F Development SPS specification : key points Ø New SPS v 2. 0 specification will be the basis for the SPS EO Profile (i. e. part of the Requirement Baseline) Ø Spec currently under construction via the SPS SWG at OGC. HMA SPS EO Profile 1. 0 will follow shortly Ø Should simplify the life of implementers. More consistent with other SWE standards and notifications are optional Ø EO Profile specification will reuse more of the core SPS and define specific data structures used in EO (hopefully better than in v 0. 9. 5) Ø Target for SPS 2. 0 draft: September 2008 (TC Atlanta, USA) Target for SPS 2. 0 final: December 2008 (TC Valencia, Spain) Frascati, 2 -3 July 2008 Slide