glast lat projectseptember 15, 2006: pre-shipment review lat requirement verification presentation 5...

GLAST LAT Project September 15, 2006: Pre-Shipment Review

LAT Requirement VerificationPresentation 5 of 12

GLAST Large Area TelescopeGLAST Large Area Telescope

Gamma-ray Large Gamma-ray Large Area Space Area Space TelescopeTelescope LAT Pre-Shipment Review

LAT Level Requirement Verification & Compliance

Rich BaunSLAC Systems Engineering


2LAT Requirement VerificationPresentation 5 of 12

AgendaAgenda

Verification & Compliance Summary Requirements & Verification Overview Requirement Verification Process LAT Level Test Program Overview LAT Level Requirement Sell-off Status Interface Verification Plan to Compliance Closure Requirement Issues LAT Compliance



LAT Verification & Compliance SummaryLAT Verification & Compliance Summary

Verification Summary– 334 of 459 VPs have been executed to date, as per plan

• Verification reports for 329 of the executed VPs have been submitted for customer approval

• 5 requirements have issues that require resolution• Preliminary analysis for 62 of the VPs has been completed and compliance is

fully expected• 219 of the verification reports submitted have been approved

Compliance Summary– LAT compliance with all valid requirements is fully anticipated, except

those noted below:• Science Requirements - Background Rejection

– Details provided in Science Requirements Verification presentation

• EMI Requirements - Conducted & Radiated Susceptibility– Details provided in EMI/EMC Test Results presentation



Requirement Verification OverviewRequirement Verification Overview

The LAT Level verification program encompasses the sell-off of 459 requirements

– 363 Level 2a/2b and 124 Level 3 requirements verified at the LAT Level • 197 requirements allocated for sell-off by LAT Level Test in the 36 test cases

documented by the Performance &Ops Test Plan, LAT-MD-02730• 204 requirements allocated for sell-off by the various Analysis Plans• 22 LAT Level requirements are sold by lower level analysis and test• The remaining 36 requirements are sold by inspection

Classical verification approach utilized– Each requirement assigned one of four verification methods

• Test – Test whose results require analysis to determine success• Demonstration - Test with a simple Go/No Go success criteria• Analysis – Simulations or models used to verify requirement, results

often based on or correlated to test data• Inspection – Visual inspection to verify compliance

– Each requirement assigned a verification level, (i.e. device, unit, subsystem, etc.)

– Detailed verification plan written for each requirement



Environmental Requirement Sell-offEnvironmental Requirement Sell-off

The environmental reqts provided in the EMI Spec and the MAR define the environments in which the LAT is tested– The LAT Performance Spec requires compliance to these

environments either directly or by reference• Sell-off of environmental requirement VPs from the LAT Performance

Spec shows compliance to the environmental requirements

– The environmental test plans also insure these reqts are met by implementing the environments specified in the LAT Environmental Specification, LAT-MD-00778

• The plans specify when, at what levels, and how to apply the environments

LAT performance through the environments is verified by the electrical tests specified in the Perf & Ops Test Plan– Electrical tests are performed before, during, and after the

environments



Requirement & Verification FlowdownRequirement & Verification Flowdown

IRD SRD MSS EMI

LAT Spec (00010)

LAT/SC ICD

Env Spec (00778)

MAR

LAT VP (00408)

VCRM (07658)

TV TP (01600)

Dynamics (01196)

EMI TP (02726)

FVM (07659)

Analysis (07980)

P&OTP (02730)

1 2 3 4 5 6 7 8 9LAT00x LAT Power On X X X X X X X X XLAT01x LAT Power Off X X X X X X X X XLAT02x LAT Reinitialization X X P P PLAT031 LAT Electical Power Subsys Performance XLAT04x Establish Science Operations Config X XLAT05x LAT Register Test X XLAT06x SIU/EPU Hardware Functional X XLAT071 LAT Energy Measurement Calibration XLAT12x LAT Science Modes X XLAT13x LAT/Spacecraft I/F Functional X X X X XLAT141 SIIS LAT/Spacecraft I/F Functional XLAT15x LAT Ambient TCS Test X XLAT16x LAT Ambient Survival Htr Test X XLAT17x LAT Conducted & Radiated Emissions X PLAT18x LAT Conducted & Radiated Susceptibility XLAT20x LAT Science Perf Diagnostics X XLAT21x LAT Timing Measure & Adjust X XLAT22x LAT Science Ops Demo X X P P P PLAT23x LAT GRB Handling X X P PLAT30x LAT ACD CPT X XLAT31x LAT ACD LPT X XLAT40x LAT CAL CPT X XLAT41x LAT CAL LPT X XLAT50x LAT TKR CPT X XLAT51x LAT TKR LPT X XLAT521 LAT Config 1 Light Tight Test XLAT651 T&DF False Triggers XLAT661 T&DF Data Transport Errors XLAT70x LAT SVAC Flight Config on Gnd X XLAT711 LAT Config 1 SVAC Muon Calibration XLAT801 LAT Config 1 SVAC Condition Scan (27 V) XLAT811 LAT Config 1 SVAC Condition Scan (29 V) XLAT821 LAT Config 1 SVAC Nominal Rate CR XLAT831 LAT SVAC Nominal Rate CR Data Volume XLAT841 LAT SVAC Nominal Rate Condition Scan CR XLAT85x LATSVAC Nominal Rate Condition Scan CR X X

= Not required for Baseline Test

ConfigurationsTest Case ID

Test Case Name

FinalPre-TV

Sine VibeL

Mount Radiators

AcousticL

T-CycleT-Bal Remove Radiators

Weight CG

Ship to Spectrum

CL L

Receive, Unpack T

L

Pack LAT

CSSC S

BaselineFC S

at SLAC

Ship to NRL

LLL

Pre Post-Axis

L Limited Performance Test

Comprehensive Performance Test

SVAC Test

C

S

F

T

E

TCS Functional Test

EMI/EMC Emissions/Susceptibility Test



SVAC Test

C

S

F

T

E

LAT Functional and FSW Test

TCS Functional Test


Rev date: 24 April 2006

F

NRLPost-Ship

CEMI/EMCL E L

TESTING IN THERMAL VAC CHAMBER

FinalPre-TV

Sine VibeL

Mount Radiators

AcousticL

T-CycleT-Bal Remove Radiators

Weight CG

Ship to Spectrum

CL L

Receive, Unpack T

L

Pack LAT

CSSC S

BaselineFC S

at SLAC

Ship to NRL

LLL

Pre Post-Axis



SVAC Test

C

S

F

T

E

TCS Functional Test




SVAC Test

C

S

F

T

E

LAT Functional and FSW Test

TCS Functional Test


Rev date: 24 April 2006

F

NRLPost-Ship

CEMI/EMCEMI/EMCLL EEE LL

TESTING IN THERMAL VAC CHAMBER

Test Case Matrix

Electrical Test Requirements

Key:= NASA Requirements

= Joint Requirements

= LAT Requirements

= Requirements Flow

= Verification & Validation Plans

= Test & Analysis Plans

= Verification Flow

Abbreviations:FVM = Function Validation MatrixP&OTP = Performance & Operations Test PlanVCRM = Verification Cross Reference Matrix

LAT/GBM ICD



Requirement & Verification Flowdown DiscussionRequirement & Verification Flowdown Discussion

All NASA Level 2A reqts in the SRD, MSS, and IRD and the ICDs are flowed to the Level 2B LAT Perf Spec (LAT-SS-00010)– All LAT reqts are flowed to Subsystem specs (Level 3) from the

LAT Performance Spec

– DOORS is used to document the reqts and reqts flowdown• NASA Systems and all LAT team members have fully reviewed the

requirements and the associated flowdown

All LAT Perf Spec requirement Verification Plans (VPs) are documented by the Verification Cross Reference Matrix (VCRM)– Each LAT requirement is traced to a VP in the VCRM

– VPs and the verification traceability is documented DOORS

All Level 2A and ICD requirements have been reviewed, flowed, have a VP, and are in the VCRM



Verification Cross Reference Matrix (VCRM)Verification Cross Reference Matrix (VCRM)

The LAT VCRM, LAT-MD-07658, documents the VPs and the verification methods, levels, locations, and results– Test and demo VPs are logically collected to form test cases as

defined by the Perf & Ops Test Plan, LAT-MD-02730http://www-glast.slac.stanford.edu/documents/cyberdoc.asp?lat_search=02730

– Analysis VPs are allocated to the appropriate analysis plan and any LAT level data collection is specified

– Inspection VPs are documented in DOORS and the VCRM

– The VCRM can be found on-line athttp://www-glast.slac.stanford.edu/systemengineering/Verification%20&%20Test/LAT%20Level%20VCRM%20v23.xls

All VPs have been approved by the LAT team and NASA Systems

All VPs have been reviewed & approved by the LAT team and NASA



VCRM ExampleVCRM Example

A complete VCRM is provided in the LAT EIDP

VERID REQID Topic Requirement Text Verif Method

Verification Plan Verif Status Reqt Owner

Test Proc or Report Name

Verification Data

Compliance (Comply/Not

LVP271 CAL3-61 CAL T&DF Interface The calorimeter electronics shall communicate with the Trigger and Data Flow (T&DF) subsystem using LAT standard communications protocols.

D5 Demonstrate the proper function of the CAL/T&DF interface by the successful completion of test cases LAT401 - LAT Config 1 CAL CPT and LAT402 - LAT Config 2 CAL CPT, (see LAT Performance and Operations Test Plan, LAT-MD-02730, paragraphs 6.7.2.22.1 and 6.7.2.22.2 respectively).

Requirement Sold

Grove intSeApp_calf_mu_trend_CPT

LAT-MD-08553

Yes

LVP273 CAL3-71 Low Energy Trigger Signal

The calorimeter shall provide a prompt (within 2 microsec of an event) low energy trigger signal to the LAT trigger system with a detection efficiency of greater than 90% (TBR) for 1 GeV gamma rays entering the calorimeter from the LAT field of view with a trajectory which traverses at least 6 radiation lengths of CsI.

T5 1) The successful completion of the CAL,TKR TREQ Timing Alignment test verifies that the CAL-LO TREQ latency is 2 us or less. This is executed as part of the test cases LAT211 - LAT Config 1 Timing Measure & Adjust and LAT212 - LAT Config 2 Timing Measure & Adjust, (see the Performance & Operations Test Plan, LAT-MD-2730, paragraphs 6.7.2.17.3 and 6.7.2.17.4).2) The 90% trigger efficiency requirement is verified by analysis of simulated 1 GeV gamma rays, as specified in the LAT Science Requirements Verification Analysis Plan, LAT-MD-07980.

Requirement Sold

GroveRitz

intSeApp_e2e_tackscan-0_0.55hr

LAT-MD-08500

Yes

LVP274 CAL3-74 High Energy Trigger Signal

The calorimeter shall provide a prompt (within 2 microsec of an event) high energy trigger signal with a detection efficiency of greater than 90% for 20 GeV gamma rays entering the calorimeter from the LAT field of view that deposit at least 10 GeV in the CsI of the calorimeter.

T5 1) The successful completion of the CAL,TKR TREQ Timing Alignment test (which uses the triggerTimeIn_new.py test script) verifies the generation of a CAL-Hi TREQ within 2 uS of an event. Likewise, the successful completion of the Trigger Efficiency test (which uses the effSuite.py test script) verifies a CAL-Hi trigger efficiency of greater than 90%by performing data collection on the LAT and off-line analysis. Both tests execute as part of the test cases LAT211 - LAT Config 1 Timing Measure & Adjust and LAT212 - LAT Config 1 Timing Measure & Adjust, (see the Performance & Operations Test Plan, LAT-MD-2730, paragraphs 6.7.2.17.3 and 6.7.2.17.4). Test results will be analyized and documented in LAT-TD-xxxxx.2) As specified in the LAT Science Requirements Verification Analysis Plan, LAT-MD-07980, simulations of the distributions of maximum uncorrected energy are performed and recorded per event and are made for all of the gamma samples around 20 GeV with theta < 70 degrees, requiring >10 GeV raw CAL energy in each

Requirement Sold

GroveRitz

intSeApp_e2e_tackscan-0_0.55hr

LAT-MD-08500

Yes



Requirement Verification DocumentationRequirement Verification Documentation

Each reqt’s verification is documented by a Requirement Verification Report (RVR), test report, or analysis report– Each RVR, test report, and analysis report is reviewed and

approved by Systems Engineering and the customer

– RVRs and test and analysis reports often combine verifications for like or related requirements

• For example, most Thermal reqts are sold by the TV Test Report

The LAT VCRM summarizes the verification results– Verification data and RVR, test report, and analysis report doc

numbers are all provided in the VCRM LAT compliance to each requirement is documented in the

VCRM

All requirement verification results are summarized in the VCRM



Requirement Sell-off ProcessRequirement Sell-off Process

Test Case Scheduling1. Test cases that sell requirements are identified in the

pre-coordinated Performance & Ops Test Plan.

2. I&T, Commissioner, and Systems identify test cases to be run each day.

3. Test case interdependencies are considered

Test Case Run Review1. I&T reviews all tests and declares run valid/invalid.

a) All anomalies are documented.

2. All runs recorded in I&T run log.a) Test name, number, start time, LAT configuration, run number, and sequence number are recorded.

Test Case Run Buy-off1. Occurs after I&T declares run valid.

2. Test data review conducted by reqt owners, Systems, Commissioner, and/or assigned experts.a) If run is sufficient, reviewer signs off on log.b) If not, reviewer writes an NCR

3. Anomalies found during review are documented on NCRs.

Analysis, Test, & Demo RVRs1. Only after test cases have been run, reviewed, and

bought off, can test, demo, and analysis VPs requiring test data be sold.

2. A Requirement Verification Report (RVR) is written for each requirement or logical group of requirements. a) RVR must include the requirement statement, verification plan, test phase, test case ID, test script name run number, run date and time, worst case measured data and margin (if applicable), test/analysis summary, applicable doc#s, compliance statement, and any JIRAs or NCRs associated with the reqt.

3. Test Reports are used to sell many requirements such as those related to TV and Dynamics.

Requirement Sell-off1. Draft RVRs and Test Reports are submitted to the

customer by e-mail.

2. The customer reviews, comments are incorporated, and then approves.

3. Approved RVRs and reports are assigned doc #s and formally released into LAT Docs.

Analysis & Inspection RVRs1. Analysis VPs note requiring test data and Inspection

VPs can be sold at any time.

2. An RVR is written for each requirement or logical group of requirements. a) Each RVR must include the requirement statement, verification plan, worst case calculated data and margin (if applicable), analysis summary, applicable doc#s, compliance statement, and any JIRAs or NCRs associated with the reqt.



Test Case Run Buy-offTest Case Run Buy-off

Test Case Run Buy-Off– Once I&T indicated a test run was complete, Systems, requirement

owners, and assigned experts reviewed the run data

– Each test run had at least two reviewers• Systems Engineering reviewed all data for every run/test case• Reqt owners/experts reviewed all data for their assigned runs/cases

– If a reviewer found the run sufficient, they signed off on the hardcopy Test Case Review Log

• Test cases with more than one reviewer were not sold until all sign-off

– If an anomaly was found or the run was insufficient, it was documented in an NCR and corrective action was taken

The LAT verification & test program was extremely thoroughand the data review was extensive and complete



LAT Level Test Program LAT Level Test Program (1 of 2)(1 of 2)SLAC

Test Title

Bas

elin

e L

AT

NR

L P

ost-

Ship

Pre

-Sin

e V

ibe

Pos

t X-A

xis

Vib

e

Pos

t Y-A

xis

Vib

e

Pos

t Z-A

xis

Vib

e

Pos

t Rad

Ins

tall

Pre

- E

MI/

EM

C

EM

I/E

MC

Tes

t

Pos

t-E

MI/

EM

C

Pre

-Aco

ustic

Pos

t-A

cous

tic

Pre

-TV

Bak

e-ou

t

Hot

The

rmal

Bal

Hot

Pro

toqu

al

Hot

to C

old

1

Col

d S

urvi

val

Col

d P

roto

qual

Col

d T

herm

al B

al

Col

d to

Hot

1

Hot

Pla

teau

2

Hot

to C

old

2

Col

d P

late

au 2

Col

d to

Hot

2

Hot

Pla

teau

3

Hot

to C

old

3

Col

d P

late

au 3

Col

d to

Hot

3

Hot

Pla

teau

4

Hot

to C

old

4

Col

d P

late

au 4

Col

d to

Hot

4

Fin

al L

AT

LAT Comprehensive Performance Test X X X X X X X XLAT Limited Performance Test X X X X X X X X X X X XLAT001 – LAT Config 1 Power On 1 1 2 2 2 2 X 2 X 2 2 2 1 X 1 X 1 X 2 X 2 2 2 X 1 1 X 1LAT002 – LAT Config 2 Power On 1 1 2 2 2 2 X 2 X 2 2 2 1 X 1 1 X X 2 2 X 2 X 2 1 X 1 1LAT003 – LAT Config 3 Power On 1 1 1 1 1 1 1 1LAT004 – LAT Config 4 Power On 1 1 1 1 1 1 1 1LAT005 – LAT Config 5 Power On 1 1 1 1 1 1 1 1LAT006 – LAT Config 6 Power On 1 1 1 1 1 1 1 1LAT007 – LAT Config 7 Power On 1 1 1 1 1 1 1 1LAT008 – LAT Config 8 Power On 1 1 1 1 1 1 1 1LAT009 – LAT Config 9 Power On 1 1 1 1 1 1 1 1LAT011 – LAT Config 1 Power Off 13 1 2 2 2 2 X 2 X 2 2 2 13 X 13 13 X 13 13 13 13 13 13 13LAT012 – LAT Config 2 Power Off 13 1 2 2 2 2 X 2 X 2 2 2 13 X 13 13 X 13 13 X 13 13 13 13 13LAT013 – LAT Config 3 Power Off 13 1 13 13 13 13 13 13LAT014 – LAT Config 4 Power Off 13 1 13 13 13 13 13 13LAT015 – LAT Config 5 Power Off 13 1 13 13 13 13 13 13LAT016 – LAT Config 6 Power Off 1 1 1 1 1 1 1 1LAT017 – LAT Config 7 Power Off 1 1 1 1 1 1 1 1LAT018 – LAT Config 8 Power Off 1 1 1 1 1 1 1 1LAT019 – LAT Config 9 Power Off 1 1 1 1 1 1 1 1LAT021 – LAT Config 1 Reinitialization 1 1 1 1 1 1 1 1LAT022 – LAT Config 2 Reinitialization 1 1 1 1 1 1 1 1LAT023 – LAT Config 3 Reinitialization 1 1 1 1 1 1 1 1LAT024 – LAT Config 4 Reinitialization 1 1 1 1 1 1 1 1LAT026 – LAT Config 6 Reinitialization 1 1 1 1 1 1 1 1LAT031 – LAT Config 1 Elect Power Subsys Perf 3LAT041 – LAT Config 1 Estab B/L Science Ops Config X 10 10 10 10 10 XLAT042 – LAT Config 2 Estab B/L Science Ops Config X 10 10 10 10 10 XLAT051 – LAT Config 1 Register Test 12 12 2 2 2 2 2 2 2 2 1 1 1 2 2 2 2 1 1 1LAT052 – LAT Config 2 Register Test 12 12 2 2 2 2 2 2 2 2 1 1 1 2 2 2 2 1 1 1LAT061 – LAT Config 1 SIU/EPU H/W Funct 1 1 1 1 1 1 1 1LAT062 – LAT Config 2 SIU/EPU H/W Funct 1 1 1 1 1 1 1 1LAT071 – LAT Config 1 Energy Meas Calib X X X X X X X XLAT121 – LAT Config 1 Science Modes X XLAT122 – LAT Config 2 Science Modes X XLAT131 – Config 1 LAT/Spacecraft I/F 1 1 2 2 2 2 2 2 2 2 1 1 1 2 2 2 2 1 1 1,4LAT132 – Config 2 LAT/Spacecraft I/F 1 1 2 2 2 2 2 2 2 2 1 1 1 2 2 2 2 1 1 1LAT133 – Config 3 LAT/Spacecraft I/F 1 1 1 1 1 1 1 1LAT134 – Config 4 LAT/Spacecraft I/F 1 1 1 1 1 1 1 1LAT135 – Config 5 LAT/Spacecraft I/F 1 1 1 1 1 1 1 1LAT141 – Config 1 LAT/Spacecraft I/F with the SIIS XLAT151 – LAT Config 1 Ambient TCS Test 5 6 6 6LAT152 – LAT Config 2 Ambient TCS Test 5 6 6 6

NRL



LAT Level Test Program LAT Level Test Program (2 of 2)(2 of 2)SLAC

Test Title

Bas

elin

e L

AT

NR

L P

ost-

Ship

Pre

-Sin

e V

ibe

Pos

t X-A

xis

Vib

e

Pos

t Y-A

xis

Vib

e

Pos

t Z-A

xis

Vib

e

Pos

t Rad

Ins

tall

Pre

- E

MI/

EM

C

EM

I/E

MC

Tes

t

Pos

t-E

MI/

EM

C

Pre

-Aco

ustic

Pos

t-A

cous

tic

Pre

-TV

Bak

e-ou

t

Hot

The

rmal

Bal

Hot

Pro

toqu

al

Hot

to C

old

1

Col

d S

urvi

val

Col

d P

roto

qual

Col

d T

herm

al B

al

Col

d to

Hot

1

Hot

Pla

teau

2

Hot

to C

old

2

Col

d P

late

au 2

Col

d to

Hot

2

Hot

Pla

teau

3

Hot

to C

old

3

Col

d P

late

au 3

Col

d to

Hot

3

Hot

Pla

teau

4

Hot

to C

old

4

Col

d P

late

au 4

Col

d to

Hot

4

Fin

al L

AT

LAT161 – LAT Config 1 Ambient Survival Heater Test 7 7 7 7LAT162 – LAT Config 2 Ambient Survival Heater Test 7 7 7 7LAT171 – LAT Config 1 Cond & Rad Emissions XLAT172 – LAT Config 2 Cond & Rad Emissions XLAT181 – LAT Config 1 Cond & Rad Susceptibility XLAT201 – LAT Config 1 Science Performance Diag 12 XLAT202 – LAT Config 2 Science Performance Diag 12 XLAT211 – LAT Config 1 Timing Measure & Adjust X X X XLAT212 – LAT Config 2 Timing Measure & Adjust X X X XLAT221 – LAT Config 1 Science Ops Demo 1 1 2 2 2 2 2 X 2 2 2 1 X 1 X 1 X 2 X 2 2 2 X 1 1 X 1LAT222 – LAT Config 2 Science Ops Demo 1 1 2 2 2 2 2 X 2 2 2 1 X 1 1 X X 2 2 X 2 X 2 1 X 1 1LAT223 – LAT Config 3 Science Ops Demo 1 1 1 1 1 1 1 1LAT224 – LAT Config 4 Science Ops Demo 1 1 1 1 1 1 1 1LAT225 – LAT Config 5 Science Ops Demo 1 1 1 1 1 1 1 1LAT226 – LAT Config 6 Science Ops Demo 1 1 1 1 1 1 1 1LAT231 – LAT Config 1 GRB Handling 1 1 2 2 2 2 2 2 2 2 1 1 1 2 2 2 2 1 1 1LAT232 – LAT Config 2 GRB Handling 1 1 2 2 2 2 2 2 2 2 1 1 1 2 2 2 2 1 1 1LAT234 – LAT Config 4 GRB Handling 1 1 1 1 1 1 1 1LAT235 – LAT Config 5 GRB Handling 1 1 1 1 1 1 1 1LAT301 – LAT Config 1 ACD CPT 1,9 1 1 1 1 1 1 1LAT302 – LAT Config 2 ACD CPT 1 1LAT311 – LAT Config 1 ACD LPT 2 2 2 2 2 2 2 2 2 2 2 2LAT312 – LAT Config 2 ACD LPT 2 2 2 2 2 2 2 2 8 8 8 2 2 2 2 8 8 8LAT401 – LAT Config 1 Calorimeter CPT 1,9 1 1 1 1 1 1 1LAT402 – LAT Config 2 Calorimeter CPT 1 1LAT411 – LAT Config 1 Calorimeter LPT 2 2 2 2 2 2 2 2 2 2 2 2LAT412 – LAT Config 2 Calorimeter LPT 2 2 2 2 2 2 2 2 8 8 8 2 2 2 2 8 8 8LAT501 – LAT Config 1 Tracker CPT 1,9 1 1 1 1 1 1 1LAT502 – LAT Config 2 Tracker CPT 1 1LAT511 – LAT Config 1 Tracker LPT 2 2 2 2 2 2 2 2 2 2 2 2LAT512 – LAT Config 2 Tracker LPT 2 2 2 2 2 2 2 2 8 8 8 2 2 2 2 8 8 8LAT521 – LAT Light Tight Test X XLAT651 – LAT Config 1 False Triggers X XLAT661 – LAT Config 1 Data Transport Errors X XLAT701 – LAT Config 1 SVAC Flight Config on Gnd X X X X X X XLAT702 – LAT Config 2 SVAC Flight Config on Gnd X X X X X X XLAT711 – LAT Config 1 SVAC Muon Calibrations X X X X X X XLAT801 – LAT Config 1 SVAC Pwr Feed Min Voltage X X X X XLAT811 – LAT Config 1 SVAC Pwr Feed Max Voltage X X X X XLAT812 – LAT Config 2 SVAC Pwr Feed Max Voltage X X X X XLAT821 – LAT Config 1 SVAC High Trigger Rate X X X X XLAT831 – LAT Config 1 SVAC High Trig Rate Muon Gain X X X X XLAT841 – LAT Config 1 SVAC High Trig Rate, Min Volt X X X X XLAT851 – LAT Config 1 SVAC High Trig Rate, Max Volt X X X X XLAT852 – LAT Config 2 SVAC High Trig Rate, Max Volt X X X X XLAT901 – LAT Config 1 FSW File System Verification XLAT902 – LAT Config 2 FSW File System Verification X

NRL



LAT Level Verification SummaryLAT Level Verification Summary

Verification Terminology– Requirement Identified: Reqt documented in Level 2B and/or Level 3 specification– Flow Down Complete: Flow down to Level 3 of Level 2A/2B requirement complete– Draft VP: Draft VP has been written and submitted to LAT team and customer for review– Final VP: Customer, Systems, and reqt owner have agreed on the contents of the VP– VP Executed: Verification plan has been executed

– Report Submitted: Draft RVR or report has been provided to the customer for review

– Requirements Sold: RVR or report approved by customer and released into LAT Docs

– Expect Compliance: RVR not submitted, but preliminary analysis indicates LAT will comply– VP Deferred: Plan execution deferred beyond post-ship

– Requirements Issue: Stale requirement or waiver required

Test Demo Analysis Inspection Children

# Comp # Comp # Comp # Comp # Comp Complete % CompRequirement Identified 124 73 204 36 22 459 100.0%Flow Down Complete 124 73 204 36 22 459 100.0%Draft Verification Plans 124 73 204 36 22 459 100.0%Final Verification Plans 124 73 204 36 22 459 100.0%Verification Plans Executed 82 54 156 23 14 329 71.7%Verification Reports Submitted 82 54 156 23 14 329 71.7%Requirements Sold 51 42 100 13 13 219 47.7%

Expect Compliance 23 0 25 12 2 62 13.5%Verifications Plan Deferred 18 19 19 1 6 63 13.7%Requirements Issues 1 0 4 0 0 5 1.1%Total VPs 124 73 204 36 22 459

CategoryVerification Method

Totals



Requirement Sell-off StatusRequirement Sell-off Status

Aside for the requirement issues, reports for all VPs planned for pre-ship execution have been submitted to the customer

No issues are anticipated in the remaining requirements– Only a paperwork exercise remains to sell the remaining VPs

RVRs have been submitted for all Pre-Ship VPs

Verification Reports Submitted 329 98.5%Requirements Sold 219 65.6%Requirement Issue 5 1.1%VPs Sold/Submitted Sub-Total 329 98.5%VPs Executed Prior to Pre-Ship 334 100.0%

Expect Compliance 62 13.5%Verification Plans Deferred 63 13.7%VPs for Future Execution Sub-Total 125 27.2%Total VPs 459 100.0%

Post-Ship Verifications

Pre-Ship Verifications

VP Status CategoryNumber at

Status Level% Complete



Interface Verification MethodologyInterface Verification Methodology

LAT/SC Interface verified primarily by test and demonstration– Interface demonstrated by SIIS power up of the LAT in LAT141

– All SC/LAT prime, redundant, and cross-strapped interfaces extensively tested by test case LAT13x, using the VSC

– Some unit level test and analysis of interface and interface data also utilized

All verification details are provided in the associated RVRs and the results summarized in the VCRM

The hardware performance of all LAT/SC Interfaceshas been verified



Interface Verification StatusInterface Verification Status

Aside for requirements issues, reports have been submitted to the customer for all interface VPs

~67% of all interface requirements have been sold No issues are anticipated for the remaining requirements

– Only a paperwork exercise remains to sell the remaining VPs

All Interface requirements will be verified

Verification Reports Submitted 60 98.4%Requirements Sold 40 65.6%Requirements Issues 1 1.3%VPs Sold/Submitted Sub-Total 60 98.4%VPs Planned for Pre-Ship Sell-off 61 100.0%

Expect Compliance 10 12.8%Verification Plans Deferred 7 9.0%VPs for Future Execution Sub-Total 17 21.8%Total VPs 78 100.0%

Post-Ship Verifications

VP Status CategoryNumber at

Status Level% Complete

Pre-Ship Verifications



Post-Ship Interface Compliance PlanPost-Ship Interface Compliance Plan

Deferred Interface VPs – 7 VPs total– All deferred interface VPs are related to LAT/GBM messaging requirements

from the LAT/GBM ICD– All physical interfaces have been verified– ECD: 15 Dec 06

Expect Compliance Interface VPs – 10 VPs total– All VPs related to TV analysis– Preliminary analysis indicates the LAT will comply with margin– ECD: 1 Nov 06

Requirements Issue Interface VPs – 1 VPs total– VP related to Symmetrical Common & Differential Mode impedance

• Current requirement is stale

– Plan forward• Analysis of measured data from LAT and SC has indicated no issues• IRD/ICD requirements need to be deleted

– IRD change to be documented by CCR• CCR in coordination with SASS

– ECD: 15 Nov 06



Post-Ship Compliance Plan Post-Ship Compliance Plan (1 of 2)(1 of 2)

Deferred VPs – 63 VPs total– Gamma Ray Burst (GRB) FSW upgrades provided by FSW B1.0.0

account for 60 of the deferred VPs• FSW awaiting GRB algorithm definition from scientific community• Target of Opportunity (TOO) and Automatic Repoint Request (ARR)

functional requirement also included in this set• ECD: 15 Dec 06

– Remaining 3 VPs are those related to Observatory environments• Observatory shock tests• Four additional thermal cycles acquired by LAT at Observatory TV• ECD: 30 days following Observatory TV



Post-Ship Verification Plan Post-Ship Verification Plan (2 of 2)(2 of 2)

Expect Compliance VPs – 62 VPs total– 51 VPs related to TV analysis and LAT Thermal Model correlation

• ECD: 1 Nov 06

– 6 VPs related to the just executed Mass Properties tests• ECD: 15 Oct 06

– 5 VPs related to EMI/EMC Testing• ECD: 15 Oct 06

– Preliminary analysis indicates the LAT will comply with margin • Excluding EMI, see the EMI/EMC Test Results presentation



Requirements IssuesRequirements Issues

Requirements Issues – 5 VPs total– 2 VPs related to Symmetrical Common & Differential Mode

impedance• Current requirements are stale• Plan forward

– Analysis of measured data from LAT and SC has indicated no issues– IRD/ICD requirements need to be deleted

• ECD: 15 Nov 06

– 1 VP related to Radiator Cut-outs venting in the wrong direction• In coordination with SASS; initial assessment: No issue• ECD: 15 Nov 06

– 2 VPs require internal waivers – no impact to LAT performance or Observatory level test

• Both waivers to T&DF Level 3 Spec, LAT-SS-00019– CAL TACK Latency: LAT-XR-08615– Subsystem Deadtime Contribution Measurements: LAT-XR-08616

• ECD: 15 Nov 06



LAT ComplianceLAT Compliance

All Level 2A & ICD reqts have been flowed down with traceability All VPs have been reviewed and approved by the customer All VPs planned for execution prior to shipment have been

executed RVRs for 98.5% of the VPs planned for execution prior to ship

have been submitted to the customer – Requirement issues are all understood, only the paper trail remains

to be completed, i.e. there is no risk A plan to full requirements sell-off has been provided

– Due to thorough test, data review, and analysis programs, no issues are anticipated for the remaining requirements to be sold

• All performance reqts in this group have been verified by preliminary analysis, i.e. Thermal, Mass Props, and EMI

• All other requirements are functional, i.e. GRB, TOO, and ARR

Full LAT compliance is expected


LAT Requirement VerificationPresentation 5 of 12

GLAST Large Area TelescopeGLAST Large Area Telescope

Gamma-ray Large Gamma-ray Large Area Space Area Space TelescopeTelescope LAT Pre-Shipment Review

LAT LevelRequirement VerificationBack-up Charts

Rich BaunSystems Engineering



Performance & Operations Test PlanPerformance & Operations Test Plan

All test cases are defined in detail in the Performance and Operations Test Plan (LAT-MD-02730-05)– The plan identifies 6 categories of test cases to be run:

• 13 test cases for the LAT CPT• 6 LAT LPT test cases• 12 SVAC/ETE test cases• 3 LAT calibration test cases• 2 LAT Level test cases• 1 one-time hardware verification test

– All requirements sold by Test and Demo are allocated to test cases by the Perf & Ops Test Plan

– All functions to be validated are also allocated to test cases by the Perf & Ops Test Plan

– The plan was reviewed by NASA Systems and approved by LAT Systems, ACD, CAL, ELX, FSW, I&T, MECH, Thermal, & TKR



LAT Level Test Case Summary LAT Level Test Case Summary (1 of 2)(1 of 2)

Item Test Case ID Test Case Name Redundancy Configurations

1 2 3 4 5 6 7 8 9

1 LAT00x LAT Power On X X X X X X X X X

2 LAT01x LAT Power Off X X X X X X X X X

3 LAT02x LAT Reinitialization X X X X X

4 LAT031 LAT Electrical Power Subsystem Performance X

5 LAT04x Establish Science Operations Configuration X X

6 LAT05x LAT Register Test X X

7 LAT06x SIU/EPU Hardware Functional X X

8 LAT071 LAT Energy Measurement Calibration X

9 LAT12x LAT Science Modes X X

10 LAT13x LAT/Spacecraft I/F Functional X X X X X

11 LAT141 SIIS LAT/Spacecraft I/F Functional X

12 LAT15x LAT Ambient TCS Test X X

13 LAT16x LAT Ambient Survival Htr Test X X

14 LAT17x LAT Conducted & Radiated Emissions X P

15 LAT18x LAT Conducted & Radiated Susceptibility X

16 LAT20x LAT Science Performance Diagnostics X X

17 LAT21x LAT Timing Measure & Adjust X X

18 LAT22x LAT Science Ops Demo X X X X X X

19 LAT23x LAT GRB Handling X X X X



Item Test Case ID

Test Case Name Redundancy Configurations

1 2 3 4 5 6 7 8 9

20 LAT30x LAT ACD CPT X

21 LAT31x LAT ACD LPT X X

22 LAT40x LAT CAL CPT X

23 LAT41x LAT CAL LPT X X

24 LAT50x LAT TKR CPT X

25 LAT51x LAT TKR LPT X X

26 LAT521 LAT Config 1 Light Tight Test X

27 LAT651 T&DF False Triggers X

28 LAT661 T&DF Data Transport Errors X

29 LAT70x LAT SVAC Flight Config on Gnd X X

30 LAT711 LAT Config 1 SVAC Muon Calibration X

31 LAT801 LAT Config 1 SVAC Condition Scan (27 V) X

32 LAT811 LAT Config 1 SVAC Condition Scan (29 V) X

33 LAT821 LAT Config 1 SVAC Nominal Rate CR X

34 LAT831 LAT SVAC Nominal Rate CR Data Volume X

35 LAT841 LAT SVAC Nominal Rate Condition Scan CR X

36 LAT85x LATSVAC Nominal Rate Condition Scan CR X X

LAT Level Test Case Summary LAT Level Test Case Summary (2 of 2)(2 of 2)



LAT Redundancy ConfigurationsLAT Redundancy Configurations

SC-P SC-R SIU-P Feed

SIU-R Feed

Pri Htr Feed

Red Htr Feed

SIU-P SIU-R GASU-P GASU-R EPU-P0 EPU-P1 EPU-R Towers ACD ACD HV1

ACD HV2

+Y HCB

-Y HCB

PDU-P PDU-R

1 On - On - On - On - On - On On - On On On - On On On -2 - On - On - On - On - On - On On On On - On On On - On3 - On On - On - On - - On On On - On On On - On On On -4 On - - On On - - On - On On - On On On - On On On On -5 - On - On - On - On On - On - On On On - On On On - On6 On - On - - On On - On - - On On On On On - On On - On7 - On - On On - - On On - On - On On On - On On On On -8 On - - On - On - On - On - On On On On On - On On - On9 - On On - On - On - - On On On - On On - On On On - On

On On- -

Config No.LAT UNITS ON

= Unit is powered On in the LAT Config specified = Unit is powered Off in the LAT Config specified



Test Case Run ReviewTest Case Run Review

Test Case Run Review– Test cases are run by I&T in virtually any order

• Systems/Commissioner should review plans to insure all case interdependencies are considered

– After each test case is run, I&T reviews the data and notifies Systems that a run was valid

• A valid run is one in which there were no script, database, test set, test software, configuration errors, or operator errors that invalidate the test

• This review must be within 24 hours of test execution• Obviously, any issues determined to be anomalies must be reported

through the appropriate system (JIRA or NCR)– Test script, software, and config file errors must be documented

– I&T must establish and maintain a Test Case Review Log that contains the following minimum information

• Test case name and number, script, start time, run number, LAT configuration discrepancies, I&T reviewer, and the numbers of any NCRs or JIRAs written during the test case

– Log should allow space for expert/Systems sign-off



Test Case Run Buy-offTest Case Run Buy-off

Test Case Run Buy-Off– Once I&T has indicated a test run is valid, Systems, the

Commissioner and/or assigned experts will review the run data

– Buy-off Process• Each test case will have at least one assigned reviewer

– Systems Engineering will produce a matrix of who is responsible to review test case/requirement data

– Requirement owners will also review the data collected in each test case that is pertinent to their requirements

– Reviewers and requirement owners will sign-off on the Test Case Review Log when review is complete

• If the reviewer finds the run sufficient, they note the test case as “complete” on the Test Case Review Log

– Test cases with more than one reviewer are not sold until all sign-off

• If a reviewer detects an anomaly or that the run was insufficient, they will report this through appropriate documentation (NCR)

– A NCR is needed to justify modification or a re-run of the test

• Buy-off must be complete within one week of test execution or before test exit, which ever occurs first



Requirement Sell-Off (Requirement Sell-Off (1 or 21 or 2))

Requirement Sell-Off, High-level approach– Only functional requirements will be sold in the Baseline LAT Test (or at the

earliest opportunity)– All performance requirements will not be sold until after all environments

have been completed, that is following TV• Performance requirement owners will be expected to look at performance data

from all test phases and perform an “early” assessment

– Environmental requirements will be sold only after testing in the appropriate environment is performed

• For example, vibe related requirements will not be sold until after Sine-Vibe

Requirement Sell-Off, Concept of Operations– Nominally, each requirement owner will have 1 week after test execution to

review the test data• Owners requiring longer time periods will need to negotiate with Systems

– For most requirements, simply executing the test case and certifying by review the test was successful is sufficient for sell-off as reported in an RVR

• For each requirement, reviewer names, when the data was reviewed, test case numbers, scripts, run times, and run numbers will be logged in the VCRM



Requirement Sell-Off (2 of 2)Requirement Sell-Off (2 of 2)

Requirement Sell-Off, Concept of Operations (continued)– The requirement owner will have 2 weeks after test execution to

produce a Requirement Verification Report (RVR)• Owners requiring longer time periods will need to negotiate with

Systems• Once an RVR is written, it will be reviewed and approved by Systems

and submitted to the customer

– Submit RVRs to customer for review and approval• Incorporate customer comments if any• Release RVRs into LAT Docs with customer approval• Test Reports can replace RVRs

– Meetings to review RVRs can be held at customer request• The customer, the Commissioner, Systems, and the appropriate

requirement owners attend

– The VCRM documents all requirement sell-off and provides traceability from requirement to RVR



Requirements Verification ReportsRequirements Verification Reports

For an agreed to subset of LAT requirements only, not all reqts Must have an assigned LAT Docs number Minimum RVR contents

– Requirement owner’s name– Requirement source, text, and number– Verification Plan text and number– Supporting test case name and number (if applicable)– Script name(s) used to run test– Date, time, and run number when supporting test case(s) were run

• If data was collected from multiple runs, each run must be noted

– Compliance statement, i.e. the report must state definitively the LAT complies with the requirement

• Margin to the requirement must be stated where appropriate

– Supporting documentation of test data, analysis, and results– Deviations from the verification plan and the reasons for the deviations must

be stated– Any NCRs or JIRAs associated with the requirement must be listed

glast lat projectseptember 15, 2006: pre-shipment review lat requirement verification presentation 5...

Documents

lat level requirements

verification level

lat level verification

glast lat projectseptember

verification methods

requirement slide

lat performance spec

plan verification reports