Simplifying Inter-Agency Interoperability with Product Distribution Service (PDS)

Slide Note
Embed
Share

Simplified alternative for managing distribution of existing products, enabling different end-users to request and obtain product files through standard requests. PDS facilitates registration for different product types, allows file delivery location specification, and supports various request types and handling options for efficient data exchange between multiple agencies.


Uploaded on Sep 29, 2024 | 0 Views


Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript


  1. PRODUCT DISTRIBUTION SERVICE (PDS) A Simplified Alternative for Inter-Agency Interoperability Dan Smith November 11, 2015

  2. Mission ops centers typically generate many types of products science observation files, event history files, nav files, loads, etc. The PDS should only manage the distribution of existing products. The standard should work without regard to product formats Requests for processing actions to generate products or to generate customized files and return them should be covered by other services (Archive Request, Replay, etc.). A common service-based approach would be a great benefit in that many different end-users can request and obtain the product files through standard requests. Support provided for both specific requests and standing order requests. PDS PRODUCT DISTRIBUTION SERVICE

  3. A user should register for different product types. Products = Files. Could do it by file extension, naming convention, or origination date/time Must specify location for file delivery Instead of copying files to the specified location, could return the file URL to the requester so they can pull file at their discretion Could also handle requests for List of my requests/subscriptions List of files sent over past XX days per the request (history kept by producer) List of available files matching criteria List of available product types and a short text description of each This is not the place to introduce full file format characterization there are many mission- specific formats, CCSDS-defined formats (NAV, etc.). Some files may happen to have tag/value pairs or other approaches easy to decipher. Terminating standing requests or suspending/resuming requests Option for bulk/periodic distribution ( daily at 3 am ) or immediate (as soon as product is available) PDS DETAILS

  4. If Product Distribution service requests can also result in the generation of products (archive retrievals, etc.), and can provide data as files, streams, or messages, then maybe this is the ONLY service needed for the exchange of data between multiple Agencies supporting the same mission. INTERESTING THOUGHT

Related


More Related Content