MANAGER SS

1
MANAGER S/S
Smog - Demo
AGF-P/MAN Management Subsystem Technical
Presentation
2
MANAGER S/S
Smog - Demo

• OBJECTIVES
• Management subsystem of the AGF Prototype
• Interface of the AGF Prototype with the GS
• Reception of DMAP
• Generation of DMAR
• Commanding the S/S in AGF Prototype, following
  DMAP
• Monitoring and control of all S/S in AGF
  Prototype
• PAS,PGS,FEP,DDS.

3
MANAGER S/S
4
MANAGER S/S

• AGF-P/MAN is in charge of the scheduling of
  incoming DMAP processing requests and the
  notification of the DMAP results using DMAR.
• It guarantees
• DMAP requests consistency.
• DMAP execution using the services provided by the
  AGF-P subsystems.
• Providing communication between the differents
  subsystems.
• AGF-P/MAN expands a DMAP processing request in a
  set of associated processing requests which
  constitute a production chain oriented to satisfy
  this whole request. Associated DMAP processing
  requests is the mechanism to ask to AGF-P the
  individual execution of the following tasks
• Acquisition of telemetry data from generic EO
  satellites
• Transformation of the telemetry into Computer
  Compatible Format
• Generation of EO products, including level 0 and
  level 1
• Storage, archive and catalogue the EO products
• Dissemination of products to the EO data users

5
MANAGER S/S

• The transfer of files between PAS, PGS and DDS is
  done through the FTP protocol.
• The transfer of messages from AGF-P/MAN and the
  AGF-P S/S are done using JMS communications
  middleware.
• AGF-P behavior is event driven
• The daemons check continually for new Dmaps.
• Daemons control the state of the orders and
  suborders.
• Daemons control and unify the different logs.
• Daemons check for the status of the different
  clients. (S/S)
• AGF-P/MAN is designed so that it is able to
  process concurrently several DMAP requests.

6
MANAGER S/S

• Dmap (Detailed Mission Activity Plan).

• DMAP file is related to one and only one
  high-level user request related to exactly one
  satellite and sensor. Dmap file is composed by
  the following four blocks
• ltIDENTIFICATION-BLOCKgt, named I-BLOCK or I.
• ltADQUISITION-BLOCKgt, named A-BLOCK or A.
• ltGENERATION-BLOCKgt, named G-BLOCK or G
• ltDISEMINATION-BLOCKgt, named D-BLOCK or D
• I-BLOCK is mandatory and A, G and D are optional,
  although at least one of them must be present.
  Any combination of them is accepted, but I,A,D
  combination is not accepted because it is the
  same as saying that a Level 0 product is going to
  be disseminated. By definition it is not
  contemplated dissemination of L0 products. So the
  following are the six possible accepted
  combinations
• I,A,G,D
• I,A
• I,A, G
• I,D
• I,G,D
• I,G

7
MANAGER S/S

• Dmap example

• lt?xml version'1.0' encoding'ISO-8859-1' ?gt
• ltdmapgt
• ltigt
• ltid-usergt555lt/id-usergt
• ltagf-p-identifiergt13452lt/agf-p-identifiergt
• ltrequest-codegt34534lt/request-codegt
• ltelaboration-dategt26/10/2004 100000lt/elaboration
  -dategt
• ltsatellite-idgt2lt/satellite-idgt
• ltsensor-idgt2lt/sensor-idgt
• ltprioritygt2lt/prioritygt
• ltadditional-content-blockgtTest dmap for test
  purposeslt/additional-content-blockgt
• lt/igt
• ltggt
• ltproduct-levelgtL1lt/product-levelgt
• ltsensing-time-blockgt
• ltbegin-sensing-timegt26/11/2004
  100000lt/begin-sensing-timegt
• ltend-sensing-timegt26/11/2004
  110000lt/end-sensing-timegt
• lt/sensing-time-blockgt
• ltL0-product-IDgt6500001lt/L0-product-IDgt

8
MANAGER S/S

• Dmar (Detailed Mission Activity Report)

• DMAR file is generated by the AGF-P/MAN subsystem
  in response to a DMAP processing request and
  reflects the status of the operations requested
  in that DMAP file. DMAR file is composed by the
  following four blocks
• ltRES-IDENTIFICATION-BLOCKgt, named R-I-BLOCK or
  RI.
• ltRES-ADQUISITION-BLOCKgt, named R-A-BLOCK or RA.
• ltRES-GENERATION-BLOCKgt, named R-G-BLOCK or RG
• ltRES-DISEMINATION-BLOCKgt, named R-D-BLOCK or RD
• RI is mandatory and there must be present the
  same combination of blocks that there were in the
  DMAP file request. So the following are the six
  possible accepted combinations, based in the
  possible DMAP request combinations
• DMAP I,A,G,D -gt DMAR RI,RA,RG,RD
• DMAP I,A -gt DMAR RI,RA
• DMAP I,A, G -gt DMAR RI,RA,RG
• DMAP I,D -gt DMAR RI, RD
• DMAP I,G,D -gt DMAR RI, RG,RD
• DMAP I,G -gt DMAR RI, RG

9
MANAGER S/S

• Generating internal AGF orders and starting from
  DMAP information that will be used forwarded to
  the rest of AGF S/S
• Scheduling of activities
• allocating activities to each S/S
• coordinating activities among S/S providing
  mechanisms to implement constraint on activities
• Monitoring of S/S activities
• Generation of DMAR
• PGS, PAS, DDS and FEP with their own local
  manager, task manager responsible for managing
  its resources and internal activities.

10
MANAGER S/S How it works (I) ?

• AGF_MAN receives of DMAP from PDS/CS (one per
  product)
• AGF_MAN generates orders and suborder based on
  DMAP information blocks and stores in AGF
  database
• AGF_MAN send suborder to S/S
• AGF S/S executes suborders and report status of
  completion to AGF_MAN
• AGF_MAN generates DMAR with the result of
  suborders execution associated to a DMAP.

11
AGF How it works (II) ?

• DMAP Logic Treatment

SUBORDER
Acquisition
ORDER
Archive L0
IAG
A
SUBORDER
DMAP
Retrieve L0
SUBORDER
G
ORDER
Generate
SUBORDER
Archieve L1
SUBORDER
12
AGF How it works (III) ?
Orders/Suborders
Sub-Orders Type Archive L0 1 Archive
L1 2 Retrieve L0 3 Retrieve L1
4 Acquisition 5 Generate
6 Disseminate 7

• Orders Type
• A Acquisition
• G Generation
• D Dissemination

Smog Database