0% found this document useful (0 votes)
25 views2 pages

Itab 1

The document outlines a series of tasks and issues related to the GMV's enhancements and operational procedures for satellite SES routines. It details specific efforts, estimations, and feedback requirements for various functionalities and fixes, including improvements to software stability and performance. Additionally, it lists several software problem reports (SPRs) that need to be addressed, along with their current status and required actions.

Uploaded by

vineetha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
25 views2 pages

Itab 1

The document outlines a series of tasks and issues related to the GMV's enhancements and operational procedures for satellite SES routines. It details specific efforts, estimations, and feedback requirements for various functionalities and fixes, including improvements to software stability and performance. Additionally, it lists several software problem reports (SPRs) that need to be addressed, along with their current status and required actions.

Uploaded by

vineetha
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

TDFORMAT TDLINE

* SEE QUOTE FOR ORDER DETAILS (TABLE)


*
*
* Id Description Effort Estimation
* man/hour GMV comments Needs
* 1 GMV to provide a list of enhancements in V7 compared to V6. GMV to
"show-off" new functionality. 0 Document delivered Any feedback.
* 2 Smooth execution of SES routine operations for 1 satellite,
specifically A2G (SKM, ephemeris upload ...) plus successful OPA non-r
= egression Proc runs. GMV may perform the usual validation checkout of about
3-4 days, of a complete testing of 15 days, we do
recommend the first one in this stage.
* It is also important for us to use the satellite DB and a simulator
aligned with the sat db Satellite DB, Simulator and procedures
* 2.1 (2.1) Functional SES "Memory2TM" (some fixes were done by SES in
hifly 6.6.2 to have it working) 50 GMV will review and incorporate the
changes done in SES Changes and test executed to validate them
* 2.2 (2.2) Functional SES derived parameters (DPGEN) compiled from C code
16 GMV will compile all derive parameters needed and the compile library
will be part of the delivery Derive parameters code
* 2.3 (2.3) Latest version of SPELL (recent EXIF interface fixes) for
better stability. (SPELL installation is under SES responsibility, but
EXIF_TM instability has been recently fixed with modifications both in
SPELL and in hifly 6.6.6). 30 If the stability problem is not
significant enough this point may be solved in the future project, if
not there are two points here, concerning hifly we will include all SPRs
solved at GMV, we will need to incorporate those fixes only done at SES,
concerning SPELL we assume SES doing the integration. Any SPRs in hifly
solved at SES to be analyzed and incorporated.
* 2.4 (2.4) A review of the SES hifly 6.6.2 MISCconfig to achieve a
similar configuration in hifly 7 30 Is it mandatory for compatibility?
If so, we have included the estimation to merge and validate on
MISCconfig file for one satellite. Miscconfig and SES support to clarify
the reason of the updates made
* 2.5 (2.5)Archiva not running 10 GMV will include archiva in all in a box
environment
* 3 Test conditions are currently sub-optimal:
* 3.1 Current system allows a single user (the one starting the system)
with a lot of Console actions required for SPELL (not good for users
impression) 20 Code to be done to allow remote X windows fowarding in
the application launcher
* 3.2 Low performance impressions? Maybe use a thick client rather than
CITRIX? (more on SES side) ? More details needed More details
* 3.3 hifly-in-a-box is simple to deploy, but limits some of the tests
(e.g. failover ...)? 20 GMV may deliver installation packages for SES to
install? Of a set of Prime - backup - ws setup
* 4 SPRs No cost will be included for any SPR
* 4.1 1) OOLs not consistent between OOL display and TQD: To be
reproduce again
* 4.2 2) Changing the sort order in hiflyViews closes directories: 16 Is
it needed in this stage? It will be solved in the final version.
* 4.3 3) Directories are no longer sorted alphabetically: 0 Already fixed
on PPR 10259
* 4.4 4) Derived orbital oscillator parameters are not working: ( NOTE: We
have no capability to build DPGEN with the C code hardcoded derived
parameter for this demo. ) 40 To be reproduce again after Dpgen
compilation of point 2.2
* 4.5 5) Execution timed out on command in OSCILLATORS_UPDATE (time-tagged
cmd). However, command was sent to the dss. 0 Seems a problem of SPELL
and not Autofly, more date needed
* 4.6 6) No archived TM displayed. Also, this new feature of linear
regression doesn't display anything: It will be solved after archiva
inclusion (point 2.5)
* 4.7 7) EXIF_TM2 crashed during SKM_CYCLE execution: To be reproduce
again
* 4.8 8) Memory2TM parameter is not working:
* [GLM] According to Yann this Memory2TM ZBAROL_A was part of our database
ingestion and should have worked. To be investigated. To be reproduce
again after fixing point 2.1
* 4.9 9) In Dump Type drop-down list, the option below the mouse is not
readable: 8 It is solve selecting gnome theme, is it mandatory for this
version?
* 4.10 10) Task 'VPKT_PROV' died when using VPD (Analyse -> Browse.. ->
firstDumpAddr -> Select -> Compare records): 8 To be reproduce again,
GMV will tested in the delivery
* 4.11 11) Unable to take control of CSKM procedure 0 It seems an SPELL
problem, if not more data is needed.
* 4.12 12) Unable to setup TC interface when trying to start CSKM
manually. Restarted EXIF_CH via task launcher to fix: 8 It seems an
SPELL problem, if not more data is needed.
* 4.13 13) Cannot update time correlation: 0 Not an SPR. Correlation is
computed automatically by hifly.
* 4.14 14) Time-tag display is not showing that ground and on-board queue
is matching: 32 GMV to check, it is not expected to happen in the
version provided
* 4.15 15) Command arguments are not correctly converted for command
JTNMMINCSK: hifly7: 0 Already fixed
*

You might also like