rsoc system testing status - 1 rsoc system test concept –covered in ro-est-pl-5013 –status to be...

9
RSOC System Testing Status - 1 RSOC System Test Concept Covered in RO-EST-PL-5013 Status to be presented at key system reviews (GSRR) Connectivity Tests Covered by tests in RO-EST-TP-3051 Interface Tests Based on Pointing & Interference Scenario inputs End-to-end Tests Based on GLEP operations used for SFT Short-term Schedule

Upload: shanon-shelton

Post on 26-Dec-2015

213 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: RSOC System Testing Status - 1 RSOC System Test Concept –Covered in RO-EST-PL-5013 –Status to be presented at key system reviews (GSRR) Connectivity Tests

RSOC System Testing Status - 1

• RSOC System Test Concept– Covered in RO-EST-PL-5013– Status to be presented at key system reviews (GSRR)

• Connectivity Tests– Covered by tests in RO-EST-TP-3051

• Interface Tests– Based on Pointing & Interference Scenario inputs

• End-to-end Tests– Based on GLEP operations used for SFT

• Short-term Schedule

Page 2: RSOC System Testing Status - 1 RSOC System Test Concept –Covered in RO-EST-PL-5013 –Status to be presented at key system reviews (GSRR) Connectivity Tests

RSOC System Testing Status - 2

• RSOC System Test Concept– Covered in RO-EST-PL-5013

• Document defines the overall system level test plan for RSOC

• Corresponding System Test Report will summarise status

• Copy will be made available on ‘livelink’

• Specific instructions will be given to PI-teams for each test

– Status to be presented at key system reviews (GSRR)• Status at GSRR will establish following readiness criteria

– RSOC Interfaces tested (PI-RSOC-RMOC)– RSOC End-to-end data flow is verified for routine ops.– Draft Interference and Pointing Scenarios are available

• End of RSOC Commissioning Phase will establish– RSOC system has been fully validated– ‘Knowledge-base’ available at RSOC is adequate for Mission

Page 3: RSOC System Testing Status - 1 RSOC System Test Concept –Covered in RO-EST-PL-5013 –Status to be presented at key system reviews (GSRR) Connectivity Tests

RSOC System Testing Status - 3

• Connectivity Tests– Covered by tests defined in RO-EST-TP-3051 – Tests conducted over the last few weeks– Results reported in RO-EST-TR-3063

– In summary ---> All ran OK !

Page 4: RSOC System Testing Status - 1 RSOC System Test Concept –Covered in RO-EST-PL-5013 –Status to be presented at key system reviews (GSRR) Connectivity Tests

RSOC System Testing Status - 4

• Interface Tests– Based on Pointing & Interference Scenario inputs

• Two REAL Scenarios will be used (Pointing & Interference).

• PI-teams will provide draft inputs for these scenarios (ITL files defining the operations and EDF files containing all necessary TC-sequences.

• These inputs (with modifications made by RSOC) will be used to perform detailed interface testing between RSOC and RMOC.

• These inputs will be collated and used as the basis for the actual Pointing and Interference scenarios to be executed at the end of the S/C commissioning phase. (First real operations of payload performed using RSOC provided inputs). Availability of these draft scenarios must be confirmed at the GSRR.

Page 5: RSOC System Testing Status - 1 RSOC System Test Concept –Covered in RO-EST-PL-5013 –Status to be presented at key system reviews (GSRR) Connectivity Tests

RSOC System Testing Status - 5

• End-to-end Tests– Based on GLEP operations used for SFT

• RSOC will provide PI teams with files to use for this test :– TC-Sequence.edf containing definitions of TC sequences needed

to perform GLEP operations.– RSDB.edf containing the command definitions for each instrument

(this RSDB.edf is invoked within in the TC-Sequence.edf and is derived from the RMOC database).

– A draft OIOR.itl to be used as the operational input file for the end-to-end test.

– PI teams will perform pre-defined actions on these files and transfer them to RSOC.

– RSOC will consolidate all inputs and transfer them to RMOC as a POR file.

– RMOC will execute this POR file on the PFM during SVT 1.2 (tbc)– PI-teams can retrieve data from DDS and confirm success.

Page 6: RSOC System Testing Status - 1 RSOC System Test Concept –Covered in RO-EST-PL-5013 –Status to be presented at key system reviews (GSRR) Connectivity Tests

RSOC System Testing Status - 6

SFT-GLEPITL’s

OIOR.itlTC-SEQ.edf

RSDB

RSDB.edf

‘livelink’

TC-SEQ.edf

OIOR.itl

RSDB.edf

TC-SEQ.edf

OIOR.itl

Add PING-SEQ

Add PING-SEQ

RSOC E2E Step 1 - prepare test files from SFT PI’s E2E Step 2 - prepare test files

Page 7: RSOC System Testing Status - 1 RSOC System Test Concept –Covered in RO-EST-PL-5013 –Status to be presented at key system reviews (GSRR) Connectivity Tests

RSOC System Testing Status - 7

CS update

OIOR.itlTC-SEQ.edf

RSDB.edf

OIOR.itlTC-SEQ.edf

Local EPS

D D S

POR file

OIOR.itlTC-SEQ.edf

RSOC EPS

RSDB.edf

PI’s E2E Step 3 - provide test input RSOC E2E Step 4 - consolidate files

Update Cycle

Planning Cycle

Page 8: RSOC System Testing Status - 1 RSOC System Test Concept –Covered in RO-EST-PL-5013 –Status to be presented at key system reviews (GSRR) Connectivity Tests

RSOC System Testing Status - 8

TM files

RMOC

DDS

POR file

PI TM Analysis

ReferenceSFT GLEP ITL

CS update

RSDB

PFMS/C

TCStack

Test ReportALL OK !

RMOC E2E Step 5 - process POR for SVT PI’s E2E Step 6 - retrieve TM from DDS & check

Page 9: RSOC System Testing Status - 1 RSOC System Test Concept –Covered in RO-EST-PL-5013 –Status to be presented at key system reviews (GSRR) Connectivity Tests

RSOC System Testing Status - 9

• Short-term Schedule– Source test-files needed by PI-teams for end-to-end test will be available on

‘livelink’ on 28th June 2002.– PI-teams will make simple modifications to test files and transfer them to

RSOC as a TC-Sequence -Update-Request (EDF file) and an OIOR (ITL file) by 5th July 2002.

– RSOC will generate TC-Sequence-Update files for ESOC (Excel files) and a consolidated POR expressing the GLEP operations for the whole payload. (Due 15th July 2002).

– ESOC will perform these GLEP operations as part of SVT 1.2 (first week August 2002)

– PI-teams will retrieve TM data from DDS and analyse it to confirm expected GLEP operations were performed. Results will be reported by 16th August 2002.

– Draft Pointing & Interference inputs from PI-teams shall be available by TBD in July.