NNJ06TA25C MODIFICATIONS - NASA

OMB Approval #: 2700-0042 

1 CONTRACT 10 CODE PAGE OF PAGES 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 01 1 

1 

2 

2. AMENoMENTIMODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 15. PROJECT NO. (lfappllcab/e) 

01 See Block 16C 4200177961 

6. ISSUED BY CODE BT / JPl 7. ADMINISTERED BY (If other than Item 6) CODE 

L 

NASA Lyndon B. Johnson Space Center 

Attn: Caroline Marrs Root, CO, Mail Code BT 

2101 NASA Parkway 

Houston, TX 77058 

8 NAME AND ADDRESS OF CONTRACTOR (No., street, county, State, and ZIp Code) 

~ 

9A. AMENDMENT OF SOLICITATION NO. 

Lockheed Martin COIporation 

Attn: James Blackwell 9B DATED (SEE ITEM 11) 

P.O. Box 179 Mail Stop L3008 

Denver, Colorado 80201 

X 

lOA MODIFICATION OF CONTRACTIORDER NO 

NNJ06TA25C 

lOB. DATED (SECE ITEM16c) 

CODE 100141 I FACILITY CODE 04236 09/08/2006 

o The above numbered solicitation Is amended as set forth In Item 14. The hour and date specified for receipt of Offers Is extended, Is not extended. 

Offers must acknowledge receipt of this amendment p~or to the hour and date specified In the solicitation or as amended, by one of the following methods: 

(a) By completing Items 8 and 15. and returning __ copies of the amendment. (b) Byacknowledglng receipt of this amendment on each copy of the offer submitted; or (c) By 

separate letter or telegram which Includes a reference to the solicitation and amendment numbers FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE 

PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER If by virtue of this 

amendment you desire to change an offer already submitted. such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation 

and this amendment. and Is received p~or to the opening hour and date speclfled. 

12. ACCOUNTING AND APPROPRIATION DATA (If required) 

72-644423 FC400000 644423.01.30 72ZVll ESAX22006D 

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS, 

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14. 

(xl A. THIS CHANGE ORDER IS ISSUED PURSUANT TO' (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN 

THE CONTRACT ORDER NO IN ITEM lOA 

X 

B THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes In payIng office, 

aptJ{Opriatlon date etc.! SET FORTH IN ITEM 14 PURSUANT TO THE AUTHORITY OF FAR 43.103lbl. AND CONTRACTOR'S LETTER DATED 31312005 

C THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO 

PURSUANT TO AUTHORITY OF' 

o OTHER (Specify type of modlflcatlon and authOrity) 

Pursuant to FAR 52.232-22, Limitation of Funds (ApnI1984) 

E. IMPORTANT: Contractor l8!is not, 0 Is required to sign this document and return __ copies to the Issuing office. 

14 DESCRIPTION OF AMENDMENTIMODIFICATION (Organized by UCF section headings, Including soliCItation/contract subject matter where feasible) 

The puxpose of this Modtfication 1 is to add incremental funding to this contract. 

See Page 2 for a description of the modification. 

ExceDt as Drovlded herein all terms and conditions of the document referenced In Item 9A or lOA. as heretofore changed remains unchanged and In full force and effect. 

15A. NAME AND TITLE OF SIGNER (Type or print) 16A NAME AND TITLE OF CONTRACTING OFFICER (Type or print) 

Caroline Marrs Root 

Contracting Officer 

15B CONTRACTOR/OFFEROR 15C. DATE SIGNED 16B UNITED STATES OF AMERICA 16C. DATE SIGNED 

(Signature of person authonzed to sign) 

NSN 7540.Q1-152-8070 

PREVIOUS EDITION UNUSABLE 

BY 

30-105 

Onglnal Signed by Caroline Marrs Root 9/21/2006 

(Signature of Contract/na Officer) 

STANDARD FORM 30 (Rev. 10-83) 

Presc~bed by GSA 

FAR (46 CFR) 53.243


Modification 01 

Page 2 of2 

The purpose of this modification is to proVIde mcremental fundmg in the amount of$563,000,000; hereby increasing the allotted 

amount from $27,000,000 to $590,000,000. Funding recapitulation is shown below: 

Cost 

Fee 

Total 

Previous This Mod 1 

27,000,000 563,000,000 

New Total 

590,000,000 

The contract is changed in the following particulars: 

I. Clause B4. CONTRACT FUNDING (NASA 1852.232 81) (JUN 1990), is hereby deleted in its entirety and the revised clause B4 

shown below is substituted in lieu thereof: 

B.4 CONTRACT FUNDING (NASA 1852.232-81) (JUN 1990) 

a. For purposes of payment of cost, exclUSive of fee, m accordance with the Limitation of Funds clause in Section I, the total 

amount allotted by the Govermnent Schedule A is an estimate for the period of performance June 30, 2007. 

b. Schedule A contract funding summary: 

Schedule A 

TOTAL 

$590,000,000 

(End of clause) 

II. All other terms and conditions of the contract remain unchanged and in full force and effect.

OMB Approval #: 2700-0042 

1. CONTRACTIDCODE 

PAGe OF, PAGES 

AMENDMENT OF SOLICITATJONIMODIFICAnON OF CONTRACT 01 1 2 

2. AMENDMENTIMODIFICAl1ON NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REO. NO. I 5. PROJECT NO. (If applicable) 

12 See Block 16C 4200202158 

S. ISSU~DBY CCCE BTfJPI 7. ADMlNlmRED BY (If other thIn Item 6) CODE 

I 


Attn: Bradley J. Niese, Mail Code BT 

2101 NASAParlc\vay 

Houston, TIC 77058 

8. NAME AND ADDREilS 01' CONl'RACTOR (No., """'" c:ounty, state, and ZIp Code) 

Lockheed Martin Corporation 

Attn: James Blackwell 

P.O. Sox 179 Mail Stop LJ008 

Denver, Colotado 80201-0719 

~ 

X 

I 

eA. AMENDMENT OF SOliCITATION ND. 

98. DATED (SEE ITEM II) 

lOA. MODIFICATION OF CONTRACTIORDER NO. 

NNJ06TA2SC 

lOB. DATED (SECE lTEMI~) 

CODE 100141 I FACILITY CODE 04236 09f08/2006 

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS 

o The above numbenld ICIICItaIIOn IUmended ..... 1OIth In Item 14. The hour IIrId d .... p.olfteci for receipt of 0Ire" 0 ,,4IlCIendtd. 0 "nat extended. 

OIreIImuli aci



Page2of2 

The purpose of this modification is to provide incremental funding in the amount of $4.890.389; hereby increasing the allotted amount 

from $590.000.000 to $594.890.389. Funding recapitulation is shown below: 

Previous 1 TIdsModU I NewTotaJ I 

Cost 

'o~ b-\' i-ltf' 

1 

Fee 

L 

-' 

Total S 590.000.000 J $ 4.890.389 I $ 594.890.389 J 

The contract is changed in the following particulars: 

I. Clause 84. CONTRACT FUNDING (NASA 1852.23281) (1UN 1990). is hereby deleted in its entirety and the reVIsed clause 84 

shown below is substituted in lieu thereof: 

8.4 CONTRACT FUNDING (NASA 1852.232·81) (JUN 1990) 

a. For purposes of payment of cost, exclusive of fee. in accordance with the Limitation of Funds clause in Section I. the total 

amount allotted by the Government Schedule A is an estimate for the period of performance October 17. 2007. 

b. Schedule A contract funding summary: 

Schedule A 

COST 

bf 

FEE 

bf 

(End of clause) 

TOTAL 

$594.890.389 

II. All other terms and conditions of the contract remain unchanged and in full force and effect.

OMB Approva IN 0.27 ()O. 0042 

AMENDMENTO'SO~~rrATIOW Jl CQIoITIVICIIU COllI: I PAll~ OF rAGES 

MODIFICATION OF coNTRACT I NNJClI'.T A "~(' I I I .!!JP 

~. I NO. ~ : nAT!;' • J>I' lII«':IlAllli RM NO I ~ ""'" ,cr.T NO 

18 N1A I N/A 

6 ISSUEOUV I cooe 7 AOMIN1S1~neOIlV(!I""""_'_6J (COOE I 

NASA I.yndon B. Johllslln Spuw Ccnter 

Alln: LlT/J"~~lca Corley 

210 I NASA PUrllWllY 

1I0118tOIl. TX 1705f1 

~PP~D 

LL~~ 

It ........ • 1 OJ: 11No .. ·""" ._ ...... J&"YI1'O( [l~ENT 

l.ockhL'Cd Marlin Corpol

I. (a). Clause 0.3, Estimated CQst and AWard Fee, for completion form work is 

summarized as follows: 

Elemcnt From I To Changc 

Estimated Cost I LL I JL _ 

bf 

Fee 

PI 

4/{ ~ 

- 

I 

Total I 54.270,600,905 I $4,329,791,521 559,190,616 - 

NNJ06TA2SC 


Page 2 

(b). 0.3 Estimated Cost and Award Fee is deleted in its entirity and replaced with the 

following: 

"B,3 ESTIMATED COST AND A W AID FEE tNFS 1152.216-85> (SIP 1993) 

•• The estimated cost and award fee for Schedule A (base foe not applicable) of this contract 

is broken out as follows: 

Completion form work 

(all work not identified as 101Q) btj 

i 

Estimated Mgimwn ThIll S:QJl 

~ Award fee and Award Fee 

• 

he-I ht( 

IDlQ Oelivery Orders Issued·· &q- bY 01- 

Total hI{ Jo'{ 1.1..J,29.1.f1.z'f.Z 

•• NOTE! Work subje

· .' 

NNJ06TA2SC 


Page 3 

6.1.3.6 Mechanisms 

n NASA wID provide the CEV to ISS dOSkinC adapter for ISS dgsking. 

I) The Contractor shaD Integrate the elv to ISS doddD,adapter for two adapter 

deUvea mllslons tq ISS. DI. fgtegr.tlOD Inslpm NASA provided avionk. 

required to operate Andromou. Peripheral A.sembly Systems. 

III. Section]. Attchment J-ll entitled "Government Furnished Property List". and 

Attachment 1-1, "Award Fee Plan, Schedule A" are deleted in their entirety and 

replaced with the attachments to this modification.

ATTACHMENT J-7 

AWARD FEE EVALUAnON PLAN 

CREW EXPLORAnON VEHICLE 

Contract NNJ08TA25C 

Schedule A 

Ayaytt 27· ~~1 ... _ 

. _ 

r,;:---------.---. . 

,~"!!!!... .. _-- .

NNI06Tmc Auachment1-7 Ii"=..-------.'~ 

I L:C:;:.I'O:.:.w:.;Ex=PI::;oratio=· 

,::.D .:.V:::eh:::ic:::Ie;....-..:;(CBV)=.:.!.-___________ 

--.:M:::od=ifi:::cati:::·:;;;OD::.:lII~ u..~ __ . ____ , __ JJ 

I. INDlQpUgnON 

In accordanCe with thl ptOvieIonI of the Federal AIlqulaltlon AlQulatIon (FAA), and NASA and JSC poIfcfll, 

a performanot Muatlon proctdu" Ie hMby aatabIlehlid tor dttetmlnatlon of award .... payable under 

th. oontract. Tk awant fee Ie deaIgned to provide aconomIo motIYatIon tor the Conhctor 10 PfOYIdI 

timely, high quality outpull that .xceed the minimum raqul~ 0/ the oontract. The Inttnt 01 this plan Is 

10 set up jIIOClldUNI tor evaluatIOn of Contractor ptIformanoe uaInO tIdItInQ data and syatamalO the 

maximum IXIiInt Whlle Impoalng minimum acfmlnletratl\lt llurdtn on the CiOvemment and ContIaotor. The 

payment of any aW8ld tee Is oontIngent upon eompIlanot with oonlIaotuaI requlrementa and pedonnance to 

the degreelf*lllac:t below. 

This ccntraot la a hybrid oontI'aot COIlIIIBllng 01 thf81 achtclUllI, SCIIIdUlII A, B, and C. AW8Id fee 

Muallon lor SclledulII A and C ." covered by attachmanta J.7 and J.17, rtapecllvely. Scheclule B 

c:ontaIna BipIltate 1nCentI\118 SIIICHIC to that oontlacl sc:hedule. and Is not lubject to a.i'd fH ptOVIeIona. 

Th. Contractor'. Interkn parfonnanol under Schedule A will be evaluated by NASA at the 8lCp1ra1ion 01 

I80h ptriod 8p11CIlIeclIn EncIoIIn II, Performance Mlleetonll. The Mluatlon to be performed by NASA 

wli be baud on NASA' ....... IntrII'of the COnttacIoI'elCCOl'llpl/ahment 0/ the vadoua .... of WOIIt 

~ by the Sw.ment Of WorJc.ln accordance with the tao\OI8, ~n"" ptOCadurI8, and other 

(IIOVI8IcInIi8lt foIth below. 

The .mount of a~e Awant Fee In _ P*Iod Is 'ubliIOt to eqult8blt id/..unenlilarillng flOll'l chengee 

or otheroonrict 1fIOd1llclillOnl. The 8IIIOUIit 01 the Awant 1". to be paid Is determined by the 

GowIrIrntnI'a evaI~ 0/ the CcInIracIoft partarmanoe In '*"" 0/ the orItarilltated In .... oontraot. Thle 

determination and ttMi hIeIhocIOIOgy, rot d4ItermInlnO N AWIIII Fee .,. unllaterald.olelonl mede eo/ely at 

tha dIscINIIoh Of the Governrntnt. The eJovemment may unll&te!allY ChanQt any a_ of this plan nOl 

otherwlle Nqulrlng mutual agreement under the oontract. Such ctI8ngea wll be made prior to the 

beginning 0/ an llVllualiOn J*Ibd to which the changet eppIy by \IIT18Iy notice to the contfaotor In writing. 

The COrItt8CIDr will be Informed o/any changee to the llVlluatlon criteria or the welghtfnga prior 10 the 

affected AWIId Fee period. 

Each awald '" evaluation. with the m:aptiOn of the Iaat evaluatlon, will be an IntetIm evaluallon and 11\. 

COI'f8IPOIIdInO tee payment 18 pnlVIllonaI only. All Interim evalua~ and provisional tee paymente will be 

superseded by the llna! evaluation and fee deterrnlnltlon lor SchIIdIIIe A. 

Attachment J·7 

Page2of8

IL 

gRQANIZADONAb tmucnJM 

A. '-fotnIInce I!vaIlIItIon loan! IntegrltJon T_ (PEB-IT) 

The pEB-rr wtU be compoaad of aeIeded NASA technical and admlnlalrative pel8Ol1llei and headed by the 

ContraCtIiIa OffIceI'a Technical Repraaenta1lVe (COTR). The COTR Will be the roc.! point for the 

accumulatIOn and devt/Opmtnt 0/ A~' F .. evaluation reporII. rlVlewe. and preaantallolw. as weft aa 

dlllCU88lon!l with Contractct manaoament 011 Award F .. matte". The PEB-rr Will evaluate the

11L..,;~;.;.;rew;.;.;I06...;;ix.;.;o~;;;.;lo""~=n_v",,eh;.;.;iC....;,le_-.:..(CBV)....;....:,-___________ 

~.;...~_ifi_C_atiOlI_· 

The FDO Win consider thl recommendation 01 thl PEl, PEB-IT Report, Information provided by th& 

CClnlraotor, If any, and any other pelllnent Information In d8l1IImInlng the ptIformance ecore. The FOOl 

delllrminalion 01 thl IICOrI will be lilted In a wrItlIIn Award F .. Dttennlnatlon and will be plOVlded 10 1111 

ContIICIOf by the contracting 0II1cer within 48 calendar days attar IhI end 0I1hI evaluation plllod. 

-7;...;.. 

t_l lA 

.... 

.... 

, tL~_-==== D 

II. IYN.lIA'I\ON PRQCIQURQ 

Schedule "AM DOTal 

NASA will evaluatIIlhiI contIMt IIChlduieln ~ with 1111 cIIuae NFS 1852,218-77, Award Fee For 

End "*" ContracfII. £ach award 'ee pl/lod wtU be baled on objectlw project mUeatortet IdentlfIad In !hie 

plan end CQ'l\r8CllIChed\lle. ElICh Inllrtm award fee period and provisIOnal payment Ie baIIId on the 

ConUacIDr'alucce.tul con\pI8IIon 01 the inHaatone(a) agreed 10 and aaldantifled In !he Contractor'a 

Integl'lllld Maatef8dMlcfull (IMa). The award fee dlstrlbultCn tIbIt contained In EncIoeure II, Performance 

MlIeemeI, pIOVid ... ,'" 01 p6I1omlll'lCe mUllion .. and availlblt provIalonal f .. for each mllellOne. In 

acconfance with NFS 1882.218-1'1. all award fie avaIuatlOnl. with lhIelllCtPllOn 011111 last evaluation. will 

be Inllrtm lYlluaIIonI. 

Ob/ICIIVII and I\I~ CrItIrIa 

NO later dIM 30 ca/endar daya ptIor 10 the 8tIrt of each Irrtellm Aweni P .. evaluation period (mll8lt«Mt), 

the Qo/ItIaCtOt may IIbnIt \0 the ContrIcIIng OffIcer rtoorMIended ~ perfolmlllCe mettlca. 

weIQhIIngt, and A,... 01 rtnphu/I (ACE) for CI;lI'IIIldtretion by NASA 10 be uI8d for the enau/ng evaluation 

period. 

NASA wit tttabIIeh performance rnauIoa and )OE for Hell lYaluatlan perIOd (m ___ ) and communlcatll 

thew \0 the ConIrtootcIt at .... 1 a cellI'Idar days ptIot to 1111 start 01 tadllYaluatton period. NASA may 

un .. 

terally changIIlhl walghlinga 0I1hI crIt8rIa from perIOd to peIfod. Howaver, coat conIIOI wli be 

waIgIMd at no '"' IhU\ 25 pII'CII\l 

Contraotor lilt EvaluatIOn and 8UbmIMIonI 

The Contractor Ihd fIlmllh a eaIf-evaJua1ion for Hell IYaIUIIIon perIOd. The eaIf.-Juation II1IIIt be 

~Ved by tht ConncIInIJ 0II1cer Holklng days prIOI' 10 !he end of the perIOd and IhaII be limited 10 no 

~ tIIIn 20 PIIJ". At the pEl 1I'IMIing., the ConttacIiof may (IIOvIdIa aeIf.tvaIuaIIon preMntltIon (a 

copy, of which IhaII be proyIded 10 the PEl) not to ellCHd 30 mlnutal.1n IIrIgIh. 

The CdnIIIIcIor will bt rum/lhld a copy 01 the ,PEl'. ~D', canoIUI/OnI, and fee recommandatloll. The 

ContracIDr wit be aI/oIIIId thl opportII'Ifty 10 allblnltfor COIIIIdatation of the FDO: (a) pIOJlO8ed evaluallona 

or conc!IuaiorIa or (b) 'liCIp~ 10 the evaluafione. concIueIona. or lee \'8CQIIIIII8Ind1ione 01 the PEl: and 

(0) lupportlnlJ reuorII for 1\ICh ~ or fII'OPOI*d evaluatlona or ccinoIUllonl. The ContraoIor'I 

.1iImIaaIonI m 

... be ~ In WIltIng I!Jd muit be IUbmItted IhrouOII the ContracIInIJ, OffIcer tel the FDO 

wflhIrI 5oWOll/lnlJdays fnIm !he date 01 the ~. ~ 01 the pEe fIrIdI~. If the ConIrIcIor doea 

not provId. ~ InfOrInaIIon 10 the CcInireotInO O/Ifcer within the time etat.d ab!Mt NASA wII 

oonoIucIe that the ContIactor oonoull WIth the .uaIIon and I'tCClI'IIIIIen 1COr&. 

In the event the FI)()"" not /I08IVed • submll8lon fnIm the Contrac\IQt, the per/omIanoe determlnatlOli 

wMl not be exeautad untilJlpilatlon of the &-worklng day period PlIlClIbeci abIMI for ConInIctor 

lJUbmilllOn. The COntraoIior 11181 ~ lIIe 5-worlclng day walIInlJ ptrIod by provldlnlJ • wrItlIIn etatement 

!hat no ~ wi. be IUbmIIied. 

Attachntent J-7 

Page4of8

Attachment 1-7 

L..:::::~==:::....;.;=:::.......:=~ ___________ Mod==ifi::::ca:;:;tio:.;:n~-.J (L ~_~ .____-:=~-D 

The Contractor ahaU submit to the Contracting OffIcer a Corrective ActIon Plan (CAP) lor any weakneaaea 

or tailing abj8c11v8 peI10lmlnce al'llllldenllflld by NASA II part 01 the evaluation. TIll CAP should 

lncIudl a d8lOrtptIon oIlI1e non-oonformance. determlnatlon of \h8 roof cause 011111 non-conformance. 

action raqull8d to correct the weakn ... and fjI'eVtnt *"1i'8nC8I, and the sohldull for compl*llon of tile 

action. The CAP IIhalI be auIlm/tIId to the ContractIng OffIcer within 30 calendar daY' after receipt 01 the 

eacIIlntIrIm peI10rmence dll8rmlnatlon lor the evaluation period. CoII'IcIIV8. ActIn \MIl be cIo8ed by 

__ Iram the Contrsotfng OffIcer and the com. FaQure to 8ubmlt a CAP within 1111 urnerraml 

stated above will reeult In 4 weakneaaln the next ev .. uatlon period. 

InI8rIm FI8dIII\Ck 110 the CoIl1rlOllOr 

During the OOUIM 0/ 4 perIodIo evaluatlqn I*fod. the PEB-IT wi! communlaate willi the evaluation monlto!I 

and 0Ihert II dlllnW ippIOpfIItIlIO IIOIIIIUl whether there ant any a ..... 01 the contraatoI'I perlormanoe In 

which eVIificant IrnpIo\ItI'IItI fa raquk'ld. TIle PSIT wi provide prompt wrllIIn notice II) till contJactor 01 

IWIY such 1IIgnIftcant ...... knOWn to him. and wII alIo hlghllQht oNr areu of BoYtrnll\ellt COIIC8m. For each 

such leIItr fIIuId. the contiIcIDt fa required io reepond In allmely 1TIIIMtr. aetIIng forth plane lor Inc:reaslng 

efIacIIveneas In the ...... Add! a ... d or 8lqlIeInfng why It II hOt taeelll810 do 10. 

TIle need for such IntIrIm I88dbII!.k wi! vary ICOOrdInIl to the oI~ IrwoIv8d, such II till I,""", of 

the 8VIlUItion I*fod. the COI'lbllClal'l ~ In pnwIoua perIOdt ... nature 0/ the WOIk baInG done 

during the period." Henoe. the ~ lain 10 Provide InIIIIm feedback to 1111 contractcr during 

the perliXt;Ht /lot PfICIuda 11'18 GowmnIent from coneIdIIIfng any dtIIcIfncy In the contnICID'" piI1oriMnoe 

In OOIII'1eotlcn with the cMIImlnstlon 01 the amount of. fee to be aWll/l$ld to the contracIor. TypIcally. the 

C30vernInent will prtwIde '''-to the CCI)IraoIor at M/y 3 I'IICII1II1Il durfnO the evalll4t1On perIOd. At a 

minimum. the ~ wi pItIvfde fMdbIok at Ihf· m/dpolnt of the evaJUItfon perIOd. 

IV. 

lJALUATJON CBlTiBlA AND WI!!CIHT!NM 

NASA will use the 1oI~ lubj8Clhle fIIcIors II a basis for arriving 411111 Inte~1II and final ,ward fee 

score: 

B. PnIgI .., ...... gement (20%) 

ThIs factor will Include an IVIIuation 0I1hI Contractor'8 perfolmlnOl In .., ...... 01 Program 

Management performanoe. both ~ end final. This Inciudel fdledule rnanaoement. 8ubcontraot 

AttachmentI-7 

PageS of8

~~~==~~~~~L_ ______________________ 

~~~~~~ 

Attachment 1·7 

management.1'lISflOI1IIIve88l, Innovation, life cycle coat management, and corporate commitment to 

capital illveslmentl and pel'llOnnei. (COrporate commitment to pellOl1nellnoludea tht quantity and 

quality of pet8OI'II1eI _",eel 10 the eEV Phaae 2 contracl QuantIty Includea rampoup and retention of 

qualified PlIIOI1I181 at adtqua1e I 

...... a to milt tchedule, coat and p8Ifonnance objllClivet. Quality of 

peI80IVIiI will be waluatad on the ContracIor's lU00M8 In maintainInG and repillOlng key ptllOlll1ei 

wI1hln the CEV PtIaM 2 contract.) 

Co COIIIllnIglIlMlflt (2ft) 

1'1111 faQIar wlllrioIudt an Muallon of the Contrsotor'l cost p8I'forINnce uncItr tht conttaGt. eamad 

Valua Manqerntnt 8yttem -. ooat performanot reporIIlI'Id other cost data sources will be uead In 

lilt COlt Managtmtnt IIi88Imant fOr til,. factor. COlt performance will be UI88ItCI by M1ua\lng the 

cost expendld on thtlClual wortc perlormld during tht perIOd btlng M1uat8d, Including quantitative 

..-amant of tht awaR! lie perfod cumulative COlt PIIIfoImlnoe Indtx COPl). In addition, a 

qualllltlll8 ......mam of app;opriate Mrneel value VlrIanctI. COlt Impllciallons or the SChedule 

Petformar'lce IndeX (SPI), and Other pertod"*PllDlflc cost management tnInd data will be considered. 

D. 8mI.~ID~luIlnlll.~Goa"(1"') 

The OontrICIOI'I ptIfonnance wli be lVlluatad againlt the CO/dIIICt goaJe for small/8mall 

dlasdvanlaald bUlln ... IUbCOntII.ctItIg. 

v. 'goBlNg 

The ptlWlliI" oJ IWt!'d _10 be pilei tot.pei'IOd Ie equat to the numerlaal80cn IIIIptd. In 

accoi'dlnce wIIfI the s.ctton G cIau8I for aW8ld IN, no awald fee will be paJd when ConfracIIlt 

perfolll1llllOl Is det8nn1ned 10 be PoorlUnlltllflCtoty. 

An overaY performance 8Vlluatlon and fee dlt8lmlnatfon or zenl eI1all be made for any -watlon pertod 

whIn there Is a mljor breach of 8Ifety or I80Urity ea dtftned In NFS 1".223-75. MIjor BIMCh of safety 

or Security. 

VI. U8T Of INCLQIUAEI 

EncIoIIurel: NwnerlCal Ranges and Adjectlvt Deflnillonl 

I!:ncIoaurw II: PIIfcJrrname Mlleatonee 

Modification ~"'I.!....:= .----~.] 


Pap6of8

AttacbmentJ·7 

L.,.;;;.;;.;;.;.;..;;.;.;£==;...;,.;;=~=~ ____________--,Mc.;;Od,,-=ifi;.;.;c.;.;;aao;.;.;· ""R-A.:-J ([D!!!~~_.~.~-_._-_-~-'-:I] 

EnClOaurel 

NumlflOli Ran .... II'Id AcI)eot1vt DIIInltlon. 

This encI08U18 sell forth the adjtCIMI ratings, dtflnl1lont, and I8IOCIattd nurntriotl rangae to be used to 

dellne the VlriouI IIVIII 01 ptIIotmll'a under the contJact. 

AOJEOTlVE RATING 

Excellent 

Very(3OOCl 

RANOEOF 

POINTS 

100·91 

90·81 

DESCRIPTION 

orelfCIPIIOnII mertt; extmplary 

perfolR1ll'a In • timely, effIcIent.nd 

economlcaI manner, vary minor (If any) 

d8llcltnc*i with no adveIu elf8CI on 

overall pt\'fOIrnaI1CI. 

80·71 

70·61 

iPQOriu-niiiiietacto--;y--- •--rao-.-o------neo.=-not.:=m:::c 

.. 

M .... or IIId111v &XC\I8dI minimum 

~-ii8iicfard.l adtqua18 reeUla; 

rtpOIIatlIt dtftclenolal with IdtntHlablt, 

bill not 8Ubttlntial, efI8CIt 01'1 overall 

perIonnance. 

=mI:;::nIm=um=aoceptib/==r.:-.-- 

IIIIIndaIdIIn one or mort a,..; remedial 

IlGIlon required In one ot mont ....; 

~ .. In~.~.~ .... whlch 

adVIl1HIIV affect QWqJf I 

.' 

Attacbmentl·7 

Pap7of8


~~~~==~~==~~~ ____________________________ ~M=od~i~fi~ca=tro~n~-J ~~_13 __________ ~] 

Enclosure II 

Performance MillSton .. 

Performance Mlleetones will be established prior to contract award. Theae mlleetonee wYI be used u 

measurements of performance In accordance with Ih. Award Fee for End Item Contractl. 

AWARD FEE Dl8TAIBunON 

I .. tone EvaluatIOn PerIod I AVIUlblaF .. 

Schedule 

.--- A TP to 8131107 

rr. 

7. 911107 to 7131108 

rr. 811108 to 6130109 

f-r. 711109 to 5131/10 

611/10 to 2126111 

fs. 

Ie: 

!t\ 

311/11 to 212Q112 

~ 

$ 

$ 

,- 

S 

r - 

$ 

S 

--. 

ElmedF .. 

- - 

I-r, 311112 to 2128113 

T" JIIIIJ. mZ{JllJ.l13 

-- ......... - 

S . - 

s 

--- 

-. 

. - 

- 


Page 8of8

NNI06TA25C 

I Crew Exploration Vehicle - (CEV) 



ArrACHMENT J-11 

GOVERNMENT FURNISHED PROPERTY UST

AMENDMENT OF SOLICITATIONIMODIFICATION OF CONTRACT 

2. 


Attn: Bradley J. Niese, Mail Code BT 



Lockheed Martin Corporation 

Attn: Bethany Lane 

P.O. Box 179 Mail Stop W3004 

Denver, Colorado 80201-0719 

_ 

The above numberecllOlldtatlOn Is amended II set rortIIln Item 14. The hOur end dale Ipec:Ifted for receipt of Orrtta Is ex1ended. 

Oft'ara muat ackmwIedge receipt of this _ment PrIor to the hour and dale IllilCllfIlll In the a:aIIcitaUon or as amended. bY one

NNJ06TAlSC 

Modifieation 29 

Page 2 of8 

(I) 

Definitization of Contract Change Order (CCO) 17 affects Schedule A of this contract as follows: 

(a) Clause B.3 Estimated Cost and Award Fee (NFS 1852.216-85) (SEP 1993) for C~mpletion 

Form Work is increased, based on the mutually agreed to negotiated price of! b'f I as 

follows: 

Estimated Maximum Total Cost 

Cost Award Fee and Award Fee 

. - -r--- 

~ ~ 

Previous 

1 

1---- I-- 

This Modification 

~ bl{ 

Iff 

I 

New Total ~I 

$4,392;682:5331 

(b) Contract Schedule A, Section B, Clause B.3 entitled "ESTIMATED COST AND A WARD 

FEE (NFS 1852.216-85) (SEP 1993)" is revised as set forth below. 

"B.3 ESTIMATED COST AND AWARD FEE



Page30fS 

here identifies the current authorized work. The maximum potentiallDIQ contract value is 

identified in Clause 1.7 ORDER LIMITATIONS. 

(End of clause)" 

(c) Contract Attachment 1-1 entitled "Statement of Work - Schedule A" is revised as set forth 

below. Only changes (additions, deletions and revisions) to this con~ attachment are 

contained herein. 

(i) The following is added to paragraph 0) of Section 2.3(C): 

1.3.(C) SPACECRAFT INTEGRATION 

• ISS C3l Communications Adapter (ICCA) 

(ii) The following paragraph (p) is added to Section 2.3(C): 

2.3.(C) SPACECRAFr INTEGRATION 

p) The Cotrttactor shall develop and maintain the ISS Resident RF equipment to ICCA 

Interface Control Document in accordance with ORO CEV -T -029 Interface Control 

Documents. 

(iii) The following paragraph (t) is added to Section 2.6.1 : 

2.6.1 AVIONICS INTEGRATION 

t) The Contractor shall lead the integration of the integrated resident RF communications 

hardware and the OFE provided ISS eJJ Communications Adapter (ICCA), with the ISS. 

(iv) The following paragraph (c) is added to Section 2.6.2: 

2.6.2 COMMAND AND DATA HANDLING (C&DH) INTEGRATION 

(c) The contractor shall participate with NASA in the integration ofCEV hard-line 

interface to the OPE ICCA onboard ISS. 

(v) The following replaces the first paragraphJn Section 2.6.3: 

2.6.3 COMMUNICATIONS AND TRACKING 

The Contractor shall integrate the DDT &E efforts of the space-to-ground and space-tospace 

communication links, RF/optical tracking devices (excluding navigational aids), 

and audio and video/imagery equipment, ihcluding hardware to be installed on the ISS. 

(vi) The following paragraphs (f), (g), and (h) are added to Section 2.6.3: 

2.6.3 COMMUNICATIONS AND tRACKING 

t) The Contractor shall design, develop. produce, integrate, verifY. validate, certifY, 

operate, maintain. document, and deliver ISS resident RF communications hardware 

(antenna, amplifiers, transponders, baseband processing. and other associated hardware). 

g) The Contractor shall integrate the resident RF communications hardware with the 

OFE proVided ISS C3I Communications Adapter (ICCA). 

h) The CEV Contractor shall participate with NASA and the Constellation Program in 

development of Radio Frequency (RF) spectrum management in compliance with the 

National Telecommunications and Information Administration (NTIA) Manual of 

Regulations & Procedures for Federal Radio Frequency Management (May 2003 Edition. 

May 2005 Revisions), Chapter 10. The Contractor shall provide RF spectrum 

management documentation in DR» CEV-T -026, Spectrum Management Docwnenls for 

the ISS CCA which is separate from the CEV stage 1,2 and 3 application.


ModifieatioD 29 

Page40fS 

(vii) The following paragraph (k) is added to Section 2.6.9: 

2.6.9 Structures Integratiou 

k) The ISS CCA will be hard mounted on a contractor provided isolation system for 

launch on Progress. 

(viii) The following paragraphs (h), (i) and (j) are added to Section 2.6.11: 

2.6.11 SuitltEVA and Survival Crew Equipment Support Systems Integration 

h) The ISS CCA primary assembly and the remotely located antennas will be mounted on 

the exterior of the ISS. 

i) The ISS CCA mOUDting design wi1l be passive. 

j) NASA provided 'brackets' will include any retention mechanism and latchinglbolting 

mechanism to secure the CCA to the ISS. 

(ix) The following paragraphs (b), (e) and (d) are added to Section 6.1.33: 

6.1.3.3 CM CommunieatioDS and Tracking 

b) The contractor shall provide the CEV to ISS CCA hardware and documentation 

necessary for CEV docking to ISS. 

c) The Contractor shall work with NASA on the integration of the CEV to ISS CCA 

hardware into the ISS. 

d) Any NASA provided components will be designed for environments consistent with 

ISS and Progress. 

(x) The following paragraph (h) is added to Section 6.1.3.6: 

6.1.3.6 CM Mechanisms 

h) The ISS CCA OSR's will be mounted such that they have a clear view to deep space. 

(xi) The following paragraphs (1) and (m) are added to Section 6.1.6.1: 

6.1.6.1 CM Fligbt Hardware AI&P 

1) The Contractor shall integrate, assemble, certify, acceptance test, and deliver flight 

hardware, for installation to the ISS meeting the requirements of CBV and the 

environments/requirements of ISS in accordance with the CEV to ISS IRD. 

m) ISS CCA qualification and acceptance testing will be conducted at the assembly level. 

(d) Contract Attachment J-3 entitled "Applicable, Guidance, and Informational Documents List" is 

revised as set forth below. Only changes (additions, deletions and revisions) to this contract 

attachment are contained herein. 

(i) All documents listed below are to be added as Applicable: 

I) CXP-70031 Revision A 

15 February 2008 

International Space Station (ISS) to CEV IRD 

(ONLY APPLICABLE FOR EFFORTS ASSOCIATED SPECIFICALLY WITH 

THE ISS COMMON COMMUNICATION ADAPTER) 

2) 1132928-103 

Revised 10/071200] 

International Space Station Program 

REQUIREMENTS FOR INTERNATIONAL PARTNBR CARGOES 

TRANSPORTED ON RUSSIAN PROGRESS AND SOYUZ VEHICLES 


THE ISS COMMON COMMUNICATION ADAPTER)



PageS ofS 

3) ClCP 70036A (rev A) with Errata (CEQATR) 


THE S-BAND TRANSPONDERS) 

4) SSP-SOOOS International Space Station Flight Crew Integration Standard 


THE ISS COMMON COMMUNICATION ADAPTER) 

(e) Contract Attachment J-7 entitled "Award Fee Evaluation Plan Crew Exploration Vehicle 

Contract NNJ06T A2SC Schedule A" is revised as set forth below. Only changes (additions, 

deletions and revisions) to this contract attachment are contained herein. 

Enclosarell 

Performaaee Milestones 

Performance Milestones will be established prior to contract award. These milestones will be 

used as measurements of performance in accordance with the Award Fee for End Item 

Contracts. 

AWARD FEE DISTRIBUTION 

Available 

EvalaatioD Available Total 

Fee: IDIQ 

Period I Milestoae Period Fee: 

Available 

Delivery 

Schedule Milestones 

Fee 

Orden 

ATPto 

8/31107 

911/07 to 

7/31108 

811108 to 

6/30/09 , 

7/1109 to 

5/311\0 

Interim 

EamedFee 

- 

...... .. - .. 

~ 

611110 to 

2128111 

0 'v>~ ~ \-J~ 

, 

3/1111 to 

2/29/12 

311112 to 

2/28113 

~ 

.. 

- 

~- 

311113 to 

10/31113 

£ ............ 

, 

. -

NNJ06TAl5C 

Modifi~atioD 29 

Page 6 ofS 

(f) Contract Attachment J-8 entitled "Subcontracting Plan for Small Business Concerns" is revised 

as set forth below. Only changes (additions, deletions and revisions) to this contract attachment 

are contained herein. 

Table A-ScheduJe A is deleted in its entirety 

. r,' 

". • 

SclfeduJe A SumnrtII'Y is revised as set forth below. 

Contract VRlue' S 4. 413916803 

Total Dollar 

Schedule A SUIIfIIfIUY I % Total I 

% Total Contract 

Value Subcontract DoDan Value 

Total SB 

WOSBTotal 

SDBTotai 

SDVTotai 

)JX 

b~ ~ 

- 

VOSBTotai 

HUBZone 

HBCUIMI 

LaraeTotai 

- 

- 

Total Subcontracts 

I 

(g) Contract Attachment J-9 entitled "Deliverable Items List" is revised as set forth below. Only 

changes (additions, deletions and revisions) to this contract attachment are contained herein. 

(i) Add new section entitled "ISS COMMON COMMUNICATION ADAPTER (CCA) 

HARDWARE" after the HARDWARE section and prior to the ELECTRICAL 

GROUND SUPPORT EQUIPMENT (EGSE) section of the Deliverable Items list as 

follows: 

ISS COMMON COMMUNICATION ADAPTER (CCA) HARDWARE 

2 ea - Shipse"* of ISS CCA Emulaton ** 

1 ea - Shipset* of ISS CCA Engineeriug Vuit** 

1 ea - Shlpset* orISS CCA Qualification Unit 

1 ea - Shipset* of ISS CCA ISIL Vult 

1 ea - Sbipset* of ISS CCA DSIL Unit 

2 ea - Ship .. "* ofISS CCA FUght Uni .. 

1 ea - Shlpset* of ISS CCA Flight Uuit (Spare) 

1 ea - ISS Unique GSE Test Cart 

Hardware will be delivered to NASA via 00250 

Scheduled DeUvery Date 

11912009 

61112009 

41112010 

1/lI2011 

11112012 

41112011 

41112011 

101312009 

·A shipset consists of the following: I each Baseband Processor, S-band Transponder, 

Diplexer, High Power Amplifier (HPA), Low Noise Amplifier (LNA), I Antenna switch 

assembly, 3 low gain antennas. 120 Volt to 28 Volt Power Converter, cold plate, thermal 

protection Blankets and connective cabling exclusive of the RF connective cable between 

the antennas and the end item deliverables 

··There is no acceptance test for the Test Units - functional checkout is completion 

criteria for DD2S0


Modifi~ation 29 

Page 7 ofs 

(h) Contract Attachment J-II entitled "Government Furnished Property List" is revised as set forth 

below. Only changes (additions, deletions and revisions) to this contract attachment are 

contained herein. 

(i) Add new item to Section 2.0 GovernmeDt Provided Property List as follows: 

, . 

, 

GoverDmeDt-Provided Property SOW RefereDu Due Date 

-- 

~L1 

/3lf • 

. . 

B,/ 

- - '" 

ion 

..... 

B'I . . " 

B'i 

I~ 'f" 

" . 

I- - 

IYf 

(Sf( 

) I /YI 

I 

I --::-- 

I 

- 

(i) Contract Attachment J-12 entitled "List of Government Facilities" is revised as set forth below. 

Only changes (additions, deletions and revisions) to this contract attachment are contained 

herein. 

(i) Add new items and durations to List of Government Facilities:



Page 8 of8 

1 

( 

) 

0) In consideration of the modification agreed to herein as complete equitable adjustment for all 

claims arising out of or attributable to the issuancc of the contract changes andlor contractor 

proposals listed below, the contractor hereby releases the Government from any liability under 

this contract for further equitable adjustment attributable to such facts or circumstanccs giving 

rise to said contract changes andlor contractor proposals, and for such additional obligations as 

may be required by this modification. 

Contract Change: 

Contractor Proposal: 

Contract Change Order 17, dated August 14, 2007, and all 

updates provided thereto 

Firm proposal NS0029, dated November 8, 2007, and all updates 

provided thereto 

(2) Contract Attachment J-16, "Integrated Project Schedule" is revised to update Table J-16-1, ''CEV 

Project Schedule A Milestones" PA-I Test Flight Launch Date from 9/23/08 to 12111108. 

(3) All other terms and conditions of the contract remain unchanged and in full force and effect.

OMB Approval.: 2700-0042 

1. CONTRACT 10 CODE 

PAGE OF rGES 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT NNJ06TA2SC I 1 7 

2. AMENDMeNTIMODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITIONIPURCHASE REQ NO. J 5. PROJECT NO. (II app/IceIII&) 

65 MAY 282009 N/A N/A 

8. ISSUED BY CODE 7. ADMINISTERED B "t.mdJ 

BT 1 JPI CODE l 


~:PROVED 

.~... 

Attn: Bradley 1. Niese, Mail Code BT 

-'1"'1.......r. 

2101 NASA Parkway JSC P~Q~UREMENT 


~:J..0FFICER 

$: L.:2 I". 

8. NAME AND ADDRESS OF CONTRACTOR (NO.. lInN( county. SII,., anti z;, Code) 

.J&. IIA. 

Ll 'AlE 

Lockheed Martin Corporation 9B. DATED (SEE ITEM 11) 

Attn: Linda Dozier 

2625 Bay Area Blvd lOA. MODIF1CATION OF CONTRACTIORDER NO. 



X 

108. DATED (SECE ITEM1IfC) 

CODE 100141 I FACIUTY CODE 04236 09/0812006 

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS 

g. The aboVe numtitnId IOI/CItatIoIIIt amended II aet forIh In IfIIm 1.. The hour lind CIIIt 8p1C1t!ed.1or ~ or ~ _ g _ It extended, g _ 

Is nat.xtllnded. 

Oft'eq must of this ameolClment to the hour and dalupecHlId In tllualldtatlOn or. _ . one of the meIIIads! 

(a) By campIeIfng HernIa and IS. and leIIIm~ aapIea of the amend(ntnt; (b) By acIcnawI8dglng raceIpt 01 tIIlt ~nt an tIICh 0IJf1I or the affer aubmltllld; CIt (e) 8y 

aepetate IeIIet or_,.,.. WIII\:h In\lIllC'." to thIi IOIIc/t.IIon and arI1enCIrnirit numbels. FAIWRE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE 

PlACE oeSIGNATEO FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue or this 

amandment ycu deIIre to cIIanoe an aItet alreedy eubmltlld. eucII cllange may be mede by"""", or letter, plOvfded aacII telegram CIt IeIIar __..-.-to the 

.. nent. and Is ~ p!Ior to the opening hour and dale !l!IC!fted. 

8CII!c!!atIon lind this _ 

12. ACCOUNTlNGANDAPPROPRIATION DATA (lIf8qU/18d) 

N/A 

13. THIS ITEM APPLIES ONLY TO MOOIFICAnONS OF CONTRACTS/ORDERS, 

IN 

&. IMPORT,\NT: Contractor Olano!, ~ " required to sign !hili doc:urnent and retum.....J..... copies to the issuing oIfIce. 

14. DESCRIPTION OF AMeNDMENTiMODlFlCATION ~ by UCF HCtIott heetItntA IIrr:Iudlng ecIIt:ItiIfIonI subJ«;t /IIIIIfeI' w/Ier8 fHsIbIe.) 

The purpose of this modification is to defmitize Contract Change Order (CCO) 24, dated November 30, 2007. 

For a detailed description of the changes, see pages 2 -1.



Definitization of Contract Change Order (CCO) 24 affects Schedule A of this contract as 

follows: 

Page 2 of7 

(1) Based on the mutuaOy agreed upon negotiated price of 51,901,000,000 for this action, 

contraet value for Schedule A Completion Form Work is equitably adjusted as follows: 

Previous 

li'dimsat"d Cnd I Award Fee I Total I 

This Modification 

b.t. ~'k bl-f 

New Total I I $6,293,682,5331 

(2) Contract Schedule A, Section B, Clause 8.3 entitled "ESTIMATED COST AND 

A WARD FEE (NFS 1852.216-85) (SEP 1993)" is revised as set forth below: 

"8.3 ESTIMATED COST AND A WARD FEE tNFS 1852.216-85) (SEP 1993) 

The estimated cost and award fee for Schedule A (base foe not applicable) of this contract is 

broken out as follows: 

Completion Form Work'" 

IDIQ Delivery Orders" 

- 

Delivery Estimate Maximum Total Cost 

Order Number Cost Award Fee and Award Fee 

----- 

Not Applicable 

$6,293,682,533 

-I- 

-I- 

NNJ07TA26T 

-I- 

NNJ07TA27T 

-I- 

NNJ07TA28T 

-I- 

NNJ07fA29T 

~~ 

NNJ07TA30T 

:-- 

NNJ07TA3IT 

-- 

I 

NNJ07TA32T 'o~ -- 

NNJ07TA33T 

-- 

I 

NNJ07TA34T 

-- 

NNJ07TA35T 

I 

-- 

NNJ08TA15T 

-I- 

'tJt 

-- 

NNJ08TA16T 

-I- 

NNJ08TA17T 

-- 

NNJ08TA18T 

I 

-I- 

NNJ08TA19T :.. I- 

NNJ08TA20T 

I 

-I- 

NNJ08TA21T : 

-I- 

NNJ09TAOlT 

, 

-f-- 

NNJ09TA02T ... a._ ....... 

.-. 

loll{ 

--

NN.J06TA25C 


Pagc40f7 

(b) 

(c) (1) Base fee, if applicable, will be paid in quarterly lI1stallments based on the percent of 

completion of the work as determined by the Contracting Officer. 

(2) 

(3)

NN.T06TA25C 


PageS of7 

(4) All interim (mld provisional, ifapplieablc) fcc payments wIll be superseded by the fee 

determination made in tho final award fee evaluation. The Government will then pay the 

Contractor, or the Contractor will refund to the Government the difference between the final 

award fee determination and the cumulative interim (and provisional, if applicable) fee 

payments. lfthe final award fee evaluation is "poor/ullsatIsfactory", any base fee paid will bc 

refunded to the Government. 

(5) Payment of base fee, if applicable, will be made based on submIssion of an invoice by 

the Contractor. Payment of award fee will be made by NASA Accounts Payable based on an 

issuance of a unilateral modification by the Contracting Otlicer. 

(d) Award fcc determinations are unilateral decisions made solely at the discretion of the 

Government. 

(End of clause)" 

(5) Contract Schedule A, Clause G.11 entitled "LIST OF INSTALLATION· 

ACCOUNTABLE PROPERTY AND SERVICES (NI

NN.J06T A25C 


Page 6 of7 

(7) Contract Schedule A, Scction n, Clause H.28 cntitled "ORION REQUIREMENTS 

TAILORING" il; added to the contract as follows: 

"H.2S ORION REQUIREMENTS TAILORIN(; 

(End of Clause)" 

(8) The folJowin/! contract J-Attachmcnts are delcted in thcir entircty and replaced with 

the updated attal!hments included with this modification: 

Title 

Stat-em-cnt of W(;rk - ._- 

-------- 

- .. ._._--'--- - ----- 

Data Procurement Document (DPJ») & 

DRD Submission Matrix 

--- 

Applicable, Guidance and Inlormation 

Documents List 

------~.~~ ...... --- .- 

~~. _._ . Gloss~~ ______ _ 

J-7 Award Fee Plan 

... J-8 _.___ Subc~£ting Plan fo~_Small Rusi_!.lE~~ 

-- ------ - - ------.--~-- 

J-9 Deliverables Items List 

J- t 0 List of Installation Accountable Property 

.---...~ 

1nd Services 

-.'- .. --.-~-..-~. ---. 

Qovernmef!.~ Furnished Pr~2£rt.l. (GF~) __ . 

Government Facilities 

l-----''---- --- ---•. - ._- 

L....-._J_-_16_ .•..• _ [ntegrated J)!()ject Sc~c::2:.u,,-le,--__ 

(9) The following new .J-Attachmcnt is hereby addcd to thc contract and included as an 

attachment to this moditication:

NNJ06T A25C Page 7 of 7 


Attachment Title 

J-26 Orion Tailored Re uirements List 

(10) Contract Schedule A, Table of Contents, is hereby updated to incorporate the addition 

of Section H, Clause H.28 entitled "ORION REQmREMENTS TAILORING." 

(11) Contractor Release Statement 

In consideration ofthe modification agreed to herein as complete equitable adjustment for all 

claims arising out of or attributable to the issuance of the contract changes and/or contractor 

proposals listed below, the contractor hereby releases the Government from any liability under 

this contract for further equitable adjustment attributable to such facts or circumstances giving 

rise to said contract changes and/or contractor proposals, and for such additional obligations as 

may be required by this modification. 

Contract Change: 

Contract Change Order 24, dated November 30, 2007, and all 

updates provided thereto 

Contractor Proposal: Proposal NS0034, dated November 14, 2008, and all updates provided 

thereto


Crew Exploration Vehicle - (CEV) 

Attachment J-1 



STATEMENT OF WORK 

May 2009 

Page 1 of119





INTRODUCTION 

The Crew Exploration Vehicle (CEV) IS the spacecraft that NASA plans to use to send human and 

cargo items into space and to return them to earth The CEV is an element of the overall 

Constellation Program that Includes launch vehicles, spacecraft, and ground systems needed to 

embark on a robust space exploration program This space exploration program will advance the 

Nation's scientifiC, security, and economic Interests. 

Scope 

The Contractor shall develop and certify the CEV System to meet the International Space Station 

(ISS) mission requirements. The Contractor shall develop and deliver a lunar block change plan 

that shows extensibility of the CEV System design to meet lunar sortie and lunar outpost mission 

requirements The lunar block change plan Will Identify those system deSign Items that have a 

development deferral to a future contract action. DUring lunar miSSions, the CEV IS used to carry 

the crew to low earth orbit (LEO) for rendezvous with other elements for the lunar missions and 

also serve as the return-to-earth vehicle for the crew. The Contractor will modify and certify the 

ISS CEV design as required to support lunar mission reqUirements The Contractor shall deliver 

the CEV spacecraft configurations below per requirements In the CXP-72000, System 

Requirements for the Crew Exploration Vehicle Element (CEV SRD) 

The following more clearly defines the different configuration variants of the CEV Spacecraft: 

1. Block 1A is a crewed, pressurized cargo vehicle for Low Earth Orbit (LEO) (including ISS crew 

change out) missions. This configuration includes. 

• A habitable Crew Module (CM) 

• A Service Module (SM) which also Includes the Spacecraft Adapter (SA) which Interfaces 

with the Crew Launch Vehicle (CLV) 

• A Launch Abort System (LAS) to provide a method for crew abort 

2Block 2 is a crewed, pressurized cargo vehicle for lunar missions It uses a habitable CM, LAS, 

SM, and SA to support lunar missions. 

CxP-70072-ANX 01, Constellation Systems Management Systems Plan, Annex 01. Common 

Glossary and Acronyms provides a detailed listing of terms used in this Statement of Work. 

CEV Implementation Strategy 

The CEV Implementation strategy reqUIres a detailed Implementation schedule to deSign the 

spacecraft, and implement, certify, and deliver It. NASA will work closely with the Contractor to 

develop the details of an Implementation strategy that maintainS the highest standards for safety, 

reliability, and mission assurance. Ways that NASA will work closely with the Contractor include 

the following. NASA will participate in daily management and deSign meetings and deCISions, 

NASA will work with the Contractor on the shop floor dUring development, NASA Will partiCipate In 

the Contractor Material Review Board (MRB) process, as described In CXP 70059-SR&QA 

ReqUirements, In order to help prevent stop-work conditions, and NASA will work with the 

Contractor In the test faCilities dUring integration and test activIties. The purpose of the level of 

participation IS for access to NASA for timely deciSions. 

NASA Will proVide the detailed oversight of all spacecraft deSign activities. However, the 

Contractor will retain responsibility for delivery of a design that meets the requirements The 

detailed process discussion to accomplish this can be found in CxP-72008, Crew Exploration 

Vehicle Project Plan. Some areas of spacecraft design will be provided by NASA and NASA will 

perform independent activities for requirements validation and design certification in other areas. 

In these areas NASA will establish design requirements teams to integrate the activities of NASA 

Page20f119





and the Contractor The Contractor will participate in and support these design requirements 

teams. NASA has responsibility for all GFE provided equipment. 

The Contractor will deliver a design that ensures simplicity, minimizes life cycle cost and 

addresses all aspects of human spacecraft development, production, certification and operations 

The Contractor will design, develop, certify, and deliver the hardware required to achieve ISS 

miSSion requirements In Schedule A. The Contractor shall develop a lunar block change plan that 

shows extensibility of the CEV System design to meet lunar sortie and lunar outpost mission 

requirements. The lunar block change plan will identify those system design items that have a 

development deferral to a future contract action The concept is to develop a "common" design 

for the spacecraft variants, where the vehicle can be utilized for both Lunar and ISS 

requirements. The common design and life cycle approaches will lead to an effective 

implementation of subsystem and spacecraft deliveries. 

The Contractor is expected to develop and verify ISS mission software during Schedule A, With 

lunar mission software being developed In future contract action With other lunar block upgrades 

However, lunar mission software requirements must be evaluated to ensure the command and 

data handling hardware can accommodate the additional software required for lunar missions, as 

well as other mission objectives The "common" vehicle design shall be configured to 

accommodate integrating the future lunar block upgrades to achieve the lunar mission objectives 

while remaining Within the vehicle requirements contstraints. 

NASA will perform the CEV ground, flight, and training operations; design and develop CEV 

ground operations facilities, faCIlity systems, and NASA-provided ground support equipment 

(GSE); and prOVide high-fidelity simulators and trainers. Further, NASA Will conduct flight testing 

to demonstrate vehicle performance characteristics NASA will lead a JOint NASA and Contractor 

Combined Test Team (CTT) that consists of representatives from all partiCipating test 

organizations. In support of the NASA operations, risk reduction flight testing, and safety and 

mission assurance activities, the Contractor must provide the necessary data products and 

expertise as detailed in the SOW. 

NASA Will use the technical Data Requirements Documents (DRDs) to sustain and operate the 

CEV over the life of the Project It IS NASA's intent to use the technical DRDs to document the 

CEV requirements, design, and certification activities 

Contract Structure 

To help differentiate the type of activities that comprise the Phase 2 contract, NASA has 

developed multiple "schedules." These include: 

1 Schedule A (DDT&E). This includes all design, development, test and evaluation activities to 

certify variants 1 A and 1 B as well as the production activities for the first actual flight module of 

the 1A variant, along With other deliverables deSCribed In thiS SOW. Schedule A Incorporates 

completion form and Indefinite delivery, indefinite quantity (IDIO) paragraphs All paragraphs are 

completion form unless speCifically marked as "IDIO." 

2 Schedule B (Production). This Includes production of all block variants 

3 Schedule C (Sustaining Engineering) This includes any new DDT&E effort required beyond 

the scope of Schedule A, such as the Block 2 variant 

This statement of work applies to Schedule A only. DeSCriptions of other contract schedules are 

provided for reference only. 

Page 3 of 119





f 

PROJECTMANAGEMENT 

The Contractor shall develop, implement and maintain a set of common project management 

processes, systems and data deliverables to be utilized for all contract schedules (A, B and C) 

throughout the life of the contract. 

1.1 Project Management and Administration 

An anchoring capability of the Constellation Program is a human-rated CEV that will carry human 

crews from Earth into space and back again Coupled with transfer stages, landing vehicles, and 

surface exploration systems, the CEV will serve as an essential component of the architecture 

that supports human voyages to ISS, the Moon, and beyond. 

a) The Contractor shall design, develop, certify, and deliver the hardware and software reqUired 

to achieve the LEO and ISS mission requirements The Contractor shall develop a lunar 

block change plan that shows extensibility of the CEV System design to meet lunar sortie and 

lunar outpost mission requirements The lunar block change plan will Identify those system 

design items that have a development deferral to a future contract action. 

b) The Contractor should minimize life cycle cost In the design, development, certification, and 

delivery of the hardware and software required to achieve the LEO and ISS mission 

reqUIrements In accordance With paragraph 1.1 a 

c) The Contractor shall ensure crew/ground safety while meeting system performance 

requirements and achieving mission objectives 

d) The Contractor shall design the CEV System to accommodate all the design reference 

missions defined in CXP-70007, Constellation Design Reference Missions (DRM) 

e) The Contractor shall design the CEV System to the requirements and terms speCified In 

CXP-72000, System Requirements for the Crew Exploration Vehicle Element (CEV SRD). 

f) The Contractor shall implement designs for the CEV spacecraft and ground systems to 

achieve efficient and effective operations 

g) The Contractor shall perform to the negotiated cost, schedule, and technical baseline. 

h) Reserved 

I) The Contractor should maximize the use of eXisting technology in the design of the CEV, 

unless new technology is reqUired to meet NASA requirements. 

j) The Contractor shall base the vehicle design on an open system architecture 

k) The Contractor should qualify components, subsystems, modules, and systems by test, to 

the maximum extent possible. 

I) The Contractor shall provide a CEV System that shall have a lifecycle that ends no less than 

20 years after the first human flight 

M) Contractor shall develop and document a lunar block change plan that shows extenSibility of 

the CEV System design to meet lunar sortie and lunar outpost mission requirements in 

accordance with ORO CEV-M-006 Lunar Block Upgrade Plan. The plan will identify those 

system design Items that have a development deferral to a future contract action The Lunar 

Block Upgrade plans hall be presented at each major design review. The Lunar Block 

Upgrade activities to be conducted In a future contract action include. 

• Lunar Software (Non C 3 1) 

• Lunar C 3 1 Software 

• LSAM Power Transfer Unit 

• Phase Change Matenal 

• M-5 Parachute Matenal Change 

• Ultra Thin Solar Array Cells 

• Structures Optimization 

• Avionics Technology Insertion 

• Lithium Polymer Battenes 

• Lunar Navigation Targets 

• Harnessing 

Page 4 of 119





Deliverables 

The Contractor shall deliver and maintain the following document(s). 

• ORO CEV-M-006. Lunar Block Upgrade Plan 

1.1.a Project Management, Systems, Planning and Reporting 

a) The Contractor shall implement an organizational structure for the management, 

coordination, and control of contract activities including the project's cost, schedule, 

performance, risks, contracts, and subcontracts uSing as gUidance ISO 14300-1, Space 

Systems - Program Management - Part 1: Structuring of a Program The Contractor shall 

develop and implement a project management plan that covers all aspects of project 

management for the CEV Project in accordance with ORO CEV-M-001, CEV Prime Project 

Management Plan. The contractor shall incorporate the proposed Streamlining Plan in ORO 

CEV-M-001, Prime Project Management Plan 

Deliverables 

The Contractor shall deliver and maintain the following document(s)' 

• ORO CEV-M-001 : CEV Prime Project Management Plan 

1.1.b Performance Management Reviews and Performance 

Metrics 

a) The Contractor shall conduct quarterly Performance Management Reviews (PMRs) with the 

Crew Exploration Vehicle Project Office (CEVPO) In accordance with ORO CEV-M-002, 

Performance Assessment Plan, Reports and Management Reviews The reviews shall 

provide insight Into the Contractor's, subcontractors', and vendors' overall technical, 

schedule, and cost performance and status 

b) The Contractor shall define the metrics, to be approved by government, in accordance with 

the ORO CEV-M-002, Performance Assessment Plan, Reports and Management Reviews. 

The Contractor shall update the metrics and performance data monthly and make it available 

for NASA review In the Contractor's collaborative enVIronment and during working-level 

discussions. The Contractor shall present the metrics and performance data at the PMRs. 

c) The Contractor shall recommend the technical performance parameters, to be approved by 

NASA, In the Performance Assessment Plan. The Contractor shall status the technical 

performance parameters quarterly in their Performance Assessment Reports 

d) The Contractor shall report on each SOW and SRO "should" statement at the PMR until the 

"shoulds" are satisfactorily accomplished. 

Deliverables 


• ORO CEV-M-002 Performance Assessment Plan, Reports and Management Reviews 

1.1.c External Relationships 

1.1.c.1 

Associate Contractors 

a) When the working environment requires Interaction with other NASA contractors, the 

Contractor shall establish cooperative relationships with other NASA contractors, defined as 

associate contractor relationships Associate relationships are required for expeditious 

exchange of management and technical data among NASA contractors 

Page 5 of 119





1.1.c.2 

NASA Centers 

a} The Contractor shall establish cooperative relationships at the NASA centers to provide 

support (e g technical analyses, data, etc.) or understand NASA GFE and associated data 

deliverables (reference SOW paragraph 6.b), schedules, interfaces, and Interactions. The 

contractor shall work JOintly with NASA to establish contractor/NASA GFE integration teams. 

These relationships shall be documented in accordance with ORO CEV-M-001, CEV Prime 

Project Management Plan. 

b} The Contractor shall provide resident office space, Including phone, computer, and desk 

space, to accommodate NASA program office personnel. 

Deliverables 

The Contractor shall deliver and maintain the following document(s}' 

• DRD CEV-M-001 : CEV Prime Project Management Plan 

1.1.d Internal/External Project Review Support 

a} The Contractor shall develop briefing materials and analyses for CEV System meetings with 

various internal and external review groups Examples of these Internal and external groups 

include the flight technique panels, Aerospace Safety Advisory Panel (ASAP), Inspector 

General/Government Accountability Office (IG/GAO), and cost assessments teams. 

b} The Contractor shall prepare and present various topics, such as CEV Project technical, cost, 

and schedule status, speCifiC safety or risk Issues, design and development Issues, and 

responses to external inquiries, as directed by NASA 

1.1.e Security Management 

Security management includes management of information technology security, physical/facility 

security, personnel security, flight vehicle security and flight test article security. 

a} The contractor shall use the following standards and requirements documents for developing 

and executing all security management processes and products' 

CxP 70070-ANX05-01, CxP Program Management Plan Annex 5' Security Management Plan, 

Book 1 Information Technology Functional Security Requirements 

CxP 72008, CEV Project Plan, section 4.10 and associated children 

NASA will be responsible for encryption handling key management, storage, COMSEC custodial 

activities, and operational integration at KSC, CAlL and Plumbrook 

b} The following documents are prOVided for Informational purposes for the contractor to support 

development of all security management processes and products. 

CxP 70070-ANX05-Book2, Constellation Program Management Plan Annex 5. Security 

Management Plan, Book 2. Information Technology (IT) Security Architecture 

Page60f119





1.2 Business Management 

1.2. (a) Financial Management 

Financial Management provides summary-level cost reporting by fund source, Work Breakdown 

Structure (WBS), elements of cost and workforce Including labor equivalent personnel (EP), 

overhead, and other direct and indirect costs. 

1) The Contractor shall develop, deliver, and implement monthly financial management 

reporting in accordance with ORO CEV-B-001, Financial Management Report (NASA Form 

533) 

2) The Contractor shall provide project-wide data once a year to be used In NASA's budget 

planning process (e.g., program operating plan (POP) budget calls) The Contractor shall 

provide an annual Operating Plan (OP) update to that data for the upcoming fiscal year as 

requested by NASA. NASA will specify the format and content of the Contractor's inputs and 

rationale. 

3) Upon request by NASA, the Contractor shall provide project-wide budget data a maximum of 

three times per year. This data will be used for the purposes of gathering budget impacts for 

various re-plannlng scenarios NASA will specify the format and content of the Contractor's 

inputs and rationale. 

4) The Contractor shall provide property financial reports in accordance with ORO CEV-B-004, 

Property Financial Reporting 

5) The Contractor shall provide Rough Order of Magnitude (ROM) estimates as requested to 

support the NASA decision making process. ROM estimates shall be delivered to NASA 

within 7 days of the formal request unless the contractor notifies NASA within 2 days of 

request receipt that the ROM will requires more time due to effort reqUired to bound the 

scope, additional reviews required, or significant complexity. The contractor shall use best 

available estimating techniques given the groundrules and assumptions provided by NASA. 

Prior to delivery to NASA, ROM estimates will be reviewed by the contractor technical 

community 

Deliverables 

The Contractor shall deliver and maintain the follOWing document(s) 

• ORO CEV-B-001. Financial Management Report (533) 

• ORO CEV-B-004. Property Financial Reporting 

1.2.(b) 

Workforce Reporting 

Workforce Reporting provides workforce Information by geographic location 

1) The Contractor shall develop, deliver and implement workforce data in accordance with ORO 

CEV-B-002, Workforce Reporting 

Deliverables 


• ORO CEV-B-002' Workforce Reporting 

1.2. (c) Integrated Baseline Review (IBR) 

1) The Contractor shall perform an Integrated Baseline Review (lBR) with NASA to establish the 

contract baseline Subsequent baseline reviews Will be reqUired by NASA to update the 

performance measurement baseline when the contract has a significant restructure or 

change in cost phasing. The IBR shall include the following accomplishment criteria and 

subsequent baseline reviews should identify only changes. 

Page 7 of 119





o Project organization fully established with cost control accounts and 

organization members Identified, Including interfaces and interactions with 

NASA. Organization and teaming roles and responsibilities defined. 

o Organizational staffing plans in place 

o IMS review 

o Risk management system and process review 

o Metrics baselined 

o Earned value management system and process review 

2) The Contractor shall ensure the technical contents of work packages and control accounts 

are consistent With the scope of work defined in the W8S, SOW and SRO. 

3) The Contractor shall work jointly with NASA to develop and document an integrated 

performance measurement baseline This baseline consists of all contract work Including the 

integration of GFE 

4) NASA will proVide agreed-to specific GFE performance measurement baseline data. 

5) The Contractor shall proVide a logical, resource-loaded, integratedflnterdependent sequence 

(Le. predecessor/successor network) of tasks supporting the contract schedule. 

6) The Contractor shall demonstrate to NASA that metnc collection methods are in place to 

mOnitor agreed-to requirements of the contract. 

1.2.(d) 

Cost Performance Report 

The Cost Performance Report (CPR) will be used to provide information for' (1) Integrating cost 

and schedule performance data with technical performance measures, (2) assessing the 

magnitude and impact of actual and potential problem areas causing Significant cost and 

schedule variances, and (3) providing valid, timely status Information to the CEV Project. 

1) The Contractor shall establish, maintain, and use In the performance of this contract, an 

integrated earned value management system In accordance with ANSI/EIA-748-98, Earned 

Value Management Systems 

2) The Contractor Will perform earned value analysis and shall capture, maintain, and provide 

NASA access to the earned value analYSIS data The earned value analysis data, at both the 

cost account and overall proJect-level, shall be presented as part of the quarterly PMR. 

Reference ORO CEV-M-002, Performance Assessment Plan, Reports and Management 

Reviews In addition, the contractor shall proVide electronic access to the Contractor's 

weekly earned value data 

3) The Contractor shall develop, deliver and implement CPR data In accordance with ORO 

CEV-B-003, Cost Performance Report, and shall support informal working-level discussions 

on the content 

Deliverables 

The Contractor shall deliver and maintain the follOWing document(s). 

• ORO CEV-8-003' Cost Performance Report 

1.2.(e) 

Life Cycle Cost Management 

1) The Contractor shall capture, maintain, and prOVide access to life cycle cost analYSIS data in 

the NASA ICE as it evolves through the project life cycle Life cycle cost definitions to be 

used In the analYSIS are defined In Attachment J-5, AppendiX 1, Life Cycle Cost Analysis 

Life cycle cost analysis data for OOT&E and operability shall be generated and presented at 

each major deSign review (e.g. SOR, POR, CDR) and at each quarterly PMR. These 

presentations shall include the latest LCC estimate, as well as a detailed diSCUSSion of the 

Impact from the current design, design and operations changes since the last review, and the 

rationale for the changes. In addition, the contractor shall utilize an integrated management 

assessment tool to perform affordability analYSIS to support life cycle cost management 

Reference SOW paragraph 2.4 Integrated Analysis 

Page 8 of 119





1.2.(f) Contracts Management 

1) The Contract Management organization shall develop, reView, Interpret, negotiate, modify 

and administer the Project Orion contract Contracts Management is the primary point of contact 

with the Orion NASA Contracting Offlcer(s), the delegated Defense Contracting Management 

Agency (DCMA) and the delegated Defense Contract Audit Agency (DCAA) Contracts 

Management shall resolve and document contract Issues. Contracts Management shall ensure 

that Contract reqUirements are fully defined and implemented by the contractor team. 

1.3 Configuration Management and Data Management 

1.3.(a) Configuration Management 

1) The Contractor shall develop and implement Configuration Management (CM) processes and 

systems. 

o The Contractor CM process and system shall use MIL-HDBK-61A, MIlitary 

Handbook Configuration Management GUidance, as gUidance 

o The Contractor's CM process and system shall provide the following' (1) 

configuration identification, (2) configuration control, (3) configuration status 

accounting, and (4) configuration management verification and audits. 

o The Contractor CM plan shall define how the Software Configuration 

Management Plan (see ORO CEV-T-006) supports this CM process and 

system 

o 

The Contractor shall work with NASA to develop a configurallon management 

process that also integrates with the Constellation Program and complies with 

the CXP-02007, Constellation Nomenclature Plan. The Contractor CM process 

and system will be approved by NASA. 

2) The Contractor shall Integrate the CM system across all CEV project elements including 

modeling and simulation, engineering drawing development and release, manufacturing, test 

equipment and test articles, operations, and quality, as well as acquisition organizations 

including customer and vendor CM systems. 

3) The Contractor shall Implement and maintain a configuration status accounting system that 

provides information defining and maintaining the as-designed and as-built configuration of 

the system hardware and software and the status of changes to this configuration. 

Deliverables 

The Contractor shall deliver and maintain the following document(s) 

• ORO CEV-M-003. Configuration Management Plan and Reports 

1.3.(b) Data Management 

a) The Contractor shall develop and Implement Data Management (DM) processes and 

systems 

o The Contractor's DM process and system shall provide the following' (1) data 

identification, (2) data control, (3) data status accounting, and (4) data 

management verification and audits. 

o The Contractor shall work With NASA to develop a data management process 

that also Integrates With the Constellation Program The Contractor DM 

process and system will be approved by NASA. 

b) The Contractor shall Integrate the DM system across all CEV project elements such as 

modeling and simulation, engineering drawing development, manufacturing, test equipment 

and test articles, operations, and quality, as well as acquisition organizations including 

customer and vendor DM systems. 

Page90f119





De/iverables 


• DRD CEV-M-004 Data Management Plan 

1.4 Risk Management 

a) The Contractor shall Identify, evaluate, manage, and control the safety, technical, cost, and 

schedule-related risks associated with all aspects of the CEV Project in accordance with 

CXP-72091 Orion Integrated Risk Management Plan 

b) The Contractor shall provide substantiating data for each risk identified in accordance with 

ORO CEV-M-005, Risk Management Plan and Reports. 

c) The Contractor shall substantiate each identified risk In the form of historical information, and 

analysis. These analyses and Information may be Integrated with Probabilistic Risk 

Assessment (PRA) analysIs, as appropriately applied to high risk hardware/software 

development and operations Reference S&MA ORO CEV·S·010, Probabilistic Risk 

Assessment Results. 

d) The Contractor shall commUnicate and elevate multi-element and external interface risks to 

the CEV Project office for the purpose of multi-element risk Integration 

e) The Contractor shall perform integrated risk analysis, mitigation, tracking/control for the CEV 

Project office ThiS effort is for the purpose of communication of external Interface and multielement 

risk integration data for the Constellation-level risk management process 

f) The Contractor shall manage risks utilizing a risk management tool The Contractor shall 

integrate their risk management tool with ICE. 

De/iverables 


• ORO CEV·M·005 Risk Management Plan and Reports 

1.5 Information Technology Management 

For IT applications, other than mission-specific software, the Contractor shall. 

o Where cost effective to NASA, use Commercial-Off-The-Shelf (COTS) and 

eXisting Government Off-The-Shelf (GOTS) products. 

o Ensure compatibility with existing NASA applications and systems 

o Comply with NASA reqUIrements for NPR 7150 2, NASA Software Engineering 

ReqUirements for the appropriate software classes, limited to classes E, F, and 

G 

1.5.(a) 

NASA Integrated Collaborative Environment (ICE) 

The NASA Integrated Collaborative Environment (ICE) IS the primary means of sharing, reporting, 

collecting, recording, and accessing project Information between NASA, the CEV Contractor, 

subcontractors and authOrized Government personnel connected with the CEV Project ICE 

prOVides secure, real-time collaborative access to a Single source of management Information, 

product information, and technical data. ICE IS the prinCipal mechanism for Integrating a project's 

digital information management environment. 

1} The Contractor shall use ICE for delivery of all data. 

2) The Contractor shall use the Interactive collaborative configuration management and 

document management enVIronments of ICE for configuration management of CEV project 

directives and change control activities 

3) The Contractor shall comply With Attachment J-14, ICE Operating Environment. 

Page100f119





4) The Contractor shall implement the ICE Interface uSing one of the two options described in J- 

14, ICE Operating EnVIronment, Section II, Data Access Requirements. 

5) The Contractor's collaborative environment shall be available within 30 days of contract 

award 

6) The Contractor's collaborative environment shall be updated with the latest status Information 

based on the Contractor-determined Interval(s) and as approved by NASA. 

7) Non Deliverable Information such as week to week coordination, working level analysis, 

action Item responses, etc shall be transmitted via an LM established data sharing system 

(eg project link). 

1.6 Reserved 

1.7 Integrated Schedule Management 

1.7.(a) 

Integrated Master Plan (IMP) 

a) The Contractor shall develop and maintain an Integrated Master Plan (IMP), as Attachment J- 

15 of this contract, which delineates Schedule A, Band C activities. All changes to the IMP 

shall be via bilateral modification 

b) The Contractor shall manage the execution of the CEV System using the IMP. The 

Contractor shall report on contract progress in accordance with the IMP at each PMR 

1.7.(b) 

Integrated Master Schedule (IMS) 

a) The Contractor shall develop, maintain, and provide NASA access to an Integrated Master 

Schedule (IMS). The Contractor shall use this schedule for day-to-day management of the 

contract tasks Reference contract Clause H .12, Electronic Data Access 

b) The Contractor shall create and maintain a schedule that supports automated time phasing of 

tasks, and is a resource loaded, predecessor/successor structured, networked schedule, with 

critical path Identification and schedule assessment capability The Contractor shall 

Incorporate delivery schedules for NASA products and data Into their IMS and provide an 

integrated IMS that reflects the entire CEV project scope. 

c) The Contractor shall maintain and update the IMS to reflect changes in the IMP and deliver It 

in accordance with Section 13.1 of ORO CEV-B-003, Cost Performance Report 

d) The Contractor shall utilize the IMS as the source for schedule data delivered to NASA 

e) The Contractor shall integrate all risk mitigation activities Into the IMS 

f) The contractor shall provide monthly reporting of risk-based critical path analysIs (via CEV-B- 

003, CPR, Format 5 Explanations and Problem AnalysIs) Including but not limited to Monte 

Carlo based analysis, analyst Judgment and proposed mitigation strategies for line items that 

drive the risk-based critical path The contractor shall perform validation of logiC links within 

the schedule uSing an automated tool 

Deliverables 


• DRD CEV-B-003: Cost Performance Report 

1.8 Special Studies (IDIQ) 

a) The Contractor shall perform special CEV-related studies and analyses as directed by NASA 

The Contractor shall define the resources required as part of their response to NASA's 

Page 11 of 119





request for a task order plan The trade studies and analyses resulting from special studies 

shall also Include the Impact to system safety and life cycle cost. 

Page 12 of 119





2 CEV VEHICLE INTEGRATION 

CEV Vehicle Integration consists of the technical and management efforts of directing and 

controlling the integrated CEV System Engineering and Integration effort to achieve a solution 

that satisfies all CEV Project requirements and otherwise balances performance, 

cost/affordability, schedule, and risk This effort Includes the development of upgrade paths for 

future missions and integration of the CEV System with all elements of the Constellation 

Program. This element also Includes task efforts in managing Technical Reviews required by 

NASA 

2.1 VI Management and Administration 

Vehicle Integration Management and Administration consists of the efforts for planning, 

organizing, directing, coordinating, controlling, and approval processes used to accomplish 

Vehicle Integration objectives. Vehicle Integration consists of the efforts to manage the 

Contractor's systems engineering and integration activities and to manage the Contractor's 

participation in NASA-led Constellation Program systems engineering and Integration activities in 

accordance With NASA requirements and the Contractor's documented plans 

a) The Contractor shall manage their systems engineering and integration actiVities consistent 

with CxP-72008, Crew Exploration Vehicle Project Plan 

b) The Contractor shall participate in Crew Exploration Vehicle Project and Constellation 

Program systems engineering and integration activities in accordance With CxP-72008, CEV 

Project Plan 

c) The Contractor shall Implement plans for managing technical data products, processes and 

organizational roles and responsibilities used to accomplish their systems engineering and 

integration activities and document their plans In the Contractor's PMP (DRD CEV-M-001, 

CEV Prime Project Management Plan) 

2.1.(a) Technical Reviews 

1) The Contractor shall support the planning and execution of technical Integration reviews 

conducted by NASA. The Contractor shall support Integrated analysis and assessment efforts 

In support of the integration reviews to identify and resolve Integration issues with other 

Constellation elements, as reqUired 

2) The reviews conducted by NASA are contained In the Integrated Master Plan as defined in 

Attachment J-15 At these reviews, the Contractor shall develop and present data and 

respond to Review Item Discrepancies (RIDs) and Identified CoFR exceptions 

2.2 CEV Requirements Definition and Management 

a) The Contractor shall address all life cycle processes including development, manufacturing, 

test, distribution, operation, support, training, and disposal to derive a complete requirements 

(functional) baseline and functional architecture 

b) The Contractor, in conjunction With NASA, shall allocate the CXP-72000, Systems 

ReqUirements for the Crew Exploration Vehicle Element (CEV SRD), and External IRDs to 

the Spacecraft and ground support equipment. The Contractor shall document the 

requirements developed from thiS process In the Spacecraft Requirements 

Specification and the Ground Support Equipment ReqUirements SpeCification per 

ORO CEV-T-031, CEV Requirements Specification, and In ORO CEV-T·032, CEV 

Specification and Drawmg Trees. The Contractor shall Integrate Module SpecifiC Drawing 

Trees Identified in Sections 6.1.2, 6 2 2, 6 4 2 Into the Integrated Stack Drawing Tree. 

Page 130f119





c) The Contractor shall document the funcllonal decomposition, requirements allocation, and 

design to the component level in ORO CEV-T-033, Architecture Design Document. 

d) The Contractor shall provide a reqUirements database Within CRAOLE® to maintain bidirectional 

requirements traceability from the CEV System level/EIRDs and the CEV 

subsystem level requirements throughout the requirements allocallon process to the 

component level. The CRAOLE® database shall also Include a functional model to which the 

requirements are linked The Contractor shall provide NASA access to thiS capability 

through NASA ICE and proVide traceability reports at all milestone reviews to verify 

requirements traceability This traceability shall be maintained and continue through the 

design, procurement specifications, hardware and software configuration items reqUirements, 

and verification of the requirements and results Traceability shall be documented per ORO 

CEV-T-034, Requirements Traceability Report 

e) The Contractor shall conflgurallon manage the allocated requirements baseline and 

architecture throughout the performance period of this contract In accordance with Section 

1 3 (a) Configuration Management 

f) The Contractor shall perform Iterative and on-going analyses to validate the allocation of 

requirements and document the results In ORO CEV-T-010, System Performance Analysis 

Report. 

g) The Contractor shall assign each reqUirement an owner who is responSible for ensuring that 

the requirement is 1) consistent With evolVing requirements and the design baseline; 2) 

complete and suffiCient relative to similar requirements; 3) correctly and clearly written; 4) 

verifiable via test or other approved method; 5) mapped to specific verification event(s); 6) if 

appropriate, tracked with a TPM for ItS predicted compliance within allocated resources, 7) 

decomposed, allocated, and linked to related requirements, 8) assigned a valldallon method 

and validation plan cross-reference, and 9) properly represented in trade studies, analysis, 

and risk assessment 

h) The Contractor shall support the CEV SRR and develop, deliver and maintain the following 

documents: In addition to standard products delivered as part of 2 4 Integrated AnalYSIS 

CEV-S-003, System Safety Hazard Analyses, ORO CEV-T-031, CEV Spacecraft System 

Requirements Specification, ORO CEV-T-032, CEV Specification and Drawing Trees, and 

ORO CEV-T-034, Requirements Traceability Report. 

I) The Contractor shall define the modules, subsystems, components, and software Units that 

make up the CEV Spacecraft per the reqUirements and dellverables included in this section 

j) The Contractor shall allocate CEV Spacecraft requirements down to the component level for 

the deSign of flight articles and maintain the allocations/specifications over the life of the 

contract. 

k) The Contractor shall document module-level requirements uSing ORO CEV-T-031, CEV 

Requirements Specifications The Contractor shall produce a reqUirements 

document for each module 

Deliverables 

The Contractor shall deliver and maintain the following document(s)· 

• DRD CEV-T-031: CEV Spacecraft Requirements Specification 

• DRD CEV-T-031 CEV Requirements SpeCifications 

• DRD CEV-T-032: CEV Specification and DraWing Trees 

• DRD CEV-T-033: CEV Architecture DeSign Document 

• DRD CEV-T-034. CEV ReqUirements Traceability Report 

2.3 CEVand Program Integration and Interfaces Management 

CEV and Program Integration and Interfaces Management consists of the efforts to integrate the 

CEV System and integrate the CEV System into the Constellation and International Space 

Station Programs 

Page 14 of 119





2.3.(a) Constellation Program Integration 

a} The Contractor shall support NASA In the performance of all work necessary to successfully 

Integrate the CEV System Into the Constellation Program, as defined by the follOWing 

documents. 

o CXP-70026, Orion to Crew launch Vehicle (ClV) IRD 

o CXP-70028, Orion to Ground Systems IRD 

o CXP-70029, Orion to MiSSion Systems IRD 

o CXP-70035, Portable EqUipment, Payloads, and Cargo IRD 

o CXP-70033, Orion to Extravehicular ActiVity (EVA) System IRD 

o 

o 

CXP-70034, Orion to lunar Surface Access Module (lSAM) IRD 

CxP-70118-1 Constellation Program Systems to Communications and Tracking 

Network Interface ReqUirements Document, Volume 1: Orion. 

Support shall include' 

o Coordination of the development, allocation, maintenance, and Implementation 

of integration requirements between the CEV System and other Constellation 

elements. 

o Development and maintenance of the CEV to other Constellation element 

External Interface Control Documents per ORO CEV-T-029, Interface Control 

Documents. 

o DeSign, development, test, and evaluation of the Interfaces between the CEV 

System and other Constellation Program elements and the integrated 

performance of the CEV with the other Constellation Program elements for 

nominal, as well as Critical, contingency deSign cases including abort design 

cases as appropriate NASA will provide, aerodynamic and 

aerothermodynamlc analyses for the CEV while mated to its launch vehicle and 

while unmated. The Contractor shall deSign the CEV for the resultant induced 

structural and thermodynamiC loads The Contractor shall use the applicable 

requirements In Contract Attachment J-3, Table 1 2, Applicable EnVironmental 

Data Documents, for loads analysis of the CEV while mated to its launch 

vehicle 

o Participation In the Constellation Program and other Project System Reviews. 

Participation In the requirements reconCiliation actiVities that will occur after the 

Constellation Program and other Project ReViews. 

b} The Contractor shall perform analyses and tests and provide reports and engineering data 

supporting Integration and operation of CEV and other Constellation elements such as: 

o Structural models and analyses for static, dynamiC and coupled-loads analyses 

o Mass properties, dimenSions and phYSical (material, thermal, etc) properties 

o Rendezvous, proximity operations, and abort mode trigger condition and 

Implementation assessments 

o Integrated compatibility analyses (EMC, RF, etc.) 

o Interface and integration drawings and buildltest procedures 

The reports and engineering data shall be provided In ORO CEV-T-010, System Performance 

Analysis Reports 

c) The Contractor shall perform analyses and support Integrated assessments in support of 

periodic Constellation Program Integration Reviews conducted in conjunction With other 

NASA elements as deSCribed in ORO CEV-M-001, CEV Prime Project Management Plan 

Analyses and assessments performed in support of Constellation Integration Reviews shall 

be documented In accordance With ORO CEV-T-030, CEVIConstellation Integrated 

Assessment Document. 

Deliverables 

The Contractor shall deliver and maintain the following(s) 

• DRD CEV-T-029' External Interface Control Documents for Constellation Elements 

Page 15 of 119





• DRD CEV-T-030 CEV/Constellation Integrated Assessment Document 

Constellation Program Integration related information IS Incorporated Into the follOWing documents 

delivered under Section 2.4, Integrated AnalysIs: 

• DRD CEV-T-010. System Performance AnalysIs Report 

2.3.(b) CEV to International Space Station Program Integration 

a) The Contractor shall support NASA in the performance of all work necessary to successfully 

Integrate the CEV System with the ISS Program Support shall include. 

o Coordination of the development, allocation, maintenance, and implementation 

of integration requirements between the CEV System and the ISS Program. 

o Development and maintenance of the CEV to ISS External Interface Control 

Documents per ORO CEV-T-029, Interface Control Documents. 

o The Contractor shall use CXP-70031, Orion to International Space Station 

(ISS) IRD to assist in the development of CEV to ISS Interfaces 

o DeSign, development, test, and evaluation of the interfaces between the CEV 

and ISS and the Integrated performance of the CEV With the ISS for nominal as 

well as critical contingency deSign cases 

b) The Contractor shall perform analyses and tests and provide reports and engineering data 

supporting Integration and operation of CEV and ISS appropriate to such integration, such as: 

o Structural models and analyses for statiC, dynamic and coupled loads analyses 

o Mass properties, dimensions and phYSical (material, thermal, etc) properties 

o Rendezvous, proximity operations, and abort trigger condition and 

Implementation assessments 

o Integrated compatibility analyses for all Impacted systems 

o Interface and integration draWings and bUild/test procedures 

The reports and engineering data shall be provided in ORO CEV-T-010, System Performance 

Ana/ysis Reports 

Deliverables 

The Contractor shall deliver and maintain the follOWing document(s): 

• DRD CEV-T-029 External Interface Control Documents for ISS Elements 

ISS Program Integration related information is incorporated Intothe following documents delivered 

under Section 2 4, Integrated AnalYSIS. 

• DRD CEV-T-010: System Performance AnalYSIS Report 

2.3.(c) Spacecraft Integration 

Spacecraft Integration Incorporates the efforts required to define and manage the internal 

spacecraft Interfaces Spacecraft Integration includes tasks to perform analyses and provide 

reports and engineering data supporting integration, verification and operation of CEV and 

provide technical data, and models required to perform Integrated CEV level analyses 

a) The Contractor shall develop, maintain, and deliver all draWings and technical Computer 

Aided Design (CAD) models of the CEV Spacecraft system, modules, subsystems and 

components 

b) The Contractor shall develop and maintain models and simulations for the CEV Spacecraft, 

modules, subsystems, and components using ORO CEV-T-001, Integrated Models, 

Simulations and Support Plan, and ORO CEV-T-002, CEV Engineering Models 

c) The Contractor shall document and maintain Interface requirements using ORO CEV-T-035, 

Internal Interface Requirement Document (IRD) The Contractor shall produce an IRD for 

each module that interfaces With another module. 

d) The Contractor shall perform the system Integration effort required to manage and control the 

Internal spacecraft interface definition process 

Page 160f119





e) The Contractor shall perform analyses required to validate the allocation of requirements and 

shall document the results In ORO CEV-T-010, System Performance Analysis Report. 

f) The Contractor shall document all internal interface design details uSing ORO CEV-T-029, 

CEV Interface Control Documents. The Contractor shall produce an ICD (CEV-T-029) for 

each Module that interfaces with another Module 

g) The Contractor shall develop and maintain the overall vehicle system design which ensures 

all subsystems are integrated into the vehicle and that the total vehicle performance closes in 

compliance with the system requirements. The Contractor shall Include NASA personnel on 

all design teams established by the Contractor. 

h) The Contractor shall design and develop the spacecraft In compliance with the NASA 

provided and maintained CxP-72085, Crew Exploration Vehicle (CEV) Spacecraft Outer Mold 

Line (OML), and Center of Gravity (Cg) box definition. The Contractor shall submit changes 

to NASA against the Spacecraft OML baseline to accommodate maturing design features. 

i) The Contractor shall design and develop the spacecraft In compliance with the NASA CxP- 

72167, Orion Aerodynamic Database, CxP-72168, Orion Aerothermodynamic Database. 

j) NASA will provide the following products to the Contractor' 

o CxP-72085, Crew Exploration Vehicle (CEV) Spacecraft Outer Mold Line 

(OML) 

o CxP-72167, Orion Aerodynamic Database (for all phases of flight) 

o 

o 

o 

CxP-72168, Orion Aerothermodynamic Database (for all phases of flight) 

CEV Spacecraft docking components (Androgynous Peripheral Assembly 

System (APAS) and Low Impact Docking System (LIDS» of the docking 

system for ISS and LSAM docking requirements 

Parachute system In support of nominal and abort entries (see Landing & 

Recovery Systems, section 6 1 314) with exception of pyrotechnic devices 

excluding pyrotechnic reefing line cutters in accordance with Attachment J-9 

Deliverable Items LISt. 

o Suit Vehicle Multiuse Connector 

o Pyrotechnics initiators 

o CEV to ISS Docking Adapter 

o ISS C31 Communications Adapter (ICCA) 

o Active and passive radiation Instrumentation 

All Government Furnished EqUipment (GFE) product teams Will produce data deliverables 

equivalent to the contractor furnished equipment product data deliverables 

k) The Contractor shall Integrate the NASA-provided products Into the spacecraft design and 

flight configurations to ensure that the Integrated spacecraft meets CXP-72000, Systems 

ReqUirements for the Crew Exploration Vehicle Element (CEV SRD). The Contractor shall 

integrate the NASA-provided products and documentation into applicable product 

deliverables Included in this SOW (these include requirements, drawings, certification 

packages, integrated analyses, and the spacecraft) 

I) NASA Will maintain detailed oversight of all spacecraft deSign activities. The Contractor shall 

maintain responsibility for delivery of a deSign that meets the requirements The detailed 

process diSCUSSion to accomplish this can be found In CxP-72008, Crew Exploration Vehicle 

Project Plan. The Contractor shall include NASA personnel on all deSign teams established 

by the Contractor 

m) The Contractor shall allocate requirements to the following government furnished products: 

o CEV Spacecraft docking components (APAS and LIDS) of the docking system 

for ISS and LSAM docking reqUirements 

o Parachute system in support of nominal and abort entries 


n) The Contractor shall ensure that traceability between the levels IS In accordance with the 

capability established in Section 2 2, ReqUirements Definition and Management 

0) The Contractor shall use the following standards for developing all subsystems' 

o 

AIAA-S-080, AIAA Standard for Space Systems - MetalliC Pressure Vessels 

Pressurized Structures, and Pressure Components 

Page 17 of 119





o ANSI/AIM-S-081A-2006, AIM Standard for Space Systems - Composite 

Overwrapped Pressure Vessels 

p) The Contractor shall develop and maintain the ISS Resident RF equipment to ICCA Interface 

Control Document in accordance with DRD CEV-T-029 Interface Control Documents. 

Deliverables 


• DRD CEV-T-029' Internal Interface Control Documents 

• DRD CEV-T-029. Internal Interface Control Document for ISS Resident RF EqUipment to 

ICCA 

• DRD CEV-T -035' Internal Interface Requirements Document (for each Module that 

Interfaces with another Module) 

Spacecraft Integration related Information is incorporated intothe follOWing documents delivered 

under Section 24, Integrated AnalysIs: 

• DRD CEV-T -001: Integrated Models, Simulations, and Support Plan 

• DRD CEV-T-002. CEV Engineering Models 

• DRD CEV-T -010: System Performance AnalysIs Report 

2.4 Integrated Analysis 

Integrated AnalysIs Includes Systems Engineering and Integration AnalysIs activities to provide 

consistency across all aspects of the CEV System development efforts. This element includes 

the work to identify and conduct trade studies and cost-effectiveness analyses across the CEV 

System and the overall Constellation Program Architecture. It includes efforts to develop design 

and analysis tools, and models and Simulations It also includes tasks to define, control and 

verify CEV mass properties and other controlled technical margins across the CEV vehicle. 

a) The Contractor shall manage crosscutting englneenng issues within the spacecraft, such as 

the allocation of resources Into the design elements Including the management of margins 

and deSign and operational performance estimates for various modules and below This 

Information shall be documented in ORO CEV-T-036, Margins Management Plan/Report, and 

Implemented by the Contractor. 

b) The Contractor shall perform analyses reqUired to validate the allocation of requirements and 

shall document the results In ORO CEV-T-010, System Performance Analysis Report. 

c) The Contractor shall identify and conduct trade studies and cost-effectiveness analyses to 

ensure realistic options and alternatives are assessed for key CEV System requirements and 

deSign deCisions. The assessment of cost shall address all elements of life cycle cost 

significantly affected by the matters being traded. 

d) The Contractor shall develop and implement a CEV System Analysis Plan The Contractor 

shall deliver the analYSIS plan per ORO CEV-T-008, CEV System Analysis Plan. The 

Contractor shall include the relationship of all analysis cycles and their products to the major 

milestones, events, etc they are to support in the Integrated Master Schedule as part of ORO 

CEV-B-003, Cost Performance Report. The Contractor shall report results of the analysis 

performed per ORO CEV-T-009, CEV AnalYSIS Reports. 

e) The Contractor shall perform an Integrated system performance analYSIS and provide reports 

In accordance with ORO CEV-T-010, System Performance Analysis Report at major 

milestone reviews and at Intervals prescnbed In CxP-72008, Crew Exploration Vehicle 

Project Plan. 

f) The Contractor shall prOVide the analysis to validate all CEV System requirements through 

the lowest level of decomposition and document the validation per ORO CEV-T-009, CEV 

Analysis Reports 

g) The Contractor shall provide/receive various mathematical models, configuration data, and 

analytical data necessary to perform Integrated assessments and analysis to integrate With 

the Constellation Program 

Page 18 of 119





h) The Contractor shall provide/receive various mathematical models, configuration data, and 

analytical data necessary to perform Integrated assessments and analysIs to Integrate with 

the ISS Program 

I) The Contractor shall define a plan for managing mass properties and document thiS plan in 

ORO CEV-T-042, Mass Properties Control Plan The Contractor shall implement this plan 

and document the results In ORO CEV-T043, Mass Properties Reports. 

J) The Contractor shall develop, Implement, deliver and maintain a Modeling and Simulation 

Support Plan In accordance with ORO CEV-T-001, Integrated Models, Simulations and 

Support Plan. 

k) The Contractor shall deliver and maintain models supporting discipline-oriented engineering 

analysis and trade studies In accordance with ORO CEV-T-002, CEV Engineering Models 

These models shall be consistent with the coordinate system described In CxP 70138, 

Constellation Program Level 2 Coordinate Systems 

I) The Contractor shall deliver and maintain a system architecture model and discrete-event 

simulation to evaluate effectiveness and performance of the vehicle design In accordance 

with ORO CEV-T-001, Integrated Models, Simulations and Support Plan. 

m) The Contractor shall deliver and maintain modular, high-fidelity, time-stepped simulations of 

vehicle behavior for avionics hardware and software Integration and test In accordance with 

the IEEE 1516 3-2000 (High Level Architecture) standard and ORO CEV-T-001, Integrated 

Models, Simulations and Support Plan. 

n) The Contractor shall make available to NASA all Contractor-developed design and analysis 

tools, models and simulations used In the development of the CEV System, including sourcecode 

and geographic models/block diagrams from Computer Aided Software Engineering 

Tools, in accordance With the Electronic Data Access Clause (H.12) 

0) Every tool, model, and simulation delivery shall be accompanied by a meta-data document In 

accordance With CXP-70041, Constellation Program NExlOM Standard for Tool, Model and 

Simulation Deliveries 

p) The Contractor shall provide the configuration management data for all technical models and 

drawings to the NASA ICE per ORO CEV-M-003, Configuration Management Plan and 

Reports. 

q) The Contractor shall deliver all CAD models per ORO CEV-T-003, CEV CAD Models, and 

drawings per ORO CEV-T-004, CEV Drawings. 

r) The Contractor shall participate in the Verification, Validation and Accreditation process 

described in CXP-70076, Constellation Program Modeling and Simulation Management 

Requirements 

s) If the Contractor utilizes modeling and simulation to conduct analYSIS In support of verification 

specification compliance, the Contractor shall comply with ORO CEV-T-001, Integrated 

Models, SImulations and Support Plan, and ORO CEV-T-002, CEV Engineering Models. 

t) NASA will develop drawings and CAD models for all GFE NASA will use ORO CEV-T-003, 

CEV CAD Models, and ORO CEV-T-004, CEV Drawings, as the template for development 

and delivery of these items 

u) NASA will develop models and Simulations for all GFE NASA will use ORO CEV-T-001, 

Integrated Models, Simulations and Support Plan, and ORO CEV-T-002, CEV Engineering 

Models, as the template for development and delivery of these items 

Deliverables 


• DRD CEV-T -001. Integrated Models, Simulations and Support Plan 

• DRD CEV-T-002 CEV Engineering Models 

• DRD CEV-T-003: CEV CAD Models 

• DRD CEV-T-004' CEV Drawings 

• DRD CEV-T-008. CEV System AnalYSIS Plan 

• DRD CEV-T-009' CEV AnalYSIS Reports 

• DRD CEV-T-010' System Performance AnalYSIS Report 

• DRD CEV-T-036: Margins Management PlanlReport 

Page 19 of 119





• DRD CEV-T-042. Mass Properties Control Plan 

• DRD CEV-T-043. Mass Properties Reports 

2.5 Spacecraft Crew Cabin and Cockpit Layout Design 

Requirements 

a) NASA and the Contractor shall jointly participate in the development of detailed design 

requirements for the CEV crew cabin, and cockpit layout and functionality 

b) Reserved 

c) Reserved 

d) The Contractor shall provide materials (e.g., layout schematics, computer 3-D models) for 

two Crew Station Reviews The Contractor shall conduct these two Crew Station Reviews 

between System PDR and System CDR of the Contractor's CEV crew cabin Internal layout 

design utilizing NASA-Identified Crew Office representatives. After each Crew Station 

Review, the Contractor shall prepare and provide to NASA an impact assessment of 

quantifiable design Issues arising from each review. 

e) NASA will document the display format standards in CxP 72242, CEV Display Format 

Standards Document 

f) NASA and the Contractor shall jointly participate in prototyping the layout and behavior of the 

display formats, uSing CxP 72242, CEV Display Format Standards Document as an 

applicable document The Contractor shall develop and maintain a Display Format Dictionary 

in adccordance With DRD CEV-T-048, Software ReqUirement Specification. The Display 

Format Dictionary shall document the results of the protyping effort. 

g) The Contractor shall develop and maintain DRD CEV-T-048, Display & Control Software 

Requirements Specification appendix for the Display Format Dictionary. 

h) The contractor shall provide supplemental rapld-prototyplng tool operators to augment the 

NASA provided tool-operators The tool operators will provide assOCiated stub models to 

exercise the prototype display formats. (1010) 

I) 

2.6 CEV Systems Integration Management 

CEV Systems Integration Management consists of the discipline-specific efforts to manage the 

overall Integrated CEV system architecture definition and engineering functions including the 

interfaces with external Constellation Systems. This includes the technical and management 

efforts of directing and controlling the integrated engineering effort for the CEV spacecraft In all 

modes and configurations. 

Systems Integration Management consists of the efforts to manage the Contractor's systems 

integration activities and to manage the Contractor's participation In NASA-led Constellation 

Program systems integration activities in accordance with NASA requirements and the 

Contractor's documented plans. 

a) The Contractor shall manage their systems integration activities consistent with CxP-72008, 

Crew Exploration Vehicle Project Plan. 

b) The Contractor shall partiCipate In CEV Project and Constellation Program systems 

Integration activities in accordance with CxP-72008, Crew Exploration Vehicle Project Plan 

c) The Contractor shall Implement plans for managing technical data products, processes and 

organizational roles and responSibilities used to accomplish their systems integration 

actiVities and document their plans In the Contractor's PMP (ORO CEV-M-001, CEV Prime 

Project Management Plan) 

d) The Contractor shall perform reqUIrements development, design, analysis and trade studies, 

assemblyfproduction, Integration, testing, verification, validation, qualification, certification, 

and delivery for all CEV Spacecraft subsystems to the component level. A small number of 

Page20of119





subsystems contain government furnished products These NASA-provided products will be 

detailed in each subsystem section. 

e) The Contractor shall hold subsystem design reviews prior to the system PDR and CDR. 

f) The Contractor shall perform analyses, trade studies, and developmental testing to determine 

the spacecraft architecture and component design that meets all requirements and best 

balances performance, cost, schedule, and risk The Contractor shall document this design 

information in each of the subsystem design and data books. 

g) The Contractor shall demonstrate how the design maps to and complies with the CEV 

System-level and external Interface reqUirements The Contractor shall document this 

requirements mapping in ORO CEV-T-034, Requirements Traceability Report. 

h) The Contractor shall support the documentation and delivery of the Master Verification Plan 

(ORO CEV-T-015). The Contractor shall document this information at the CEV Spacecraft 

system, module, subsystem, and component levels in the Spacecraft Master Verification 

Plan. 

I) The Contractor shall specify, produce and deliver integration testing assemblies and flight 

test articles necessary to Implement the Spacecraft Master Verification Plan. The Contractor 

shall document this information at the CEV Spacecraft system, module, subsystem, and 

component levels in ORO CEV-T-017, Certification Data Package. Note: Module, subsystem 

and component-level test and test documentation requirements are defined In Sections 6.1.5 

CM Test, Verification, and Certification, 6.2.5 SM Test, Verification, and Certification, 6.4.5 

LAS Test, Verification, and Certification and 6 5 4 CEV Software Test and Verification The 

contractor shall deliver Certification Approval Requests per ORO CEV-T-018 in preparation 

for design certification milestones. 

j) The Contractor shall perform acceptance testing at the Integrated spacecraft level using ORO 

CEV-T-039, Acceptance Test Procedures, and document the results using ORO CEV-T-040, 

Acceptance Data Package 

k) NASA has Identified subsystem-specific standards the Contractor shall follow dUring all 

design, development, and test activities The standards are listed in Subsection sections 

within Sections 6.1.3 (CM Subsystems), 62 3 (SM/SA Subsystems) and 6.4.3 (LAS 

Subsystems Crosscutting standards applYing to all subsystems are covered in Section 2.B, 

Specialty Engineering, sections 2 9 (Aerosciences), and 24 (Integrated AnalYSIS). 

I) The Contractor shall use the following standards and requirements documents for developing 

all subsystems' 

o JPR BOBO.5, JSC Design and Procedural Standards (and associated Children 

documents as speCified In Attachment J-3, Applicable, Guidance, and 

Informational Documents List) (exclusive of government "shalls") 

o CXP-70024, Constellation Human Systems Integration ReqUirements (HSIR) 

(and associated Children documents as specified In Attachment J-3, 

Applicable, Guidance, and Informational Documents List) 

Deliverables 


• DRD CEV-T-034. ReqUirements Traceability Report 

The following DROs for the integrated vehicle are collected in the OROs specified In Sectlon10. 

• ORO CEV-T -015. Master Verification Plan 

• ORD CEV-T-017 Certification Data Packages 

• DRD CEV-T-01B. Certification Approval Request 

• DRD CEV-T-039. Acceptance Test Procedures 

• ORO CEV-T-040' Acceptance Data Package 

Page 21 of 119





2.6.1 Avionics Integration 

The contractor shall integrate the efforts to design, develop, test, certify, and deliver the software, 

computers, firmware, and other electncal and electronic equipment used for commanding, 

monitoring, and communicating with CEV sUbsystems. 

AVIonics Integration includes the integration of the hardware and software components in the 

areas of Flight Software, Command & Data Handling (C&DH), Instrumentation, Communications 

and Tracking (C&T), Displays. & Controls (D&C), and all data/signal Interfaces between these 

functions and other CEV Spacecraft systems/modules/subsystems/components and external 

elements. This element also includes efforts to develop and implement an approach for modular 

open systems architecture in the design of the CEV System, and to define the collection and 

processing of vehicle transducer and sensor information and vehicle health monitoring data 

specified by other subsystems for use on the vehicle and ground. 

a) The Contractor shall use a modular, multi-use open systems approach In the design of the 

CEV System making the Impact to the overall modular, multi-use open systems architecture a 

primary conSideration In the selection of eqUipment to meet the CEV design functionality. 

ThiS approach shall be reflected In the architecture documented In the Architecture Design 

Document (ORO CEV-T -033) 

b) The Contractor shall use a modular, multi-use open systems approach and analYSIS of longterm 

supportability, Interoperabllity, and growth for future modifications in the final selection of 

CEV equipment and the Integration approach for future Constellation elements and 

equipment 

c) The Contractor's design shall permit future upgrades and incremental technology insertion to 

allow for incorporation of additional or higher performance components with minimal impact 

to the existing systems 

d) The Contractor shall report the results of an open systems architecture analysis for modular, 

multi-use systems that extends beyond CEV to other Constellation elements and equipment 

in accordance With ORO CEV-T -009, CEV Analysis Reports. 

e) NASA Will perform independent requirements validation and design certification in key areas. 

In these key areas NASA will establish design requirements teams Intended to integrate the 

activities of NASA and the Contractor. The Contractor shall participate In and support these 

design requirements teams for CEV AVIonics Integration Laboratory Requirements 

f) The Contractor shall define and Implement an integrated plan for CEV Spacecraft 

Instrumentation. The Contractor shall provide in thiS plan provIsions for the calibration of the 

instrumentation transducers and sensors to assure end-to-end error and tolerances are within 

required performance specifications The Contractor shall document these plans in ORO 

CEV-T-041, CEV InstrumentatIon Plan 

g) The Contractor shall define and document sensor range and calibration Information in ORO 

CEV-T-046, CEV Data and Command Dictionary, uSing the standards and formats called out 

in CxP 70022-4 Constellation Program Command, Control, Communication, and Information 

(C31) Interoperability Standards Books, Volume 4. Information Representation SpeCification 

(and associated children documents as speCified In Attachment J-3, Applicable, Guidance, 

and Informational Documents List). 

h) The Contractor shall develop, Implement, and maintain an Integrated Avionics Master 

Verification Plan, per ORO CEV-T-015, that details the Contractor's plan for verifying, 

certifying, and acceptance of the aviOniCS system 

I) The Contractor shall perform certification testing of the aVionics subsystem and document the 

results using ORO CEV-T-017, CertIfIcation Data Package- 

J) The Contractor shall develop and maintain a sortable CEV Data and Command Dictionary 

(ORO CEV-T-046), which Includes channelization information, calibration information, 

telemetry Information, and command Information reqUired to define, manage and record all 

data elements that Interface with the core aVionics software and hardware, the subsystem 

specifiC software, and the ground systems, using the standards and formats called out in CxP 

70022-4 Constellation Program Command, Control, CommUniCation, and Information (C31) 

Page 22 of 119





Interoperabllity Standards Books, Volume 4 Information Representation Speclflcation(and 

associated 

k) The Contractor shall develop an AVIonics Subsystem - Constellation C31 Interoperabllity 

Report (also see section 6.5.2) per ORO CEV-T-047, Avionics Design and Data Book Volume 

V - Avionics Subsystem - Constellation C3//nteroperability Report, to detail how the 

Contractor's design will adhere to CXP-70022, Constellation Command, Control, 

Communication, and Information (C31) Interoperabllity Standards Book, Volumes 1, 2, 3, 4, 5 

and 8 (and associated Children documents as specified In Attachment J-3, Applicable, 

Guidance, and Informational Documents List). 

I) The Contractor shall develop ORO CEV-T-047, Avionics Design and Data Book Volume / 

Avionics System-Level Data, which contains aVIOniCS architecture diagrams, results of trade 

studies and performance analyses, block diagrams, schematics, prototyplng results, design 

data, planned growth proviSions/margins/scarring, and discussion of fault tolerance and 

effects of failures on performance 

m) The Contractor shall utilize open architecture designs and Industry standards where feaSible 

and cost-effective in the avionics subsystem hardware and software designs, taking Into 

consideration long-term maintainability/availability and extensibility. The Contractor shall 

utilize modular hardware and common building blocks such as power supplies, chassis, 

processor cards, memory cards, network cards, etc where feasible and cost-effective 

n) The Contractor shall utilize standard compilers, operating systems, and software 

development tools/enVironments throughout the CEV software deSign and development 

process where feaSible and cost-effective 

0) Reserved 

p) For each avionics LRU that requires active cooling, the Contractor shall determine the 

maximum time that the LRU can be operated Without active cooling applied. The Contractor 

shall document this data in each volume of the aVionic design and data book 

q) The Contractor shall use the follOWing standards for designing the aVIOniCS subsystem: 

CxP 70022-1 Constellation Program Command, Control, Communication, and Information 

(C31) Interoperabllity Standards Books, Volume 1 Interoperabllity Specification (and 

associated Children documents as specified In Attachment J-3, Applicable, GUidance, and 

Informational Documents List) 

CxP 70022-2 Constellation Program Command, Control, CommUniCation, and Information 

(C31) Interoperability Standards Books, Volume 2: Spectrum and Channel Plan 

CxP 70022-3 Constellation Program Command, Control, Communication, and Information 

(C31) Interoperabllity Standards Books, Volume 3. Master Link Book 


(C31) Interoperability Standards Books, Volume 4: Information Representation Specification 

(and associated Children documents as specified in Attachment J-3, Applicable, GUidance, 

and Informational Documents List) 


(C31) Interoperability Standards Books, Volume 5: Data Exchange Protocol Specification 


(C31) Interoperability Standards Books, Volume 8. Common Command and Control 

Functional Requirements (and associated Children documents as speCified in Attachment J- 

3, Applicable, Guidance, and Informational Documents List) 

r) The Contractor shall design, develop, produce, Integrate, verify, validate, certify, operate, 

maintain, document, and deliver a separate backup flight control system (BFCS), which 

houses an Independently developed subset of the primary flight software functions. 

s) The Contractor shall deSign, develop, produce, integrate, verify, validate, certify, operate, 

maintain, document, and deliver an avionics architecture based on fifth generation 

Page230f119





commercial aircraft heritage, that IS of a high (greater than 6) technology readiness level 

(TRL) 

t} The Contractor shall lead the Integration of the integrated resident RF communications 

hardware and the GFE provided ISS C31 Communications Adapter (ICCA), with the ISS. 

u} The Contractor shall develop an Avionics Subsystem - Constellation Functional Security 

Report per ORO CEV-T -047, Avionics Design and Data Book Volume VI - Avionics 

Subsystem - Constellation Security Report, to detail how the Contractor's design will adhere 

to CxP 70070-ANX05, Book 1, Constellation Program Functional Security ReqUirements (and 

associated children). 

v) The Contractor shall develop and maintain ORO-CEV-T-031, CEV 

ReqUirements SpecificatIOn for the AVIOniCS Subsystem 

w) The Contractor shall develop and maintain ORO CEV-T-029, CEV Interface 

Control Documents and ORO CEV-T -035, CEV Interface Requirements 

Documents for the Avionics Subsystem interfaces to other subsystems. 

x) The Contractor shall document the AVIOniCS subsystem requirements traceability in ORO 

CEV-T-034, Requirements Traceability Report. 

Deliverables 


• DRD-CEV-T-015: Integrated Avionics Volume Master Verification Plan (excluding GN&C) 

• DRD-CEV-T-029. AVioniCs Subsytem Interface Control Documents 

• DRD-CEV-T-031. Avionics Subsystem Requirements Specification 

• DRD-CEV-T-035: Avionics Subsytem Interface Requirements Documents 

• DRD CEV-T-041' CEV Instrumentation Plan 

• DRD CEV-T-046 CEV Data and Command Dictionary 

• DRD CEV-T-047: Avionics Design and Data Book Volume 1 AviOniCS, System-Level Data 

• DRD CEV-T-047: AVIOniCS DeSign and Data Book Volume VI, Avionics Subsystem 

Constellation Security Report 

The following subsystem specific data is collected in the DRDs specified in Section 2.2: 

• DRD CEV-T-033: Architecture Design Document 

• DRD CEV-T-034. ReqUirements Traceability Report 

The following subsystem specific data is collected in the DRDs specified In Section 2.4: 

• DRD CEV-T-009 CEV AnalYSIS Reports 

The follOWing subsystem speCifiC information IS collected In the DRDs specified in Section 6.5.2. 

• DRD CEV-T-047. Avionics Design and Data Book Volume V, AVIOniCS - Constellation 

C31 Interoperabillty Report 

The following subsystem specific data is collected in the DRDs speCified In Sections 10.2: 

• DRD CEV-T-017. Certification Data Package 

2.6.2 Command and Data Handling (C&DH) Integration 

C&DH hardware includes data processing and computing resources including processors, 

memory, inpuVoutput devices, data multlplexersl demultiplexers, mass storage devices, intercomputer 

time-synchronization devices, and networking equipment 

(a) The contractor shall Integrate the DDT&E efforts of the C&DH hardware. 

(b) The Contractor shall document the design integration for all C&DH hardware as speCified in 

ORO CEV-T-047, AviOniCS Design and Data Book Volume /1- C&DHllnstrumentation 

Subsystem Data. 

(c) The Contractor shall partiCipate With NASA In the Integration of CEV hard-line interface to the 

GFE ICCA on board ISS. 

(d) The Contractor shall develop and maintain ORO CEV-T-031, CEV 

Requirements Specifications for the C&DH components 

Page 24 of 119





Deliverables 


• DRD CEV-T-031: Command and Data Handling Component Requirements Specifications 

• DRD CEV-T-047. Avionics Design and Data Book Volume II C&DH/lnstrumentation 

Subsystem Data 

2.6.3 Communications and Tracking 

The Contractor shall integrate the DDT&E efforts of the space-to-ground and space-to-space 

communication links, RF/optlcal tracking deVices (excluding navigational aids), audio and 

videolimagery equipment and ISS resident RF communications hardware including hardware to 

be installed on the ISS 

(a) The Contractor shall prepare, deliver, and maintain ORO CEV-T-047, Avionics Design and 

Data Book Volume III - Communications and Tracking Subsystem Data. 

b) The Contractor shall participate in the development of Constellabon's Integrated 

communications and tracking concepts, architecture, and requirements. The Contractor shall 

comply with the design of the Constellation communications architecture according to CXP- 

70022 Constellation Program Command, Control, Communication, and Information (C31) 

Interoperabllity Standards Books Volumes 1, 2, 3, 4, 5 and 8 (and associated Children 

documents as specified In Attachment J-3, Applicable, Guidance, and Informational 

Documents List) 

c) Subsystems other than C&T may contain RF/optlcal devices (Le., wireless sensors, GPS) 

The Contractor shall apply the standards In this section to those subsystems containing 

RF/opbcal deVices The Contractor shall proVide the same documentation required in ORO 

CEV-T-047, AVIOniCS DeSign and Data Book Volume III - Communications and Tracking 

Subsystem Data, for all subsystems containing RF/optlcal deVices The Contractor shall 

document this Information In that subsystems design and data book. 

d) The Contractor shall participate In the development of Radio Frequency/Optical ICDs and 

document the results In ORO CEV-T-058, Radio Frequency/OpticaIICDs. 

e) The Contractor shall use the following standards for deSigning the C&T subsystem: 

o 450-SNUG, Space Network Users' GUide 

o FIPS 140-2, Security Requirements for Cryptographic Module 

o FIPS-197, Advanced Encryption Standard 

o 

o 

ICD-GPS-200, Navstar GPS Space Segment/Navigation User Interfaces 

NTIA Manual, National Telecommunications and Information Administration 

(NTIA) Manual of Regulations & Procedures for Federal Radio Frequency 

Management (May 2003 Edition, May 2005 ReVISions) Chapter 10 

f) The Contractor shall deSign, develop, produce, Integrate, verify, validate, certify, operate, 

maintain, document, and deliver ISS resident RF communications hardware (antenna, 

amplifiers, transponders, baseband processing, and other associated hardware). 

g) The Contractor shall Integrate the reSident RF communications hardware with the GFE 

prOVided ISS C31 Communications Adapter (lCCA). 

h) The CEV Contractor shall participate with NASA and the Constellation Program in 

development of Radio Frequency (RF) spectrum management in compliance with the 

National Telecommunications and Information Administration (NTIA) Manual of Regulations & 

Procedures for Federal Radio Frequency Management (May 2003 Edition, May 2005 

ReVisions), Chapter 10 The Contractor shall provide RF spectrum management 

documentation In ORO CEV-T-026, Spectrum Management Documents 

I) The Contractor shall develop and maintain ORO CEV-T-031, CEV 

ReqUirements SpeCifications for the C&T components. 

Defiverables 


• DRD CEV-T-026, Spectrum Management Documents 

Page 25 of 119





• DRD CEV-T-031 Communication & Tracking Components Requirements Specifications 

• DRD CEV-T-047' AVionics Design and Data Book Volume 111- Communications and 

Tracking Subsystem Data 

• DRD CEV-T-058 Radio Frequency/OptlcallCDs 

2.6.4 Displays & Controls Integration 

The contractor shall integrate the DDT&E efforts of the crew interface with the on-board computer 

systems and the manual controls/feedbacks used by the crew to control the vehicle, Interact with 

ItS subsystems, and mOnitor automated processes. This work is done in concert with Human 

Engineering activities under Section 2 8, Specialty Engineering, and 2.5, Spacecraft Crew Cabin 

and Cockpit Layout Design Requirements. 

a) Reserved 

b) The D&C subsystem shall utilize naming conventions as established in CXP-02007, 

Constellation Nomenclature Plan. 

c) The Contractor shall prepare, maintain, and deliver Avionics Design and Data Book Volume 

IV - Displays and Controls Subsystem Data per ORO CEV-T-047 

d) The Contractor shall develop and maintain ORO CEV-T-031, CEV 

ReqUirements Specifications for the Displays and Controls components 

Deliverables 


• DRD CEV-T-031: Displays & Controls Components ReqUirements Specifications 

• DRD CEV-T-047: Avionics Design and Data Book Volume IV - Displays and Controls 


2.6.5 Electrical Power Subsystem (EPS) Integration 

The contractor shall integrate the DDT&E efforts of the power generation, energy storage, 

electrical power distribution and control, and external/internal CEV lighting 

a) The Contractor shall participate with the Constellation Program In the development of ORO 

CEV-T-060, Electrical Power Quality Specification Requirements Document. The Contractor 

shall perform testing and analyses required to develop a power quality specification that will 

be compatible with the technology needed to generate, store, and distribute electrical power. 

The Constellation Program will provide oversight and guidance with an emphasis to tailor this 

specification to be compatible to both the CEV and other Similar Constellation EPS systems. 

b) The Contractor shall document the design for the Electrical Power Subsystem as specified in 

ORO CEV-T-059, Electrical Power System (EPS) Design and Data Book 

c) The Contractor shall develop, implement, and maintain an Integrated EPS Master Verification 

Plan, per ORO CEV-T-015, that details the Contractor's plan for verifying, certifying, and 

acceptance of the EPS system. 

Deliverables 


• DRD CEV-T-059' Electrical Power System (EPS) Design and Data Book 

• DRD CEV-T-060: Electrical Power Quality SpeCification Requirements Document 

The follOWing subsystem specific information IS collected In the DRDs specified in Section 10.2 

• DRD CEV-T -015. EPS Volume - Master Verification Plan 

Page 26 of 119





2.6.6 Mechanisms Integration 

The Contractor shall Integrate the DDT&E efforts of any mechanical or electromechanical devices 

that control the movement of a mechanical part of the spacecraft relative to another part. These 

devices Include latches, hatches, doors, and fasteners installed, removed, or adjusted dUring 

flight. 

a) The Contractor shall design develop, and verify safety or mission critical mechanisms in 

accordance with the follOWing standard: 

o NASA-STD-5017, Design and Development Requirements for Mechanisms, 

Sections 1-4 

b) The Contractor shall document the design for all CEV mechanisms as speCified In ORO CEV 

T-061, Mechanical Systems Design and Data Book, and ORO CEV-T-062' Stress AnalysIs 

Report 

c) The Contractor shall develop, Implement, and maintain an Integrated Mechanisms Master 


certifying, and acceptance of the Mechanisms system 

Deliverables 


• DRD CEV-T-061' Mechanical Systems Design and Data Book 

• DRD CEV-T-062: Stress AnalysIs Report 

The following subsystem specific information IS collected in the DRDs specified In Section 10 2 

• DRD CEV-T -015' Mechanisms Volume - Master Verification Plan 

2.6.7 Passive Thermal Control Integration 

The Contractor shall integrate the OOT&E efforts of hardware, coatings, blankets, heaters, and 

other design accommodations that protect the vehicle, crew, and ItS constituent components from 

thermal environmental extremes dUring all mission phases. 

a) The Contractor shall develop thermal analytical models to support integrated Constellation 

vehicle analyses and CEV thermal analyses. 

b) The Contractor shall develop, implement, and maintain an Passive Thermal Control 

Subsystem Master Verification Plan, per ORO CEV-T-015, that details the Contractor's plan 

for verifying, certifYing, and acceptance of the PTC system. 

c) The Contractor shall document the design for the Passive Thermal Control subsystem as 

specified in ORO CEV-T-063, Passive Thermal Control Design and Data Book. 

d) The contractor shall deliver ORO CEV-T-064, Passive Thermal Control Mathematical Models 

and Documentation, which Will edliver and desCribe the mathematical models used In the 

PTC analyses 

Deliverables 


• DRD CEV-T-063. Passive Thermal Control Design and Data Book (PTCDDB) 

• DRD CEV-T-064: Passive Thermal Control Mathematical Models and Documentation 

The following subsystem specific information is collected In the DRDs speCified in Section 10.2 

• DRO CEV-T-015 PTC Volume - Master Verification Plan 

Page 27 of 119





2.6.8 Reserved 

2.6.9 Structures Integration 

The Contractor shall integrate the DDT&E efforts of the primary structure, secondary structure, 

and all structural components of vehicle equipment, including spacecraft and component loads, 

dynamics, and stress analysis 

a) The Contractor shall perform structural analysis on all spacecraft structures, including 

pressure vessels, to show that all elements of the design such as the strength, stiffness, 

structural stability, and life meet all specified criteria for the anticipated loads and 

environments 

b) The Contractor shall perform loads and dynamics analyses and document the results In ORO 

CEV-T-067, Structural Loads Data Book 

c) The Contractor shall perform stress and fatigue analyses and document the results In ORO 

CEV-T-062, Stress Analysis Report 

d) The Contractor shall develop models to support integrated Constellation vehicle analyses as 

well as CEV loads and stress analyses The Contractor shall deliver ORO CEV-T-068, 

Structures Mathematical Models and Documentation, which will deliver and describe the 

mathematical models used In the CEV Spacecraft system, module, subsystem, and 

component loads and stress analyses. 

e) The Contractor shall implement a fracture control program and Identify fracture critical parts 

to protect against catastrophic structural hazards associated With flaw presence, fatigue crack 

propagation and fracture. The Contractor shall deliver and implement ORO CEV-T-069, 

Fracture Control Plan, and ORO CEV-T-070, Fracture Control Summary Report 

f) The Contractor shall use NASA-HDBK-7005, Dynamic Environmental Criteria, as a guidance 

document to support the ORO CEV-T-015, Master Verification Plan DRD product 

development activity. 

g) The Contractor shall use the following standards for deSigning and analYZing the structures 

subsystem: 

o Contract Attachment J-3, Table 1.2, Applicable EnVironmental Data Documents 

o JSC-62550, Structural Design and Verification Criteria for Glass, Ceramics and 

Windows in Human Space Flight Applications 

o NASA-STD-5001, Structural Design and Test Factors of Safety for Space 

Flight Hardware 

o NASA-STD-5019, Fracture Control ReqUirements for Spaceflight Hardware as 

implemented by CEV-T-069 

o NSTS 08307, Space Shuttle Criteria for Preloaded Bolts 

o CxP-70135, Structural Design and Verification Requirements (SDVR) 

h) The contractor shall produce an engineering development Ground Test Article (GTA) for use 

in enVIronmental testing. The contractor shall perform environmental testing on the 

engineering development structure including, as a minimUm, modal testing, Vibration testing, 

and acoustic testing. The contractor shall include the engineering development structure 

testing activity as part of the ORO CEV-T-015, Master Verification Plan, and shall ensure that 

the testing IS completed In time to support component qualification testing. The contractor 

shall document the results of the engineering development structure testing in ORO CEV-T- 

067, Structural Loads Data Book, and ORO CEV-T-068, Structures Mathematical Models and 

Documentation. 

I) The Contractor shall deliver a CEV Structural Test Article (used for structural verification 

static and dynamic testing) after the Contractor completes the structural test program 

J) The Contractor shall support Integrated Vehicle Ground Vibration Test (IVGVT) at MSFC as 

defined In the Ares IVGVT & Orion Bilateral Exchange Agreement (BEA) 

k) The ISS CCA will be hard mounted on a contractor provided isolation system for launch on 

Progress 

Page 28 of 119





I) The Contractor shall develop, implement, and maintain a Structures Master Verification Plan, 

per ORO CEV-T·015, that details the Contractor's plan for verifying, certifying, and 

acceptance of the Structures system. 

Deliverables 


• ORO CEV-T-062.Stress AnalysIs Report 

• ORO CEV-T-067: Structural Loads Data Book 

• ORO CEV-T-068. Structures Mathematical Models and Documentation 

• ORO CEV-T-069: Fracture Control Plan 

• ORO CEV-T-070' Fracture Control Summary Report 

• Property transfer of Structural Test Article and Ground Test Article residual components 

• 00250 of IVGVT test article 

The following subsystem speCifiC data IS collected in the ORO specified in Sections 10.2' 

• ORO CEV-T -015. Master Verification Plan 

2.6.10 Propulsion Integration 

The Contractor shall integrate the OOT&E efforts of vehicle components that prOVide propulsive 

thrust used for trajectory Insertion, orbital maneuvering, and translation and rotation reaction 

control 

a) The Contractor shall perform deSign, development, test, certification and delivery of all 

propulsion systems and develop all propulSion related ORO products. 

b) The Contractor shall develop, document, Implement, and execute comprehensive verification 

activities and associated processes for all propulsion systems in order to certify the 

propulSion systems for compliance with CEV component, subsystem, module, Spacecraft 

system, and vehicle-level requirements The Contractor shall also design, fabricate and test 

Integrated propulSion systems in order to evaluate and certify Integrated propulSion system 

hot fire performance for each propulsion application The Contractor shall also design, 

fabricate, and test integrated propulSion systems to evaluate and certify integrated propellant 

system storage and conditioning deSigns and capabilities in order to evaluate and certify 

propellant conditioning performances The Contractor shall design and certify liquid 

propellant rocket engines for combustion stability, using CPIA 655, Guidelines for 

Combustion Stability SpeCifications and Verification Procedures for Liquid Propellant Rocket 

Engines. 

c) The Contractor shall develop, Implement, and maintain a PropulSion Master Verification Plan, 

per ORO CEV-T·015, that details the Contractor's plan for verifYing, certifYing, and 

acceptance of the Propulsion system 

d) The Contractor shall document the deSign for the Propulsion subsystem as specified in ORO 

CEV·T·071, Propulsion Systems DeSign and Data Book 

Deliverables 


• ORO CEV-T-071 Propulsion Systems DeSign and Data Book 

The following subsystem specific Information IS collected In the OROs speCified In Section 10.2 

• ORO CEV-T-015 Propulsion Systems Volume - Master Verification Plan 

2.6.11 Suits, EVA and Survival Crew Equipment Support 

Systems Integration 

a) The Contractor shall Integrate the OOT&E efforts of components that interface to Suits, EVA 

and Survival Crew EqUipment Support Systems. 

Page 29 of 119





b) NASA will provide the CEV suits and EVA support equipment (e g., EVA suits, launch and 

entry suits, helmets, gloves, undergarments, and standard EVA tools if applicable). 

c) NASA will provide crew equipment systems and gear for emergency egress and survival, 

crew/personnel post landing tracking systems, and crew/personnel post landing 

communications systems 

d) The Contractor shall perform requirements development, design, analysis and trade studies, 

assembly/production, integration, testing, verification, validation, qualification, certification, 

and delivery of the CEV Interfaces for the NASA-provided suits, EVA support equipment, and 

survival crew equipment 

e) The Contractor shall supply the vehicle resources to the NASA-provided SUitS with power, 

oxygen, water, cooling, contaminant control and communications as defined in the CXP- 

70033, Orion to EVA Systems IRD. The Contractor shall control/provide/analyze the vehicle 

side interface, and NASA Will control/provide the umbilical/support systems hardware and the 

suit-side interface 

e) The Contractor shall supply vehicle resources and Interfaces for vehicle depressurization/repressurization 

as defined In support of an EVA. 

f) The Contractor shall provide an IVA/EVA-operable CEV Spacecraft hatch and mechanisms, 

specialized CEV-speclflc EVA tools, and external deVices, restraints, and mobility aids 

g) The Contractor shall use the human engineering standards listed in section 2.8.7, Human 

Engineering, to design all interfaces to SUitS, EVA, and survival crew eqUipment systems. 

h) The contractor shall proVide EVA handling aids mounted to the exterior of the ISS CCA to 

support installation, activation, and check out 

i) RESERVED 

j) The Contractor shall develop, Implement, and maintain a SUitS, EVA, and Survival Crew 

Equipment Master Verification Plan, per ORO CEV-T-015, that details the Contractor's plan 

for verifying, certifying, and acceptance of theSUlte, EVA, and Survival Crew EqUipment 

Support Systems 

k) The Contractor shall document the deSign for the SUitS, EVA, and SurVival Crew EqUipment 

Support Systems as specified in ORO CEV-T-072, SUitS, EVA, and Survival Crew EqUipment 

Support Systems DeSign and Data Book 

Deliverables 


• DRD CEV-T-072' Suits, EVA and Survival Crew EqUipment Support Systems DeSign and 

Data Book 

The following subsystem speCifiC Information IS collected In the DRDs specified in Section 10.2 

• DRD CEV-T-015 SUitS, EVA, and Survival Crew Equipment Support Systems Volume 

Master Verification Plan 

2.6.12 Environmental Control and Life Support (ECLS), Crew 

Health and Habitation Accommodations Integration 

The Contractor shall integrate the DDT&E efforts of the spacecraft subsystems for EnVironmental 

Control and Life Support (EClS), active thermal control, medical systems Interfaces, and 

habitation accommodations. 

a) NASA will provide food and food packaging The Contractor shall deSign the Interfaces for 

these NASA-provided Items. 

b) NASA will provide portable medical kits, equipment and supplies, and portable 

countermeasures systems The Contractor shall deSign the Interfaces for these NASAproVided 

Items. 

c) NASA Will prOVide additional FCE such as personal hygiene kitS, hygiene consumables, sleep 

restraints, portable supplemental lighting, portable vacuum cleaner, dust abatement system, 

disposable wipes, personal carry-on stowage, standard tools, crew clothing, and portable 

crew personal Items (e g , relaxation and entertainment systems) The Contractor shall 

Page 30 of 119





design the interfaces for these NASA-provided Items In accordance with the following 

document 

o CXP-70035, Portable Equipment, Payloads, and Cargo IRD 

d) NASA will provide active and passive radiation instrumentation. The Contractor shall design 

the Interfaces for these NASA-provided Items 

e) The Contractor shall use the follOWing EClS, crew health and habitation accommodations 

standards and the Human Engineering Standards listed in Section 2 8.7, Human 

Engineering, for designing this subsystem: 

o JSC 20584, Spacecraft Maximum Allowable Concentrations for Airborne 

Contaminants 

f) The Contractor shall provide definition of the process to be used for cleanliness of 

components for use in oxygen, fuel, and pneumatic systems. The Contractor shall provide 

this information In ORO CEV-T-073, Environmental Control and Life Support Design and Data 

Book. The process must meet or exceed the requirements identified in the following 

documents' 

o 

o 

o 

o 

MSFC-SPEC-164B, Specification for Cleanliness of Components for Use in 

Oxygen, Fuel and Pneumatic Systems (and associated Children documents as 

specified In Attachment J-3, Applicable, Guidance, and Informational 

Documents list) 

MSFC-PROC-404, Gases, Drying and Preservation, Cleanliness level and 

Inspection 

MSFC-PROC-1831, The Analysis of Nonvolatile Residue Content 

MSFC-PROC-1832, Sampling and Analysis of Nonvolatile ReSidue Content 

on Critical Surfaces 

g) The Contractor shall identify the standard for test methods for environmental engineering In 

ORO CEV-T-073, Environmental Control and Life Support Design and Data Book. This 

standard shall meet or exceed the follOWing standard' 

o 

Mll-STD-810F, DOD Test Method Standard for Environmental Engineering 

ConSiderations and laboratory Tests, Section 5 and Part 2 

h) The Contractor shall develop, Implement, and maintain an EClS Master Verification Plan, per 

ORO CEV-T-015, that details the Contractor's plan for verifying, certifying, and acceptance of 

the EClS system. 

i) The Contractor shall document the design for the Habitation Accommodations as specified in 

ORO CEV-T-074, Habitation Accommodations DeSign and Data Book 

Deliverables 

The Contractor shall deliver and maintain the following document(s): 

• DRD CEV-T-073. Environmental Control and life Support Design and Data Book 

• DRD CEV-T-074 Habitation Accommodations DeSign and Data Book 

The following subsystem specific information IS collected In the DRDs specified in Section 10.2 

• DRD CEV-T-015 EClS Volume - Master Verification Plan 

2.6.13 Pyrotechnics Integration 

The Contractor shall integrate all CEV mounted deVices and assemblies containing or 

operated/actuated/severed by, propellants and/or explOSives 

a) NASA will supply the pyrotechniC Initiators for all pyrotechniC events excluding mechanically 

initiated devices NASA will supply interface and performance requirements for the system 

used to fire the Initiators 

b) If the Contractor selects existing Shuttle pyrotechnic deVices for the CEV Spacecraft, then 

NASA will supply those pyrotechniC deVices 

c) NASA will supply pyrotechniC reefing line cutters used In the CPAS. 

d) The Contractor shall comply With all requirements In JSC 62809, Constellation Spacecraft 

PyrotechniC Specification and JPR 8080.5 Standards P1-P7 

Page 31 of119





e) The Contractor shall perform preliminary design reviews and critical design reviews for each 

pyrotechnic device not provided by NASA. The Contractor shall conduct development, 

qualification, and acceptance testing on all other pyrotechnic devices selected for the CEV 

Spacecraft. The Contractor shall conduct Phase I, Phase II, and Phase III technical reviews 

on all other pyrotechnic devices selected for the CEV Spacecraft per the requirements of JSC 

62809, Constellation Spacecraft Pyrotechnic Specification 

f) The Contractor shall perform stress analysis and deliver stress analYSIS reports (ORO CEV-T- 

062, Stress Analysis Report) on all pyrotechniC devices selected for the CEV Spacecraft 

g) The Contractor shall develop, Implement, and maintain an PyrotechniCS System Master 


certifying, and acceptance of the pyrotechniCS system 

h) The Contractor shall use the follOWing standards for designing the pyrotechnics subsystem. 

o AFJMAN 24-204, Preparing Hazardous Materials for Military Air Shipments 

o 

o 

AFCPCMAN 91-710 Eastern and Western Range Safety User Requirements 

FED-STD-H28/20, Screw - Thread Standards for Federal Services Revision A 

or Later Inspection Section 20 Methods for Acceptability of UN, UNR, UNJ, M, 

and MJ Screw Threads 

o JSC 20431, NASA JSC Neutron Radiography Specification 

o JSC 62809, Constellation Spacecraft PyrotechniC SpeCification for Production 

Flight tests 

o JSC/SKD 26100132, Performance SpeCification for NSTS Use of Percussion 

Primers 

o NASA-STD-8739.3 Soldered Electncal Connections 

o MIL-DTL-398, RDX (Cyclotrimethylenetrinitramine) 

o MIL-DTL-45444, HMX (Cyclotetramethylenetetranltramlne) 

o MIL-L-3055, Type I Lead Azide 

o MIL-L-46225, Lead Azide RD-1333 

o MIL-P-20444C, Primer, PerCUSSion, M42 Parts for and Loading, Assembling 

and Packaging 

o MIL-P-387, Pentaerythnte Tetranltrate (PETN) 

o JPR 8080.5 Standards P1-P7 

o MIL-STD-286, Military Standard Propellants, Solid: Sampling Examination and 

Testing; Method 8021 

o MIL-STD-810, EnVironmental Test Methods and Englneenng GUidelines 

o MIL-STD-2073-1, Department of Defense Standard Practice for Packaging 

o WS 5003F, Matenal SpeCification for HNS Explosive 

I) The Contractor shall Identify their standards for deSigning the pyrotechnics subsystem, in the 

follOWing areas ThiS standard shall meet or exceed the following standards: 

o AIA/NAS NASM20995, Wire, Safety or Lock 

o ANSI/ASOC Z1 4, Sampling Procedures and Tables for Inspection by 

Attributes 

o ANSI/NCSL Z450-1, Calibration Laboratones and Measunng and Test 

EqUipment - General Requirements 

o ASME B46.1, Surface Roughness, Waviness and Lav 

o ASTM E1742, Standard Practice for Radiographic Examination 

o ASTM E8, Standard Test Methods of Tension Testing of Metallic Materials 

o DOD 4145 26-M, DOD Contractors' Safety Manual for AmmUnition and 

ExplOSives 

o MIL-P-116, Preservation, Methods of 

o MIL-STD-2073-1, Department of Defense Standard Practice for Packaging 

o MIL-S-22473, Sealing, Locking and Retaining Compounds, Single Component 

o MS20003, Indicator, Humidity, Card, Three Spot, Impregnated Areas 

J) The Contractor shall document the deSign for the Pyrotechnics Integration as specified in 

ORO CEV-T-075, PyrotechniCS Subsystem DeSign and Data Book. 

Page 32 of 119





Deliverables 


• DRD CEV-T-062: Stress AnalysIs Report 

• DRD CEV-T-075 Pyrotechnics Subsystem Design and Data Book 

The following subsystem specific Information IS collected in the DRDs specified in Section 10 2 

• DRD CEV-T -015' Pyrotechnics Volume - Master Verification Plan 


2.6.15 Guidance, Navigation, and Control (GN&C) Integration 

The Contractor shall integrate the DDT&E efforts of the Guidance, Navigation, and Control 

(GN&C) subsystem including the Integrated CEV Flight Dynamics design. 

a) The CEV GN&C requirements design and functional venflcation effort will be performed 

through the use of specialized mode teams NASA and the Contractor will co-lead the 

development of detailed design requirements for the CEV GN&C flight system. The 

Contractor shall document the GN&C requirements in ORO CEV-T-031, CEV GN&C 

Subsystem Requirements Specification, and ORO CEV-T-048, Software Requirements 

Specification The Contractor shall provide support to the following teams' 

o CEV Ascent/Abort Mode Team 

o Entry GN&C Mode Team 

o On-Orbit GN&C Mode Team 

o Flight Mechanics/MIssion Design Mode Team 

b) NASA will perform independent requirements validation and design certification in key areas. 

In these key areas NASA Will establish design requirements teams intended to integrate the 

activities of NASA and the Contractor. The Contractor shall partiCipate in and support these 

design requirements teams for GN&C Flight Software 

c) The Contractor shall develop, implement, and maintain an GN&C System Master Verification 

Plan, per ORO CEV-T-015, that details the Contractor's plan for verifying, certifying, and 

acceptance of the GN&C system 

d) The Contractor shall document the design for the GN&C subsystem as specified in ORO 

CEV-T-078, GN&C Subsystem Design and Data Book. 

Deliverables 


• DRD CEV-T-078' GN&C Design and Data Book 

The follOWing subsystem speCifiC information IS collected In the DRDs specifice in Section 6.1.2 

• DRD CEV-T-031 GN&C Requirements Specification 

• DRD CEV-T-031 GN&C Requirements SpeCification 

The following subsystem specific information is colledted in the DRD speCified In Section 6.5.2 

• DRD CEV-T-048' Software Requirements Specidfication 

The following subsystem specifiC Information IS collected In the DRDs speCified in Section 10.2 

• DRD CEV-T -015 GN&C Volume - Master Verification Plan 

2.6.16 Wiring Integration 

The Contractor shall integrate the DDT&E efforts of the wIring harnesses and optical cabling for 

both electncal and optical Signals and proVides the power, data, and command paths, 

connections, production breaks, and access points required to develop, assemble, test, operate, 

verify, certify, service and safeguard the CEV Spacecraft throughout ItS life cycle 

Page 33 of 119





a) The Contractor shall develop and document the process for defining, fabricating, testing, 

routing, installing, verifying, and maintaining the CEV wiring subsystem throughout the life 

cycle, including vehicle modifications, upgrades, and discrepancy resolution ThiS process 

shall be documented in the ORO CEV-T-079, CEV Wiring Plan. 

b) The Contractor shall develop a wiring database that provides definition down to the level of 

Pln-to-pin connectivity for all electrical harnesses and optical cables used on the CEV for 

ground, launch, flight, and recovery operations including testing, verification, calibration, and 

maintenance The Contractor shall deliver the wIring database to NASA as ORO CEV-T-OBO, 

CEV Wiring Database and Reports 

c) The Contractor shall develop, implement, and maintain a Wiring Master Verification Plan, per 

ORO CEV-T-015, that details the Contractor's plan for verifYing, certifYing, and acceptance of 

the wIring system. 

Deliverables 


• DRD CEV-T-079. CEVWiring Plan 

• DRD CEV-T -080: CEV Wiring Database and Reports 

The follOWing subsystem specific information IS collected In the DRDs specified In Section 10 2 

• DRD CEV-T-015: Wiring Volume - Master Verification Plan 

2.7 Flight and Ground Operations Integration 

CEV Operations is a NASA-led function With the Contractor providing the necessary data 

products, operational requirements, and support for NASA to develop the plans, processes, 

procedures, and tools to operate the CEV System. Operations Includes the development and 

Implementation of the processes, plans, system requirements, support and reference documents, 

training, procedures, and work associated With the preparation, launch and flight execution, and 

recovery of the CEV spacecraft. The scope of operations Includes use of the CEV System 

hardware/software after delivery to NASA in support of the preparation and execution of the Ares- 

1Y, Orion-1 and Orlon-2 operational flights. 

The two prinCiple areas of operations are ground operations and flight operations Ground 

operations are activities associated with the processing of the flight hardware using ground 

systems for the launch and post-landing operations These actiVities Include the planning, prelaunch 

processing, launch, and post-landing operations. Flight operations are activities performed 

to support the spacecraft and crew to accomplish the mission objectives The scope of flight 

operations includes the early preflight analyses and design, flight planning, flight product and 

procedure development, flight training, and flight execution by the crew and mission operations. 

2.7.1 Operational Analysis Supporting Design 

a) The Contractor shall participate With Constellation Operations In the development of 

operations plans involVing multiple systems across the Constellation Program. 

b) The Contractor shall provide a concept of operations for the CEV in accordance with ORO 

CEV-O-001, Contractor's CEV Concept of Operations, uSing ANSI/AIAA-G043-1992, 

GUidance for the Preparation of Operational Concept Documents, paragraph 4.0 and 

Appendix A, as guidance documents 

c) The Contractor shall perform and update operational analyses using operations requirements 

analYSIS and operations assessment analysiS processes for Implementation per SOW 

Sections 2 4, Integrated Analysis, 2 3 (a), CEV to Constellation Program Integration, and 2.3 

(b), CEV to ISS Program Integration in accordance With ORO CEV-T-010, System 

Performance Analysis Report, to ensure a balance of cost, schedule and risk between 

spacecraft design and ground and flight infrastructure needed to accomplish the operational 

mission These operational analyses Will produce an "operational view" that describes how 

Page 34 of 119





the system products serve the operators (e.g. flight crew, ground operations, and flight 

operations) The Contractor shall provide operational analyses that establish lifecycle 

operation and support requirements for the system. These operational analyses shall be 

sufficient for use by NASA to determine how best to provide operational support, determine 

under what environmental conditions the system products may be used, and how well they 

may perform under anticipated conditions The Contractor shall incorporate the applicable 

human-to-machine interface considerations for ground processing from the CXP-70024, 

Constellation Human System Integration Requirements (HSIR) and associated Children 

documents as specified in Attachment J-3, Applicable, Guidance, and Informational 

Documents List) Example subjects for operational analyses include: 

o Reduction and consolidation of flight-to-ground Interface pOints In addition to 

flight-element to flight-element interfaces; 

o Use of common/consistent fasteners, connectors, and 

consumables/propellants; 

o Use of non-toxIc consumables, 

o Design of Line Replaceable Units (LRUs) that allows for removal, replacement 

and retest throughout the ground processing flow; 

o 

o 

o 

Use of design that allows for in-space maintenance; 

Minimize operational constraints on vehicle in-space attitudes caused by 

design limitations In such systems as commUniCations, thermal, or power 

system, and 

DeSign of flight software architecture for less costly maintenance and 

certification following updates 

Deliverables 


• DRD CEV-O-001 : Contractor's CEV Concept of Operations 

The following Operational Analysis specific data is collected in the DRD specified in Section 2.4 

• DRD CEV-T-010: System Performance AnalysIs Report 

2.7.2 Ground Operations Integration 

Ground Operations will be the responsibility of the NASA, however, it is essential that the 

Contractor participate with NASA in the overall planning and implementation of ground 

operations 

Ground Operations Integration Includes efforts reqUired to prOVide (1) plans for CEV stand-alone 

ground operations where the activities involve the CEV system and (2) requirements for 

integrated ground operations where the activities Involve the spacecraft With other Constellation 

flight elements. It also Includes tasks to develop concepts, requirements and plans for 

maintenance and logistics for CEV Project supportability for operations. These activities are 

generally performed in cooperation with the CxP Ground Operations Project. 

a) The Contractor shall develop, Implement and update ORO CEV-T-011, Integrated Logistics 

Support Plan, using the CXP-70064, Constellation Program Supportability Plan as 

informational. 

b) The Contractor shall perform a Logistics Support Analysis (ORO CEV-T-012) in accordance 

with the ORO CEV-T-011, Integrated Logistics Support Plan. 

c) The Contractor shall perform iterative design evaluations utiliZing the results of on-going 

reliability, maintainability, and supportability assessments to Identify logistiCS impacts and 

apply these evaluations to the deSign of the system In order to minimize the Identified 

logistics impacts 

d) The Contractor Will prOVide initial flight spares per Sections 2.10 CEV Assembly, Integration, 

and Production, 6 1 3 CM Flight Spares, 6 2 3 SM/SA Flight Spares, 6 4.3 LAS Flight Spares; 

initial ground support equipment spares per Section 2.7.2(e), Ground Support Equipment, 

and planning for storage of spares per Section 2.7.2 (b), Storage. The Contractor shall 

Page 35 of 119





participate in the Government-sponsored Provisioning Guidance Conference and lead CEV 

Provisioning Conferences 

e) The Contractor shall develop and maintain a launch site forecast of CEV propellants, fluids, 

and gases for the CEV Project life cycle per ORO CEV-T-013, Launch Site CEV Propellants, 

Fluids, and Gases Forecast 

f) The Contractor shall provide and maintain data to support a Logistics Management System 

(LMS) for the tracking and management of equipment, spares, repair parts, supplies, 

material, and shipping containers, and Identify excess or obsolete assets and initiate 

disposal. The LMS applies to both ground-based and space-stored assets. 

g) The Contractor shall develop the capability within the CEV spacecraft to Interface/utilize the 

LMS for on-board inventory management. 

h) The Contractor shall deliver all supportability data developed and acqUired for the deSign and 

manufacturing of CEV spacecraft to support flight hardware and Ground Support Equipment 

(GSE) reprocurement, remanufacturing, refurbishment, failure analysis, and repair In 

accordance with ORO CEV-T-014, Supportability Data Package 

I) The Contractor shall name CEV spacecraft components, assemblies, data products, 

applications and operations consistently In accordance with CXP-02007, Constellation 

Nomenclature Plan 

j) The Contractor shall test (acceptance test only) and deliver flight spares. The Contractor 

shall provide a spare parts list as part of the ORO CEV-T-012, Logistics Support Analysis 

(Recommended Spare Parts List). (lOIQ) 

k) The Contractor shall deliver one ship set of}lIght spares (Le., 1 copy of every line replaceable 

unit) (IOIQ) 

I) The Contractor shall support NASA ground operations in the development of a CEV ground 

operations plan addressing pre-launch processing, launch operations, and post-landing 

operations to ensure that ground operations activities are appropriately planned and 

implemented. Examples of Contractor support to NASA ground operations Include: provide 

flight and ground design data, provide technical assistance to the system integrated testing 

approach, identify support requirements for vehicle processing, provide technical expertise 

during the operations reviews, and prOVide work force resource loading forecasts for ground 

operations activities involVing Contractor-provided hardware and software. (IOIQ) 

m) The Contractor shall develop and update the flight hardware/software operations and 

maintenance plans and requirements for ground operations in accordance With ORO CEV-O- 

002, Flight Hardware/Software Operations and Maintenance ReqUIrements Development 

Plan and Requirements Document. The Contractor shall coordinate flight hardware/software 

operations and maintenance plans and requirements development With NASA. 

n) The Contractor shall provide flight and ground hardware/software technical assistance dUring 

ground operations phases to support ground operations activities, ensure operations and 

maintenance requirements Implementation, assist in element-to-element Integrated testing, 

assist in flight hardware/software corrective action disposition, ensure consistent, clear 

commUnications between the Contractor and NASA ground operations, and provide an 

advocate between the ground operations organizations and the spacecraft deSigners. (IOIQ) 

0) NASA will implement the requirements as defined In the ORO CEV-O-002, Flight 

Hardware/Software Operations and Maintenance Requirements Development Plan and 

Requirements Document, during ground operations. The Contractor shall assess and 

provide recommendations regarding changes to the NASA-developed ground operations 

procedures to assure that the changes are consistent With the CEV Spacecraft and GSE 

requirements, constraints, and capabilities (IOIQ) 

p) For work that IS to be accomplished by the Contractor at either KSC or CCAFS, the 

Contractor shall develop and update the support requirements In compliance With KSC-HB 

GP60-3 ASRS Handbook and In accordance With ORO CEV-O-003, Launch Site Support 

Requirements Documentation. 

Deliverables 


Page 36 of 119





• DRD CEV-O-002: Flight Hardware/Software Operations and Maintenance Requirements 

Development Plan and Requirements Document 

• DRD CEV-O-003· Launch Site Support Requirements Documentation 

• DRD CEV-T-011. Integrated Logistics Support Plan 

• DRD CEV-T -012· Logistics Support AnalysIs 

• DRD CEV-T-012: Logistics Support AnalysIs (Recommended Spare Parts List). (IDIQ) 

• DRD CEV-T-013 Launch Site CEV Propellants, Fluids, and Gases Forecast 

• DRD CEV-T-014· Supportability Data Package 

2.7. 2. (a) Facilities and Facility Systems 

The ground facilities and facility systems encompass processing facilities, control rooms, landing 

and recovery facility systems and other monitoring systems. 

a) The Contractor shall develop and update end Item-level requirements in accordance with 

ORO CEV-O-008, Ground Systems Requirements, Plans, Reports, and Design Data, Volume 

I, Ground Systems End Item Requirements Document and Report 

b) The Contractor shall support NASA In the requirements development; and In the design, 

development, modification, and implementation activities for the facilities and facility systems 

that will be provided by NASA. Examples of Contractor support Include. prOVide flight 

hardware/software Interface deSign and data, participate In the deSign reViews, working 

groups, and technical Interchange meetings; ensure Contractor requirements are 

implemented appropriately; and participate In the activation and verification of NASA provided 

faCilities and faCility systems (IDIQ) 

Deliverables 


• DRD CEV-O-008 Ground Systems Requirements, Plans, Reports and DeSign Data 

• DRD CEV-O-007. Range Safety Requirements Documents 

2. 7. 2. (b) Storage 

Ground Systems Storage includes the development of requirements for storage facilities for flight 

and ground systems and logistical spares proVided by the CEV Contractor 

a) The Contractor shall develop the requirements for the storage of Contractor-provided flight 

hardware and logistical spares In accordance With ORO CEV-O-002, Flight 

Hardware/Software Operations and Maintenance Requirements Development Plan and 

Requirements Document. 

b) The Contractor shall develop the requirements for the storage of Contractor-provided ground 

systems and logistical spares In accordance With ORO CEV-O-008, Ground Systems 

Requirements, Plans, Reports, and Design Data, Volume I, Ground Systems End Item 

Requirements Document and Report 

Deliverables 


• DRD CEV-O-002 Flight Hardware/Software Operations and Maintenance Requirements 

Development Plan and ReqUirements Document 

• DRD CEV-O-008 Ground Systems ReqUirements, Plans, Reports and Design Data 

Volume I, Ground Systems End Item ReqUirements Document and Report 

Page 37 of 119





2. 7. 2. (c) Transportation 

a) The Contractor shall perform the planning and implementation for government furnished 

transportation support of CEV spacecraft element or equipment other than that provided in 

Section 2 10 The Contractor shall work With the appropriate NASA Ground Operations 

organizations to coordinate the Implementation of government furnished transportation of 

CEVelements and equipment. These plans shall be included in ORO CEV-T-087 CEV 

Spacecraft Handling and Transportation Plan 

b) The Contractor shall develop and Implement plans detailing the design and construction of all 

CEV transportation support equipment, and the plans for transportation of the CEV 

Spacecraft elements to and from Government Furnished transportation locations, test faCility 

locations, processing Sites, and/or launch/landing sites. These plans shall be included in ORO 

CEV-T-087, CEV Spacecraft Handling and Transportation Plan 

Deliverables 


• ORO CEV-T-087. CEV Spacecraft Handling and Transportation Plan 

2. 7. 2. (d) CEV Ground and Training Systems 

Ground Systems Include facilities, faCIlity systems, and support equipment hardware and 

software required for ground and flight operations NASA will provide all ground systems 

faCilities, faCIlity systems, and a portion of the support equipment 

Training Systems include facilities, hardware and software to support ground and flight operations 

training. 

NASA operations Will develop the training products and conduct the operations training and 

certification for ground and flight operations 

a) For ground operations, the Contractor shall provide support for NASA development of training 

materials Examples of Contractor support Include' proVide technical assistance In flight 

hardware processing, handling, and safety considerations; and provide an advocate between 

the ground operations' training organization and the spacecraft designers (1010) 

2.7. 2. (e) Integrated Ground Support Equipment 

Ground Support EqUipment (GSE) Includes hardware and software needed for ground 

operations 

a) The Contractor shall support NASA In developing the allocation list of GSE to be provided by 

the Contractor The allocation list Will Include GSE end Items required to support SOW 

Sections 6 5, CEV Software, 10.3 Integrated Test and Verification, 2.7.2, Ground Operations 

Integration, and 10.6, Flight Test. The Contractor shall Identify all Contractor-provided GSE 

In Attachment J-9, Deliverable Items LISt. The NASA-provided GSE deSCribed In Attachment 

J-11, Government Furnished Property LiSt, Will be delivered to NASA ground operations for 

the RRF and operational flights. Contractor use of the NASA-provided equipment Will be 

determined during the allocation list development Examples of the types of GSE to be 

provided by the Contractor include. 

o lifting DeVices - Contractor to proVide lifting slings and adapters from Hydraset 

down to spacecraft elements/components 

o Fluid and Gases Servicing Systems - Contractor to prOVide spacecraft 

Interfacing connections 

Page 38 of 119





o 

o 

o 

o 

o 

Command, Control and Monitoring System - Contractor to provide CEV 

standalone Command, Control and Monitoring System 

Facility Infrastructure Systems - Contractor to provide spacecraft specialty 

systems (Spacecraft specific special electrical power supplies, data handling, 

etc.) 

Access stands - Contractor to provide internal access equipment 

Special tools - Contractor to provide spacecraft specific special tools and 

ancillary equipment (LRU Installation and removal devices and tools, inspection 

tools, ) 

Special Test equipment - Contractor to provide special test equipment (Cabin 

Leak test equipment, Data bus test equipment, etc.) 

b) The Contractor shall develop and update the GSE Specification In accordance with ORO 

CEV-T-031, CEV Requirements Specification, for Contractor-provided GSE. The 

Contractor shall ensure that the GSE Specification IS consistent with ORO CEV-O-001, 

Contractor's CEV Concept of Operations and balances performance, life-cycle cost, 

schedule, and risk The Contractor shall develop and update the ORO CEV-T-035, Internal 

Interface Requirements Document, for all interfaces with flight hardware, NASA and 

Contractor-provided GSE, facility systems, and faCilities. The Contractor shall develop and 

update the ORO CEV-T-029, Interface Control Document, for all interfaces with flight 

hardware, NASA and Contractor-provided GSE, faCility systems, and facilities. 

c) The Contractor shall develop and update the contractor provided GSE end Item-level 

requirements in accordance With ORO CEV-T-031, CEV Requirements 

Spaciflcatlons and CEV ReqUirements Specifications. The Contractor 

shall use the follOWing applicable documents 

o 

NASA-STD-5005S' NASA Standard for Ground Support EqUipment (and 

assOCiated Applicable Document Children as specified in Attachment J-3, 

Applicable, GUidance, and Informational Documents List). 

d) The Contractor shall develop and update the NASA provided GSE end Item-level 

requirements in accordance With ORO CEV-O-008, Ground Systems Requirements, Plans, 

Reports, and DeSign Data, Volume I, Ground Systems End Item ReqUirements Document 

and Report The Contractor shall use the follOWing applicable documents: 

o 

NASA-STD-5005S: NASA Standard for Ground Support EqUipment (and 

associated Applicable Document Children as specified in Attachment J-3, 

Applicable, Guidance, and Informational Documents List). 

e) The Contractor shall design, develop, produce, Integrate, verify, validate, certify, document, 

and deliver Integrated CEV GSE in accordance With all requirements In CXP-72000, Systems 

ReqUirements for the Crew Exploration Vehicle Element (CEV SRD), and In this SOW, and in 

accordance With ORO CEV-O-008, Ground Systems Requirements, Plans, Reports, and 

Design Data, Volume II, Ground Systems End Item Implementation Plan and Report. The 

Contractor shall provide common GSE for use dUring multiple phases including 

manufactUring, transport, processing, operations, and integration. The Contractor shall 

provide a common CM handling and transportation fixture The Contractor shall assess 

existing material eqUipment lists for eXisting programs for any GSE hardware Items that can 

be used for CEV. The Contractor shall plan for and deliver the GSE end Items 90 days prior 

to first need date. The Contractor shall use the follOWing applicable documents for deSign 

and development of Contractor-provided GSE: 

o 

NASA-STD-5005S' NASA Standard for Ground Support Equipment (and 

assOCiated Applicable Document Children as speCified In Attachment J-3, 

Applicable, GUidance, and Informational Documents List) 

f) The Contractor shall support NASA In the reqUirements development, deSign, modification, 

and implementation activities for the GSE that will be provided by NASA. Examples of 

Contractor support include proVide flight hardware/software Interface design and data; 

participate in design reViews, working groups, and technical interchange meetings; ensure 

Contractor requirements are Implemented appropriately; and participate In the test and 

verification of the NASA-provided GSE. (IDIO) 

Page 39 of 119





g) The Contractor shall develop and update ORO CEV-O-008, Ground Systems Requirements, 

Plans, Reports, and DeSign Data, Volume IV, Ground Systems Sustaining Engineering Plan, 

for the Contractor-provided GSE. 

h) NASA will perform the GSE sustaining engineering activities The Contractor shall support 

NASA sustaining engineering activities Examples of Contractor support Include' prOVide 

engineering support for problem resolution including Material Review Board (MRB) Items; 

provide engineering review and analYSIS of proposed upgrades and modifications; review 

FMEA-CIL and hazard analysis identified critical items for mitigation or elimination, and 

prOVide an advocate between the ground operations organizations and the GSE designers. 

(IDIO) 

i) The Contractor shall develop and deliver ORO CEV-T-040, Acceptance Data Package, for 

each Contractor-provided GSE end item. 

j) The Contractor shall provide initial spares, concurrent with the delivery of the GSE end items 

and in accordance With the provIsioning procedures In ORO CEV-T-011, Integrated Logistics 

Support Plan, and ORO CEV-T·012, Logistics Support AnalYSIS, for all Contractor-provided 

GSE. (IDIO) 

k) The Contractor shall complete the DD-250 for the Contractor-provided GSE and deliver the 

Contractor-provided GSE to the NASA-deSignated faCIlities 

I) The Contractor shall develop and update 2-D and 3-D Simulation models of the ContractorprOVided 

spacecraft and Contractor-provided GSE to assess clearances, placement, conflicts 

and the moving of hardware In accordance With ORO CEV-T-003, CEV CAD Models. The 

Contractor shall develop and deliver these models In accordance With SOW Section 2 4 

m) The Contractor shall develop, implement, and maintain an GSE Master Verification Plan, per 

ORO CEV-T-015, that details the Contractor's plan for verifYing, certifYing, and acceptance of 

GSE system. 

n) The Contractor shall develop and maintain ORO CEV-T·032, CEV SpeCification and Drawing 

Trees for GSE. 

Deliverables 


• DRD CEV-O-008 Ground Systems Requirements, Plans, Reports, and DeSign Data 

• DRD-CEV-T-029. GSE Interface Control Documents 

• DRD-CEV-T-031' GSE Requirements SpeCification 

• DRD-CEV-T-031 GSE ReqUirements Specification 

• DRD-CEV-T-031. GSE ReqUirements SpeCification 

• DRD CEV-T-032 GSE SpeCification and DraWing Tree 

• DRD-CEV-T-035' GSE Intererface requiremetns Document 

• DRD-CEV-T-040' Acceptanc Data Package 

The following GSE data is incorporated in the DRD speCified In Section 24' 

• DRD CEV-T-003' CEV CAD Models 

The following GSE specifiC Information IS collected In the DRDs specified in Section 10 2. 

• DRD CEV-T -015: GSE Volume Master Verification Plan 

2.7.3 Flight Operations Integration 

Flight Operations include the plans, processes, schedules, and products required to perform the 

flight design, analyses, and flight planning actiVities, flight products and procedure development; 

and execution of Ares 1-Y, Orion 1, and Orion 2 operational flights. Flight operations Will be the 

responsibility of NASA, however, it is essential that the Contractor provide the data and support to 

NASA for the development of the flight operations products to prepare for and execute the CEV 

missions. 

Page 40 of 119





2.7.3.(a) 

Flight Operations Preparation 

Flight Operations Preparation is the development of the pre-flight plans, processes, schedules, 

flight design and analyses, flight plans, procedures, and support products necessary to prepare 

for the CEV mission execution The culmination of these activities will produce a complete, 

Integrated set of operations products and procedures necessary to execute a CEV mission. 

A single authoritative source of vehicle deSign and performance data IS reqUired to develop, 

produce, and Implement the flight deSign process, trade studies, analyses, simulations, and flight 

products and procedures 

a) The Contractor shall develop and update vehicle systems, flight deSign, and analysis data for 

the CEV spacecraft In accordance with ORO CEV-O-004, CEV Operations Data Book, 

a Volume I. CEV Spacecraft Systems Performance and Constraints Data 

a Volume II. CEV Spacecraft Systems Electrical EqUipment List 

a Volume III CEV Mission Mass Properties Data 

a Volume IV. CEV Spacecraft Systems Contingency AnalysIs Data 

a Volume V: CEV Aerodynamic and Astrodynamic Performance and Constraints 

Data 

a Volume VI: CEV Crew Module Landing and Emergency Rescue Data 

a Volume VII' CEV Flight Capability Envelopes 

a Volume VIII: CEV Ascent, Entry, and On-orbit Structural Envelopes 

b) The Contractor shall develop the Initial procedures inputs in accordance with ORO CEV-O- 

005, Flight Operations Procedures Data These provide nominal operations, maintenance, 

and nominal/off-nominal time critical response CEV spacecraft procedure inputs. 

c) The Contractor shall develop the CEV stowage procedures, and supporting documentation In 

accordance with ORO CEV-O-006, CEV Stowage CapabIlities and Services Handbook. 

d) The Contractor shall prOVide support to the NASA flight operation's systems, flight planning 

and cargo integration, and flight deSign and analysIs disciplines The Contractor shall ensure 

consistent, clear communications between the Contractor and NASA flight operations, and 

shall research and disseminate the necessary data and technical information from the 

spacecraft designers for NASA to develop ItS flight products Examples of Contractor 

support to NASA flight operations include' provide technical assistance dUring NASA's 

development of the flight crew and flight controller procedures, flight rules, flight plans, 

system briefs, reference products, flight design and analysis tools, system analysIs tools, 

telemetry parameter selection, displays necessary to prepare for and execute CEV flight 

operations, and prOVide an advocate between the flight operations organizations and the 

spacecraft designers (1010) 

e) The Contractor shall assess and prOVide recommendations regarding flight rule change 

requests and procedures change requests to assure that changes are consistent with CEV 

spacecraft requirements, constraints, and capabilities. (1010) 

Deliverables 


• ORO CEV-O-004: CEV Operations Data Book 

• ORO CEV-O-005' Flight Operations Procedures Data 

• ORO CEV-O-006' CEV Stowage Capabilities and Services Handbook 

2. 7.3. (b) Flight Operations Execution (IDIQ) 

Flight Operations Execution encompasses real-time support for all phases of mission operations 

beginning with pre-launch activities through post-landing egress of the flight crew It IS the 

culmination of all of the earlier pre-flight flight deSign, mission planning, training, and ground 

operations activities. 

Page 41 of119





a) The Contractor shall provide support dUring the execution of the CEV missions using the 

Contractor personnel supporting the NASA flight operation's systems, flight planning and 

cargo integration, flight design and analysis, and training disciplines. 

b) The Contractor shall provide engineering support dUring flight execution to provide technical 

Information, Interpret systems health data, and perform In-depth analysis in response to 

anomalous spacecraft conditions The Contractor shall support the NASA CEV SUb-system 

managers 

2.7.4 Range Safety Integration 

Test and operational flights of the CEV from U.S. airspace and ranges will require interaction with 

the agency responsible for the range. Support to Range Safety includes the technical and 

management efforts to assemble the appropriate team; develop and prepare plans for 

compliance with range safety requirements dUring deSign, development, preparation and 

execution of CEV test and operational flights, establish meetings and reviews with range safety 

personnel and the CEV subsystems personnel; coordinate with NASA operations personnel; and 

obtain range safety support to hazardous activities at the launch and test flight Sites, launch 

operations, and hazards analysIs for the launch/ascent and the descent/landing phases. 

a) In association with the ClV Project and the launch vehicle contractors, the Contractor shall 

define and resolve range safety issues in support of CEV system development, and provide 

data necessary to gain approval of the range safety requirements in accordance with ORO 

CEV-O-007, Range Safety ReqUIrements Documents. The Contractor shall Incorporate the 

requirements set developed In accordance With ORO CEV-O-007 into the appropriate CEV 

Spacecraft and GSE specifications delivered in ORO CEV-T-031, CEV System 

Requirements Specification and ORO CEV-T-031, CEV System Requirements 

Specification 

b) The Contractor shall use the following applicable standards for ORO CEV-O-007, Range 

Safety Requirements Documents 

• AFSPCMAN 91-710' Range Safety User Requirements Manual 

• NPR 8715.5, Range Safety Program 

• Range Commanders Councll- Range Safety Group - Standard 321-02. Common Risk 

Criteria for National Test Ranges 

Deliverables 


• DRD CEV-O-007 Range Safety ReqUirements Documents 

The following GSE related Range Safety data IS collected In the DRD specified in Section 2 7 2 

• DRD CEV-T-031' CEV System Specification 

• DRD CEV-T-031. CEV System Specification 

2.7.5 Training Systems (IDIQ) 

NASA Will provide the Training Systems necessary to prepare the crew, ground, and flight 

operations personnel for successful execution of CEV missions. 

a) For ground operations training systems, the Contractor shall support NASA in the 

implementation of the training systems reqUirements Examples of the support Include: 

proVide flight hardware interface design and data, participate In the design reviews, working 

groups, and technical interchange meetings; and participate in the test and verification of the 

NASA-provided training systems. 

b) The Contractor shall prOVide support to assist NASA's development of the CEV Simulators 

and mockups used for crew and flight controller training, procedure verification, real-time 

support, and control center testing Examples of Contractor support include: prOVide flight 

hardware Interface deSign and data, participate in the deSign reViews, working groups, and 

Page 42 of 119





technical interchange meetings; and participation in the test and verification of the NASAprovided 

training systems 

2.7.6 Training 

NASA operations will develop the training products and conduct the operations training and 

certification for ground and flight operations. 

a) The Contractor shall provide NASA operations access to all data products produced by the 

Contractor, Its subcontractors, and Its vendors for the purpose of their In-house training and 

familiarization of the CEV System and Its subsystems. The Contractor shall proVide the data 

products in accordance With SOW Section 1.5 (a), NASA ICE. 

b) For flight operations, the CEV Contractor shall provide support to the NASA training 

organization The Contractor shall ensure consistent, clear communications between the 

Contractor and the NASA training organization, and shall provide technical assistance during 

NASA's development of the training materials necessary to prepare the flight crew, flight 

controllers, and other flight operations personnel for CEV missions. Examples of Contractor 

support Include research and dissemination of the necessary vehicle systems data and 

technical information from the spacecraft designers for NASA to develop its training products; 

provide preliminary vehicle deSign and test data, vehicle deSign rationale and drivers, and 

clarify vehicle reqUIrements, deSign, and Interfaces; and provide an advocate between the 

flight operations' training organization and the spacecraft deSigners (IDIQ) 

c) The Contractor shall be responSible for maintaining all trainer-delivered hardware for 

assurance that the hardware receives all upgrades and all fixes. 

D) NASA shall support the Contractor in "Test Participation" training and CAlL familiarization of 

Crew members for Contractor led Verifications taking place in the CAlL. NASA shall provide 

to the Contractor data products and Crew Operational Procedures. 

2.8 Specialty Engineering 

Specialty Engineering applies the crosscutting speCialty engineering diSCiplines of materials and 

processes, electromagnetic compatibility, Electrical, ElectrOnic, and Electromechanical (EEE) 

parts, and enVIronments to the CEV System. 

a) The Contractor shall apply specialty engineering throughout the life cycle of the CEV System 

b) The Contractor's approach to incorporating the engineering speCialties Into the systems 

engineering process and the technical effort reqUired shall be documented in ORO CEV-M- 

001, CEV Prime Project Management Plan 

Deliverables 

The following SpeCialty Engineering data IS collected In the DRD specified in Section 1.1 

• DRD CEV-M-001. CEV Prime Program Management Plan 

2.8.1 Natural and Induced Environments 

a) The Contractor shall deSign the CEV System for the speCifiC natural environments and 

Induced environments that the CEV System must operate within and for which the CEV 

System must be qualified, encompassing all phases of CEV System production, testing and 

operation In all modes through disposal in accordance with CXP-70023, Constellation 

Program DeSign SpeCification for Natural Environments (DSNE) (and associated Children 

documents as speCified In Attachment J-3, Applicable, Guidance, and Informational 

Documents List) utilizing the CxP-70044, Constellation Program Natural EnVIronment 

Definition for Design (NEDD) The Contractor shall use the applicable requirements in 

Contract Attachment J-3, Table 1 2, Applicable Environmental Data Documents 

Page 43 of 119





b) The Contractor shall derive, control and validate enVIronment data and analysIs models for 

the design, certification, and operation of the CEV System, subsystems, and components. 

2.8.2 Micrometeoroid and Orbital Debris (MMIOD) Environments 

a) The Contractor shall assess MMOD risk for loss of vehicle/crew and loss of mission based on 

the design MMOD enVIronments derived from CXP-70023, Constellation Program Design 

Specification for Natural Environments (DSNE) (and associated Children documents as 

specified in Attachment J-3, Applicable, Guidance, and Informational Documents List), 

utilizing CxP-70044,Consteliation Program Natural Environment Definition for Design 

(NEDD). 

b) In performing the analysis and providing the protection hardware, the Contractor shall comply 

with the following standards 

o NASA TP-2003-21 0788, Meteoroid/Debris Shielding, 2003, Section 2 for 

describing the MMOD risk assessment process using Bumper code 

o JPR 8080 5 M/S-11, JSC Design and Procedural Standards, Section M/S-11, 

Meteoroid and Orbital DebriS Protection Levels for Structures 

Deliverables 

The Contractor shall deliver and maintain the follOWing document(s)' 

• DRD CEV-T-044: CEV MMOD Analysis Report 

2.8.3 Radiation Environments for Crew Exposure 

a) The Contractor shall use radiation analyses, including crew radiation exposure analYSIS 

(using analytical tools Integrated to structural models), to certify that the spacecraft meets the 

CEV radiation requirements for the space radiation environments deSCribed CXP-70023, 

Constellation Program DeSign SpeCification for Natural EnVIronments (DSNE) (and 

associated Children documents as specified in Attachment J-3, Applicable, Guidance, and 

Informational Documents LiSt), utilizing the CxP-70044, Constellation Program Natural 

EnVironment Definition for DeSign (NEDD) The Contractor shall document the certification 

results in ORO CEV-T-045, CEV Space Radiation Ana/ysis and Certification Report 

b) The Contractor shall use the following radiation protection reqUirements and applicable 

document(s) in the design of the CEV Spacecraft· 

a 

CXP-70024, Constellation Human Systems Integration Requirements (HSIR), 

Section 327 per the HSIR allocation matrix In Appendix J. 

o OSHA Standards 29 CFR, Supplementary Standards 1960.18 

a National Council on Radiation Protection and Measurements Report No. 132: 

Radiation Protection Guidance for Activities in Low-Earth Orbit 

o 

National CounCil on Radiation Protection and Measurements Report No TBD: 

"Radiation Protection and Science Goals for Lunar Missions", to be published 

in 2006 (Note Upon completion, this document Will replace National Council on 

Radiation Protection and Measurements Report No 132: Radiation Protection 

GUidance for Activities In Low-Earth Orbit) 

Deliverables 


• DRD CEV-T-045 CEV Space Radiation AnalYSIS and Certification Report 

Page 44 of 119





2.8.4 Materials and Processes 

a) The Contractor shall ensure materials are selected, controlled, implemented and venfled to 

be consistent with their Intended usage environments. 

b) The Contractor shall select, treat, fabricate, inspect, test, and analyze matenals of 

construction to ensure the safety and success of the CEV System. 

c) The Contractor shall develop and Implement ORO CEV-T-019, Materials and Processes 

Selection, Implementation, and Control Plan that tailors the requirements and applicable 

documents of NASA-STD-(I)-6016, Standard Materials and Processes for Requirements for 

Spacecraft indicating the degree of conformance and method of Implementation for each 

requirement as well as providing rationale for any requirements altered or not Implemented. 

d) The Contractor shall develop and implement corona design criteria as gUided by MSFC-STD- 

531, High Voltage Design Criteria and JPR 8080.5, E-6, JSC Design and Procedural 

Standard E-6, Corona Suppression. The contractor shall document and Implement DRD 

CEV-T-024, Corona Design Criteria. 

e) The Contractor shall use the following applicable standards for Materials and Processes or 

demonstrate use of an equivalent standard. 

o IPC/EIA J-STD-001, Performance Class 3 with Space Addendum 

(Requirements for Soldered Electrical and Electronic Assemblies) 

o IPC-A-610, Acceptability of Electronic Assemblies - Performance Class 3 

o JPR 8080.5, E-6, JSC Design and Procedural Standard E-6, Corona 

Suppression 

o JPR 8080.5, E-14, JSC Design and Procedural Standard, E-14, Electncal Wire 

Harness Acceptance Testing 

o JPR 8080.5, E-24, JSC Design and Procedural Standard, E-24, Electrical Wire 

o 

and Cable Acceptance Test 

NASA-STD-(I)-6016, Standard Requirements for Matenals and Processes for 

Spacecraft. 

f) The Contractor shall develop and Implement DRD CEV-T-020, Materials Usage Agreements 

(MUA), DRD CEV-T-021, Contamination Control Plan (CCP), DRD CEV-T-022, Matenals 

Identification and Usage List (MUlL); DRD CEV-T-023, Nondestructive Evaluation Plan. 

Deliverables 


• DRD CEV-T-019 Matenals and Processes Selection, Implementation, and Control Plan 

• DRD CEV-T-020' Materials Usage Agreements (MUA) 

• DRD CEV-T-021 Contamination Control Plan (CCP) 

• DRD CEV-T-022: Matenals Identification and Usage List (MIUL) 

• DRD CEV-T-023 Nondestructive Evaluation Plan 

• DRD CEV-T-024' Corona Design Criteria 

2.8.5 EMlfEMe 

a) The Contractor shall design, develop, venfy and deliver a CEV System that is 

electromagnetically compatible with internally generated electromagnetic energy, external 

electromagnetic energy environments, and the other elements of the Constellation System 

throughout ItS life cycle. 

b) The Contractor shall develop and Implement ORO CEV-T-025, CEV Electromagnetic 

Compatibility (EMC) Control and Venflcatlon Document to define the plans, processes, 

procedures, and test data that the Contractor will use to deSign, construct, and verify the CEV 

System electromagnetic compatibility requirements 

c) The Contractor shall tailor MIL-STD-461 E, ReqUirements for the Control of Electromagnetic 

Interference (EMI) Charactenstics of Subsystems and EqUipment and MIL-STD-464A, 

Electromagnetic Environmental Effects Requirements for Systems, to assist In establishing 

Page 45 of 119





the Contractor's documented requirements to meet the overall EMC requirements for CEV. 

This tailoring shall be documented in ORO CEV-T-025, CEV Electromagnetic Compatibility 

Control and Verification Document 

d) The Contractor shall develop and design the CEV System to control and mitigate hardware 

malfunction and damage throughout its life cycle that can be caused by lightning The 

Contractor's CEV lightning protection effort shall Include the Lightning Protection Plan, the 

Lightning Verification Plan, and the Lightning Protection Verification Report Information 

requested in ORO CEV-T-025, CEV Electromagnetic Compatibility Control and Verification 

Document 

e) The Contractor shall develop and Implement an Electrostatic Discharge (ESD) control 

program. The Contractor's electrostatic discharge control program and processes shall be 

documented In ORO CEV-T-025, CEV Electromagnetic Compatibility (EMC) Control and 

Verification Document The CEV System shall be constructed and delivered in accordance 

with these ESD processes. 

f) The Contractor shall deSign and deliver a CEV System which complies with the requirements 

of NASA-STD-4003, Electrical Bonding for NASA Launch Vehicles, Spacecraft, Payloads, 

and Flight EqUipment The Contractor's processes for Implementing electrical bonding 

requirements shall be documented In ORO CEV-T-025, CEV Electromagnetic Compatibility 

(EMC) Control and Verification Document. 

g) The Contractor shall tailor ML0303-0014, Electrical Wire Harnesses and CoaXial Cables, 

Installation ReqUirements for Electromagnetic Compatibility; SSP 30240, Space Station 

Grounding Requirements, and SSP 30242, Space Station Cable/wire Design and Control 

ReqUirements for Electromagnetic Compatibility to establish the Contractor's documented 

requirements to meet the overall EMC reqUirements for the CEV System. This tailoring shall 

be documented In ORO CEV-T-025, CEV Electromagnetic Compatibility Control and 

Verification Document The CEV System shall be deSigned, constructed, and delivered In 

accordance with the Contractor's wlre/harness/cable installation processes. 

(h) The Contractor shall participate with NASA and the Constellation Program through the 

Constellation E3 Control Working Group. CxP 70141, Appendix A is provided for information 

to coordinate and ensure CEV meets overall Constellation Program Electromagnetic 

Compatibility. The Contractor support to this working group Will be tailored to support the 

functions defined In sections 4 2 and 4.3 of CxP 70141 and documented In ORO-T-025, CEV 

Electromagnetic Compatibility (EMC) Control and Verification Document. 

Deliverables 


• DRD CEV-T-025. CEV Electromagnetic Compatibility Control and Verification Document 

2.8.6 Electrical, Electronic, and Electromechanical (EEE) Parts 

a) The Contractor shall develop, update, and implement ORO CEV-T-027, Electrical, Electronic, 

and Electromechanical Parts Management and Implementation Plan for the CEV System 

b) The contractor shall incorporate a control plan for ionizing radiation effects for all CEV 

electronics hardware as part of ORO CEV-T -027, Electrical, Electronics, and 

Electromechanical Parts Management and Implementation Plan, uSing informational 

document CxP 70144, Constellation Ionizing Radiation Control Plan. 

c) The Contractor shall use the follOWing applicable standards for EEE Parts 

o JPR 8080 5, E-7, JSC Design and Procedural Standards, Section E-7, 

Electrical Components - Restrictions on Use 

o JPR 8080 5, E-22, JSC Design and Procedural Standards, Section E-22, 

Ionizing Radiation Effects 

d) The Contractor shall develop and maintain DRD CEV-T-028, As-built EEE Parts List. 

Deliverables 


Page 46 of 119





• DRD CEV-T-027: Electrical, Electronic, and Electromechanical Parts Management and 

Implementation Plan 

• DRD CEV-T-028: As-Built EEE Parts List 

2.8.7 Human Engineering 

a) The Contractor shall participate with NASA In the human engineering of the CEV System as 

specified in Section 2 Vehicle Integration, Section 6, CEV Spacecraft Development and 

Section 2.7.2, Ground and Training Systems Human engineering processes will be used to 

ensure crew and ground personnel safety, and enhance performance, efficiency, productivity, 

and cost effectiveness throughout the system's expected life cycle for onboard crew, ground 

operators, and malntalners 

b) The Contractor shall perform all human engineering In accordance With CXP-70024, 

Constellation Human Systems Integration Requirements (HSIR) (and associated Children 

documents as specified In Attachment J-3, Applicable, Guidance, and Informational 

Documents List). The Contractor shall convert analYSIS data, Information on human 

capabilities and limitations, and system requirements into (a) detail design, and (b) 

development plans to create human system Integration concepts that operate Within human 

capabilities, and accomplish mission objectives 

c) The Contractor shall ensure Human Engineering personnel are Integrated Into the CEV 

development process, verify requirements for all human system Interfaces, participate in each 

Integrated Product Team, slgnoff all drawings and specifications involving human system 

Interfaces, support risk and engineering review boards, and participate in the NASA-led 

Cockpit Working Group 

d) The Contractor shall use the following applicable standards for DRD CEV-T-089, Orion Crew 

Interface Label Map. 

o CxP 70024, Constellation Human Systems Integration ReqUirements (HSIR) 

o CxP 70152, Constellation Program Crew Interface Labeling Standard 

Deliverables 


DRD CEV-T-089, Orion Crew Interface Label Map 

2.9 Aerosciences 

a) NASA will develop, update, and implement aerothermal and aerodynamic databases as part 

of the deSign and development of the CEV Spacecraft. NASA will maintain the CEV 

aerothermal and aerodynamic databases for the duration of contract performance. 

b) NASA will define the Initial Crew Module OML shape, including any flight control surfaces that 

might be required 

c) NASA will control all changes to the configuration of the Crew Module OML shape through a 

NASA-led Crew Module OML Panel. 

d) NASA will document the development of the CEV databases with an explanation of the 

methodologies used to develop, populate, validate, and utilize the databases, including the 

following 

o Documentation of experimental testing, including descriptions of the model, 

instrumentation, facilities, test conditions, and results. 

o Computational tool documentation deSCribing the application of Computational 

FlUid DynamiCs (CFD) codes and engineering tools used to populate the 

databases Including code deSCriptions, gas dynamiC modeling assumptions, 

best practices followed In grid refinement and result validation 

Page 47 of 119





o Electronic files detailing solid model geometries, computational grids, and 

flowfield solutions used in creating the databases with complete descriptions of 

file formats and content. 

o Assumptions and extrapolations used to Incorporate experimental and 

computational data Into the database 

o Specification of aerodynamic and heating uncertainties and corresponding 

justification 

o Definition of constants, variables, functions, and engineering units. 

o Documentation of aerodynamic and aerothermodynamic verification analysIs 

e) The Contractor shall be responsible for uSing the aerothermal and aerodynamic databases 

for Implementing the spacecraft design. 

f) The Contractor shall participate In an aerodynamic technical panel, which will coordinate the 

development, implementation, maintenance, and delivery of the aerodynamic database 

g) The Contractor shall participate in an aerothermodynamlc technical panel, which Will 

coordinate the development, implementation, maintenance, and delivery of the 

aerothermodynamic database. 

h) The Contractor shall participate In the Crew Module OML Panel. 

I) The Contractor shall be responsible for developing all CAD models of the OML, subsequent 

to delivery of the initial NASA-defined OML. 

2.10 CEV Assembly, Integration, and Production 

CEV Assembly, Integration, and Production consists of all activities needed to plan for the 

production of an Integrated, verified, and validated vehicle and for the coordination of the 

accepted vehicle and all deliverable hardware, software, and documentation products. CEV AI&P 

includes Integrated CEV-Ievel Imagery and imagery archiving for the CEV Project. 

a) The Contractor shall Integrate, assemble, certify, acceptance test, and deliver flight 

spacecraft meeting the requirements for the configurations Identified In Sections 2.3, 6 1 6, 

6.2.6, and 6.4 6 for Spacecraft, CM, SM/SA, and LAS, respectively 

b) Reserved 

c) The Contractor shall provide to NASA test equipment, facilities, tooling or fixtures reqUired for 

producing and testing miSSion-cycle flight articles 

d) The Contractor shall develop and implement an Imagery plan to prOVide imagery (e. g., still 

photo, motion picture, digital imagery, or video) of the CEV Spacecraft system, modules, 

subsystems, and components during manufactUring, assembly, test, Integration, and closeout 

to document the hardware configuration. The Contractor shall include the plan and 

Imagery in ORO CEV-T-088, CEV Imagery Plan/Imagery DellVerables. 

e) The Contractor's delivery plans shall include the planned method of manufacturing (including 

the Contractor's plans for deSign for manufacturabillty) and assembly of the flight articles(s) 

and assOCiated unique tooling, fixtures and support and test equipment In accordance with 

ORO CEV-T-086, Manufacturing and Assembly Plan. 

f) The Contractor shall deliver 1 CEV for the Ares-1Y with the requirements speCified In Section 

10.6, Flight Test for the Ares 1Y (minimum functionality to support LAS abort capability, suborbital 

test) 

g) The Contractor shall deliver 2 additional production CEVs for Orion-1 (orbital test) and Orion 

2 (Crewed Mission). 

h) The Contractor shall prOVide and maintain the non-standard ODIN hardware and software 

reqUired for production activities. 

I) The Contractor shall perform faCIlity modifications and/or upgrades as required for facility 

production operations. (IDIQ) 

Deliverables 


• ORO CEV-T-086: Manufacturing and Assembly Plan 

• ORO CEV-T-088: CEV Imagery Plan/Imagery Dellverables 

Page 48 of 119





Page 49 of 119





.1 SAFETY, RELIABILITY, ANO QUALITY ASSURANCE 

Safety, Reliability and Quality Assurance Includes integration of Safety and Mission Assurance 

Into the CEV System design, development, risk identification and mitigation, test, ground and 

flight operations, and ground processing activities 

3.1 SR&QA Management and Administration 

a) The Contractor shall demonstrate and document compliance with requirements stated in the 

CXP-70059, Constellation Program Integrated Safety, Reliability and Quality Assurance 

Requirements for safety, reliability, maintainability, supportability, manufacturabillty, hardware 

and software quality assurance, industrial safety, and environmental safety for all aspects of 

the CEV System 

b) The Contractor shall develop, Implement and maintain an Safety and Mission Assurance 

(S&MA) Plan in accordance with (ORO CEV-S-001). The S&MA Plan encompasses the 

System Safety Plan, Industrial, Environmental and Range Safety Plan, Reliability, 

Maintainability and Supportability Plan, Quality Assurance Plan and the Software Assurance 

Plan. Each of these plans shall define the key processes and describe the methodology for 

accomplishment of and adherence to these processes 

c) The Contractor shall Incorporate and maintain in the Integrated Master Schedule all 

Constellation Safety Engineering Review Panel (CSERP) meetings and Technical 

Interchange Meetings (TIMs) where Orion production and Flight Test Article hazards are 

addressed The Contractor shall also Incorporate the S&MA ORO deliveries, including the 

Interim deliveries of Probabilistic Risk Assessment models, hazard reports and FMEAlCILs. 

d) The Contractor shall support concurrent engineering by providing S&MA representation at 

program technical and management meetings, milestones and reviews (e.g., technical 

interchange meetings, Integration meetings, review boards, safety review panels, and change 

control boards) and provide POSitions, analYSIS results and decision support. 

e) The Contractor shall provide S&MA representation for Constellation Safety Engineering 

Review Panel (CSERP) meetings and TIMs where Orion flight, ground, Flight Test Article, or 

integrated hazards are addressed 

f) The Contractor shall provide an S&MA evaluation of flight rules, change requests, 

procedures, and contingency operations for both ground and flight operations. 

g) The Contractor shall provide S&MA support for the CEV System integrated project risk 

assessment for the Constellation Program. 

h) The Contractor shall generate, document, analyze and Incorporate lessons learned for 

incorporation Into NASA's Lessons Learned database 

I) The Contractor shall provide an S&MA evaluation of all waivers, deviations, and changes With 

an emphasis on impacts to safety and mission success 

Deliverables 


• ORO CEV-S-001. Safety and MIssion Assurance (S&MA) Plan 

3.2 System Safety 

a) The Contractor shall develop and maintain the hazard reports In accordance With CXP- 

70038, Methodology for Conduct of Project Constellation Hazard Analysis (Section 6, Hazard 

Reports). The Contractor shall deliver all CEV System hazard reports to the Constellation 

Hazards Database 

b) The Contractor shall deliver flight safety data packages per ORO CEV-S-003, Flight System 

Safety Hazard Analyses, (which include the flight operations Hazard AnalYSIS, mitigations and 

controls, design drawings, schematiCs, systems descriptions and system analysis) at all flight 

Page 50 of 119





phased safety reviews in accordance with the project schedule and CXP-70038, Methodology 

For Conduct of Project Constellation Hazard Analyses 

c) The Contractor shall deliver ground safety packages per ORO CEV-S-005, Ground System 

Safety Hazard AnalYSIS, (which Include the ground operations Hazard Analysis, mitigations 

and controls, design drawings, schematiCs, systems descriptions, hazardous operations 

descriptions, and launch site processing plans and procedures) at all ground phased safety 

reviews In accordance With the project schedule, and CXP-70038, Methodology for Conduct 

of Project Constellation Hazard Analysis 

d) The Contractor shall develop and maintain fault trees analyses to identify, mitigate and 

control the hazards of the CEV System throughout the CEV System life cycle using FTH, 

Fault Tree Handbook With Aerospace Applications, August 2002, version 1.1 (Chapters 1-9), 

as guidance, and, shall document and deliver the results per ORO CEV-S-002, Fault Tree 

Analysis. The FTAs shall address hardware, software and human failures and shall be used 

to faCilitate the hazard analyses 

e) Reserved. 

f) The Contractor shall use Spacecraft Survivability Engineering (SSE) to address the deSign 

and Implementation of opportunities to Increase spacecraft survival to ensure all threats and 

hazard consequences to the completion of the mission are analyzed, and that all sources of 

uncertainty are Identified and minimized As part of SSE, Damage Modes and Effects 

AnalYSIS (DMEA) shall be used to Identify the vulnerabilities and areas where the spacecraft 

can incorporate robustness into the design and operation, and the results submitted as part 

of ORO CEV-S-003. 

Deliverables 


• DRD CEV-S-002' Fault Tree Analysis 

• DRD CEV-S-003 Flight System Safety Hazard AnalYSIS 

• DRD CEV-S-005 Ground System Safety Hazard AnalYSIS 

3.3 Industrial, Environmental, Processing Site, Launch Site 

and Range Safety 

a) The Contractor shall develop and deliver a mishap prevention plan per ORO CEV-S- 

004,Mishap Plan and Safety Statistics. 

b) The Contractor shall provide immediate verbal notification (upon discovery) and prompt 

written reporting (within 24 hours) to the NASA safety office and contracting officer of any 

aCCident, inCident, or exposure resulting In fatality, lost-time occupational injury, disease, 

contamination of property beyond any stated acceptable limits, or property loss of $1 ,000 or 

more In addition, the Contractor shall proVide mishap, close calls, and safety statistiCS 

including trend items per ORO CEV-S-004, Mishap Plan and Safety Statistics, and shall 

assist the NASA investigating authority, as requested, in investigating these InCidents 

c) Reserved 

d) Reserved 

e) The Contractor safety organization shall actively participate In Test Readiness ReViews to 

ensure personnel and hardware safety. 

f) The Contractor shall provide, In ORO CEV-O-007 Range Safety Requirements Documents, 

safety and reliability data to support a range safety flight termination system (FTS) 

determination analysis per NPR 8715.5, Range Safety Program, and AFSPCMAN 91-710, 

Range Safety User Requirements Manual, or Range Commanders CounCil - Range Safety 

Group - 321-02 In accordance With the requirements In SOW Section 2.7.4, Range Safety 

Integration. 

g) The Contractor shall furnish a list of all hazardous operations to be performed and a list of 

key operations planned in the performance of the contract per ORO CEV-S-006, 

Hazardous/Key OperatIOns List 

Page 51 of 119





h) The Contractor shall provide safety and reliability data to support the range safety analYSIS 

per ORO CEV-S-003, System Safety Hazard Analysis, and ORO CEV-S-010, Probabilistic 

Risk Assessment Results, to meet all local test range safety reqUirements 

I) The Contractor shall coordinate With the CEV Project and the Constellation Program to 

develop and implement operational range safety requirements, plans, procedures, and check 

lists including mission rules and flight commit criteria, pertaining to Range Safety aspects of 

the CEV, In accordance With ORO CEV-O-007, Range Safety Requirements Document. 

J) The Contractor shall provide support to the joint Constellation Program and Air Force Eastern 

Range tailOring process for the Integrated CEV/CLV and NPR 8715 5, Range Safety 

Program, with supporting technical expertise, analYSIS and requirements review to support 

CEV/CLV processing and launch 

k) The Contractor shall provide technical expertise, supporting analysis and requirements 

review for the Constellation-led tailOring process of NPR 8715.5, Range Safety Program with 

respect to CEV entry and landing phases, In accordance With DRD CEV-O-007, Range 

Safety ReqUirements Documents 

I) The Contractor shall perform an orbital debriS assessment on the CEV system per ORO 

CEV-S-007, Orbital Debris Assessment, to determine the amount of orbital debris that may 

be generated both In nominal and malfunction operations and for colliSions In orbit. 

m) The Contractor shall proVide a safety and health program which Identifies, eliminates, 

mitigates and controls hazards and risks in all Contractor activities and document the plan in 

ORO CEV-S-008, Safety and Health Plan. 

n) The Contractor and their subcontractors (If any) shall follow applicable OSHA, NASA, and 

CEV safety and health requirements. The Contractor and their subcontractors shall document 

thiS "flow down" of safety and health responsibility In the Safety and Health Plan (ORO CEV 

S-008) 

0) The Contractor shall prOVide a debriS catalog for the LAS to NASA to be used by the test 

range flight safety office to determine LAS debriS Impact areas 

Deliverables 


• DRD CEV-S-004 Mishap Plan and Safety Statistics 

• DRD CEV-S-006. Hazardous, Key Operations List 

• DRD CEV-S-007. Orbital DebriS Assessment 

• DRD CEV-S-008' Safety and Health Plan 

The following Range Safety Implementation specifiC data IS collected In the DRD speCified In 

Section 2.7.4 

• DRD CEV-O-007. Range Safety ReqUirements Documents 

3.4 Reliability, Maintainability, and Supportability (RMS) 

a) The Contractor shall develop, implement, and maintain an RMS Plan per ORO CEV-S-001, 

Safety and MISSIon Assurance (S&MA) Plan, which defines the implementation of RMS within 

their organization Including processes, required Skills, tasks and products for the CEV 

System 

b) The Contractor shall perform Failure Modes Effects Analyses ICrltlcalltems Lists (FMENCIL) 

per CxP-70043, Constellation Program Hardware Failure Modes and Effects AnalYSIS and 

Critical Itesm List Methodology and document the results per ORO CEV-S-009, Failure Mode 

and Effects Analysis & Critical Items List (FMEAlCIL). The Contractor shall establish and 

maintain the results in a common database that integrates the FMENCIL document, Hazard 

Analysis, Problem Reporting and Corrective Action (PRACA) data, Risk data and the 

Reliability Block Diagram Analysis. This common database shall prOVide the capability to 

Interactively query, search, and sort the data to generate worksheet and Index reports These 

reports shall be used as part of the validation of the PRA models and R&M analysis used to 

show compliance to the CEV SRD requirements 

Page 52 of 119





c) The Contractor shall perform CEV System Probabilistic Risk Assessments for each Design 

Reference Mission as defined in CxP 70007, Constellation Design Reference Missions and 

Operational Concept, In support of risk-informed deSign. The PRAs will identify and prioritize 

the primary risk drivers and shall be conducted in accordance with CxP 70017. The results 

will be documented In ORO CEV-S-010, Probabilistic Risk Assessment Results The 

Contractor shall also perform focused CEV PRAs to support necessary design trade studies 

or hazard analyses 

d) The Contractor shall perform Reliability, Maintainability, and Supportability analyses for the 

reliability and maintainability requirements for the CEV System and shall document the 

results per the ORO CEV-S-011, Reliability, Maintainability, and Supportability Integrated 

Report These results will be used to support the maintenance concept. 

e) The Contractor shall identify where DeSign for MInimum Risk (DFMR) is used in lieu of fault 

tolerance, where adding additional redundancy IS not technically feasible or where 

redundancy would negatively impact overall system safety and reliability The Contractor 

shall identify the rationale for acceptance of these DFMR functions deSigns The Contractor 

shall document the above In ORO CEV-S-011, Reliability, Mamtainability, and Supportability 

Integrated Report 

f) The Contractor shall develop Reliability and Maintainability Planning Document(s) using the 

gUidance of CxP 70087, Constellation Program Reliability, Availability, and Maintainability 

Plan. 

g) The Contractor shall participate In the GIDEP and NASA Alerts process employing ORO 

CEV-S-012, Government-Industry Data Exchange Program and NASA Advisories/Alerts. 

Deliverables 


• DRD CEV-S-009' Failure Modes Effects AnalYSIS & Critical Items List (FMEAlCIL) 

• DRD CEV-S-010' Probabilistic Risk Assessment Results 

• DRD CEV-S-011 Reliability, Maintainability, and Supportability Integrated Report 

• DRD CEV-S-012: Government-Industry Data Exchange Program and NASA 

AdviSOries/ALERTS 

3.5 Hardware Quality Assurance 

a) The Contractor shall develop, implement and maintain a quality management system and 

Quality Assurance Plan per ORO CEV-S-001, Safety and Mission Assurance (S&MA) Plan, 

and in accordance With CXP-70059, Constellation Program Integrated Safety, Reliability & 

Quality Assurance (SR&QA) Requirements The Quality Assurance Plan shall define their 

Quality Assurance organization including processes, required skills, tasks and products for 

the CEV project 

b) The Contractor shall Implement and document a Problem Reporting and Corrective Action 

(PRACA) system and provide all reportable problems, their status, and corrective actions, for 

both hardware and software software in accordance with CxP 70068, Constellation Program 

Problem Reporting, Analysis and Corrective Action (PRACA) Requirements, Volumes 1, 2 

and 3. PRACA Reports shall be delivered per ORO CEV·S·013, Problem Reporting and 

Corrective Action (PRACA) Reports. 

c) The Contractor shall identify, track, and disposition all hardware and software nonconformances, 

anomalies, and discrepancies In a Contractor database and provide NASA 

with access to these records, for the life of the Project 

d) The Contractor shall perform Internal and subcontractor audits per the Safety and Mission 

Assurance (S&MA) Plan (ORO CEV·S·001) The Contractor shall document the findings and 

results of the Internal and subcontractor audits per ORO CEV·S·014, Quality Assurance Audit 

Reports. 

e) The Contractor's S&MA organization shall review design specifications and designs to 

determine compliance with required materials specifications 

Page 53 of 119





f) The Contractor's S&MA organization shall review Materials and Special Processes activities 

in the CEV Spacecraft Manufacturing process, to ensure compliance with materials and 

process control specifications (including welding and brazing assurance, and NDE expertise 

to assure proper methods, techniques and standards are being used 'In the performance of 

NDE upon the hardware). 

g) The Contractor's S&MA organization shall participate In the Fracture Control Board for the 

CEV System to evaluate fracture-critical hardware. 

h) The Contractor shall document the controls for any process that cannot be verified by a 

reliable and repeatable inspection or test, and if not precisely applied and controlled within its 

defined limits, could result in hardware failure that results In loss of human life or serious 

injury/illness to the flight crew, ground crew, or general public; or results In loss of mission, or 

loss of a significant mission resource These processes and their controls shall be 

documented in ORO CEV-S-015, Critical Processes. 

i) The Contractor shall develop, implement, and document a Mechanical Parts Assurance Plan 

for flight and critical ground support equipment hardware per ORO CEV-S-016, Mechanical 

Parts Management and Implementation Plan. 

j) The Contractor shall document its workmanship standards/specifications to ensure that they 

meet or exceed applicable NASA and Program Standards per ORO CEV-S-017, 

Workmanship Standards. 

Deliverables 


• DRD CEV-S-013: Problem Reporting and Corrective Action (PRACA) Reports 

• DRD CEV-S-014 Quality Assurance (QA) Audit Report 

• DRD CEV-S-015: Critical Processes 

• DRD CEV-S-016: Mechanical Parts Management and Implementation Plan 

• DRD CEV-S-017' Workmanship Standards 

The following Quality Assurance Plan specifiC data IS collected Inthe DRD specified in Section 

3.1. 

• DRD CEV-S-001' Safety and MISSion Assurance Plan 

3.6 Software Safety and Assurance 

a) The Contractor shall develop, implement, and maintain a Software Assurance Plan per ORO 

CEV-S-001, Safety and Mission Assurance (S&MA) Plan, Chapter 6. 

b) The Contractor shall demonstrate and document software assurance functions for all 

software in the CEV System In accordance With NASA-STD 8739.8 NASA Software 

Assurance Standard 

o Chapter 6, ProVider Software Assurance 

o Chapter 7, Software Assurance Disciplines 

c) The Contractor shall audit its own and any software suppliers Internal software assurance 

activIties to allow evaluation of both the progress and effectiveness of software assurance 

tasks and the need for adjustments or changes and document the results in ORO CEV-S- 

018, Software Quality Assurance (SQA) Audit Reports 

d) The Contractor shall implement a systematic approach to software safety as an Integral part 

of the project's overall system safety program, per ORO CEV-S-001, Safety and Mission 

Assurance (S&MA) Plan, Chapter 2 - System Safety Plan 

Deliverables 


• DRD CEV-S-018 Software Quality Assurance (SQA) Audit Report 

Page 54 of 119





4RESERVEO 

Page 55 of 119





5RESERVEO 

Page 56 of 119





6 CEVSPACECRAFT DEVELOPMENT 

Spacecraft development Includes the tasks required for the design, development, production, 

assembly, test, and certification efforts to deliver the completed Spacecraft for integration with the 

launch vehicle and other mission elements 

6.1 Crew Module 

The Crew Module includes the tasks required for the deSign, development, production, assembly, 

test, and certification of the Crew Module (CM) and efforts to deliver the completed Crew Module 

for Spacecraft Integration 

6.1.1 CM Management and Administration 

CM Management and Administration includes the efforts for planning, organizing, directing, 

coordinating, controlling, and approval processes used to accomplish Crew Module Development 

objectives. , 

a) NASA will maintain detailed oversight of all Crew Module deSign activities. The Contractor 

shall maintain responsibility for delivery of a deSign that meets the requirements. The 

detailed process diSCUSSion to accomplish this can be found In CxP-72008, Crew Exploration 

Vehicle Project Plan The Contractor shall include NASA personnel on all deSign teams 

established by the Contractor. 

6.1.2 CM System Engineering and Integration 

CM Systems Engineering and Integration consists of the efforts to lead the Crew Module's overall 

system architecture definition and engineering functions. ThiS Includes the technical and 

management efforts of directing and controlling the Integrated engineering effort for the CM This 

also Includes the effort to coordinate CM integration with the CEV integration functions described 

In Section 2. 

a) The Contractor shall define the modules, subsystems, components, and software Units that 

make up the Crew Module per the requirements and dellverables included in this section. 

b) The Contractor shall develop, maintain, and deliver all draWings and technical Computer 

Aided Design (CAD) models of the Crew Module system, subsystems and components. The 

Contractor shall use ORO CEV-T-003, CEV CAD Models, and ORO CEV-T-004, CEV 

Drawmgs, as the template for development and delivery of these items 

c) The Contractor shall develop and maintain models and simulations for the Crew Module 

system, subsystems, and components uSing ORO CEV-T-002, CEV Engineering Models. 

d) The Contractor shall document ICD(s) for the government furnished products below: 

o CEV Spacecraft docking components (APAS and LIDS) of the docking system 

for ISS and LSAM docking requirements 

o Parachute system In support of nominal and abort entries 


e) The Contractor shall document Crew Module subsystem requirements using ORO CEV-T- 

031, CEV ReqUirements Specifications. 

f) The Contractor shall document component-level requirements Within the Crew Module uSing 

ORO CEV-T-031, CEV Requirements Specifications. 

g) The Contractor shall document all hardware Interfaces requirements uSing ORO CEV-T-035, 

Internal Interface Requirement Document (IRD) The Contractor shall produce an IRD for 

each subsystem that Interfaces With another subsystem. 

Page 57 of 119





h) The Contractor shall develop and maintain the Crew Module portion of the CEV Specification 

and Drawing Trees, ORO-CEV-T-032. The top drawing shall be incorporated into the CEV 

System Drawing Tree Identified In Section 2 2 

I) The contractor shall provide a CEV stowage interface design document In accordance With 

ORO CEV-T-029 

J) The contractor shall document all Crew Module internal subsystem Interface deSign details 

uSing ORO CEV-T-029, Interface Control Documents 

Deliverables 


• DRD-CEV-T-029' Crew Module Internal Interface Control Documents 

• DRD CEV-T-029' Crew Module Internal Interface Control Documents 

• DRD CEV-T-029. Crew Module Internal Stowage Interface Contreol Documents 

The follOWing Module speCifiC data IS collected in the DRD specified in Section 2 2 

• DRD CEV-T-031' Crew Module ReqUirements SpeCifications 

• DRD-CEV-T-031 Crew Module ReUirements SpeCifications 

• DRD CEV-T-032 CEV Specification and Drawing Tree for the Crew Module 

• DRD CEV-T-035 Crew Module Internal Interface Requirements Documents 

The follOWing Module speCifiC data IS collected In the DRDs speCified In Section 2 4 

• DRD CEV-T-002 CM Engineering Models 

• The following deliverables areseparate Module deliverables and are integrated by 

reference into the System level submittal in 2 4. 

• DRD CEV-T-003' CM CAD Models 

• DRD CEV-T-004 CM DraWings 

6.1.3 eM Subsystems 

This Section includes the work required to design, develop, produce, and test through certification 

and acceptance all Crew Module subsystems required to meet CEV module-level and interface 

requirements. 

a) The Contractor shall deSign, develop, test, certify, and deliver Crew Module subsystem 

hardware complying with all requirements in CXP-72000, Systems Requirements for the 

Crew Exploration Vehicle Element (CEV SRD) (including the listed applicable documents and 

those included in this Statement of Work (SOW) See section 2 2) 

b) In support of the Crew Module avionics development effort, the Contractor shall prOVide the 

following for each subsystem. 

o 

o 

Validation of the subsystem's software requirements 

Validation of subsystem models/simulations used for flight software and 

integrated aviOniCS verification 

c) The Contractor shall proVide system and CM-Ievel deSign definition data in the ORO CEV-T- 

033, Architectural Design Document and deSign definition and data down to the component 

level In the Subsystem DeSign and Data Books. (See Section 2 2) 

d) The Contractor shall hold subsystem design reviews prior to the system PDR and CDR 

e) The Contractor shall test (acceptance test only) and deliver flight spares for the Crew Module 

subsystems. (IDIQ) The Contractor shall proVide a spare parts list as part of DRD-CEV-T- 

012 (See Section 2.7 2) 

f) The Contractor shall deliver Flight Spacecraft Crew Modules for Orion 1 and Orion 2. 

g) The Contractor shall deliver one ship set of Crew Module flight spares (I.e., 1 copy of every 

line replaceable unit) (IDIQ) 

h) The Contractor shall use the following standards and requirements documents for developing 

all CM subsystems 

o 

JPR 8080.5, JSC DeSign and Procedural Standards (and assOCiated Children 

documents as specified in Attachment J-3, Applicable, GUidance, and 

Informational Documents List) (exclUSive of government "shalls") 

Page580f119





o CXP-70024, Constellation Human Systems Integration Requirements (HSIR) 



i) The Contractor shall use the following standards for developing all CM subsystems: 

o AIAA-S-OBO, AIAA Standard for Space Systems - Metallic Pressure Vessels 


o ANSI/AIAA-S-OB1A-2006, AIAA Standard for Space Systems - Composite 


Deliverables 


The following module specific Information is collected in the DRDs specified In Section 2.7 2 

• ORO CEV-T -012. Logistics Support AnalysIs 

The following module specific Information IS collected in the DRDs specified In Section 2.2 

• ORO CEV-T-033: Architecture Design Document 

6.1.3.1 Reserved 

6.1.3.2 CM Command & Data Handling 

a) The Contractor shall document the design for all Crew Module C&DH hardware as specified 

in ORO CEV-T-047, AVionics Design and Data Book Volume 1/- C&DHllnstrumentation 

Subsystem Data. 

b) The Contractor shall deliver three ship sets offlight eqUivalent unit C&DH hardware (for the 

trainer). 

Deliverables 

The following module specific Information IS collected In the DRDs specified in Section 2.6.1 

• ORO CEV-T-047: Avionics Design and Data Book, Volume 11- C&DHllnstrumentation 


6.1.3.3 CM Communications & Tracking 

a) For the Crew Module, the Contractor shall prepare, deliver, and maintain ORO CEV-T-047, 

Avionics Design and Data Book Volume III - Communications and Tracking Subsystem Data. 

b) The contractor shall provide the CEV to ISS CCA hardware and documentation necessary for 

CEV docking to ISS 

c) The Contractor shall work with NASA on the integration of the CEV to ISS CCA hardware Into 

the ISS 

d) Any NASA provided components will be designed for environments consistent with ISS and 

Progress 

Deliverables 

The following module specific Information IS collected In the DRDs specified In Section 2.6.3 

• DRD CEV-T-047 AVIonics Design and Data Book, Volume 111- Communications and 

Tracking Subsystem Data Book 

6.1.3.4 CM Displays and Controls 

a) The Contractor shall prepare, maintain, and deliver AVionics Design and Data Book Volume 

IV - Displays and Controls Subsystem Data per ORO CEV-T-047 

Page 59 of 119





b) The Contractor shall deliver one ship set of flight equivalent unit D&C hardware (for the 

trainer). 

Defiverables 

The follOWing module speCifiC Information is collected in the DRDs specified in Section 2 6.4 

• DRD CEV-T-047: AVIonics Design and Data Book, Volume 111- Displays and Controls 

Subsystem Data Book 

6.1.3.5 CM Electrical Power System 

a) The Contractor shall document the design for all Crew Module EPS Hardware as specified in 

ORO CEV-T-059, Electrical Power System (EPS) Design and Data Book 

b) The Contractor shall participate with the Constellation Program In the development of DRD 

CEV-T-060, Electrical Power Quality Specification ReqUirements Document. 

Deliverables 

The following module specific Information IS collected In the DRDs speCified in Section 2.6.5 

• DRD CEV-T-059 CM Electrical Power System (EPS) Design and Data Book 

• DRD CEV-T-060' CM Electrical Power Quality SpeCification ReqUirements Document 

6.1.3.6 CM Mechanisms 

a) NASA will provide the Androgynous Peripheral Assembly System (APAS) and associated 

data products as necessary to support ISS docking. 

b) The Contractor shall Integrate ATLAS Into the CEV Spacecraft configuration necessary to 

support specified ISS docking missions 

c) NASA will prOVide the Low Impact Docking System (LIDS) and associated data products. 

d) The Contractor shall integrate LIDS Into the CEV Spacecraft design as necessary to support 

ISS and Lunar docking. 

e) The Contractor shall document the design for all Crew Module mechanisms as specified in 

ORO CEV-T-061, Mechanical Systems DeSIgn and Data Book, and ORO CEV-T·062: Stress 

Analysis Report 

f) NASA Will prOVide the CEV to ISS Docking Adapter for ISS docking 

g) The Contractor shall integrate the CEV to ISS docking adapter for two adapter delivery 

missions to ISS. ThiS Integration Includes NASA provided avioniCS reqUired to operate 

Androgynous Peripheral Assembly Systems 

h) The ISS CCA OSR's will be mounted such that they have a clear view to deep space 

Deliverables 

The following module specifiC Information IS collected In the DRDs specified In Section 2.6 6 

• DRD CEV-T-061 :CM Mechanical Systems DeSign and Data Book 

• DRD CEV-T-062' CM Stress AnalYSIS Report 

6.1.3.7 CM Passive Thermal Control 

a) The Contractor shall develop thermal analytical models to support Crew Module thermal 

analyses 

b) The Contractor shall document the deSign for all Crew Module Passive Thermal Control as 

speCified in ORO CEV-T-063, PTC Systems Design and Data Book, and ORO·CEV-T-064, 

Passive thermal Control Mathematical Models and Documentation 

Deliverables 

The follOWing module specific information IS collected In the DRDs specified in Section 2.6.7 

Page 60 of 119





• DRD CEV-T-063. CM Passive Thermal Control Design and Data Book (PTCDDB) 

• DRD CEV-T-064' CM Passive Thermal Control Mathematical Models and Documentation 

6.1.3.8 eM Thermal Protection System 

a) NASA will perform advanced development of two designs for the TPS forebody heat shield 

component through the Onon PDR. The forebody heat shield component includes both the 

TPS matenals or matenal system, the underlYing support structure to which the TPS material 

is mounted, and the attachment or bonding agents or system These two advanced 

development design options are as follows' 

o Primary Lunar Return capable 

o Alternate Lunar Return capable 

b) NASA Will produce the follOWing subsystem products for PDR 

o TPS Component (Forebody Heatshleld) Requirements SpeCification (ORO 

CEV-T-031) 

o TPS Component (Forebody Heatshleld) section of the Thermal Protection 

System Design and Data Book (TPSDDB) (ORO CEV-T-065) 

o TPS Component (Forebody Heatshleld) Math Models as part of Thermal 

Protection System Mathematical Models and Documentation (ORO CEV-T- 

066) and CEV CAD Models (ORO CEV-T-003) 

o Inputs to Integrated Contractor products 

c) The contractor shall produce the following subsystem products post-transition. 

o TPS Component (Forebody Heatshield) Requirements Specification (ORO 

CEV-T-031) 

o TPS Component (Forebody Heatshield) section of the Thermal Protection 

o 

System Design and Data Book (TPSDDB) (ORO CEV-T-065) 

TPS Component (Forebody Heatshield) Math Models as part of Thermal 

Protection System Mathematical Models and Documentation (ORO CEV-T- 

066) and CEV CAD Models (ORO CEV-T-003) 

d) The Contractor shall participate in advanced development activities to the extent necessary 

to execute the efforts described in this SOW. 

e) The Contractor shall produce all remaining subsystem PDR products not produced by NASA. 

f) FollOWing the TPS subsystem design review that occurs pnor to Onon PDR, the Contractor 

shall perform detailed design, test, and analYSIS of the two TPS heat shield designs 

g) The Contractor shall establish a milestone for selecting one of the two TPS heat shield 

designs based on test and evaluation of the two designs The Contractor shall recommend 

the TPS heat shield design to be used for final Implementation at this milestone. The 

Contractor shall document thiS milestone In the Integrated Master Plan (IMP) NASA Will 

select the final TPS heat shield design 

h) The Contractor shall develop one engineering development unit (EDU) for the selected heat 

shield design for use in Contractor and NASA testing 

i) The Contractor shall complete design, development, test, certification, and delivery of the 

selected TPS heat shield and all post-PDR DRD products 

J) The Contractor shall design, develop, test, certify, and deliver all other CEV Spacecraft TPS 

components and DRD products 

k) The Contractor shall develop thermal analytical models to support Integrated Constellation 

vehicle analyses and CEV thermal analyses. 

I) NASA will lead, and the Contractor shall participate in, joint advanced development activities 

for the CEV thermal protection system through the Preliminary Design Review (PDR) The 

Contractor shall develop and Implement plans, which detail the transition from development 

to insertion Into the pnmary design path, for these advanced technologies The Contractor 

shall document these plans in the design and data books for each subsystem. 

Deliverables 

• DRD CEV-T-065 Thermal Protection System Design and Data Book (TPSDDB) 

Page 61 of 119





• DRD CEV-T-066: Thermal Protection System Mathematical Models and Documentation 

The following subsystem documentation IS collected In the DRDs specified in Section 6 1 2, Post 

PDR 

• DRD CEV-T-031 CM Thermal Protection System Requirements 

Specification 

• DRD CEV-T-031 CM Thermal Protection System Requirements 

Specification 

The following module specific information is collected In the DRDs specified In Section 2 4, Post 

PDR 

• DRD CEV-T-002 CM TPS Engineering Models 

• DRD CEV-T-003 CM TPS CAD Models 

• DRD CEV-T-004' CM TPS DraWings 

6.1.3.9 eM Structures 

a) The Contractor shall perform structural analYSIS on all Crew Module structures, including 

pressure vessels, to show that all elements of the deSign such as the strength, stiffness, 

structural stability, and life meet all speCified criteria for the anticipated loads and 

environments 

b) The Contractor shall perform Crew Module loads and dynamics analyses and document the 

results in ORO CEV-T-067, Structural Loads Data Book. 

c) The Contractor shall perform Crew Module stress and fatigue analyses and document the 

results in ORO CEV-T -062, Stress Analysis Report. 

d) The Contractor shall develop Crew Module models to support Integrated Constellation vehicle 

analyses as well as CEV loads and stress analyses The Contractor shall deliver ORO CEV 

T-06S, Structures Mathematical Models and Documentation, which Will deliver and describe 

the mathematical models used in the Crew Module system, subsystem, and component loads 

and stress analyses. 

e) The Contractor shall implement a fracture control program and identify fracture critical parts 


propagation and fracture The Contractor shall deliver and Implement ORO CEV-T-069, 

Fracture Control Plan, and ORO CEV-T-070, Fracture Control Summary Report. 

f) The Contractor shall use NASA-HDBK-7005, DynamiC Environmental Criteria, as a guidance 



g) The Contractor shall use the follOWing standards for deSigning and analYZing the Crew 

Module structures subsystem. 

o Contract Attachment J-3, Table 1.2, Applicable EnVironmental Data 

DocumentsJSC-62550, Structural Design and Verification Criteria for Glass, 

Ceramics and Windows in Human Space Flight Applications 

o NASA-STD-5001, Structural DeSign and Test Factors of Safety for Space 


o 

o 

NASA-STD-5002, Loads Analyses of Spacecraft and Payloads 

NASA STD-(I)-5019, Fracture Control Requirements for Space Flight 

Hardware 

h) The contractor shall produce an engineering development Crew Module structure (Ground 

Test Article) for use In environmental testing (See Section 2 6.9) 

I) The Contractor shall deliver a CM Structural Test Article (used for structural verification static 

and dynamiC testing) via DD1149 process 

Deliverables 

The follOWing module speCifiC information IS collected In the DRDs speCified In Section 2 6 9 

• DRD CEV-T -015 Master Verification Plan 

• DRD CEV-T-062 CM Stress AnalYSIS Report 

Page 62 of 119





• DRD CEV-T-067: CM Structural Loads Data Book 

• DRD CEV-T-068. CM Structures Mathematical Models and Documentation 

• DRD CEV-T-070: CM Fracture Control Summary Report 

6.1.3.10 Crew Module Propulsion 

a) The Contractor shall perform design, development, test, certification and delivery of all Crew 

Module propulsion systems and develop all propulsion related DRD products 


activities and associated processes for all Crew Module propulsion systems In order to certify 

the propulsion systems for compliance with CEV component, subsystem, module, Spacecraft 

system, and vehicle-level requirements The Contractor shall also deSign, fabricate and test 

Integrated Crew Module propulsion systems in order to evaluate and certify Integrated 

propulSion system hot fire performance for each propulsion application. The Contractor shall 

also deSign, fabricate, and test integrated Crew Module propulsion systems to evaluate and 

certify integrated propellant system storage and conditioning designs. (See Section 2 6 10) 

c) The Contractor shall document the design for all Crew Module propulsion as specified in 

DRD CEV-T -071, Propulsion Systems Design and Data Book. 

Deliverables 

The follOWing module specific Information is collected in the DRDs specified In Section 2.6.10 

• DRD CEV-T-071' CM PropulSion Systems Design and Data Book 

6.1.3.11 Suits, EVA, and Survival Crew Equipment Support 

Systems 

a) NASA Will proVide the CEV SUitS and EVA support equipment per Orion to EVA SystemsCEV 

IRD, CxP 70033 (e g , EVA SUitS, launch and entry suits, helmets, gloves, undergarments, 

and standard EVA tools If applicable) 

b) NASA Will provide portable crew equipment systems and gear as defined in CxP-70035 

Portable Equipment, Payloads and Cargo IRD requirements for emergency egress and 

survival, crew/personnel post landing tracking systems, and crew/personnel post landing 

commUnications systems. 

c) The Contractor shall perform requirements development, design, analysis and trade studies, 

assembly/production, integration, testing, verification, validation, qualification, certification, 

and delivery of the CEV interfaces for the NASA-prOVided SUitS, EVA support equipment, and 

survival crew equipment as defined in CxP-70035 Portable Equipment, Payloads and Cargo 

IRD requirements. 

d) The Contractor shall provide specialized CEV-speclfic EVA tools, and external deVices, 

restraints, and mobility aids 

e) The Contractor shall use the human engineering standards listed in section 2 8 7, Human 

Engineering, to design all interfaces to SUitS, EVA, and survival crew equipment systems 

f) The contractor shall proVide EVA handling aids mounted to the exterior of the ISS CCA to 

support installation, activation, and check out 

g) NASA Will prOVide the Vehicle Multiple Connector (MC) shipsets, and associated data 

products 

h) The contractor shall support and integrate the NASA developed Vehicle Multiuse Connector 

Deliverables 

The following module speCifiC Information IS collected in the DRDs speCified In Section 2.6.11 

• DRD CEV-T-072. CM SUitS, EVA and Survival Crew EqUipment Support Systems DeSign 

and Data Book 

Page 63 of 119





6.1.3.12 Crew Module Environmental Control and Life Support 

(ECLS), Crew Health and Habitation Accommodations 

a) NASA will provide food and food packaging The Contractor shall design the Crew Module 

Interfaces for these NASA-provided items 

b) NASA will provide portable medical kits, equipment, and supplies, and portable 

countermeasures systems The Contractor shall design the Crew Module Interfaces for these 

NASA-provided items 

c) NASA will provide additional FCE such as personal hygiene kits, hygiene consumables, sleep 

restraints, portable supplemental lighting, portable vacuum cleaner, dust abatement system, 

disposable wipes, personal carry-on stowage, standard tools, crew clothing, and portable 

crew personal items (e.g, relaxation and entertainment systems) The Contractor shall 

design the Crew Module Interfaces for these NASA-provided Items. 

d) NASA will provide active and passive radiation Instrumentation. The Contractor shall design 

the interfaces for these NASA-provided Items 

e) The Contractor shall use the following EClS, crew health and habitation accommodations 

standards and the Human Engineering Standards listed in section 287, Human Engineering, 

for designing this subsystem. 

o 

JSC 20584, Spacecraft Maximum Allowable Concentrations for Airborne 

Contaminants 

f) The Contractor shall provide definition of the process to be used for cleanliness of 

components for use In oxygen, fuel, and pneumatic systems. The Contractor shall prOVide 

this information in ORO CEV-T-073, Environmental Control and Life Support Design and Data 

Book. The process must meet or exceed the requirements identified In the following 

documents: 

o 

o 

o 

o 

MSFC-SPEC-164B, SpeCification for Cleanliness of Components for Use in 


speCified In Attachment J-3, Applicable, GUidance, and Informational 



Inspection 

MSFC-PROC-1831, The AnalysIs of Nonvolatile Residue Content 

MSFC-PROC-1832, Sampling and AnalysIs of Nonvolatile ReSidue Content 


g) The Contractor shall identify the standard for test methods for enVIronmental engineering in 

ORO CEV-T -073, Environmental Control and Life Support Design and Data Book. This 

standard shall meet or exceed the follOWing standard' 

o 

Mll-STD-810F, DOD Test Method Standard for Environmental Engineering 


Deliverables 


The following module speCifiC information is collected in the DRDs specified in Section 2.6.12 

• ORO CEV-T-073: GM Environmental Control and Life Support DeSign and Data Book 

• ORO CEV-T-074: CM Habitation Accommodations Design and Data Book 

6.1.3.13 CM Pyrotechnics 

a) The Contractor shall perform deVice level preliminary design reviews and Critical design 

reviews for each Crew Module pyrotechnic devices not proVided by NASA The Contractor 

shall conduct development, qualification, and acceptance testing on all other pyrotechniC 

devices selected for the Crew Module The Contractor shall conduct Phase I, Phase II, and 

Phase III technical reviews on all other pyrotechnic deVices selected for the Crew Module per 

Page 64 of 119





the requirements of JSC 62809, Constellation Spacecraft Pyrotechnic Specification and JPR 

8080 5 Standards P1-P7 

b) Crew Module specific stress analysis reports will be collected In the DRD (ORO CEV-T-062, 

Stress Analysis Report) specified in Section 2.6.13 for all pyrotechnic deVices selected for the 

Crew Module. 

c) The Contractor shall document the design for the Crew Module pyrotechnic subsystem as 

specified in ORO CEV-T-075, Pyrotechnic Subsystem Design and Data Book 

d) NASA will supply pyrotechnic reefing line cutters used in the CPAS architecture 

Deliverables 


The following Module specific data IS collected In the DRD specified in Section 2.4 

• DRD CEV-T-002: CM Engineering Models 

• DRD CEV-T-003 CM CAD Models 

• DRD CEV-T-004 CM Drawings 

The following Module specific data is collected In the DRD specified In Section 3.4 

• DRD CEV-S-009 FEMA Cil 

The following Module specific data is collected in the DRD specified In Section 2 8 4 

• DRD CEV-T-022 MIUl 

The follOWing module specific Information IS collected in the DRDs specified in Section 2.6.13 

• DRD CEV-T-062: CM Stress Analysis Report 

• DRD CEV-T-075: CM Pyrotechnic Subsystem Design and Data Book 

6.1.3.14 Landing and Recovery Systems 

a) NASA Will proVide the parachute system 

b) The contractor shall provide the pyrotechnic deVices with the exception of the reefing line 

cutters, and select Parachute Test Vehicle hardware (Parachute Bays and Forward Bay 

Covers) In support of the parachute system. 

c) NASA Will perform advanced development of the landing attenuation system leading up to the 

landing attenuation subsystem deSign review 

d) NASA will produce the following landing attenuation system PDR products that are derived 

from landing and Recovery System Subsystem ReqUirements Specification (ORO CEV-T- 

031) 

o landing Attenuation System Subsystem ReqUirements Specification (ORO 

CEV-T-031, CEV Requirements Specification) 

o landing Attenuation System Component Requirements Specification (ORO 


o 

o 

Input to ORO CEV-T-076, Recovery Systems Design and Data Book 

Input to ORO CEV-T-077, Recovery Systems Simulation Models and 

Documentation 

e) The Contractor shall participate in the advanced development activities to the extent 

necessary to execute the efforts described in this SOW 

f) The Contractor shall produce all remaining PDR products not produced by NASA 

g) The Contractor shall complete design, development, test, certification, and delivery of the 

selected landing attenuation system and all post-PDR DRD products. 

o 

o 

o 

o 

landing Attenuation System Subsystem ReqUirements Specification (ORO 


landing Attenuation System Component Requirements Specification (ORO 


ORO CEV-T-076, Recovery Systems DeSign and Data Book 

ORO CEV-T-077, Recovery Systems Simulation Models and Documentation 

Page 65 of 119





h) The Contractor shall perform the requirements development, trade studies, design, analysis, 

production, assembly, integration, testing, verification, validation, qualification, certification, 

and maintenance for Contractor-provided CEV recovery hardware as specified by the CEV 

Project 

i) The Contractor shall develop models and simulations for Contractor-provided hardware and 

Integrate with the models and simulations for the NASA-provided hardware to support 

recovery systems development (ORO CEV-T-077, Recovery System Simulation Models and 

Documentation) 

j) NASA will lead, and the Contractor shall participate In, JOint advanced development activities 

for the CEV landing attenuation through the system Preliminary Design Review (PDR). The 

Contractor shall develop and Implement plans, which detail the transition from development 

to Insertion Into the primary design path, for these advanced technologies. The Contractor 

shall document these plans In the design and data books for each subsystem. 

k) The Contractor shall develop, Implement, and maintain an Landing and recovery Systems 

Master Verification Plan, per ORO CEV-T-015, that details the Contractor's plan for verifying, 

certifying, and acceptance of the Landing and Recovery System. 

Deliverables 


• DRD CEV-T-076' CM Recovery Systems Design and Data Book 

• DRD CEV-T-077' CM Recovery Systems Simulation Models and Documentation 

The following subsystem documentation is collected in the DRDs specified in Section 6 1 2, Post 

PDR 

• DRD CEV-T-031 CM Landing Attenuation System Requirements 

SpeCification 

• DRD CEV-T-031 CM Landing Attenuation System Requirements 

SpeCification 

The following module specific information IS collected In the DRDs speCified In Section 102, Post 

PDR 

• DRD CEV-T -015' CM Recovery Systems Volume - Master Verification Plan 

6.1.3.15 Crew Module Guidance, Navigation, and Control 

(GN&C) 

a) The Crew Module GN&C requirements design and functional verification effort will be 

performed through the use of specialized mode teams NASA will co-lead with the Contractor 

the development of detailed design requirements for the Crew Module GN&C flight system. 

The Contractor shall document the Crew Module GN&C requirements in ORO CEV-T-031, 

CEV GN&C Subsystem Requirements Specification, and ORO CEV-T-048, Software 

Requirements Specification The Contractor shall prOVide support to the follOWing teams 


o Entry GN&C Mode Team 


o Flight Mechanics/Mission Design Mode Team 

b) The Contractor shall document the design for the Crew Module GN&C subsystem as 

speCified In ORO CEV-T-078, GN&C Systems Design and Data Book 

Deliverables 

The following module specific information is collected in the DRDs specified in Section 6.1.2 

• DRD CEV-T-031:CM GN&C Requirements Specification 

• DRD CEV-T-031 CM GN&C Requirements SpeCification 

The follOWing module speCifiC information IS collected In the DRDs speCified In Section 6.5.2 

• DRD CEV-T-048. Software Requirements Specification 

The follOWing module speCifiC information IS collected In the DRDs speCified In Section 2.6.15 

Page660f119





• DRD CEV-T-07B: CM GN&C Design and Data Book 

6.1.3.16 CM Wiring 

a) The Contractor shall develop a wiring database that provides definition down to the level of 

pin-to-pin connectivity for all electrical harnesses and optical cables used on the Crew 

Module for ground, launch, flight, and recovery operations Including testrng, verrflcatlon, 

calibration, and maintenance. The Contractor shall deliver the wiring database to NASA as 

ORO CEV-T-080, CEV Wiring Database and Reports The Contractor shall provide a 

hierarchical path/signal structure which links the wiring database to ORO CEV-T-046, CEV 

Data and Command Dictionary 

b) The Contractor shall develop, manufacture/fabrrcate, test, install, and certify all Crew Module 

wiring in accordance with ORO CEV-T-079, CEV Wiring Plan, and ORO CEV-T-080, CEV 

Wiring Database and Reports. 

Deliverables 

The following module specific Information IS collected In the DRDs specified rn Section 2 6 1 

• DRD CEV-T-046: CEV Data and Command Dictionary 

The following module specific Information IS collected In the DRDs specified in Section 2.6.16 

• DRD CEV-T-079 CM Wlrrng Plan 

• DRD CEV-T-OBO: CM Wiring Database and Reports 


6.1.5 CM Test. Verification. and Certification 

a) The Contractor shall execute the Spacecraft Master Verification Plan for the verification, 

qualification, certlflcatron, and acceptance of the Crew Module, subsystems, and 

components. 

b) The Contractor shall perform qualiflcatron tests uSing ORO CEV-T-037, Qualification Test 

Procedures, and document the test results In ORO CEV-T-038, Qualification Test Report, and 

ORO CEV-T-017, Certification Data Package. The Contractor shall perform qualification 

testing at component, CM and intermediate levels of assembly as necessary to accumulate 

the data necessary for certification The Contractor shall produce a Certification Data 

Package for the component, each subsystem in the Crew Module, the Crew Module, and the 

Spacecraft. Note. Software test documentation IS handled In SOW section 6.5, CEV 

Software. The contractor shall develop a dedicated qualification Crew Module for systemlevel 

qualification testrng Followrng the completion of system-level qualification testing, the 

contractor shall maintain configuration control of the dedicated qualification CM and store it in 

an environmentally-controlled and access-controlled area. 

c) The Contractor shall perform acceptance testing at the Crew Module and CM component 

level using ORO CEV-T-039, Acceptance Test Procedures, and document the results using 

ORO CEV-T-040, Acceptance Data Package. An Acceptance Data Package shall be 

produced for the production flight Crew Modules (Orion 1 and 2) 

d) The Contractor shall hold Test Readiness Reviews (TRRs) before all formal verrflcatlon 

activities The Contractor shall make subsystem and module test procedures available to 

NASA. The Contractor shall invite NASA, to witness all formal verification activities, including 

TRRs and test executions 

e) The Contractor shall conduct verification testing of all rnterface designs and requirements 

within the Crew Module (between subsystems, and between components) 

f) If the Contractor utilizes modeling and slmulatron to conduct analysIs In support of verification 


Models, Simulations and Support Plan, and ORO CEV-T-002, CEV Engineering Models 

Page 67 of 119





g) The Contractor shall provide the Integration, test, & verification facilities required to test and 

certify the Crew Module and all CM subsystems and components The Contractor shall invite 

NASA to witness all subsystem faCility design reviews, test, verification, and certification 

activities 

h) The Contractor shall provide the Integration, Test, & Verification (IT&V) facilities required to 

complete Integrated verification of the Crew Module The requirements for the IT&V faCilities 

shall be derived from the products developed under Section 10 1, Test, Verification 

Management and Administration 

i) The Contractor shall develop, Implement, and maintain an CM Master Verification Plan, per 

ORO CEV-T-01S, that details the Contractor's plan for verifying, certifying, and acceptance of 

Crew module 

j) The Contractor shall provide support in order to conduct verification testing of all Interface 

deSigns and requirements within the CM Module for those verification activities that are 

NASA led in NASA facilities 

Defiverables 


The following module specific Information IS collected In the DRDs specified in Section 10.2: 

• DRD-CEV-T-015: Crew Module Volumen Master Verification Plan 

The Contractor shall deliver the follOWing DRDs for the Qualification Vehicle CM, Incorporating all 

lower level element Qualification data. These DRDs will be also collected Into the DRD specified 

in Sections 10.2 and 10 3 for the Integrated CEV 

• DRD CEV-T-017 Certification Data Package 

• DRD CEV-T-037 Qualification Test Procedures 

• DRD CEV-T-038: Qualification Test Report 

The Contractor shall deliver the following DRDs for the Production Vehicle CM, Incorporating all 

lower level element acceptance data These DRDs will be also collected into the DRD specified 

In Sections 10.2 and 10.3 for the integrated CEV. 

• DRD CEV-T-039 Acceptance Test Procedures 

• DRD CEV-T-040. Acceptance Data Package 

6.1.6 eM Assembly, Integration, and Production (AI&P) 

a) The Contractor shall Integrate, assemble, certify, acceptance test, and deliver flight Crew 

Modules meeting the requirements for the configurations below 

b) The Contractor shall develop and Implement an Imagery plan to proVide Imagery (e g, still 

photo, motion picture, digital Imagery, or Video) of the Crew Module, subsystems, and 

components during manufacturing, assembly, test, integration, and close-out to document the 

hardware configuration The Contractor shall Include the plan and Imagery In ORO CEV-T· 

088, CEV Imagery Plan/Imagery Deliverables 

c) The Contractor shall develop and Implement plans detailing the deSign and construction of all 

Crew Module transportation support equipment, and the plans for transportation of the Crew 

Module to the processing andlor launch sites These plans shall be included in ORO CEV·T· 

087, CEV Spacecraft Handling and Transportation Plan 

Deliverables 


The following module specific information is collected in the DRDs specified in Section 2 7 2' 

• DRD CEV·T·087· CEV Handling and Transportation Plan 

The following module specific information is collected in the DRDs specified in Section 2.10: 

• DRD CEV-T-086: Manufacturing and Assembly Plan 

• DRD CEV-T-088 CEV Imagery Plan/Imagery Deliverables 

Page680f119





6.1.6.1 eM Flight Hardware AI&P 

a) The Contractor shall Integrate, assemble, certify, acceptance test, and deliver flight Crew 

Modules meeting the requirements for configurations below 


Crew Module transportation support eqUipment, and the plans for transportation of the Crew 

Module to the processing and/or launch sites These plans shall be included In ORO CEV-T- 

087, CEV Spacecraft Handling and Transportation Plan. 

c) The Contractor shall deliver a production CM for Orion 1 and a production CM for Orion 2. 

d) The Contractor shall be responsible for post-flight refurbishment of any reusable Items 

delivered under Schedule A. (IDIO) 

e) The Contractor shall design, develop, produce, Integrate, verify, validate, certify, document, 

and deliver Crew Module GSE In accordance with all requirements in CXP-72000, Systems 

Requirements for the Crew Exploration Vehicle Element (CEV SRD), and in this SOW, and in 

accordance with ORO CEV-O-008, Ground Systems Requirements, Plans, Reports, and 


Contractor shall plan for and deliver the GSE end items in accordance with Attachment J-9 

The Contractor shall use the follOWing applicable documents for design and development of 

Contractor-provided GSE: 

o 

NASA-STD-5005B' NASA Standard for Ground Support EqUipment (and 


Applicable, Guidance, and Informational Documents list). 

f) The Contractor shall develop and update ORO CEV-O-008, Ground Systems Requirements, 

Plans, Reports, and Design Data, Volume III, Systems Operations and Maintenance Plan and 

ReqUIrements Documentation, for the ground support equipment provided for the Crew 

Module. 

g) The Contractor shall develop, maintain and deliver all technical models and draWings of the 

GSE associated with the Crew Module In accordance With ORO CEV-T-003, CEV CAD 

Models, and ORO CEV-T-004, CEV Drawings. 

h) The Contractor shall develop and update 2-D and 3-D Simulation models of the Contractorprovided 

Crew Module and Contractor-provided Crew Module GSE to assess clearances, 

placement, conflicts and the moving of hardware In accordance With ORO CEV-T-003, CEV 

CAD Models. The Contractor shall develop and deliver these models in accordance with 

SOW Section 2.4. 

i) The Contractor shall develop and deliver ORO CEV-T-040, Acceptance Data Package, for 

each Contractor-provided Crew Module GSE end item. 

J) The Contractor shall prOVide Initial spares, concurrent With the delivery of the GSE end Items 

and in accordance with the provisioning procedures in ORO CEV-T-011, Integrated Logistics 

Support Plan, and ORO CEV-T-012, Logistics Support Analysis, for all Contractor-provided 

Crew Module GSE. (IDIO) 

k) (reserved) 

I) The Contractor shall integrate, assemble, certify, acceptance test, and deliver flight hardware, 

for installation to the ISS meeting the requirements of CEV and the 

environments/requirements of ISS in accordance with the CEV to ISS IRD. 

m) ISS CCA qualification and acceptance testing will be conducted at the assembly level. 

n) For Orion 1, the Government shall provide a Developmental Flight Instrumentation (DFI) 

system and installation engineering, Installed by the Contractor 

0) 

Deliverables 

The following CM GSE data is incorporated in the DRD specified in Section 2 4 

• DRD CEV-T-003 CEV CAD Models 

• DRD CEV-T-004' CEV DraWings 

The follOWing CM GSE data is Incorporated in the DRD specified in Section 2.7.2: 

• DRD CEV-O-008' Ground Systems Requirements,Plans, Reports, and DeSign Data 

• DRD CEV-T-040 Acceptance Data Package 

Page 69 of 119





• DRD CEV-T-087' CEV Handling and Transportation Plan 

6.1.6.2 Test Article Design and Production 

a) The CM primary structure for PA1 and AA1 will be provided by NASA 

b) For PA1 and AA1, the Contractor shall design, develop, procure, build, assemble, integrate, 

and verify the CM avionics and mechanisms kits per the requirements and specifications 

developed in Section 10.64, Flight Test Article (FTA) DDT&E 

c) RESERVED 

d) For PA2, and AA2, the Contractor shall design and develop the prototype CMs uSing the 

system, module, sub-system, and component level requirements and specifications 

developed in section 10.6.4, Flight Test Article (FTA) DDT&E; documented In ORO CEV-O- 

002, Flight Test Article Specification 

e) For PA2, and AA2, the Contractor shall procure, build, assemble, integrate, and test the 

prototype CMs under this section of the SOW. Prototype FTAs must meet the production 

standards as specified in section 1064, FTA DDT&E, paragraph u, documented in ORO 

CEV-O-004, Flight Test Article (FTA) Design and Data Book. 

f) For PA2, and AA2, ,the Contractor shall validate and verify the flight test unique design as 

specified in CEV- T-015, Volume VII, Master Verification Plan, Flight Test Volume and 

documented in accordance with section 10.6.4, FTA DDT&E, paragraph y *' 

g) For PA2, and AA2, the Contractor shall deliver three (3) two (2) prototype CMs. (+ DD250 for 

each CM) 

h) For Ares-1 Y~ the Contractor shall deliver one production like CM With elements removed 

(and replaced with simulators) that are not required to meet mission objectives defined in 

CXP-72166. 

I) The Contractor shall design, develop, produce, Integrate, verify, validate, certify, document, 

and deliver CM FTA GSE in accordance with all requirements in CXP 72000, Systems 

ReqUIrements for the Crew Exploration Vehicle Element (CEV SRD), and In thiS SOW, and In 

accordance With ORO CEV-O-008, Ground Systems ReqUIrements, Plans, Reports, and 


Contractor shall use the following applicable documents for design and development of 

Contractor-provided GSE 

o NASA-STD-5005B. NASA Standard for Ground Support EqUipment (and 



J) The Contractor shall deliver a CM test article for a Ground Vibration Test at MSFC in 

accordance With CxP 72234, Integrated Vehicle Ground Vibration Test Task Plan. This CM 

test article can either be simulated modules or residual test articles refurbished to support 

specific requirements of the test. Support for Integrated Vehicle Ground Vibration Test shall 

be in accordance with the Ares IVGVT & Orion Bilateral Exchange Agreement (BEA). 

k) The Contractor shall develop ORO-CEV-T-031, CEV FTA Requirements Specification for 

Flight Tests Ares 1-Y as defined In Section 1064 

I) The Contractor shall develop and maintain ORO CEV-O-005, Flight Test Article (FTA) 

Validation and Verification Data Book, Identified In Section 106, for the CM FTA. 

Deliverables 


The follOWing CM FTA data IS Incorporated In the DRD specified in Section 10.2. 

DRD-CEV-T-015. FTAVolume Master Verification Plan (per Section 10.6) 

The following Module specific information IS collected In the DRDs specified In Section 10.6.4. 

• DRD CEV-D-002. Flight Test Article Specification for Pad Abort and Ascent 

Abort Flight Tests. 

• DRD CEV-D-004: Flight Test Article (FTA) Engineering Design and Data Book 

• DRD CEV-D-005. Flight Test Article (FTA) Validation and Verification Data Book 

Page 70 of 119





• DRD CEV-T-031 CEV Requirements Specification, for the Flight Test Articles 

for Ares 1Y 

The following Module specific information IS collected In the DRDs specified In Section 2.7.2 

• DRD CEV-O-OOB. Ground Systems Requirements, Plans, Reports, and Design Data, 

Volume II, Ground Systems End Item Implementation Plan and Report 

6.2 Service Module 

Service Module (which Includes the Spacecraft Adapter) includes the tasks required for the 

design, development, production, assembly, test, and certification of the Service Module, and 

efforts to deliver the completed SM for Spacecraft Integration 

6.2.1 SM Management and Administration 

SM Management and Administration includes the efforts for planning, organizing, directing, 

coordinating, controlling, and approval processes used to accomplish Service Module 

development objectives. 

a) NASA will maintain detailed oversight of all Service Module design activities The Contractor 

shall maintain responsibility for delivery of a design that meets the requirements. The 

detailed process diSCUSSion to accomplish thiS can be found In CxP-7200B, Crew Exploration 

Vehicle Project Plan. The Contractor shall include NASA personnel on all design teams 

established by the Contractor 

6.2.2 SM System Engineering and Integration 

SM Systems Engineering and Integration consist of the efforts to lead the Service Module's 

overall system architecture definition and engineering functions This includes the technical and 

management efforts of directing and controlling the integrated engineering effort for the SM. ThiS 

also Includes the effort to coordinate SM integration with the CEV Integration functions described 

In Section 2 

a) The Contractor shall define the modules, subsystems, components, and software units that 

make up the Service Module per the requirements of thiS section 

b) The Contractor shall define the modules, subsystems, components, and software units that 

make up the Service Module per the requirements and dellverables Included In thiS section. 

c) The Contractor shall develop, maintain, and deliver all drawings and technical Computer 

Aided Design (CAD) models of the Service Module system, subsystems and components. 

The Contractor shall use ORO CEV-T-003, CEV CAD Models, and ORO CEV-T-004, CEV 

Drawings, as the template for development and delivery of these items. 

d) The Contractor shall develop and maintain models and Simulations for the Service Module 

system, subsystems, and components uSing ORO CEV-T-002, CEV Engineering Models. 

e) The Contractor shall document and maintain ICD(s) for the government furnished products 

below' 

o PyrotechniCS Initiators 

f) The Contractor shall document Service Module- level requirements using ORO CEV-T-031, 

CEV Requirements Specifications. 

g) The Contractor shall document component-level requirements within the Service Module 

using ORO CEV-T-031, CEV Requirements Specifications. 

h) The Contractor shall document all hardware interfaces requirements uSing ORO CEV-T-035, 

Internal Interface Requirement Document (lRD). The Contractor shall produce an IRD for 

each subsystem that Interfaces With another subsystem 

i) The Contractor shall develop and maintain the Service Module portion of the CEV 

Specification and Drawing Trees, ORO-CEV-T-032. The top drawing shall be Incorporated 

into the CEV System Drawing Tree identified in Section 2.2 

Page 71 of 119





J) The contractor shall document all Service Module internal subsystem interface design details 

using ORO CEV-T-029, Interface Control Documents 

Deliverables 


• DRD-CEV-T-029' Service Module Internal Interface Control Documents 

• DRD CEV-T-031: Service Module Requirements Specifications 

• DRD-CEV-T-031: Service Module ReUirements Specifications 

• DRD CEV-T-032' CEV Specification and Drawing Tree for the Service Module and 

Spacecraft Adapter 

• DRD CEV-T-035 Service Module Internal Interface Requirements Documents 

The following Module specific data IS collected in the DRDs specified in Section 2.,4 3 

• DRD CEV-T-002: SM Engineering Models 

• The following deliverables are separate Module deliverables and are Integrated by 

reference into the System level submittal In 2.3. 

• DRD CEV-T-003 SM CAD Models 

• DRD CEV-T-004' CM Drawings 

6.2.3 SM Subsystems 

This section Includes the work required to design, develop, produce, and test through certification 

and acceptance all Service Module subsystems required to meet CEV module-level and interface 

requirements. Spacecraft Adapter Subsystems deliverables Will be developed as appropriate 

a) The Contractor shall design, develop, test, certify, and deliver Service Module subsystem 

hardware complying with all requirements In CXP-72000, Systems Requirements for the 

Crew Exploration Vehicle Element (CEV SRD) (including the listed applicable documents and 

those included in this Statement of Work (SOW) See Section 2 2). 

b) In support of the Service Module aVIOniCS development effort, the Contractor shall provide the 

following for each subsystem. 

o 

o 


Validation of subsystem modelslslmulatlons used for flight software and 

Integrated aVionics verification 

c) The Contractor shall provide system and LAS-level design definition data In the ORO CEV-T- 

033, Architectural Design Document and design definition and data down to the component 

level in the Subsystem Design and Data Books. 

d) The Contractor shall hold subsystem design reviews prior to the system PDR and CDR 

e) The Contractor shall test (acceptance test only) and deliver flight spares for the Service 

Module subsystems. The Contractor shall provide a spare parts list as part of the ORO CEV 

T-012, Logistics Support Analysis (Recommended Spare Parts List) (IDIO) 

f) The Contractor shall deliver 1 Flight Spacecraft Service Module (including the Spacecraft 

Adapter) for Orion 1 and 1 Flight Spacecraft Service Module for Orion 2. 

g) The Contractor shall deliver one ship set of Service Module flight spares (Le , 1 copy of every 

line replaceable unit) (IDIO) 

h) The Contractor shall use the follOWing standards and requirements documents for developing 

all SM subsystems 

o 

JPR 8080 5, JSC DeSign and Procedural Standards (and associated Children 

documents as specified in Attachment J-3, Applicable, Guidance, and 

Informational Documents List) (exclusive of government "shalls") 

o CXP-70024, Constellation Human Systems Integration ReqUirements (HSIR) 

(and associated Children documents as specified in Attachment J-3, 


i) The Contractor shall use the following standards for developing all SM and SA subsystems: 

o 

AIM-S-080, AIM Standard for Space Systems - Metallic Pressure Vessels 


Page 72 of 119





o 

ANSIIAIM-S-081A-2006, AIM Standard for Space Systems - Composite 


Deliverables 


The following module specific information is collected in the DRDs specified In Section 2.7.2 

• DRD CEV-T-012. Logistics Support Analysis 

The following module specific information is collected in the DRDs specified In Section 2 2 

• DRD CEV-T-033. Architecture Design Document 


6.2.3.2 SM Command and Data Handling (C&DH) 

a) The Contractor shall document the design for all Service Module C&DH hardware as 

specified in ORO CEV-T-047, Avionics Design and Data Book Volume /1- 

C&DHllnstrumentation Subsystem Data 

Deliverables 

The Contractor shall deliver and maintain the following document(s) as applicable: 

• DRD CEV-T-047: AVIonics Design and Data Book, Volume II - C&DHllnstrumentation 


6.2.3.3 SM Communications and Tracking (C& T) 

a) For the Service Module, the Contractor shall prepare, deliver, and maintain DRD CEV-T-047, 

AVIOniCS DeSign and Data Book Volume III - Communications and Tracking Subsystem Data. 

Deliverables 

The Contractor shall deliver and maintain the follOWing document(s) as applicable: 

The following module specific Information IS collected In the DRDs specified In Section 2.6.3 

• DRD CEV-T-047 Avionics Design and Data Book, Volume 111- Communications and 



6.2.3.5 SM Electrical Power System 

a) The Contractor shall document the deSign for all Service Module EPS Hardware as speCified 

In ORO CEV-T-059, Electrical Power System (EPS) Design and Data Book 

b) The Contractor shall participate With the Constellation Program In the development of DRD 

CEV-T-060, Electrical Power Quality SpeCification ReqUirements Document. 

Deliverables 

The Contractor shall deliver and maintain the following document(s) as applicable 

The following module specific information is collected in the DRDs specified in Section 2.6 5 

• DRD CEV-T-059. SM Electrical Power System (EPS) DeSign and Data Book 

• DRD CEV-T-060 SM Electrical Power Quality SpeCification Requirements Document 

Page 73 of 119





6.2.3.6 SM Mechanisms 

a) The Contractor shall document the design for all Service Module mechanisms as specified in 

ORO CEV-T-061, Mechanical Systems Design and Data Book, and ORO CEV-T-062: Stress 

AnalysIs Report 

Deliverables 

The Contractor shall deliver and maintain the following document(s) as applicable. 

The following module specifiC information is collected in the DRDs speCified In Section 2.6.6 

• ORO CEV-T-061 :SM Mechanical Systems Design and Data Book 

• ORO CEV-T-062 SM Stress Analysis Report 

6.2.3.7 SM Passive Thermal Control 

a) The Contractor shall develop thermal analytical models to support Service Module thermal 

analyses. 

b) The Contractor shall document the design for all Service Module Passive Thermal Control as 

specified in ORO CEV-T-063, PTC Systems Design and Data Book, and ORO-CEV-T-064, 

PassIVe thermal Control Mathematical Models and DocumentatIOn 

Deliverables 

The Contractor shall deliver and maintain the following document(s) as applicable 

The following module speCifiC information is collected in the DRDs speCified In Section 2.6.7 

• ORO CEV-T-063. SM Passive Thermal Control Design and Data Book (PTCDDB) 

• ORO CEV-T-064. SM Passive Thermal Control Mathematical Models and Documentation 


6.2.3.9 SM Structures 

a) The Contractor shall perform structural analysIs on all Service Module structures, including 

pressure vessels, to show that all elements of the deSign such as the strength, stiffness, 

structural stability, and life meet all speCified criteria for the anticipated loads and 

environments 

b) The Contractor shall perform Service Module loads and dynamics analyses and document 

the results In ORO CEV-T-067, Structural Loads Data Book 

c) The Contractor shall perform Service Module stress and fatigue analyses and document the 

results In ORO CEV-T-062, Stress Analysis Report. 

d) The Contractor shall develop Service Module models to support Integrated Constellation 

vehicle analyses as well as CEV loads and stress analyses. The Contractor shall deliver 

ORO CEV-T-068, Structures Mathematical Models and Documentation, which will deliver and 

describe the mathematical models used In the Service Module system, subsystem, and 

component loads and stress analyses 

e) The Contractor shall implement a fracture control program and identify fracture Critical parts 


propagation and fracture. The Contractor shall deliver and implement ORO CEV-T-069, 

Fracture Control Plan, and ORO CEV-T-070, Fracture Control Summary Report. 

f) The Contractor shall use NASA-HDBK-7005, DynamiC Environmental Criteria, as a gUidance 

document to support the ORO CEV-T-015, Master Verification Plan ORO product 


Page 74 of 119





g) The Contractor shall use the follOWing standards for designing and analYZing the Service 

Module structures subsystem' 

o CXP-15002, Crew Exploration Vehicle (CEV)/Crew Launch Vehicle (CL V) 

Loads Requirements Data Book 

o JSC-62550, Structural Design and Verification Criteria for Glass, Ceramics and 

Windows In Human Space Flight Applications 



o NASA-STD-5002, Loads Analyses of Spacecraft and Payloads 

o NASA STD-(I)-5019, Fracture Control Requirements for Space Flight Hardware 

h) The contractor shall produce an engineering development Service Module structure for use 

In environmental testing (Ground Test Article). (See Section 2.6.9) 

i) The Contractor shall deliver an SM Structural Test Article (used for structural verification 

static and dynamic testing), via DD1149 process 

Deliverables 


The following module specifiC Information IS collected In the DRDs specified in Section 2.6.9 

• DRD CEV-T-062' SM Stress AnalYSIS Report 

• DRD CEV-T-067' SM Structural Loads Data Book 

• DRD CEV-T-068: SM Structures Mathematical Models and Documentation 

• DRD CEV-T-070' SM Fracture Control Summary Report 

• DRD CEV-T-015. Structures Subsystem Volume Master Verification Plan 

6.2.3.10 SM Propulsion 

a) The Contractor shall perform deSign, development, test, certification and delivery of all 

Service Module propulSion systems and develop all propulsion related DRD products. 

b) The Contractor shall develop, document, implement, and execute comprehenSive verification 

activities and associated processes for all Service Module propulsion systems In order to 

certify the propulsion systems for compliance With CEV component, subsystem, module, 

Spacecraft system, and vehicle-level requirements The Contractor shall also deSign, 

fabricate and test Integrated Service Module propulsion systems in order to evaluate and 

certify integrated propulsion system hot fire performance for each propulsion application. The 

Contractor shall also deSign, fabricate, and test Integrated Service Module propulsion system 

to evaluate and certify integrated propellant system storage and conditioning deSigns and 

capabilities In order to evaluate and certify propellant conditioning performances (See 

Section 2610) 

c) The contractor shall incorporate Single-fault tolerance Into the blpropellant valves and 

pneumatic system of the CEV Service Module main engine 

d) The Contractor shall document the design for all Service Module propulsion as speCified In 

ORO CEV-T-071, Propulsion Systems Design and Data Book. 

Deliverables 


• DRD CEV-T-071. SM PropulSion Systems DeSign and Data Book 

6.2.3.11 Suits, EVA, and Survival Crew Equipment Support 

Systems 

a) The Contractor shall prOVide speCialized CEV-speciflc EVA tools, and external devices, 

restraints, and mobility aids as necessary in the Service Module design 

Page 75 of 119





Deliverables 


The following module specific information is collected In the DRDs specified In Section 2.6.11 

• DRD CEV-T-072' EVA and Survival Crew Equipment Support Systems Design and Data 

Book 

6.2.3.12 Service Module and Spacecraft Adapter Environmental 

Control and Life Support (ECLS), Crew Health and 

Habitation Accommodations 

a) The Contractor shall use the following EClS, standards and the Human Engineering 

Standards listed in section 2 8 7, Human Engineering, for designing this subsystem: 

o JSC 20584, Spacecraft Maximum Allowable Concentrations for Airborne 

Contaminants 

b) The Contractor shall provide definition of the process to be used for cleanliness of 

components for use in oxygen, fuel, and pneumatic systems. The Contractor shall prOVide 

this Information In ORO CEV-T-073, Environmental Control and Life Support Design and Data 

Book. The process must meet or exceed the requirements identified In the following 

documents 

o 

o 

o 

o 

MSFC-SPEC-164B, Specification for Cleanliness of Components for Use in 


specified In Attachment J-3, Applicable, Guidance, and Informational 



Inspection 

MSFC-PROC-1831, The Analysis of Nonvolatile ReSidue Content 

MSFC-PROC-1832, Sampling and AnalysIs of Nonvolatile Residue Content on 

Critical Surfaces 

c) The Contractor shall Identify the standard for test methods for environmental engineering In 

ORO CEV-T-073, Environmental Control and Life Support Design and Data Book. This 

standard shall meet or exceed the following standard' 

o 

Mll-STD-810F, DOD Test Method Standard for EnVIronmental Engineering 


Deliverables 


• The following module speCifiC Information is collected in the DRDs speCified in Section 

2612 

• DRD CEV-T-073: Environmental Control and life Support Design and Data Book 

6.2.3.13 SM Pyrotechnics 

a) The Contractor shall perform device level preliminary design reviews and critical design 

revlews- for each Service Module pyrotechnic device not provided by NASA The Contractor 

shall conduct development, qualification, and acceptance testing on all other pyrotechnic 

devices selected for the Service Module. The Contractor shall conduct Phase I, Phase II, 

and Phase III technical reviews on all other pyrotechnic devices selected for the Service 

Module per the reqUirements of JSC 62809, Constellation Spacecraft Pyrotechnic 

Specification and JPR 8080 5 Standards P1-P7 ' 

b) Service Module specific stress analYSIS reports Will be collected in the DRD (ORO CEV-T- 

062, Stress Analysis Report) speCified In Section 2 6 13 for all pyrotechnic devices selected 

for the Service Module. 

Page 76 of 119





c) The Contractor shall document the design for the Service Module Module pyrotechnic 

subsystem as specified in DRD CEV-T-075, Pyrotechnic Subsystem Design and Data Book 

Deliverables 

The Contractor shall deliver and maintain the following document(s) as applicable:The following 

module specific Information IS collected in the DRDs specified in Section 2 4 

• DRD CEV-T-002 SM Engineering Models 

• DRD CEV-T-003: SM CAD Models 

• DRD CEV-T-004' SM Drawings 

The following Module specific data IS collected in the DRD specified in Section 3.4 

• DRD CEV-S-009 FMEA Cil 

The following Module specific data IS collected In the DRD specified in Section 2.8.4 

• DRD CEV-T-022 MIUl 

The following module specific information is collected In the DRDs specified in Section 2.6.13 

• DRD CEV-T-062: SM Stress AnalysIs Report 

• DRD CEV-T-075' SM PyrotechniC Subsystem Design and Data Book 


6.2.3.15 SM Guidance, Navigation, and Control (GN&C) 

a) The Service Module GN&C requirements design and functional verification effort will be 

performed through the use of specialized mode teams. NASA will co-lead with the 

Contractor the development of detailed design requirements for the Service Module GN&C 

flight system. The Contractor shall document the Service Module and Spacecraft Adapter 

GN&C requirements In ORO CEV-T-031, CEV GN&C Subsystem Requirements 

Specification, and ORO CEV-T-048, Software Requirements Specification. The Contractor 

shall provide support to the following teams 

o CEV AscenVAbort Mode Team 


o Flight Mechanics/MIssion Design Mode Team 

b) The Contractor shall document the design for the Service Module GN&C subsystem as 

speCified In ORO CEV-T·078, GN&C Systems Design and Data Book 

Deliverables 


The follOWing module speCifiC Information IS collected in the DRDs specified in Section 6.1 2 

• DRD CEV-T-031:SM GN&C Requirements Specification 

• DRD CEV-T-031 SM GN&C Requirements SpeCification 

The following module specific information is collected In the DRDs speCified In Section 6 5 2' 

• DRD CEV-T-048: Software Requirements SpeCification 

The following module specific Information IS collected In the DRDs speCified In Section 2 6 15' 

• DRD CEV-T-078. SM GN&C Design and Data Book 

6.2.3.16 SM Wiring 

a) The Contractor shall develop a wIring database that provides definition down to the level of 

pin-to-pin connectivity for all electrical harnesses and optical cables used on the Service 

Module for ground, launch, flight, and recovery operations including testing, verification, 

calibration, and maintenance The Contractor shall deliver the wIring database to NASA as 

ORO CEV-T·080, CEV Wiring Database and Reports. The Contractor shall provide a 

Page 77 of 119





hierarchical path/signal structure which links the wiring database to ORO CEV-T-046, CEV 


b) The Contractor shall develop, manufacture/fabricate, test, Install, and certify all Service 

Module wiring in accordance with ORO CEV-T-079, CEV Wiring Plan and ORO CEV-T-080, 

CEV Wiring Database and Reports 

Deliverables 


The following module specific Information is collected in the DRDs specified In Section 2.6 1 

• DRD CEV-T-046' CEV Data and Command Dictionary 

The following module specific information is collected In the DRDs specified In Section 2.6.16 

• DRD CEV-T-079: SM Wiring Plan 

• DRD CEV-T-080' SM WIring Database and Reports 


6.2.5 SM Test, Verification, and Certification 


qualification, certification, and acceptance of the Service Module, subsystems, and 

components. 

b) The Contractor shall perform qualification tests uSing ORO CEV-T-037, QualificatIon Test 

Procedures, and document the test results In ORO CEV-T·038, Qualification Test Report and 

ORO CEV-T-017, Certification Data Package. The Contractor shall perform qualification 

testing at component, SM and Intermediate levels of assembly as necessary to accumulate 

the data necessary for Service Module certification. The Contractor shall produce a 

Certification Data Package for each component and each subsystem In the Service Module, 

and the Service Module . The contractor shall develop a dedicated qualification Service 

Module for system-level qualification testing FollOWing the completion of system-level 

qualification testing, the contractor shall maintain configuration control of the dedicated 

qualification SM and store It In an enVIronmentally-controlled and access-controlled area 

c) The Contractor shall perform acceptance testing at the Service Module and Spacecraft 

Adapter and SM component level using ORO CEV-T-039, Acceptance Test Procedures, and 

document the results using ORO CEV-T-040, Acceptance Data Package An Acceptance 

Data Package shall be produced for Service Modules for Orion 1 and 2. 

d) The Contractor shall hold Test Readiness Reviews (TRRs) before all formal verification 

activities. The Contractor shall make subsystem and module test procedures available to 

NASA The Contractor shall invite NASA to witness all formal verification activities, including 

TRRs and test executions. 

e) The Contractor shall conduct verification testing of all interface designs and requirements 

within the Service Module (between subsystems, and between components). 

f) If the Contractor utilizes modeling and Simulation to conduct analysIs In support of verification 


Models, SimulatIons and Support Plan, and DRO CEV-T-002, CEV Engineering Models 

g) The Contractor shall provide the integration, test, & verification facilities required to test and 

certify the Service Module and all SM subsystems and components The Contractor shall 

invite NASA to witness all subsystem facility deSign reviews and certification activities 

h) The Contractor shall provide the Integration, Test, & Verification (IT&V) facilities reqUired to 

complete integrated verification of the Service Module The requirements for the IT&V 

facilities shall be derived from the products developed under Section 10.1, Test, Verification 

Management and Administration 

Page 78 of 119





I) The Contractor shall develop, Implement, and maintain an SM Master Verification Plan, per 

ORO CEV-T -015, that details the Contractor's plan for verifYing, certifYing, and acceptance of 

Sevice Module system. 

Deliverables 


The following module specific information IS collected In the DRDs specified In Section 10.2 

• DRD-CEV-T-015 Service Module Volume Master Verification Plan 

The Contractor shall deliver the following DRDs for the Qualification Vehicle SM, incorporating all 

lower level element Qualification data. These DRDs will be also collected into the DRD specified 

in Sections 10 2 and 10 3 for the Integrated CEV 

• ORO CEV-T-017 Certification Oata Package 

• ORD CEV-T-037 Qualification Test Procedures 

• ORO CEV-T-038: Qualification Test Report 

The Contractor shall deliver the follOWing DROs for the Production Vehicle SM, incorporating all 

lower level element acceptance data. These DRDs will be also collected Into the DRD specified 

In Sections 10.2 and 10 3 for the Integrated CEV 

• ORO CEV-T-039' Acceptance Test Procedures 

• ORO CEV-T-040: Acceptance Data Package 

6.2.6 SM Assembly, Integration, and Production 

a) The Contractor shall Integrate, assemble, certify, acceptance test, and deliver flight Service 

Module meeting the requirements for configurations below 

b) The Contractor shall develop and Implement an imagery plan to proVide Imagery (e g, still 

photo, motion picture, digital Imagery, or Video) of the Service Module, subsystems, and 

components dUring manufactUring, assembly, test, integration, and close-out to document the 

hardware configuration. The Contractor shall Include the plan and imagery In ORO CEV-T- 

088, CEV Imagery Plan/Imagery Deliverables 

c) The Contractor shall develop and implement plans detailing the design and construction of all 

Service Module transportation support equipment, and the plans for transportation of the 

Service Module and Spacecraft Adapter to the processing and/or launch sites These plans 

shall be Included in ORO CEV-T-087, CEV Spacecraft Handlmg and Transportation Plan 

Deliverables 


The following module speCifiC Information IS collected in the DRDs specified In Section 2.7.2: 

• ORD CEV-T-087. CEV Handling and Transportation Plan 

The following module specific Information IS collected In the DRDs specified in Section 2.10 

• ORD CEV-T-086' Manufacturing and Assembly Plan 

• ORD CEV-T-088 CEV Imagery Planllmagery Deliverables 

6.2.6.1 SM Flight Hardware AlP 

a) The Contractor shall integrate, assemble, certify, acceptance test, and deliver flight Service 

Module meeting the requirements for the configurations below. 

b) The Contractor shall develop and implement plans detailing the design and construction of all 

Service Module transportation support equipment, and the plans for transportation of the 

Service Module to the processing and/or launch sites These plans shall be included in ORO 

CEV-T-087, CEV Spacecraft Handling and Transportation Plan 

c) The Contractor shall deliver 1 production SM (Including the SA) for Orion 1 and 1 production 

SM for Orion 2 (inclUding the SA) 

Page 79 of 119





d) The Contractor shall design, develop, produce, integrate, verify, validate, certify, document, 

and deliver Service Module GSE in accordance with all requirements in CXP-72000 04002, 

Systems Requirements for the Crew Exploration Vehicle Element (CEV SRD), and in this 

SOW, and In accordance With ORO CEV-O-008, Ground Systems Requirements, Plans, 

Reports, and Design Data, Volume II, Ground Systems End Item Implementation Plan and 

Report The Contractor shall plan for and deliver the GSE end Items In accordance with 

Attachment J-9. The Contractor shall use the following applicable documents for design and 

development of Contractor-provided GSE: 

o 

NASA-STD-5005B NASA Standard for Ground Support EqUipment (and 



e) The Contractor shall develop and update ORO CEV-O-008, Ground Systems Requirements, 

Plans, Reports, and Design Data, Volume III, Systems Operations and Maintenance Plan and 

Requirements Documentation, for the ground support equipment provided for the Service 

Module. 

f) The Contractor shall develop, maintain and deliver all technical models and draWings of the 

GSE associated With the Service Module in accordance with ORO CEV-T -003, CEV CAD 

Models, and ORO CEV-T-004, CEV Drawings 

g) The Contractor shall develop and update 2-0 and 3-0 Simulation models of the Contractorprovided 

Service Module and Contractor-provided Service Module GSE to assess 

clearances, placement, conflicts and the moving of hardware In accordance with ORO CEV 

T-003, CEV CAD Models. The Contractor shall develop and deliver these models In 

accordance with SOW Section 2.4. 

h) The Contractor shall develop and deliver ORO CEV-T-040, Acceptance Data Package, for 

each Contractor-provided Service Module GSE end item. 

I) The Contractor shall proVide Initial spares, concurrent with the delivery of the GSE end Items 

and in accordance With the provIsioning procedures in ORO CEV-T-011, Integrated Logistics 

Support Plan, and ORO CEV-T-012, LogIstics Support Analysis, for all Contractor-provided 

Service Module GSE (IDIQ) 

j) The Contractor shall complete the DD-250 for the Contractor-provided Service Module GSE 

and deliver the Contractor-provided Service Module GSE to the NASA-designated facilities. 

K) For Orion 1, the government shall provide a Developmental Flight Instrumentation system 

(DFI) and installation engineering to be installed by the Contractor (IDIQ) 

Deliverables 


The following SM & SA GSE data IS Incorporated in the DRD specified In Section 2.4: 

• DRD CEV-T-003 CEV CAD Models 

• DRD CEV-T-004 CEV DraWings 

The following SM &SA GSE data IS Incorporated In the DRD specified in Section 2 7 2' 

• ORO CEV-O-OOS' Ground Systems Requlrements,Plans, Reports, and Design Data 

• DRD CEV-T-040 Acceptance Data Package 

• DRD CEV-T-OS7' CEV Handling and Transportation Plan 

6.2.6.2 SM Test Article Design and Production 

For PA1, AA1, PA2, and AA2, the government Will provide the Separation Ring (SR) that 

performs the CM/SM Retention and Release (R&R) function and is the Interface to the Abort Test 

Booster. The following requirements only apply to contractor provided SR components, SMs and 

SAs. 

a) For AA 1, PA2, and AA2, the Contractor shall design, develop, and procure, bUild, verify, and 

deliver three (3) sets of CM/SM R&R mechanisms kits In accordance with the requirements 

and specifications developed in section 10.6.4, Flight Test Article (FTA) DDT&E, documented 

in ORO CEV-O-004, Flight Test ArtIcle (FTA) Design and Data Book. 

Page SO of 119





b) For AA 1, PA2 and AA2 the Contractor shall deliver three (3) CMISM Umbilical Mechanism 

Kits, as defined in Attachment J-9. 

c) For AA1, PA2, and AA2, the Contractor shall validate and verify the mechanisms kit design 

as speCified In ORO- CEV- T-015, Volume VII, Master Verification Plan, Flight Test Volume 

and documented in accordance with section 1064, FTA DDT&E, paragraph y 

d) For AA1 the Contractor shall design, develop, procure, and bUild a harness kit between the 

TO interface, CM/SR interface, and Contractor-provided mechanisms kit with the 

requirements and specifications developed In section 1064 FTA DDT&E; documented in 

ORO CEV-O-004, Test Article (FTA) Design and Data Book. 

e) For PA2 and AA2, the Contractor shall deSign, develop, procure, and bUild a harness kits 

between the T-O Interface, and Contractor-provided mechanisms kit with the requirements 

and specifications developed in section 10.6.4 FTA DDT&E; documented in ORO CEV-O- 

004, Test Article (FTA) Design and Data Book 

f) For Ares-1-Y, the contractor shall deliver one (1) production representative SM with mass 

simulators and ballast which supports meeting flight test objectives defined in CxP-72166. 

This SM and SA is unique In that it will be configured with the minimum functionality required 

to execute a LAS abort within 30 seconds of 1 st to 2 nd stage staging. The SM and SA are 

configured to achieve flight representative OMLlgeometry, mass, and dynamiC 

characteristics. 

g) Reserved 

h) Reserved 

I) The Contractor shall deSign, develop, produce, integrate, verify, validate, certify, document, 

and deliver SM FTA Unique GSE in accordance With all requirements In CxP 72000, Systems 


accordance With ORO CEV-O-008, Ground Systems Requirements, Plans, Reports, and 


Contractor shall use the follOWing applicable documents for deSign and development of 

Contractor-provided GSE. 

o 

NASA-STD-5005B' NASA Standard for Ground Support EqUipment (and 

associated Applicable Document Children as specified In Attachment J-3, 


j) The Contractor shall deliver a SM test article for a Ground Vibration Test at MSFC in 

accordance With CxP 72234, Integrated Vehicle Ground Vibration Test Task Plan. ThiS SM 

test article can either be simulated modules or residual test articles refurbished to support 

speCifiC reqUirements of the test Support for Integrated Vehicle Ground Vibration Test shall 

be in accordance with the Ares IVGVT & Orion Bilateral Exchange Agreement (BEA). 

k) The Contractor shall support and provide SM and SA ground test articles for a Ground 

Vibration Test at MSFC In accordance With CxP 72234, Integrated Vehicle Ground Vibration 

Test Task Plan. I) The Contractor shall develop ORO-CEV-O-002, Flight Test Article 

Requirements for Pad Abort and Ascent Abort tests. 

m) The Contractor shall develop and maintain ORO CEV-O-005, Flight Test Article (FTA) 

Validation and Verification Data Book, Identified In Section 10.6, for the SM FTA. 

Deliverables 


• DRD-CEV-T-015. FTA Volume Master Verification Plan (per Section 106) 

The following Module speCifiC Information IS collected in the DRDs speCified In Section 10.6.4. 

• DRD-CEV-D-002, Flight Test Article Requirements 

• DRD CEV-D-004' Flight Test Article (FTA) Engineering Design and Data Book 

• DRD CEV-D-005 Flight Test Article (FTA) Validation and Verification Data Book 

• DRD CEV-T-031. CEV ReqUirements Specification, for the Flight Test Article 

The following Module speCifiC information IS collected in the DRDs specified In Section 2.7 

• DRD CEV-O-008. Ground Systems ReqUirements, Plans, Reports, and Design Data, 


Page 81 of 119





6.3 Reserved 

6.4 Launch Abort System 

Launch Abort System includes the tasks required for the design, development, production, 

assembly, test, and certification of the Launch Abort System (LAS) and efforts to deliver the 

completed LAS for Spacecraft Integration. Development of unique launch abort system 

components and integration of all other subsystem components that make up the abort system is 

the responsibility of the launch abort system team 

6.4.1 LAS Management and Administration 

LAS Management and Administration Includes the efforts for planning, organizing, directing, 

coordinating, controlling, and approval processes used to accomplish Launch Abort System 

Development objectives 

a) NASA will maintain detailed oversight of all Launch Abort System design activities The 

Contractor shall maintain responsibility for delivery of a design that meets the requirements. 

The detailed process discussion to accomplish this can be found in CxP-72008, CEV Project 

Plan. The Contractor shall Include NASA personnel on all design teams established by the 

Contractor. 

6.4.2 LAS System Engineering and Integration 

LAS Systems Engineering and Integration consists of the efforts to lead the Launch Abort System 

overall system architecture definition and engineering functions. This includes the technical and 

management efforts of directing and controlling the Integrated engineering effort for the LAS 

ThiS also Includes the effort to coordinate LAS integration With the CEV integration functions 

desCribed In Section 2 

a) The Contractor shall define the modules, subsystems, components, and software Units that 

make up the Launch Abort System per the requirements and deliverables included in thiS 

section. 

b) The Contractor shall develop, maintain, and deliver all drawings and technical Computer 

Aided Design (CAD) models of the Launch Abort System, subsystems and components 

The Contractor shall use ORO CEV-T-003, CEV CAD Models, and ORO CEV-T-004, CEV 

Drawings, as the template for development and delivery of these Items 

c) The Contractor shall develop and maintain models and Simulations for the Launch Abort 

System, subsystems, and components uSing ORO CEV-T-002, CEV Engineering Models. 

d) The Contractor shall document and maintain ICD(s) for the government furnished products 

below' 

o Pyrotechnics Initiators 

e) Reserved 

f) The Contractor shall document Launch Abort System subsystem-level requirements using 

ORO CEV-T-031, CEV ReqUIrements Specifications. 

g) The Contractor shall document component-level requirements within the Launch Abort 

System uSing ORO CEV-T-031, CEV Requirements SpeCifications. 

h) The Contractor shall develop and use Integrated models With suffiCient fidelity to allow 

accurate trades to be performed for the design and development of the launch abort system 

to meet the requirements speCified by the CEV Project. 

i) The Contractor shall document all hardware Interfaces requirements using ORO CEV-T-035, 

Internal Interface ReqUIrement Document (IRD). The Contractor shall produce an IRD for 

each module that interfaces With another module The Contractor shall produce an IRD for 

each subsystem that Interfaces With another subsystem 

Page 82 of 119





j) The contractor shall develop ORO CEV-T-081 Launch Abort System Design and Data Book 

which contains detailed design descriptions for the LAS module, subsystems and major 

components, subsystem definitions, reqUirements analyses, operational analyses, as well as 

maintainability and testmg data. 

k) The Contractor shall develop and maintam the Launch Abort System portion of the CEV 

Specification and Drawing Trees, ORO-CEV·T·032. The top drawing shall be incorporated 

into the CEV System Drawmg Tree IIdentlfied in Section 2.2 

Deliverables 


• DRD CEV-T-031: Launch Abort System Requirements Specification 

• DRD-CEV-T-031' LAS Requirements Specifications 

• DRD CEV-T-032: CEV Specification and Drawing Tree for the Service Module and 

Spacecraft Adapter 

• DRD CEV-T-035 LAS Subsystem Internal Interface Documents 

• DRD CEV-T-OS1 LAS Design and Data Book 

The follOWing Module specific information IS collected m the DRDs specified m Section 2.4-3 

• DRD CEV-T-002' LAS Engineering Models 

• DRD-CEV-T-032 LAS Specification and Drawing Trees 

• The following dellverables are are separate Module dellverables and are Integrated by 

reference into the System level submittal in 2 3 

• DRD CEV-T-003.LAS CAD Models 

• DRD CEV-T-004' LAS Drawmgs 

6.4.3 LAS Subsystems 

This Section mcludes the work required to design, develop, produce, and test through certification 

and acceptance all Launch Abort System subsystems required to meet CEV module-level and 

interface requirements 

a) The Contractor shall design, develop, test, certify, and deliver Launch Abort System 

subsystem hardware complymg With all requirements in CXP-72000, Systems Requirements 

for the Crew Exploration Vehicle Element (CEV SRD) (including the listed applicable 

documents and those included m thiS Statement of Work (SOW) See Section 2.2). 

b) In support of the Launch Abort System avionics development effort, the Contractor shall 

provide the follOWing for each subsystem 

o 

o 


Validation of subsystem models/simulations used for flight software and 

integrated aVionics verification 

c) The Contractor shall provide system and LAS-level design definition data m the ORO CEV·T· 

033, Architectural Design Document and design defmltion and data down to the component 

level m the Subsystem DeSign and Data Books. 

d) The Contractor shall hold subsystem deSign reviews prior to the LAS system PDR and CDR 

e) The Contractor shall test (acceptance test only) and deliver flight spares for the Launch Abort 

System subsystems The Contractor shall provide a spare parts list as part of the ORO CEV· 

T·012, Logistics Support AnalYSIS (Recommended Spare Parts List). (IDIQ) 

f) The Contractor shall deliver one ship set of Launch Abort System flight spares (i e , 1 copy of 

every line replaceable Unit) (IDIQ) 

g) The Contractor shall deliver 2 production LAS for Onon 1 and Orion 2. 

h) The Contractor shall use the followmg standards and reqUirements documents for developmg 

all LAS subsystems' 

o 

JPR SOSO 5, JSC Design and Procedural Standards (and associated Children 

documents as specified m Attachment J-3, Applicable, GUidance, and 

Informational Documents List) (exclUSive of government "shalls") 

PageS30f119





o CXP-70024, Constellation Human Systems Integration Requirements (HSIR) 



i) The Contractor shall use the following standards for developing all LAS sUbsystems. 

o AIAA-S-080, AIAA Standard for Space Systems - Metallic Pressure Vessels 


o ANSIlAIAA-S-081A-2006, AIAA Standard for Space Systems - Composite 


Deliverables 


The following module specific information IS collected In the DRDs specified In Section 2.7.2 

• DRD CEV-T-012' Logistics Support AnalYSIS 

The following module speCific information is collected In the DRDs specified in Section 2 2 

• DRD CEV-T-033 Architecture DeSign Document 


6.4.3.2 LAS Command & Data Handling (C&DH) 

a) The Contractor shall document the deSign for all Launch Abort System C&DH hardware as 

speCified In ORO CEV-T-047, Avionics Design and Data Book Volume 1/ 

C&DHllnstrumentation Subsystem Data 

Deliverables 


The following module speCific Information is collected In the DRDs specified In Section 2.6.1 

• DRD CEV-T-047. AVioniCs Design and Data Book, Volume 11- C&DHllnstrumentation 


6.4.3.3 LAS Communications and Tracking (C& T) 

a) For the LAS, the Contractor shall prepare, deliver, and maintain DRD CEV-T-047, Avionics 

DeSign and Data Book Volume III - Communications and Tracking Subsystem Data 

Deliverables 

The following module speCifiC Information IS collected In the DRDs speCified In Section 2 6.1 

• DRD CEV-T -047: Avionics DeSign and Data Book, Volume III - Communications and 



6.4.3.5 LAS Electrical Power System 

a) The Contractor shall document the deSign for all Launch Abort System EPS Hardware as 

speCified in ORO CEV-T-059, Electflcal Power System (EPS) Design and Data Book 

b) The Contractor shall participate with the Constellation Program in the development of DRD 

CEV-T-060, Electrical Power Quality SpecifIcation Requirements Document. 

Deliverables 

The following module speCifiC information IS collected In the DRDs speCified In Section 2.6.5 

Page 84 of 119


Crew Exploratron Vehicle - (CEV) 



• DRD CEV-T-059: LAS Electrical Power System (EPS) Design and Data Book 

• DRD CEV-T-060 LAS Electrical Power Quality Specification Requirements Document 

6.4.3.6 LAS Mechanisms 

a) The Contractor shall document the design for all Launch Abort System mechanisms as 

specified in DRD CEV-T-061, Mechanical Systems Design and Data Book, and ORO CEV-T- 

062, Stress Analysis Report 

Deliverables 

The following module specific information IS collected In the DRDs specified in Section 2.6.6 

• DRD CEV-T-061 LAS Mechanical Systems Design and Data Book 

• DRD CEV-T-062' LAS Stress Analysis Report 

6.4.3.7 LAS Passive Thermal Control 

a) The Contractor shall develop thermal analytical models to support Launch Abort System 

thermal analyses 

b) The Contractor shall document the deSign for all Launch Abort System Passive Thermal 

Control as specified in ORO CEV-T-063, PTC Systems Design and Data Book, and ORO 

CEV-T-064, Passive thermal Control Mathematical Models and Documentation 

Deliverables 

The following module speCifiC Information IS collected In the DRDs specified in Section 2.6.7 

• DRD CEV-T-063' LAS Passive Thermal Control DeSign and Data Book (PTCDDB) 

• DRD CEV-T-064.LAS Passive Thermal Control Mathematical Models and Documentation 


6.4.3.9 LAS Structures 

a) The Contractor shall perform structural analysIs on all Launch Abort System structures, 

including pressure vessels, to show that all elements of the design such as the strength, 

strffness, structural stability, and life meet all speCified criteria for the anticipated loads and 

environments. 

b) The Contractor shall perform Launch Abort System loads and dynamiCs analyses and 

document the results In ORO CEV-T-067, Structural Loads Data Book 

c) The Contractor shall perform Launch Abort System stress and fatigue analyses and 

document the results In ORO CEV-T-062, Stress Analysis Report. 

d) The Contractor shall develop Launch Abort System models to support Integrated 

Constellation vehicle analyses as well as CEV loads and stress analyses. The Contractor 

shall deliver ORO CEV-T-068, Structures Mathematical Models and Documentation, which 

Will deliver and deSCribe the mathematical models used In the Launch Abort System system, 

subsystem, and component loads and stress analyses 

e) The Contractor shall Implement a fracture control program and Identrfyfracture critical parts 

to protect against catastrophic structural hazards associated with flaw presence, fatigue crack 

propagation and fracture The Contractor shall deliver and Implement ORO CEV-T-069, 

Fracture Control Plan, and ORO CEV-T -070, Fracture Control Summary Report. 

f) The Contractor shall use NASA-HDBK-7005, Dynamic Environmental Criteria, as a guidance 


development actrvlty 

Page 85 of 119





g) The Contractor shall use the following standards for designing and analYZing the Launch 

Abort System structures subsystem: 

o The Contractor shall use the applicable requirements In Contract Attachment J- 

3, Table 1 2, Applicable EnVIronmental Data Documents Requirements Data 

Book 

o JSC-62550, Structural Design and Venflcatlon Criteria for Glass, Ceramics and 




o 

o 

NASA-STD-5002, Loads Analyses of Spacecraft and Payloads 

NASA STD-(I)-5019, 9-12-2006, Fracture Control Requirements for Space 

Flight Hardware _(children documents are to be used by the contractor as a 

level of standards that must be met or exceeded If alternative standards are 

recommended by the contractor) 

h) The contractor shall produce an engineering development Launch Abort System structure for 

use in environmental testing (Ground Test Article) (See Section 2.6.9 h) 

i) The Contractor shall deliver an LAS Structural Test Article (used for structural venflcation 

static and dynamiC testing) via the DD149 process. 

Deliverables 


The follOWing module speCifiC Information is collected In the DRDs specified In Section 2 6 9 

• DRD CEV-T-062 LAS Stress Analysis Report 

• DRD CEV-T-067: LAS Structural Loads Data Book 

• DRD CEV-T-068. LAS Structures Mathematical Models and Documentation 

• DRD CEV-T-070. LAS Fracture Control Summary Report 

• DRD CEV-T -015 Structures Subsystem Volume Master Verification Plan 

6.4.3.10 LAS Propulsion 

a) The Contractor shall perform design, development, test, certification and delivery of all 

Launch Abort System propulSion systems and develop all propulSion related DRD products. 


activities and associated processes for all Launch Abort System propulSion systems in order 

to certify the propulsion systems for compliance with CEV component, subsystem, module, 

Spacecraft system, and vehicle-level requirements. The Contractor shall also design, 

fabricate and test Integrated Launch Abort System propulsion systems In order to evaluate 

and certify Integrated propulsion system hot fire performance for each propulsion application 

The Contractor shall also deSign, fabricate, and test integrated Launch Abort System 

propulsion systems to evaluate and certify Integrated propellant system storage and 

conditiOning designs and capabilities In order to evaluate and certify propellant conditiOning 

performances (See Section 2.6.10) 

c) The Contractor shall document the deSign for all LAS propulsion as speCified in ORO CEV-T- 

071, Propulsion Systems Design and Data Book 

Defiverables 


The follOWing module specific information IS collected in the DRDs speCified in Section 2.6.10 

• DRD CEV-T-071 LAS PropulSion Systems DeSign and Data Book 

Page86of119







6.4.3.13 Pyrotechnics 

a) The Contractor shall perform device level preliminary design reviews and cntlcal design 

reviews for each Launch Abort System pyrotechnic device not provided by NASA- The 

Contractor shall conduct development, qualification, and acceptance testing on all other 

pyrotechniC devices selected for the Launch Abort System. The Contractor shall conduct 

Phase I, Phase II, and Phase III technical reviews on all other pyrotechnic devices selected 

for the Launch Abort System per the requirements of JSC 62809, Rev C Constellation 

Spacecraft PyrotechniC Specification and JPR BOBO 5 Standards P1-P7. 

b) Launch Abort System specific stress analysis reports will be collected in the DRD (ORO CEV 

T -062, Stress Ana/ysls Report) specified In Section 2.6.13 for all pyrotechnic devices selected 

for the Launch Abort System 

c) The Contractor shall document the design for the Launch Abort System Module pyrotechnic 

subsystem as specified in ORO CEV-T-075, Pyrotechnic Subsystem Design and Data Book. 

Deliverables 

The follOWing module specific information IS collected In the DRDs specified in Section 2.6.13 

• DRD CEV-T-062 Stress AnalysIs Report 

• DRD CEV-T-075 Pyrotechnic Subsystem Design and Data Book 


6.4.3.15 LAS Guidance, Navigation, and Control (GN&C) 

a) The Launch Abort System GN&C requirements design and functional venflcatlon effort Will be 

performed through the use of specialized mode teams NASA Will co-lead with the Contractor 

In the development of detailed design requirements for the Launch Abort System GN&C flight 

system. The Contractor shall document the Launch Abort System GN&C reqUIrements In 

ORO CEV-T-031, CEV GN&C Subsystem Requirements Specification, and ORO CEV-T-048, 

Software Requirements Specification. The Contractor shall provide support to the following 

teams. 


o Flight Mechanics/Mission Design Mode Team 

b) The Contractor shall document the design for the LAS propulsion subsystem as specified in 

ORO CEV-T-078, GN&C Systems DesIgn and Data Book 

Deliverables 

The following module specific information is collected in the DRDs specified in Section 6 1 2 

• DRD CEV-T-031:LAS GN&C Requirements Specification 

• DRD CEV-T-031 LAS GN&C Requirements Specification 

The follOWing module specific Information IS collected in the DRDs specified in Section 6.5.2 

• DRD CEV-T-04B Software Requirements Specification 

The follOWing module specific Information is collected in the DRDs specified in Section 2.615 

• DRD CEV-T-07B: LAS GN&C Design and Data Book 

Page 87 of 119





6.4.3.16 LAS Wiring 

a) The Contractor shall develop a wiring database that proVides definition down to the level of 

pin-to-pin connectivity for all electrical harnesses and optical cables used on the Launch 

Abort System for ground, launch, flight, and recovery operations Including testing, verification, 

calibration, and maintenance The Contractor shall deliver the wIring database to NASA as 

ORO CEV-T-080, CEV Wiring Database and Reports The Contractor shall provide a 

hierarchical path/signal structure which links the wIring database to ORO CEV-T-046, CEV 


b) The Contractor shall develop, manufacture/fabricate, test, install, and certify all Launch Abort 

System wiring In accordance with DRD CEV-T-079, and ORO CEV-T-080, CEV Wiring 

Database and Reports 

Deliverables 

The follOWing module specific information is collected in the DRDs specified In Section 2.6.1 

• DRD CEV-T-046: CEV Data and Command Dictionary 

The following module specific Information IS collected In the DRDs speCified In Section 2.6.16 

• DRD CEV-T-079. LAS Wiring Plan 

• DRD CEV-T-080: LAS WIring Database and Reports 


6.4.5 LAS Test, Verification, and Certification 


qualification, certification, and acceptance of the Launch Abort System, subsystems, and 

components 

b) The Contractor shall perform qualification tests uSing ORO CEV-T-037, Qualification Test 


ORO CEV-T-017, Certification Data Package The Contractor shall perform qualification 

testing at component, LAS and intermediate levels of assembly as necessary to accumulate 

the data necessary for Launch Abort System certification. The Contractor shall produce a 

Certification Data Package for each component and each subsystem In the Launch Abort 

System, the Launch Abort System, and spacecraft Note. Software test documentation is 

handled In SOW section 6 2 1 1, Flight Software. The contractor shall develop a dedicated 

qualification inert Launch Abort System for system-level qualification testing. FollOWing the 

completion of system-level qualification testing, the contractor shall maintain configuration 

control of the dedicated qualification LAS and store it in an environmentally-controlled and 

access-controlled area 

c) The Contractor shall perform acceptance testing at the Launch Abort System and LAS 

component level using ORO CEV-T-039, Acceptance Test Procedures, and document the 

results uSing ORO CEV-T-040, Acceptance Data Package. An Acceptance Data Package 

shall be produced for Launch Abort Systems for Orion 1 and 2 

d) The Contractor shall hold Test Readiness ReViews (TRRs) before all formal verification 

activities The Contractor shall make subsystem and module test procedures available to 

NASA two weeks prior to each TRR. The Contractor shall invite NASA to witness all formal 

verification actIVIties, Including TRRs and test executions 

e) The Contractor shall conduct verification testing of all interface designs and requirements 

within the Launch Abort System (between modules, between subsystems, and between 

components) 

f) If the Contractor utilizes modeling and simulation to conduct analysis in support of verification 


Models, Simulations and Support Plan, and ORO CEV-T-002, CEV Engineering Models. 

Page 88 of 119





g) The Contractor shall provide the integration, test, & verification facilities required to test and 

certify the Launch Abort System and all LAS subsystems and components. The Contractor 

shall inVite NASA to witness all subsystem facility design reviews, test, venflcatlon, and 

certification activities. 

h) The Contractor shall provide the Integration, Test, & Venflcatlon (IT&V) facilities required to 

complete Integrated venfication of the Launch Abort System. The requirements for the IT&V 

facilities shall be derived from the products developed under Section 10.1, Spacecraft Test, 

Venflcatlon and Certification. LAS Master Verification Plan, per ORO CEV-T·015, that details 

the Contractor's plan for verifying, certifYing, and acceptance of Launch Abort System. 

Deliverables 


The follOWing module specific information is collected In the OROs specified In Section 10.2 

• ORO-CEV-T-015. LAS Volume Master Venflcatlon Plan 

The Contractor shall deliver the follOWing OROs for the Qualification Vehicle LAS, Incorporating 

all lower level element Qualification data. These OROs will be also collected Into the ORO 

specified in Sections 10.2 and 10.3 for the Integrated CEV 

• ORO CEV-T -017 Certification Data Package 

• ORO CEV-T-037. Qualification Test Procedures 

• ORO CEV-T-038' Qualification Test Report 

The Contractor shall deliver the following OROs for the Production Vehicle LAS, incorporating all 

lower level element acceptance data. These OROs Will be also collected Into the ORO specified 

in Sections 10.2 and 10 3 for the integrated CEV. 

• ORO CEV-T-039 Acceptance Test Procedures 

• ORO CEV-T-040: Acceptance Data Package 

6.4.6 LAS Assembly, Integration, and Production (AlP) 

a) The Contractor shall integrate, assemble, certify, acceptance test, and deliver flight Launch 

Abort System meeting the requirements configurations below 

b) The Contractor shall develop and Implement an imagery plan to provide Imagery (e. g., still 

photo, motion picture, digital Imagery, or video) of the Launch Abort System, and components 

dunng manufacturing, assembly, test, Integration, and close-out to document the hardware 

configuration. The Contractor shall Include the plan and imagery in ORO CEV-T-088, CEV 

Imagery Plan/Imagery Deliverables. 

c) Reserved 

d) The Contractor shall provide the launch abort system for the CEV launch abort flight tests 

and flight vehicles 

Deliverables 


The follOWing module specific information is collected In the OROs specified in Section 2.7 2 

• ORO CEV-T-087: CEV Handling and Transportation Plan 

The following module specific Information IS collected in the OROs specified In Section 2.10 

• ORO CEV-T-086 Manufactunng and Assembly Plan 

• ORO CEV-T-088' CEV Imagery Plan/Imagery Oeliverables 

6.4.6.1 LAS Flight Hardware AI&P 

a) The Contractor shall Integrate, assemble, certify, acceptance test, and deliver flight Launch 

Abort Systems meeting the requirements for the configurations below 


Launch Abort System transportation support equipment, and the plans for transportation of 

Page 89 of 119





the Launch Abort System to the processing and/or launch sites These plans shall be 

included in ORO CEV-T-OS7, CEV Spacecraft Handling and Transportation Plan. 

c) The Contractor shall deliver a production LAS for Orion 1 and a production LAS for Orion 2. 

d) The Contractor shall design, develop, produce, Integrate, verify, validate, certify, document, 

and deliver Launch Abort System GSE in accordance with all requirements in CXP-72000, 

Systems Requirements for the Crew Exploration Vehicle Element (CEV SRD), and in this 

SOW, and In accordance with ORO CEV-O-OOS, Ground Systems Requirements, Plans, 


Report. The Contractor shall plan for and deliver the GSE end items in accordance with 

Attachment J-9 -The Contractor shall use the following applicable documents for design and 

development of Contractor-provided GSE' 

o 

NASA-STD-5005B NASA Standard for Ground Support Equipment (and 



e) The Contractor shall develop and update ORO CEV-O-OOS, Ground Systems Requirements, 

Plans, Reports, and DeSign Data, Volume III, Systems Operations and Maintenance Plan and 

Requirements Documentation, for the ground support eqUipment provided for the Launch 

Abort System 

f) The Contractor shall develop, maintain and deliver all technical models and drawings of the 

GSE associated with the Launch Abort System in accordance with ORO CEV-T-003, CEV 

CAD Models, and ORO CEV-T-004, CEV Drawings. 

g) The Contractor shall develop and update 2-0 and 3-0 Simulation models of the ContractorprOVided 

Launch Abort System and Contractor-provided LAS GSE to assess clearances, 

placement, conflicts and the moving of hardware in accordance with ORO CEV-T-003, CEV 

CAD Models. The Contractor shall develop and deliver these models in accordance with 

SOW Section 2 4 

h) The Contractor shall develop and deliver ORO CEV-T-040, Acceptance Data Package, for 

each Contractor-provided Launch Abort System GSE end Item. 

i) The Contractor shall proVide Initial spares, concurrent with the delivery of the GSE end items 

and In accordance with the provIsioning procedures In ORO CEV-T-011, Integrated Logistics 

Support Plan, and ORO CEV-T-012, Logistics Support Analysis, for all Contractor-provided 

Service Module GSE (1010) 

j) For Orion 1, the Contractor shall provide the installation deSign, assOCiated hardware and 

installation of NASA provided LAS Development Flight Instrumentation (DFI) elements 

J) The Contractor shall complete the 00-250 for the Contractor-provided Launch Abort System 

GSE and deliver the Contractor-provided LAS GSE in accordance with Attachment J-9. to the 

NASA-deSignated faCilities 

Deliverables 


The follOWing LAS GSE data IS Incorporated in the ORO speCified In Section 2 4' 

• DRD CEV-T-003' CEV CAD Models 

• DRD CEV-T-004' CEV Drawings 

The following LAS GSE data IS Incorporated in the DRD specified in Section 2 7 2 

• DRD CEV-O-OOS' Ground Systems Requirements,Plans, Reports, and DeSign Data 

• DRD CEV-T-040. Acceptance Data Package 

• DRD CEV-T-OS7' CEV Handling and Transportation Plan 

6.4.6.2 LAS Test Article Design and Production 

The Contractor shall prOVide all the LASs 

a) For PA 1 and AA 1, the Contractor shall deSign and develop the developmental LAS's using 

the system, module, sub-system, and component level requirements and speCifications 

developed in Section 10.6.4, Flight Test Article (FTA) DDT&E ; documented in ORO CEV-O- 


b) For PA 1 and AA 1, the Contractor shall deliver two (2) prototype LAS. 

Page90of119





c) For PA2, and AA2, the Contractor shall design and develop the developmental LAS's uSing 

the system, module, sub-system, and component level requirements and specifications 

developed in Section 1064, Flight Test Article (FTA) DDT&E, documented In ORO CEV-O- 


d) For PA2 and AA2, the Contractor shall deliver two (2) development LAS 

e) For PA1, AA1, PA2 and AA2, and Ares 1Y the Contractor shall provide the installation 

design, associated hardware and installation of NASA provided LAS Development Flight 

Instrumentation (DFI) elements. 

f) For Ares-1 Y the Contractor shall deliver a production LAS 

g) The Contractor shall design, develop, produce, Integrate, verify, validate, certify, document, 

and deliver LAS FTA unique GSE In accordance With all requirements In CXP 72000 

Systems Requirements for the Crew Exploration Vehicle Element (CEV SRD), and In this 

SOW, and In accordance with ORO CEV-O-008, Ground Systems Requirements, Plans, 


Report. The Contractor shall use the following applicable documents for deSign and 

development of Contractor-provided GSE. 

o 

NASA-STD-5005B NASA Standard for Ground Support Equipment (and 

associated Applicable Document Children as speCified in Attachment J-3, 


h) The Contractor shall prOVide the LAS Side of a LAS to CM mechanical interface simulator 

(MIS) to be used for LAS/CM Retention and Release (R&R) mechanism fit checks, and 

functional tests 

i) The Contractor shall provide LAS propulsion data and an LAS OML in the post-Jettison 

configuration for the test range flight safety office to determine the nominal LAS Impact area. 

j) The Contractor shall perform/support a structural calibration test of the LAS/CM R&R 

structural Interface 

k) The Contractor shall deliver a LAS test article for a Ground Vibration Test at MSFC In 

accordance With CxP 72234, Integrated Vehicle Ground Vibration Test Task Plan. ThiS LAS 

test article can either be Simulated modules or residual test articles refurbished to support 

specific requirements of the test. Support for Integrated Vehicle Ground Vibration Test shall 

be In accordance With the Ares IVGVT & Orion Bilateral Exchange Agreement (BEA). 

I) The Contractor shall develop ORO-CEV-T-031, CEV FTA Requirements Specification for 

Flight Tests Ares 1 Y as defined In Secetion 10 6 4 

m) The Contractor shall design, develop, produce, integrate, verify, validate, document, and 

deliver LAS FTA Unique GSE In accordance with all requirements in CxP 72000, Systems 


accordance with ORO CEV-O-008, Ground Systems Requirements, Plans, Reports, and 


Contractor shall use the follOWing applicable documents for deSign and development of 

Contractor-provided GSE. 

o 

NASA-STD-5005B. NASA Standard for Ground Support EqUipment (and 



n) The Contractor shall validate and verify the flight test unique design as specified in ORO 

CEV- T-015, Volume VII, Master Verification Plan, Flight Test Volume 

Deliverables 


• DRD-CEV-T-015. FTA Volume Master Venflcatlon Plan (per Section 10.6) 

The following Module specific information IS collected In the DRDs specified in Section 10.6.4 

• DRD CEV-O-002: Flight Test Article Specification for Pad Abort and Ascent 

Abort FTAs 

• DRD CEV-T-031. CEV ReqUirements SpeCification, for the Flight Test Article for 

Ares-1Y 

The follOWing Module speCifiC Information is collected in the DRDs speCified In Section 2 7 

• DRD CEV-O-008 Ground Systems ReqUirements, Plans, Reports, and Design Data, 


Page 91 of 119





6.5 CEV Software 

CEV Software includes the tasks required for the design, development, production, assembly, 

test, and certification efforts to deliver the completed software for Spacecraft integration This 

element includes all aspects of software production from the early stages of system specification 

through maintenance of the system in the field 

6.5.1 CEV Software Management and Administration 

a) The Contractor shall design, develop, produce, Integrate, verify, validate, certify, operate, 

malntarn, document, and deliver CEV flight and accompanying ground and test/simulation 

software In accordance with all Block 1 A and Block 1 B requirements and in thiS SOW. 

6.5.2 CEV Software System Engineering 

a) The Contractor shall define, design, develop, test, qualify, integrate, verify, validate, deliver, 

and maintain all CEV software The plans for accomplishing this work shall be documented in 

ORO CEV-T-005, Software Development Plan. 

b) The Contractor shall justify the reuse of existing software, modification of existing software, 

and the development of new software In ORO CEV-T -005, Software Development Plan 

c) The Contractor shall, under CEV Project direction, participate rn coordinating with the NASA 

IV&V Facility in accordance with NASA-STD-8739.8, NASA Software Assurance (Chapter 6 

and 7) to plan for the participation of the NASA IV&V FacIlity in the software development 

lifecycle activities 

d) The Contractor and ItS subcontractors' organrzations associated with CEV software 

development responsibilities shall be at Software Engineering Institute Software Capability 

Maturrty Model Integration (CMMI) - SE/SW/lPPD Maturity Level III (Staged Representation) 

or higher prror to the CEV Preliminary Design Review This requirement does not apply to 

commerclal-off-the-shelf software procured for the CEV ProJect. 

e) The Contractor shall develop, update, and marntaln all software and software development 

tools under configuration management In accordance with the ORO CEV-T-006, Software 

Configuration Management Plan 

f) The Contractor shall develop and maintain electronic Software Development Folders for all 

flight, ground, and test software per ORO CEV-T-007, Software Development Folder. 

g) The Contractor shall develop and malntarn the Display Software Requirements Specification, 

usrng CxP 72242, Display Format Standards, and the CEV Display Format Dictionary, as 

applicable documents. This requirement specification shall be developed in accordance with 

DRD CEV-T-048, Software Requirements Specification. The display format dictionary shall 

be documented as an Appendix to DRD CEV-T-048, Software Requirements Specification 

h) The Contractor shall use the following standards for designing, developing, and testing all 

software. 

o NPR 7150.2 NASA Software Engrneerrng Requirements 

o NASA-STD-8739.8, NASA Software Assurance Standard (chapters 6 and 7) 

I) The Contractor shall allocate CEV Spacecraft requirements (section 2.2, Requirements 

Definition and Management) to the Computer Software Configuration Item (CSCI) level for 

the design of flight software and flight test software and maintain the allocations/requirements \ 

over the life of the system as development transltrons to production (Schedule B) and 

sustaining englneerrng (A future contract action). The Contractor shall produce a Software 

Requirements Specification (SRS) for each CSCI, using ORO CEV-T-048, Software 

Requirements Specification 

j) The Contractor shall allocate the requirements of each CSCI to the Computer Software 

Components (CSCs) and Computer Software Units (CSUs) levels ThiS design breakdown 

Page920f119





shall be documented In the Interface Control Documents (ORO CEV-T-029) and Software 

Design Description (ORO CEV-T-050) documents 

k) The Contractor shall plan, execute and document trade studies to identify criteria and prOVide 

resolution data for flight software Issues related to the selection of software, software tools, 

and hardwarelsoftware architectures (e g , operating system selections and bus 

architectures) The Contractor shall determine the ability of the CEV system to be 

upgradeable to the Block 2 configuration and perform trade studies to determine that 

memory, throughput, and processing margins are adequate to meet the Block 2 configuration 

requirements Trade study reports shall be documented per the requirements captured in 

ORO CEV-T-009, CEV Analysis Reports 

I) The Contractor shall perform configuration management of the flight and flight support 

software Within their configuration management system and prOVide "mirror Imaging" of all 

software development folders, source code, and documentation into ICE on a weekly baSIS 

m) The Contractor shall develop a flight software mission reconflguration process that details the 

Contractor's plan for flight-to-flight reconflguratlon of the flight software and ground facility 

software to meet miSSion-specific requirements The Contractor's process shall address the 

changing of software parameters to account for vehicle modifications, vehicle differences, or 

to specify values for mission-specific requirements The Contractor shall document the 

reconfiguration process plans, reqUirements, and design in ORO CEV-T-005, Software 

Development Plan, ORO CEV-T-048, Software Requirements Specification, and ORO CEV 

T -050, Software Design Description The Contractor shall develop tools to support the 

reconflguratlon process. 

n) The Contractor shall design, develop, produce, Integrate, verify, validate, certify, operate, 

maintain, document, and deliver a space-time partitioned real time operating system as part 

of the contractor's flight software implementation. 

0) The Contractor shall use a modular software architecture that evolves With the vehicle's 

capabilities. The Contractor's flight software architecture shall be deSigned to support system 

evolution through incremental enhancements Introduced within each block cycle. Each 

Incremental enhancement shall add supplemental functional capabilities including selectable 

autonomy, miSSion management, and systems management In a time frame compatible with 

the increaSing maturity of requirements and mission needs 

p) The Contractor shall ensure that ground systems software complies With Software 

Engineering standards identified Within thiS section. For ground operations, the Contractor 

shall develop and update the software and interface reqUirements specifications for 

Contractor-provided ground systems software In accordance with ORO CEV-T-048, Software 

Requirements Specification, and Implement the design processes and plans documented in 

the ORO CEV-T-005, Software Development Plan. 

q) The Contractor shall allocate the requirements of each Computer Software Configuration 

Item (CSCI) to the Computer Software Components (CSCs) and Computer Software Units 

(CSUs) levels for Contractor-provided GSE The Contractor shall document the software 

design breakdown in accordance With the ORO CEV-T-029, Interface Control Documents, 

and ORO CEV-T-050, Software Design Description. 

r) For FTA efforts, the Contractor shall develop and update the software and Interface 

requirements speCifications for Contractor-provided flight support software in accordance With 

ORO CEV-O-002, FlIght Test Article (FTA) SpecifIcatIOns 

s) For FTA Efforts, the Contractor shall allocate the requirements of each Computer Software 

Configuration Item (CSCI) to the Computer Software Components (CSCs) and Computer 

Software Units (CSUs) levels for FTA software The Contractor shall document the software 

deSign breakdown in accordance with the ORO CEV-O-004, Flight Test Article (FTA) 

Engineering Design Data Book defined in Section 10.64, FTA DDT&E. 

t) The contractor shall perform software build planning for each Identified build and shall 

document the bUild planning results in accordance With CEV-T-005, Software Development 

Plan, Volume 6 Software Build Plan 

u) The Contractor shall develop, maintain, and deliver ORO CEV-T-049, Monthly Software 

Metrics Report 

v) The Contractor shall develop, maintain, and deliver ORO CEV-T-056, Software User Manual 

Page 93 of 119





Deliverables 


• DRD CEV-T-005: Software Development Plan 

• DRD CEV-T-006 Software Configuration Management Plan 

• DRD CEV-T-007. Software Development Folder 

• DRD CEV-T-029' Interface Control Documents 

• DRD CEV-T-04B. Software Requirements Specifications 

• DRD CEV-T-049: Monthly Software Metrics Report 

• DRD CEV-T-050: Software Design Description 

• DRD CEV-T-056 Software User Manual 

The following software specific information IS collected in the DRDs specified In Section 10.6.4. 

• DRD CEV-D-002' Flight Test Article (FTA) Specifications 

• DRD CEV-D-004: Flight Test Article (FTA) Engineering DeSign Data Book 

6.5.3 CEV Software Production 

a) The Contractor shall develop all flight and ground support equipment software following the 

plans, processes, and standards outlined in DRO CEV-T-005, Software Development Plan, 

and section 6 5 2, Software System Engineering 

b) The Contractor shall develop and deliver the FTA software and accompanying test software 

(source code, executables, build procedures, and graphical models/block diagrams from 

Computer Aided Software Engineering Tools) per NPR 7150.2, NASA Software Engineering 

ReqUirements uSing class C and class D definitions and, requirements for thiS software. 

c) The Contractor shall maintain the FTA software and accompanying test software until the 

completion of testing as determined by the flight test matrix. 

d) The Contractor shall deliver Flight software (source code, executables, graphical models, 

block diagrams from Computer-Aided Software Engineering tools, and build procedures). 

Flight software deliveries shall start occurring at CDR and occur at a frequency of no more 

than every SIX months thereafter 

e) The Contractor shall develop, maintain and deliver ORO CEV-T-007, Software Development 

Folder, ORO CEV-T-050, Software Design Description; ORO CEV-T-051, Software Inspection 

and Peer Review Report, ORO CEV-T-055, Software Maintenance Plan, and ORO CEV-T- 

057, Version Description Document in support of the CEV Software production and delivery. 

f) In support of the Flight Test Program, the Contractor shall maintain ORO CEV-O-004, FTA 

Engineering Design and Data Book for Flight Test Article related software. 

Deliverables 


• DRD CEV-T-007: Software Development Folder 

• DRD CEV-T-050 Software Design Description 

• DRD CEV-T -051. Software Inspection and Peer ReView Report 

• DRD CEV-T-055 Software Maintenance Plan 

• DRD CEV-T-056: Software User Manual 

• DRD CEV-T-057 Version Description Document 

The following software speCifiC Information IS collected In the DRDs speCified In Section 10.6.4. 

• DRD CEV-D-004' Flight Test Article (FTA) Engineering Design Data Book 

6.5.4 CEV Software T&V 

a) The Contractor shall perform Unit testing of the flight software Unit test procedures (CSUlevel), 

CSU-to-CSU Interface, CSC-Ievel, and CSC-to-CSC interface tests will not be a 

deliverable to NASA; however, they shall be made available to NASA upon request via ORO 

Page 94 of 119





CEV-T-007, Software Development Folders The Contractor's software test plan shall be 

documented in ORO CEV-T-052, Software test Plan All CSCI-Ievel test procedures shall be 

documented In ORO CEV-T-053, Software Test Descnption The Contractor shall document 

test results in ORO CEV-T-054, Software Test Report. The Contractor shall develop and 

deliver ORO CEV-T-017, Certification Data Package for each CSCI and for the integrated 

flight software. The Contractor shall develop and deliver ORO CEV-T-040, Acceptance Data 

Package for each flight software deliverable. 

b) The Contractor shall perform unit testing of the Flight Support software. Unit test procedures 

(CSU-Ievel), CSU-to-CSU interface, CSC-Ievel, and CSC-to-CSC Interface tests will not be a 

deliverable to NASA, however, they shall be made available to NASA upon request via ORO 

CEV-T-007, Software Development Folders The Contractor's software test plan shall be 

documented In ORO CEV-T-052, Software test Plan. All CSCI-Ievel test procedures shall be 

documented in ORO CEV-T-053, Software Test Description The Contractor shall document 

test results In ORO CEV-T-054, Software Test Report. The Contractor shall develop and 

deliver ORO CEV-T-017, Certification Data Package, for each GSE software CSCI and the 

integrated GSE softwar&. The Contractor shall develop and deliver ORO CEV-T-040, 

Acceptance Data Package, for each Flight Support GSE software deliverable. 

c) The Contractor shall perform unit testing of the FTA software. Unit test procedures (CSUlevel), 

CSU-to-CSU interface, CSC-Ievel, and CSC-to-CSC Interface tests Will not be a 

deliverable to NASA; however, they shall be made available to NASA upon request via ORO 

CEV-T-007, Software Development Folders 

d) The Contractor shall develop and maintain ORO CEV-T-057, Software Verion Description 

Document. 

e) In support of the Flight Test Program, ORO CEV-T-0005, FTA ValidatIOn and Verification 

Data Book, for Flight Test Article related software 

Deliverables 


• DRD CEV-T-007. Software Development Folder 

• DRD CEV-T-040, Acceptance Data Package 

• DRD CEV-T-051: Software Inspection and Peer ReView Report 

• DRD CEV-T-052' Software Test Plan 

• DRD CEV-T-053: Software Test DeSCription 

• DRD CEV-T-054: Software Test Report 

• DRD CEV-T-057 Version DeSCription Document 

The foillowing software specifiC information IS collected in the DRDs idenified in Section 10.2 

• DRD CEV-T-017: Certification Data Package 

The follOWing software specifiC information is collected in the DRDs specified in Section 10.64 

• DRD CEV-D-005 Flight Test Article (FTA) Validation and Verification Data Book 

6.5.5 Independent Validation and Verification 

ThiS Contractor shall plan, coordinate and conduct Independent software validation and 

verification throughout the software development lifecycle. 

Page 95 of 119





7RESERVEO 

Page 96 of 119





8RESERVEO 

Page 97 of 119





DRESERVEO 

Page 98 of 119





10 CEV TEST ANO VERIFICATION 

Test and Verification Includes the activities, hardware, and software required to manage the CEV 

Project verification, certification, and acceptance processes and execute the Integrated 

spacecraft and multi-system testing and verification, including flight testing. Planning and 

execution (including the hardware and software used for execution) of testing and verification at 

the module, subsystem and component levels is contained In Sections 2 and 6 

10.1 Test and Verification Management and Administration 

CEV Test and Verification Management and Administration includes the efforts for planning, 

organizing, directing, coordinating, controlling, and approval processes used to accomplish CEV 

Test and Verification objectives. 

a) The Contractor shall provide information and technical data to support NASA's completion of 

a National Environmental Policy Act (NEPA) analYSIS for the CEV project In accordance with 

NPR 8580.1, Implementing the National Environmental Policy Act and Executive Order 

12114. 

10.2 Verification Management 

CEV Verification Management consists of defining and managing the policy, requirements, and 

processes for verifying that the CEV meets Project requirements This covers the work to certify 

the CEV System by Inspection, demonstration, simulation, analYSIS and/or test Verification 

Management Includes development of a plan for the verification and certification of the CEV 

System (hardware, firmware, and software) and associated subsystems and components. For 

Orion verification tests involving significant government furnished assets and in some case 

crewmembers, the testing roles and responSibilities Will be as listed In table 10 1 

Test Type NASA responsibilities Contractor Responsibilities 

Leads testing event • Provides test engineering data, 

• Integrates test 

necessary design data, Orion mockup 

objectives 

hardware specific to Orion EVA 

• Provides test crew, EVA verification requirement testing, and 

SUitS, EVA umbilicals, engineering support dUring test 

NBL basIc Orion mockup preparation and execution 

Demonstrations structure • Provides procedures With use of Crew 

• ResponSible for cost of test partiCipants specific to Orion 

test facility time 

verification test objectives 

• Responsible for engineering analysis 

necessary for verification requirement 

closure 

JSC Orion • Provides flight and • Leads testing event, integrates test 

Mockup Testsl ground crew for test, objectives, and provides crew training 

Demonstrations EVA/pressure SUitS, for test assets 

EVA umbilicals, and • Provides procedures With use of Crew 

Orion Qual. basic Orion mockup test participants specific to Orion 

Vehicle Tests structure verification test objectives. 

(Plumbrook SPF) • ResponSible for cost of • Provides high fidelity hardware specific 

CAlL Testing with 

Crew-in-the-Loop 


to verification test objectives and not 

already intrinsIc to the test article, such 

as high fidelity hatches on a mockup or 

non-GFE stowage Items. 

Page990f119



(Orion Project 

testing only) 



• Responsible for engineering analysis 


closure 

• Provides flight and • 

ground crew for test, 

EVA/pressure SUitS, 

Post-landing EVA umbilicals, and • 

Tests/Oemonstrati baSIC Orion mockup 

ons with Crew-in- structure • 

the-Loop (Orion • ResponSible for cost of 

Project testing test facility time 

only) 

• 

Leads testing event • 

• I ntegrates test 

objectives 

Post-landing • Provides flight and 

Tests/Oemonstrati ground crew for test, 

ons with Crew-in- EVA/pressure suits, 

the-Loop (CxP EVA umbilicals, and • 

Integrated testing) basic Orion mockup 

structure 

• 

CAIL-ESTL 

Testing involving 

other Cx Projects 

• ResponSible for cost of 


• Leads testing event 

• Integrates test 

objectives 

• Provides flight and 

ground crew for test, 

EVA/pressure SUitS, 

EVA umbilicals, ESTL 

and CAlL faCilities 

• ResponSible for cost of 


Table 10 1 CEV Verification Roles and ResponSibilities 

• 

• 

• 

Leads testing event, integrates test 

obJectives, and provides crew training 

specific to the test event 

Provides crew procedures specific to 

Orion verification test objectives 

Provides high fidelity hardware specific 

to verification test obJectives, such as 

high fidelity hatches or non-GFE 

stowage items. 

ResponSible for engineering analysIs 


closure 

Provides test engineering data, 

necessary deSign data, Orion hardware 

specific to Orion post-landing 

verification requirement testing, and 

engineering support during test 

preparation and execution 

Provides crew procedures speCifiC to 

Orion verification test objectives 

Responsible for engineering analysis 


closure. 

PrOVides crew training and crew 

procedures specific to the Orion test 

objectives 

PrOVides test configuration data and 

reqUired Orion test hardwarEHl9t 

s~eGlfleEl as G~e eR J ~ ~, J ~ 2 mF 

GFieR veFifiGatieR test e9jeGtives 

Provides engineering support dUring 

test preparation and execution, and 

closure of verification requirement 

satisfied by the Orion test objectives. 

10.2.1 Verification Requirements and Integration 

a) The Contractor shall develop a plan for the verification and certification of the CEV System 

(hardware and software) and associated subsystems and components by inSpection, 

demonstration, analYSIS, and test In accordance With ORO CEV-T-015, Master Verification 

Plan. The plan shall address the requirements defined in CXP-72097, Constellation Master 

Integration and Verification Plan. 

b) The Contractor shall document the verification method for each CEV System level 

requirement and all lower-level requirements In a verification matrix. The matrix will be 

Included as part of the corresponding specification, requirements, or interface document 

c) The Contractor shall develop and execute a Spacecraft Master Verification Plan for the 

Verification, qualification, certification, and acceptance of the CEV Spacecraft system, 

modules, subsystems, and components The Contractor shall use ORO CEV-T-015, Master 

Verification Plan, to develop the Spacecraft Master Verification Plan The Contractor may 

Page 100 of 119





use multiple volumes In the development of the Spacecraft Master Verification Plan to 

document the module, subsystem, and component level verification plans. 

d) The Contractor shall develop, update, and implement a GSE MVP for the approach, 

requirements, implementation strategies and associated test documentation to test, verify, 

activate, and qualify Contractor-provided GSE in accordance with ORO CEV-T-015, Master 

Venfication Plan 

Deliverables 


• DRD CEV-T -015. Master Verification Plan 

10.2.2 Integrated Vehicle Certification and Acceptance 

a) The Contractor shall develop Certification Plans per ORO CEV-T-016 for CEV equipment. 

The Contractor shall deliver Certification Data Packages per ORO CEV-T-017 and 

Certification Approval Requests per ORO CEV-T-018 in preparation for deSign certification 

milestones 

b) The Contractor shall accomplish qualification of the CEV System and its hardware and 

software elements In accordance with CXP-70036, Constellation Environmental Qualification 

and Acceptance Testing Requirements (CEQATR) Document as defined In ORO CEV-T-015, 

Master Verification Plan. Through rigorous testing, the Contractor shall confirm that the CEV 

System can deliver the planned performance over its expected service life when exposed to 

levels of stress with qualification margin above that defined in the predicted non-operating 

and operating enVIronments and conditions. Qualification by methods other than test shall be 

described in the Certification Plan and be approved by the Government. 

c) The Contractor shall accomplish acceptance testing of each flight hardware Item delivered In 

accordance with the CXP-70036, Constellation Environmental Qualification and Acceptance 

Testing ReqUirements (CEQATR) Document, including functional testing of each hardware 

and software operating mode at the most stressing operating conditions, enVIronmental 

testing at the maximum predicted non-operating and operating environments and final 

functional testing 

d) The Contractor shall define pass-fall criteria or acceptance tolerance bands, based on 

requirements. 

Deliverables 


• DRD CEV-T-016: Certification Plans 

• DRD CEV-T-017' Certification Data Package 

• DRD CEV-T-01S' Certification Approval Request 

The following integrated vehicle certification and acceptance Information IS collected in the RD 

specified In Sectlon10 2 1 

• DRD CEV-T -015 Master Verification Plan (MVP) 

10.2.3 Program Integrated Verification Support 

a) The Contractor shall partiCipate With Constellation Program SE&I in the development of 

integrated verification plans involVing multiple systems across the Constellation Program 

b) The Contractor shall participate in integrated verification activities InvolVing multiple systems 

across the Constellation Program including necessary in-space communication systems In 

accordance with CXP-7000S, Constellation Master Integration and Verification Plan 

c) The Contractor shall partiCipate In the development of Integrated verification plans with the 

ISS Program. 

Page 101 of 119





d) The Contractor shall partiCipate In Integrated verification activities with the ISS Program and 

in-space communication systems as required in the CXP-70031, International Space Station 

(ISS) to Crew Exploration Vehicle (CEV) IRD. 

10.3 Integrated Test and Verification 

Integrated Test and Verification consists of all tasks associated With ground testing at the 

Integrated vehicle (multiple modules or multiple subsystems) level and verifying that the 

integrated vehicle meets applicable Project requirements The test facilities and labs include 

hardware and software produced for Integrated ground testing of high-fidelity hardware provided 

by the CM and SM development teams (see Section 6). The test faCIlities and labs also provide 

for internal and external interface testing for risk reduction. 

10.3.1 Integrated Vehicle Hardware Testing 

a) The Contractor shall plan and conduct integration and Interface checkout testing to assure 

the assembly has been completed successfully and that hardware and software functional 

performance meets requirements 

b) The Contractor shall use flight-qualified software dUring verification testing of all subsystems 

and components 

c) The Contractor shall perform qualification tests using ORO CEV-T-037, Qualification Test 


ORO CEV-T-017, Certification Data Package The Contractor shall perform qualification 

testing at the CEV Spacecraft system, and intermediate levels of assembly as necessary to 

accumulate the data necessary for CEV Spacecraft certification. The Contractor shall 

produce a Certification Data Package for the spacecraft. The Contractor shall produce a 

Certification Data Package for each subsystem (end-to-end) The Contractor shall deliver 

Certification Approval Requests per ORO CEV-T-018 In preparation for design certification 

milestones. Note: Software test documentation is handled In SOW section 6.5.4, CEV 

Software T&V The contractor shall develop a dedicated qualification vehicle (CM/SM/lnert 

LAS) for system-level qualification testing FollOWing the completion of system-level 

qualification testing, the contractor shall maintain configuration control of the dedicated 

qualification vehicle and store It In an environmentally-controlled and access-controlled area. 

d) The Contractor shall perform acceptance testing at the spacecraft level using ORO CEV-T- 

039, Acceptance Test Procedures, and document the results uSing ORO CEV-T-040, 

Acceptance Data Package An Acceptance Data Package shall be produced for the 

spacecraft. 

e) The Contractor shall hold Test Readiness ReViews (TRRs) before all formal verification 

activities. The Contractor shall make spacecraft-level test procedures available to NASA two 

weeks prior to each TRR The Contractor shall Invite NASA to witness all formal verification 

actiVities, including TRRs and test executions. 

f) NASA Will prOVide faCilities with the capabilities to conduct, performance/functional, 

EMI/EMC, Shock, Sinusoidal/Random Vibration Vlbro-acoustics and System Thermal 

Vacuum testing to expected maximum predicted environment levels with appropriate 

margins. 

g) The Contractor shall verify software-controlled interfaces using flight-qualified software 

h) The Contractor shall conduct systems tests of the total spacecraft with the flight-qualified 

hardware and software. 

I) The Contractor shall conduct tests of ground-based CEV software/hardware systems that 

interface With flight systems uSing interface test equipment that has been shown to be a valid 

emulation of the flight systems before connecting With the flight systems. 

Page 102 of 119





j) The Contractor shall conduct tests using flight-qualified hardware and software for final 

acceptance of the ground-based CEV software/hardware systems used to perform launch 

and flight operations 

k) The Contractor shall include the following types of tests in their program: (1) ground, (2) flight, 

(3) development, (4) item, (5) functional, (6) Integration, (7) Hardware-In-the-Loop (HWIL), (8) 

Software-In-the-Loop (SIL), (9) Human-In-the-Loop, (10) nonoperating environment, (11) 

operating conditions & environment, (12) acceptance, and (13) qualification The Contractor 

shall document the test and verification program In the ORO CEV-T-015, Master Verification 

Plan. 

I) The Contractor shall provide support In order to conduct verification testing of all interface 

designs and requirements within the Spacecraft for those verification activities that are NASA 

led in NASA facilities with NASA Mockups and Contractor supported. 

Deliverables 


• ORO CEV-T-037. Qualification Test Procedures 

• ORO CEV-T-038: Qualification Test Report 

• ORO CEV-T-039' Acceptance Test Procedures 

• ORO CEV-T-040. Acceptance Oata Package 

The following Integrated Vehicle Hardware Testing specific information IS collected in the ORO 

specified in Section 10.2.2. 

• ORO CEV-T -015: Master Verification Plan (MVP) 

• ORO CEV-T-017. Certification Oata Package 

• ORO CEV-T-018 Certification Approval Requests 

10.3.2 Avionics and Software Testing 

Avionics and Software Testing consists of all tasks associated with Integrated testing of CEV 

avionics and software conducted In the CEV Avionics Integration Laboratory (CAlL), including 

hardware/software integration (HSI) testing The element Includes all hardware and software 

produced exclusively to support CAlL testing, with the exception of high-fidelity hardware 

provided by the Module development teams 

a) NASA will lead, and the Contractor shall participate In, the development of detailed 

reqUirements for the CEV AVIOniCS Integration Lab (CAlL) The purpose of the CAlL IS to 

perform integration testing of the CEV aVIOniCS hardware and software and associated 

internal and external CEV interfaces using flight aVIOniCS hardware, flight software, and an 

appropriate sUite of certified ground support tools/systems and software The Contractor 

shall document the CAlL reqUirements In ORO CEV-T-082, Spacecraft Test & Verification 

Facility System Requirements Document, the CAlL design in ORO CEV-T-083, Spacecraft 

Test & Verification Facility System Design Document, the CAlL certification plan In ORO 

CEV-T-084, Spacecraft Test & Verification Facility Certification Plan, and the CAlL 

certification results In ORO CEV-T-085, Spacecraft Test & Verification Facility Certification 

Package 

b) The Contractor shall develop a CAlL that at a minimum Includes the following: 

o A certified flight hardware sUite representing the CEV Spacecraft avionics 

(down to the firmware-level). 

o A simulator (inclUding hardware, software, and Interfaces) certified to represent 

the flight environment needed to verify the end-to-end performance of the data 

processing system. 

o Test capabilities to perform Integrated verification 

o PrOVide connectiVity to the ElectrOnic Systems Test Laboratory (ESTL) to 

support CaT RF testing 

o Integration of the above items 

Page 103 of 119





o Interfaces to Constellation element emulators. 

o Integration of the above items 

c) The Contractor shall develop, Install, certify, and deliver the CAlL, including all applicable 

operating procedures, instructions, and drawings, to NASA. The CAlL shall include two full 

operational rigs and a third development rig 

d) The Contractor shall deSign the CAlL to be reconfigurable for all spacecraft configurations. 

e) The Contractor shall deliver the follOWing 

o CAlL 

Acceptance Data Packages (ORO CEV-T-040) 

Deliverables 



• DRD CEV-T-082' Spacecraft Test & Verification Facility System ReqUirements Document 

• DRD CEV-T-083 Spacecraft Test & Verification Facility System DeSign Document 

• DRD CEV-T-084: Spacecraft Test & Verification FaCIlity Certification Plan 

• DRD CEV-T-085 Spacecraft Test & Verification Facility Certification Package 

10.3.3 Integrated EPS Testing 

System-level Integrated EPS Testing consists of all tasks assoCiated With Integrated test and 

verification of the CEV CM/SM Electrical Power System (EPS) in the Exploration EPS Testbed 

(EEST) The EEST includes all hardware and software produced exclusively for testing hardware 

provided by the CM and SM development teams 

a) The Contractor shall develop capabilities for testing power quality of the total CM/SM EPS, 

from power source outputs to electrical load connections, when Interfaced with CM/SM 

Internal and external hardware emulators, an EPS subset of ground support equipment, and 

EPS software. 

b) The Contractor shall perform reqUirements development (with NASA partiCipation and 

concurrence), design, integration, certification, and delivery of the EEST The Contractor 

shall document the CEV EEST requirements In ORO CEV-T-082, Spacecraft Test & 

Verification Facility System Requirements Document, CEV EEST design in ORO CEV-T-083, 

Spacecraft Test & Verification Facility System Design Document, CEV EEST certification 

plan In ORO CEV-T-084, Spacecraft Test & Verification Facility Certification Plan, and tRe 

CEV EEST certification results in ORO CEV-T-085, Spacecraft Test & Verification Facility 

Certification Package. 

c) The Contractor shall develop an EEST that at a minimum includes the follOWing. 

o CEV electrical test bed deSign for Integrated power quality testing In a NASAproVided 

and -operated facility. 

o Flight-like power generation, storage, and distribution/control hardwarer 

however, emulators that provide flight-like performance can be substituted for 

the power generation and storage hardware as defined by test objectives. 

o Flight-like CEV power interfaces to the EPS (includes interfaces with 

flight/flight-like electrical loads). 

o Electrical load emulators (Including hardware, software, and interfaces) that 

provide flight-like performance 

o Test capabilities to perform integrated verification and-accommodate the 

electrical testing of the follOWing 

• CEV contractor-provided equipment 

• Integrated or portable Internal/external GFE and payload electrical 

equipment 

• CEVelectrical interfaces required for ground maintenance, launch 

support, and other in-flight vehicles 

Page 104 of 119





• Capabilities for nominal and off-nominal testing (includes destructive 

testing with provIsions to isolate and protect the integrity of the test-bed) 

• CEV-Integrated EPS with critical test-point measurements without 

adversely affecting flight-like performance 

• Integration of the above items 

• Capabilities for command/control and testing of CM/SM Subsystems 

power quality within the scope of capabilities developed for CM/SM EPS 

testing. 

d) The Contractor shall develop, Install, certify, and deliver the certified EEST with all applicable 

operating procedures, instructions, and drawings, to NASA. 

e) The Contractor shall design the EEST to be reconflgurable for all spacecraft configurations. 

f) The Contractor shall deliver the follOWing. 

o EEST 

o Acceptance Data Packages (ORO CEV-T-040) 

o EEST DD250 

Deliverables 



• DRD CEV-T-082 Spacecraft Test & Verification FaCIlity System Requirements Document 

• DRD CEV-T-083: Spacecraft Test & Verification Facility System Design Document 

• DRD CEV-T-084. Spacecraft Test & Verification FaCIlity Certification Plan 

• DRD CEV-T-085' Spacecraft Test & Verification FaCility Certification Package 

10.3.4 Other Integrated Subsystem Testing 

a) The Contractor shall conduct verification testing of all Interface designs and requirements 

within the spacecraft (between modules, between subsystems, and between components). 

10.3.5 Interface Testing 

Interface testing consists of risk reduction testing for both external (With other Constellation 

elements), and internal (inter-module) Interfaces Interface verification testing is conducted by the 

modules (see Section 6). The element Includes development, maintenance, and management of 

unique test hardware 

10.3.5.1 Internal Interface Testing 

Internal Interface testing consists of risk reduction testing for Internal (inter-module) interfaces. 

Interface verification testing IS conducted by the modules (see Section 6). 

a) The Contractor shall conduct verification testing of all interface designs and requirements 

Within the spacecraft (between modules, between subsystems, and between components). 

10.3.5.2 External Interface Testing 

External Interface testing consists of risk reduction testing for external (with other Constellation 

elements) interfaces. Interface verification testing IS conducted by the modules (see Section 6). 

a) The Contractor shall support the Government In defining test objectives. 

b) The contractor shall support NASA In the development of BI-Lateral Exchange Agreements 

and Joint Test Plans. 

Page 105 of 119





c) The Contractor, In conjunction with NASA, shall allocate the functional, performance and 

Operational requirements contained in CEV System Requirements Document, CxP 72000, 

and Constellation External Interface ReqUirements. 

d) The Contractor shall support the Government In the development and maintenance of all 

detailed documentation for test activities to include specifications, design, implementation, 

Interface definitions, test and qualifications documentation on test articles and draWing trees. 

e) For the JOint Constellation element tests, the Contractor shall support periodic Technical 

Reviews, Plan and Procedure ReViews, and Test Readiness ReViews 

f) The Contractor shall support the Government In the development and maintenance of the 

test procedure documentation for test activIties 

g) The Contractor shall support the Government dUring test preparation, execution, and posttest 

tasks. The Contractor shall proVide support for the test execution. ThiS Includes console 

support at the launch site for all training events reqUIred to certify console operators, 

combined systems tests in support of test preparation, and test preparation through test 

configuration break operations. The Contractor shall be available real time with technical and 

quality resources to provide test execution and resolve deviations or anomalies as they may 

occur 

h) The Contractor shall support the Government in the development and maintenance of the 

test reporting documentation including data assessment and archive for test activities. 

10.3.5.3 Interface Test Equipment/Emulators 

a) The Contractor shall conduct tests of ground-based CEV software/hardware systems that 

Interface With flight systems using interface test equipment that has been shown to be a valid 

emulation of the flight systems before connecting with the flight systems. 

b) The Contractor shall develop, deliver, and sustain CEV System functional and physical 

interface slmulator(s) and emulator(s) in compliance with the relevant Interface Control 

Document (ICD) requirements for use by other Constellation projects (Including ClV and 

lSAM) to produce and evaluate the element Interfaces to the CEV. The Contractor shall 

Include operating instructions for the Interface slmulator(s) and emulator(s) in the ORO CEV· 

T·040, Acceptance Data Packagers) delivered with the Simulators and emulators 

c) The Contractor shall verify the CEV spacecraft with physical and functional Simulators and 

emulators prior to Integration with the other Constellation elements The Contractor shall 

define requirements for Constellation element-provided physical and functional interface 

simulators and emulators PhYSical and functional interface simulator and emulator 

requirements shall be delivered in accordance With ORO CEV·T·031, CEV 

Requirements Specification and ORO CEV·T·029, Interface Control Documents for ground 

support equipment The Contractor shall develop and maintain ORO CEV·T·035, Interface 

Requirements Document for each ORO CEV·T·029, Interface Control Document. 

d) The Contractor shall develop, deliver, and sustain functional and phYSical Interface 

slmulator(s) and emulator(s) in compliance with the relevant ICD reqUIrements for use by the 

ISS Program to produce and evaluate ISS Interfaces to the CEV The Contractor shall 

include operating instructions for the Interface slmulator(s) and emulator(s) in the ORO CEV· 

T·040, Acceptance Data Packagers) delivered with the Simulators and emulators 

e) The Contractor shall verify the CEV spacecraft With phYSical and functional Simulators and 

emulators prior to integration With the ISS The Contractor shall define requirements for ISSprOVided 

physical and functional interface simulators and emulators. PhYSical and functional 

interface simulator and emulator requirements shall be delivered in accordance with ORO 

CEV·T·031, CEV Requirements Specification, and ORO CEV·T·029, Interface 

Control Documents for ground support equipment. 

f) The Contractor shall deliver CEV emulators, and 00250, (Including target processor and 

flight software) for Interface testing, as required in Section 2.3. 

g) NASA will lead and the Contractor shall participate In the Post landing verification activities. 

h) The Contractor shall verify the CEV spacecraft with physical and functional joint test activities 

with Crew in suits in simulated operational donning and doffing of suits and egress /ingress 

Page 106 of 119





and suit retrieval events with both contractor and GFE supplied equipment prior to 

integration with the ISS 

Deliverables 


• ORO CEV-T-040: Acceptance Data Packages 

• ORO CEV-T-031, CEV Requirements SpeCification for ground support 

equipment simulators and emulators 

• ORO CEV-T-029, Interface Control Documents for ground support equipment sinulators 

and emulators 

• ORO CEV-T-035 Interface Requirements SpeCifications 

10.3.6 Program Integrated Test Support 

a) The Contractor shall support Level 2 (Constellation) Inter-project testing for CARD 

requirements verification and Program-level risk mitigation 

b) The Contractor shall support an integrated stack Ground Vibration Test (GVT) at MSFC in 

accordance with CxP 72234, Integrated Vehicle Ground Vibration Test Task Plan.(and 

associated Children documents as specified in Attachment J-3, Applicable Guidance and 

Informational Documents List). Support for Integrated Vehicle Ground Vibration Test 

shall be in accordance with the Ares IVGVT & Orion BEA. 

10.3.7 Verification Analysis and Trades 

a) If the Contractor utilizes modeling and Simulation to conduct analysis in support of verification 

specification compliance at the Integrated spacecraft level (Sections 2 and 6 address module 

and subsystem levels), the Contractor shall com ply with ORO CEV-T -001, Integrated Models, 

Simulations and Support Plan, and ORO CEV-T-002, CEV Engineering Models. 

10.4 Facilities 

ThiS section consists of all actiVities needed to prOVide the Integration, Test, & Verification 

facilities required to complete Integrated verification of the spacecraft. This consists of test and 

verification facility hardware and software needed to support integrated CEV testing involving 

multiple subsystems and modules. This does not Include test article and test support hardware 

and software. Outfitting, test article and test support hardware and software IS contained in 

Sections 10.3 and 6 

Page 107 of 119







10.4.3 Other Facilities 

a) The Contractor shall provide the integration, test, & verification facIlities required to test and 

certify the integrated CEV spacecraft The Contractor shall inVite NASA to witness all 

subsystem facIlity design reviews and certification activities 

b) The Contractor shall provide the Integration, Test, & Verification (IT&V) facIlities required to 

complete Integrated verification of the Integrated CEV spacecraft The requirements for the 

IT&V facilities shall be derived from the products developed under Section 10.1, Test and 

Verification Management and Administration 

c) Reserved 

d) The Contractor shall perform requirements development (with NASA participation and 

concurrence), deSign, integration, delivery of manufacturing, assembly and test equipment, 

verification, validation, qualification, and certification of manufacturing, assembly, and 

contractor test facilities The Contractor shall document the CEV facility requirements In ORO 

CEV-T-082, Spacecraft Test & Verification Facility System Requirements Document, the 

facility design in ORO CEV-T-083, Spacecraft Test & Verification Facility System Design 

Document, the facility certification plan in ORO CEV-T-084, Spacecraft Test & Venflcation 

Facility Certification Plan, and the facility certification results in ORO CEV-T-085, Spacecraft 

Test & Venflcation Facility Certification Package 

e) The Contractor shall provide support to NASA for development, deSign, Integration, delivery 

of manufacturing, assembly and test equipment, verification, validation, qualification, and 

certification of manufacturing, assembly, and contractor test facilities (IDIO). 

Deliverables 


• DRD CEV-T-082' Spacecraft Test & Verification Facility System Requirements Document 

• DRD CEV-T-083 Spacecraft Test & Verification Facility System DeSign Document 

• DRD CEV-T-084: Spacecraft Test & Verification FacIlity Certification Plan 

• DRD CEV-T-085' Spacecraft Test & Verification Facility Certification Package 

10.5 Ground Test Pathfinder Hardware 

Reserved 

10.6 Flight Test 

All flight test activities Will be managed and conducted by NASA, as a NASA-provided service to 

the Contractor, with support from the Contractor, for the Design, Development, Test, and 

Evaluation (DDT&E) phase. As the lead for this activity, NASA has defined flight tests for the Pad 

Abort (PA) and Ascent Abort (AA) testing of the Launch Abort Vehicle (LAV) In Table 10 1, and 

Ares sub-orbital and orbital flight tests In Table 102 The PA and AA tests are considered part of 

the Abort Flight Test Project (AFTP), and Ares 1 Y test is considered part of the I ntegrated Flight 

Page 108 of 119





Test Project (IFTP). Although it is anticipated that flight test planning, monitoring, and reporting 

will continue past the Ares flights, the scope of Section 10.6 of this SOW is all abort and 

integrated Ares flights prior to the first human launch (FHL). Tables 10.1 and 10.2 provide 

conceptual gUidance for the complexity required for each test article, and the primary supplier of 

the hardware. The actual compleXity required for each test vehicle will be determined by the 

vehicle design and the reqUired test objectives for each test 

SOW Section 10 6 covers the work associated With pre-production fidelity test hardware furnished 

by the Contractor and Contractor support requirements for Government-furnished test hardware. 

For thiS effort, the Contractor will support NASA In the development of test-unique non-production 

and production CEV requirements as appropriate. Per Table 10.1 and 102, the Contractor Will 

deSign, manufacture, verify, and deliver the Flight Test Articles (FTAs) appropriate for these tests. 

For PA-1 and AA-1, NASA shall provide the CM primary structure. The contractor shall provide 

the CM primary structure for PA-2, AA-2, and the remainder of the flight test program. For PA-1 

and AA-1, NASA will lead the systems engineering and integration (SE&I) effort, and the 

assembly, Integration and test/production (AIT/P) to be performed at Dryden Flight Research 

Center (DFRC). 

Figure 10.1, Abort Flight Test Matrix, shows the components to be used for the PAlAA flight test 

vehicles, and where appropriate, the primary supplier of the hardware. For the AA aborts flown 

on the ATB, the Interface between the FTA and the ATB is between the Sep Ring and the service 

module sub-section (SMSS) The SMSS IS an integral part of the ATB and Will be provided by 

the government The Sep Ring IS an Integral part of the FTA and is the minimum hardware 

required to perform the CM/SM retention and release (R&R) and umbilical disconnect functions. 

PA tests Will consist of the FTA components Without the ATB NASA will supply the ATB used in 

AA tests 1-3 as Identified in Table 10 1 An ATB will be supplied for the high altitude abort if the 

Ares launch vehicle IS not available. 

A test team led by NASA, With Contractor support, Will coordinate the development and 

implementation of the AFTP and IFTP. SOW Section 10.6 also Includes the Contractor support 

effort associated With PA-1 and PA-2, AA-1 thru AA-23, and Ares 1 Y flight tests 

For the Ares 1 Y flight tests, the Contractor will support NASA in the development of the test 

unique production CEV reqUIrements. ThiS requirement set will contain requirements that vary 

from the production CEV requirements set and configuration changes from the production CEV 

configuration. The requirement definition activity IS covered in this section of the SOW. The 

design, production, assembly, checkout and delivery of the spacecraft for these tests are covered 

in SOW Section 6, CEV Spacecraft Development, using the modified requirements developed in 

this sectlon.The Contractor operations support effort for the Orion/Ares flight tests is covered in 

SOW Section 2.7, Flight and Ground Operations Integration. 

The test unique GSE for the flight tests IS covered in SOW Section 10669 Flight Test Ground 

Support Equipment; SOW section 6.1.6.2, 6262, 6.4.6.2 Flight Test Article Design and 

Production All GSE that is non-Flight Test unique IS covered in Sections 2.7 2 e, 6 1.6.1, 6.2.6.1, 

6.4 6.1. 

The Contractor shall perform acceptance testing of Flight Test Articles document the results 

uSing ORO CEV-T-040, Acceptance Data Package 

Deliverables 

• The Contractor shall deliver the follOWing document(s): 

• ORO CEV-T-040: Acceptance Data Package Type 4 as tailored in J-2 DPD 

Page 109 of 119





10.6.1 Project Management and Tech Planning 

Reserved 

10.6.2 Flight Test Vehicle (FTV) SE&I 

Reserved 

10.6.3 Abort test Booster (ATB) DDT&E 

Reserved 

10.6.4 Flight Test Article (FTA) DDT&E 

ThiS consists of the effort to define the number, fidelity, system and interface requirements, and 

specifications of the FTAs necessary to complete the flight test effort. ThiS also Includes the 

design, development, systems engineering, integration, test, and verification of unique FTAs not 

provided by Section 6, CEV Spacecraft Development. Unique FT hardware manufactUring, 

production, and delivery IS contained In Section 10 6 6 

a) The Contractor shall refine the PA and AA tests defined In Table 10 1 The Contractor shall 

document the configurations in ORO CEV-O-001, FTA Defmition 

b) The Contractor shall support the Government in defining AFTP and IFTP flight test 

objectives. 

c) Based on the flight tests outlined In Table 10 1, Abort Flight Test Matrix, and Table 10.2, Ares 

Flight Test Matrix, the Contractor shall document the proposed fidelity of Contractor-furnished 

FTAs to complete the flight test effort and document the configurations in ORO CEV-O-001, 

FTA Definition. 

d) The contractor shall support NASA in the development of FTO-AFT-FTA-004, Flight Test 

Article System ReqUirement Document, for PA1 and AA1 

e) The Contractor, in conjunction With NASA, shall allocate the functional, performance and 

operational requirements contained In FTO-AFT-FTA-004, Flight Test Article System 

Requirement Document to the Flight Test Articles and Ground Support Equipment The 

Contractor shall document the requirements developed from this process In the FTA 

Specifications, ORO CEV-O-002, Flight Test Article (FTA) Specifications. 

f) Reserved 

g) The Contractor shall develop and maintain system requirements for PA2, and AA-2 as 

identified in Table 10 1, Abort Flight Test MatriX, and ORO CEV-O-001, FTA Definition. The 

Contactor shall deliver the requirements in ORO CEV-O-002, FTA SpecificatIOns. 

h) The Contractor shall develop and maintain module, subsystem, and component requirement 

specifications appropriate for Contractor-furnished hardware configuration based on the flight 

test objectives Identified In CxP-72166, Flight Test Vehicle Mission and Flight Objectives, in 

ORO CEV-O-002, FTA Specifications. The Contractor shall make available bidirectional 

traceability for these requirements 

i) The Contractor shall develop and maintain FTA specifications in ORO CEV-O-002, FTA 

Specifications and draWing trees for Contractor-furnished hardware and deliver them 

In ORO CEV-O-004, FTA Engineering Design Data Book. 

j) The Contractor shall develop and maintain all detailed documentation for Contractorfurnished 

flight test articles to Include speCifications, design, implementation, interface 

definitions, test and qualifications documentation on modules, subsystems, components and 

draWing trees and deliver them In ORO CEV-D-004, FTA Engineering Design Data Book. 

Page 113 of 119





The Contractor shall support the Government in the maintenance and development of all 

similar related detailed documentation for Government-furnished test articles 

k) The Contractor shall support the development of module, subsystem, and component 

reqUirement specifications appropriate for each NASA-furnished FT A configuration based on 

the flight test obJectives. 

I} The Contractor shall develop and maintain system specifications for the FTAs for Ares/Orion 

flight test articles. It is expected that these FTAs will have configuration changes from the 

CEV System ReqUirements as defined in Section 2.2 CEV Requirements Definition and 

Management and Sections 2 2, ReqUirements Definition and Management 6 1 2 CM System 

Engineering and Integration, 622 SM and SA System Engineering and Integration, 6.4.2 

LAS System Engineering and Integration The Contractor shall document the requirements 

in ORO CEV-T -031, CEV Requirements Specification. 

m) The Contractor shall define and proVide the internal Interfaces requirements between each 

module, subsystem, and computer software configuration Item as identified in ORO CEV-O- 

002, Flight Test Article (FTA) SpeCifications 

n) The Contractor shall develop the module-to-module and sUbsystem-to-subsystem IRDs/lCDs 

and document in ORO CEV-O-002, Flight Test Article (FTA) Specifications. 

0) NASA will prOVide the follOWing products to the Contractor. 

o CxP-72167, Orion Aerodynamic Database (for all phases of flight) 

o 

o 

CxP-72168, Orion Aerothermodynamic Database (for all phases of flight) 

FTO-AFT -FTV-011-PA 1, Orion Launch Abort Vehicle (LAV)Development Flight 

Instrumentation (DFI) Master Measurement List for PA-1 

p) The Contractor shall provide the installation deSign, associated installation hardware and 

installation of NASA-provided Development Flight Instruments (DFI) for the PA-1 LAS in 

accordance With FTO-AFT -FTA-024-PA 1, FTA-to-DFI Interface Control Document. 

q) NASA Will prOVide the Contractor the ATB-Induced enVIronments as defined in FTO-AFT 

FTA-001, Flight Test Article Environmental Requirements Document 

r) The Contractor shall provide NASA the CEV LAS Induced environments. 

s) The Contractor shall design the FTAs for the specific natural environments and Induced 

environments that the FTA must operate within and for which the FTA must be qualified, 

encompassing all phases of FTA production, testing and operation In all modes through 

disposal in accordance with FTO-AFT -FTA-001, Flight Test Article Environmental 

Requirements Document 

t) The Contractor shall define the FTA System Command, Control, Communications, and 

Information (C31) interoperabillty Interfaces to be compatible with the range and document 

these interfaces per ORO CEV-O-004, FTA Engineering Design Data Book. 

u) For the Abort Test Flights identified In Table 10 1, the Contractor shall support FTA Periodic 

Technical Reviews, and Flight Test Readiness Reviews. 

v) The Contractor shall document production and SR&QA standards per ORO CEV-O-004, FTA 

Engineering Design Data Book 

w) The Contractor shall ensure that the FTAs are built and tested In accordance With the 

Contractor's product assurance requirements and standards as documented in ORO CEV-O- 

004, FTA Engineering Design Data Book 

x) The Contractor shall document the as-bUilt FTAs per ORO CEV-O-004, FTA Engineering 

Design Data Book 

y) The Contractor shall verify the design as specified and documented In ORO CEV-O-005, FTA 

Validation and Verification Data Book, documenting the FTA validation and verification effort. 

z) For each Flight Test Article, the Contractor shall deliver to the NASA deSignated Integration 

faCility In accordance With Attachment J-9 

aa) NASA Will prOVide the Contractor the WSMR natural environments as defined in FTO-AFT 

FTA-001, Flight Test Article Environmental Requirements Document 

ab) The Contractor shall develop the Master Verification Plan Volume for the Flight Test Articles, 

ORO-CEV-T-015, Master Venflcation Plan 

Deliverables 


Page114of119





• DRD CEV-D-001: Flight Test Article (FTA) Definition 

• DRD CEV-D-002 Flight Test Article (FTA) Specifications 

• DRD CEV-D-004: Flight Test Article (FTA) Engineering Design Data Book 

• DRD CEV-D-005' Flight Test Article (FTA) Validation and Verification Data Book 

• DRD CEV-T -031. CEV ReqUIrements Specification for the FTA 

• DRD-CEV-T -015 Flight Test Article Volume Master Verification Plan 

10.6.5 Flight Test Operations DDT&E (IDIQ) 

Flight Test Operations DDT&E consists of the generic concepts, plans, procedures, and training 

for flight test operations and the design, development, systems engineering, integration, test, and 

verification of the ground hardware and software associated with flight test execution. The 

element includes all non-recurring costs associated With establishing and maintaining the flight 

test operations infrastructure. (IDIO) 

10.6.6 Flight Test Hardware Production 

Reserved 









10.6.6.9 Flight Test GSE Production 

Flight Test Article Ground Support Equipment (GSE) covered in this section includes the design, 

production, and delivery of the FTA-unique Mechanical GSE (MGSE) and Electrical GSE (EGSE), 

both hardware and associated software, needed for ground and flight operations to support all 

FTA components furnished by the Contractor In addition, the GSE covered in this section 

includes all LAS GSE 

Note. Work associated With GSE common With the production vehicle is covered In Section 

2 7 2 (e), Integrated Ground Support Equipment 

Page1150f119





a) The Contractor shall manufacture, deliver, and accept (including acceptance testing) the flight 

test GSE required for the Flight Test Program 

b) The Contractor shall design, develop, certify, produce, and deliver GSE for FTAs for the flight 

test defined in ORO CEV-O-002, FTA System Requirements, and the requirements in this 

SOW 

c) The Contractor shall design the GSE to support FTA C311nteroperability Interfaces to be 

compatible With the range and document these interfaces per ORO CEV-O-006, FTA GSE 

Data Book. 

d) The Contractor shall design and produce the FTA GSE required for all phases of FTA 

production, transportation, integration and checkout, and ground and launch processing 

e) The Contractor shall include FTA GSE in FTA PeriodiC Technical Reviews, FTA System 

Acceptance Reviews, and Flight Test Readiness Reviews. 

f) The Contractor shall document production and S&MA standards per ORO CEV-O-006 FTA 

GSE Data Book. 

g) The Contractor shall ensure that the GSE is bUilt and tested In accordance with the 

Contractor's product assurance requirements and standards as documented in ORO CEV-O- 

006 FTA GSE Data Book. 

h) The Contractor shall document the as-built FTA GSE per ORO CEV-O-006, FTA GSE Data 

Book 

i) The Contractor shall design and produce the FTA GSE reqwred for post-test FTA safing and 

recovery. 

j) The Contractor shall include FTA GSE requirements In ORO CEV-O-002, FTA 

Specifications and FTA GSE design in ORO CEV-O-006, FTA GSE Design Data Book. 

k) The Contractor shall complete the DD250 for the FTA GSE and deliver the FTA GSE to the 

NASA- designated test faCIlity In accordance with Attachment J-9 

I) The Contractor shall operate, maintain and update the FTA GSE for the duration of the flight 

test activity. 

m) The Contractor shall provide procedures for the FTA GSE. 

n) The Contractor shall provide training for the use of FTA GSE. 

0) The Contractor shall use a ground command, telemetry, and display system that IS 

compatible with the host range Use of data converters is unacceptable. 

p) The Contractor shall develop a common ground telemetry and data network that allows for 

software updates via the network Sites include the Contractor's home Site, the host range, 

and DRFC 

q) The Contractor shall provide the deSign of the ground transportation and handling (GT&H) 

equipment to NASA 

Note: NASA-LaRC will build the GT&H eqUipment to ship the LaRC provided CMs and LAS 

pathfinders 

r) The Contractor shall deliver the EGSE to the DFRC 

Deliverables 


• DRD CEV-D-002: Flight Test Article (FTA) Data Book 

• DRD CEV-D-006' Flight Test Article (FTA) GSE DeSign Data Book 

10.6.7 Abort Test Booster Production 

Reserved 

Page1160f119











10.6.8 Flight Test Operations (IDIQ) 

Flight Test operations includes the Contractor support for the flight test activities 

Flight Test Operations include the plans, processes, schedules, and products required to perform 

the flight design, analyses, and flight planning activities, flight products and procedure 

development; and execution of flight tests through Ares-1Y. Flight Test Operations will be the 

responsibility of NASA; however, it is essential that the Contractor provide the data and support to 

NASA for the development of the flight test operations products to prepare for and execute the 

CEV missions. 

Note. Flight Test Support for Orion flight tests are covered In Section 2.7. 

a) For PA-1 and AA-1, the Contractor shall provide side-by-slde support for the LAS, the 

avionics sub-system, the MGSE and the EGSE. As FTAs Increase In functionality and 

complexity (PA-2 and beyond), additional support shall be provided as appropriate Support 

Includes, but is not limited to, EGSE OFI telemetry database updates, EGSE software 

updates, and EGSE hardware spares and troubleshooting support AVionics and LAS flight 

software updates, regression testing, and troubleshooting support 

Note: ConSideration should be given to uSing Ground Operations personnel from KSC to 

augment the Ground Operations team at WSMR for training purposes. 

b) For PA-1 and AA-1, the Contractor shall provide initial training to NASA test team personnel 

on the LAS module, the CM aVIOniCS, the MGSE and the EGSE As FTAs increase in 

functionality and compleXity (PA-2 and beyond), additional training shall be prOVided as 

appropriate. 

c) The Contractor shall provide support for the test execution. ThiS Includes console support at 

the test range for all training events required to certify console operators, combined systems 

tests in support of launch preparation, and launch through recovery operations ThiS also 

Includes the Contractor operations and maintenance of the EGSE at the test range 

d) Reserve 

e) The Contractor shall proVide support for the Post Flight Test Report 

f) The Contractor shall proVide data to NASA for range safety in accordance With Section 2.7.4, 

Range Safety, and ORO CEV-O-007, Range Safety ReqUirements Documents. 

g) The Contractor shall support NASA-provided parachute and pyrotechnic Initiator integration 

into the FT A. 

h) The Contractor shall provide support for flight test planning, to Include module and subsystem 

procedures, ground processing, checkout, launch, recovery and refurbishment procedures, 

flight rules, launch commit criteria, and minimum eqUipment list required for launch. 

Page 117 of 119





10.7 Special Projects/Studies - T&V 

This section addresses unique projects or studies needed to support, faCIlitate, Improve, or 

enhance CEV test and verification completeness or effectiveness. 

a) The Contractor shall perform special CEV-related studies and analyses as directed by NASA. 

The Contractor shall define the resources required as part of their response to NASA's 

request for a task order plan The trade studies and analyses resulting from special studies 

shall also Include the impact to system safety and life cycle cost 

10.7.1 TPS Flight Test 

This is a study to determine the value, feasibility, and necessity of performing a flight test to prove 

the effectiveness of the TPS materials and application for lunar-return entries. 

Page 118 of 119





11 EOUCATION ANO PUBLIC OUTREACH (/OIQ) 

Education and Public Outreach Incorporates the development of the Education and Public 

Outreach portion of the CEV Project Provide for the EPO responsibilities In alignment with 

NASA's Strategic plan for Education This includes management and coordinated activIties, 

formal education, informal education, public outreach, media support, and web site development. 

Page 119 of 119






May 2009 

DATA PROCUREMENT DOCUMENT 

AND 

DATA REQUIREMENTS DOCUMENTS





1.0 INTRODUCTION 

1 1 Scope: Subject to the Rights In Data clause, this Data Procurement Document (DPD) 

sets forth the data requirements In each Data Requirements Description (DRD) and 

shall govern that data required by the DPD for the contract The Contractor shall 

furnish data defined by the DRD's listed on the Data Requirements List (DRL) by 

category of data, attached hereto, and made a part of this DPD. Such data shall be 

prepared, maintained, and delivered to NASA In accordance with the requirements set 

forth within this DPD In cases where data requirements are covered by a Federal 

Acqulsitron Regulation (FAR) or NASA FAR Supplement (NFS) regulation or clause, 

the regulation will take precedence over the DPD, per FAR 52.215-8. 

1.2 DPD Description: This DPD consists of an Introduction, a Statement of General 

Requirements, DPD maintenance procedures, a DRL, and the DRD's 

1.2 1 General Requirements The general requirements, as specified in paragraph 2.0 of this 

DPD, prescrrbe those requirements applicable to the preparation, maintenance, and 

delivery of data that are better defined in aggregate than in the individual DRD's 

1 22 Data Requirements List





1.2.3.4 To facilitate the usage and maintenance of the DPD, the DRD's have been divided Into 

sections In accordance with the above data categories 

1 2.3 5 The DRD's are filed by data category and are In alpha-numeric sequence as listed on 

the DRL pages that precedes the DRD's 

1 2 4 DPD Maintenance Procedures. Maintenance procedures define the detailed methods 

to be employed in maintaining the DPD. Detailed maintenance procedures are 

specified in paragraph 3 0 of thiS DPD. 

1.3 Data Types for Contractual Efforts' The types of data and their contractually applicable 

requirements for approval and delivery are' 

TYPE 

DESCRIPTION 

1 All issues and Interim changes to those issues require written approval from the 

requiring organization before formal release for use or Implementation 

2 NASA reserves a time-limited right to disapprove In writing any issues and 

interim changes to those Issues Data shall be submitted to the procuring activity 

for review not less than 45 calendar days prior to ItS release for use or 

Implementation. The Contractor shall clearly identify the release target date in 

the "submitted for review" transmittal. If the Contractor has not been notified of 

any disapproval prior to the release target date, the data shall be considered 

approved. To be an acceptable delivery, disapproved data shall be revised to 

remove causes for the disapproval before ItS release 

3 These data shall be delivered by the Contractor as required by the contract and 

do not require NASA approval However, to be a satisfactory delivery, the data 

must satisfy all applicable contractual requirements 

4 These data are produced or used during performance of the contract and are 

retained by the Contractor They shall be delivered when NASA requests it 

according to instructions In the request. The Contractor shall maintain a list of 

these data and shall furnish copies of the list to NASA when requested to do so 

5 These data are InCidental to contract performance and are retained by the 

Contractor In those cases where contracting parties have agreed that formal 

delivery is not required However, the Contracting Officer or the Contracting 

Officer's Representative shall have access to and can Inspect thiS data at its 

location In the Contractor's or subcontractor's faCilities, or In an electronic 

database acceSSible to the Government 

2.0 STATEMENT OF GENERAL REQUIREMENTS 

2.1 Applicable/Reference Documents' Documents Included as applicable documents In 

this DPD are the issue specified In the Statement of Work, and form a part of the DPD 

to the extent specified herein. Applicable documents listed in Item 13.2 of a DRD are 

applicable only to the preparation of the deliverable documentation described by that 

DRD. 

References to documents other than applicable documents In the data requirements of 

thiS DPD may sometimes be utilized, and shall be Indicated In 11, Remarks of the 

DRD These do not constitute a contractual obligation on the Contractor. They are to 


Page 3 of8





be used only as a possible example or to provide related information to assist the 

Contractor in developing a response to that particular data requirement 

2.2 Subcontractor Data Requirements 

2 2 1 The Contractor shall specify to subcontractors and vendors, if any, the availability 

source of all data reqUired for the satisfactory accomplishment of their contracts. The 

Contractor shall validate these requirements for documents when appropriate; where 

the requirement concerns other Contractor data, the Contractor shall provide his 

subcontractor or vendor with the necessary documents All such requests shall be 

accomplished under the auspices of the Contractor 

2 2 2 Reference to subcontractor data In the Contractor's responses IS permissible, providing 

the references are adequate and Include such Identification elements as title, number, 

reVISion, etc, and a copy of the referenced data is supplied with the response 

document at time of delivery to NASA 

2 3 Data Distribution. Format and Transmittal 

2 3.1 Distribution Distribution of required documentation shall be in quantities determined by 

the Contracting Officer Recipient names and email addresses shall be noted on a 

separate distribution list to be furnished by the Contracting Officer. The Contracting 

Officer's letter may Include other information pertinent to delivery of data, as reqUired 

23.2 Format 

2.3.2.1 Electronic Format: ElectroniC submission of data deliverables is reqUired. Electronic 

deliverables shall be printable where pOSSible The Contractor will not be required to 

deliver the data in a printable format for data deliverables such as binary executables, 

CAD models, mathematical models, etc which are not printable The versions of all 

submittals shall be confirmed prior to delivery such that the delivered version 

corresponds to the Intended delivered version 

Data Deliverables outlined by each DRD shall be delivered to NASA In the format 

specified by the NExlOM standard when the follOWing conditions are met: 

1) Modeling and Simulation data Input and output are used to support an analYSIS, 

2) thiS M&S data is presented Within a DRD document or deliverable report and does 

not exist in an Industry standard native format (I e NASTRAN). 

3) the data support analytical and test conclusions In analysis and test related 

deliverables and the delivered data are sufficient to support the conclusions made in 

the deliverable. 

NExlOM formats will be governed by the NExlOM Working Group NExlOM will govern 

both acceptable formats for the applicable data deliverables called out In each DRD as 

well as metadata that must accompany each delivery product NExlOM mandated 

meta-information will be expressed In XML and be governed by the NExlOM Working 

Group This accompanying metadata must be conformant to the follOWing standard: 

CXP-70041, Constellation Program NExlOM Standard for Tool, Model, and Simulation 

Data All applicable deliverables Will consist of at least the deliverable itself and 

accompanying meta-Information Model and Simulation (M&S) output data sufficient to 

support deliverable conclusions as defined above shall be delivered in NExlOM format 

for non-developed and heritage M&S tools as applicable and input data In native format 

that is used to generate the data shall be retained to support the conclusions Where 


Page 4 of8





new development M&S is utilized, input data shall also be supplied in NExlOM format 

as applicable relative to the above conditions. Any NExlOM data products that are 

required In addition to the applicability defined above will be managed through the 

Constellation Model and Simulation Working Group (CxMSWG). 

Software tools, models, or simulations made available to NASA shall be accompanied 

by an XML metadata document conformant to the following schema. CxP-70041, 

Constellation Program NExlOM Standard for Tool, Model, and Simulation Data. When 

a tool, model or simulation IS used to produce or support a ORO-governed deliverable 

or CEV program milestone, an Indication of the tools, models and simulations used 

shall be supplied conform ant to the CxP-70041, Constellation Program NExlOM 

Standard for Tool, Model, and Simulation Data metadata document accompanying the 

ORO or milestone data 

Data submittals in MS Word, MS Project, Excel or PowerPoint shall consist of a single, 

searchable Adobe Acrobat PDF file in addition to the native Word, Excel, Project, or 

PowerPoint electronic file(s). 

Where a single native format file is not possible, multiple files may be Integrated Into a 

Single ZIP file for submiSSion With the concurrence of NASA. The organization of the 

contents of the integrated ZIP file must be made readily apparent to the reader, and 

each file within the integrated product shall be clearly identifiable and traceable Within 

the organization of the integrated product 

All native format files delivered by the Contractor shall be readable by COTS software. 

Where the native file formats are not readable by COTS software, and With the 

concurrence of the NASA COTR, the Contractor shall deliver the application (source 

code and executable) required In order to read the native file format The preferred 

format for CAD data Will be Pro Engineer. The Contractor may request an alternative 

format 

2.3.2.2 Hardcopy Format In addition to the electroniC submittal, one hardcopy package of 

specific data 

dellverables shall be delivered to the NASA Contracting Officer for the Government 

contract file ORO's which require hardcopy submittals will indicate this in Item 13.4, 

Format. The hardcopy package shall consist of the Contractor's Transmittal Memo and 

one copy of the data deliverable 

2.33 Transmittal 

2331 Data shall be transmitted to NASA via the Integrated Collaborative Environment (ICE) 

in accordance with Attachment J-14, hardcopy, or other mechanism agreed to by the 

Contracting Officer, COTR, and Project representatives who are responsible to receive, 

Index, and store the data deliverables. 

2.3.3.2 Data Transmittal Package Each data transmittal package shall include. 

a. Transmittal memorandum that specifies the meta-data below for each data 

transmittal 

1. Contract number 

2 Data ReqUirements DeSCription (ORO) number 

3. ORO data type (speCified In Item 3 on the ORO) 

4 SubmiSSion date or milestone being satisfied. 

5 Document number and revision. 

6 Document title. 


Page 5 of8





7 File names of all files being delivered, multiple files per document must be 

clearly related to the document 

8. Distnbutlon (as defined by the Contracting Officer's letter). 

9 Requested response date 

b. Printable electronic files or hardcopy data 

c. NExlOM meta-data document per section 2 3 2 1 

234 Use of the ICE Repository See J-14, ICE Operating Environment for details on using 

the ICE repository 

2.4 Pnntlng All printing, duplicating, or binding shall be in accordance with NFS 1852.208- 

81, Restrictions on Pnntlng and Duplicating Printing of formal reports and Type 1 and 

2 data In book format shall be in accordance with the following general specifications: 

a. Method of reproduction - offseVxerography 

b. Finished size - 81/2" X 11". 

c. Paper - 20-pound opaque bond. 

d. Cover - Litho cover stock 

e. Pages will be pnnted on both sides, blank pages will be avoided when possible. 

f 

Oversize pages will be avoided when possible, but if necessary will be folded 

to 81/2" X 11" 

g. Binding shall be the most economical method commensurate with the size of the 

report and ItS Intended use. 

2 5 Contractor's Internal Documents. The Contractor's internal documents shall be used to 

meet the data requirements of this DPD unless a specific format is required by the 

applicable DRD The format being used by the Contractor's Internal documents shall be 

readable by COTS tools 

2 6 Document Identification. Type 1 and 2 documents published by the Contractor and 

submitted In response to the data requirements of this DPD shall be identified within an 

organized identification numbenng system prescribed to NASA by the Contractor and, If 

applicable, as approved by NASA. This number, change legend, date, and title 

constitute the minimum identification of the specific document and shall appear on the 

cover and title page. The contract number shall also appear on the cover and title page 

as separate markings The originator and organization shall be Included on the title 

page. The document number, change legend, and date shall appear on each page of 

the document In the front matter of each document, Identify the DPD number and 

applicable DRD number(s} required for document preparation. Successive Issues or 

revisions of documents shall be Identified in the same manner as the basIc Issue and 

shall have appropriate change Identification Drawings and ECP's are excluded from 

the marking provIsions of this paragraph. All Type 1 documentation, excluding 

configuration management requirements, will be marked "PRELIMINARY PENDING 

NASA APPROVAL," and once approved shall be reissued with "APPROVED BY 

NASA" and the date and approval authonty annotated on the cover only. 

2 7 Reference to Other Documents and Data Deliverables In Data Submittals All 

referenced documents shall be made readily available to the cognizant NASA 

organization upon request The Contractor should make sure that the references are 

available to NASA In a manner which does not incur delays in the use of the response 

document. Reference may be made, Within one data submittal, to other data submittals 

delivered In response to this DPD in those cases where the data reqUired by one DRD 

may have been delivered by the Contractor in response to another DRD. The 

reference to previously-submitted data shall Include the applicable DRD number, data 

submittal version date, and location Within the referenced document. 


Page 6 ofS





2.8 Maintenance of Type 1 Document Submittals 

2.8.1 Revisions of Type 1 documentation may be accomplished either by Individual page 

revision or by a complete reissue of the document Identified In accordance with 

requirements of 2 7 above, with the exception of drawings (which shall be revised in 

accordance with contract configuration management requirements). 

2.8 2 Individual page revisions shall be made as deemed necessary by the Contractor or as 

directed by the Contracting Officer. 

2.8.3 A Type 1 document shall be completely reissued when, In the opinion of the Contractor 

and/or NASA, the document has been revised to the extent that It IS unusable in its 

present state, or when directed by the Contracting Officer. When complete reissues 

are made, the entire contents of the document shall be brought up to date and shall 

incorporate revised pages. All revisions shall be recorded. A revision log shaliidenbfy 

complete reissues except for periodiC reports and documents which are complete 

within themselves as final 

284 Changes of a minor nature to correct obvious typing errors, misspelled words, etc., 

shall only be made when a technical change is made, unless the accuracy of the 

document is affected. 

2.8.5 All revised pages shall be Identified by a revision symbol and a new date. Each 

document shall contain a log of revised pages that will identify the revIsion status of 

each page with the revision symbol. This list shall follow the table of contents in each 

document The line or lines revised on a given page shall be designated by the use of 

vertical line In the margin of the page, and the change authority shall be indicated 

adjacent to the change 

2.8.6 Contractor Type 1 documents shall not be submitted containing pen and ink markups 

which correct, add to, or change the text, unless schedule problems exist and approval 

IS obtained In writing from the Contracting Officer. Such markups, however, shall not 

exceed 20 percent of the page content and shall be acceptable provided that the 

reproduced copies are legible In addition, hand-drawn schematics, block diagrams, 

data curves, and Similar charts may be used in original reports in lieu of formally 

prepared art work, as long as legibility of copies IS not Impaired. Acceptability will be 

determined by the Contracting Officer 

30 DPD MAINTENANCE PROCEDURES 

3 1 NASA-Initiated Change. New and/or revised data requirements Will be Incorporated by 

contract modification to which the new or revised portion of the DPD will be appended 

The Contractor shall notify the Contracting Officer in the event a deliverable data 

requirement is imposed and is not covered by a DRD, or when a DRD IS changed by a 

contract modification and for which no revIsion to DPD IS appended. In such cases, the 

Contractor shall submit the requested changes to NASA for approval See paragraph 

3 3 1 for change procedures 

32 Contractor-Initiated Change' Contractor-proposed data reqUirements, or proposed 

changes to existing requirements shall be submitted to NASA for approval. 

3 3 DPD Change Procedures 


Page 7 of8





3.3.1 Changes to a contractual issue of this DPD will be Identified by NASA on the Document 

Change Log and Page Revision Log. The actual revised material on the DPD page will 

be identified by placing a heavy vertical line in the right-hand margin extending the 

entire length of the change In addition, the numerical control number of the 

contractual direction authorizing the change shall be placed adjacent to the vertical 

revision line These revIsion Identifiers shall be used to reflect the current revIsion only; 

any prevIous symbols on a page will be deleted by the current revIsion. 

3.3.2 The date of the contractual direction paper, e g., Change Order, Supplemental 

Agreement, or Contracting Officer's letter shall be entered under the "Status" column 

of the Page RevIsion Log adjacent to the affected page or DRD number, and in the "as 

of' block The date that was In the "as of' block Will be entered In the "Superseding" 

block. 

3.3.3 The Document Change Log entitled "Incorporated Revisions" will be changed to 

Indicate the number, portions affected, and associated Supplemental Agreement 

number, if applicable. 

3 3.4 The Document Change Log entitled "Outstanding Revisions" is changed periodically to 

indicate outstanding Change Orders and Contracting Officer notification letters 

3.4 DPD Reissues 

3.4.1 When conditions warrant, the DPD will be reissued by NASA and will supersede the 

eXisting DPD In its entirety. Reissues will be issued by contractual direction. 

3.4.2 All reviSion symbols (vertical lines and contractual direction control numbers) will be 

removed from all pages; revIsion dates shall remain In the Date ReVised block on DRD's 

that have been revised. The Issue symbol, which Will commence With "A" and progress 

through "Z," Will be entered In the DPD Identification block of each DRD page of the DPD 


Page 8 of8

NNJ06TA25C Attachment J-2 



DATA REQUIREMENTS DESCRIPTION (DRD) 

1. 

3. 

6. 

7. 

PROGRAM: CEV 2. DRDNO.: CEV-B-003 

DATA TYPE: 3 4. DATE REVISED: May 2009 

5 PAGE. 1 

TITLE. Cost Performance Report 

DESCRIPTlONIUSE: 

This Data Requirements Descr~ption (DRD) contains the format and content 

preparation instructions for the data product generated by the specific 

and d~screte task requirement as delineated in the contract. This report 

consists of two maJor sections. The first section is the Contractor 

Integrated Management Schedule and the second section contains the cost 

reporting formats. 

a. The Integrated Master Schedule (IMS) is an integrated schedule 

containing the networked, detailed tasks necessary to ensure successful 

project execution. The IMS is vertically traceable to the Integrated 

Master plan (IMP) the Work Breakdown Structure (WBS) , and the Statement 

of Work (SOW). The IMS shall be used to verify attainab~lity of contract 

objectives, to evaluate progress toward meeting project objectives, and 

to integrate the proJect schedule activities with all related components. 

This DRD is applicable to development, major modification, and low rate 

initial production efforts; ~t ~s not typically applied to full rate 

production efforts. 

a.1. The pr~me Contractor is required to include significant 

external interfaces and critical items from suppliers, teammates, or 

other detailed schedules that depict significant and/or critical elements 

and Government furnished equipment or information dependencies for the 

entire contractual effort ~n a single ~ntegrated network. The 

determ~nation of significant and critical shall be defined and 

documented, and agreed to by NASA. 

a.2. The IMS shall be statused according to the Contractor's 

management control system and shall be submitted no less frequently than 

monthly. If a Contract Performance Report (CPR) ~s requ~red, the IMS 

shall be statused and subm~tted to the procuring act~vity prior to or 

concurrently with CPR Formats 1-5 (as applicable) The IMS may reflect 

data either as of the end of the calendar month or as of the Contractor's 

accounting period cutoff date, provided it is consistent and traceable to 

the CPR (if applicable). When subcontractor schedule data reflects a 

different status date than the prime Contractor's schedule status date, 

these status dates shall be descr~bed in the analysis section of the IMS. 

b. The five cost report~ng formats contain data for measuring 

contractors' cost and schedule performance on the NASA Crew Exploration 

Veh~cle (CEV) acqu~sition contract. Format 1 provides data to measure 

cost and schedule performance by product-oriented Work Breakdown 

Structure (WES) elements, the hardware, software, and services the 

Government ~s buy~ng. Format 2 prov~des the same data by the 

Organization Breakdown Structure (OBS) elements. Format 3 provides the 

budget baseline plan against which performance is measured. Format 4 

provides staffing forecasts for correlation with cost estimates. Format 

5 is a narrative report used to explain significant cost and schedule 

variances and other identified contract problems and topics. CPR data 

shall be used by NASA project management to: (1) integrate cost and 

schedule performance data w~th technical performance measures, (2) 

identify the magnitude and impact of actual and potential problem areas 


CEV-B-003 Page 1 of21





causing significant cost and schedule variances, and (3) provide valid, 

timely project status information to higher management. The CPR is a 

management report. It provides tlmely, reliable summary-level data with 

which to assess current and projected contract performance. The CPR's 

primary value to NASA is its ability to reflect current contract 

performance measurement status and reasonably project future contract 

performance. It lS important that the CPR be as accurate as possible so 

it may be used for its intended purpose, which is to facilitate informed, 

timely decisions. It will be used by the NASA component staff, including 

project and program managers, engineers, cost estimators, and financial 

management personnel, to confirm, quantify, and track known or emerging 

contract problems and serve as a basis for communicatlng wlth the 

contractor. The CPR data shall accurately reflect how work is being 

planned, performed, and measured and shall be consistent with the actual 

contract status. 

c. The CPR shall be used to obtaln cost and schedule performance 

information Refer to the Federal Acquisltlon Regulation (FAR) or 

Federal Acquisition Regulatlon Supplement clause on contract. The CPR 

data elements shall reflect the output of the contractor's integrated 

management system which shall be complaint wlth the American National 

Standards Institute/Electronic Industries Alliance Standard 748 

(ANSI/EIA-748), Earned Value Management Systems (EVMS) (current version 

in effect at time of contract award) 

c.l The CPR is a crucial element of NASA's Continuous Cost-Risk 

Management (CCRM) process (Step 9) providing the NASA ProJect Manager 

high quality, tlmely cost-risk feedback for cost management lmprovement. 

Whereas the level of detail to be reported in Format 1 normally will be 

at level three of the WBS, for CCRM lmplementation purposes earned value 

cost performance data for medium and hlgh-risk WBS elements listed below 

shall be reported on CPR Formats 1 & 2 until such time as both government 

project management and the contractor agree that they no longer represent 

medium or high risks. This reporting should be at a level that is 

adequately sensitive to performance measurement indicators to ensure 

earliest identification of cost and schedule problems caused by the 

source rlsks. The Contractor shall identify known risks if not provided 

in the list above and track their performance measurement in the same 

manner. NASA reserves the right to amend the above list at the 

appropriate time during source selectlon, at Final Proposal Revision 

(FPR) , and at any time during the effort as new information on risks 

becomes available. NASA and the Contractor shall periodlcally review and 

adjust as necessary WES reporting levels on Format 1 to ensure they 

continue to provlde appropriate visibility without requiring excessive 

information. If there lS a slgnlficant problem at a lower level, detailed 

reportlng for that WBS element shall be required until the problem is 

resolved. 

c.2 All five formats are mandatory in all cases. 

c.3 Slgnificant variances require problem analysis. The thresholds for 

significant varlances are: 

Cum-to-Date Current Month At Completion 

Schedule Varlance +/-10% and +/-$100k +/-10% and +/-$50k 

Cost Variance +/-10% and +/-$100k +/-10% and +/-$50k +/ -$5M 

8. DISTRIBUTION: As determined by the Contracting Officer 

9. INITIAL SUBMISSION' Per Data Requirements Matrix 

10. SUBMISSION FREQUENCY: Per Data Requirements Matrix. 







11. REMARKS' 

The Cost Performance Report shall be available for online viewing at any 

time during the effort by NASA using appropr1ately protected 

Internet/Intranet technologies. 

The CPR shall be subm1tted monthly by the 10th to 12th working day of the 

month following the month being reported. 

The time increments to be used 1n Format 3 will correspond (within the 

limits of the Contractor's disclosed fiscal calendar) with the government 

fiscal year. 

CPR reporting shall reflect costs at WES Level 3 with the exception of 

Systems Engineering and Integrat10n, which shall be reported at Level 4, 

and Spacecraft, which shall be reported at Level 5. 

CPR reporting shall include the flow down of EVM requirements to 

subcontractors as well as any re1rnbursable agreements with other 

government agencies. 

For a detailed discuss10n of CCRM, see www.ceh.nasa.gov 

The following document(s) may be used as reference: 

533 DRD-eCCR: 533 Electronic Submiss10n Example 

CPR Formats 1-5: CPR Formats 1 through 5 

12 INTERRELATIONSHIP: Parent sow Paragraph(s): 1.2. (d), 1. 7. (b). 

Referenced in sow Paragraph: 2.4 

13. DATA PREPARATION INFORMATION: 

131 SCOPE: 

The Cost Performance Report (CPR) includes data to measure cost and 

schedule performance. The CEV Integrated Master Schedule provides data 

for the assessment of contract schedule and logic network of the tasks to 

be performed. 

13.2 APPLICABLE DOCUMENTS: 

ANSI/EIA-748-98: Earned Value Management Systems 

NPD 9501.3A: Earned Value Management 

NPR 9501.3: Earned Value Management Implementation Plan on NASA Contracts 

13 3 CONTENTS: 

13.3.1 The integrated master schedule shall contain the contract 

milestones, accomp11shments, and discrete tasks/activities (1ncluding 

planning packages where applicable) from contract award to the completion 

of the contract. The schedule shall be an integrated, logical networkbased 

schedule that correlates to the CWES, and is vertically and 

horizontally traceable to the cost/schedule reporting instrument used to 

address variances such as the CPR. The schedule shall have a numbering 

system that provides traceab1l1ty to the IMP and sow. It shall contain 

contractual mllestones and descriptions and display summary, 

intermediate, and detailed schedules, and periodic analysis of progress 

to date. It shall 1nclude f1elds and data that enable the user to access 

the information by product, process, or organizational lines. 

13.3.2 Contract M1lestones and Definitions. Key project events, which 

define progress and complet1on for each CWES element, along with the 

definition for successful completion of the milestone. 







13.3.3. Summary Master Schedule. A top-level schedule of key 

tasks/activ~ties and milestones at the summary level of the CWES and IMP 

(if applicable). It shall be an integrated roll up of the intermediate 

and detailed schedules (see 13.3.3 and 13.3.4) (vertical integration). 

13.3.4. Intermediate Schedules. Midlevel contract schedules that include 

key tasks/activities and m~lestones and all associated accomplishments in 

the summary master schedule, traceable to the CWES element or IMP event 

as necessary to display work effort at the intermediate level of 

summarization. There may be several intermediate schedules that depict 

varying levels of detail. They shall be integrated roll ups of the 

detailed schedules (see 13.3.4 below) (vertical integrat~on). 

13.3 5. Deta~led Schedules. The lowest level of contract 

tasks/activities that form the network. The detailed schedules shall 

contain horizontal and vertical integration, as a minimum, at the work 

package and planning package level The detailed schedules shall include 

all tasks/activities, work packages, and planning packages identified in 

the contract Performance Measurement Baseline (PMB). Every discrete 

task/activity, work package, and planning package shall be clearly 

identified and directly related to a control account. Work packages and 

planning packages shall be individually represented and summarize to or 

reconc~le with the total budget for that control account. If Level of 

Effort (LOE) control accounts, work packages, or planning packages are 

included as tasks in the IMS, they shall be clearly identified as such. 

The detailed tasks/activities, work packages, and plann~ng packages shall 

be traceable to only one CWBS, IMP, and performing organizational 

element, as applicable. The level of detail ~n the IMS (including number 

and duration of tasks/activities) shall follow the Contractor's EVM 

process as documented ~n the EVMS system description, project directives, 

etc. Shorter-term work packages (ideally equal in length to the 

statusing interval) are preferred because they provide more accurate and 

reliable measures of work accomplished. 

13.3.6. Key Elements of Detailed Schedules. The key elements of the 

detailed schedules include the following: 

13.3.6.1. Task/Activity. An element of work with durat~on. 

13.3.6.2 Milestone. A specific definable accomplishment in the contract 

network, recognizable at a particular point in time. Milestones have zero 

durat~on and do not consume resources. 

13.3.6.3 Durat~on. The length of t~me estimated (or realized) to 

accomplish a task/activity. 

13.3.6.4 Percent Complete (Schedule). The proportion of an activity or 

task that has been completed to time now. This usually involves updating 

or statusing the activity or task ut~lizing one of two methods: (1) 

update the remaining time to complete (remaining duration) and the 

scheduling software will then automat~cally update the schedule percent 

complete or (2) update the schedule percent complete and allow the 

scheduling software to calculate the t~me remaining (remaining duration) 

to complete. Either method will use the follow~ng formula: Percent of 

Duration Completed = (Actual Duration / Total Durat~on) X 100. 

13.3.6.5 Task/Activity and Milestone Descript~ons. These are descriptive 

titles that are concise, complete, and clearly identify the work effort 

being accomplished. Abbreviations may be used to shorten the descriptive 

titles. 

13.3.6.6 Task/Activity Codes and Data Dictionary. A list of field 




Crew Exploration Vehicle - (CEV) Modification 65 

definit10ns and code structures. Th1S 11St shall be provided to the 

procuring activ1ty. 

13.3.6.7 Relationsh1p/Dependency. These identify how predecessor and 

successor tasks/activities and milestones are logically linked. 

Relationships, also called network logic, are modeled in four ways: 

13.3.6.7.1 Finish to Start (FS). A predecessor task/activity or 

milestone that must finish before a succeeding task/activity or milestone 

can start. FS relationships shall be used whenever possible. 

13.3.6.7.2 Start to Start (SS). A predecessor task/activity or milestone 

that must start before a succeeding task/activity or milestone can start. 

13.3.6.7.3 Finish to Finish (FF). A predecessor task/activity or 

milestone that must f1n1sh before a succeeding task/activity or milestone 

can fl.n1sh. 

13.3.6.7.4 Start to Finish (SF) A predecessor task/activity or 

milestone that must start before a succeeding task/activity or milestone 

can finish. 

13.3.6.8 Total Float/Slack. The amount of time a task/activity or 

milestone can slip before it delays the contract or project finish date. 

13.3.6.9 Free Float/Slack. The amount of time a task/activity or 

milestone can slip before it delays any of its successor tasks/activities 

or milestones. 

13.3.6.10 Lag. An interval of tl.me that must occur between a predecessor 

and successor task/activity or milestone. Since negative time is not 

demonstrable, negat1ve lag 1S not encouraged. (Note: Lag should not be 

used to manipulate float/slack or constrain schedule.) 

13.3.6.11 Early Start (ES) The earliest start date a task/activity or 

milestone can begin the precedence relationships. A computer-calculated 

date. 

13.3.6.12 Early F1n1sh (EF). The earliest finish date a task/activity or 

milestone can end. A computer-calculated date. 

13.3.6.13 Late Start (LS). The latest start date a task/actl.vity or 

milestone can start without delaying the contract or project target 

completion date. A computer-calculated date. 

13.3.6.14 Late Fl.n1Sh (LF) The latest date a task/activity or milestone 

can finish without delaying the contract or project target completion 

date. A computer-calculated date. 

13.3.6.15 Critical Path. A sequence of discrete tasks/activities 1n the 

network that has the longest total duration through the contract or 

project. Discrete tasks/activities along the cr1tical path have the 

least amount of float/slack. The crit1cal path and near-critical paths 

(report1ng requ1rements for near-cr1tical paths shall be a total float of 

5 days or less) are calculated by the scheduling software application. 

Note: Total float is the amount of time that an activity can be 

lengthened or slipped without delaying the project completion or 

mandatory critical milestone completion, assuming that all other 

activities are done in their normal time. The guidelines for critical 

path and near-critical path reporting are as follows: 

13.3.6.15.1 Methodology. The IMS software application computes a 







critical path and near-crit~cal paths based on precedence relationships, 

lag times, durations, constraints, and status. Artificial constraints 

and incorrect, incomplete, or overly constrained logic shall be avoided 

because they can skew the critical path and near-critical paths. 

13.3.6.15.2 Identification. The critical path shall be easily 

identified. 

13.3.6.16 Constraints. Limits applied to network start and finish dates 

(e.g., "finish no later than'). (Note: Certain types of constraints 

should be used judiciously because they may impact or distort the network 

critical path.) 

13.3.6.17 Current Schedule. The IMS reflects the current status and 

forecast. It ~ncludes forecasted starts and finishes for all rema~ning 

tasks/activities and milestones Significant variances to the baseline 

schedule shall be explained in the periodic analysis. Thresholds for 

reporting shall be specified in the Performance Assessment Plan. The 

Performance Assessment plan shall be delivered in accordance with DRD 

CEV-M-002. 

13.3.6.18 Baseline Schedule. Baseline dates in the IMS shall be 

consistent with the baseline dates in the PMB for all work packages, 

planning packages, and control accounts (if applicable). The guidelines 

for maintaining the basel~ne schedule are as follows: 

13.3.6.18.1 Schedule Changes. Changes to the schedule shall be baselined 

when ~ncorporated into the schedule. 

13.3.6.18 2 Baseline Schedule Changes. Changes to the baseline schedule 

shall be made in accordance with the Contractor's EVM process. Any 

movement of contractual milestones in the baseline schedule requires the 

approval of the procuring act~v~ty. 

13.3.6.19 Schedule Progress. The IMS shall reflect actual progress and 

maintain accurate start and finish dates for all tasks/activities and 

milestones. The guidelines for reflecting schedule progress are as 

follows: 

13.3.6.19.1 Actual Start and Fin~sh Dates. Actual start and actual 

finish dates shall be recorded ~n the IMS. Actual start and actual 

finish dates, as recorded, shall not be later than the status date. 

13.3.6.19.2 Progress Line. The progress line dep~cted in a Gantt chart 

shall be applied to the current schedule. 

13.3.6.20 Retention of Data for Completed Tasks/Activities. Historical 

performance on completed tasks/activities shall be maintained 

electronically for analytical use. Data to be retained includes logic, 

actual and baseline durations, actual and baseline start and finish 

dates, and the three-point est~mates that were used before the 

task/activity started. The retention of the IMS data shall be identified 

in the Contractor Data Management Plan. 

13 3.6.21 External Dependencies. The IMS shall identify significant 

external dependencies that ~nvolve a relationship or interface with 

external organizat~ons, ~ncluding all Government furnished items (e.g., 

decisions, facilities, equipment, information, data, etc.). The 

determ~nat~on of s~gnificant shall be defined and documented, and agreed 

to by NASA. The required or expected del~very dates shall also be 

identified in the IMS. 




Crew Exploration Vehic1e - (CEV) 



13.3.6.22 Schedule Margin. A management method for accommodating 

schedule contingencies. It ~s a designated buffer and shall be 

identified separately and considered part of the baseline. Schedule 

margin is the difference between contractual milestone date(s) and the 

Contractor's planned date(s) of accomplishment. 

13.3.6.23 Schedule Risk Assessment. A schedule risk assessment predicts 

the probability of project completion by contractual dates. Three-point 

estimates shall be developed for remaining durations of remaining 

tasks/activities that meet any of the following criteria: (1) critical 

path tasks/activities, (2) near-critical path tasks/activities (as 

specified in the CDRL) , (3) moderate to high risk tasks/activities in the 

project's risk management plan. These est~mates include the most likely, 

best case, and worst case durations. They are used by the Contractor to 

perform a probability analysis of key contract completion dates. The 

cr~teria for estimated best and worst case durations shall be applied 

consistently across the entire schedule and documented in the 

Contractor's schedule notes and management plan. The guidelines for 

est~mates are as follows: 

13.3.6 23.1 Most Likely Estimate. Schedule durations based on the most 

likely estimates. 

13.3.6.23.2 Best/Worst Case Estimates. Best and worst case assumptions 

shall be disclosed. The Contractor schedule risk assessment shall 

explain changes to the critical path, margin erosion, and m~t~gat~on 

plans. It shall be incorporated into the Contractor's project risk 

management process. The schedule risk assessment shall be submitted as 

specified in the CDRL and prior to the Integrated Baseline Review. The 

r~sk analysis may be performed within the IMS or within a separate risk 

tool as appropr~ate based on the capability of the automated sCheduling 

tool. 

13.3.6.24 User Defined Fields. All user defined fields in the IMS shall 

be identified by providing a mapp~ng of all fields used ~n the scheduling 

software application. 

13.3.5.25 Reserved Fields. NASA may reserve some fields and/or 

the Contractor to use certain fields for spec~fic information. 

requirement for reserved fields shall be specified in the CDRL. 

require 

The 

13.3.6.26 Calendar. The arrangement of normal working days, together 

with non-working days, such as holidays, as well as special work days 

(i.e., overt~me periods) used to determine dates on which project work 

will be completed. 

13.3.7. Monthly Analys~s. Monthly analys~s ~s a monthly assessment of 

schedule progress to date and includes changes to schedule assumptions, 

variances to the basel~ne schedule, causes for the variances, potential 

~mpacts, and recommended correct~ve actions to minimize schedule delays. 

The analysis shall also identify potential problems and an assessment of 

the cr~t~cal path and near-cr~t~cal paths. Thresholds for reporting 

significant variances to the baseline schedule and near-critical paths 

shall be specified in the CDRL. If a CPR Format 5 is required, the 

monthly analys~s shall be subm~tted to the procuring act~vity prior to or 

concurrently with the CPR Format 5. 

13.3.8. Format for the Cost Performance Report. Use the relevant DD 

Forms as listed above. All formats shall be submitted electronically in 

accordance with the follow~ng requ~rements. All formats shall be in a 

readable digital format (e.g., PDF files are not acceptable). 

Amer~can Nat~onal Standards Inst~tute (ANSI) X12 standard (839 


CEV-B-003 Page 7 of21 

The





transaction set), the United Nations Electronic Data Interchange for 

Adm1nistrat10n, Commerce and Transport (UN/EDIFACT) standard (PROCST 

message), the XML equ1valent or any other equ1valent or better electronic 

format shall be used to submit data electronically to the procuring 

activity. Contractor formats may be substituted whenever they contain 

all of the required data elements at the specified reporting levels and 

are compliant with the X12 standard, XML schema, or equivalent. On-line 

access to the data may be provided to augment formal CPR submission. 

(Note: Until the ANSI X12/XML standards are redefined to incorporate the 

changes to the forms, the new data elements shall be reported in Format 

5.) The final decision of the acceptable format shall be made by the 

NASA COTR. 

13.3.9. Content. The CPR shall conta1n the follow1ng: 

13.3.9.1. Heading Information - Formats 1 - 5. Preparation instructions 

for Heading Information (Blocks 1 through 4) apply to Formats 1 through 

5. 

13.3 9.1.1. Contractor. Enter in Block 1.a the Contractor's name and 

division (if appI1cable). Enter 1n Block 1 b the fac111ty location and 

mailing address of the reporting contractor. 

13.3.9.1.2. Contract. Enter the contract name in Block 2.a, the contract 

number (and the applicable Contract Line Item Number(s) (CLINs)) in Block 

2.b, the contract type in Block 2.c, and the contract share ratio (if 

applicable) in Block 2.d. 

13.3.9.1.3 Project. Enter in Block 3.a the project name, number, 

acronym, type, model, and series, or other designation of the prime 

item(s) purchased under the contract. Indicate the project phase 

(development, production, etc) in Block 3.b. Ind1cate whether the 

Contractor's EVMS has been accepted by NASA and the date of the 

acceptance. 

13.3.9.1.4. Report Period. Enter the beginning date 1n Block 4.a and the 

ending date in Block 4.b of the period covered by the report. 

13.3.9.1.5. Security Classification. Enter the appropriate security 

classification at the top and bottom of each page. 

13.3.9.1.6. Dollars in _ (to be filled in by Offeror) ____ . If reported 

dollar amounts are in thousands, millions, or billions, enter the factor 

at the top of each page. 

13.3.9.2.Format 1 - Work Breakdown Structure. Submission of Format 1 

using a product-oriented WBS is mandatory and shall be 1n accordance with 

the Center WBS standard. If there are deviations, a mapping shall be 

provided. 

13.3.9.2.1. Contract Data. 

13.3 9.2.1 1. Quantity. Enter in Block 5.a the number of principal items 

to be procured on this contract. 

13.3.9.2.1.2.Negotiated Cost. Enter in Block 5.b the dollar value 

(excluding fee or profit) on which contractual agreement has been reached 

as of the cutoff date of the report. For an incentive contract, enter 

the definitized contract target cost. Amounts for changes shall not be 

included in this item until they have been priced and incorporated in the 

contract through contract change order or supplemental agreement. For a 

cost plus fixed fee, award fee, or 1ncent1ve fee contract, enter the 


CEV-B-003 Page 8 of2l





estimated cost negotiated. changes to the estimated cost shall consist 

only of estimated amounts for changes in the contract scope of work, not 

for cost growth ('overrun') above the original est1mated cost. 

13.3.9.2.1.3.Estimated Cost of Authorized, Unpriced Work. Enter in Block 

S.c the amount (excluding fee or profit) estimated for that work for 

which wr1tten authorization has been received, but for which definitized 

contract prices have not been incorporated in the contract through 

contract change order or supplemental agreement. 

13.3.9.2.1.4 Target Profit/Fee. Enter 1n Block S.d the fee or 

percentage of profit that shall apply if the negotiated cost of the 

contract is met. (See 13.3.9 2.1.2 above.) 

13 3.9.2.1.5. Target Price. Enter in Block 5.e the target price 

(negotiated contract cost plus profit/fee) applicable to the definitized 

contract effort. 

13.3.9.2.1.6. Estimated Price. Based on the most likely estimate of cost 

at completion for all authorized contract work and the appropriate 

profit/fee, incentive, and cost sharing provisions, enter in Block S.f 

the estimated final contract price (total est1mated cost to the 

Government). This number shall be based on the most llkely management 

EAC in Block 6.c 1 and normally will change whenever the management 

estimate or the contract 1S rev1sed. 

13.3.9.2.1.7. Contract Ce1l1ng. Enter in Block 5.g the contract ceiling 

pr1ce applicable to the def1n1t1zed effort. 

13.3.9.2.1.8. Estimated Contract Ceiling. Enter in Block 5.h the 

estimated ceiling price appl1cable to all authorized contract effort 

includ1ng both definitized and undefin1tized effort. 

13.3.9.2.1.9. Over Target Basel1ne/Over Target Schedule. 

S.i the date the last over target baseline or over target 

implemented (if applicable). 

Enter in Block 

schedule was 

13.3.9.2.2. Est1mated Cost at Completion. These blocks shall present the 

Contractor's range of estimated costs at completion. The range of 

estimates 1S 1ntended to allow contractor management flexibility to 

express possible cost outcomes. Contractors shall provide the most 

accurate Estimates at Completion (EACs) possible through project-level 

assessments of factors that may affect the cost, schedule, or technical 

outcome of the contract. Such project-level assessments shall include 

consideration of known or ant1cipated risk areas, and planned risk 

reductions or cost conta1nment measures. EACs shall be reported without 

regard to contract ceiling. 

13.3.9.2.2.1. Management Est1mate at Completion - Best Case. Enter in 

Block 6.a.1 the Contractor's best case EAC. The best case estimate is 

the one that results in the lowest cost to NASA. This estimate shall be 

based on the outcome of the most favorable set of circumstances. If this 

estimate is different from the most likely EAC (Block 6.c.1), the 

assumptions, conditions, and methodology underlY1ng th1S est1mate shall 

be explained briefly in Format 5. Th1s estimate is for informational 

purposes only; it is not an official company estimate. There is no 

requirement for the Contractor to prepare and maintain backup data beyond 

the explanation prov1ded 1n Format 5. 

13.3.9.2.2.2. Management Estimate at Completion - 

Block 6.b.1 the Contractor's worst case EAC. The 

the one that results in the highest cost to NASA. 

Worst Case. 

Enter in 

worst case estimate is 

This estimate shall be 







based on the outcome of the least favorable set of circumstances. If 

this estimate is different from the most likely EAC (Block 6.c.1), the 

assumptions, conditions, and methodology underlying this estimate shall 

be explained briefly 1n Format 5 This estimate is for informational 

purposes only; it is not an official company estimate. There is no 

requirement for the Contractor to prepare and maintain backup data beyond 

the explanation prov1ded in Format 5. 

13.3.9.2.2.3. Management Estimate at Completion - Most Likely. Enter in 

Block 6.c.1 the Contractor's most 11kely EAC. Th1s estimate is the 

contractor's official contract EAC and, as such, takes precedence over 

the est1mates presented in Column (15) of Formats 1 and 2 and Blocks 

6.a.1 and 6.b.1. This EAC is the value that the Contractor's management 

believes is the most 11kely outcome based on a knowledgeable estimate of 

all authorized work, known risks, and probable future conditions. This 

value need not agree with the total of Column (15) (Block S.e). However, 

any difference shall be explained in Format 5 in such terms as risk, use 

of Management Reserve (MR), or higher management knowledge of current or 

future contract conditions The assumptions, conditions, and methodology 

underlying this estimate shall be expla1ned briefly in Format 5. This 

EAC need not agree with EACs conta1ned in the Contractor's internal data, 

but must be reconcilable to them. The most likely EAC shall also be 

reconcilable to the Contractor's latest statement of funds required as 

reported in the CFSR, or its equivalent. 

13.3.9.2.2.4. Contract Budget Base. Enter in Block 6.c.2 the total of 

negot1ated cost (Block 5.b) and est1mated cost of authorized, unpriced 

work (Block 5.c). 

13.3.9.2.2.5. Variance Enter in Block 6.c.3 the contract Budget Base 

(Block 6.c.2) minus the most likely estimate at complete (Block 6.c.1). 

This value shall be explained in Format 5 according to applicable 

contractual requirements. 

13.3.9.2.3. Authorized Contractor Representative. Enter in Block 7.a the 

name of the authorized person (project manager or higher level designee) 

signing the report. Enter that person's t1tle in Block 7.b. The 

authorized person shall s1gn in Block 7.c. Enter the date s1gned in 

Block 7.d. Electronic signatures are encouraged. 

13.3.9.2.4. Performance Data. 

13.3.9.2.4.1. Column (1) -Work Breakdown Structure Element. Enter in 

Column (1) of Block S.a the noun description of the CWES items for which 

cost 1nformation is be1ng reported. CWBS elements and levels reported 

shall be those specif1ed in the contract. (See d.1 above.) 

13.3 9.2.4.2. Cost of Money. Enter in Columns (2) through (16) of Block 

S.b the Facilities Cap1tal Cost of Money applicable to the contract. 

13.3.9.2 4.3. General and Administrative Enter in Columns (2) through 

(16) of Block S.c the appropr1ate General and Administrative (G&A) costs. 

If G&A has been included 1n the total costs reported in Block S.a above, 

G&A shall be shown as a non-add entry on this line w1th an appropriate 

notation. However, if these contracts require CCDRs, the Contractor must 

report costs without G&A for CWES elements reported in Block S.a if the 

Government requests such information on an exception basis. If a G&A 

classification is not used, no entry shall be made other than an 

appropriate notation to that effect. 

13.3.9.2.4.4. Undistributed Budget (UB). Enter the amount of budget 

applicable to contract effort that has not yet been identified to CWES 







elements at or below the reporting level. For example, if contract 

changes were authorized late in the report~ng per~od, they should have 

received a total budget; however, assignment of work and allocation of 

budgets to ~ndividual CWES elements may not have been accomplished as of 

the contractor's accounting period cutoff date. Budgets that can be 

identified to CWBS elements at or below the specified reporting level 

shall be included in the total budgets shown for the CWES elements in 

Block 8.a and shall not be shown as UB. Enter in Column (15) of Block 

8.d the EAC for the scope of work represented by the UB in Column (14) of 

Block 8.d. Enter in Column (16) of Block 8.d the variance, if any, and 

fully explain it in Format 5. The reason(s) for UB shall be fully 

explained in Format 5 

13.3.9.2.4.4.1.Use of Undistributed Budget. UB is used to accommodate 

temporary situations where t~me constraints prevent adequate budget 

plann~ng or where contract effort can only be defined in very general 

terms. UB shall not be used as a substitute for adequate contract 

planning. Formal budgets shall be allocated to contract effort and 

responsible organ~zat~ons at the earliest possible time, preferably 

within the next reporting period. 

13.3.9.2.4.5. Subtotal (Performance Measurement Baseline). In Columns 

(2) through (16) of Blocks 8.a through 8 e, enter the sum of the costs 

and budgets for direct, indirect, cost of money, and G&A. This subtotal 

represents the dollars in the allocated budget (less MR), which is the 

Performance Measurement Baseline (PMB) against which performance is 

measured. 

13.3.9.2.4 6. Management Reserve (MR). MR is an amount of the overall 

contract budget withheld for management control purposes and is held for 

project unknowns (realized risks on authorized work scope). Reserve is 

held for future needs and shall not be used to offset cumulat~ve cost 

variances. It shall not be eliminated from contract prices by the 

Government during subsequent negotiations nor used to absorb the cost of 

contract changes. In Column (14) of Block 8.f enter the total amount of 

budget identified as MR as of the end of the current reporting period. 

The amounts shown as MR in Formats 1, 2, and 3 should agree. Amounts of 

MR applied to CWES elements during the reporting period shall be listed 

in Block 6.b of Format 3 and explained in Format 5. 

13.3.9.2.4.6.1. Negative Management Reserve. Negative entries shall not 

be made in Management Reserve (Column (14) of Block 8.f). There is no 

such thing as ' negat~ve MR.' If the contract ~s budgeted in excess of 

the Contract Budget Base (the negotiated contract cost plus the estimated 

cost for authorized, unpriced work), the provisions applicable to formal 

reprogramm~ng and the ~nstruct~ons ~n paragraphs 13.3.9.2.5.1, 

13.3.9.2.6.6., 13.3.9.2.6.7., and 13.3.9.4.1.7 apply. 

13.3.9.2 4.7. Total. Enter the sum of all direct, indirect, cost of 

money, and G&A costs, and UB and MR (if applicable) in columns (2) 

through (14) of Block B.g. The Total lines of Format 1 (Block B.g) and 

Format 2 (Block 5.g) should agree. The total of Column (14), Block B.g, 

should equal the Total Allocated Budget shown in Block 5.f on Format 3. 

13.3.9.2.5. Reconc~l~at~on to Contract Budget Base. 

13.3.9.2.5.1. Formal Reprogramming. In exceptional cases, the 

Contractor, with the approval of the Government, may establish 

performance measurement budgets that exceed the Contract Budget Base. 

This process is called formal reprogramming. 

The Contractor and the 

Government shall agree on how the results of a formal reprogramming will 

be reported ~n the CPR before the formal reprogramming is initiated. 







This agreement and any other pertinent details on the reporting of the 

formal reprogramming shall be ~ncluded in Format 5. Blocks 9.a and 9.b 

are used to reconcile the higher performance measurement budgets, also 

called an 'Over Target Baseline,' to the Contract Budget Base. 

(See13.3.9.2.6.6." 13 3.9.2.6.7., 13.3.9.4.1.7. and 13.3.9.6.5 below for 

more information on reporting Over Target Baselines (Formal 

Reprogramming) .) 

13.3.9.2.5.2. Variance Adjustment. In a formal reprogramming (Over 

Target Baseline), the Contractor may: (1) apply the additional budget to 

completed work, thereby eliminat~ng some or all of the existing cost or 

schedule variances, (2) apply the additional budget to remaining work, 

(3) apply some of the additional budget to completed work and some to 

remaining work, and/or (4) apply some of the additional budget to MR. If 

the Contractor uses a portion of the additional budget to eliminate 

variances appl~cable to completed work, the total adjustments made to the 

cost and schedule variances shall be shown ~n Columns (10) and (11) of 

Block 9.a The total cost variance adjustment entered in Column (11) of 

Block 9.a should be the sum of the individual cost variance adjustments 

shown in Column (12) of Block 8.g. 

13.3.9.2.5.3. Total Contract Variance. In Columns (10) and (11) of Block 

9.b, enter the sum of the cost and schedule variances shown on the Total 

line (Block 8.g) and on the Variance Adjustment line (Block 9.a). In 

Column (14) enter the Contract Budget Base from Block 6.c.2. In Column 

(15) enter the management EAC from Block 6.c.1. In Column (16) of Block 

9.b enter the difference between Columns (14) and (15) of Block 9.b. 

13.3.9.2.6. Columns (2) Through (16) Since compliance with the 

ANSI/EIA-748 (current version in effect at time of contract award) is 

contractually required, the data in Columns (2) through (16) shall 

reflect the output of the contractor's ANSI/EIA-748 compliant integrated 

management system. 

13.3.9.2.6.1. Column (2) and Column (7) - Budgeted Cost - Work Scheduled. 

For the t~me period indicated, enter the Budgeted Cost for Work Scheduled 

(BCWS) in these columns. 

13.3.9.2.6.2. Column (3) and Column (8) - Budgeted Cost - Work Performed. 

For the time period indicated, enter the Budgeted Cost for Work Performed 

(BCWP) in these columns 

13.3.9.2.6 3. Column (4) and Column (9) - Actual Cost - Work Performed. 

For the time period indicated, enter the Actual Cost of Work Performed 

(ACWP) w~thout regard to ceiling. In all cases, costs and budgets shall 

be reported on a comparable basis. 

13.3.9.2.6.4. Column (5) and column (10) - Variance - Schedule (i.e., 

accomplishment). For the time period indicated, these columns reflect 

the differences between BCWS and BCWP. For the current period column, 

column (5) (schedule variance) is der~ved by subtracting Column (2) 

(BCWS) from Column (3) (BCWP). For the cumulative to date column, Column 

(10) (schedule variance) is der~ved by subtracting Column (7) (BCWS) from 

Column (8) (BCWP). A pos~t~ve number ~n Column (5) and column (10) 

indicates a favorable variance. A negative number (indicated by 

parentheses) indicates an unfavorable var~ance. Significant variances as 

spec~f~ed in the contract shall be fully explained in Format 5. If the 

contract does not spec~fy variance analysis thresholds, the Contractor 

shall provide appropriate variance analyses. 

13.3.9 2.6.5. Column (6) and Column (11) - Variance - Cost. For the time 

period indicated, these columns reflect the difference between BCWP and 







ACWP. For the current per~od column, Column (6) (cost variance) is 

der~ved by subtracting Column (4) (ACWP) from Column (3) (BCWP). For the 

cumulative to date column, Column (11) (cost variance) ~s derived by 

subtracting Column (9) (ACWP) from Column (8) (BCWP). A positive value 

indicates a favorable variance. A negative value (~ndicated by 

parentheses) indicates an unfavorable variance. significant variances as 

specif~ed in the contract shall be fully explained in Format 5. Since 

the contract does not specify variance analysis thresholds, the 

contractor shall provide appropriate variance analyses. 

13.3.9.2.6.6. Column (12a) and Column (12b) Reprogramming Adjustments - 

Cost Variance and Schedule Variance. Formal reprogramm~ng (Over Target 

Baseline) results in budget allocations in excess of the Contract Budget 

Base and, in some instances, adJustments to previously reported 

variances. If previously reported variances are being adjusted, the 

adjustment applicable to each reporting line item affected shall be 

entered in Column (12a) ~f for a cost variance and Column (12b) if for a 

schedule variance. The total of Column (12a) and Column (12b) should 

equal the amount shown on the Var~ance Adjustment line (Block 9.a) in 

Column (10) and Column (11). 

13.3.9 2.6.7. Column (13) Reprogramming Adjustments - Budget Enter the 

total amounts added to the budget for each reporting line item as the 

result of formal reprogramming (Over Target Baseline). The amounts shown 

shall consist of the sum of the budgets used to adJust cost variances 

(Column (12)) plus the additional budget added to the CWES element for 

remaining work. Enter the amount of budget added to MR in the space 

provided on the Management Reserve line (Block 8.f of Column (13)). The 

total of Column (13) should equal the budget amount by which the Total 

Allocated Budget exceeds the Contract Budget Base as shown in Block 5.g 

of Format 3. An explanation of the reprogramming shall be provided in 

Format 5. 

13.3.9.2.6.7.1. Formal Reprogramming Reporting. Columns (12) and (13) 

are intended for use only in situat~ons ~nvolv~ng formal reprogramming 

(Over Target Baseline). Internal replanning actions within the Contract 

Budget Base do not requ~re entries in these columns. Where contractors 

are submitting CPR data directly from automated systems, the addition of 

Columns (12) and (13) as shown may not be pract~cal due to computer 

reprogramming problems or space limitations. In such cases, the 

information shall be prov~ded in Format 5. Contractors shall not be 

required to abandon or modify existing automated reporting systems to 

~nclude Columns (12) and (13) if significant costs will be associated 

with such change. Nor shall contractors be required to prepare the 

report manually solely to include this information. 

13.3.9.2.6.7.2. Formal Reprogramm~ng T~mel~ness. Formal reprogramming 

(Over Target Baseline) can be a significant undertaking that may require 

more than a month to ~mplement To preclude a disruption of management 

visibility caused by a report~ng h~atus, formal reprogramming shall be 

implemented expeditiously. If a report~ng h~atus ~s needed, the 

Contractor and the Government shall agree on the date and duration of the 

h1atus before the formal reprogramming is initiated. 

13.3 9.2.6.8.Column (14) - At Complet~on - Budgeted. Enter the budgeted 

cost at completion for the ~tems l~sted in Column (1). This entry shall 

consist of the sum of the original budgets plus or minus budget changes 

resulting from contract changes, ~nternal replanning, and application of 

MR. The total (Block 8.g) should equal the Total Allocated Budget shown 

in Block 5.f on Format 3. 

13.3.9.2.6.9. Column (15) - At Completion - Estimated. Enter the latest 







revised estimate of cost at completion including estimated 

overrun/underrun for all authorized work. If the subtotal (Block 8.e) 

does not agree with the most likely management EAC (Block 6.c.1), the 

difference shall be explained in Format 5. 

13.3.9.2.6 10 Column (16) - At Completion - Variance. Enter the 

d~fference between the Budgeted - At Completion (Column (14)) and the 

Estimated - At Completion (Column (15)) by subtracting column (15) from 

Column (14). A negative value (indicated by parentheses) reflects an 

unfavorable variance. S~gnificant variances as specified in the contract 

shall be fully explained ~n Format 5. If the contract does not specify 

variance analysis thresholds, the contractor shall provide appropriate 

variance analyses. 

13.3.9.3. Format 2 - Organizational Categories 

13.3.9.3.1 Performance Data. 

13.3.9.3.1.1. Column (1) - Organ~zat~onal Category. In Block 5.a list 

the organizational categories that reflect the contractor's internal 

management structure. The level of detail to be reported normally will 

be limited to the organizational level immediately under the operating 

head of the facility. The contractor may report this information 

according to its own ~nternal management structure. If the contractor is 

organized by product teams, th~s format may not be needed because it may 

resemble Format 1. 

13.3.9.3.1.2 Cost of Money. Enter ~n Columns (2) through (16) of Block 

5.b the Facilities Cap~tal Cost of Money applicable to the contract. 

13.3.9.3.1.3. General and Administrative. Enter ~n Columns (2) through 

(16) of Block 5.c the appropriate G&A costs. If G&A has been included in 

the total costs reported in Block 5.a above, G&A shall be shown as a nonadd 

entry on this line with an appropr~ate notation. If a G&A 

classificat~on is not used, no entry shall be made other than an 

appropriate notation to that effect 

13.3.9.3.1.4. Und~str~buted Budget. Enter in Column (14) of Block 5.d the 

budget applicable to contract effort that cannot be planned in sufficient 

detail to be assigned to a responsible organizational area at the 

reporting level. The amount shown on this format may exceed the amount 

shown as UB on Format 1 if budget is identified to a task at or below the 

CWES reporting level but organizat~onal ~dentification has not been made; 

or may be less than the amount on Format 1 where budgets have been 

assigned to organizations but not to CWBS elements. Enter in Column (15) 

of Block 5.d the EAC for the scope of work represented by the UB in 

Column (14) of Block 5.d. Enter in Column (16) of Block 5.d the 

variance, if any, and fully explain it in Format 5. 

13.3.9.3.1.5. Subtotal (Performance Measurement Baseline). Enter the sum 

of the direct, indirect, cost of money, and G&A costs and budgets in 

Columns (2) through (16) of Blocks 5.a through 5.e. 

13.3.9.3.1.6. Management Reserve. 

amount of budget ~dentif~ed as MR. 

amounts shown in Formats 1 and 3. 

In Column (14) of Block 5.f enter the 

The MR entry should agree with the 

13.3.9.3.1.7. Total. Enter the sum of all direct, indirect, cost of 

money, and G&A costs and budgets, UB, and MR (if applicable) in Columns 

(2) through (14) of Block 5.g. The totals on this page should equal the 

Total line on Format 1. The total of Column (14) should equal the Total 

Allocated Budget shown ~n Block 5.f on Format 3. 







13.3.9.3.2.Columns (2) Through (16). The instructions applicable to 

these columns are the same as the instructions for corresponding columns 

on Format 1. 

13.3.9.4. Format 3 - Basel~ne. 

13.3.9.4.1. Contract Data. 

13.3.9.4.1.1. Or~ginal Negotiated Cost. Enter in Block 5.a the dollar 

value (excluding fee or profit) negotiated in the original contract. For 

a cost plus fixed fee, incentive, or award fee contract, enter the 

estimated cost negot~ated. For an incentive contract, enter the 

definitized contract target cost. 

13.3.9.4.1.2. Negotiated Contract Changes. Enter in Block 5.b the 

cumulative cost (excluding fee or prof~t) applicable to definitized 

contract changes that have occurred since the beginning of the contract. 

13.3.9.4.1.3. Current Negotiated Cost. Enter in Block 5.c the sum of 

Blocks 5.a and 5.b. The amount shown should equal the current dollar 

value (excluding fee or profit) on which contractual agreement has been 

reached and should be the same as the amount in Negotiated Cost (Block 

5.b) on Format 1. 

13.3.9.4.1.4. Estimated Cost of Author~zed, Unpriced Work. Enter ~n 

Block 5.d the estimated cost (excluding fee or profit) for contract 

changes for which authorization has been received from the contracting 

officer, but for which contract prices have not been ~ncorporated in the 

contract, as shown in Block 5.c of Format 1. 

13.3.9.4.1.5. Contract Budget Base. Enter in Block 5.e the sum of Blocks 

5.c and 5.d. 

13.3.9.4.1.6. Total Allocated Budget. Enter in Block 5.f the sum of all 

budgets allocated to the performance of the contractual effort. The 

amount shown shall include all MR and UB. Th~s amount should be the same 

as that shown on the Total line in Column (14) on Format 1 (Block 8.g) 

and Format 2 (Block 5.g). 

13.3.9.4.1.7. Difference. Enter in Block 5.g the difference between 

Blocks 5.e and 5.f. In most cases, the amounts shown in Blocks 5.e and 

5.f w~ll be identical. If the amount shown in Block 5.f exceeds that 

shown in Block 5.e, ~t usually is an indication of a formal reprogramming 

(Over Target Baseline). The difference shall be explained ~n Format 5 at 

the time the negative value appears and subsequently for any changes in 

the difference between Contract Budget Base and the Total Allocated 

Budget. 

13.3.9.4.1.8. Contract Start Date. Enter in Block 5.h the date the 

Contractor was authorized to start work on the contract, regardless of 

the date of contract def~nitization. (Note: Long-lead procurement 

efforts authorized under prior contracts are not to be considered.) 

13.3.9.4 1.9. Contract Definitization Date. Enter ~n Block 5.i the date 

the contract was definitized. 

13.3.9.4.1.10. Planned Completion Date. Enter in Block 5.j the 

completion date to which the budgets allocated in the PMB have been 

planned. This date represents the planned completion of all significant 

effort on the contract. The cost associated w~th the schedule from which 

th~s date ~s taken is the Total Allocated Budget (Block 5.f of Format 3). 







13.3.9.4.1.10.1. Performance Measurement Schedule Inconsistent With 

Contractual Schedule. In exceptional cases, the Contractor may determine 

that the existing contract schedule cannot be achieved and no longer 

represents a reasonable basis for management control. With Government 

approval, the contractor may rephase its performance measurement schedule 

to new dates that exceed the contractual milestones, a condition known as 

'Over Target Schedule.' These new dates are for performance measurement 

purposes only and do not represent an agreement to modify the contract 

terms and conditions. 

13.3.9.4.1.10.2. Over Target Schedule Agreement. The Government and the 

Contractor shall agree on the new performance measurement schedule prior 

to reporting it in the CPR. The Contractor shall provide pertinent 

information in Format 5 on any schedule milestones that are inconsistent 

w~th contractual m~lestones, beginning the month the schedule is 

implemented and each month thereafter. 

13.3.9.4.1.10.3. Indicators of a Performance Measurement Schedule 

Inconsistent With the Contractual Schedule. Formal reprogramming or 

internal replann~ng may result in performance measurement milestones that 

are inconsistent with the contractual m~lestones (Over Target Schedule). 

A d~fference between the planned completion date (Block 5.j) and the 

contract completion date (Block S.k) usually indicates that some or all 

of the performance measurement milestones are inconsistent with the 

contractual milestones. 

13 3.9.4.1.11. Contract Completion Date. Enter in Block 5.k the 

contract scheduled completion date in accordance with the latest contract 

modification. The cost assoc~ated with the schedule from which this date 

is taken is the Contract Budget Base (Block 5.e of Format 3). 

13.3.9.4.1.12 Estimated Completion Date. Enter in Block 5.1 the 

Contractor's latest revised est~mated completion date. This date 

represents the est~mated completion of all significant effort on the 

contract. The cost associated with the schedule from which this date is 

taken ~s the 'most likely' management EAC (Block 6.c.1 of Format 1). 

13.3.9.4.2. Performance Data. 

13.3.9.4.2.1. Column (1) -Performance Measurement Baseline (Beginning of 

Period). Enter in Block 6.a the time-phased PMB (including G&A) that 

existed at the beginning of the current report~ng period. Most of the 

entries on this line (e.g., for Columns (4) through (9)) are taken 

directly from the PMB (End of Period) line on the previous report. For 

example, the number in Column (4) on the PMB (End of Period) line from 

the last report becomes the number in Column (3) on the PMB (Beginning of 

Period) line on this report. The number in Column (5) (End of Period) 

last report becomes Column (4) (Beginning of Period) on this report, etc. 

(if each of the two columns covers the same length of t~me). 

13.3.9.4.2.2. Basel~ne Changes. In Block 6.b, list all significant 

baseline changes that have occurred during the reporting period. This 

listing shall include the contract changes and supplemental agreements 

authorized during the reporting per~od, allocations from MR and VB, and 

any sign~ficant rephasing of budgets. All significant authorized 

baseline changes shall be listed whether priced or unpriced. 

13.3.9.4.2.3. Performance Measurement Baseline (End of Period). Enter in 

Block 6.c the time-phased PMB as it exists at the end of the reporting 

period. The difference between this line and the PMB (Beginning of 

Period) represents the effects of all sign~f~cant 

changes, including the 





authorized changes, allocations of MR made during the period, and changes 

to time phasing due to ~nternal replanning or formal reprogramming. The 

reasons for these changes shall be explained in Format 5. 

13.3.9.4.2.4. Management Reserve. Enter in Block 7 the total amount of 

MR remaining as of the end of the reporting period. This value should 

agree with the amounts shown as MR in Formats 1 and 2. 

13.3.9.4 2.5. Total. Enter in Column (16) of Block 8 the sum of Column 

(16) of Block 6.c {PMB (End of Period)) and column (16) of Block 7 

(Management Reserve). This amount should be the same as that shown on 

the Total line (Block 8.g) in column (14) on Format 1. 

13.3.9.4.3. Column (2) - BCWS - Cumulative To Date. On the PMB 

(Beginning of Period) l~ne (Block 6.a), enter the cumulative BCWS as of 

the first day of the reporting period. This should be the same number 

reported as BCWS -Cumulative To Date on the Total line (Column (7) of 

Block 8.g) of Format 1 of the previous CPR. On the PMB (End of Period) 

line (Block 6.c), enter the cumulative BCWS as of the last day of the 

reporting period. This should be the same number reported as BCWS - 

Cumulative to Date on the Total line (Column (7) of Block 8.g) of Format 

1 for this CPR 

13.3.9.4.4. Column (3) - BCWS For Report Period. On the PMB (Beginning 

of Period) line (Block 6.a), enter the BCWS planned for the reporting 

period. This should be the number in Column (4) on the PMB (End of 

Period) line (Block 6.c) on the previous CPR. 

13.3.9.4.5. Columns (4) Through (14). Enter the names of each month for 

the contract period of performance ~n the headings of each of the Columns 

(4) through (9), and the names of the appropriate periods in the headings 

of each of the Columns (10) through (14) of Block 6. Columns beyond (14) 

may be added when necessary or desirable. In the PMB (Beginning of 

Period) line (Block 6.a), enter the BCWS projection reported in Format 3 

of the previous CPR as PMB (End of Period) (Block 6.c). In the PMB (End 

of Period) l~ne (Block 6.c) of this report, enter the projected BCWS by 

month for the next s~x months and for periodic increments (monthly, 

quarterly, or annually) thereafter for the remainder of the contract. 

The time phasing of each item listed in Column (1) of Block 6.b need not 

be shown ~n Columns (4) through (14) It is useful to show the time 

phasing of any baseline changes. (Note: For the purposes of 

illustration, Sample Format 3 has Columns (4) through (14) for reporting 

BCWS. The actual number of columns w~ll vary from contract to contract.) 

13.3.9.4.6. Column (15) - Undistributed Budget. On the PMB (Beginning of 

Period) line (Block 6.a), enter the number from Column (15) on the PMB 

(End of Period) line (Block 6.c) from the previous CPR. On the PMB (End 

of Per~od) line, enter the UB shown ~n Column (14) of Block 8.d on Format 

1 of this report. 

13.3.9.4.7. Column (16) - Total Budget. On the PMB (Beginning of Period) 

line (Block 6.a) enter the number from Column (16) on the PMB (End of 

Period) line (Block 6.c) from the previous CPR. In the section where 

basel~ne changes that occurred dur~ng the per~od are listed (Column (1) 

of Block 6.b), enter the amount of each of the changes listed. On the 

PMB (End of Period) line (Block 6.c), enter the sum of the amounts in the 

preceding columns on this line. On the Management Reserve line (Block 7), 

enter the amount of MR available at the end of the per~od. On the Total 

line (Block 8) enter the sum of the amounts in this column on the PMB 

(End of Period) line and the Management Reserve line. (Note: This should 

equal the amount in Block 5.f on th~s format and also the amount of the 

Total line in Column (14), Block 8.g, of Format 1.) 







13.3.9.5. Format 4 - Staff~ng. 

13.3.9.5.1. Performance Data. For those organizational categories shown 

in Column (1) of Block 5, equivalent months shall be indicated for the 

current reporting period (Column (2)), cumulative through the current 

period (Column (3)), forecast to completion (Columns (4) through (14)), 

and at completion (Column (15)). Direct equivalent months shall be shown 

for each organizational category for the contract. An equivalent month 

is defined as the effort equal to that of one person for one month. 

Values shall be reported in whole numbers. (Note: Partial months, .5 and 

above, shall be rounded to 1; below .5 to 0.) When the Government and the 

contractor agree, staffing may be reported in equivalent days or hours. 

13.3.9.5 1.1. Column (1) -Organizational Category. In Block 5, list the 

organizational categories that reflect the contractor's internal 

management structure. Format 4 categories may differ from those reported 

in Format 2. If the Government needs different categories in Formats 2 

and 4, the Format 4 categories shall be addressed during negot~at~ons. 

(See f.4 above.) 

13.3.9.5.1.2. Total Direct. In Block 6, Columns (2) through (15) enter 

the sum of all direct equ~valent months for the organizational categories 

shown in Column (1). 

13.3.9.5.2. Column (2) - Actual - Current Period. Enter the actual 

equ~valent months incurred during the current reporting period. 

13.3.9.5 3. Column (3) - Actual End of Current Period (Cumulative). 

Enter the actual equ~valent months incurred to date (cumulative) as of 

the end of the reporting period. 

13.3.9.5 4. Columns (4) Through (14) - Forecast (Non-Cumulative). Enter 

the names of each month for the contract period of performance in the 

headings of each of the Columns (4) through (9), and the names of the 

appropriate periods in the headings of each of the Columns (10) through 

(14) of Block 5. Enter a staffing forecast by month for the next six 

months and for periodic increments (monthly, quarterly, or annually) 

thereafter for the remainder of the contract. The staffing forecast 

shall reflect the same staffing estimate used as the basis for the EAC in 

Column (15) on both Formats 1 and Format 2. (Note: For the purposes of 

illustration, Sample Format 4 has Columns (4) through (14) for reporting 

staffing forecast. The actual number of columns will vary from contract 

to contract.) 

13.3.9.5.5. Column (15) - Forecast at Completion. Enter the estimate of 

equivalent months necessary for the total contract in Column (15) by 

organizational category. This estimate shall be consistent with the 

'most likely' management EAC shown in Column (15) of Block 8.e of Format 

1. Any significant change in the total number of equ~valent months at 

complet~on of the contract (~.e., Column (15) Total) shall be explained 

in Format 5. 

13.3.9.6. Format 5 - Explanations and Problem Analyses. 

13.3.9 6.1. General. Format 5, Explanations and Problem Analyses, is a 

narrative report prepared to amplify and explain data in the other CPR 

formats. Format 5 shall normally address the following: (1) 

contractually required cost, schedule, and EAC variance analyses, (2) MR 

changes and usage, (3) UB contents, (4) differences between the best 

case, worst case, and most likely management EAC, if any, (5) the 

difference between the most likely management EAC and the estimate in 







Block 8.e of Column (15), if any, (6) significant differences between 

beginning of per~od PMB time phasing and end of period PMB time phasing 

~n Format 3, (7) performance measurement m~lestones that are inconsistent 

with contractual milestones (Over Target Schedule), (8) formal 

reprogramming (Over Target Baseline) ~mplementation details, and (9) 

significant staffing estimate changes in Format 4. Any other topic 

relevant to contract cost, schedule, or technical performance may be 

addressed in this format. The date(s) of the Integrated Baseline 

Review(s) may also be addressed in this format. Contractors may elect to 

attach subcontractor Format 5 reporting and cross reference this analysis 

in the Format 5 reporting submitted to the Government to gain time 

efficiencies and meet submiss~on dates. 

13.3.9.6.2. Total Contract. Prov~de a summary analysis that identifies 

sign~f~cant problems affecting performance. Indicate corrective actions 

required, including Government act~on where applicable. Significant 

changes since the previous report shall be highlighted. Discuss any 

other ~ssues affecting successful attainment of contract cost, schedule, 

or technical object~ves that the Contractor deems s~gn~ficant or 

noteworthy. This section is brief, normally one page. 

13.3.9.6.3. Cost and Schedule Variances. Exp1a~n all variances that 

exceed specified variance thresholds. Explanations of variances shall 

clearly identify the nature of the problem, significant reasons for cost 

or schedule variance, effect on the immediate task, impact on the total 

contract, and the corrective action taken or planned. Explanations of 

cost variances shall identify amounts attributable to rate changes 

separately from amounts applicable to hours worked; amounts attributable 

to material price changes separately from amounts appl~cable to material 

usage; and amounts attributable to overhead rate changes separately from 

amounts applicable to overhead base changes or changes in the overhead 

allocat~on basis To reduce the volume of variance analysis 

explanations, the Contractor may refer to a prior CPR's variance analysis 

explanations if the explanation for the current CPR's variance has not 

changed significantly. The contractor shall classify and document all 

variances as either 'risk-driven cost & schedule growth' or 'externallydriven 

cost & schedule growth' (see below for def~nit~ons) in Format 5 as 

source informat~on for the CADRe. The source of this ~nformation shall 

be at the Control Account level, however, the consolidation and customer 

reporting can be done at higher levels w~thin the performing organization 

'Risk-Driven Cost & Schedule Growth' (RDCG & RDSG) is that cost and 

schedule growth caused by overruns and funded or unfunded changes, linked 

to technical risks identified in paragraph 7.c.1 above. 'Externally 

Driven Cost & Schedule Growth' (EDCG & EDSG) is that cost and schedule 

growth caused by overruns and funded or unfunded changes, linked to 

external factors (e.g., requirements changes, techn~cal enhancements not 

driven by risk, perturbations to budgets by external agents causing 

schedule changes, etc.) over which the contractor has little, if any, 

control. (NOTE: The EDCG & EDSG drivers shall be specifically 

identified in variance analysis reporting). Explanations of schedule 

variances and the ~mpact on the contract shall be performed 1n parallel 

with the schedule analys~s called out by the IMS DID. 

13.3.9.6.3.1. Sett~ng Variance Analysis Thresholds. In Format 5, the 

Government will require only that amount of variance analysis that 

satisfies its management information needs. Excessive variance analysis 

~s burdensome and costly, and detracts from the CPR's usefulness, while 

too l~ttle ~nformation is equally undesirable. 

13.3.9.6 4. Other Analyses. In addition to var~ance explanations, the 

following analyses are mandatory: 







13.3.9.6.4.1. Management Estimate at Completion. If the best or worst 

case management EACs differ from the most l~kely estimate (Column (1) of 

Block 6 of Format 1), a brief explanation of the difference shall be 

provided. Also, if the most l~kely management EAC differs from the total 

entered in Column (15) of Format 1 or 2, the difference shall be 

explained. The explanations shall focus on such areas as a 

knowledgeable, real~st~c risk assessment; projected use of MR; estimate 

for DB; and higher management's knowledge of current or future contract 

conditions. The assumptions, conditions, and methodology underlying all 

management EACs shall be explained. (See 13.3.9.2.2 to 13.3.9.2.2.3., 

13.3.9.2.2.5, 13.3.9.2.6.9, and 13.3 9.2.6.10 above.) The reasons for 

significant sh~fts in time phasing of the EAC shall also be explained. 

13.3.9.6.4.2. Undistributed Budget. Identify the effort to which the DB 

applies. Also, expla~n any variance between the DB and the est~mate for 

UB ~n Formats 1 and 2. (See 13.3.9.2.4.4, and 13.3 9.3.1.4.above.) 

13.3.9.6.4.3. Management Reserve Changes. Identify the sources and uses 

of MR changes during the reporting period. Identify the CWES and 

organizat~onal elements to which MR is applied, and the reasons for its 

application. (See 13 3.9.2.4.6. above.) 

13.3.9.6.4.4. Baseline Changes. Explain reasons for significant shifts 

in time phasing of the PMB shown on Format 3. (See 13.3.9.4.2.3. above.) 

13.3.9.6.4.5. Staffing Level Changes. 

total staffing EAC shown on Format 4. 

significant shifts in time phasing of 

above. ) 

Explain significant changes in the 

Also, explain reasons for 

planned staffing. (See 13.3.9.5.5 

13.3.9.6.5. Formal Reprogramming (Over Target Baseline). If the 

difference shown in Block 5.g on Format 3 becomes a negative value or 

changes in value, provide information on the following. 

13.3.9.6.5.1. Author~zat~on Procuring activity authorization for the 

baseline change that resulted in negat~ve value or change. 

13.3.9.6.5.2. Reason. A discussion of the reason(s) for the change. 

13.3.9.6.5.3. CPR Report~ng. A discussion of how the change affected CPR 

reporting (i.e., amount allocated to MR, adJustments to cost or schedule 

variances, etc.). (See 13.3 9.4.1.7., 13.3.9.2.5.1., and 13.3.9.2.6.7. 

above. ) 

13.3.9.6.5.4. Schedule. Indicate whether the contract schedule was 

retained for performance measurement or was replaced with a schedule that 

exceeds the contractual schedule (Over Target Schedule). 

13.3.9.6.5.5. Over Target Schedule. If a performance measurement 

schedule exceeding the contractual schedule (Over Target Schedule) has 

been implemented, provide a d~scuss~on of the pertinent information, such 

as authorization, reasons, and significant dates. (See 13.3.9.4.1.10.1 

above. ) 

13.4 FORMAT: CPR formats shall be completed according to the instructions 

outlined in th~s DRD: 

The IMS shall be created using a network capable scheduling software 

application. The IMS shall be del~vered in native digital format (i.e., 

an electron~c file produced by the Contractor's scheduling tool). The 

IMS shall be submitted electronically per Section J-2 2.3.2.1 and 3. The 







American National Standards Institute (ANSI) Xl2 standard (806 

transaction set), the Unlted Nations Electronlc Data Interchange for 

Adminlstration, Commerce and Transport (UN/EDIFACT) standard (PROTAP 

message) ,or the XML equivalent shall be used to submlt data 

electronically to the procuring activity with on-line access to the data. 

Those CPR Forms are reproduced at the end of this document and can also 

be found in the Bidder's Reference Library. Contractor formats shall be 

substituted for CPR formats whenever they contain all the required data 

elements at the specified reporting levels in a form suitable for NASA 

management use. 

13 5 MAINTENANCE: Changes shall be lncorporated by complete relssue. 








1. 

3 

6. 

PROGRAM: CEV 

DATA TYPE 3 

TITLE' Property Financial Reporting 

2 

4. 

5. 

DRDNO.: CEV-B-004 

DATE REVISED' May 2009 

PAGE: 1 

The only change to this DRD is in #3: 

From "Data Type 2" 

To Data "Type 3" 


CEV-B-004 Page 1 of!





1. 

3. 

PROGRAM: CEV 

DATA TYPE: 2 

2. 

4. 

5. 

6. TITLE. Flight Test Article (FTA) Definition 

DRDNO.: 

DATE REVISED' 

PAGE: 

CEV-D-001 

May 2009 

1 

7. DESCRIPTIONIUSE' 

The DRD describes the FTA design concept based on the objectives 

specified in SOW Tables 10 1 Abort Flight Test Matr1x and 10.2 

Integrated Flight Test Matrix. Based on the object1ves identified in 

these tables, the DRD descr1bes the FTA configuration proposed for each 

test. The DRD is a precursor to a more definitive FTA System 

Requirements document. 

8. DISTRIBUTION: As determined by the Contracting Officer. 

9 INITIAL SUBMISSION' Per Data Requirements Matrix 

10 SUBMISSION FREQUENCY Per Data Requirements Matrix 

11. REMARKS: 

12. INTERRELATIONSHIP: Parent SOW Paragraph(s): 10.6.4. 


13.1 SCOPE 

13.2 APPLICABLE DOCUMENTS. 


The FTA Configuration Definition DRD describes the arch1tecture of each 

FTA, and for which flight test the FTA will be used. 

Each FTA includes the following· 

- FTA Number. 

- The relationship of th1s FTA to tables 10.1 Abort Flight Test Matrix 

and 10.2 Ares Flight Test Matr1x that 1dentify which test the FTA is 

linked to. 

- The flight specific flight test objectives that are designated as a 

primary or secondary objective and whether the objective is to 

Demonstrate l Determiner or Obtain. 

- Description of FTA proposed architecture: 

o Launch Abort System (LAS) Concept 

- Passive vs Active 

- Hardware and software 

- F1de11ty compared to Flight LAS (Concept, Proto Type, Flight) 

o Structures and mechanisms 

o Avionics and power scheme 

o Software arch1tecture, 1nclud1ng its relationship to the production 

vehicle software 

o Ground Support Equipment architecture 

o Ground Support Equipment hardware and software architecture 


CEV-D-OOI Page 1 of2





o Guidance Navigat10n & Control scheme 

o Vehicle System Management (VSM) scheme (as applicable) 

o Estimated Software Lines of Code (SLOC) (new and reused, including 

software reused from prior FTA releases) 

o Redundancy scheme 

o Instrumentation plan 

o Ground support equ1pment requirements 

o Reusability plans 

o Spares plan. 

For each area, describe plans for the use of COTS hardware and Software 

as well as new hardware and software development 

13.4 FORMAT. Documents shall be electronic format per Section J -2 2.3.2.1 

13.5 MAINTENANCE: Changes shall be identified and complete re-1ssue of the 

document is required. 


CEV-D-OOI Page 2 of2





1. 

3 

6. 

7. 

PROGRAM. CEV 2 DRDNO.: CEV-D-002 

DATA TYPE: 2/3* 4. DATE REVISED: May 2009 

5. PAGE' 1 

TITLE: Flight Test Artl.cle (FTA) Specifications 

DESCRIPTIONIUSE: 

The FTA Specificatl.on DRD documents the allocation of the: 

- Flight Test Ml.ssion and Flight Objectl.ves (CxP 72166) to the FTA System 

Requirements Specificatl.on. 

- FTA System Level requirements to the FTA Module level & Contractor 

provided Ground Support Equipment (GSE) Module level requirements 

specification 

- FTA & GSE module requirements to the FTA &GSE subsystem level 

- FTA & GSE subsystem requirements to the hardware component and software 

CSCI level, and GSE End Item level 

To specify the interface requl.rements between each module, between 

Contractor-provided GSE & FTA, between each subsystem, and between 

Computer Software Configuration Items (CSCls). Also to specify 

requl.rements imposed upon or by manual operations, or other system 

components to achieve one or more interfaces among the modules, 

subsystems, and CSCls. To be used l.n conjunction with the Software 

Requirements Specification as a basl.s for design and proto-qualification 

testing of software systems and CSCls. 

To provide documentatl.on in the form of drawings and/or written records 

to identify for each side of an interface those necessary design 

definitions between one or more systems, modules, subsystems, computer 

software configuration items (CSCI's), manual operations, contractors 

and/or Government agencies to provide control of and ensure an agreeable 

and compatible interface. The Interface Control Document (ICD) provides 

the design solutions to the requirements found l.n the system 

specifications and/or the Interface Requirements Document (IRD); these 

companion documents serve to communicate and control interface design 

decisions. 

8. DISTRIBUTION: As determined by the Contractl.ng Officer. 

9. INITIAL SUBMISSION: Per Data Requirements Matrix 

10. SUBMISSION FREQUENCY: Per Data Requirements Matrix 

11. REMARKS: 

For PA-1 and AA-1 Contractor-provided FTA & GSE, all module, subsystem, 

hardware component-level and software CSCI-Ievel, and end-item-Ievel 

requirement documents have FTO-AFT-FTA-004, FTA SRD, as their parent 

document For PA-2, and AA-2, Contractor-provided FTA & GSE, all 

module, subsystem, hardware com[ponent-level and software CSCI-level, and 

end item-level requirements documents wl.II have DRD CEV-D-002, FTA SRD as 

their parent document. A common format shall be used across the module, 

subsystem, hardware component end item-level, and software CSCI-level 

requirements documents. 

In naming each document, should be replaced with the appropriate 

name (e.g., FTA Crew Module Requirements Specification, etc.). 

All system level, subsystem level, LAS abort motor, jettl.son motor and 


CEV-D-002 Page 1 of 4





attitude control motor level, LAV, CM, and GSE module level requirement 

documents are type 2 documents. All external interface and subsystem 

level interface documents are type 2 documents. 

All hardware component-level, end ~tem-Ievel requirements and SRS 

documents are type 3 documents. All internal interface documents are type 

3 documents. 

The following document(s) may be used as guidance: 

IEEE/EIA 12207.1-1997: Industry Implementation of International 

Standard ISO/IEC 12207; 1995, Standard for Information Technology - 

Software life cycle processes - Lifecycle data. 

12. INTERRELATIONSHIP: Parent sow Paragraph(s): 10.6 4. 

Referenced from sow Paragraph(s): 6.1.6.2, 10.6.6.9. 

13. DATA PREPARATION INFORMATION. 

13.1 SCOPE: The FTA Specification DRD establishes the format and 

contents of the follow~ng requirements specifications: 

- Contractor-provided FTA & GSE Module Requirements Specifications 

- The subsequent Cotractor-prov~ded subsystem, hardware component-level 

and software CSCI-Ievel, and end item-level requirements specifications, 

including GSE components and CSCIs. 

The Internal Interface Requirements Document (IRD) shall contain the 

interface requirements between each of the CEV modules, subsystems, and 

CSCI ~nterfaces within the FTA & GSE. This specification also details 

provisions for qualification and requirements traceability. An IRD shall 

be produced for each CSCI that ~nterfaces to another CSCI and for each 

CSCI that interfaces directly to a hardware component. The corresponding 

interface verification requirements for the IRDs will be contained in the 

applicable Interface Control Document (ICD). 

The Interface Control Documents (lCD's) identify design definitions for 

each side of an interface that shall ensure design control and 

compatibility. An ICD may describe any number of software interfaces. 


FTO-AFT-FTA-004, FTA SRD 

CxP 72166, Flight Test Vehicle Mission and Flight Objectives document, 

Version: Baseline 

FTO-AFT-OPS-001, Concept of Operat~ons 

FTO-AFT-FTA-001, FTA Environmental Requirements document 

FTO-AFT-FTA-003, FTA Geometry and Mass Properties document 

The following documents may be used for Reference: 

RCC Standard 321-02, Common Risk Criteria for Nat~onal Test Ranges 

White Sands Missile Range Regulation 385-17, Missile Flight Safety 

Department of the Army Pamphlet 385-64, Ammunition and Explosives Safety 

Standards 

Army Test and Evaluation Command (ATEC) Regulation 385-1, ATEC Safety 

Program 

NPR 7150.2' NASA Software Engineering Requirements 

13 3 CONTENTS. 

The FTA Systems Requirements Specificat~on shall be the allocation of the 

"Mission and Flight Objectives" document, CxP 72166, to the Flight Test. 

The FTA module requirements spec~f~cations shall decompose the FTA system 

functional, performance, and operational requirements to the module 


CEV-D-002 Page 2 of 4





level. A FTA module is defined as a self-contained unit of a spacecraft 

that performs a specific task or class of tasks in support of the major 

function of the craft. For example, a FTA may be broken up into a crew 

module, a service module, etc. 

The GSE module requirments specification shall decompose FTA System GSE 

functional, performance, and operat1onal requirements to the GSE 

Subsystem level. 

The FTA & GSE subsystem requirements spec1fications shall decompose the 

FTA & GSE module functional, performance, constraints and design 

requirements to def1ne the design and arch1tecture of the total 

subsystem, includ1ng software. 

The FTA component & GSE end item requirements specifications shall 

contain the decomposition of the requirements from the FTA & GSE 

subsystem level through the lowest level of the decomposition. This 

specification will document the allocated funct1onal, performance, 

constraints and des1gn requirements for the FTA & GSE subsystem to the 

component/end item-level. For the purposes of this DRD, 'component' will 

be used to describe each level of the decomposit10n below the subsystem 

level as defined by the Contractor. The decomposition of the subsystem 

is continued until a procurement or build-to specificat10n has been 

developed. A component is defined as an aggregate of hardware and/or 

software that can be characterized by one specification, is designed by a 

single activity to be functionally tested, and 1S verified as a unit. 

The Software Requiremetns Specification (SRS) details the software 

functional, performance, interface, operational, and quality assurance 

requirements. SRSs are produced for each CSCI. At the contractor's 

discretion, SRSs can be produced as a single document with a section for 

each CSCI. 

Each document shall contain a sect10n titled 'Verification'. For each 

requirement in the documents, there shall be a corresponding verification 

requirement. The document shall contain, in addition to the verification 

requirements, a ver1f1cation traceability matrix that establishes the 

relationship between each requirement and its verification requirements, 

and contains the methods that will be used to accomplish the indicated 

verification actions. 

The Internal Interface Requirements Document (IRD) shall define all 

physical, functional and procedural interface requirements to ensure 

system, hardware, GSE, and software compat1b1lity. The IRDs shall 

include the following: 

a. Physical - Interface requirements involving physical mating and 

spatial relationships between interconnecting parts of interfacing end 

1tems, including clearance envelopes established to avoid interferences 

and to permit access. 

b Functional - Interfaces involving the interaction or influence 

of condit10ns imposed by one subsystem or component upon another or by 

external sources such as fluids, thermal, electrical, environmental, 

data, and loads. 

c. Procedural - Interfaces involving cr1t1cal sequence of events 

occurring in assembly, disassembly, alignment, service operations, and 

computer programs. 

For software, using IEEE/EIA 12207.1-1997 as guidance, IRD shall include: 

d. Requirements imposed on one or more modules, subsystems, 

conf1guration items, manual operations or other system components to 

achieve one or more software interfaces among these entities. 

1. Interface identification and diagrams. 

2. ProJect-unique identifier of interface. 


CEV·D·002 Page 3 of 4



3. Precedence and criticallty of requirements. 

e. proto-qualification provlsions. 

f. Requirements traceablllty. 

The Interface Control Document (ICD) shall document the physical, 

functional, and procedural interface design. The ICD shall provide the 

descriptive text and diagrams to fully describe the interface 

implementation. The ICD shall address all of the engineering disciplines 

associated with the interface design. The ICD shall identify all 

applicable workmanship and applicable standards being utilized as part of 

the interface design. The ICD shall provide traceability from the 

Interface Requirements Document (IRD) to document design compliance with 

the requirements. 

The ICD shall address the following class of interfaces: 

(a) Physical - Interfaces invo1vlng physical matlng and spatial 

relationships between interconnecting parts of interfaclng end items, 

including clearance envelopes established to avold interferences and to 

permit access. 

(b) Functl0na1 - Interfaces lnvo1ving the interaction or influence of 

conditions imposed by one subsystem or component upon another or by 

external sources such as fluids, thermal, electrical, environmental, 


(c) Procedural - Interfaces involving critical sequence of events 

occurring in assembly, dlsassemb1y, alignment, service operations, and 


For software, in accordance with NPR 7150.2 NASA Software Engineering 

Requirements (class C & D definitions & requirements, only), and using 

IEEE/EIA 12207.1-1997 as guidance, the ICD shall include: 

(d) Priority assigned to the interface by the lnterfacing entity(ies). 

(e) Type of interface (e.g., real-time data transfer, storage-andretrieval 

of data) to be lmp1emented. 

(f) Specification of lndividua1 data elements, format, and data content 

including bit-level descrlptions of data interface that the interfacing 

entity(ies) will provlde, store, send, access, receive. 

(g) Specification of data element assemblies, format, and data content 

including bit-level descriptions of data interface that the interfacing 

entlty(ies) will provide, store, send, access, recelve. 

(h) Specification of communication methods that the interfacing 

entity(ies) will use for the interface. 

(i) Specificatl0n of protocols the interfaclng entity(ies) will use for 

the interface. 

(j) Other specifications, such as physical compatibility of the 

lnterfacing entity(ies) . 

(k) Traceability from each interfacing entity to the system or CSCI 

requirements addressed by the entity's interface design, and traceability 

from each system or CSCI requirement that affects an interface. 

(1) Interface compatibility, e.g., little endian vs. big endian. 

13.4 FORMAT: Documents shall be electronic format per Section J-2 2.3.2.1. 

13.5 MAINTENANCE: Changes shall be ldentified and complete re-issue of the 

document is requlred. 


CEV -D-002 Page 4 of 4




I. 

3 

PROGRAM. CEV 

DATA TYPE' 2 


2. 

4. 

5. 

DRDNO .. 

DATE REVISED: 

PAGE: 

6. TITLE: Flight Test Article (FTA) Engineering Design Data Book 

CEV-D-004 

May 2009 

1 

7. DESCRIPTIONIUSE 

Documents the FTA design in adequate detail for FTA integration with the 

Abort Test Booster (ATB) , Test Range, Test Facility. Documents the 

design in adequate detail for final assembly, integration, and test 

activities performed at the designated NASA facility for PA-1 and AA-1. 

Provides adequate technlcal documentation to satisfy safety reviews and 

test readiness reviews. 

8 

9. 

10 

II. 

12 

13 

13.1 

13.2 

DISTRIBUTION As determined by the Contracting Officer. 

INITIAL SUBMISSION: Per Data Requirements Matrix 

SUBMISSION FREQUENCY: Per Data Requirements Matrix 

REMARKS: 

INTERRELATIONSHIP' Parent sow Paragraph(s): 10.6.4, 10.6.6.9. 

Referenced from sow Paragraph: 6.1.6.2 

DATA PREPARATION INFORMATION: 

SCOPE' 

APPLICABLE DOCUMENTS. 

133 

1. 

CONTENTS: 

Launch Abort System LAS, Engineering Design Data Book 

a. Contractor specified design and production standards for the LAS. 

b. All data necessary to support compliance to the contractor 

speclfled design and production standards for the LAS. 

c. All LAS Diagrams, Drawings, Analysis & Models for the specific 

FTA. 

d. Any supporting data needed to completely understand the operation 

of the LAS. 

e. Identificatlon of lift points and description of lifting 

operations expected prior to the fllght test and during post test 

recovery. 

f. detailed description of each mechanism, including a description of 

their functional requirements and operating environments. 

g. A llst of mandatory inspection points 

2. Crew Module CM, Engineering Design Data Book 

a. Contractor specified design and productlon standards for the CM. 

b. All data necessary to support compllance to the contractor 

speclfled design and production standards for the CM. 

c. All CM Diagrams, Drawings & Models for the specific FTA. 

d. Any supporting data needed to completely understand the operation 

of the CM. 

e 

Identification of lift points and descrlption of lifting 

operations expected prior to the flight test and during post test 

recovery 


CEV-D-004Page I of3





f. detailed description of each mechanism, includ~ng a description of 

their functional requirements and operat~ng environments. 

g. A list of mandatory inspection po~nts. 

3. Contractor-provided Spacecraft Adapter/Service Module SA/SM, Engineering 

Design Data Book 

a. Contractor specified design and production standards for the 

SA/SM. 

b. All data necessary to support compliance to the contractor 

specified design and production standards for the SA/SM. 

c. All SA/SM Diagrams, Drawings & Models for the specific FTA. 

d. Any support~ng data needed to completely understand the operation 

of the SA/SM 

e. Identification of l~ft points and description of l~ft~ng 

operations expected prior to the flight test and during post test 

recovery. 

f. detailed description of each mechan~sm, including a description of 

their funct~onal requ~rements and operating environments. 

g. A list of mandatory inspection points. 

4. Avionics and Power, Engineering Design Data Book 

a. Contractor specified requirements and design and production 

standards for Avionics and Power systems. 

b. All data and analyses necessary to support compl~ance to the 

Contractor specified requirements and design and production 

standards. 

c. Electrical Power System Circuit Protection and Isolation Plan. 

Plan and provisions for establishing, and maintaining electrical 

circuit protection for the FTA and FTA interfaces (including human 

safety) with ground maintenance/test facilities, Abort Test 

Booster, recovery, and refurb~shment facilities (if applicable) . 

d. Functional schematics 

e. Electrical Power System Grounding Analysis. Documents the 

electrical grounding des~gn. Documents the analysis results of 

the electr~cal grounding. 

f. Electrical Power System Voltage Drop Analysis. Documents the 

analysis results using circuit res~stance values based On wire 

size, wire length, temperature conditions, circuit element 

resistances, and varying load conditions. Documents voltage drops 

on all major circu~ts, loads, and interfaces at varying load 

cond~tions. 

g. Electr~cal Power System Transient Analyses. Documents the 

analysis results us~ng normal and worst case subsystem and system 

interface cond~t~ons (voltage and bus transient and ripple) , 

evaluates the design for proper performance and compatibility, and 

assures adequate margins between the source and the loads. Also 

documents the evaluation of power on/off sw~tching transient 

generat~on for adverse (out-of-spec.) impacts to the interfacing 

bus 

h. Electrical Power System Equipment Description, Design, Drawings 

and Performance Data. Comprehens~ve equ~pment documentation of the 

electrical power system that will provide detailed reference 

~nfor.mat~on for supporting Engineering and Operations including 

funct~onal block diagrams. 

i. Av~on~cs Equ~pment Description, Design, Drawings and Performance 

Data. Comprehensive equipment documentation of the Avion1cs 

subsystem that will provide detailed reference 1nformation for 

supporting Engineering and Operations including functional block 

diagrams. 

5. Fl~ght Software, Engineering Design Data Book 

a. Flight Software Development Plans. 

b. Flight Software Descriptions. 


CEV-D-004 Page 2 of3





c. Flight Software Dictionary. 

d. CSC! architectural design 

e. CSC! decomposition and lnterrelationship between software 

components, includlng lts evolution path to the production vehicle 

software. 

f. Any Additional Flight Software documentation of the subsystem that 

will provide detailed reference information for supporting 

Engineering and Operatlons including functional block diagrams. 

6. Systems Analysis, Engineering Design Data Book 

a. Loads & Environments Analyses 

b. GN&C Analyses 

c. AeroSClences Analyses 

d. Thermal Analyses 

e. Mission Analyses 

13 4 FORMAT: Contractor may divide into volumes/books if necessary. Models 

and code shall be submltted in their native format. Electronic format 

requlrements per Section J-2 2.3.2.1 shall be followed as well. 

13.5 MAINTENANCE· Changes shall be ldentified and complete re-issue of the 

document or other product is required. 


CEV-D-004 Page 3 of3




1. 

3. 

PROGRAM. CEV 

DATA TYPE: 1/3/3 * 


2. 

4. 

5. 

DRDNO .. 

DATE REVISED: 

PAGE' 

CEV-M-002 

May 2009 

1 

6 TITLE: Performance Assessment plan, Reports and Management Reviews 

7. DESCRIPTIONIUSE: 

The Performance Assessment Plan provides the overall contract performance 

measurement approach. The initial submittal will be used in developing 

the Surveillance Plan. 

The Performance Assessment Reports are a key component of quarterly and 

semi-annual performance assessments. 

The Performance Management Review packages that support the quarterly 

management reviews of costs, schedule, and technlcal performance. The 

format provides a standardlzed approach for review materials. 

8. DISTRIBUTION As determined by the Contracting Officer 

9 INITIAL SUBMISSION Per Data Requirements Matrix 


11. REMARKS: 

NASA Data Management will send notification to the following: 

Financial Office 

Assessment Office 

Contractlng Officer 

Contracting Offlcer's Technical Representative (COTR) 

* Plan is Type 1, Reports are Type 3, Review Packages are Type 3 

12. INTERRELATIONSHIP: Parent SOW Paragraph(s): 1.1.b 

Referenced from SOW Paragraph: 1.2. (d) 


131 SCOPE. 

The Performance Assessment plan shall descrlbe the Contractor's overall 

approach to contract performance assessment and the implementation 

process for accomplishing metrlc evaluation and reporting. 

The Performance Assessment Reports shall provide a self-assessment for 

quarterly and semi-annual performance assessments reporting periods. 

Performance Management Review data packages document the integrated 

management reviews of the cost, schedule, and technical performance on 

the contract. The reviews are held quarterly. These packages must be 

reconcilable with Financlal Management Report (533) reporting, DRD CEV-B- 

001. 

13 2 APPLICABLE DOCUMENTS: 

CXP-72000: Crew Exploratl0n Vehicle System Requirements Document (CEV 

SRD) 

NPR 9501.2D. NASA Contractor Financial Management Reporting 

13.3 CONTENTS: 


CEV-M-002 Page I oB





The Performance Assessment Plan shall conslst of the following: 

(a) Description of the Contractor's approach and rationale for assessing 

performance, lncluding reporting on the status of 'should' requirements 

in CXP-72000, Crew Exploration Vehicle System Requirements Document (CEV 

SRD) and the sow. 

(b) Description of the methods the Contractor plans to use to assess 

performance, systems used, reporting mechanisms, and how the data will be 

used to lmprove future performance and adjust to changing requirements. 

(c) Description of management systems and processes used to implement the 

plan includlng the developing, timely gathering, compiling, maintainlng, 

audlting, analyzing, reporting, and provlding management reVlew of 

performance metrics. 

(d) Descript10n of the performance metrics including references to SOW 

paragraphs. 

(e) Description of the Technlcal Performance Parameters (TPPs) selected 

by the Contractor, and approved by NASA, for monitoring during the design 

and development. The Performance Assessment Plan shall identify a subset 

of the data included in the Margins Management Plan as TPPs. The TPPs 

will be proposed in the initial Performance Assessment Plan and 

'selected' via approval of the Plan. Examples of TPPs are margins for 

mass properties, power allocatlon, volume, CPU utilization, 

bandwidth/throughput. 

(f) Descriptlon of any metrics used to address the performance toward IMP 

events, including the rationale for the development process and linkage 

between the metrics and the IMP events. 

The metric descrlption shall consist of at least the following for each 

metric: 

(a) Definition and descrlptlon of the metric 

(b) Graphical representatlon 

(c) Algorlthm (if calculated) 

(d) Assessment criteria for expected (standard) performance and excellent 

performance 

The Performance Assessment Reports for metrics shall consist of the 

following: 

(a) Contractor's summary assessment ('metric score card') for all metrics 

(b) Status of all Technical Performance Parameters and their margin 

growth/loss and forecast 

(c) Metrics as described in the plan updated to reflect actual 

performance and quality durlng the period 

(d) Narrative performance assessment by month for each metric 

(e) Historical performance data 

(f) Index of any changes to metrlcs since the last period 

(g) Recommended action (i.e performance improvement lnitiatives, lessons 

learned) 

The Performance Management Review data packages support the quarterly 

management review of cost, schedule, and technical performance. Metrics 

for the lnitial submittal, including the Technical Performance Parameters 

(TPP) , shall come from Contractor's approved Performance Assessment plan. 

These metrics shall provide linkage to CEV Project-level metrlCS and 

Constellation Program-level metrics in the Integrated Collaborative 

Environment. The cost baseline 18 the Performance Measurement Baseline 

(PMB). The format provides a standardized approach for review materials. 

The quarterly Performance Management Review package consists of: 

(a) Summary section 

(b) Pertlnent performance/outcome based metrics (as requested by the PM, 

COTR) 

(c) Technical performance parameters (including margin growth/loss and 

forecast) 

(d) Stoplight status of fiscal year project cost, schedule, and technical 


CEV-M-002 Page 2 of3





performance 

(e) Summary status of fiscal year reserves, risks and opportunities, and 

earned value performance 

(f) Fiscal year cost and workforce summarles (including attrition 

metrics) 

(g) Cumulative variance explanations (to fiscal year plan) and end-ofyear 

trend variance explanations (if threshold criteria exceeded) 

(h) SOW reconciliation (i.e., special projects, etc. that need to be 

accounted for) (as required) 

(i) Status of CXP-lOOOl, Systems Requirements for the Crew Exploration 

Vehicle Element (CEV SRD) and SOW 'shoulds' 

(J) Areas of emphasis summary 

(k) Major contract milestone schedule - 90 Day lookahead 

(1) Component Sections (done at major element/organization/subsystem 

level) : 

Include all Summary Section items 

Significant achlevements 

• Pertinent next level performance/outcome based metrics (include any 

other yellow or red metrics) 

• Details of technlcal, cost and schedule risks and opportunities 

(m) Total contract plannlng assumptions for budget horizon estimates (5 

years) (e.g., assumed launch sequence of Constellation elements), work 

content summary, workload drivers 

(n) Cost and workforce estimates through the budget horizon (5 years) 

(updates to work packages or their plannlng packages) 

(0) Major project milestone schedule - 5 Year lookahead (updated as 

required) 

(p) Life cycle cost analysis update since last major design review 

(q) Summary risks and opportunities (unique to the project, the budget 

for the extended horlzon) 

13.4 FORMAT: Electronic format per Section J-2 2.3.2.1. 

13.5 MAINTENANCE: Contractor-proposed changes shall be submitted to NASA 

for approval. Complete re-issue of the documents are required. The 

Performance Assessment plan, lncluding metrics, shall be reviewed 

annually and updated as required. Metrics shall be evaluated, updated 

and reported on a monthly basis on the web. Performance Management 

Review data packages shall be updated for quarterly Performance 

Management Revlews 


CEV-M-002 Page 3 on





1. 

3. 

PROGRAM: CEV 

DATA TYPE: 2/3* 

6. TITLE: Risk Management plan and Reports 

2 

4. 

5. 

DRDNO.: 

DATE REVISED: 

PAGE' 

CEV-M-005 

May 2009 

1 


To provide the Contractor and the Government a baseline document for 

planning, management, control, and implementation of the Contractor's 

risk management program. To implement a risk management process that is 

consistent with the government provided guidelines. To develop and 

maintain risk management waterfall charts. 



10. SUBMISSION FREQUENCY: Per Data Requuements Matrix 

11. REMARKS: 

* The Risk Management Plan shall be data type 2. All other submissions 

are type 3. 

12. INTERRELATIONSHIP: Parent SOW Paragraph(s): 1. 4. 

Related DRD(s): CEV-S-001 


13 1 SCOPE. 

The Risk Management Plan addresses how NASA risk management requ~rements 

are to be implemented throughout the proJect's life cycle. The Risk 

Management Report provides a status of risks and risk mitigation plans 

and activities. 


CxP 72091, Constellation Integrated Risk Management 


The Risk Management Report shall contain the following data (Monthly): 

(a) Risk ID #, R~sk Statement, Risk Context, L~kelihood of Occurrence 

score and rationales, Consequence of Occurrence score (with cost, 

schedule, and techn~cal rationale), and T~meframe. Risk Consequence and 

Risk Likelihood shall be def~ned and scored consistent with the risk 

management requirements. 

(b) The Risk Waterfall chart for all high and med1um rated risks. The 

R1sk Waterfall chart is a graphical representat10n of the risk mitigation 

planning when a task plan is required. 

(c) Status of all risk mitigation plans and metrics. 

(d) Summary of risk mitigation activity and progress including objective 

evidence of exit criteria accomplishments. 

(e) Cost est1mate, applicable schedule, and allocated resources for 

mitigation activity 

(f) Documentation of contingency planning for risks that could not be 

successfully mitigated, accepted, or closed. 

(g) Summary of risk analyses. 

Identified unfunded risks will conta1n the following data (Monthly): 

(a) Risk ID#, R1sk Statement, Risk Context, Likelihood of Occurrence 







score and rationales, Consequence of Occurrence score (with cost, 

schedule and technical rationale) and Timeframe. Risk Consequence and 

Risk Likel1hood shall be defined and scored consistent with the risk 

management requirements. For Unfunded risks a Change 

Request will be written containing the Contractor's proposal for 

mitigation, cost est1mates and justificat1on. 

(b) Cost estimate, applicable schedule, and allocated resources for 

mitigation activity. 

(c) Documentation of cont1ngency planning 

(d) Integrated prioritized r1sk listing (including funded and unfunded 

risks) based on System needs. 

The Contractor shall use a database tool compatible with the Integrated 

Collaborative Environment (ICE) Active R1sk Manager Database to track 

identification and treatment of risks. If the ICE Active Risk Manager 

Database itself is not ut111zed, then the Contractor database shall be 

capable of exporting all required risk data to an Excel-based flat ICE 

Active Risk Manager database format file compatible with the ICE Active 

Risk Manager Database and delivered monthly with the risk management 

report. 

WATERFALL CHART FEATURES 

The plot of Risk Level vs. Calendar Time will be divided 1nto three 

colored areas. 

Risk Exposure Level 

High 

Moderate 

Low 

Color 

Red 

Yellow 

Green 

Determination of r1sk level is the qualitative combination of the 

likelihood of occurrence and the consequences of occurrence. The steps on 

the waterfall chart (Activities) are called gates. When a gate is 

completed, a downward step 1n Risk Level is achieved. As progress is made 

1n completing the risk reduct10n plan, the line showing Risk Level is 

thickened to the point in time where activities have been completed. The 

chart will also contain the follow1ng features: 

(a) Gates will be denoted with activity numbers. 

(b) The chart will contain labels for the activit1es and exit criteria. 

(c) The three colored areas are labeled High, Moderate, and Low. 

(d) The risk identification title 1S at the top of the page. 

(e) The risk file name and date of last update are shown in the bottom 

right corner. 

(f) Project milestones such as major tests and project and applicable 

program reviews are placed along the Calendar time axis. 

If gate completion is delayed, and the completion date is not known, the 

risk level 11ne 1S extended past the step to the current p01nt in time. 

If an activity completion date changes, the or1ginal plan will be shown 

as a dashed line and the new plan denoted with a sol1d line. Activity 

numbers should be shown on both the original and new steps on the 

waterfall chart 

RISK RECOVERY PLAN 

The risk recovery plan describes actions to be taken if act1vit1es in the 

risk reduction plan on the waterfall chart are not successfully 

completed. Recovery act10ns should be outlined for all gates, but at a 

minimum, they should be completed for any gate associated with a change 

in Technical Risk Level from High to Moderate or Moderate to Low and for 

gates associated w1th important testing. This plan will be attached to 

the waterfall chart and w1ll contain the following features: 







(a) Risk title. 

(b) Gate numbers. 

(c) Activities names. 

(d) Exit criteria associated with the activities. 

(e) Actual and planned activity completion dates. 

(f) Recovery plan for the gate. If the gate is completed successfully, 

the recovery actions are removed from the chart. For completed 

activities, which required some or all of the recovery actions, those 

actions should remain on the chart 

(g) Recovery plan activities outside of the project's scope should be 

flagged. 

(h) The appropriate proprietary markings are placed at the top and bottom 

of the chart. 


13 5 MAINTENANCE: Contractor-proposed changes to document shall be 

submitted to NASA for approval. Complete re-issue of the document is 

required. 








1. PROGRAM: CEV 2 DRDNO.: 

3. DATA TYPE: 1 4 DATE REVISED: 

5 PAGE: 

6. TITLE: Lunar Block Upgrade Plan 

CEV-M-006 

May 2009 

1 


The Lunar Block Upgrade plan prov~des an approach and detailed listing of 

those requirements and planned configurat~on changes which are being 

deferred to a future contract act~vity. 


9 INITIAL SUBMISSION: Per Data Requirements Matrix 


11. REMARKS: 

None 

12 INTERRELATIONSHIP Parent SOW Paragraph(s): 1.1.m 

13 DATA PREPARATION INFORMATION: 

13.1 SCOPE' 

The Lunar Block Upgrade Plan shall describe the Contractor's approach to 

support NASA in the management of contract requirements which are being 

deferred to a future contract activity. 

13 2 APPLICABLE DOCUMENTS. N/A 

13.3 CONTENTS 

The Lunar Block Upgrade Plan shall contain the following: 

(a) The Contractor's approach to ~mplementing a Lunar Block Upgrade plan 

(b) Future contract Lunar Block Upgrade content: 

i) Specif1c Contract applicable document reference 

ii) Recommended conf1guration change defined to lowest known level 

iii) Level and type of verifcation required 

iv) Projected Schedule for Implementation 

13.4 FORMAT: Electronic format per Section J -2 2.3.2.1. 

13.5 MAINTENANCE: Contractor-proposed changes shall be subm1tted to NASA 

for approval. Complete re-issue of the document is required. 


CEV-M-006Page 1 of1





1. 

3. 

PROGRAM: CEV 

DATA TYPE: 2 

2. 

4. 

5 

6. TITLE' Contractor's CEV Concept of OperatJ.ons 

DRDNO.· 

DATE REVISED: 

PAGE. 

CEV-O-001 

May 2009 

1 


ThJ.s document descrJ.bes the contractor-recommended life cycle operations 

concepts for the entire CEV System. This document is necessary to provide 

a mechanism for NASA to understand and assess the Contractor's CEV 

Concept of Operations (CONOPS) for J.ntegration with NASA's CEV concept of 

operations. It also provJ.des an integration mechanism with the CEV 

design process to assure operational needs and attributes are 

appropriately implemented in the design. While the CONOPS does not 

represent explicit design-to requirements, it is expected that the CONOPS 

wJ.ll be reflected in the allocated requJ.rements baseline derived using 

the CONOPS as a source. 

8. DISTRIBUTION. Per ContractJ.ng Officer's letter 


10. SUBMISSION FREQUENCY: Per Data RequJ.rements Matrix 

11 REMARKS: 


ANSI/AIAA G043-1992: Guidance for Preparation of Operational Concept 

Documents 

CxP-70007: Constellation Design Reference Missions and Operational 

Concepts 

12. INTERRELATIONSIDP: Parent sow Paragraph (s): 2 7.1. 

Referenced from sow Paragraph(s): 2.7.2. (e) 


131 SCOPE: 

The Contractor's CEV Concept of Operations describes operations for the 

entire CEV System from delivery of the spacecraft to the launch site, 

through pre-launch processing, pre-mission flight design and planning, 

launch, flight , re-entry, landing, and dJ.sposal and/or refurbishment for 

a future flight. It addresses operations from the flight crew, ground 

operations, and flight operations perspectives. It is expected that 

the depth and breadth of information contained in the Contractor CEV 

CONOPS will increase over time and with subsequent deliveries. 

132 APPLICABLE DOCUMENTS. 

CxP-72000: System Requirements for the Crew Exploration VehJ.cle Element 

13.3 CONTENTS' 

This plan consists of the CEV Contractor plan and recommendations for CEV 

operations includJ.ng Contractor Support to OperatJ.ons. 

Contractor CEV Concept of Operations 

The Contractor CEV CONOPS shall provide gUJ.dance to the CEV System 

developers on how the CEV System is to be used, operated, and maintained 

in a given environment so that their designs, development, integration, 


CEV-O-OOI Page 1 of2





and tests will accommodate CEV goals, missions, and operational 

philosophy. The document shall describe the contractor's concept of the 

'what, where, when, who, why, and how' of CEV System operations from 

dellvery to KSC through disposal of assets. 

The Contractor CEV CONOPS shall address the followlng: 

(a) qescription of operations concept. This includes scenarios from CEV 

spacecraft dellvery to the launch site, through pre-launch processing, 

pre-mission flight design and plannlng, launch, fllght, re-entry, 

landing, and disposal and/or refurbishment for a future flight. 

(b) Fundamental spacecraft capabilities. 

(c) Description of the operational environment. 

(d) Operations constraints due to spacecraft design. Including, but not 

limited to, attitude constraints, consumables (prop and non-prop) , 

thermal constraints, power constraints, processing constraints, and 

facility constraints. 

(e) Roles and Responslbilities of the Flight Crew, Ground Operations, and 

Flight Operations. Include descrlption of automation. 

(f) Nominal, off-nomlnal, and emergency operational scenarios in 

narrative and graphical form. 

(g) Provlde a comparlson of the CXP-700074, Constellation Operations 

Concept Document and the CEV-O-001, CEV Concept of Operations. Also 

provide evidence that the Contractor's specifications and design support 

the concepts and provide the supporting rationale for any deviations. 

(h) Identify and provide supporting rationale for the CEV spacecraft 

limlting factors (e.g systems' performance, consumables, etc.) for each 

DRM and across all DRMs. 

(i) Description of CEV System integration with the Constellation flight 

and ground systems. 

(j) CEV Contractor Support to Operations 

(1) Proposed organlzational infrastructure, personnel and Contractorprovided 

equipment needed to support both the sustaining engineering 

effort and the continued safe operation of the CEV through the completion 

of its life cycle; includes a llst of critical activitles with supporting 

rationale requiring contractor support; and an approach for interactions 

wlth NASA operations; 

(2) Descriptlon of proposed activities to continually improve operational 

processes throughout the CEV System life-cycle to decrease operations 

costs and improve efficlency and how the identlfied improvements wlII be 

incorporated into those operational processes. 

13 4 FORMAT: The CONOPS shall be narrative and delivered in electronic format 

per Section J-2 2.3 2.1. 

13 5 MAINTENANCE: Changes shall be incorporated by complete reissue. 


CEV-O-OOI Page 2 of2





1. 

3 

PROGRAM: CEV 

DATA TYPE' 3 

2. 

4 

5. 

DRDNO.· 

DATE REVISED: 

PAGE. 

6. TITLE: Launch Site Support Requirements Documentation 

CEV-O-003 

May 2009 

1 


This document shall be used to coordinate the identified resources to 

enable the hardware developer and ground operations to complete the 

necessary work on the flight hardware during pre-launch and post-launch 

operations. Support requlrements include shared services and facilities 

provided by KSC, Cape Canaveral Air Force Station (CCAFS), and the 

landing and recovery site 

8 DISTRIBUTION' Per Contracting Ofhcer's letter 



11. REMARKS: 

12. INTERRELATIONSHIP: Parent sow Paragraph (s): 2 7.2. 


13.1 SCOPE: 

Provides the launch site support requlrements needed by the hardware 

developer and ground operations for work to be done at either KSC or 

CCAFS. 


KSC-HB-GP60-3: ASRS Handbook 


The Launch Site Support Requlrements Documentatlon shall identify the 

operations resources (e.g., commodotles, office space, special flight 

hardware access requirements, telephones, fax machines) required by the 

CEV Contractor to process the CEV System at KSC/CCAFS in accordance wlth 

KSC-HB-GP60-3, ASRS Handbook. 

The Launch Slte Support Requirements Documentation shall identify the 

operations resources required by the fllght vehile during ground 

operations and landing and recovery operations. 

13.4 FORMAT. Electronic format per Section J -2 2 3.2.1. 



CEV -0-003 Page I of I






1. 

3. 

PROGRAM: CEV 

DATA TYPE' 2(3 

6. TITLE.CEV Stowage Capabilities and SerVlces Handbook 

2. DRDNO.. CEV-O-006 

4. DATE REVISED' May 2009 

5. PAGE. 1 

The only change to this DRD is in #3: 

From "Data Type 2" 

To Data "Type 2/3" to match the DRD Matrix 


CEV-O-006Page 1 of1





1. 

3 

6. 

7. 

PROGRAM' CEV 2. DRDNO.: CEV-O-OO7 

DATA TYPE: 1 4 DATE REVISED: May 2009 

5. PAGE: 1 

TITLE: Range Safety Requirements Documents 


Provide CEV analyses and data products as required by Range Safety 

Requirements Documents which lnclude the AFSPCMAN 91-710, Range Safety 

User Requirements Manual (Volume 2 and 4) and/or equivalent test range 

standards that satlsfy NPR 8715.5, Range Safety Program. These Range 

Safety Requirements Documents are to be tailored for CEV by the NASA 

Constellation Program. These tailored Range Safety Requirements Documents 

address CEV ascent, earth entry, and landing operational phases. 

8. DISTRIBUTION' Per Contracting Officer's letter 

9. INITIAL SUBMISSION. Per Data Requirements Matrix 

10. SUBMISSION FREQUENCY. Per Data Requirements Matrix 

11. REMARKS: 

The NASA Constellation Program will lead the development of the tailored 

Range Safety Requirements and obtaln Range approval of these tailored 

Range Safety Requirements. 

12 INTERRELATIONSHIP: Parent sow Paragraph (s): 2.7.4 

Referenced from sow Paragraph(s): 2.7.2(a), 3.3 

Referenced from SOW Paragraph(s)' 10.6 8 

13. DATA PREPARATION INFORMATION' 

131 SCOPE: 

(a) For flights conducted at the Eastern Range, analyses and data 

products addressing the tailored AFSPCMAN 91-710 Volume 2 shall be 

provided. These analyses and data products shall address tailored 

versions of AFSPCMAN 91-710, Vol 2 for two different flight 

configurations: 

1. Unmanned CEV/CLV flight test missions (such as the Ares 1-Y mlssion) 

2. Crewed CEV/CLV misslons 

(b) For fllght tests conducted at White Sands Mlsslle Range (WSMR) , 

analyses and data products consistent with Range Commanders Council - 

Range Safety Group - Standard 321-02, Common Risk Criteria for National 

Test Ranges shall be provlded Speclfic analyses to be defined by WSMR 

Flight Safety Office (FSO) Fllght dynamics data products in support of 

fllght safety for WSMR are covered by DRD CEV-D-004. 

(c) For flight tests conducted at other test ranges involving CEV 

elements, analyses and products conslstent with NPR 8715.5, Range Safety 

Program, or those specified by the applicable range safety requirements 

of the host test range shall be provided 



CEV-O-007Page 1 of5




• AFSPCMAN 91-710, volume 2 and 4: Range Safety User Requirements 

Manual (as tailored for CEV) 

• NPR 8715.5: Range Safety Program (as tailored for CEV) 

• Range Commanders Council - Range Safety Group - Standard 321-02: 

Common Risk Criteria for Natlonal Test Ranges 


1. CEV analyses or other data products required to satisfy tailored 

AFSPCMAN 91-710 Volume 2 requirements. Applies to flights conducted at 

the Eastern Range. Examples of anticipated analyses are included in 

Table 13.3-1. 

Table 13.3-1 AFSPCMAN 91-710 Candidate Analyses 

AFSPCMAN 91-710. Vol. Requirement Potential Analysis Support 

2 Requirement number 

1.2.1 No launch vehicle, payload, or 

jettisoned body shall be 

intentionally impacted on land 

Confirmation or analysis 

showing there are no planned 

land touchdowns for pad or 

unless approved by the Chief of ascent abort cases 

Safety and meets the public 

risk criteria in Volume 1, 3.2 of 

this publication. 

Proposed flights shall be 

planned and trajectories shaped 

so that normal impact 

dispersion areas for such items 

do not encompass land. 

1.2.2 If any jettisoned body remains 

buoyant after impact and 

presents a hazard to maritime 

vessels or platforms, a means 

of sinking or recovering the 

body shall be provided. 

Analysis showing that the LAS 

and the ejected panels on the 

SM sink or float. 

1.6.8 Providing hazard assessments 

(the process of identifying 

operation-related hazards, 

assessments 

of those hazards, and 

quantification of risk to 

establish operation constraints.) 

The CEV will have hazardous 

elements that will play into the 

into the overall analysis - 

example: hypergolic 

propellants in the service 

module 

2.2.3.2.5 2.2.3.2.5. General description 

oflaunch vehicle and payload 

in sufficient detail for hazard 

assessment providing the 

following information: 

2.2.3.2.5.1. Type, weight, and 

TNT equivalency of all 

propellants. 

"Payload" items will have to 

be addressed by Orion (prop, 

ordnance, pressure vessels, 

etc.) 


CEV-O-007 Page 2 of5



2.2.3.2.5.2. Description of 

ordnance items. 

2.2.3.2.5.3. Description of toxic 

and radioactive materials. 

2.2.3.2.5.4. Characteristics of 

high pressure vessels, lasers, 

and batteries. 


materials, thickness, and safety 

factors of pressure vessels. 

2.2.3.2.5.6. Thrust and burn 

times of motors and thrusting 

devices. 


guidance and control system. 

2.2.3.2.5.8. Drawings and 

diagrams showing structural 

arrangement and layout of 

significant components in each 

stage or payload. 

2.2.3.2.9 Telemetry measurement listing 

and data word definitions. 

2.2.3.2.13 Estimates of the nominal 

impact point and the threesigma 

drag-corrected 

dispersion area for each 

jettisoned body. 

2.2.3.2.14 Buoyancy analysis of all 

jettisoned bodies that impact 

water; for bodies that remain 

buoyant after impact and 

present a hazard to mantlme 

vessels or platforms, a means 

of sinking or recovering the 

body is required. If recovery is 

desired, a recovery procedure 

shall be identified. 

2.2.3.3 Reliability and Malfunction 

Analysis Data Requirements. 

Reliability of each stage 

and probability of a normal 

mission or failure rate data for 

each stage shall be provided. 



Orion telemetry may be used 

as an independent source of 

vehicle state data, therefore the 

range will require specifics on 

the OFI 

Orion provides the IP for the 

LAS and the SM panels 

LAS and SM panels 

Orion elements could 

conceivably fail in such a way 

as to contribute to CL V failure 


CEV -0-007 Page 3 of 5



2.2.3.4 Propellant Description. If a 

vehicle has the capability of 

exploding as a result of 

self-initiation, FTS activation, 

or ground or water impact or if 

a vehicle uses propellants that 

are toxic in gaseous or vapor 

states due to combustion or 

release to the atmosphere, the 

following data shall be 

provided ... (long list of data) 

2.2.4.2.3 Solid Propellant Data 

Requirements. The following 

data are required for solid 

propellants: (long list of data) 

3.1.2 Trajectory Analysis 

Products: 

3.3 Debris Analysis. These 

requirements apply to the 

following programs: ballistic 

missiles, space vehicles, cruise 

missiles, RPVs, small unguided 

rockets, and probe launch 

vehicles. 

3.3.1. General. The Range 

User shall perform a debris 

analysis that identifies inert, 

explosive, and other hazardous 

vehicle debris resulting from a 

vehicle malfunction and from 

any planned jettison of vehicle 

components for orbital and 

suborbital launches. (more 

specific requirements follow) 

3.4 Debris Risk Analysis These 

requirements apply to the 

following programs: ballistic 

missiles and 

space vehicles, cruise missiles 

and RPV s, and small unguided 



Orion propellants will fall in 

this category - particularly the 

SM. 

LAS components 

Orion elements will require 

inputs for the overall trajectory 

package. Examples include 

IP's and flydowns of the LAS 

and SM panels. Pad and 

ascent abort flyouts of Orion 

elements. Orbit insertion data 

for the CM/SM 

Orion elements that are 

nominally jettisoned (LAS and 

SM panels) are included here. 

For early aborts, the SM itself 

stays with the CL V and 

becomes part of the debris. 

The LAS is also debris 

For a total catastrophic failure 

of the CEV/CLV stack without 

an abort, the entire Orion 

component might be included 

as debris 

For early aborts, the SM itself 

stays with the CL V and 

becomes part of the debris. 

The LAS is also debris 

For a total catastrophic failure 






3.7 

3.8 

rockets and probe launch of the CEV /CL V stack without 

vehicles. (more specific an abort, the entire Orion 

requirements follow) 

component might be included 

as debris 

FTS Determination Analysis. Analysis is needed for the LAS 

These requirements apply to to waive addition of an FTS 

ballistic missiles, space for this component. Successful 

vehicles, cruise missiles, small exclusion of an FTS will mean 

unguided rockets, probe launch that there are no Orion related 

vehicles, and air-launched inputs for Vol 4. 

vehicles. 

3.7.1. General. The threat from Analysis is also required waive 

any payload or stage without an extension of the FTS to the SM 

FTS shall be analyzed to (which has toxic propellants) 

determine the risk associated 

with a malfunctioned vehicle 

whose payload or stage may 

separate prematurely. (more 

specific requirements follow) 

Post-Flight Vehicle 

Orion elements will need to be 

Performance Analysis. These included in the postflight 

requirements apply to all report 

programs identified in this 

volume.. (more specific 

requirements follow) 

2. CEV analyses and other data products requ~red to address Range 

Commanders Council - Range Safety Group - Standard 321-02, Common Risk 

Cr~ter~a for Nat~onal Test Ranges. Specific analyses and other data 

products are defined by the WSMR FSO for all flight test conducted at 

WSMR 

3. CEV analyses and data products requ~red to satisfy NPR 8715.5 (as 

tailored for CEV) or other applicable host range range safety 

requirements. 

13.4 FORMAT: Format shall follow documented processes and procedures in 

AFSPCMAN 91-710 and Range Commanders Council - Range Safety Group - 

Standard 321-02 or other pertinent and applicable Range Safety 

Requirements Documents. Electronic format per Section J-2 2.3.2.1. 

13.5 MAINTENANCE: Changes shall be incorporated by complete re~ssue. 


CEV-O-007 Page 5 of5





1. 

3 

6. 

7 

PROGRAM: CEV 2 DRDNO.· CEV-O-OOS 

DATA TYPE' 2/3* 4 DATE REVISED May 2009 

5. PAGE: 1 

TITLE: Ground Systems Requirements, Plans, Reports and Design Data 

DESCRIPTIONIUSE' 

Volume I: Define CEV requlrements for NASA-provided facilities, facility 

systems, NASA-provided support equipment to support ground operations in 

preparation for flight. 

Volume II: Deliver plans and design data for CEV Contractor-provided 

support equipment end items to support ground operations in preparation 

for flight. 

volume III: Deliver an operations and maintenance plan and requirements 

for Contractor-provided support equipment necessary for CEV ground 

operations 

Volume IV: Dellver a sustainlng engineering plan for Contractor-provided 

support equipment necessary for CEV ground operatlons. 

8. DISTRIBUTION' Per Contractlng Ofhcer's letter 



11. REMARKS: 

* Plan submitted at SDR wll1 be Data Type 2. Reports will be Data Type 3. 

As part of the Quarterly PMR, the ground system project report addresses 

design, acquisition, bUlldlmodification and certification activities of 

CEV Contractor-provided support equipment including schedules, 

procedures, progress to date, expenditures, and cost forecast. 

12. INTERRELATIONSIDP: Parent sow Paragraph(s)' 2.7.2. (a), 2.7.2. (b). 

Related DRD(s): CEV-T-005, CEV-T-029, CEV-T-031, CEV-T-035, CEV-T-04S, 

CEV-T-OS7 


131 SCOPE: 

Provide design and development details of CEV Contractor-provided ground 

systems, the CEV design requirements for Government-provided ground 

systems, and operations and maintenance requirements for Contractorprovided 

GSE. 


NASA-STD-5005B: NASA Standard for Ground Support Equipment (and 


Appllcable, Guidance, and Informatlonal Documents L1St) 


CEV Ground Systems Requirements, Plans, Reports and Design Data shall 

consist of four volumes, each providing the Contractor's requirements, 

plan or approach to a dlfferent aspect of ground systems. 

I. Ground Systems End Item Requirements Document and Report 

II. Ground Systems End Item Implementation Plan and Report 

III. Ground Systems Operatl0ns and Maintenance plan and Requirements 







IV. 

Documentation 

Ground Systems Sustaining Engineering Plan 

The volumes are to include detail at the level commensurate with the 

state of the des~gn at the time of document delivery. 

1. Volume I: Ground Systems End Item Requirements Document and Report 

The document shall def~ne the requirements for NASA provided facilities, 

facility systems, and NASA prov~ded Ground support equipment and 

associated software. This volume shall flowdown the requirements from the 

Ground Support Equipment SRD (DRD CEV-T-031) and the Software 

Requirements Spec~f~cat~on (DRD CEV-T-048) for GSE. 

Requirements for NASA Provided facilities and facility systems shall 

include: 

(a) Narrative descript~on of the purpose and/or function of the facility, 

room, system, and/or equipment item. 

(b) Physical dimensions of the item(s) or area including any required 

l~ft~ng weight, center of gravity, and ce~l~ng hook height 

(c) Number and sk~ll of personnel assigned to a facility or area by 

discipline (e.g., managers, engineers, accountants, secretaries, and 

administrative personnel requ1r1ng office space; technic1ans, mechanics, 

inspectors, requiring break rooms and lab space) . 

(d) Hazard identificat~on (e.g., class~fication of hazards, type of 

propellants, types of vents, types of purges, max~mum fuel/ox~d~zer 

propellant quantities, types of ord~nance, power voltages and 

frequenc~es, no~se levels, RF radiation levels). 

(e) Environmental requirements (e.g., temperature, humidity, particle 

counts, radio frequency shielding, noise attenuation, etc.). 

(f) Power, grounding and lighting, including the use of uninterruptible 

power systems and supplies for ground operations activit~es. 

(g) Plumb~ng/venting and commod~ties for ground operations activities. 

(h) Fire and hazard protection. 

(i) communications, data networking systems. 

(j) Special structural needs (e.g., v~brat~on controls, floor loading, 

etc.) . 

(k) Security (e.g., facilities, facility systems, personnel, hardware, 

software, badging, and access control). 

(1) Material handling requirements (e.g., crane or hoist requirements). 

(m) Env~ronmental pollut~on controls. 

(n) Backup power and other backup or contingency requirements (chilled 

water, hot water, etc.). 

(0) Internal IRD (DRD CEV-T-035) for all interfaces with flight hardware, 

NASA and Contractor-provided ground support equipment, facility systems, 

and facilities. 

(p) References to any special studies and analyses that influenced the 

requirements. 

(q) Cons~deration of human engineering requirements. 

(r) Special operational requ~rements. 

Requirements for NASA Provided ground support equipment and associated 

software shall include: 

(a) Narrative description of the purpose and/or function of the support 

equipment item. 

(b) Phys~cal d~mens~ons of the item(s) including any required lifting 

weight, center of grav~ty, and ceiling hook height. 

(c) Number and sk~ll of personnel assigned to operate the Contractorprovided 

support equipment. 

(d) Hazard identification (e.g., classification of hazards, type of 

propellants, types of vents, types of purges, max~mum fuel/oxidizer 

propellant quantities, types of ordinance, power voltages and 

frequencies, noise levels, RF radiat~on levels). 


CEV-O-008 Page 2 of 4





(e) Environmental requirements (e.g., temperature, humidity, particle 

counts, radio frequency shield1ng, noise attenuation, etc.). 

(f) Power, grounding and lighting, including the use of uninterruptible 

power systems and supplies for ground operations activ~ties. 

(g) Communications, data networking systems. 

(h) Special structural needs (e.g., vibration controls, etc.). 

(i) Material handling requirements. 

(j) Environmental pollution controls. 

(k) Backup power and other backup or cont~ngency requirements. 

(1) Storage requirements. 

(m) Internal IRD (DRD CEV-T-035) for all interfaces with flight hardware 

and support equipment. 

(n) Internal IRD (DRD CEV-T-035) for all ~nterfaces with facilities and 


(0) References to any special studies and analyses that influenced the 

requirements. 

(p) Cons~deration of human engineering requirements. 

(q) Special operational requirements. 

The volume shall identify and include the Contractor's researched 

innovative technologies and methodologies for infusion into ground 

systems to ~mprove safety, efficiency and life cycle costs. 

The quarterly ground system project report addresses requirements 

development act~vities of CEV Contractor-NASA provided ground systems 

including schedules, procedures, progress to date, expenditures, and cost 

forecast. 

2. Volume II: Ground Systems End Item Implementation Plan and Report 

For Contractor-provided support equipment and associated software, the 

implementation plan provides the detailed hardware and software 

implementation approach and preliminary designs. This volume shall be in 

accordance with the ground systems requirements defined in the Volume I 

of this document. 

The follow~ng elements are ~ncluded as appropr~ate: 

(a) Provide descriptions, approaches, and prelim~nary designs with the 

intent to satisfy each of the requirements End Item Specification per DRD 

CEV-O-008, Volume I. 

(b) Environmental assessments, hazards abatements, analyses, and impact 

statements, as required. 

(c) Proposed site locat~ons for activat~on and operational use 

(d) Support equipment projected cost analyses. 

(e) Project design, acqu~s~tion and build/mod~fication approaches, 

concepts, and schedules. 

(f) ICD (DRD CEV-T-029) for all interfaces with flight hardware and 


(g) Proposed initial spares to be purchased for each support equipment 

item. 

(h) plans to maintain and reconf~gure these ground systems to be 

consistent with each configurat~on unique to the hardware/software 

characteristics of the test or flight. 

(i) Plans for the manufacture, assembly, ~nspection, test, calibration, 

certificat~on and acceptance of ground system end items. 

The quarterly ground system project report addresses design, acquisition, 

build/modif~cation and certif~cat~on activities of CEV Contractorprovided 

ground systems including schedules, procedures, progress to 

date, expenditures, and cost forecast. 

The volume shall identify and ~nclude 

the Contractor's researched 







innovative technologies and methodolog~es for infusion into ground 

systems to improve safety, eff~c~ency and life cycle costs. 

3. Volume III: Ground Systems Operations and Maintenance Plan and 


For Contractor-provided support equipment and associated software, this 

volume shall include: 

(a) Plans and requ~rements necessary for safe and effective operation and 

maintenance, including calibration and val~dation intervals, for ground 

systems that support ground and flight operations. 

(b) Plans and requ~rements for requ~red maintenance intervals, techniques 

and implementation. 

(c) Preventive and predictive technologies used, ~ncluding the equipment 

and labs required 

(d) Plans and requ~rements for systems and equipment required to perform 

maintenance 

4. Volume IV: Ground Systems Sustaining Engineering Plan 

For Contractor-provided support equipment and associated software, this 

volume shall include: 

(a) Planning for engineering support for problem resolution including 

Material Review Board (MRB) ~tems. 

(b) The approach for engineering review and analysis of proposed upgrades 

and modifications. 

(c) The approach for maintaince and updates of all system documentation 

(d) The approach for reviewing all FMEA-CIL and hazard analysis 

identified critical items for mitigation or elimination. 




CEV-O-008 Page 4 of 4





1. PROGRAM: CEV 2. DRDNO.: CEV-S-OOl 

3. DATA TYPE. 1 4. DATE REVISED: May 2009 

5. PAGE' 1 

6. TITLE: Safety and Misslon Assurance (S&MA) Plan 

The only change to this DRD is in #13.2 to update the Applicable Document #: 


CxP-70059: constellation Program Integrated Safety, Rellability & Quality 

Assurance (SR&QA) Requirements (and associated Chlldren documents as specified 

in Attachment J-3, Applicable, Guidance, and Informational Documents List). 


1. 

3. 

PROGRAM: CEV 

DATA TYPE: 1 

6. TITLE' Flight System Safety Hazard Analyses 

2 

4. 

5. 

DRDNO .. 

DATE REVISED' 

PAGE: 

CEV-S-003 

04/09/2009 

1 


The Contractor shall perform a safety/hazard analysis per Constellation 

hazard analysis requlrements. The intent of the hazard analysls is to 

reduce safety risk and to establish the acceptable risk of the program 

through the iterative process. Early analysis provides insight to either 

allow hazards to be designed out of the spacecraft or to allow for early 

identification of hazards to aid in early identification of required 

controls for incorporation into the design. The hazard analysis shall 

facilitate and support a hazard control and risk management program for 

the CEV System and Constellation programs and provide information to the 

Government regardlng hazards identlfled through analysis techniques and 

the status of their resolution and level of control. The safety review 

panels will use the hazard reports to assess the design and operation of 

the CEV System as well as to whether or not lt meets the program 

requirements for safety. 

The contractor will develop and document a Verification Tracking L1St to 

document the Contractor's open items from the Phase 3 safety review 

process, includlng those open hazard control verifications that are not 

complete at the time of the phase 3 safety reviews. This 11St will be 

used to track the status, completion, and the method of verification for 

these hazard controls. 


9 INITIAL SUBMISSION. Per Data Requirements Matrix 

10. SUBMISSION FREQUENCY: Per Data Requlrements Matrix 

11 REMARKS: 

During the preliminary analysis and defintion phases, a preliminary 

hazard analysis shall be performed to aid designers in identifying 

potential controls for the identified hazards. In the preliminary and 

final design phases, the hazard analyses shall be updated as the program 

progresses, providing continuity and covering the interrelated areas of 

design, operatl0ns, and spacecraft subsystem integration. Software 







Hazards shall be included in the submission of the Hazard Analysis during 

this contract period, as causes for credible hazards are determined. 

CxP 70038, Constellation Program Hazard Analysis Methodology, defines the 

level of matur~ty required for major design rev~ews and CSERP phase 

levels. 

At FRR the following level of maturity is required: 

(a) System Hazard Analysis (SHA) / Subsystem Hazard Analysis (SSHA) 

complete. 

After the phase 3 Safety Review, new hazard reports that result in 

increased risk shall be submitted at least 30 days prior to a mission'S 

Flight Readiness Review. 

All open Hazard Reports will be forwarded for status tracking. 

For the Verification tracking List: 

(a) Initial submission: 60 days prior to the phase 3 Safety Review of the 

subject hardware. 

(b) Final mission submission: 30 days prior to fl~ght. 

Depending on the control verificat~on status, this del~verable will be 

required for each mission until all hazard control ver~fications are 

complete. 

12. INTERRELATIONSHIP: Parent sow Paragraph(s): 3 2. 

Related DRD(s): CEV-S-OOl, CEV-S-002, CEV-S-005, CEV-O-007, CEv-S-009 

13 DATA PREPARATION INFORMATION· 

13.1 SCOPE· 

System Safety Hazard Analyses identify hazards, evaluate risk, and 

establish verification methods for the CEV Project. hazard analysis will 

be performed in accordance w~th the appropriate sections of Appendix C, 

entitled Hazard Analys~s Types and Techniques, of CxP 70038. 

Hazard analys~s shall consider all catastrophic events, and critical 

events, and the need for highly reliable shut down features (such as, 

h~gh speed laser shut down) should such events occur. 

Hazard reports shall be created or updated as a result of the safety 

review or analysis to show any identified r~sk change. 

The Ver~fication Tracking L~st ~s to be used to track hazard control 

verifications st~ll open after the phase 3 safety review. This list 

contains: 

The number of the hazard control still open 

The description of the action required for closure 

The status of each open item 

The scheduled and actual completion dates 

The Contractor will keep the Verification Tracking List up-to-date. 

At the phase 3 flight safety review meetings, the Contractor will present 

all flight hazards, respectively, their controls, the verification method 

for the controls, and proof that the verification has been completed. 

These are all required for approval of the hazards reports. In some 

cases, the control verificat~on methods may not be complete. In these 

cases, the hazard reports will be held open and tracked in the 

verification tracking list. This allows the hazard reports to be 

presented to the Project/Program managers along with the open control 


CEV -S-003 Page 2 of 5





verification actions. Final, formal approval of the hazard reports is 

complete when the verification tracking list shows that the control 

verificat~on has been successfully completed. 


CxP 70038 - Constellation Program Hazard Methodology 


The contractor shall perform Hazard Analysis to ~dentify hazards and 

ensure their appropriate disposition, tracking and resolution. Hazard 

Analyses shall address the flight hazards that arise in the design, 

development, manufacturing, construction, facilities, operations, and 

disposal associated with the hardware, software, operations and 

environment. 

The analyses shall identify flight hazards, evaluate risk, and establish 

verification methods applicable to design, development, manufacturing and 

assembly, testing, inspect~on, integration, and the operation of flight 

system. Similarly for ground hazards, DRD CEV-S-005 shall address 

contractor-provided portable CEV ground support equipment (GSE) , 

facilities interfaces, env~ronments and ground operat~ons, as well as 

software, in accordance w~th 13.2, Appl~cable Documents. 

Preparation of Hazard Analyses shall beg~n at the concept phase of a 

project to evaluate different concepts and develop appropriate safety 

requirements for early risk management decisions. The safety analysis 

and review process is a phased process as docuemnted in CxP 70038. 

The CEV System Hazard Analysis shall be l~nked to a structured 

methodology such as a fault tree analysis and pertinent FMEA/CIL entries 

to show the interrelationship of hazards to system and subsystem failure 

mechanisms. 

Hazard reports are the means of formally presenting hazards identified in 

the hazard analyses to the CEV Project. The development of flight Hazard 

Reports involves the conveyance of basic informat~on about the hazard and 

the means of satisfying the applicable safety requirements. It shall 

provide sufficient information to allow the PrOJect to analyze the hazard 

reports within the context of other aspects of the ProJect. Each hazard 

report shall describe a single hazardous condition and shall contain the 

data elements specified in CXP-70038. 

The CEV Flight System Safety Hazard Analysis Reports shall contain, as a 

minimum, the data required for the appropriate flight phase review 

according to CXP-70038, Section 5.0, Hazard Reports, in order to 

comprehensively identify and document hazards and related controls. 

Hazard reports shall reference applicable areas from the Failure Mode and 

Effects Analysis/Critical Items List to help identify the primary causes 

of an identified hazard. 

Hazards shall be mitigated according to the following stated order of 

precedence: 

1. Eliminate hazards 

2. Design for minimum hazards 

3. Incorporate safety devices 

4. Provide caution and warning devices 

5. Develop administrative procedures and training 

Hazard Reports shall be prepared as a means of reporting the results of 

formal flight hazard analys~s process. Once prepared, they shall be 

maintained to reflect changes ~n the design, operations, verifications, 

etc. In the event of a signif~cant anomaly during any test or system 


CEV-S-003 Page 3 of5





operation, all related hazard reports shall be re-opened and 

reconsidered. Negative failure history trends in flight hardware or in 

flight-like hardware will result 1n associated hazard reports being 

reopened and reconsidered. 

Hazard reports will be formally reviewed through a series of Phased 

reviews w1th the Safety Review Panel. 

For those controls that cannot be verif1ed as complete by the phase 3 

Safety Review process, the Contractor shall document these open actions 

in a Verif1cation Tracking List. 

The Verification Tracking List will contain the following columns: 

* Log Number 

* Hazard Report Number 

* Cause 

* Description/Hardware (Control) 

* Operation(s) Constrained 

* Independent Verification Requ1red? (Y/N) 

* Scheduled Date 

* Completion Date 

* Method of Closure, Comments/Ver1f1cation Complet10n Notice 

Informal reV1ews with NASA Project S&MA personnel will occur on a 

continuing basis prior to and before phase SRP reviews. 

Spacecraft Survivability Analyses 

Damage Modes and Effects Analysis (DMEA) The contactor shall document 

damage mechanisms and the damage processes with the potential component 

or subsystem failures identified in the FMEA, as well as other possible 

damage-caused failures. The DMEA shall also document secondary hazard or 

cascading damage that can occur from the pr1mary damage mode. The format 

of the DMEA shall start with the immed1ate effects on the function and 

operation of the component, then progressing to the fl1ght and mission 

essential functions 


13.5 MAINTENANCE: Contractor-proposed changes to document shall be 

submitted to NASA for approval. Complete re-1ssue of the document is 

required. 







1. 

3. 

6. 

7. 

PROGRAM: CEV 2. DRDNO.: CEV-S-004 

DATA TYPE: 2/3 4. DATE REVISED: May 2009 

5 PAGE: 1 

TITLE' Mishap Plan and Safety Statistics 


The Contractor shall perform investlgations, generate mishap 

investlgatl0n reports, and provide notlflcation and reportlng of mishaps 

and related information. In addition, the Contractor shall also develop a 

project mishap plan that is consistent with the CEV Project's mishap 

plan. 

8. DISTRIBUTION: Mishap and close call reports will be recorded in the NASA 

IRIS/EX3 database or by submittal of NASA form 1627 and distributed to 

the CEV Project and Center Safety and Missl0n Assurance Office. 



11. REMARKS: 

Plan is Type 2 and Reports are Type 3. 

The Contractor shall perform mishap investigatlons, generate mishap 

reports and provide monthly status reports documenting monthly mishaps 

and safety statlstics starting wlth contract approval. The objective of 

mishap and close call lnvestigations is to lmprove safety by identifying 

what happened, where it happened, when it happened, why it happened, and 

what should be done to prevent recurrence and reduce the number and 

severity of mishaps. These lnvestigations shall be independent, unbiased, 

and non-punitive. These investigations shall be performed by trained 

investigators. The Contractor shall also support all NASA mishap and 

close call investigations. All mishap and close call reports are 

consldered the property of NASA. 

The Contractor shall submit reports for all of the following: 

(a) Notification of mishaps and closes calls. 

(b) Reporting of mishaps and close calls in EX3 (NASA's on-line reporting 

system)or on NASA Form 1627. 

(c) Mishap reports, wlthln 75 days of the mlshap or close call. 

Monthly updates of the investigation status in IRIS/EX3 or by a revised 

Form 1627 or by letter to NASA JSC SR&QA. 

- Monthly updates of the corrective action plan status in IRIS/EX3 EX3 

or by a revised Form 1627 or by letter to NASA JSC SR&QA. 

(d) Monthly status reports documenting mishap/close call and safety 

statistics. 

The monthly statistics report format shall be NASA JSC Form 288. 

(a) QUlck Incident Report for Safety (into the NASA IRIS/EX3 Data 

Management System or by letter to NASA JSC SR&QA or using JSC FORM 288) 

(b) Quick Incident Report for Injury & Illness (into the NASA IRIS/EX3 

Data Management System or by letter to NASA JSC SR&QA or using JSC FORM 

288) 

~Tracklng Report (into the NASA IRIS/EX3 Data Management System or by 

letter to NASA JSC SR&QA or uSlng JSC FORM 288) 







12. INTERRELATIONSHIP. Parent sow Paragraph(s): 3.3. 

Related DRD(s): CEV-S-001 

13. DATA PREPARATION INFORMATION 

131 SCOPE: 

The Contractor's mishap plan shall include, but not be limited to, 

special procedures for safing, handl~ng, or containing hazardous 

chemicals present in proJect hardware; ~nclude special procedures for 

emergency response personnel; include procedures to impound records, 

data, equipment, facilities; list nat~onal, state, and local 

organizations which are likely to take part in debris collection 

(including ~dentifying the roles and responsibilities of each 

organization), and document how off-site debris will be collected, 

transported and stored. 

The scope of the contractor team ~s the major project Orion contractors, 

defined as Lockheed Mart~n Space Systems, Lockheed Martin Michoud 

Operations, Lockheed Martin M~ssion Systems, Aerojet, Hamilton 

Sundstrand, Honeywell, Orbital Sciences Corporation, and USA work on 

Project Orion. 

The Contractor shall report unplanned events that result in the 

follow~ng: 

(a) Injury to non-NASA personnel caused by NASA ops 

(b) Damage to public or pr~vate property caused by NASA ops or NASA 

funded development or research projects 

(c) Occupat~onal injury or ~llness to NASA personnel 

(d) NASA mission failure 

(e) Damage or destruct~on of NASA property 

Test failures involving damage to equipment or property as a result of 

testing are not considered mishaps if: 

(a) The test article ~s not flight hardware 

(b) The testing ~s part of an authorized 

research/development/qualificat~on/certification program 

(c) Damage is lim~ted to the test article and test ~nstrumentation 

(d) Risk of damage to the test article was accepted explicitly by 

program/project management 

(e) The test team performs a test failure analysis and generates a 

techn~cal report instead of treating ~t as a mishap 

Close Calls: An occurrence or condition of employee concern in which 

there is no injury or only minor ~nJury requiring first aid and no 

significant equipment/property damage, but which possesses a potential to 

cause a mishap. 

The severity of the personnel inJury and the direct cost of the mishap 

shall determine the classif~cation level of the mishap or close call per 

the information below: 

1. Type A Mishap 

Property Damage: 

Total direct cost of mission failure and property damage is 

$1,000,000 or more OR 

Crewed aircraft hull loss has occurred, OR 

Occurrence of an unexpected aircraft departure from controlled flight 

(except high performance Jet/test aircraft such as F-15, F-16, F/A-18, 

T-38, and T-34, when engaged in flight test activities). 

Injury: 

Occupational injury and/or illness that resulted in: 







A fatality OR 

A permanent total disability OR 

The hospitalization for inpatient care of 3 or more people within 30 

workdays of the mishap. 

2. Type B Mishap 


Total direct cost of miss10n failure and property damage of at least 

$250,000 but less than $1,000,000. 

Injury: 

Occupational injury and/or illness has resulted in permanent partial 

Disability OR 

The hospitalization for inpatient care of 1-2 people within 30 

workdays of the mishap. 

3. Type C Mishap 


Total direct cost of mission fa1lure and property damage of at least 

$25,000 but less than $250,000. 

Injury: 

Nonfatal occupational 1njury or illness that caused any workdays away 

from work, restricted duty, or transfer to another job beyond the 

workday or shift on wh1ch it occurred. 

4. Type D Mishap 


Total direct cost of mission failure and property damage of at least 

$1,000 but less than $25,000. 

Injury: 

Any nonfatal OSHA recordable occupational injury and/or illness that 

does not meet the def1nition of a Type C mishap. 

5. Close Call 


Total direct cost of mission failure and property damage is less than 

$1,000 OR 

An occurrence or cond1tion of employee concern in which there is no 

property damage but possesses the potential to cause a mishap. 

Injury: 

Minor injury requiring first aid which possesses the potential to cause 

a mishap OR 

An occurrence or condition with no injury but possesses the potential 

to cause a mishap. 

13.2 APPLICABLE DOCUMENTS 


The Contractor's mishap plan shall include, but not be limited to, 

plans and special procedures for safing, handl1ng, or containing 

hazardous chemicals present in project hardware; 

include procedures for not1fication of, reporting to, investigating, and 

recording to NASA; 

include the procedures to appoint contractor personnel to investigative 

boards; include spec1al procedures for emergency response personnel; 







include procedures to impound records, data, equipment, facilities; list 

national, state, and local organizations which are likely to take part in 

debris collection (including identifYlng the roles and responsibillties 

of each organization; 

document how off-site debris will be collected, transported and stored; 

and identlfy personnel who shall perform and control the lrnpounding 

process. 

For mishap notification, notlfy (by phone) the NASA Center Safety Office 

and Project wlthin one hour of the occurrence of the following: 

(a) Type A mishaps 

(b) Type B mishaps 

(c) High visibillty mishaps 

(d) High visibillty close calls 

(e) Non-Occupational Fatality, Permanent or Partial Disability or Lost 

Tlme Injury that Occurred on a NASA Center or Facllity 

Information to include, location of the incldent, time of incident, 

number of fatalities, number of hospitalized employees, type of injury, 

type of damage, contact person, contact person's phone number, br1ef 

description of the mishap. 

Within 24 hours, for all Mlshaps and close calls submit an electronic 

report with. 

(a) Author of the report 

(b) Author's phone number and mail code 

(c) Location of author 

(d) Date report submitted 

(e) Time reported submitted 

(f) Incident date, 

(g) incident time 

(h) incident general location 

(i) exact location 

(j) responsible organization 

(k) organlzation's point of contact 

(1) point of contacts phone number and mail code 

(m) missl0n affected 

(n) program impact (if known) 

(0) number and type of injuries or fatalities 

(p) type of damage to equipment 

(q) flight hardware 

(r) flight software 

(s) facilities 

(t) estlmate direct cost of damage 

(u) brief description of mishap or close call 

The contractor shall email this lnformation to the Center Safety Office 

and enter this information into the IRIS/EX3 Data Management System 

listed in 13.4 to comply with notification, and reporting requirements 

The monthly statlstics report content shall include the total number of 

hours worked by the ProJect Orion major contractors dur1ng the previous 

month. 

13 4 FORMAT: The following formats shall be submitted electronically: 

(a) Q,lie], IHeiEieHt R8j!lsrt fsr Safet} 

(e) Q"ie], IHeiEieHt R8j!lsrt fsr 1H301r} & IIIHess 

(e) 'f'raelEil'lg R8j!lsrt 

(d) Mishap Report (Microsoft Word compatible lnto the NASA IRIS/EX3 Data 

Management System and sent via email to the Center Safety Office) 

(e) Correctlve Action Plan 

(f) Lessons Learned 


CEV-S-004 Page 4 of 5





(g) Mlshap completion Statement indicatlng that the investigation was 

performed, the corrective action plan was developed, implemented and 

closed, and the lessons learned were entered into the NASA Lessons 

Learned Information Systems 


submitted to NASA for approval. Complete re-lssue of the document is 

required. 







1. 

3 

PROGRAM: CEV 

DATA TYPE' 1 

2. 

4. 

5 

6. TITLE: Ground System Safety Hazard Analysls 

DRDNO.: 

DATE REVISED: 

PAGE: 

CEV-S-005 

May 2009 

1 

7 DESCRIPTIONIUSE: 

The Contractor shall provide ground safety data packages, including 

hazard analyses, applicable to the CEV Spacecraft, CEV Flight Test 

Artlcle(FTA) & associated CEV Ground Support Equlpment (GSE) designs and 

operations (from arrival at the launch site through liftoff and during 

post-landing activities) per Constellation and launch site documentation 

requirements. The ground safety review panel will review the ground 

safety data package to address the safety impacts and risks that CEV/CEV 

FTA and CEV GSE deslgns and operations will have on the launch site's 

processing facilities, personnel and other spacecraft. This document will 

be used by the CEV Project to qualify the CEV/CEV FTA System and 

associated CEV GSE for safety certificatl0n to the Processing/Launch Site 

Safety Offlce. 

8. DISTRIBUTION' Per Contracting Officer's letter 



11. REMARKS. 

The ground safety data package documentation requirements and the ground 

phase safety reviews will be based upon the hazardous nature and degree 

of complexity of the CEV, CEV FTA and CEV GSE designs and operatlons. 

When flight payload safety reviews and ground payload reVlews are 

separate reVlews, an assessment shall be made by the CEV Project to 

assure hazards identlfled in each package are assessed for applicability 

to the other; e.g., if a ground safety hazard report on inadvertent 

thruster firing does not eXlst, the flight safety hazard report must be 

referenced in the ground safety package and it must contain a discussion 

of the applicability of the flight safety controls to ground safety. 

This document wll1 apply to: 

a. All organizatl0ns processing the CEV Spacecraft or CEV FTAs at the 

ER/KSC, the White Sands Missile Range(WSMR) or other test ranges. This 

includes all contractor organizations. 

b. Contractors in direct support of the above organizations. 

c. Other organizations providing direct personnel and equipment interface 

to CEV Spacecraft or CEV GSE support. 

d. Any of the above organizations required to support CEV Spacecraft post 

landing operations at any landing site. 

The 'CEV Contractor' refers to the Contractor unless otherw1se stated. 

12 INTERRELATIONSHIP Parent SOW Paragraph(s): 3.2; 

Related DRDs: DRD-O-007, DRD CEV-S-003 






13.1 SCOPE. 



ThlS document supports the ground safety reVlew and approval process 

required by the launch site and CxP 70038. Documentation submitted shall 

be consistent wlth the CEV ProJect phase level under review and shall be 

approved prior to completion of the phase III Ground Safety Review. 


CxP 70038, Constellation Program Hazard Analysis Methodology 

13 3 CONTENTS' 

The document shall contain the Contractor's procedures for: 

1) phase Safety Reviews 

2) Ground Safety Documentation 

For Phase Safety Reviews 

The CEV Contractor shall document ltS plan for support of the ground 

phase safety review process per Constellation document Program Hazard 

Analysis Methodology, CxP 70038. This procedure provides for an early 

safety interface to be established between the CEV Contractor and the 

processing/Launch site. 

For Ground Safety Documentation 

General: 

Documentation shall be provided that describes the Contractor's procedure 

for ldentifying, documenting and sUbmitting the data required by the 

Constellation Program and the launch site for the ground phase safety 

reVlew process. plans and procedures that address the ground safety 

analysis and review process, safe conduct of operations and mishap 

reporting shall be submitted to the PSSO / LSSO for review and comment. 

Documentation shall include. 

For Phase Safety Review Documentatl0n: 

The CEV Contractor shall prepare ground safety data packages packages in 

accordance with CxP 70038. These reviews (see Data Submission Matrix) 

align with maJor program mllestones and provlde for the delivery and 

presentation of safety documentatlon required by the Processing/Launch 

site prior to delivery of the CEV Spacecraft/FTA and GSE to that site. 

The documentation shall include verification to the PSSO/LSSO that 

hazards that are not ellminated by deslgn exist for valid technical 

reasons and are not for operational convenlence or cost savings. These 

hazards can cause operational restrictions that could limit personnel 

numbers, require a specific sequence of operations, or limit operations 

to specific facilities. As a result of this information presented at the 

ground safety reV1ew, the PSSO/LSSO will communicate, 1n writing, to the 

CEV Contractor, the rat10nale for any restr1ctions imposed on the CEV 

Spacecraft or CEV GSE design as early as possible. The PSSO/LSSO will 

also assist the CEV Project and Contractor in determining the course of 

actl0n which can best serve operational efficiency. 

This document shall include. 

1. Block diagrams, schematics, and descriptions of safety critical 

subsystems. This includes tables of deslgn and operating parameters for 

such items such as liftlng equipment, pressure systems, ordnance, and 

batteries. 

2. Launch site processing plan including timelines for handling, storage, 

assembly, servicing, and checkout operations. 


CEV-S-005 Page 2 00





3. List of Technical Operating Procedures (TOP's), a synopsis of each 

procedure, and their preliminary classifications, i.e., hazardous or non 

hazardous. TOP interrelationships to hazard controls shall be 1ndicated 

in the hazard reports. This list1ng may be provided as an appendix to 

the ground safety data package. 

4. Documentat10n certifying compliance with 10nizing radiation control 

requirements. 

5. Failure/accident summary reports. 

6. Copies of all noncompliance (waiver and deviation) reports. 

7. Ordinance storage and handling data requirements. 

8. A list of all hazardous mater1als and physical agents. Material Safety 

Data sheets (MSDS's) shall be provided to the PSSO/LSSO for all material 

and agents brought by the CEV contractor. 

9. A list of all plastic films, quantity, and location of use. 

10. List of the CEV Spacecraft T-O umb111cal functions, 1f any. 

11. Identification of cr1tical software commands and verification of how 

they are managed. These critical software commands include commands 

which, if executed or executed out of sequence, would create a hazardous 

condition or would remove a safety inhibit. 

12. Potent1al hazards result1ng from the human 1nterface shall be 

addressed by the CEV contractor during the phase review process. 

13. Mechan1cal or electromechanical devices that must be failure tolerant 

shall be identified in the operational hazards analysis with the 

requirement for caution and warning notations incorporated in the TOP's 

For Processing site & Launch Site Documentation: 

The Contractor shall provide Fac1lity Safety Plans and Emergency 

Procedure Documents (EPD's) for all CEV facility/area users. These 

Facility Safety Plans and Emergency Procedure Documents (EPD's) developed 

for the processing/Launch sites, contain specific requirements for 

hazardous processing fac1lities/areas and w111 be mandatory for all 

facil1ty/area users. The plans may be submitted as appendices to the 

ground safety data package or under separate cover for review and 

approval by the CEV Project and the ground safety review panel. 

For CEV Contractor Processing/Launch Site Safety plan: 

The CEV Contractor shall provide a Processing/Launch Site Safety Plan 

that demonstrates the means by which the Contractor manages, conducts and 

1nterfaces safety w1thin its organization and how it applies the 

Processing/Launch s1te safety requirements. The specifics of the plan 

contents shall be identified by the CEV Contractor early in the phase 

safety review process. The plan may be submitted as an appendix to the 

ground safety data package or under separate cover for review and 

approval by the CEV Project and the ground safety review panel. 


13.5 MAINTENANCE: Changes shall be incorporated by complete re1ssue. 







1. PROGRAM: CEV 

2. DRDNO.. CEV-S-009 

3 DATA TYPE. 1 

4. DATE REVISED' May 2009 

5. PAGE: 1 

6. TITLE: Failure Modes Effects Analysis & Critical Items List (FMEA!CIL) 


The Failure Modes Effects Analysis and Critical Items List is a design 

and operations tool and will be used to a1d design engineering, 

operations, and manufacturing of the CEV. The Contractor shall perform 

Fa1lure Modes and Effects Analysis (FMEA) and the Critical Items List in 

accordance with the Constellation Program requ1rements for preparation of 

hardware fa1lure modes and effects analysis and cr1tical items list 

(FMEA/CIL) - This analys1s shall be performed - to identify possible 

failure modes and effects including all hardware failures and integrated 

system failure modes and effects. Software failures and effects analysis 

shall be performed according to the govern1ng Constellation Requirements 

for Software product Assurance 

1) Additional design action 

2) Safety analysis 

3) Test plann1ng 

4) Mission Planning 

5) Preparation of mandatory inspection points 

6) Fault detection and 1solation 

7) Maintainability Design Character1stics 

8) Maintenance Planning 

9) Logist1cs Planning. 

The purpose of the Cr1t1cal Items List (CIL) is to 1dentify those items 

or hardware that do not meet failure tolerance requ1rements (CXP-10001, 

Systems Requirements for the Crew Exploration Vehicle Element (CEV SRD) , 

para's 3.3.7.1, 3.3.7.2, 3.3.7.3, 3 3.7.4) and, in addition, those items 

that do not pass the redundancy screens (screening to determine if an 

item's redundant path can be functionally verified or 1f a redundant path 

failure can be detected prior to use, or if all redundant paths can be 

lost as a result of single credible common failure cause) that require 

special attention when establishing hardware spec1f1cations and 

qualification requirements. 

The CIL shall consist of all failure modes with Criticalities (relat1ve 

measure of the consequence of the failure,) identified in the FMEA in 

accordance with the Constellation criticality cr1teria (see CXP-02019, 

Program Requirements for Preparat10n of Hardware FMEA/CIL, Table 4.6-1: 

Crit1cality Categories). The FMEA and CIL analysis shall cover Common 

Cause Failure (CCF) Analysis at the subsystems (i.e., Environmental 

Control and Life Support Subsystem, Guidance, Navigation, and Control 

Subsystem, Reaction Control Subsystem, etc.) level and be proof that the 

design is free from CCF Each CIL item, via its documented 'retention 

rationale' (proposed rationale for Project acceptance of the Risk, see 

CXP-02019, Program Requirements for Preparation of Hardware FMEA/CIL, 

section 5 2 ), drives the development and implementation of inspection, 

process control, and test and verification requirements for the critical 

items. The CIL item also influences operations planning (including 

mission planning, procedure development, and logist1cal and maintenance 

support requirements), and includes failure h1story. 

8. DISTRIBUTION: As determined by the Contracting Ofhcer 









11. REMARKS: 

At System Definition Review the following level of matur~ty is required: 

(a) The contractor shall develop and document preliminary System level 

Reliability Block Diagrams (RBDs) (Logic Diagrams which graphically 

depict items, configured in s~ngle or redundant paths, that must work for 

the def~ned function to be completed successfully and to assess the 

System fa~lure tolerance) of the CEV System, its modules, the subsystems, 

and their functions, major mission phases or modes identified. 

(b) Master logic diagrams, functional failure modes defined, preliminary 

high level (System and Spacecraft level) failure effects identified. 

At Preliminary Design Review the follow~ng level of maturity is required: 

(a) Detailed Subsystem and component level REDs matching the detail of 

equipment lists from the CEV System Contractor. 

(b) Failure mode effects will describe the out-of-spec outputs (including 

higher level spacecraft and System effects) required to support failure 

propagation assessments. 

(c) Lowest level effects (subsystem and component level) accurately 

propagated to the high level (System and spacecraft) effects. 

(d) Failure causes sufficiently developed to a level commensurate with 

the design. 

(e) Failure effects developed to a level consistent with design detail, 

for both hardware and software. 

Note: To enable more timely evaluation to the design effort, informal 

FMEA and CIL submittals to Technical Interchange Meetings (TIMs) with 

NASA subsystem eng~neers will be provided per~odically prior to the PDRs, 

outside of the PDR rev~ew process. 

At Critical Design Rev~ew (CDR) the following level of maturity is 

required: 

(a) System and Component Level FMEA and CIL complete 

(b) Detailed subsystem and component level REDs complete. 

(c) FMEA and CIL completed analysis to the deepest level of indenture 

(component level) for the analysis. 

(d) Failure mode effects complete to the lowest level (component level). 

(e) Failure Causes sufficiently developed to a level commensurate with 

the design. 

Following CDR, the FMEA and CIL results shall be of sufficient quality, 

level of detail and timeliness to be used to develop test plans and to 

troubleshoot test failures. The FMEA database shall be maintained as 

needed to document des~gn and operational changes, to document new 

content as well as to capture belatedly recognized failure modes and 

effects. 

12. INTERRELATIONSmp: Parent sow Paragraph (s): 3.4. 

Related DRD(s): CEV-S-001, CEV-S-002, CEV-S-003, CEV-S-010, CEV-S-011 


13.1 SCOPE' 

The FMEA is an analys~s for the CEV System to determine possible modes of 

failure and their effects on the crew, spacecraft and mission success, 

w~th the provisions for ~dentifying each failure mode by its Criticality 

category number. A FMEA shall be prepared for each CEV System and 

subsystem to the component level (described ~n 13.3). 

The CIL is a l~st of hardware identif~ed in the FMEA categorized as being 

'Critical', i.e., those ~tems whose failure could result in a loss of 

life, the vehicle, and the mission. The Critical Items List shall 

consist of those failure modes identified by the FMEA that are 

Criticality 1, Cr~ticality 2, all Crit~cality 1R items where the next 







failure of any redundant item could cause loss of the crew, and all 

Criticality lR and 2R ~tems that fail one or more redundancy screens. 

The FMEA and CIL worksheet documents (object~vely) the 'retention 

rationale' for the design features, test~ng, and inspections, operational 

use, mainta~nability, and includes the fa~lure history of the item to 

help minimize the failure occurrence probability. 

CIL worksheets shall be documented as open (not approved by the NASA 

Project) until the request for CEV Project acceptance has been approved. 

Maintenance of the CEV FMEA and CIL w~ll be limited to changes of the 

System, subsystem, or components as required! to a~d in design, 

operation, and manufacturing decisions, to document new content as well 

as to capture belatedly recognized failure modes and effects. 


CxP 70038, Constellation Program Hazard Analysis Methodology 


a A brief System and subsystem overview shall be provided along with a 

subsystem level Reliab~lity Block Diagram (RBD) to reflect the 

configuration and deta~ls of the systems. 

b. FMEA worksheets shall be prepared at the lowest level (component 

level) required to support potential uses (redesign, testing, failure 

report~ng or corrective act~on, preparation of mandatory inspection 

points), in accordance with Document CXP-02019, Constellation Program 

Requirements for Preparation of Hardware FMEA/CIL. 

c. FMEA and CIL worksheets shall be prepared as appropriate (with regard 

to Cr~ticality) with 'retention rationale' that contains data that 

supports the premise that the risk presented by inclusion of the item in 

the assembly/subsystem/spacecraft/System/CEV has been minimized by proper 

design controls, inspections, tests, critical processes and maintenance 

controls, and that no adverse failure history exists. The rationale shall 

also contain data, which describes operational constraints caused by 

occurrence of the failure, and describe the measures taken to ensure that 

the function is restorable. The contractor shall also prepare as part the 

verification activity, an entry on the worksheet, that lists the methods 

for verifying CIL 'retention rationale' and hazards control activity. 

Ground rules shall be consistent with sections 4 and 5 of CXP-02019, 

Constellation Program Requirements for Preparat~on of Hardware FMEA/CIL. 

d The fidelity of the FMEA and CIL shall reflect the latest hardware 

and software designs and identify risks for all flight software and 

hardware and its interactions during various phases of the program per 

the scope as listed in par. 13.1. If the contractor determines that 

future FMEA and CIL submissions should separate hardware and software, 

th~s can be accompl~shed by separate chapters within the analysis, 

however, there must be a final system FMEA and CIL that ties the hardware 

and software interactions together as often the two are used in concert 

to obtain adequate fault and failure tolerance. 

e. A 'single point' failure summary shall be provided as a section of the 

CIL. An independent redundant items failure analysis shall be done for 

critical Items to evaluate the potential effects for latent defects and 

other process ~ssues including potential human errors. The FMEA and CIL 

analysis shall cover Common Cause Failure (CCF) Analysis at the Systems 

and subsystems level and CCF shall be designed out to an acceptable risk 

level (as approved by the NASA Project) and residual risks shall be 

documented and controlled. 

f. The FMEA and CIL analys~s shall cover Common Cause Failure (CCF) 

Analysis at Systems and subsystems level and CCF shall be designed out to 

an acceptable risk level (as approved by the NASA Project) and residual 

risks shall be documented and controlled. 

13.4 FORMAT: Electronic format per Section J-2 2.3.2 1. 








submitted to NASA for approval. Only changes or updates to the baselined FMEA 

and ClLs shall be resubmltted for NASA approval. 







1. 

3. 

PROGRAM: CEV 

DATA TYPE: 1/4 

2. 

4. 

5 

6. TITLE' Probabilistic Risk Assessment Results 

DRDNO. 

DATE REVISED: 

PAGE: 

CEV-S-010 

May 2009 

1 


To define and document the contractor's data and findings ln implementing 

and performlng a Probabilistlc Risk Assessment (PRA) per the 

Constellation PRA Methodology Document 

8 DISTRIBUTION' As determined by the Contracting Officer 

9. INITIAL SUBMISSION Per Data Requirements Matrix 

10 SUBMISSION FREQUENCY: Per Data Requirements Matrix 

11. REMARKS' 

Dellveries of Probabilistic Risk Assessments at design milestones are 

Type 1 documents. 

Preliminary PRAs are due at System Definitlon Review to current design 

level of detail. Event trees, fault trees, model integration & 

quantification, and uncertainty analysis shall be under development 

Included wlth the PRAs, ground rules, mission success criteria, end 

states shall be ready to basellne. 

At Preliminary Design Review (PDR) the following level of maturity is 

required: 

(a) Changes to Event trees, fault trees, model integration & 

quantification, and uncertainty analysls from System Definition Review 

statused. 

(b) Risk scenarlO development complete. 

(c) Event sequence Diagram complete. 

(d) Master Logic diagrams complete. 

(e) Initiating events updated to PDR level of detail using available 

hazard analysis. 

At Crltlcal Design ReVlew (CDR) the following level of maturity is 

requlred: 

(a) Initiating events updated to CDR level of detail using available 

hazard analysis. 

(b) Event trees, fault trees, model integration & quantification, and 

uncertainty analysls development continued. 

(c) Changes to previous submittals addressed. 

Following CDR, updates shall lnclude the following: 

(a) Analyses complete and should be high level of detall and maturity 

with accurate test-supported input data. 

(b) Update with changes to the deslgn. 

(c) Changes to preVl0US submittals addressed. 

Type 4 Reports shall be dellvered every 6 months after the PDR delivery. 

The Type 4 Reports are "interim" status deliveries, which shall contain 

the following: 

• List of model changes from previous delivery (software, human 

rellability, common cause methodology,uncertainty, etc.) 

List of upcoming PRA components for the next delivery 

(software, human reliability, common cause methodology, 

uncertainty, etc.) 

• Updates to the model from the previous delivery. 


CEV-S-OlOPage 1 of4



• Identification of data and assumption changes. 

• Updated schematics and design information 



The following documents may be used as guidance documents: 

(a) Probabilistic Risk Assessment Procedures Guide for NASA Managers and 

Practitioners, (August 2002), Chapters 4-14 

(b) Fault Tree Handbook with Aerospace Applications (August 2002), NASA 

HQ OSMA, Chapters 1-9 

12. INTERRELATIONSIDP: Parent SOW Paragraph (s). 3.4. 

Referenced from SOW Paragraph(s): 1.4. 

Related DRD(s)' CEV-S-001, CEV-S-002, CEV-S-009, CEV-S-Oll 


13.1 SCOPE. 

The Contractor shall develop the CEV PRA per CxP 70017, Constellation PRA 

Methodology Document and the Probabilistic R1Sk Assessment Procedures 

Guide for NASA Managers and Practitioners, (August 2002), chapters 4-14. 

The CEV probabilistlc Risk Assessment Results shall include the models, 

basis for the models, analysis results, detalled descriptions of the 

analysis, justifications for assumptions, data, and basis for the data. 

The models, analysis, and data used will comply with the requirements in 

the Constellatl0n PRA plan. 

(a) Probabilistic Risk Assessments (PRAs) shall be used to model 

potential accident scenarlOS during each Design Reference Mission to 

determine the rellabllity and risk of each CEV deslgn concept. 

(b) Success or failure of a CEV mission shall be directly related to 'end 

states' ln the PRA analyses. Additional end states can be included in 

the analysis as desired by the program. 

(c) Perform comprehensive function analysis to identify all system 

functions necessary for the system to achieve its operational objectlves 

for the Des1gn Reference Miss10ns in the specified miss10n environments. 

Function analysis should include functions that will be performed by 

hardware, software, and people. 

(d) Develop Function Flow Diagrams to illustrate flow of information and 

processing requlred. The functlonal flow diagrams shall illustrate all 

interrelationships between function interfaces. The interrelationships 

shall be evaluated to determine if an lnterface failure results in a PRA 

end state. 

(e) PRA models shall be graphically lllustrated ln top-level fault trees 

called Master Logic Dlagrams (MLD) , ln which the top level blocks are the 

end states (or FOM) , the intermediate blocks represent the chain of 

events necessary to produce the end states, and the bottom blocks are the 

inltiating events. 

(f) The CEV PRA shall identlfy important lnitiating events that can 

trigger failures/events for each series of end states. Initiating events 

shall include hardware fallures, software failures, human errors, and 

naturally occurring phenomena. Internal lnltiators as well as external 

initiators (e.g., MMOD) shall be considered. 

(g) The CEV PRA shall lnclude human reliability analysis (HRA) for both 

pre-inltlating events and post-initlating events, including those modeled 

ln support system initiating event fault tress. The HRA should comply, at 

a minimum, w1th the high level requirements as outlined 1n ASME RA-SlQQl: 

Standard for Probabillstic Risk Assessment for Nuclear Power Plant 

Applications or an equivalent document. 

(h) The CEV PRA shall include quantitatlve evaluations of the probability 

that the initiating events will lead to end states corresponding to CEV 

success or failure. 

(i) The CEV PRA analyses shall lncorporate parametric common-cause 

failure techniques in the system failure analysis models and failure 

probability evaluations. 

(j) The CEV PRA analyses shall include an evaluation and description of 


CEV -S-01 0 Page 2 of 4





quantitative uncertainties. 

(k) To the extent feasible, CEV Probabilistic Risk Assessments shall 

include analys~s of software system safety, rel~ability and qual~ty. 

(1) The processes and techniques provided in the PRA Guidebook for NASA 

Managers and Practioners and further defined by CxP 70017 Constellation 

PRA Methodology Document shall be used for conducting PRAs. 

(m) Uncertainty analysis shall be performed on the CEV Project PRA to 

provide the decision maker with a full appreciation of the overall degree 

of uncerta~nty about the PRA results and an understanding of which 

sources of uncertainty are critical to the results that guide decisions. 

(n) Results and Insight from the CEV PRA shall be utilized to update the 

design, operating, and implementation plans. 

(0) All mission scenarios leading to crew fatality or permanent 

disability shall have a quantitative r~sk assessment developed. 

(p) The CEV risk assessment model shall be maintained throughout the 

system life cycle. 


CxP 70017 Constellation PRA Methodology Document 


1. The CEV Probabilistic Risk Assessment Results shall use the applicable 

document processes and techniques in CxP 70017 Constellation PRA 

Methodology Document to provide the following: 

a. Groundrules and assumptions (inputs). 

b. ModelS/Data sources. 

c. Miss~ons, phases Analyzed. 

d Values calculated. 

e. Model/Data Sources. 

f. Analys~s results. 

g. Risk estimates. 

h. Risk breakdown with relative contr~butions. 

i. Sensitiv~ty analyses. 

j. Validation or benchmark of methodology and code. 

2. The CEV PRA shall be performed per the processes and techniques 

provided in the CxP 70017 Constellation PRA Methodology Document andPRA 

Procedures Guide for NASA Managers and Practioners, chapters 4-14. 

3.The Contractor shall ident~fy the major contributors to r~sk as 

determined by the CEV PRA. 

4. The CEV PRA shall be balanced, comprehensive and tailored. 

5. The Contractor shall perform uncertainty analysis on their PRA as part 

of their reporting of the PRA results and identify those sources which 

are critical to Program/Project risk decisions. 

6. The CEV PRA shall identify and evaluate potential scenarios leading to 

undesired consequences. 

7. The CEV PRA shall evaluate the failure (type and probability) of each 

event ~n the potential scenarios lead~ng to undesired consequences (see 

4. ) 

8. The CEV PRA shall quantify the scenarios establ~shed for the CEV by 

the CEV Project PRA plan. 

9. The Contractor shall ~nclude the degree of uncerta~nty about the CEV 

PRA results and an understanding of which sources of uncertainty are 

critical. 

10. The Contractor shall supply all data analyses in support of the 





quantification of the CEV PRA. 



11. The Contractor shall use term~nology that is cons~stent with that 

used by the CEV Project ~n the CEV PRA. 

13 4 FORMAT: Electronic format per Sect~on J -2 2.3.2.1. 



required. 


CEV -S-O 10 Page 4 of 4





l. 

3. 

PROGRAM: CEV 

2 

DATA TYPE. 1/2* (See Data Requ~rements 4. 

Matrix) 

5 

DRDNO.: 

DATE REVISED. 

PAGE: 

6. TITLE: Government-Industry Data Exchange Program and NASA 

Advisor~es/ALERTS 

CEV-S-012 

May 2009 

1 

7. DESCRIPTION/USE. 

To provide a controlled method for CEV Project and Contractor ALERT 

initiation, investigat~on, resolution, and response. The types of data 

include: 

(a) Contractor and subtier implementation procedures. 

(b) Preperation and submittal of GIDEP documents. 

(c) Coordinat~on 

of potential NASA Advisories (NASA unique items) with 

NASA (JSC NASA Advisory Coordinator) . 

(d) Task managemnt, control, and tracking status. 

(e) Cost data on special problems (involving crim~nal 

8. DISTRIBUTION: As determined by the Contract~ng Officer 


investigations). 

10. SUBMISSION FREQUENCY: Per Data Requirements Matrix and as fOllows: 

a) Contractor and subtier implementation procedures (60 days after 

contract award) 

b) Release of GIDEP documents (in compliance with S0300-BT-PRO-010) 

c) Release of NASA Advisories (in coordination with the NASA-JSC Advisory 

Coordinator per NASA policy) 

d) GIDEP/NASA Advisory problem data assessment (30 days after receipt of 

GIDEP/NASA Advisory problem data) 

e) Cost data on special problems (involving criminal investigations) 

11 REMARKS' 

Contractor must provide NASA the name and contact details of the 

Contractor's ALERT Coordinator, w~thin 30 days of contract award. 

12 INTERRELATIONSHIP: Parent sow Paragraph(s): 3.4. 

Related DRDs: CEV-S-001 


13.1 SCOPE. 

The CEV project ALERT System Documentation provides informat~on relative 

to unexpected failures or discrepant conditions of parts, components, 

mater1als, specifications, software, facilities, manufacturing processes 

or test equipment used in equipment and to safety problem of general 

concern. 

This appl~es to failures or discrepant conditions encountered when such 

parts, components, materials, specifications, software, facilities, 

manufacturing processes or test equipment are applied within the limits 

of the applicable specificat~on. 

Generic problems experienced by the project or by program assests shall 

be reported in the GIDEP or NASA Adv~sory Network, as appropriate. 

Management documentation shall be adequate to ensure that: 

(a) the subject problem data are received, properly distr~buted, and 

thoroughly assessed for potential impact 

(b) ~dentified impact issues are resolved or corrected with NASA program 





managenement concurrence 

(c) cost data for special problem issues are accumulated and reported 

(d) all this information is captured and retained in a database. 

The Contractor and ltS subcontractors shall partlcipate in the Exchanging 

Parts, Materials, and Safety Problem Data Utilizing the Government 

Industry Data Exchange Program (GIDEP) and ensure that all applicable 

GIDEP ALERTS, GIDEP SAFE-ALERTS, GIDEP Problem Advisories, GIDEP Agency 

Action Notices, and NASA Advisories are: 

1) reviewed and dispositioned, 

2) ensure that all significant parts, components, materials, 

specifications, software, facilities, manufacturing processes or test 

equipment, and safety problems of a general concern are identified and 

corresponding data are exchanged wlth this system, and 

3) present the status of all applicable items for review at program 

milestones and readiness reviews in accordance with the S&MA Plan (DRO 

CEV-S-001) . 


S0300-BT-PRO-010: Government-Industry Data Exchange Program (GIDEP) 

Operations Manual 

NOTE: GIDEP Operations Manual identifies the GIDEP Requirements 

Guide as Appendix E. 


A. Implementation Procedures: 

The contractor and sub contractor implementation procedures shall provide 

details that will ensure that the contractor understands and wlll 

implement these procedures, which cover the scope; task importance; 

management responsibillties; technical expertise to identify and resolve 

any impacts; 'special problem' information sensitivity; and documentation 

necessary to comply with GIDEP and NASA policles. 

B. GIDEP ALERTs and NASA Advisories shall be prepared and responded to in 

accordance with the GIDEP Operations Manual, NASA Policies, and include: 

(a) Contractor initiated GIDEP Documents - The proposed GIDEP Document 

shall include, but not be limlted to: 

1. Essential details required ldentifying problem by types and/or 

manufacturer's name, special requirements and environments, the problem 

situation (conditlon) and cause, actions taken and recommendations. Such 

data shall be restrlcted to objective, factual information. 

2. Names of responsible lndividuals and organizations that may be 

contacted for further technical details. 

3. Upon CEV Project approval, contractor initiated ALERTs that are of 

general concern shall be coordinated wlth NASA (JSC NASA Advisory 

Coordinator) identfying the GIDEP document type (GIDEP ALERT, GIDEP SAFE 

ALERT, GIDEP PROBLEM ADVISORY, or GIDEP AGENCY ACTION NOTICE). If it is 

determined that a GIDEP document is required, the Contractor shall 

prepared the appropriate GIDEP document and submit to GIDEP, in 

accordance with the GIDEP Operations Manual. 

4. If it is determined in coordination with NASA (JSC NASA Advisory 

Coordinator) that the potentla1 problem lnformation lS limited to NASA 

only, the contractor will be provided JSC NASA Advisory Form, JSC Form 

1159 for completion. 

(b) Response reports for ALERT/Advisory disseminated by CEV Program (JSC 

NASA Advlsory Coordlnator) : 

1. The contractor shall respond to GIDEP Documents and NASA 

Advisories dlsseminated by the CEV Program (JSC NASA Advisory 

Coordinator) with one of the following three categories: 


CEV-S-012Page30f5





(a) No Impact 

(b) Usage w1th No Impact 

(c) Usage with Impact 

2. If the response is 'Usage with No Impact' or 'Usage with Impact', 

rationale/justification shall be provided to NASA (JSC NASA Advisory 

Coordinator) for continued usage. The "Usage with Impact" shall also 

require Contractor completion of the NASA Form 1544. Some items addressed 

in the NASA Form 1544 shall 1dentify the ALERT/Advisory number, the 

hardware which the response applies, identify the the part numbers 

affected, the system affected, give an analysis of the problem, and a 

narrative recommendation and/or corrective actions accomplished. 

3. Follow-up reports provide results of investigations, analyses, 

etc. extended beyond the 21 working days allowed for the initial report 

(may closeout if no corrective act10n required) . 

4. No response required on GIDEP Documents/NASA Advisories marked 

'Information Only' unless an impact 1S identified. 

134 FORMAT. 

(a) The Contractor's format is acceptable for the1r internal 

implementation procedures. 

(b) GIDEP docuements are to be prepared on the appropriate GIDEP form 

found in the GIDEP operations Manual. 

(c) NASA Advisories are to be prepared on the JSC NASA Advisory Form, JF 

1159. 

(d) The contractor's format is acceptable for providing the 'Task 

Management, Control, and Tracking Status' as long as it includes all the 

necessary information. An electronic database with access permission to 

the appropriate NASA personnel is preferred, especially the NASA JSC 

Advisory Coordinator. 

(e) Cost data are to be provided as required by the financial management 

reporting system and as necessary to substant1ate the data being 

submitted in support of criminal 1nvestigations 

(f) Contractor initiated GIDEP Document, - The Contractor proposed GIDEP 

Document shall be submitted to the project's S&MA representative with a 

copy to the CEV ProJect ALERT Coord1nator (JSC NASA Advisory 

Coordinator). Preliminary GIDEP Documents on the appropriate GIDEP Form 

shall also be coordinated. When 1mmediate NASA community notification is 

identified as urgent but time and/or complete technical detail is being 

gathered, a NASA AdV1sory, NASA Form 1159 may be utilized by coordinating 

with the NASA JSC Advisory Coordinator. Upon approval and technical data 

evaluation, the Contractor initiator shall follow-up with the appropriate 

GIDEP Document in accordance with the GIDEP Operations Manual. 

13.5 MAINTENANCE: Data shall be maintained as required to: 

(a) Document the current implementat10n procedures and GIDEP and NASA 

Advisory Policies. 

(b) Ensure that the released GIDEP 1nformation is complete, factual, 

accurate and up to date. 

(c) Ensure that the released NASA Adv1sory informat1on is complete, 

factual and up to date. 

(d) Tracking status provided periodically to demonstrate complete 

accomplishment of the task. 

(e) Stay current and accurate or as requested to support management 

activitJ.es. 

(f) Substantiate submitted costs or to include additional costs as they 

are 1ntended. 







1. 

3. 

PROGRAM: CEV 

DATA TYPE' 1/2/3* 

2. 

4. 

5 

DRDNO .. 

DATE REVISED. 

PAGE: 

6. TITLE. Problem Reporting and Correctlve Action (PRACA) Reports 

CEV-S-013 

May 2009 

1 

7 DESCRIPTIONIUSE' 

The Contractor shall report, evaluate, track, trend, process and 

disposition CEV-related hardware and software problems into the NASA 

Constellatlon problem data system. 

8. DISTRIBUTION' As determined by the Contracting officer 


10. SUBMISSION FREQUENCY: Per Data Requirements Matnx 

11 REMARKS: 

*Data Type 

Initial Report is Data Type 2 

Preliminary Report is Data Type 3 

Close-Out/Explanatlon is Data Type 1 

12. INTERRELATIONSHIP: Parent sow paragraph(s): 3.5. 


13.1 SCOPE: 

This data requirement establlshes a standard closed-loop process for 

handling CEV Project process, hardware, software, and ground support 

equlpment problems. 

13.2 APPLICABLE DOCUMENTS' 

cxP 70068 Constellation Program Problem Reporting Analysls and Corrective 

Actlon Requirements, Volume 1, 2, and 3. 

13.3 CONTENTS 

This DRD establishes requirements for reportlng of nonconformance/Problem 

data in accordance with the requirements provided in 

CxP 70068 Volumes 1, 2, and 3. 

a. Non-conformance/Problem documentatlon, data fields, and data field 

content shall be ln accordance wlth CxP 70068, Constellation Program 

Problem Reporting, Analysis and Corrective Action (PRACA) Requirements, 

Volume 3: Appendlces, and in accordance with thlS DRD. (as specified 

below) . 

Additional Data Elements: 

1 ProJect Element-CEV element 

2. System-CEV System 

3. Detected During Number- document number and type descrlbing this 

operation when problem was detected 

4. Subsystem-CEV Element subsystem 

5. Element location- Physical location on the CEV where the problem 

occurred 







6. End Item Control Number-An end-ltem control number is a sequential 

identifier contained in an implementing organization instructions 

Each problem entered into the PRACA information system that meets one or 

more of the conditions below shall have the data fields listed below 

completed: 

a. The problem is a functional failure of an item (explalned or 

unexplained) 

b. The problem occurs after the first instance of Acceptance 

Testing for an item 

c. The problem occurs after the first instance of Qualification 

Testing for an item 

1. prevailing Condition-Environment type when detected (hardware 

only) 

2. FMEA number-FMEA number which addresses the failure mode of failed 

elements (to the lowest level possible) 

3. Failure mode-A descrlption of the manner in which an item failed 

4. elL Ratlonale-Yes/No indicator that tells whether a elL is 

affected 

5. Materlal Defect, A-Defect-Indicates the defect that resulted in 

the failure (hardware only) 

6. Material Defect, B-Material-Indlcates the materlal that failed 

(hardware only) 

7. Correctlve Action/Recurrence Control Code-Classification of the 

primary recurrence control actions (hardware only) 

8. Baa Item 0satrsl !!~er :~ eaa item 8satrsl auffi8er is a se~eatial 

iaeseiEieF sOlitaiRes iR as im~lemeRt1Rg orgaaiBatisR 1Rstr~e6ieRs 

9. Expected date or mission of Interim disposition-Date that last 

interim disposltlon occurred 

10 Latest Interim D1Sposition Date-Date that last interim disposition 

occurred 

11. Hazard Report Number-Number assoclated with the approved hazard 

report 

12. Hazard Report Cause Identifier-Unique number of hazard report 

hazard cause 

13. Operating tlme/Cycle-total operating time on the hardware when the 

problem occurred, may be number of cycles (hardware only) 

14. Fallure Detection-How the problem was lnitially detected 

15. Time to repair-Time taken to complete repairs on the original 

failed unit (from problem detectlon, until full operation restored) 


16. Assembly Level-Level of maintenance where the repair took place 


17. Number of maintenance crew-number of persons required to perform 

the Repair (hardware only) 

b. Processing of non-conformances and determination of PRACA 

reportable status shall be in accordance with CxP 70068, Volume 1. 

c. All problem data from the CxP contractor shall be transferred into 

CxP PRACA system in accordance with CxP 70068, Volume 1 TABLE 4.1.1.3-1 

SCHEDULE OF PROBLEM CAPTURE AND TRACKING. 

Interim Dispos1tion 

Temporary disposltlon of problems for time frames not to exceed 6 months 

shall be permitted. 

Additional Documentation Requirements for Problem Disposltion 

Requlred documentation for problem dlsposition shall be as follows: 

Closed Problem - Documentation shall include the root cause(s), remedial 

and/or correctlve action (if required) or ratlonale for no corrective 

action required. If the problem is dispositloned by explanation with no 







corrective action required, the consequences of the problem occurring inservice 

and possible work-around shall also be documented. 

If problem analyses reveal inaccuracies or omissions in the FMEA/CIL, 

human factors process FMEA, software fault analysis, or Hazard Analysis, 

the contractor responsible for contlnuing engineering support on the 

system shall update the involved document(s) to correct the deficiency. 

Trending 

The Contractor shall periodlcally perform and report trend results and 

also on a timely, ad hoc basis in response to identified significant 

adverse trends. The Contractor shall use nonconformance/problem data, 

production parameters (such as Statlstical Process Control), and 

performance data to identify hardware, software, and/or human interface 

processes that are not in control, need additional review, and/or require 

correction. The Contractor will also report trends based on failure 

recurrence, risk measure, and/or cost. This will include 

effectiveness/concerns resulting from use of standard repairs. Where 

possible, trend tracking technologles such as Integrated Vehicle Health 

Monitoring Trending shall be incorporated to proactlvely measure trends. 

Trending and/or data mining mechanlsms/systems shall also to be employed 

to preemptively isolate impending failures/fal1ure conditions and support 

recommendations for corrective actions to mltigate critical failures or 

reduce risk. As a mlnimum, the trending data shall show problem 

occurrence frequency by subsystem, by LRU, by fal1ure mode, and by cause. 

Trend results shall be normalized into failure rates based on wear (as 

run tlme or starts) and/or opportunities for error detection (as 

inspections, tests, or units delivered). Trending results and related 

problem analyses shall be provided to the CEV Project on a regular basis 

(at least quarterly) and to the Constellation Program when significant 

results are determined 

13.4 FORMAT: Electronic format per Section J-2 2.3 2.1. 

13 5 MAINTENANCE: PRACA Reports shall be maintained and processed in 

accordance with CxP 70068 Volumes 1 and 3. 







1. 

3 

PROGRAM: CEV 

DATA TYPE. 1 

6. TITLE Cn.tical Processes 

2. 

4. 

5. 

DRDNO.: 

DATE REVISED. 

PAGE' 

CEV-S-015 

May 2009 

1 

7 DESCRIPTION/VSE: 

The Contractor shall document the controls that they shall use for those 

manufacturing processes where uniform high quality cannot be ensured by 

inspectlon or test alone and the failure would be of a critical nature. 

8. DISTRIBUTION' As determined by the Contracting Officer 



11. REMARKS' 

The Contractor should demonstrate and verify control of the quality of 

the operation by employing process controls throughout all phases of 

hardware manufacture. The intent of this standard is to ensure that 

manufacturing quality requirements are defined and that designs permit 

and facilitate the quality consideratlons of producibillty, 

repeatability, and refurbishabillty/maintainability. 

12. INTERRELATIONSHIP: Parent SOW Paragraph(s): 3.5. 


13.1 SCOPE: 

Any process that can not be verlfied by a reliable and repeatable inspection 

or test, and if not precisely applied and controlled within its defined 

limits, could result in hardware failure that results in loss of human life 

or serious inJury/illness to the flight crew, ground crew, or general 

public; or results in loss of mlSS10n, or loss of a significant mission 

resource. 


CXP 70059: Constellation Program Integrated Safety, Reliability, and 

Quality Assurance Requirements (and assoclated Children documents as 

specified in Attachment J-3, Applicable, Guidance, and Informational 



The Critical Processes document shall include as a minimum: 

1. Process controls' 

(a) Applicable manufacturing processing requirements with detailed 

performance and control prov~s~ons. 

(b) Process preparatlon requirements. 

(c) Detalled processing operations. 

(d) Conditions to be maintained during each phase of the process 

including environmental controls. 

(e) Methods for verlfying the adequacy of the processing materials, 

solutions, equipment, environments, and their assoclated control 

parameters. 

(f) Required records for documenting the results of the process 

~nspection, test, and verification. 







2. Equipment certlfication: 

(a) Manufacturing equipment tests and thelr results shall be recorded, 

certified, and maintained. 

(b) Plans for recertifying equipment as required by quality surveys, 

inspections or tests, or when changes are made which may affect process 

integrity. 

13.4 FORMAT' Electronic format per Section J -2 2.3.2.1. 



required. 







1. 

3. 

PROGRAM: CEV 

DATA TYPE' 2 

6. TITLE' Mechanical Parts Management Plan 

2. 

4 

5. 

DRDNO .. 

DATE REVISED' 

PAGE: 

CEV-S-016 

May 2009 

1 


To define and document the contractor's plan for acquisition, testing, 

handling, packaging, storing, and malntaining traceability for Mechanical 

Parts (including fasteners, bearings, studs, pins, rings, shims, valves, 

springs, brackets, clamps, and spacers) for flight and critical ground 


8. DISTRIBUTION: The contractor's Mechanical Parts Control Plan shall be 

provided to the NASA CEV S&MA organization as a minimum for approval. 



11. REMARKS' 

12 INTERRELATIONSmp: Parent SOW Paragraph (s): 3.5. 

Related DRD(s): CEV-T-019, CEV-T-069 


131 SCOPE: 

The Mechanical Parts Management Plan defines the contractor's approach 

for acquisitlon, testing, handllng, packaging, storing and maintaining 

the traceability of mechanical parts Fasteners shall be subject to 

additional requirements per NASA-STD-6008. 


NASA-STD-I-6016: Standard Materials and Processes Requlrements for 

Spacecraft 

CxP 70135: Structural Deslgn and Verificatlon Requirements 

CxP 70059: Constellation Program Integrated Safety, Reliability, and 

Quality Assurance (SR&QA) Requirements 

NPD 8730.2B. NASA Parts Pollcy 

NASA-STD-5019: Fracture Control Requirements for Spaceflight Hardware 

NASA-STD-6008: NASA Fastener Management and Control Practices 


The Contractor's Mechanical Parts Management Plan shall include the 

following: 

1. Acquisition: 

plan shall def~ne a process that specifles which mechanlcal parts 

must be procured from an approved manufacturer or a distributor. 

Plan shall define a process for certifying manufacturers and 

distributors of mechanlca1 parts. 

• Plan shall define a process to avoid procurlng defective 

mechanical parts as identlfied in a NASA Advisory or Government 

Industry Data Exchange Program (GIDEP) Alert. 

Plan shall define a process for ldentifying replacements for 

mechanical parts that become obsolete. 







Plan shall define a process for tracking the usage of limited life 

items. 

plan shall def1ne a process for 1dentification and disposition of 

mechanical parts that have exceeded their life limit. 

2. Testing: 

plan shall def1ne a process for acceptance testing of mechanical 

parts. 

plan shall def1ne how nonconform1ng mechanical parts shall be 

dispositioned according to the contractor's qua11ty management 

system (QMS). 

• Plan shall define a process to report generic nonconformances 

and/or counterfeit part 1ssues to GIDEP. 

3. Handling, Packaging and Storage: 

Plan shall describe how mechanical parts w111 be maintained in 

the appropr1ate environment and controlled access storage. 

• plan shall describe how reuse of mechanical parts will be 

controlled. 

• Plan shall describe how mechanical parts will be issued and 

returned to storage for proper account1ng. 

4. Traceability: 

Plan shall describe how commingling of mechanical parts, and 

specific lots of mechanical parts (when lot control requirements 

are requ1red) will be prevented. 

• plan shall describe when Manufacturer's Tset Reports (MTRs) or 

equ1valent are required MTRs are always required for fracturecr1tical 

items per NASA-STD-5019. MTRs are always requ1red for 

fracture-crit1cal, low-risk, and fail-safe fasteners per NASA-STD- 

6008. 

Plan shall describe when Certificates of Compliance or equivalent 

are required. 

5. Compliance: 

• Plan shall, for fasteners, define an implementation approach 

consistent w1th the applicable sections of NASA-STD-6008. 

• Plan shall define an approach consistent with CxP 70059, Appendix 

A, to verify compliance with this Mechanical Parts Control Plan at 

the contractor and subcontractor level. 

13.4 FORMAT: Electronic format per section J -2 2.3.21 


subm1tted to NASA for approval. Complete re-issue of the document is 

requ1red. 






DATA REQUIREMENTS DESCRIPTION (ORD) 

1. 

3. 

6 

7. 

PROGRAM: CEV 2. DRDNO.: CEV-T-001 


5 PAGE: 1 

TITLE: Integrated Models, Simulations and Support Plan 


Th1s DRD defines the period1c delivery of a group of related models and 

s1mulations and a Modeling and Simualtion Support Plan. The DRD 

includes: 

1. Architectural models and system diagrams developed using an 

architectural modeling tool; 

2. A full system, discrete-event simulation model runnable on an 

analyst's desktop; 

3. High-fidelity simulations implemented as HLA federations; 

4. A Modeling and Simulat10n Support Plan 

These deliveries provide NASA with detailed funct10nal and behavioral 

views of the CEV design as it matures and with a modular simulation 

capability to support trade studies, system engineer1ng and integration, 

flight software development and testing, and operations planning. 

8. DISTRIBUTION' As determined by the Contracting Officer. 

9. INITIAL SUBMISSION. Per Data Reqmrements Matrix. 


11. REMARKS 

12. INTERRELATIONSHIP. Parent SOW Paragraph (s): 2.4. 

Referenced from SOW Paragraph{s): 2.3. (c), 6.1.5, 10.3.7 

Related DRD{s): CEV-T-002 

13 DATA PREPARATION INFORMATION. 

13.1 SCOPE: 

The Modeling and Simulation Support Plan and associated model deliveries 

includes all the planning and effort necessary to perform analysis of 

integrated vehicle performance, environmental effects and reSOurce 

management plus all simulat10n models needed for test1ng system hardware 

and software. It is expected that all deliveries will cover the full 

vehicle and that detail, accuracy and scenar10 coverage will increase as 

the CEV design matures. 


CxP-70041 Constellation Program NExIOM Standard for Tool, Model and 

S1mulation Data 

CxP 70076 Constellation Program Modeling and Simulation Management 

Requ1rements - Level II 

IEEE 1516 -2000: IEEE Standard for Modeling and S1mulation (M&S) High 

Level Architecture (HLA) -- Framework and Rules 

IEEE 1516.1-2000: IEEE Standard for Modeling and S1mulation (M&S) High 

Level Architecture (HLA) .Federate Interface Specification 

IEEE 1516.2-2000: IEEE Standard for Modeling and Simulation (M&S) High 

Level Architecture (HLA). Object Model Template (OMT) Spec1fication 

IEEE1516.3-2000· IEEE Recommended Practice for High Level Architecture 

(HLA) Federat10n Development and Execution Process (FEDEP) 


CEV-T-OOI Page 1 of3






Coverage: Delivered models shall represent all CEV subsystems listed in 

sow section 6.2 plus (a) any ground systems and communications models 

required to simulate intended system function, (b) any relevant vehicle 

environment models (e.g. gravltational, thermal, electromagnetic, 

radiation) utilized to evaluate nominal and off-nominal system 

performance and (c) models of other Constellation elements at a fidelity 

appropriate to enable evaluation of integrated CEV performance. 

The models will emulate nominal performance over a range of inputs 

corresponding to design parameters to support trade studies as well as 

off-nominal operations to support safety analysis and flight software 

testlng. Scope of variability for trade studies and off-nominal 

scenarios will be determined by the Integrated Modellng and Simulation 

(IM&S) Working Group. 

Each delivery for this DRD shall consist of: 

1. A revision of the Modeling and Simulation Support plan 

2. An Excel-based manifest listing each model included in the delivery 

along with the model version and a brief description. 

3. A revision of the System Architecture Model. This model shall 

represent vehicle function, structure and behavior via: 

(a) Function and component hierarchies 

(b) An allocatlon of functions to components 

(c) Functlonal models (Functional Data Flow Diagram, IDEFO, extended 

Function Flow Block Diagram) 

(d) Dynamic models (State Transition Diagram) 

(e) UML diagrams (e.g., sequence diagrams, state charts) 

(f) Architectural (Physlcal Architecture Diagram, Architecture 

Interconnect Diagrams) 

(g) Process (Process Flow Diagram) 

The System Architecture Model and its components shall be delivered in an 

electronic format readable by Cradle. 

4. A revision of the full-system, desktop, Discrete-Event Simulation that 

can be run in a COTS tool (e.g., COREsim) or a non-COTS simulation 

package. If a non-COTS simulation package is used, then the Contractor 

shall also dellver source code, bUlld files and a compiled version. 

(a) For the discrete-event slmulation model, no constraint is placed on 

the units of simulation other than good software engineering practice. 

(b) The Discrete-event Simulation Models be capable of running full 

vehicle, full-mission scenarios in less than one hour and narrower 

simulations In 10-20 minutes. 

5. Starting at subsystem PDR, an HLA federation wlth coverage described 

above and including documentation 

(a) HLA federates shall be modeled at levels that support modularity, 

effective reuse and unit testing and that support the needs of software 

and hardware-ln-the-loop testing. 

(b) The HLA federation shall simulate system performance at least as fast 

as realtime. When this is not achievable via the HLA protocol, a solution 

(e g. Mil-Std 1553) that corresponds to the flight enVlronment will be 

agreed upon Vla the Integrated Modeling and Simulation (IM&S) Working 

Group. 

(c) Plannlng and development of HLA federates shall be coordinated with 

development of the Engineerlng CEV models speclfied in DRD CEV-T-002. 

The HLA models shall reuse code or algorithms from the Engineering CEV 

models where approprlate. 







6. Documentation for each model or federate 

7. Source code, data files and bUlld files for each model or federate 

8. Compiled versions of each model that runs under one of Windows, 

Maclntosh, Linux or another Unix distribution. 

9. Source code for tools used to create data used by or included in the 

models, unless they were created with COTS software 

Each revisl0n of the Modeling and Slmulation Support Plan shall contain 

at least these sections: 

1. An overview of the Contractor's approach to managing the development 

of models and simulations 

2. A manifest briefly describing each planned model and simulation, what 

analyses it will help support, the date the model or simulation will be 

dellvered and an indication of which DRD-governed deliverables (if any) 

the model or simulation contributes to. It lS expected that thlS 

manifest will contaln TBDs. This manlfest can optionally be combined 

with the Excel-based manifest of models actually delivered in this DRD 

delivery. 

The Contractor can include additional sections that further describe 

thelr modeling and simulatlon support process or can substitute a 

document template used internally if it contains thlS information. 

Documentation for each model shall include: 

1. An XML document conformant to the CXP-70041, Constellation Program 

NExIOM Standard for Tool, Model and Simulation data. 

2. System and Federation Object Models for the HLA federation; 

3. Written documentation for each model sufficient for knowledgeable 

engineers to conduct trade studies or to build models that correctly 

interface to this one where additional detail is needed over the HLA 

System and Federation Object Models and NExIOM portl0ns of this delivery. 

13.4 FORMAT. ElectronlC format per Section J -2 2.3.2.1. 

13 5 MAINTENANCE: A11 models sha11 be utllized for CEV system maturation 

through operatl0n and therefore maintalned to the as-built configuration. 







1. 

3. 

6. 

7. 

PROGRAM' CEV 2. DRDNO.: CEV-T-002 


5. PAGE 1 

TITLE:CEV Engineering Models 

DESCRIPTIONJUSE: 

This DRD defines the per~odic delivery of engineering models of the CEV 

system, modules, subsystems, and components These models will be 

discipline (e.g. aerothermal, structural loads, trajectory), mission 

(e.g. logistics planners, sequence planners) and system (e.g. sizers, 

cost estimators, risk est~mators) oriented and will be implemented using 

many different tools and data formats. These models are different in 

nature than models addressed in CEV-T-001 (Integrated Models, simulations 

and Support Plan) in that they do not represent strict mission-time-line 

simulations. CEV-T-001 should be referred to for all mission time-stepped 

models and simulations. 

These models provide NASA and the Contractor with des~gn and operational 

trade study results that guide system and mission design decisions. These 

models are used by NASA and the Contractor in day-to-day design and 

analysis activ~t~es. NASA requires ~nformed application of available 

tools and models based on their capability and applicability to CEV 

design ~ssues as they arise. 

Models of th~s type are called out in several DRDs, including CEV-T-009 

(CEV Analysis Report) as well as discipl~ne and system oriented data 

books and mathematical model DRDs. NASA intends to have insight and 

understanding ~nto the applicabil~ty and provenance of these models. NASA 

intends to own a searchable electronic store of CXP-70041, NExIOM 

Standard for Tool, Model and Simulation Deliveries conformant documents 

for each tool, model or simulation util~zed in the development of the 

CEV. 


9. INITIAL SUBMISSION Per Data Requirements Matrix. 


11. REMARKS: 

12 INTERRELATIONSHIP: parent sow Paragraph (s): 2.4. 

Referenced from sow Paragraph(s): 2.3. (c), 6.1.5, 10.3.7; 6.1.2 (and 

subparagraphs), 6.2.2 (and subparagraphs), 6.4.2 (and subparagraphs), 

6.1.3 (and subparagraphs), 6.2 3 (and subparagraphs), 6.4.3 (and 

subparagraphs), 6.1.6.2, 6.2.6.1, 6.4.6.2. 



13.1 SCOPE' 

This DRD appl1es to tools, models and simulat10ns that are: 

a) Not covered by CEV-T-001, Integrated Models, Simulations and 

Support plan. 

b) Direct or ind1rect sources of data delivered in any other DRD 

c) Direct or ind1rect sources of data utilized 1n a CEV Project 

reV1ew milestones. 


CEV-T-002Page 1 of2



Models covered by this DRD are exemplified by system sizers, performance 

estimators, environmental models, scenario planners, failure calculators, 

and cost estimation utillties. Models of other types are also covered per 

the requirements of SOW section 2.1 2. 


CxP-70041 constellation Program NExIOM Standard for tool, Model and 

Simulation Data. 

CxP 70076 Constellation Program Modeling and Simulation Management 

Requirements - Level II 


Each CEV Model delivery shall consist of: 

a. An XML document conformant to CxP-70041. 

b. Any pre-existing technical documentation lncluding user manuals and 

technical publications. 

c. Source code and build flIes for all models. 

d. Compiled versions that run under one of Windows, Macintosh, Linux and 

UNIX variants. 

e Source code for tools used to create lookup tables within the models, 

unless they were created with COTS software. 

f. Lookup tables utlllzed within the models. 

13.4 FORMAT: Model format shall be the native format associated with the 

model being dellvered. When other DRDs callout a specific format (e.g. 

NASTRAN, etc ... ) then the delivery format requirements called out in that 

DRD shall be adhered to. Electronlc format requirements per Section J-2 

2.3.2 1 shall be followed as well. 

13.5 MAINTENANCE: All models shall be utllized for CEV system maturation 

through operation and therefore maintained to the as-built configuration. 


CEV-T-002 Page 2 of2





1. 

3. 

PROGRAM: CEV 

DATA TYPE: 2 

6. TITLE: Software Development Plan 

2 

4 

5. 

DRDNO.: CEV-T-005 

DATE REVISED. May 2009 

PAGE 1 

7. DESCRlPTIONIUSE: 

A plan for conductlng the software development effort. This DRD develops 

and records the plans for all software development activities. 

8 DISTRIBUTION: As determined by the Contractmg Officer. 

9. INITIAL SUBMISSION: per Data Requirements Matrix 

10 SUBMISSION FREQUENCY Per Data Requirements Matrix 

11. REMARKS: 

The term 'software development' is meant to include new development, 

modification, reuse, reengineering, maintenance, and all other activities 

resulting in software products. 


CxP 70065, Constellation Program Computing System Requirements, 

Appendix C (Software Types by Classification Matrix) 


Standard ISO/IEC 12207: 1995, Standard for Informatl0n Technology - 

Software life cycle processes 



Software life cycle processes - Lifecycle data 

12. INTERRELATIONSHIP' Parent SOW Paragraph (s): 6.5.2. 

Referenced from SOW Paragraph(s): 6.5.3 

Related DRD(s): CEV-O-008, CEV-S-001,CEV-T-006 

13 DATA PREPARATION INFORMATION' 

13.1 SCOPE: 

The Software Development plan provides inslght into, and a tool for 

monitorlng, the processes to be followed for software development, the 

methods to be used, the approach to be followed for each activity, and 

project schedules, organizatlon, and resources. This plan details the 

system software, project documentation, project schedules, resources 

requirements and constraints, and general and detailed software 

development activities. 


NPR 7150.2: NASA Software Englneering Requirements (all shall 

statements/the compliance matrix only, excluding the software safety 

requiremen t) 


In accordance wlth NPR 7150.2, NASA Software Engineerlng Requirements, 

and using IEEE/EIA 12207.1-1997 as guidance, the Software DevelopmentPlan 

shall conslst of seven volumes. 

Volume 0 Software Development Plan shall contain. 


CEV -T -005 Page 1 of 5





(a) Project organizational structure showing authority and responsibility 

of each organizational unit, including external organizations (i.e., 

Safety and Mission Assurance, Independent Verification and Validation 

(IV&V)) . 

(b) Engineering environment (for development, operation or maintenance, 

as applicable), includ1ng test environment, library, equipment, 

facilities, standards, procedures, and tools. 

(c) Work Breakdown Structure (WBS) of the life cycle processes and 

activities, 1ncluding the software products, software services, and nondeliverable 

items to be performed. The WBS also includes budgets, 

staffing, physical resources, software size, and schedules associated 

with the tasks. 

(c) Management of safety, security, privacy, and other critical 

requirements of the software products or services. 

(d) Subcontractor management, including subcontractor selection and 

involvement between the subcontractor and the acquirer, if any. 

(e) Quality assurance. 

( f) RESERVED 

(g) Verification and validation, including the approach for interfacing 

with the independent verificat10n and validat10n agent. 

(h) Acquirer involvement. 

(i) User involvement. 

(j) Risk management. 

(k) Security policy. 

(1) Approval required by such means as regulations, required 

certifications, proprietary, usage, ownership, warranty and licensing 

rights. 

(m) Process for scheduling, tracking, and reporting. 

(n) Training of personnel. 

(0) Software life cycle model including description of development 

methodology and approach, software integration and hardware/software 

1ntegration processes, software delivery, and maintenance/regression 

testing. 

(p) Configurat10n management process of all software products, 1ncluding 

this document. 

(q) Software documentation tree. 

(r) Peer review/inspect10n/walkthrough process of all software work 

products. 

(s) Process for early identificat10n of testing requirements that drive 

software design decisions, e.g., special system level timing 

requirements/checkpoint restart. 

(t) Content of software documentation to be developed on the project. 

(u) Justification for reuse of exist1ng software, modification of 

existing software, and the development of new software. For reuse of 

exist1ng software, a map must be developed which shows the original 

requirements associated w1th the existing software matrixed against the 

CEV requ1rements to demonstrate that the reuse is appropr1ate. 

Volume 1 Software Process Improvement Plan (SPIP) 

The software process improvement plan describes the plan for performing 

continuous process improvement of the software development, configuration 

management, test and verification, build and release management, and 

maintenance processes used to produce, control and mainta1n the software 

products and artifacts. 

The Software Process Improvement plan shall contain: 

a. Purpose and scope of document volume 

b. Introduction/overview of software process improvement 

c. Relationsh1p to other software and project plans 

Volume 2 software Measurement Plan (SNP) 







The software measurement plan defines the software measurements, or 

metrices, that will be collected and reported. The plan will also 

include the process used to collect software metrics and the relationship 

to software metrics collected by subcontractors. 

The Software Measurement Plan shall contain: 


b. Introduction/overview of software metrics and collection process 

c. Relationshipt to other software and project plans 

d. Description of the software measurement process, goals and 

objectives, organization, roles and responsibilities, planning 

and collection activ1tes 

e. Description of the relationship of the software measurement plan 

to the project performance and measurement plan 

f. Description of software metrics to be collected, including (but 

not limited) 

i) Metric collection category 

ii) Metric name 

iii) Purpose/scope of metric 

1V) Collection frequency 

v) Collection method 

vi) Analysis cr1ter1a 

Volume 3 Software Development Plan Tailoring 

The software development plan tailoring describes the process tailor1ng 

that has been approved by CEV software management. It shall also 

descr1be any approved subcontractor ta1loring of the standard processes 

descr1bed in the Software Development or Configuration Management Plans. 

It shall also describe any NPR 7150.2 waivers approved by the NASA 

Independent Technical Authority. 

The Software Development Plan Tailoring shall contain: 


b. Introduction/overview of software reconfiguration process 

c Relationship to other software and project plans 

d Descript10n and guidelines for SDP tailoring 

e. Separate section for each project orgainizational unit or 

subcontractor providing SDP tailoring to include: 

i) Descr1pt1ons of each tailored process or product to the 

equ1valent level of detail contained in the SDP 

ii) List of all tools used that are not part of the standard 

software development tool chain as listed in the SDP 

1ii) List of all additional programming languages and 

associated programming language coding standards used 

Volume 4 Software Reconfiguration process Plan 

The software reconfiguration process plan provides a descr1ption of the 

plans to to collect, process, vaI1date/verify, and produce 

reconfiguration data products. 

The Software Reconfiguration Process plan shall contain: 


b. Introduct10n/overview of software reconf1guration process 

c. Relat~onship to other software and project plans 

d. Descriptions of the follow1ng software reconfiguration process 

areas: 

i) Flight Software Mission reconfiguration 

i1) Ground Software Mission reconfiguration 

11i) Simulation software reconfiguration 

e. Description of the tools and support software developed used to 

produce the reconfiguration products for each of the above 

areas (d.) 







f~ Description of the review process for reconfiguration products 

produced by each of the above areas (d.) 

Volume 5 Software Classification and NPR 7150.2 Mapping 

The Software Classification and NPR 7150.2 Mapping shall contain: 

a. Purpose and scope of the document 

b. Introduction/overview of NPR 7150.2 software class1fication 

activites and process mapping 

c. Relationship to other documents 

In accordance with NPR 7150.2, NASA Software Engineering Requirements the 

contractor shall 

d. Provide a table that lists the following: 

1) Classification all software developed or used by the 

project at a level that allows appropriate process rigor 

to be applied 

ii) Determ1nation of the safety criticality of the software 

(yes/no) 

iii) Assessment of the appropriate level of software 

assurance based on classifact10n and safety criticality 

e. Provide a set of tables that map the appropriate processes to 

each requirement in the NPR 7150.2 for each software 

classification level 

Provide add1tional tables, based on software classificat10n, for any 

approved tailoring or waivers from 7150.2 for a specific software 

classification level. 

CxP 70065, Constellation Program Computing System Requirements, Appendix 

C (Software Types by Classification Matrix) shall be used as guidance in 

prepar1ng the software classification sect10n of this volume. 

Volume 6 Software Build Plan 

The Software Build Plan shall contain: 

a Scope, includ1ng system identification, system overview, and 

relationship to other plans. 

b. ProJect organization structure showing authority and 

responsibility of each organization unit, including external 

organizations, and any organization unique to a software bU11d. 

c. Software bU11d planning process applied to all software builds. 

d. Mapping of software components (CSCI/CSC) to software builds. 

e. Traceability between software builds and the software requirements 

being implemented 

For each software build, the following contents shall be provided: 

f. a description of the software build. 

g. Assumptions and ground rules. 

h. Necessary process tailoring from the SDP or SCMP. 

i. An integrated software load schedule including major milestones, 

external dependencies, and customers who need the software load. 

j. A 11st of the software components in terms of CSCI/CSC 

incorporated in the software load, including flight software, 

ground software, simulation software, and data service software. 

k. A list of COTS/GaTS/MOTS incorporated into the software build. 

1. A description of the evolution of software components of the 

software load, including capability addltlon and deletlon for each 

software component, and software classification and criticality 

changes of software components. 

m Software load building instructions and procedures. 

n. A list of all Change Requests (CRs) , Software Problem Reports 

(SPRs) incorporated into the SW build. 

o. A list of deliverable products of the build, or a reference to the 

deliverable list. The deliverable products shall include the 

build software package and the associated documentation. 







p. A description of the software build delivery mechanism and a 

descript~on of the maintenance of the software build prior to the 

next software build. 

q. Lessons learned. 

13.4 FORMAT: Electron~c format per Section J-2 2.3.2.1. 


submitted to NASA for approval. Changes shall be ~dentified and complete 

re-issue of the document is required 






Modification 65





1. 

3. 

PROGRAM. CEV 

DATA TYPE: 2 

6 TITLE:CEV System Analysis Plan 

2 

4. 

5 

DRDNO.: 

DATE REVISED: 

PAGE' 

CEV-T-008 

May 2009 

1 

7. DESCRIPTIONIUSE. 

The purpose of th~s document is to describe the overall plan/approach the 

contractor shall ~mplement for completing all analyses and trade studies 

required for the development and delivery, as an end product, of the Crew 

Exploration Veh~cle (CEV) to NASA. The plan should be formulated based 

on Requ~rement Analysis Cycles (RACs) , Design Analysis Cycles (DACS), and 

Verification Analysis Cycles (VACs) that tie directly to major 

milestones, major events (e.g., verification tests), etc. of the CEV 

development/delivery. Note, this plan should ~nclude assessments for the 

operational use of the CEV, but does not ~nclude studies/updates to be 

completed after delivery of the CEV which will be addressed in another 

product. 

This plan is updated prior to each RAC/DAC/VAC and should serve as a 

single-source catalog of information to personnel performing the analyses 

and trade studies as a part of the upcoming analysis cycle, for NASA 

personnel responsible for monitoring the contractor's activities, and for 

overall implementat~on of the CEV program 

8. DISTRIBUTION: As determ~ned by the Contract~ng Officer. 


10. SUBMISSION FREQUENCY· Per Data Requirements Matrix 

11 REMARKS: 

Contractor may propose the use of task sheets or other formats inclusive 

to the plan. 

12. INTERRELATIONSHIP: Parent SOW Paragraph(s): 2.4 

Referenced from SOW Paragraph 6 1.6.2 


13 1 SCOPE. 

See 13.3 Contents below. 



The minimum content for this plan is described below. 

1. A descrlptlon of the contractorls methodology for lmplementation of 

the overall CEV Master Analysis Plan and Schedule, to include issue 

resolution, change requests, etc. 

2. A descr~pt~on of the contractor's methodology for ensuring compliance 

w~th the overall CEV development/design requirements and schedule(s) 

3. The contractor's methodology to use this plan and its implementation 

to provide an understanding of the CEV performance as a part of an 

integrated vehicle system (e.g., CEV mated to CLV, CEV docked with the 





ISS, etc.) 



4. A description of the contractor's methodology for ensuring consistency 

among assessments, analyses and trade studies 

5 Clearly ident~fied roles and responsibilities between the contractor 

organization and NASA relat~ve to implement~ng the CEV Master Analysis 

Plan and Schedule, the supporting RACs, DACs, and VACs, etc. Note, this 

can include required reviews/concurrences of the plan and updates, 

required information exchange/dependencies, contractual obligations, etc. 

6. A description of the contractor's methodology for completion/closeout 

of all activit~es within an analysis cycle; note, may include planned 

presention(s), solicitation for comments/feedback, action item closures, 

final report(s), etc. 

The minimum content for each RAC/DAV/VAC update is described below. 

1. Identif~cation of the analyses to be completed, with an ~dentifier for 

each cycle (e.g., number, letter). 

2. For each RAC/DAC/VAC planned, 

(a) A listing and descr~ption of all analyses, assessments and trade 

studies to be completed as a part of this cycle. Note, the description 

may ~nclude the fidel~ty of the product to be prov~ded (e.g., draft, 

initial baseline, update). 

(b) A description or matrix of the interdependencies between the analyses 

etc. completed as a part of this cycle and/or other cycles. 

(c) A description of the configuration(s) assumed/to be utilized for the 

CEV for the analyses of this cycle. Note, this is meant to provide 

supporting information for the analyses and ensure the CEV is capable of 

performing in the planned operational scenarios. 

(d) A descr~pt~on of the common assumptions and input data for all 

personnel performing the analyses and trade studies to use as a part of 

th~s cycle, with rationale and/or the source for this information 

identified. 

(e) Any required matrices or other assessment tools to ensure the 

products for any cycle satisfy the requirements of the overall CEV 

program (e.g , matrix cross-referencing the analyses to the CEV 

verification plan) . 

(f) A list~ng of all products/deliverables required for this spec~fic 

cycle, including the proposed format for each or identification of a 'goby' 

as an example. Note, where possible the contractor should strive for 

s~mplicity and clarity in the delivered products (e.g., short analyses 

summaries and/or executive summaries with supporting data, internal 

documents available on request, use of web site or share area rather than 

paper distributions, etc.). 

(g) A matrix or description of which products are to be provided by the 

contractor versus NASA personnel, with rationale for the proposed 

approach. Note, this can include redundant assessments if required for 

verificat~on/validation of the contractor's products of the problem or 

objective that motivated the innovation's development. 

13.4 FORMAT: Electron~c format per Section J-2 2 3.2.1. 


submitted to NASA for approval. Updates to the plan that is baselined at 

SDR must be provided for each cycle, and the contractor must account for 

the time required for NASA review and approval in their outl~ned 

schedule. 







1. 

3. 

PROGRAM CEV 

DATA TYPE: 3 

6. TITLE. System Performance Analysis Report 

2. 

4. 

5 

DRDNO .. 

DATE REVISED: 

PAGE: 

CEV-T-010 

May 2009 

1 


This deliverable is used to verify the integrated system performance of 

the CEV Spacecraft through analysis of the spacecraft requirements in the 

relevant design environments. This deliverable provides a summary of the 

findings for each analysis cycle, showing progress along the trade tree 

and giving key data backing up those flndings. This DRD is used to 

archive the rationale for decisions made in the project during each of 

these analysls cycles, and can be used to provide key decision summaries 

to project management. 

8. DISTRIBUTION. As determlned by the Contracting Officer. 

9 INITIAL SUBMISSION' Per Data ReqUlrements Matrix 


11. REMARKS. 

12. INTERRELATIONSHIP: Parent sow Paragraph(s): 2.4. 

Referenced from sow Paragraph(s)' 2.7.1 


131 SCOPE: 

The System Performance Analysls Report will serve as an integration and 

analysis tool for determlning that the CEV System will meet its 

performance and operational requirements and for documenting the 

rationale on all analysis cycle decisions. 



Each report shall include the following sections: 

(a) Executive Summary 

(b) Analysis Cycle Objectives 

(c) Analysis Cycle Requirements and Constraints 

(d) Inltializing Data References 

(e) Summary Results 

(f) Key Flndings/Recommendatlons. 

Summary Results shall lnclude integrated performance analysis of the 

following products: 

(a) Thermal analysis of the spacecraft including components and habitable 

volume to ensure adequate heat rejection capability and passive thermal 

control. 

(b) Power analysis to ldentify peak and average power for all scenarios. 

(c) Mass properties analysls for the spacecraft throughout all mission 

phases. 

(d) Aerodynamlc and aero thermal analysis. 

(e) Micrometeorold and orbital debrls lmpact/penetratlon analysis. 

(f) Communications coverage analysis. 

(g) Propulsion system analysls including propellant margins and on-orbit 


CEV-T-OlO Page 1 of2





maneuverability. 

(h) Guidance, navigation and control analysis including rendezvous, 

proximity operations, and mating. 

(i) Thermal analysls for safing upon landlng. 

(j) Delta-v budget for CEV 

(k) Deceleration/ landing system performance. 

(1) EMI/EMC analysis. 

(m) Descent trajectory analysis including any orbltal phasing to increase 

landing cross-range, heating, aerodynamic loads, stability, accelerations 

and safe disposal of expendable elements. 

(n) Attitude determination and navigation state accuracy analysis. 

(0) Radiation assessment for crew health and spacecraft performance. 

(p) CEV performance assessment when subjected to environments. 

(q) Thermal Protection System integrity. 

(r) Human factors assessment for all CEV crew operations including crew 

time estimation and habitability assessments. 

(s) Analyses of fllght and ground operational attributes to include a 

description of how the systems products serve the operators (e.g., flight 

crew, ground operations, and flight operations) . 

(t) Integrated abort performance assessment. 

(u) CEV computer resource estimation. 

(v) Internal volume allocatlon of the CEV cabin. 

(w) Consumable analysis including CEV spacecraft systems, food and 

drinking water. 

(x) Flammability, toxic off gassing and materials compatibility analysis. 

The summary results for each product of the System Performance Analysis 

Report shall address the following if applicable: 

(a) provide the detailed analysis of the lntegrated performance for all 

mission phases (including operations) of the CEV Spacecraft in the 

relevant design environments. 

(b) document analysis cycle and document the resulting key findings, 

performance metrics, and selectl0n recommendations, with rationale. 

(c) document in summary fashlon the trades conducted, recommended changes 

wlth associated rationale, and lnterface and interoperability issues and 

recommendat10ns. 

(d) evaluate operational sequences/scenarios which include utilization 

environments, measures of effectiveness (MOEs), and how the system 

producrs should be used. 

13.4 FORMAT: Electronic format per Section J-2 2.3.2.1. Requirements 

traceablllty (including decision support and requirements valldation 

data) must be maintained wlthin the requirements database. 

13.5 MAINTENANCE. Changes shall be ldentified and complete re-lssue of the 



CEV-T-OIO Page 2 of2





1 

3 

PROGRAM. CEV 

DATA TYPE. 1 

6. TITLE: Master Verifl.cat~on plan (MVP) 

2. 

4. 

5. 

DRDNO.: 

DATE REVISED. 

PAGE: 

CEV-T-015 

May 2009 

1 


The MVP documents the ver~fication planning and ~mplementation activities 

that will provide evidence that the CEV System meets the identified 

system, module, subsystem, and component requirements. 



10. SUBMISSION FREQUENCY: Per Data Requirements Matnx 

11. REMARKS: 

The following applicable documents: CXP-70135 applies to the 

static/strength test plan and dynamic test plan volumes only. 

The follow~ng document(s) may be used as guidance: 

NASA-HDBK-7005: Dynamic Environmental Criter~a 

• CXP-70008: Constellation Program Master Integration and Verification 

plan 

12. INTERRELATIONSHIP: parent sow Paragraph(s): 2.1.7. 

Referenced from SOW Paragraph(s): 6.1.4, 6.2, 6.2.1, 6.2.6, 6.2.7 


CXP-72097: Crew Exploration Vehicle Master Verification Plan 

13 DATA PREPARATION INFORMATION. 

131 SCOPE: 

The Master Verif~cation plan shall discuss all disciplines and activities 

required for the verification of deliverable hardware and software. The 

Master Verification plan provides a thorough description of the approach 

and structure for implementing the verificat~on program, as well as 

detailed descriptions of the planned verification act~v~ties for each 

requirement. 


CXP-72097: Crew Exploration Vehicle Master Ver~fication plan 

CXP-70135: Constellation Program Structural Design And Ver~fication 

Requirements 

NASA-STD-5017: Des~gn and Development Requirements for Mechanisms, 

Sections 1-4 


The Master Verification plan shall comply with the CEV Master 

Verif~cation plan (CXP-72097). This plan shall define the verificat~on 

planning and implementation activities that provide evidence that the 

system waS bu~lt to meet design and performance requ~rements. Component, 

subsystem, module, and system testing shall be planned as an integrated 

program; i e., test plans for an individual element shall be tailored to 

that element's operational requirements, consider~ng all testing to be 

performed from development through System acceptance testing and 

integrated test~ng. These plans shall be subject to NASA approval and be 



NNJ06TA2SC 



Modification 6S 

configuration controlled in accordance with DRO CEV-M-003, Configuration 

Management Plan and Reports. 

The Master Verification Plan shall define the verification and 

cert1fication process for the design, functional, interface and specialty 

engineering requirements for CEV hardware and software at the end-to-end 

system, subsystem assembly and component levels including interface 

requirements with other Constellation systems and equipment. 

The verification program shall include the tests, demonstrations, 

analyses, and 1nspections requ1red to meet Critical Items List (CIL) 

retention rationale and to control hazards. 

The Master Verification Plan shall be organized to include system-level 

and subsystem-level verification discussions, to facilitate its 

distribution and review. Addit1onally, for each subsystem, a detailed 

overview of verification object1ves, scope and extent of associated 

verification activities, including the verification configuration and its 

relationship to the flight configurat1on, will be defined at the module, 

integrated subsystem, subsystem assembly, and major components levels. 

The Master Verification Plan shall include verification requirements that 

are specific to performance and operational parameters. These 

Verification requirements w111 be satisfied using the methods of test, 

analysis, inspection or demonstrat1on for compliance. 

In addition to demonstration, analysis and inspect10n, the Master 

Verificat10n plan shall address the following types of testing: (1) 

Ground Tests, (2) Flight Tests, (3) Development Tests, (4) Component 

Tests, (5) Functional Tests, (6) Integration Tests, (7) Hardware-in-theloop 

(HWIL) Tests, (8) Software-1n-the-Ioop (SIL) Tests, (9) Human-inthe-loop 

Tests, (10) Nonoperating Environment Tests, (11) Operating 

Conditions & Environment Tests, (12) Acceptance Tests, and (13) 

Qualification Tests 

The Master Verification Plan shall include: 

1. Overview of the Project's verification program (i.e., 

qualif1cation/acceptance vs. protoflight, verification of spares, 

refurb1shrnent/reverificat1on/recertificat1on plans) . 

2. Description of the Project's organizational structure for implementing 

the ver1f1cation program (1.e., organizat1on's involved in component vs. 

system tests, review and signoff authority for compliance data) . 

3. Verification matrix that clearly documents the verification method or 

methods employed for each System level requirement and each allocated 

requirement. For each major test (i.e. formal verification, acceptance 

article, etc.), a test plan shall be subm1tted to NASA for approval and 

final signature authority. Test objectives shall be planned to verify 

compl1ance with the design and specif1ed requirements involved, including 

interfaces. 

4. For each ver1fication act1v1ty identified 1n the verification matrix, 

a detailed description of the activity including the verification 

configuration and its relat10nship to the flight configuration as well as 

the associated prerequisites, constraints, object1ves, procedures, 

relevant environmental conditions, pass/fail cr1teria, and analysis 

models, if applicable. Verification requirements shall be individually 

defined for each component or assembly consider1ng 1ts function, 

complexity, redundancy, design, and maintenance requirements. 

5. Acceptance tests ground-rules that assure Acceptance Test Procedures 

(ATPs) will demonstrate conformance to specificat10n requirements and 

provide quality control assurance against workmanship or material 

deficienc1es 

6. Ground-rules assur1ng qualificat10n test (or demonstration) hardware 

and software test articles shall be of the same configuration and 


CEV-T-01S Page 2 ofS





manufacturer, and be manufactured under the same production processes as 

the flight hardware and software, unless variances are approved formally 

by the contractors and NASA and adequately documented according to the 

test article supplier's established configuration management procedures. 

(a) Identlficatlon of selected software verification procedures and 

criteria across the I1fe cycle (e.g., peer review procedures, inspection 

procedures, re-inspection criteria, testlng procedures) . 

(b) Identification of selected software work products to be verified 

(e.g., peer reviews of requirements and test plans, peer 

reviews/inspections of critical code, testlng code against requirements 

and design) 

(c) Description of software verlfication environments that are to be 

established for the proJect (e.g., software testing environment, system 

testing environment, regression testing envlronment) . 

(d) Identiflcation of where the actual software verification records and 

analysis of the results will be documented (e.g., test records, peer 

review records, inspectl0n records), and where software verification 

corrective actl0n wll1 be documented. 

7. Qualification re-veriflcatlon analysis shall be requlred when any of 

the following occur. 

(a) Design or manufacturing process changes have been made which affect 

function or reliability. 

(b) Inspection, test, mission change, or other data indicate that a more 

severe environment or operating condltion exists than that to which the 

hardware/software was originally qualified. 

(c) Changes are made ln procurement source. 

(d) Changes are made ln specification, manufacturlng processes or 

procurement sources for fluids or other materials used in processing or 

operating the hardware/software 

(e) Software changes occur that affect requirements or fllght software 

capabilities. 

(f) Based on the results of the analyses, re-verification type and scope 

shall be subject to government approval. 

8. Retest for those activltles in the Acceptance Phase will be required 

when any of the following occur: 

(a) A previously mated and verifled interface has been de-mated 

(b) Modificatl0n, repair, replacement, or rework occurs after inspection 

or testing. 

(c) The article or material is subJect to drift or degradation during 

storage or handling. 

(d) Software changes occur that affect requirements or flight software 

capabllitles. 

Based on the results of the analyses, re-verification type and scope 

shall be subject to government approval. 

9. Functional compliance matrix that identifies all safety-critical 

functions and provides detailed descrlptl0ns of the associated 

verification methods(s) for each safety-critical function including the 

verification configuratl0n and its relationshlp to the flight 

configurat1on, as well as the associated prerequisites, constraints, 

objectlves, procedures, relevant environmental conditlons, pass/fail 

criteria, and analysis models, if applicable. 

10. A fault-tolerance dlagram or matrix that demonstrates the design and 

functional compllance of the CEV System wlth the fault-tolerance 

requirements decomposed through the system, module I subsystem, and 

component levels. 

11. Detalled time-correlated sequence of verification activities. 

12. Description, planned usage, and certification plans of the support 

equipment, software, faclilties, and tools necessary to execute the 

system verification actlvlties. 

13. Identification of the resources required to perform the required 

verification actlvities as well as resource owners and/or provlders. 

These resources (e.g., facilities, software, simulators) lnclude those 

that do not currently exist or existing resources that need to be 


CEV-T-OI5 Page 3 of5





upgraded. 

14. Certification plans for ground systems (reference SOW section 9). 

A Structural Verif1cation plan (SVP)shall be included as an additional 

volume of the Master Verif1cation plan. The SVP shall: 

1. Include a requirements applicability matrix that identifies which 

paragraphs in section 3.0 of CXP-70l35 are applicable to the system or 

hardware being delivered. 

2. Identify the the methods of structural ver1fication for each hardware 

element. 

3. Identify the methods of verificat10n for the structural and dynamic 

math models. 

4. Identify the proposed development, qualification and acceptance 

tests. 

The SVP shall 1nclude information for the following special tests: 

static/strength test plan and dynamic test plan. 

The following information shall be included in the static/strength test 

plan port10n of the SVP: 

1. Description and sketches of the structure. 

2. Identification of mater1als that are used, material allowables which 

will be used for strength analysis, and a description of manufacturing 

processes that are used. 

3. Comparison of the test article, including boundary conditions, to the 

flight article. Explain and provide justification as to why any 

differences are acceptable for stat1c testing. 

4. D1SCUSS the derivation of the static test loads and their comparison 

to the design/flight loads. 

5. Description and sketches of test setup, includ1ng load application 

techniques, load magnitudes and locations, instrumentation layout, and 

data recording system. 

6. Provide the pretest analysis for deflections, internal loads and 

stresses of the test configurat10n to predict critical deflections, and 

stress regions for test measurement locations. 

7. Planned correlation analys1s to verify the stat1c math model. 

8. Describe plans for vehicle handling and transportation. 

9. Description of special materials (i.e., composites, beryllium, and 

glass) and the correspond1ng measures which w1ll be taken to verify their 

strength and reliability. 

The following information shall be included 1n the dynamic test plan 

portion of the SVP: 

1. Description of test article in relat10n to the flight article. 

Include a summary of dummy masses that will not be included in test and 

components that will not be 1ncluded in test. 

2. Comparison of test and flight article mass properties. 

3. Descript10n and sketches of test setup includ1ng: 

(a) Description and sketches of the instrumentation location on the test 

article and test f1xture. 

(b) Description of and rationale for selection of excitation method, 

levels, and applicat10n points. 

4. Description of test article boundary conditions: 

(a) For the test article support structure, provide evidence that the 

support structure does not participate 1n the test frequency range. 

Otherwise, descr1be how a 'test verif1ed' model of the support structure 

w111 be obtained, as well as how it will be instrumented during testing. 

(b) For 'free-free' test, describe how the interface modes will be 

ver1fied. Describe the suspension system and predicted suspension modes. 

5. Summary of steps which will be taken to investigate linearity. 

6. Derivation of test specimen math model which will be used for 

correlation analys1s. 







7. Summary of pretest analysis and results including: 

(a) Identification of the target modes and the rationale for their 

selection. 

(b) Description and plots of the target mode shapes. 

(c) Assessment of the test fixture/test article interaction including 

work done in correlat1ng the test fixture itself. 

(d) comparison of the test article modes installed 1n the test fixture 

with the flight article modes. 

(e) Evaluation of the instrumentat10n locations including a comparison of 

the full model modes to the modes from the model reduced to the 

instrumentation locations (cross-orthogonality comparison) . 

8. Description of the planned correlation analysis. 

9. Describe plans for veh1cle handling and transportation. 

A Mechanical Systems verification Plan (MSVP) shall be included as an 

additional volume of the Master Verification Plan. The MSVP shall 

identify the inspect10n, analyses and tests that will be performed to 

meet the requ1rements of Sections 1 through 4 of NASA-STD-5017. 

134 FORMAT. Electronic format per Section J-2 2.3.2.1. 


subm1tted to NASA for approval Only volumes with content changes require 

a complete re-issue. If utilized, appendices with content changes 

require a complete re-issue. 







1 

3. 

6 

7. 



5. PAGE 1 

TITLE: Certification Plans 


TO document the plans for certifying the capability of fl~ght hardware 

and software Each cert~f~cation plan describes the work to be performed 

to create the certified capability baseline for the flight hardware or 

software it addresses. 




11. REMARKS: 

12. INTERRELATIONSHIP. Parent sow Paragraph(s): 10.2.1, 10.2.2. 

Referenced from sow Paragraphs: 2.7.2 



13.1 SCOPE. 

A Certification Plan prov~des the detailed description of flight hardware 

or software certificat~on requirements, work plans, source and product 

documentation, and data to be supplied for establishing an as-certified 

baseline and informing subsequent integrat~on, operation, and problem 

resolution activit~es. 


Cxp-72097 : Crew Exploration Vehicle Master Verification Plan 


A Certification Plan shall include the following: 

a. A descr~ption of the flight hardware or software covered by the plan. 

For assemblies, include a list of items integrated into the assembly 

which are individually certified. 

b. A description of the character~stics, capab~l~ties, and limits that 

will be addressed in the certification record(s) produced in accordance 

with the plan. 

c. A discussion, reference, and example of requirements and standards 

(including verificat~on matrix) that will be fully or partially verif~ed 

using the plan. 

d. A discuss~on, reference, and example of detailed requirements for 

tests, analyses, etc., that will be performed to verify the design's 

compliance with spec~fications, qualify the design for ~ts intended 

purpose, and create the certification records needed to baseline the 

certified capabilities and limits of the flight hardware or software. 

e. A discussion, reference t and example of accessible, verS1oncontrolled, 

engineering data or reports used to derive, define, or 

predict the detailed funct~ons, performance ranges, service (nonoperating, 

operating, and test) environments and operating behaviors of 

the design that will be certified by the plan. 

f. A discussion, reference, and example of test articles, support 







equipment, software, facilities, or models to be used. 

g. A discussion, reference, and example of safety and quality provisions 

applied in the plan. 

h. An undated Program Evaluation and Review Technique (PERT) schedule 

for implementing the plan identifying the critical path and any 

prerequisites, constraints or dependencies in the plan. 

13.4 FORMAT: Electronic format per Section J -2 2.3 2.1. 

13 5 MAINTENANCE: Changes shall be incorporated by change page or complete 

reissue. 







1. 

3. 

6 

PROGRAM' CEV 2. 

DATA TYPE. 1/3 (Type 1 for Spacecraft, 4. 

Module and Subsystem, Type 3 for 5. 

Components) 

TITLE: Certification Data Package 

DRDNO.: 

DATE REVISED: 

PAGE: 

CEV-T-017 

May 2009 

1 

7 DESCRIPTIONIUSE 

To provide the ev~dence and audit trail required by NASA to establish an 

as-certified baseline for the CEV and it's components, and to confirm 

that verification act~vities indicate all requirements were met. 




11. REMARKS: 

Certification data are produced in accordance w~th the certification 

plans to create a record of qualification and integration activities that 

together create a certified capability description. 

12. INTERRELATIONSHIP. Parent sow Paragraph(s)' 10.2.1, 10.2.2. 

Referenced from sow Paragraph(s): 2.6, 2.6.1, 6.1.5, 6.2.5, 6.4.5, 6.5.4, 

10.3.1 

Related DRD(s). CEV-T-016, CEV-T-018 


13.1 SCOPE: 

The Certification Data Package contains the elements of documentation 

required to establish that all requirements have been met by the 

integrated systems, hardware, and/or software. 



A Certification Data Package shall contain the following: 

1. Current version of the spacecraft system, module, subsystem, or 

component requ~rements document for the integrated system, hardware, or 

software that is be~ng certified. 

2. Current version of the certification plan for the spacecraft system, 

module, subsystem, or component. 

3. Verificat~on compliance report I including the verification matrix 

mapped to all verif~cation data. This report shall include: 

(a) Qualificat~on report, includ~ng test, analys~s, inspection, and 

demonstration reports. 

(b) Acceptance report for the qualification unit or the first flight 

unit. 

(c) Summary of and references to Failure Mode and Effects Analysis 

(FMEA) , hazard analysis and controls reports, and Critical Items List 

(CIL) rationale for retent~on, including residual risk ~nformation. 

(d) List of approved operational controls. 

(e) Ver~f~cation track~ng log. 







4. A certification data summary, whlch contains the following· 

(a) Englneering drawings 

(b) Operational informatlon and relevant documentation 

(c) Materials information 

(d) Electrical informatlon 

(e) Electromagnetlc compatibility informatlon 

(f) EEE parts informatlon 

(g) Natural and induced environment reports 

(h) Software/flrmware Version Descriptlon Document (VDD) 

5. Manufacturing and acceptance testing standards, procedures and 

processes now qualified 

6. Wa1vers, deviations, non-conformance reports and problem closure 

reports 

7. Limits on run time, ldle time, age, cycle, or storage shelf life 


13.5 MAINTENANCE: Contractor-proposed changes to this document shall be 

submitted to NASA for approval. Changes to the Certification Data 

Package shall be made with a Certification Approval Request detailing the 

portions of the current version that is ammended, revised, or replaced 

with new certlflcation data. 







1. 

3 

PROGRAM: CEV 

DATA TYPE: 1 

6. TITLE: Certification Approval Request 

2 DRDNO.: 

4. DATE REVISED 

5 PAGE: 

CEV-T-018 

May 2009 

1 

7 DESCRIPTIONIUSE. 

A request for NASA approval of the certification records that establish, 

amend, revise, or replace the cert~fied capability baseline for flight 

hardware and software. 

8. DISTRIBUTION' As determined by the Contract~ng Officer 

9. INITIAL SUBMISSION' Per Data Requirements Matnx 


11 REMARKS: 

A Certif1cation Approval Request (CAR) 1S delivered in support of design 

certification m1lestone. 

12. INTERRELATIONSHIP Parent sow Paragraph(s): 10.2.1, 10.2.2. 



13.1 SCOPE: 

A CAR may cover one or more flight hardware and software items at the 

levels of assembly covered by the certified capability baseline 

description and the supporting certification records delivered in 

accordance with CEV-T-017 



A CAR provides a request for NASA approval of the certified capability 

baseline - the detailed description and recognized definition of 

equipment capab1l1ties, limits, and constraints for the purposes of 

establishing flight rules/crew procedures, documenting and resolving nonconformances, 

and susta1ning equipment design. Qualification marg1ns are 

not be intruded upon by production hardware in service and should not be 

reflected by the certified basel1ne.capability. 

A CAR shall 1nclude: 

1. A definition of the flight hardware and software covered by the 

request, including 

a. Supplier 

b. Part numbers 

c. Drawing references 

d. Used-on location(s) (next higher assemblies) 

2. Reference to a detailed descr1pt10n of the performance capabilities, 

behaviors, limits and constra1nts being certified, including 

a. Operational signatures. 

b. Order of operations requirements. 

c. Limits on operating time, cycles, age or shelf life. 

Capabilities, llm1ts, behaviors, etc. shall be expressed in terms 

of measurable, observable indications ava1lable to operators and data 

evaluators. 

3. A list of the Certification Data Packages (CEV-T-017) supporting the 





CAR 

4. Reference to the Certlfication Plan(s) implemented for this 

certification 

13.4 FORMAT. Electronic format per Section J-2 2.3.2.1. 



13.5 MAINTENANCE: Changes shall be incorporated by submittal of a "delta" 

certification approval request in accordance with thls DRD. 






1. 

3 

PROGRAM: CEV 

DATA TYPE. 2 


2. 

4. 

5. 

DRDNO.: 

DATE REVISED: 

PAGE' 

CEV-T-019 

May 2009 

1 

6. TITLE: Materials and Processes Selection, Implementation, and Control 

plan 


Each organization respons~ble for the design and fabr~cation of 

spacecraft flight hardware shall provide a Materials and Processes 

Selection, Control, and Implementation plan. This plan shall document the 

degree of conformance and method of implementation for each requirement 

in NASA-STD-(I)-6016 Standard Materials And Processes Requirements For 

spacecraft, identifying appl~cable specifications used to comply with the 

requirement. It shall also describe the methods used to control 

compliance with these requirements by subcontractors and vendors. 

The Materials and Processes Selection, Control, and Implementation Plan, 

upon approval by the procuring activity shall become the Materials and 

Processes ~mplementation document used for verification. 

8. DISTRIBUTION: As determined by the Contractmg Officer. 


10. SUBMISSION FREQUENCY: Per Data Requuements Matrix 

11. REMARKS: 

12. INTERRELATIONSHIP: Parent sow Paragraph(s): 2.1.9.1. 

Related DRD(s): CEV-S-001, CEV-T-020, CEV-T-021, CEV-T-022, CEV-T-023 


13.1 SCOPE. 

The Materials and Processes Selection, Implementat~on, and Control Plan 

defines the objectives, procedures, log~c, reporting, and management 

controls for materials and processes selection, implementation, 

verification, and control for use in the product~on of space flight 

hardware, support hardware, and associated ground support equipment. In 

addition, this plan shall be used to tailor the requirements identified 

in NASA-STD-(I)-6016. 


NASA-STD-(I)-6016: Standard Mater~als 

Spacecraft 

And Processes Requirements For 


The plan shall describe the hardware developer's act~v~ties involved in 

the identificat~on, evaluation, documentation, and reporting of materials 

and processes usage in space fl~ght hardware, support hardware and ground 

support equipment. The necessary interfaces with procuring activity in 

the operation of this plan shall be defined. The method for materials 

control and verification of subcontractors and vendors shall be included 

in the hardware developer's plan. As a minimum and as applicable, the 

plan shall address the following: 

1. Conformance - The plan shall address each applicable paragraph of 

NASA-STD-(I)-6016 and describe the method of implementation and 

degree of conformance for each applicable requirement. If 

tailoring of the requirements is planned or necessary, the 







alternate approaches to NASA-STD-(I)-6016 may be submitted in this 

plan, which meet or exceed the stated requirements. This tailoring 

approach will allow for NASA approval of alternate requirements. 

2. Hardware Developer's Organization - Authority shall be assigned to 

an individual or group who shall be responsible for review and 

approval of all M&P specified prior to release of engineering 

documentatl.on. 

3. Materials and Processes Identification - Identification and 

documentation of the M&P used, both in the original design and in 

any changes shall be contained in the Material & Process 

Identification and Usage List DRD (CEV-T-022). 

4. Testing - Logic, procedures and data documentation for any 

proposed test program to support the certl.fication of 

materials/processes for use in spaceflight hardware shall require 

prior NASA approval. 

5. Material Usage Agreement (MUA) Procedures - Logic, procedures and 

documentatl.on l.nvolved l.n documentl.ng and approving 

materials/processes as indicated in NASA-STD-(I)-6016 shall be 

defined, including those that do not meet the established 

requl.rements, but are proposed for use due to lack of replacement 

materials/processes or other considerations. MUA shall be 

contained in the Materials Usage Agreement DRD (CEV-T-020) 

6. Material Design Properties - The plan shall contain the philosophy 

describing how material properties will be determined, and if 

those properties do not exist, how the material properties will be 

developed including, but not limited to the statistical approaches 

to be employed. 

7. Process Controls - The plan shall identify all process 

specificatl.ons used to l.mplement specl.fic requirements in NASA 

STD-(I)-6016. All materials processes used in manufacturing shall 

be documented in process specificatl.ons and all applicable process 

specifications shall be identified on the engineering drawing. 

Each processing step l.n the process specification shall be 

identified in a level of detail that ensures the process is 

repeatable. 

13.4 FORMAT. Electronic format per Sectl.on J-2 2.3.2.1. For each paragraph 

in sections 4 and 5 of NASA-STD-(I)-6016, the plan shall state the 

requirement from NASA-STD-(I)-6016, identify the degree of conformance 

under the subheading "Degree of Conformance," and identify the method of 

implementatl.on under the subheading "Method of Implementation." 



required. 







1.1. 

3 

PROGRAM. CEV 

DATA TYPE: 1 (Category I and II MUM) 

2 (Category III MUAs) 

6. TITLE: Materials Usage Agreements (MUA) 

2. DRDNO.: CEV-T-020 

4. DATE REVISED: May 2009 

5. PAGE. 1 


MUAs shall be submitted for all mater~als and processes that are 

technically acceptable but do not meet the technical requirements of 

NASA-STD-(I)-6016, as ~mplemented by the approved Materials and Processes 

Selection, Implementation, and Control Plan (DRD CEV-T-019) . [The use of 

materials and processes that do not comply with the technical 

requirements of th~s standard may be technically acceptable if hardware 

rel~ab~lity and vehicle safety are not affected 1 


9 INITIAL SUBMISSION Per Data Requirements Matrix 


11 REMARKS. 

The DRD type ~s dependent on the nature of the MUA being submitted. For 

Category I and II MUAs the type shall be 1. For Category III MUAs the 

type shall be 2. 

12. INTERRELATIONSIDP. Parent sow Paragraph (s): 2.8.4 



13.1 SCOPE: 

MUAs shall be submitted as described below. 

Category I MUAs - Category I MUAs are those that involve 

material/processes usage that could affect the safety of the mission, 

crew, or vehicle or affect the mission success, but must be used for 

funct~onal reasons. Approval by the respons~ble NASA Materials and 

Processes organization and the NASA Program/Project Office shall be 

required. 

Category II MUAs - Category II MUAs are those that involve 

material/processes usage that fa~ls a screening of Material and Processes 

requirements and is not cons~dered a hazard in ~ts use application but 

for which no Category III rationale code exists. Approval by the 

responsible NASA Materials and Processes organization shall be required. 

Category III MUAs - Category III MUAs are those that involve materials or 

processes that have not been shown to meet these requirements but have an 

approved rationale code listed in Append~x B of NASA-STD-(I)-6016. They 

are evaluated and determined to be acceptable at the configuration/part 

level. Category III MUAs shall be reported in the Materials 

Identification and Usage List (MIUL, DRD CEV-T-022) system or electronic 

data system utilizing the approved rationale codes in Appendix B. A key 

may be provided to correlate contractor Category III MUA database codes 

to the codes in Appendix B No MUA form is submitted. 

MUAs shall be revised and resubmitted whenever design modifications 

affect the part numbers ~dentified on the MUA or the MUA rationale. 








- NASA-STD-(I)-6016: Standard Materials And Processes Requirements For 

Spacecraft (and assoc~ated Children documents as specified in 

Attachment J-3, Applicable, Guidance, and Informational Documents 

List) 

- MSFC-STD-3029: Guidelines for the Selection of Metallic Materials for 

Stress Corrosion Cracking Resistance in Sodium Chloride Environments 

NASA-STD-(I)-5019: Fracture Control Requirements For Spaceflight 

Hardware 


The MUA package shall include all technical information required to 

justify the application. MUAs for stress corrosion shall include a 

Stress Corrosion Crack~ng Evaluation Form per MSFC-STD-3029 (see NASA 

STD-(I)-6016) and a stress analysis. 

13 4 FORMAT. Electronic format per Sect~on J -2 2.3.2.1 A sample MUA form is 

provided in NASA-STD-(I)-6016; however, contractor format is acceptable. 

The complete MUA package shall be provided in Adobe PDF searchable 

format; the MUA data shall also be provided in a format that is 

compatible with the NASA Materials and Processes Technical Information 

System (MAPTIS) database. The MUA data shall be delivered to ICE in 

accordance w~th Append~x 2. 

13.5 MAINTENANCE· Contractor updates to the Category I and Category II MUAs 

shall be submitted to NASA for approval. Complete re-issue of the MUA is 

required 







1. 

3. 

PROGRAM: CEV 

DATA TYPE: 2 

6. TITLE. Contaminatl.On Control plan (CCP) 

2. 

4 

5 

DRDNO.: 

DATE REVISED: 

PAGE: 

CEV-T-021 

May 2009 

1 


The contaminat10n control plan defines implementation measures to control 

contaminat1on of flight hardware/GSE and fluid systems during 

manufacturing, assembly, test, transportation, launch site processing, 

during the mission and post-flight refurbishment. 

8. DISTRIBUTION. As determined by the Contracting Officer. 



11. REMARKS. 

12. INTERRELATIONSHIP: Parent sow Paragraph(s): 2.8, 2.8.4. 

Related DRD(s): CEV-S-001, CEV-T-019 


131 SCOPE: 

The contamination control plan shall be generated in accordance with the 

CxP 70145 using the guidelines of ASTM E1548, Standard Practice for 

Preparation of Aerospace Contam1nation Control Plans (as specified by 

NASA-STD-(I)-6016) and shall include: 

a. A Foreign Object Debr1s (FaD) control plan to prevent damage to 

flight hardware/GSE and injury to the flight and ground crews by FaD 

during manufacture, assembly, test, transportation, launch site 

processing, operation, repair, modification, refurbishment and 

maintenance. The FaD prevention program shall conform to NAS 412, Foreign 

Object Damage/ Foreign Object Debris (FaD) Prevention, as specified by 

NASA-STD-(I)-6016. 

b Definition of cleanliness level acceptance limits and verif1cation 

methods for fluid systems, for general CEV fl1ght hardware and GSE, 

internal and external surfaces, and airborne particulate. The plan shall 

also contain a 11st identifying all system fluids, together with the 

fluid specificat10ns (for procurement or custom mixing) and the required 

cleanliness levels for the fluid system. Gases are included under fluid 

systems. 

c. The contamination control plan shall also comply with the requirements 

in CxP 70145. Although it is the responsibility of the contractor to 

identify requ1red hardware cleanl1ness levels, cleanl1ness level 

definitions shall be consistent with CxP 70145 (i.e., visual and 

precision cleanliness levels shall be selected from the levels defined in 

CxP 70145). 


NASA-STD-(I)-6016: Standard Materials And Processes Requirements For 

Spacecraft 







ASTM E1548, standard Practice for Preparation of Aerospace 

Contamination Control Plans (Informational) 

NAS 412: Foreign Object Damage/ Foreign Object Debris (FOD)Prevention 

CxP 70145, Constellation Program Contamination Control Requirements 


The CCP shall include: 

1. The FOD control plan. 

The FOD Control plan shall address the following elements: 

(a) Identification of probable FOD sources 

(b) Early design cons~derations for FOD prevention, resistance to damage, 

foreign object entrapment, etc 

(c) Manufacturing plann~ng for minimizing FOD generation and cleaning up 

whatever FOD is generated. 

(d) FOD control methods. 

(e) FOD Awareness and Prevent~on Training. 

(f) Metrics - Measuring techniques for analysis, trending, and feedback. 

(g) Incident investigation/reporting, 'lessons learned.' 

(h) Awareness/Employee Feedback. 

(i) Updates to plan based on results of Metric and lessons learned. 

2. Cleanliness level acceptance lim~ts definition and verification 

methods. 

The document shall define cleanliness level acceptance limits and 

ver~fication methods for fluid systems, for general CEV fight hardware 

and GSE, internal and external surfaces, and airborne particulate. The 

document shall also include a l~st identifying all system fluids, 

together with the fluid specifications (for procurement or custom mixing) 

and the required cleanliness levels for the flu~d system. Gases are 

~ncluded under flu~d systems. Update document as required based on any 

updated limits, verification methods, flight hardware changes, GSE 

changes, and environmental changes. 




required 







1. PROGRAM: CEV 

2 DRDNO.: CEV-T-022 

3. DATA TYPE: 2 

4 DATE REVISED: May 2009 

5. PAGE. 1 

6. TITLE. Materials IdentLfication and Usage List (MIUL) 


The MIUL lS an electronic searchable parts list or separate electronic 

searchable materials identLflcation and usage list. The MIUL identifies 

all Material and Processes (M&P) usages contalned in the end item, 

excluding piece part electronics, for evaluation of the acceptability of 

M&P selected and utillzed. 


9 INITIAL SUBMISSION' Per Data Requuements Matrix 


11 REMARKS. 

12. INTERRELATIONSmp Parent sow Paragraph (s): 2.1. 9.1. 



13.1 SCOPE: 

Materials and processes usage shall be documented in an electronic 

searchable parts list or separate electronic searchable Materials 

Identification and Usage List (MIUL). The procedures and formats for 

documentation of materials and processes usage will depend upon specific 

hardware but shall cover the final design. The system used shall be an 

integral part of the engineer Lng configuration control/release system. A 

copy of the stored data shall be provided to NASA in a form compatible 

with the Materials and Processes Technical Information System (MAPTIS). 


NASA-STD-(I)-6016: Standard Materials And Processes Requirements For 

Spacecraft 


The parts list or MIUL shall identify the following applicable 

information: 

- Detail drawing and dash number 

- Next assembly and dash number 

- Change letter designation 

- Drawing source (contractor or vendor) 

- Mater~al form 

- Material manufacturer 

- Material manufacturer's deslgnation 

- Material specif1cation 

- Process specification 

- Environment 

- Weight 

- Material code 

- MAPTIS Rating 

- Standard/commercial part number 





- Contractor 

- System 

- Subsystem 

- Maximum temperature 

- Minimum temperature 

- Fluid type 

- Surface Area 

- Associate contractor number 

- Project 

- Document title 

- Criticality 

- Line number 

- Overall evaluation 

- Overall configurat~on test 

- Maximum pressure 

- Minimum pressure 

- Test MUA Document 

- Cure codes 



13.4 FORMAT: Electronic format per Section J-2 2.3.2.1. However, Contractor 

format for electronic subm~ttal of MIUL data shall be compatible with the 

NASA Materials and Processes Technical Information System (MAPTIS) 

database. MIUL data shall be delivered to ICE ~n accordance with 

Appendix 2. 

13 5 MAINTENANCE: Contractor updates to the MIUL shall be submitted to NASA 

for approval Complete re-issue of the document is not required. 







1. 

3. 

6. 

7. 


DATA TYPE. 2 4. DATE REVISED' May 2009 

5 PAGE. 1 

TITLE: Nondestructive Evaluation Plan 


The Nondestructive Evaluation (NDE) plan shall address the NDE 

requirements necessary to assure the health and integrity of the CEV 

System includlng Flight and GSE hardware throughout its life cycle. This 

plan shall identify all NDE and nondestructive testing procedures and 

speciflcations employed in the inspection of materials. 

8. DISTRIBUTION. As determined by the Contractmg Officer. 



11 REMARKS' 

12 INTERRELATIONSHIP' Parent sow Paragraph (s): 2.1.9.1. 

Related DRD(s): CEV-T-019, CEV-T-069, CEV-T-070 


13.1 SCOPE: 

The NDE plan shall address the process for establlshment, implementation, 

execution, and control of NDE. The plan shall meet the intent of MIL 

HDBK-6870A, Inspection Program Requirements, Nondestructive for Aircraft 

and Mlssile Materlals and Parts and NASA-STD-5009, Nondestructive 

Evaluation Requirements for Fracture Control Programs as specified by 

NASA-STD-(I)-6016. 


- NASA-STD-(I)-6016: Standard Materlals And Processes Requlrements For 

Spacecraft 

- MIL-HDBK-6870A: Inspection Program Requirements Nondestructive for 

Aircraft and Misslle Materials and Parts 

- NASA-STD-5009: Nondestructive Evaluation Requirements for Fracture 

control Programs 

- NASA-STD-(I)-5019: Fracture Control Requirements For Spaceflight 

Hardware 

- NAS 410: Certificatlon and Qualification of Nondestructive Test 

Personnel 


13.3.1 NDE Specifications and Standards: The NDE plan shall address the 

selection and the order of precedence of appllcable Government, Industry 

and prime contractor NDE specifications and standards and how the 

requirements contained therein are implemented through internal 

procedures and how-to documents. The oversight of subcontractor 

implementatl0n and flow down of the NDE requirements shall also be 

addressed. The plan shall address commonly used aerospace lndustry NDE 

methods lncluding, but not limlted to, dye penetrant, radiographic (film 

radiography, digltal radiography, computed tomography), ultrasonic, 

neutron radiography, magnetic partlcle, eddy current, infrared 

thermography, and visual lnspection. The plan shall address how all NDE 





specifications and standards for the Constellation program will be 

approved by the appropriate government authority. 



13.3 2 NDE Requirements During Hardware Deslgn: The NDE plan shall 

address how the processes are implemented to ensure that all deslgns are 

reviewed to establish NDE inspection requirements and to ensure that the 

parts are inspectable. The plan shall address how the areas or zones of 

the part to be inspected are identified on the drawing. The plan shall 

address how the operations and maintenance NDE requirements will be 

integrated in the design of the hardware. 

13.3.3 Part Classlfication: The plan shall address appropriate flight 

hardware and GSE part classification In accordance with MIL-HDBK-6870A 

and NASA-STD-(I)-5019. 

13.3.4 NDE Sensitivlty Levels: NDE sensitivlty levels shall be classified 

as Standard NDE, Special NDE, Custom NDE and Visual Inspection in the NDE 

plan. The plan shall address minimum detectable flaw size for Standard 

NDE for each materlal group of Constellatlon hardware in compliance with 

NASA-STD-5009 where appllcable. The plan shall address procedures for 

defining NDE acceptance criteria for each of the sensitivity levels and 

identify organizatlons and their responsibillties in establishing NDE 

acceptance criteria, NDE drawing call outs, NDE Operations and 

Maintenance criteria Note: Custom sensitivity level refers to an NDE 

sensitivity level that is not covered under the other three NDE 

sensitivity levels and lS applicable to non-fracture critical parts 

13.3.5 NDE Acceptance Crlterla: The plan shall address how NDE acceptance 

criteria are determined and implemented for each sensitivity level. For 

flight hardware, the plan shall require rejection of any cracklike flaw 

irrespective of the sensltlvity level of the inspection. The plan shall 

address how significant flaw indications, irrespective of the acceptance 

criteria, will be dispositioned. 

13.3.6 NDE During Manufacturing: The plan shall address establishment of 

mlnimum NDE acceptance requlrements in terms of NDE sensitivity level, 

methods of inspectlon (dye penetrant, ultrasonic etc.), sampling 

frequency, NDE inspection coverage (e.g. 100% surface area or selected 

area) for manufactured hardware as grouped by classification of the part, 

material type and form. The NDE plan shall address how NDE is sequenced 

such that inspection rellablllty is optimized by performing NDE before 

manufacturing processes that may significantly reduce flaw detectlon 

capabllity. The requirements for etching of metal parts prior to 

penetrant inspectlon shall be specifically addressed in the plan. 

13.3.7 NDE Material Compatlblllty: The plan shall address compatibillty 

of NDE materials and processes with the Constellation hardware especially 

liquid oxygen systems 

13.3.8 Fracture critlcal Parts: The Plan shall address how the listing of 

all Fracture Critical parts, created accordlng to the Fracture Control 

plan, will be integrated with NDE requirements. The plan shall address 

Special NDE and Standard NDE methods in accordance with NASA-STD-5009. 

13.3.9 NDE During Operations and Maintenance: The NDE plan shall address 

the NDE requirements necessary to assure the health and lntegrity of the 

Constellation hardware throughout ltS life cycle. The NDE plan shall 

address NDE requlrements during operations and maintenance of those parts 

that are susceptible to damage such as impact, corrosion, material 

degradation and wear, etc. The NDE plan shall address NDE requirements 

for inspecting repaired parts. The plan shall address the NDE procedures 

and physical standards required to perform the operatlons and maintenance 

NDE inspectlons. 







13.3.10 NDE Reporting and Record 

the NDE nonconformance reporting 

traceability. 

Retention: The NDE plan shall describe 

system, record retention and 

13.3.11 Process Audit: The plan shall address periodic auditing of NDE 

processes at prime contractor, vendors and subcontractors to verify 

compliance with the NDE requirements established in the plan. 

13.3.12 Personnel Tra1ning: The NDE plan shall identify formal training 

and certification requirements for NDE Inspection in accordance with NAS 

410. 

13 4 FORMAT· Electronic format per Section J-2 2 3.2.1. 



required. 


CEV -T -023 Page 3 of3





1 PROGRAM: CEV 


3. DATA TYPE' 1 


5. PAGE: 1 

6. TITLE: CEV Electromagnetic Compatibility Control and verification 

Document 

7. DESCRlPTIONIUSE: 

To define the plans, processes, procedures and test data the CEV System 

Contractor will use to ensure that the design, construction, and 

verification of CEV System wlil result in the delivery of a System which 

satisfies the specified Electromagnetic Compatibility (EMC) requirements. 

8. DISTRIBUTION. As determined by the Contractlng Officer. 

9. INITIAL SUBMISSION. Per Data Requuements Matrix 


11. REMARKS: 

This DRD lncorporates Electromagnetic Environmental Effects (EME) 

information which must be addressed to design, develop, assemble and 

deliver a CEV which is electromagnetically compatible. 

NASA will use the information in thls DRD to integrate other 

Constellation space elements to the CEV. 


ANSI/ESD S20.20-2007: ESD Association Standard for the Development of 

an Electrostatic Discharge Control Program for Protection of Electrical 

and Electronic Parts, Assemblies and Equlpment (Excluding Electrically 

Initiated Explosive Devices) 

RTCA/DO-160D: Environmental Condltions and Test Procedures for 

Airborne Equlpment (Section 22: Lightning Induced Transient 

Susceptibility and Section 23:Lightning Direct Effects) 

SAE-ARP-54l2: Aircraft Lightning Environment 

SAE-ARP-54l3: Certification of Alrcraft Electrical/Electronic Systems 

for the Indirect Effects of Lightnlng 

SAE-ARP-54l4 Aircraft Lightning Zoning 

SAE-ARP-54l5: Users Manual for Certification of Aircraft 

Electrical/Electronlc Systems for the Indirect Effects of Lightning 

SAE-ARP-54l6: Alrcraft Lightning Test Methods 

SAE-ARP-5577: Aircraft Llghtning Direct Effects Certification 

SSP 30240: Space Statlon Grounding Requirements 

SSP 30242: Space Station Cable/Wlre Design and Control Requirements 

for Electromagnetic Compatibillty 

12. INTERRELATIONSmp. Parent sow Paragraph(s). 2.8.5. 


13.1 SCOPE: 

The CEV Electromagnetic Compatlbillty Control and verification Document 

includes all of the planning and effort necessary to for the Contractor 

to control the generation and absorption of electromagnetic energy in 

every part of the CEV for the complete life cycle of its components. The 







Contractor is expected to use this DRD as a management document to the 

meet the overall EMC requ~rement to be electromagnetically compatible. 


MIL-STD-l576: Electro Explos~ve Subsystem Safety Requirements and Test 

Methods for Space Systems 

MIL-STD-46lE: Requirements for the Control of Electromagnetic 

Interference (EMI) Characteristics of Subsystems and Equipment 

MIL-STD-464A: Electromagnetic Environmental Effects Requirements for 

Systems 

ML0303-00l4: Electrical Wire Harnesses and Coaxial Cables, Installation 

Requ~rements for Electromagnetic Compat~b~lity 

NASA-STD-4003. Electrical Bonding for NASA Launch Vehicles, Spacecraft, 

Payloads, and Flight Equipment 


The CEV Electromagnet~c Compatibility Control and Verification Document 

shall consist of 7 Sect10ns: 

SECTION 1: The Electromagnetic Env~ronmental 

Effects Control plan 

SCOPE: 

The Electromagnetic Environmental Effects Control plan defines the 

approach for implementation of an electromagnetic compatibility (EMC) 

control program. It describes the Contractor control program organization 

and responsibilit~es. It also includes interpretation of EMC requirements 

and a descr1ption of additional EMC requ1rements levied by the Contractor 

on subsystems and equipment to meet CEV Project EMC requirements. 

Additionally, this section addresses specific design measures to meet EMC 

requirements as well as addressing EMC design, test, and analysis 

requJ.rements. 

CONTENTS: 

The Electromagnetic Env1ronmental Effects Control Plan shall document the 

Contractor's approach for implementation of an EMC control program for 

the CEV System. General and detailed requirements for systems EMC are 

contained in MIL-STD-464A. The detailed plan shall include. 

(a) Internal organization and responsibility 

(b) System compatibility 

(c) Subsystem compatib11~ty 

(d) Subsystem and equipment requirements 

(e) Electromagnetic interference safety margins for critical equipment. 

Critical equ1pment is defined as that equipment of which the loss of 

normal or expected functional~ty would result in loss of life or vehicle. 

(f) Interference and susceptibility control 

(g) Degradation criteria 

(h) Subsystem interconnection and routing 

(i) Electrical power and electrical interface, transients, and ripple 

(j) Power frequency leakage current 

(k) Bonding 

(1) Grounding and Isolation 

(m) Static electricity, both ESD and veh1cle charging 

(n) Personnel hazards 

(0) Pyrotechnics and br1dge W1re actuated devices (BWAD's) 

(p) Spacecraft charging controls 

(q) EMC analys1s methods and techn~ques 

(r) EMC verification plann1ng and methodology (ver1fication flow to lower 

level specifications) 

The plan shall include des1gn and test approach that will ensure 

compatibility within the CEV System as well as with all external 

interfaces. This includes modif1cation of equipment level requirements to 

be compat1ble with special element requirements and the EMC sections of 





applicable Interface Control Documents (lCD's). 



SECTION 2: Electromagnetic Environmental Effects Requirements for Systems 

SCOPE: 

This section establ~shes the Contractor's requirements for 

Electromagnetic Environmental Effects Requirements for Systems. 

CONTENTS: 

The requirements and considerations of MIL-STD-464A shall be tailored by 

the contractor for use on the CEV Project to meet the contractual EMC 

Requirements. The Contractor's tailored version shall include the 

following sections: 

(a) Contents 

(b) Scope 

(c) Applicable Documents 

(d) Definitions 

(e) General Requirements 

(f) Detailed Requirements 

(g) Notes 

(h) Tables 

(i) Figures 

SECTION 3: Cable/Wire Design & Control Requirements Section for 

Electromagnetic Compatibility (EMC) 

SCOPE: 

The Cable/Wire Design and Control Requirements Section for 

Electromagnet~c Compatibility (EMC) shall provide uniform specifications 

and methodologies for cabling and wiring requirements to ensure the 

electromagnetic compatibil~ty of subsystems, equipment, and the overall 

CEV Project. These requirements minimize the effects of electric and 

magnetic field coupl~ng between the wiring and circuits associated with 

the wiring. 

CONTENTS: 

The Cable/Wire Design and Control Requirements section for 

Electromagnetic Compatibility (EMC) sect~on shall provide detailed 

information regarding cable and W1re design character1stics necessary to 

ensure electromagnetic compatibility. The tailoring of ML0303-0014, 

'Electrical Wire Harnesses and Coaxial Cables, Installation Requirements 

for Electromagnetic Compatibility', SSP 30242 'Space Station Cable/Wire 

Design and Control Requirements for Electromagnetic Compatibility', and 

SSP 30240 'Space Station Grounding Requ~rements' will assist ~n 

establishing the Contractor's requirement to meet the overall EMC 

requirements for CEV. These tailored requirements shall be documented in 

this sect~on and shall also address as a minimum, the following: 

(a) Circuit Classification 

1. Operating Frequency and/or Rise and Fall Times 

2. Loop and/or Circuit Impedance 

3. Loop and/or Circuit Voltage and Current 

4. Loop and/or Circuit Suscept1bility 

5. Signal and Wire Type 

6. An installat~on specification that complies with e~ther ML0303- 

0014, or a NASA-accepted alternative that will achieve quality consistent 

with ML0303-0014, Electr~cal Wire Harnesses and Coaxial Cables, 

Installation Requirements for Electromagnetic Compatibility. 

(b) Classification and Wiring Procedure 

(c) Determinat~on of Interface Wir~ng Requirements 

(d) Signal and Wire Types 

(e) Shield Termination 

(f) Implementation of Signal/Circuit Type Cod~ng 

(g) Implementation of Harness Installation 





1. Physical Separation Requirements 

2. Shield Termination 

3. Breakouts 

4. pyrotechnic Devices. 

(h) Clrcuit Grounding 



SECTION 4· Electromagnetic Environmental Effects Design Analysis Reports 

SCOPE 

This section of the CEV Electromagnetic Compatlbility Control and 

Verification Document defines the content that will be dellvered in the 

Electromangetic Environmental Effects Design Analysis Reports that will 

be delivered In accordance with other DRDs for the delivery of CEV 

evaluation, verification and certification documents. The Electromagnetic 

Environmental Effects (E3) Design Analysis Reports describes the design, 

analyses, tests and results of efforts to ensure individual equipment 

meets the E3 requirements and the entire system lS compatible. 

CONTENTS: 

The Electromagnetic Environmental Effects (E3) Design Analysls Reports 

shall describe the approach taken to ensure E3 requirements are met in 

accordance with Electromagnetic Environmental Effects (E3) Control plan 

and the results of that effort. The reports are delivered in accordance 

with requlrements to provide evaluation, verification and certification 

data for developed and integrated hardware. Reports shall include the 

following informatlonal items (where appllcable) for hardware: 

(a) Electrical bonding 

(b) Circuit grounding and lsolation 

(c) Cable design and routlng 

(d) Connector separation and shield termlnation 

(e) Frequency management 

(f) Emission and susceptlblilty control 

(g) Crltical circuit identiflcation 

(h) Lightning protectlon 

(i) Electrostatlc dlscharge protection 

(j) Analyses results 

(k) Test results 

SECTION 5: Requirements for the control of Electromagnetic Interference 

(EMI) characteristics of subsystems and equipment intended for use by the 

CEV ProJect 

SCOPE: 

This section establishes interface and associated verification 

requirements for the control of electromagnetic lnterference (emissions 

and susceptibility) characteristics of hardware procured for use by the 

CEV Project. Such hardware may be used independently or as an lntegral 

part of other hardware. This section is directly applicable to items such 

as electronlc enclosures and electromechanical systems and electrical 

interconnections composed of discrete wiring harness between enclosures. 

CONTENTS: 

MIL-STD-461E shall be tailored to descrlbe the interface and associated 

verification requirements for the control of electromagnetic interference 

(emissions and susceptibility) characteristics of electrical, electronic, 

and electromechanlcal equipment and subsystems designed or procured for 

use by the CEV Project. As a mlnimum the following sections of MIL-STD- 

461E shall be addressed: 

(a) Scope 

(b) Applicable Documents 

(c) Definitions 

(d) General Requirements 

(e) Detailed Requlrements 







SECTION 6: Electrostatic Discharge (ESD) Control Plan 

SCOPE: 

The Electrostat~c D~scharge Control plan defines the tasks, activities 

and procedures necessary to protect CEV Project ESD sensitive items at or 

above the ESD sensitivity levels defined for the CEV Project. The Plan 

outlines strategies for meeting administrative and technical 

requirements, and shall ~nclude information about organizational 

respons~bil~t~es, methods for measuring ESD control effectiveness, and 

the approach to be used for utilizat~on of CEV Project data and 

documentation. The plan shall address training, compliance verification, 

facility grounding & bond~ng, personnel grounding, protected areas, 

packaging, marking, and handling. 

CONTENTS' 

The Electrostatic Discharge Control plan establishes methods and 

procedures to be ~mplemented for system, subsystem, and component 

protection from the deleterious effects of ESD, and shall address the 

follow1ng areas as a m1nimum: 

(a) Administrative Requirements 

1 ESD Control Program plan 

(a) Scope 

(b) Tasks, Activities and Procedures Necessary for Protection of 

ESD Sensitive Items 

(c) Organizat~onal Responsibilities 

(d) Methods Used to Determ~ne ESD Sens~tivity assessment 

2. Employee Training 

(a) Initial Training 

(b) Recurrent Training 

(c) Procedures for Recording Tra~ning 

3. Compl~ance Ver~f~cat~on plan 

(a) Identifies Requirements to be ver~f~ed 

(b) Frequency of Verification 

(b) Technical Requirements 

1. Grounding/Bond~ng Systems 

2. Personnel Grounding 

3. Protected Areas 

4. Packaging 

5. Marking 

6 Equipment 

7 Handling Procedures 

8. Implications for other system elements 

SECTION 7: CEV ProJect Lightning Protection 

SCOPE: 

This Section spec~f~es the CEV lightning protection evaluation and design 

requirements, and defines the analysis and testing used to demonstrate 

CEV systems meet their performance requirements while operating in the 

defined external lightning environment 

CONTENTS: 

A) The CEV Lightning Protect~on plan (LPP): The LPP describes the 

considerations that must be addressed by the Contractor in carrying out 

overall design, planning, demonstration, and management of lightning 

protection for the CEV spacecraft, modules, subsystems, and components. 

The LPP provides means for NASA evaluation and judgment of acceptability 

of the Contractor's proposed lightning protection program and shall 

conta~n the following elements: 

(a) Management control 

(b) Lightning zone identificat~on 





(c) Vehicle lightning environment 

(d) Lightning criticality 

(e) Hazards assessment 

(f) Direct effects protection 

(g) Indirect effects protection 

(h) Vehicle Lightning Detection Instrumentation 

(i) Cumulative effects 

(j) Electrical bonding and corrosion control 

(k) Des~gn analys~s/development test~ng 

(1) Verification criteria 

1. Applicable documents 

2. Description of test articles 

3. Pass/fail criteria 

4. Test hardware definition 

5. Pertinent test/analysis details 

6. Set up details 

7. Test schedule 

(m) Life cycle aspects 

(n) Configuration/documentation control 

(0) Protection of facilities and ground support equipment 

(p) Lightning protection survey 



B) The CEV Lightning Protection verification plan (LPVP): The LPVP shall 

include the test/analyses data and methods to be used as well as the 

pass/fa~l definitions for each subsystem/component to verify lightning 

protection designs for those designated as Catastrophic, 

Hazardous/Severe-MaJor, or Major. The plan shall contain the following: 

(a) Applicable documents. 

(b) Description of test articles. 

(c) Pass/fail criteria. 

(d) Test hardware def~n~t~on. 

(e) Pertinent test/analysis details. 

(f) Set-up details. 

(g) Test schedule. 

(h) Final Lightning protection survey 

C) Lightning Protection Verification Report (LPVR): The CEV 

Electromagnetic Compatib~l~ty Control and Verification Document shall 

define the data content required in the LPVR that is delivered in 

accordance with with requirements to prov~de verification and 

certif~cat~on data for developed and integrated hardware. The LPVR 

presents the results of analyses, tests, and other data needed to verify 

the adequacy of lightning protection designs for all systems, subsystems, 

and/or components whose failure is designated as Catastrophic, 

Hazardous/Severe-Major, or Major. The LPVR provides the means for NASA 

evaluation and judgment of the acceptab~l~ty of the contractor's 

lightning protection designs and hardware/software. 

The report shall contain the following: 

(a) Descr~pt~on and photographs of test set-up, including associated load 

impedances. 

(b) Date, personnel performing test, and location of test. 

(c) Test current ampl~tude and waveforms. 

(d) Conducted and induced voltages and currents measured. 

(e) Measurement records of the instrumentation noise level. 

(f) Test results. 

(g) Statement of qualif~cat~on. 

13.4 FORMAT: ElectronlC format per Section J-2 2.3.2.1. 

13 5 MAINTENANCE: Maintained through formal Program change process after 

initial basel~ning. 







1. 

3 

PROGRAM. CEV 

DATA TYPE' 1 

6. TITLE: Spectrum Management Documents 

2 

4 

5 

DRDNO .. 

DATE REVISED' 

PAGE: 

CEV-T-026 

May 2009 

1 


Spectrum Management documentation is required to request frequency 

authorization for each communication link in accordance with NTIA Manual 

of Regulations & Procedures for Federal Radio Frequency Management (May 

2003 Edition, May 2005 Revisions) Chapter 10. NASA w~ll use this 

information to request frequency authorization for all RF/optical 

devices. Authorization is requested by NASA with contractor's 

participation. 

8 DISTRIBUTION: As determined by the Contracting Ofhcer. 


10 SUBMISSION FREQUENCY: Per Data Requirements Matnx 

11. REMARKS: 

These documents shall be cons~stent with the Constellation Program's 

integrated plans such as CXP-70022, Constellation Command, Control, 

Communication, and Information (C3I) Interoperability Specification (and 

associated Children documents as specified in Attachment J-3, Applicable, 

Guidance, and Informational Documents L~st) 

12. INTERRELATIONSHIP: Parent sow Paragraph(s): 2.6.3. 


13.1 SCOPE. 

Spectrum Management documentation is required for all RF/Optical devices 

in the Crew Explorat~on Vehicle. 


CxP 70022-1 Constellation Program Command, Control, Communication, and 

Information (C3I) Interoperability Standards Books, Volume 1: 

Interoperability Specification (and assoc~ated Children documents as 

specified in Attachment J-3, Applicable, Gu~dance, and Informational 



Informat~on (C3I) Interoperability Standards Books, Volume 2: Spectrum 

and Channel plan 


Information (C3I) Interoperability Standards Books, Volume 3: Master Link 

Book 

CxP 70118, Volume 1: Constellation to Communications and Tracking 

Networks Interface Requ~rements Document, Volume 1-CEV 

CxP 70034, CEV to LSAM IRD 

CxP 70028, CEV to GS IRD 





CxP 70029, CEV to MS IRD 



CxP 70031, CEV to ISS IRD 

NTIA Manual: National Telecommunicatlons and Information Administration 

(NTIA) Manual of Regulatl0ns & Procedures for Federal Radio Frequency 

Management (May 2003 Edition, May 2005 Revlslons) Chapter 10 


The Spectrum Management Report shall lnclude: 

Forms NTIA-33 - Transmitter Equipment Characteristics, NTIA-34 -Receiver 

Equipment Characterlstics, & NTIA-35 -Antenna Equipment Characteristics 

shall be completed by the contractor for each RF system for operational 

vehicle. 

RF link compatibility analyses - Documents the RF compatibility between 

CEV communication links and between CEV communlcatlon links and other 

interfacing elements. 

Power Flux Density analysis - Analysis that shows that all modes of 

operation meet Interdepartmental Radio Advisory Committee flux density 

requirements according to NTIA Manual: NTIA Manual of Regulations & 

Procedures for Federal Radio Frequency Management (May 2003 Edition, May 

2005 Revisions) Chapter 8 (paragraph 8 2.36) for RF radiation impinging 

on the Earth. 

13 4 FORMAT: Electronic format per Section J -2 2.3.2.1. 



required, with changes clearly identified. 







1. 

3. 

PROGRAM: CEV 

DATA TYPE: 1 

2. 

4. 

5. 

DRDNO.: 

DATE REVISED' 

PAGE: 

CEV-T-027 

May 2009 

1 

6 TITLE: Electrlcal, Electronlc, and Electromechanical Parts Management and 

Implementatl0n Plan 


To deflne and document the contractor's requirements, system and 

implementation plan for controlling the selection, acquisition, 

traceability, testlng, handllng, packaging, storage and application of 

Electrical, Electronic and Electromechanical (EEE) Parts for flight and 

critlcal ground support equipment .. 

8. DISTRIBUTION: As determlned by the Contracting Officer 



11. REMARKS. 

12. INTERRELATIONSHIP: Parent SOW Paragraph (s): 2.8.6. 


131 SCOPE: 

The EEE Parts Management and Implementation Plan def~nes Contractor'S 

approach to accomplishing the electrical, electronic, and 

electromechanical parts control requirements and tasks. This DRD also 

includes the ionizing radiation control plan for all CEV EEE Parts. 


JPR 8080.5, E-22: JSC Design and Procedural Standards, Section E22, 

lonizing Radiation Effects 

JPR 8080.5, E-7: JSC Design and Procedural Standards, Section E-7, 

Electrical Components - Restrictions on Use 


The contractor's EEE Parts Management and Implementation plan shall 

include the following: 

1. Parts Selectlon: The Parts Management and Implementation plan shall 

describe a concurrent engineering process, integrated with hardware 

deslgn, ln which parts are selected for use on the basis of suitability 

for the intended application. The plan shall identify application grades, 

parts that are considered standard for each grade (i.e. 'class B), the up 

screening requirements to use a lower grade part in a higher grade 

application, and how other (nonstandard) parts w~11 be evaluated, 

approved for fllght and controlled. The plan shall describe how EEE parts 

selection shall be driven by the performance demands, environmental and 

circuit applications, reliablllty (necessary for the satisfactory 

performance of the systems in which they are used) and maintenance 

allocations defined by the equipment specifications, how EEE parts shall 

be selected based on the suitability for thelr applications and proven 

qualifications to the requlrements of their specifications. 

2. Non-standard EEE Parts Documentation: The EEE Parts Management and 







Implementation Plan shall document the process for non-standard parts 

requests. This process shall include supporting documentation including 

specificatlons, and shall be submltted for NASA approval prior to 

procurement Non-standard parts requests shall identify and provide 

rationale for non-standard EEE part selections, clearly documenting 

justification for use, suitablllty for the appllcation and envlronment, 

and qualification status. 

3. EEE Parts Obsolescence Management: The EEE Parts Management and 

Implementation Plan shall address the Contractor's approach to mitigating 

EEE parts obsolescence. 

4. Audits and Survey's' The EEE Parts Management and Implementation Plan 

shall include a process for surveying suppliers and manufacturers for the 

value-added services or products. In addition, a process documenting 

pre-award surveys shall be lncluded. Pre-award survey shall, as a 

minimum, include sites performing : 

a. Screening and testlng, 

b. Destructive Physlcal Analysis (DPA) , 

c. Failure analysis, 

d. Radiation laboratories. 

5. Destructive Physical Analysis: The EEE Parts Management and 

Implementation Plan shall describe the requirements for performing 

Destructive Physical Analysis (DPA) on EEE parts to qualify or screen 

batches of parts to be utilized. This plan shall deflne when DPA will be 

performed, the DPA requlrements by part type, and the process to 

disposition parts with anomalies. 

6. Part Stress Analysis: The EEE Parts Management and Implementation Plan 

shall document the derating criteria for worst case environments, 

operating conditions, and duty cycle, by part type (i.e. Integrated 

Circults (ICs), resistors, capacitor, etc) to be applied to the hardware, 

and actions necessary to correct any deficiencies. 

7. Controlling speciflcations: The EEE Parts Management and 

Implementation Plan shall define parts that are to be controlled by 

specifications and the minlmum specification contents. As a mlnimum the 

contents shall include: 

a. Complete ldentification of the part. 

b. Physical, environmental, and performance specifications. 

c. Rellability requirements, including inspections and tests for 

quallfication, acceptance, and lot sampllng. 

d. Special explicit requirements such as screening and burn-in, X-ray, 

ionizing radiation, single event effects, and positive particle 

protection (e.g., coating, Particle Impact Noise Detection (PIND)). 

e. Special handling, packaging, and storage requirements. 

f. Documentation, data retention, and submittal requirements. 

8. AS Designed (Where Used) Parts L1St: The EEE Parts Management and 

Implementation plan shall define how to prepare, submit and maintain an 

as-designed (e.g., where-used) EEE parts list. The list contents shall 

include, as a minimum: 

a. Gener~c part type and name, 

b. Common designation, 

c. Controlllng specificatl0n number, 

d Identification of authorized sources, 

e. Quantity used, 

f. Package type, 

g. Qualification and Non-Standard status, and 

h. Next higher assembly. 

9 Part Qualiflcation: The EEE Parts Management and Implementation Plan 


CEV-T-027 Page 2 of 4



shall define how EEE parts w~ll be qualified, when parts shall be 

requalified, and the qualification status of the parts will be 

documented. 



10. Design Configuration Acceptability and Control: The EEE Parts 

Management and Implementat~on Plan shall address how the selected parts 

for a design are rev~ewed for application and environment suitability, 

how the parts quality and rel~ability will meet the operational 

performance requirements, and ~f the parts are being used within the 

specific dev~ce ratings. The selection process, technical acceptability 

of devices, application documentation and review results shall be 

available to NASA to support hardware design reviews, certification, 

acceptance reviews, problem resolutions, and ground and flight 

operations. Key elements are as-designed-parts lists, application stress 

analyses (includ~ng radiation effects), and nonstandard parts 

acceptability assessments. 

11. Parts Procurement: The EEE Parts Management and Implementation Plan 

shall address how the Contractor will select, qual~fy, control, and 

monitor parts manufacturers. The plan shall address the Contractor's 

source inspections, rece~ving inspection (including destructive physical 

analysis), and stocking and handling procedures prior to and during 

assembly. These procedures shall address how the Contractor w~ll avoid 

the procurement and any subsequent installation of parts or 'lots' of 

parts subject to conditions identif~ed in Government-Industry Data 

Exchange Program (GIDEP) and NASA ALERT's. This section of the plan shall 

ensure that the selection and use of the parts will not have an 

'obsolescence' issue to the greatest extent possible. 

12. Commercial Off-The-Shelf/Off the Shelf (COTS/OTS)) hardware: The EEE 

Parts Management and Implementation Plan shall address the use of COTS 

sub-assemblies, and shall define screen~ng, non-standard parts request, 

and risk assessment requirements The analysis of COTS/OTS subassemblies 

shall include as a minimum: 

a. A rev~ew of the as-designed and as-built EEE parts list (or 

equivalent) as applicable, and supporting documentation (e.g., 

procurement spec~flcations, upgrade specifications I waivers, deviations, 

etc.) . 

b. A review of fabrication processes, history, GIDEP, and ALERTS. 

c. Identificat~on of EEE parts that are obsolete or which may be nearing 

obsolescence. 

d. An application/derating analysis at the EEE part level shall be 

developed 

f. A test or assessment of the OTS hardware and/or associated EEE parts 

for susceptibility to the space radiation, micro-gravity and vacuum 

environment. 

g. A review process considering and ~dentifying any ava~lable prior 

h~story of successful operations, previous space fl~ght history, 

failures, and causes of failures for EEE parts in the proposed hardware. 

h. Identification of any known l~fe limiting factors that may affect the 

~ntended useful l~fe of the hardware in the appl~cation, such as use of 

aluminum electrolytic capac~tors. 

i. Rationale and plan for the cert~fication of OTS hardware. 

j. Any other available data that may be pert~nent to the rev~ew process. 

The EEE Parts Management and Implementation Plan shall also address the 

use of COTS sub-assemblies for which ~nsufficient parts information is 

available. In these cases, the plan shall ~dentify how parts used in COTS 

sub-assemblies may be qualified (~.e. by environmental and accelerated 

life testing at the COTS sub-assembly level) . 

13. Parts Problem Reporting and Corrective Action: The EEE Parts 

Management and Implementation Plan shall address a formal and controlled 

closed-loop system for the report~ng, analysis, correction/prevention, 





and data feedback of SRU end item failures. 



14. Ionizing Radiation Effects: 

The EEE Parts Management and Implementation Plan shall require a 

Contractor Ionizing Radiation Control Plan. Thls plan must define the 

processes and methodology used to insure that all EEE parts will 

successfully operate in the CEV radiation enVlronments as described in 

CxP 70023, Constellation Program Design Specificat~on for Natural 

Environments. The Ionlzlng Radiation Control plan shall define the 

required content of all radlatlon test plans, test procedures, and test 

reports & analyses. The CxP 70144, Constellation Ionizing Radiat~on 

Control Plan shall be used to provide guidance for defining radiation 

test protocols and analysis methodology used. 

15. Data Retention Requirements: The EEE Parts Management and 

Implementatlon Plan shall define all EEE parts data retention 

requirements. Data retention requirements shall as a mlnlmum be required 

for: 

a. Non-Standard Parts Requests 

b. EEE Part Specifications 

c. Qualification Reports 

d. Audit and Survey Reports 

e. Destructive Physlcal Analysis (DPA) 

f. EEE Parts Stress Analysis and Application Reviews 

g. Ionizing Radiation test plans, procedures and reports 

h. EEE Parts llsts 

i. Data used to evaluate COTS/OTS Hardware 




required 







1. 

3. 

PROGRAM: CEV 

DATA TYPE' 1/3* 

6. TITLE: Interface Control Documents 

2. 

4 

5 

DRDNO.: 

DATE REVISED' 

PAGE. 

CEV-T-029 

May 2009 

1 


To provide documentation in the form of drawings and/or written records 

to identify for each side of an 1nterface those necessary design 

definitions between one or more systems, modules, subsystems, computer 

software configuration items (CSCI's)r or computer software components 

(CSC's), manual operations, contractors and/or Government agencies to 

provide control of and ensure an agreeable and compatible interface. The 

Interface Control Document (ICD) provides the design solutions to the 

requirements found in the system specifications and/or the Interface 

Requirements Document (IRD); these companion documents serve to 

communicate and control interface design decisions. The 11st of CEV 

internal IRDs requr1ed are specif1ed 1n the DRD for CEV-T-035, Internal 

Interface Requirements Documents. 

8. DISTRIBUTION. As determ1ned by the Contracting Officer. 


10 SUBMISSION FREQUENCY: Per Data Requnements Matrix 

11 REMARKS' 




Software 11fe cycle processes - Lifecycle data. 

The Contents sect10n of this DRD calls out the need to identify 

Functional and Procedural interfaces. Functional interfaces pertain to 

interactions between two entities across an interface. Procedural 

interfaces are functional 1nterfaces that also include sequence 

dependencies. A good example of th1s is an arm-fire interface between 

two entities. The entities share two functional interfaces, namely arm 

and fire. However, they also share a procedural interface, namely the 

arm function must be invoked before the fire function. 

*Subsystem ICDs, Module and External ICDs = Type 1. Avionics & Software 

IDDs = Type 3 

12 INTERRELATIONSHIP: Parent sow Paragraph (s): 2 2, 2.3, 6.1. 2, 6.2.2, 

6.4.2, 6.5.2, 10.3.5.3 

Related DRD(s): CEV-O-008, CEV-T-035 


13.1 SCOPE 

The Interface Control Documents (lCD's) identify des1gn definitions for 

each s1de of an interface that shall ensure des1gn control and 

compat1b1lity. An ICD may describe any number of software interfaces. 

13 2 APPLICABLE DOCUMENTS. 

NPR 7150.2: NASA Software Engineering Requirements (all shall 

statements/the compliance matrix only, excluding the software safety 

requirement) . 


CEV-T-029 Page 1 on






The Interface Control Document (ICD) shall document the physical, 

funct~onal, and procedural ~nterface design as applicable. The ICD shall 

provide the descr~pt~ve text and diagrams to fully describe the interface 

implementation. An ICD shall be produced for each software element 

(flight, ground, s~mulat~on and data services) to document the design of 

each interface ~dentif~ed in the associated IRD. The ICD shall address 

all of the engineering disciplines associated with the interface design. 

The ICD shall identify all applicable workmanship and applicable 

standards being utilized as part of the interface design. The ICD shall 

provide traceability from the Interface Requirements Document (IRD) to 

document design compliance with the requirements. 

The ICD shall address the following class of ~nterfaces: 

For hardware 

(a) Phys~cal - Interfaces involving physical mating and spatial 

relationships between ~nterconnect~ng parts of interfacing end items, 

including clearance envelopes established to avo~d ~nterferences and to 

permit access. Other examples ~nclude power before connector mate and 

order of connector mate. 

(b) Functional - Interfaces involving the ~nteraction or influence of 

conditions imposed by one subsystem or component upon another or by 

external sources such as flu1ds, thermal, electrical, environmental, 


(c) Procedural - Interfaces involving cr~t~cal sequence of events 

occurring in assembly, disassembly, alignment, service operations, and 


For software, in accordance with NPR 7150.2 NASA Software Engineering 

Requ~rements, and us~ng IEEE/EIA 12207.1-1997 as guidance, each software 

ICD shall include: 

(a) Physical - Interfaces involving CSCI's or CSC's that ~nteract 

through: 

1) software to hardware interfaces, including but not limited to 

hardware reg~ster ~nterfaces and memory interfaces. 

2) network interfaces or external communications bus interfaces 

between software CSCI's or CSC's execut~ng on separate computer processor 

modules within separate hardware components. 

3) backplane ~nterfaces or ~nternal communications bus interfaces 

between software CSCI's or CSC's executing on separate computer processor 

modules within the same hardware component. 

4) memory based interfaces between software CSCI's or CSC's executing 

on the computer processor module of any hardware subsystem. 

(b) Functional - Interfaces involving the interaction (data exchange, 

function invocation, or signal generation) or influence of conditions 

imposed by one CSCI or CSC upon another. 

(c) Procedural - Interfaces involving critical sequence of events 

performed through collaboration between software CSCI's or CSC's (as 

applicable). (e.g., an "arm" signal must always be provided prior to the 

"fire" signal for any pyrotechnic event.) 

(d) Priority assigned to the interface by the interfac~ng entity(ies) . 

(e) Type of functional/procedural interface (e.g., function invocation, 

send real-time data, send data for informat~on management, generate event 

or signal for control) to be 1mplemented. 

(f) Specification of individual data elements (command and data 

dictionary ident~fer / mnemon~c, class attributes, record/structure 

const~tuents or passed parameters), data type, range of values (e.g., the 

numeric range for integer or real types and the integer mapping for 

enumerated values), un~ts of measure, size (in bits), and bit-level 

descriptions of data elements that the interfac~ng entity(ies) will 

provide, store, send, access, receive. 

(g) Specification of protocols the interfacing ent~ty(ies) will use for 

the ~nterface(e.g., the unique identifer of a specif~c hardware register, 







network bus, backplane bus or memory interface) . 

(h) Other specifications, such as physical compatibility of the 

interfacing entitY(1es) (synchronous or asynchronous, frequency of 

exchange, FIFO or LIFO, buffered queue or non-buffered sample, etc.). 

(1) Traceability from each interface des1gn to the associated software 

interface requirement(s)in the software Interface Requirements Document 

(IRD) . 

(j) Interface compatibility, e.g., l1ttle endian vs. big endian. 

(k) Error Handling, such as synchronous error handling (error handling 

assoc1ated with indications explicitly passed over the interface) and 

asynchronous error handling (error handling associated with failure to 

communicate over the interface) as appl1cable. 



subm1tted to NASA for approval. Complete re-issue of the document is 

required with changes clearly identified. 

Attachment J -2 

CEV -T -029 Page 3 of3





1. 

3. 

6. 

7. 


DATA TYPE: 1/3* 4. DATE REVISED' May 2009 

5 PAGE. 1 

TITLE: CEV Requirements Specificatlon 

DESCRIPTIONfUSE' 

The CEV Requirements Specl£ication DRD documents the allocation 

of the following: 

- CEV System requirements to the Spacecraft and Contractor-provided 

Ground Support Equipment System Requirements Specifications 

- CEV Spacecraft requirements to the module level 

- CEV module requirements to the subsystem level 

- CEV subsystem requirements to the component level 

8. DISTRIBUTION' As determined by the Contractlng Officer. 



11. REMARKS. 

All system, module, subsystem, and component-level requirement documents 

have CXP-10001, Systems Requlrements for the Crew Exploratlon Vehicle 

Element (CEV SRD), as their parent document. A common format shall be 

used across the system, module, subsystem, and component-level 

requirements documents. CEV configuration items will be determined 

during CEV Project phases and wlll be documented in the Contractor's 

Configuration Management plan. 

In naming each document, should be replaced wlth the appropriate 

name (e.g., CEV Spacecraft System Requlrements Specification, CEV Crew 

Module Requirements Specification, etc.) 

All CEV System, module, subsystem, MGSE and EGSE level requirements 

documents are type 1 documents. 

All CEV component and CEV GSE End Item level requirements documents are 

type 3 documents. 

12. INTERRELATIONSHIP' Parent sow Paragraph(s): 22,2.7.2,2.7.4,6.1, 

6.2, 6.4, 10.6.4. 

Related DRD(s): CEV-O-008, CEV-D-002, CEV-D-005 


13.1 SCOPE' 

The CEV Requirements Specificatlon DRD establishes the format and 

contents of the following system-level requirements specifications: 

- Spacecraft Systems Requirements Speclfication 

- Contractor-provided Ground Support Equipment Systems Requlrements 

Specification and the subsequent module, subsystem MGSE, EGSE, component 

and GSE End Item level requirements specifications. 


CXP-72000: Systems Requirements for the Crew Exploration Vehicle Element 

(CEV SRD) 








The system requirements specifications shall allocate the CEV System 

functional, performance and operational requirements and constraints to 

define the des1gn and arch1tecture of the total System, 1nclud1ng 

software, between the Spacecraft and Ground Systems. Two (2) documents 

shall be produced comprising the next level of decomposition from the CEV 

System level requirements. The requirements shall be allocated between 

Spacecraft and Ground Support Equipment 

The module requirements specificat10ns shall decompose the CEV spacecraft 

system functional, performance, and operat10nal requirements to the 

module level. A module is defined as a self-contained unit of a 

spacecraft that performs a specific task or class of tasks in support of 

the major function of the craft For example, a spacecraft may be broken 

up into a crew module, a service module, etc. 

The subsystem requirements specifications shall decompose the CEV module 

functional, performance, constra1nts and design requirements to define 

the des1gn and architecture of the total subsystem, including software. 

The component requirements specifications shall conta1n the decomposition 

of the requirements from the subsystem level through the lowest level of 

the decomposition. This specification will document the allocated 

functional, performance, constra1nts and des1gn requirements for the CEV 

subsystem to the component level. For the purposes of this DRD, 

'component' will be used to describe each level of the decomposition 

below the subsystem level as defined by the Contractor. The 

decomposition of the subsystem is cont1nued until a procurement or buildto 

spec1ficat1on has been developed. A component is defined as an 

aggregate of hardware and/or software that can be characterized by one 

specification, is designed by a single activity to be funct10nally 

tested, and is verified as a un1t. 

The MGSE & EGSE functional grouping requ1rements specifications shall 

decompose the CEV GSE system functional, performance, constraints and 

design requirements to define the design and arch1tecture of the total 

MGSE & EGSE functional group1ngs. 

The end item requirements specifications shall contain the decomposition 

of the requirements from the MGSE & EGSE requirements through the lowest 

level of the decomposition, including associated software per the 

Software Requirements Specification (DRD CEV-T-048) for MGSE and EGSE. 

APPLICABLE DOCUMENTS for CEV GSE: 

NASA-STD-5005B: NASA Standard for Ground Support Equipment (and 

assoc1ated Ch1ldren documents as specified in Attachment J-3, Appl1cable, 

Guidance, and Informat1onal Documents List) 

Each document shall conta1n a sect10n titled 'verification'. For each 

requirement 1n the documents, there shall be one or more verification 

methods identified. The document shall contain a definition of each 

verification method that identifies the general verification approach, 

and is consistent w~th identification of the verification methods used in 

the Master Verification Plan, T-015. The document shall also contain a 

verif1cation traceability matrix that establishes the relationship 

between each requ1rement and the verification methods that will be used 

to accomplish the indicated ver1f1cat10n actions. 

13.4 FORMAT. Electron1c format per Section J-2 2.3.2.1. As required by ICE, 

the Contractor shall also include th1s data in a requirements management 

tool for easy data entry. 









required. 







1. 

3. 

PROGRAM. CEV 

DATA TYPE: 2 

6. TITLE: Archltecture Deslgn Document 

2 

4. 

5. 

DRDNO.· 

DATE REVISED. 

PAGE. 

CEV-T-033 

May 2009 

1 

7. DESCRIPTION/USE: 

To describe the functional design of CEV and its operational and support 

environments. To identify an approprlate set of resources to satisfy the 

system/mission performance, and the driving requirements that provide a 

sound basis for the system's des~gn or select~on. To describe the 

organlzatlon of a CEV as composed of hardware configuration items 

(HWCI'S), computer software conflguration items (CSCI'S), CSCI groupings, 

and manual operations. To describe the CEV physical architecture for 

purposes of guiding horizontal integration, requlrements engineering, 

functional analyses, trade studies and system analyses activities across 

the CEV Project. 



10 SUBMISSION FREQUENCY: Per Data ReqUlrements Matrix 

11 REMARKS' 

Informatlon provlded In other DRD's is anticipated to be used in the 

preparation of data items In response to this DRD. This information may 

be included by reference in this data item. The Architecture Design 

Document (ADD) provides the functional and physical description of CEV. 

12. INTERRELATIONSHIP. Parent SOW Paragraph(s): 2.3. 

Referenced from SOW Paragraph(s): 2.1.3, 6.2 


13.1 SCOPE: 

In the early development phase, through completion of preliminary design 

work, the systems engineering activity focuses on identificatlon of the 

technical requirements for the system that define what the modules, 

subsystems, and components must do and how well they must do it. During 

the detalled design phase the systems engineering activity emphasis 

switches to identification of requirements for the acceptance of the 

physical product elements by the Constellation Program and logistics 

requirements. 

The Architecture Design Document provldes the functional design and 

associated design rationale for the system's driving requirements that 

shall ensure proper testability and performance over the entire range of 

operations. 


13.3 CONTENTS 

The Architecture Design Document shall contain: 

a. Introduction. ThlS sectlon shall establish the context for the 

remainder of the document. In particular, it defines the scope of 

this document, and the relationship of thls document to other key 







CEV documents; change authortiy, convention and notation and overall 

document organization 

b. Applicable and Reference Documents. This section shall outline the 

reference and applicable documents. This section shall list the 

number, title, revision, and date of all documents referenced in this 

document. This section shall also identify the source for all 

documents not available through normal NASA stocking activities. 

c. CEV Missions Overview. This section shall briefly state the purpose of 

the CEV System and summarizes the CEV architecture evolution in 

relation to the Design Reference Missions. These missions will serve 

as the basis for describing the CEV Architecture throughout the 

document. The architecture descriptions in the rest of the document 

are outlined according to each of the CEV DRMs. 

d. CEV Funct10nal Architecture. This section shall provide the general 

funct10nal architecture desciption. This section shall provide a 

summary of CEV internal and external functional interfaces and a 

summary of the funct10nal architecture for each DRM. 

e. CEV Physical Architecture Description. This sect10n shall describe 

the CEV Physical Arch1tecture and shall provide a summary of CEV 

internal and external physical interfaces and a summary of the 

physical architecture for each DRM. The physical architecture 

descriptions shall be broken down into the CEV modules and 

subsystems. The level of detail prov1ded 1n th1s document varies 

depending on the maturity of the baseline for each CEV module. 

Critical design decisions that were based upon trades and/or analysis 

shall be addressed. This section shall also address any block 

configuration deltas, mass properties, Master Equ1pment List (MEL), 

and power allocations. Design convent10ns needed to understand the 

design shall be presented or referenced. 

NOTE: This section shall be divided into subsections that decribe 

the CEV System Module Architecture Design and the modules associated 

subsystems. Each subsection shall cover the follow1ng areas: 

1. Identify the major components of the subsystems. 

2. Show the static (such as 'consists of') 

components. Multiple relationships may be 

the selected design methodology. 

relationship(s) of the 

presented, depending on 

3. State the purpose of each module/subsystem and identify the key 

driving requirements (if applicable). 

4. Ident1fy each module/subsystem development status/type, if 

known (such as new development, exist1ng component to be reused as 

is, existing design to be reused as is, existing design or 

component to be reengineered, component to be developed for reuse, 

component planned for Build N, etc.) For existing design or 

components, the descr~ption shall provide identifying information, 

such as name, version, documentat10n references, locat10n, etc. 

5. Include diagrams and descriptions showing the dynamic 

relationship of the components, that is, how they will interact 

during System operation, including, as applicable, flow of 

execution control, data flow, dynamically controlled sequencing, 

state transition diagrams, timing diagrams, priorities among 

components, hand11ng of interrupts, timing/sequencing 

relationsh1ps, except10n handling, concurrent execution, dynamic 







allocation/deallocation, dynamic creatlon/deletion of objects, 

processes, tasks, and other aspects of dynamic behavior. 

6.Include interface design characteristics between subsystems. One 

or more interface diagrams shall be provided, as appropriate, to 

depict the interfaces. Characteristics may include: 

a) Type of interface 

b) Data elements 

c) Communication methods 

d) Physical compatlbiltiy 

f. Spacecrate Software Architecture Description. This section shall 

describe the functional design of Spacecraft Software Architecture. 

To describe the organization of a CEV as composed of computer 

software configuratlon ltems (CSCI'S), CSCI groupings, and manual 

operations. To describe how the functional design and the SWCIs, and 

interfaces between them comprise an architecture consistent with a 

modular open systems approach. Critical design declsions that were 

based upon trades and/or analysis shall be addressed. 

NOTE: This section shall be divided into subsections that decribe 

the componenents of the CEV Spacecraft Software Architecture. Each 

subsection shall cover the following areas: 

1 Identlfy the major software components of the Software 

Architecture subsystems 

2. Show the static (such as 'consists of') relationship(s) of the 

components. Multiple relationships may be presented, depending 

on the selected design methodology. 

3. State the purpose of each component and identlfy the Key 

driving system requirements (if applicable) 

4. For each computer system or other aggregate of computer 

hardware resources identified for use in the System, describe 

its computer hardware resources (such as processors, memory, 

input/output devices, auxlllary storage, and communications/ 

network equipment) Each description shall, as applicable, 

identlfy the configuration items that will use the resource, 

describe the allocation of resource utilization with associated 

margin to each CSCI that will use the resource 

5. Include diagrams and descrlptlons showing the relationship of 

the components, including, as applicable, flow of execution 

control, data flow, dynamlcally controlled sequencing, state 

transltl0n diagrams, timing diagrams, priorltles among 

components, handling of interrupts, tlming/sequencing 

relatlonships, exception handling, concurrent execution, 

dynamic allocation/deallocatlon, dynamic creation/deletion of 

objects, processes, tasks, and other aspects of dynamic 

behavior. 

6. Include lnterface design characteristics between software 

componenets One or more interface diagrams shall be provided, 

as appropriate, to depict the interfaces. Characteristics may 

lnclude: 

a) Type of interface (such as real-time data transfer, 

storage-and-retrieval of data, etc.) to be implemented. 

b) Characteristics of lndlvidual data elements that the 

interfaclng entity(ies) will provide, store, send, 

access l receive, etc. (e.g., ldentlflers, data type, 

Slze, format, range, accuracy, etc.). 

c) Characteristics of data element assemblies (records, 

messages, files, arrays, displays, reports, etc.) that 

the lnterfacing entity(ies) will provide, store, send, 

access, receive, etc. (e.g., identifiers, data elements, 

medium, visual and auditory characteristics, etc.). 







d) Characteristics of communication methods that the 

interfacing entity(ies) will use for the Interface 

(e.g., identifiers, links/bands, formatting, transfer 

rates, etc.). 

e) Characteristics of protocols that the interfacing 

ent~ty(~es) w~ll use for the interface (e.g., 

~dent~fiers, priority/layer, error control, packeting, 

synchronization, etc.). 

g Requ~rements traceab~l~ty. Th~s paragraph shall contain (if 

1nfor.mation is contained in Requirements Traceability Matrix, or 

elsewhere, it may be referenced) : 

1. Traceability from each system identif~ed ~n this Architecture 

Definition Document to the system requirements allocated to it. 

2. Traceability from each system requirement to the System 

components to wh~ch ~t ~s allocated. 

3. Traceability from design decision data to the requirements to 

support validation of the requirements 

h. Notes. Th~s section shall contain any general informat~on that aids 

in understanding this document (e.g., background information, 

glossary, rationale). Th~s section shall contain an alphabetical 

listing of all acronyms, abbreviations, and their meanings as used in 

this document and a list of any terms and def~nitions needed to 

understand this document 

i. Appendices. Appendices may be used to provide information published 

separately for conven~ence in document maintenance (e.g., charts, 

class~fied data). As applicable, each append~x shall be referenced 

in the main body of the document where the data would normally have 

been prov~ded. Appendices may be bound as separate documents for 

ease in handling. Append~ces shall be lettered alphabetically (A, B, 

etc.) . 

The appendices may contain any general informat~on that aids in 

understanding this document (e.g., background information, glossary, 

rationale). This section shall contain an alphabetical listing of all 

acronyms, abbreviations, and their meanings as used in this document and 

a list of any terms and definitions needed to understand this document. 

13.4 FORMAT. Electron~c format per Section J-2 2.3.2.1. Requirements 

(including decision support and requirements validation data) must be 

maintained within the requ~rements database. 



required. 







1. 

3 

PROGRAM: CEV 

DATA TYPE' 1 

6. TITLE' Requ~rements Traceabil~ty Report 

2 

4. 

5. 

DRDNO.: 

DATE REVISED' 

PAGE: 

CEV-T-034 

May 2009 

1 


To ensure traceability and visibility that program/project requirements 

and that they have been completely and properly flowed down to 

appropriate lower level requirements documents 




11. REMARKS: 

12. INTERRELATIONSHIP: Parent SOW Paragraph (s): 2.3 

Referenced from SOW Paragraph(s): 6 2 

Related DRDs: CEV-T-031, CEV-T-032 


13.1 SCOPE' 

The Requirements Traceability Report documents the flow down of 

requirements starting with the CEV System requirements down through 

subsequent levels as determined by the Specification Tree. 


CXP-72000: Systems Requirements for the Crew Exploration Vehicle Element 

(CEV SRD) 


The Requirements Traceability Report shall 1dentify and provide bidirectional 

traceability for all tier 1 level CEV Project requirements 

from the CEV System requirements as documented in the Spec1fication Tree. 

Traceability must be established for all requ~rements sources. The 

report shall be produced from the requirements database as part of the 

Contractor's system eng~neering tool. The report shall state the 

requirement numbers and requ1rements to be met at each level. Higherlevel 

requ~rements that are not flowed down shall be identified. 

13 4 FORMAT: Electron~c format per Section J -2 2.3.2.1. 


submitted to NASA for approval. Complete re-1ssue of the document is 

required. 







1. 

3. 

PROGRAM CEV 

DATA TYPE: 1 

6. TITLE: Internal Interface Requirements Document 

2. 

4 

5. 

DRDNO. 

DATE REVISED: 

PAGE: 

CEV-T-035 

May 2009 

1 


To spec~fy the ~nterface requirements between each module, between each 

subsystem, and between Computer Software Configuration Items (CSCls) or 

Computer Software Components (CSCs). Also to spec~fy requirements 

imposed upon or by manual operations, or other system components to 

achieve one or more interfaces among the modules, subsystems, and CSCls 

(and/or CSCs). To be used in conjunction with the Software Requirements 

Specification as a basis for des~gn and qualification testing of software 

systems and CSCIs. 




11. REMARKS. 




software life cycle processes - L~fecycle data 

12. INTERRELATIONSHIP' Parent sow Paragraphs: 2.2, 2.7.2, 2.7.4, 6.1, 6.2, 

6.4, 10.6.4 

Related DRD(s): CEV-O-008, CEV-T-029, CEV-T-048 


13.1 SCOPE: 

The Internal Interface Requirements Document (IRD) shall contain the 

interface requirements between each of the CEV modules, subsystems, and 

CSCI or CSC interfaces within the spacecraft as applicable. This 

specification also details provisions for verification and requirements 

traceability. An IRD shall be produced for each software element 

(flight, ground, simulation, and data services) to document the interface 

between each CSCI or CSC that interfaces to another CSCI or CSC, and each 

CSC to CSC interface within a CSCI (~f applicable), and for each CSCI or 

CSC that interfaces directly to a hardware component. 



The Internal Interface Requirements Document (IRD) shall define all 

physical, functional and procedural interface requirements to ensure 

system, hardware, and software compatibility. The IRDs shall include the 

following: 

For hardware: 

a. Phys~cal - Interface requirements involving phys~cal 

mating and spatial relationships between interconnect~ng parts of 

~nterfacing end items, including clearance envelopes established to 

avoid interferences and to permit access. 







b. Functional - Interfaces involving the interaction or 

influence of conditions imposed by one subsystem or component upon 

another or by external sources such as fluids, thermal, electrical, 

environmental, data, and loads. 

c. Procedural - Interfaces involving critical sequence of 

events occurr~ng ~n assembly, d~sassembly, alignment, service 

operations, and computer programs. 

d. Each document shall contain a section titled 'Ver~fication'. 

For each requirement in the document, there shall be one or more 

verification methods identified. The document shall contain a 

definition of each verification method that identifies the general 

verif~cat~on approach, and is consistent with identification of the 

verification methods used in the Master Verification plan, CEV-T-015. 

The document shall also contain a verification traceability matrix 

that establishes the relationship between each requirement and the 

ver~f~cat~on methods that w~ll be used to accomplish the indicated 

verification actions. 

In addition, for software, us~ng IEEE/EIA 12207.1-1997 as guidance, IRD 

shall ~nclude: 

a. Requirements imposed on one or more systems, subsystems, 

configurat~on ~tems, manual operations or other system components to 

achieve one or more software interfaces among these entities. 

1 Interface ident~f1cation and diagrams. One or more 

diagram shall be provided to depict the interfaces between 

the CSCIs or CSCs and between each CSCI or CSC that 

interfaces directly to hardware. (e.g., a UML Domain Chart 

Diagram with dependencies depicted between each domain and 

or a context d~agram dep~cting the interfaces between 

unique software and or hardware elements) . 

2. Project-unique identifier of interface. A project 

un~que ~dent~fier shall be assigned to each interface w~th 

the ~dent1fier constructed by concatenating the following 

strings separated by an underscore character: "ORN", _ 

"FSW" for a flight software interface used for software 

verification, "GSW" for a ground software interface, "SSW" 

for a simulation software interface or "DSW" for a data 

serv~ces software interface, _ the UML KEY letter string 

for the source CSCI, CSC or hardware interface, _ and the 

UML KEY letter string for the dest~nation CSCI, CSC or 

hardware interface. (e.g., ORN_FSW_GNC_CDH for a flight 

software interface between the GNC software entity and the 

CDH software entity). The project-unique identifier shall 

be annotated on the interface diagram(s). Note, by 

def~n~t~on, interfaces between one software element 

(flight, ground, simulation or data services) and another 

are hardware interfaces which are represented on the 

software ~nterface diagram for each element as a software 

to hardware interface at the final point where the software 

interfaces with the hardware interface that provides 

communications between the fl~ght, ground, simulation or 

data services systems. 

3. One pair of requirements shall be documented for each 

unique form of interaction that occurs over each interface. 

One requirement of each pair shall state what the source of 

the 1nterface "provides" to the dest1nation of the 

~nterface, and one requirement of each pair shall state 

what the destination of the l.nterface "receives'I 

from the 

source of the interface. (e.g., if software entity A 

provides data to software entity B and software entity A 

invokes a funct~on of software entity B, then two pairs of 

interface requirements shall be written; one pair 

describing the data exchange, and one pair descr~bing the 

funct~on invocation). For the spec~al case of a broadcast 

type of interface where there is a single "provider" and 

mUltiple "receivers", a pair of requirements shall be used 







to document each interface for which the requirements, 

design or implementation of the interface differs between 

the provider and one receiver and the provider and any 

other receiver (e.g., one pair of requirements is written 

for the single provlder and the list of all receivers only 

if the interfaces between the provider and all receivers 

are ldentlcal in requirements, design and implementation, 

for all other conditions a pair of requirements is written 

for each combination of provlder and receiver) . 

Requlrements associated with synchronous error handling 

(indications explicitly passed over the interface) and 

asynchronous error handllng (indications associated with 

failure to communicate over the interface) shall be 

documented for each lnterface as applicable. 

4. Precedence and crlticality of requirements. The IRD 

shall document the precedence of the lnterface requirements 

(as applicable). The criticality of the interface 

requirements shall be determined and documented using the 

same approach applied to software requirements. 

b. Qualification provisions The quallfication provisions for 

interface requirements shall be determined and documented using the same 

approach applied to software requirements. 

c Requlrements traceabllity shall be documented between the 

software interface requirements and the assoclated software, subsystem or 

system level requirement(s). 

13.4 FORMAT: Electronic format per Section J-2 2.3.2.1. As required by ICE, 

the Contractor shall also lnclude this data in a requirements management 

tool for easy data entry. 










1 

3. 

PROGRAM: CEV 

DATA TYPE' 2/3* 

6. TITLE' Margins Management Plan/Report 

2. 

4 

5 

DRDNO .. 

DATE REVISED: 

PAGE: 

CEV-T-036 

May 2009 

I 

7 DESCRIPTIONfUSE: 

The Margins Management plan is the unified system level approach to 

margin/contingency control. It defines the system design resources, 

their budgets, subsystem allocations, and current properties. The 

Margins Management Report includes margin properties reports for all 

managed design margins. 

8 DISTRIBUTION. As determined by the Contractmg Officer. 

9 INITIAL SUBMISSION Per Data Requirements Matnx 


11 REMARKS: 

The Marg~ns Management Plan shall be Data Type 2, Margins Management 

Reports shall be Data Type 3. 

12 INTERRELATIONSHIP: Parent SOW Paragraph(s): 2.4. 


131 SCOPE: 

The Margins Management Plan is a statement of the contractor's margin 

management philosophy The Margins Management plan and Marg~ns 

Management Reports prov1de the CEV ProJect with detailed 1dentification 

of all resource margins and embedded margins necessary to ensure mission 

success and system robustness. 



This DRD consists of two products: 

Marg1ns Management Reports. 

The Margins Management Plan and 

The CEV Margins Management plan shall include: 

a. Identif1cation of system level margins by SDR (e.g. mass, 

power, etc). 

b. Identification of subsystem level margins by PDR. 

c Plan for system level margins management, including depletion. 

d. Plan for subsystem margins management, including depletion. 

e. Quant1fication of system level marg1ns (preliminary by SDR, 

final by PDR) . 

f. Quantification of subsystem level margins (final by PDR). 

The CEV Margins Management Reports shall include. 

a. Margins status, includ1ng current margin values and margin 

targets based on depletion plan. 

b. Rationale for unplanned deplet~on. 









subm~tted to NASA for approval. Complete re-issue of the document is 

required. 







1. 

3. 

6. 

7. 

PROGRAM' CEV 2. DRDNO.: CEV-T-040 

DATA TYPE. 1/3/4* (See Data Requirements 4 DATE REVISED' May 2009 

Matrix) 5. PAGE: 1 

TITLE. Acceptance Data Package 

DESCRIPTIONIUSE 

To provide the documentation needed by NASA to establish the 

acceptability of lntegrated systems/hardware/software for their intended 

use. 


9. INITIAL SUBMISSION. Per Data Requirements Matnx. Acceptance data shall 

be prepared and electronically dellvered for each inltial delivery of 

Production hardware or software meeting the criteria established in CxP 

70146. Acceptance data shall be prepared and electronically delivered for 

each initial delivery of Flight Test hardware or software in Contractor 

Format. 

10 SUBMISSION FREQUENCY . Per Data Requirements Matnx. 

shall be prepared and electronically delivered for each 

delivery of Production hardware or software meeting the 

established in CxP 70146. 

Acceptance data 

subseql.\ent recriteria 

11. REMARKS' 

To support hardware or software deliveries to the CEV Project, specific 

data, which identlfies and represents the status of the item being 

delivered, must be provided to the receiving organization. The 

accumulation of this data, originally delivered for acceptance and 

subsequently maintained throughout the life of the item, is known as the 

Acceptance Data Package (ADP). 

The ADP provides a complete and verlfied status, including the as-built 

configuration, of hardware or software, contains information pertinent to 

acceptance, identifies information unique to the item, and enables the 

continuatl0n of required actlvities by the uSlng organization. The ADP 

is prepared as part of the hardware or software acceptance/delivery 

criteria and will be malntained throughout the hardware or software life 

cycle after government acceptance. The ADP must be maintained throughout 

lntegrated testing, ground processing, launch site processing, on-orbit 

or in-flight operation, post landing, and 

malntenance/modificatlon/refurbishment activities until the hardware or 

software is decommissioned. 

Flight Test ADPs are Data Type 4 

12 INTERRELATIONSHIP: Parent sow Paragraph(s)' 10.3.1,10.3.2,10.3.3, 

10.3.5.3. 

Referenced from sow Paragraph(s): 2.6, 2.7.2. (e), 6.1.5, 6.5.4 



13.1 SCOPE' 

An ADP shall contain the lnformation necessary for NASA, or its delegate, 

to determine the acceptability of delivered hardware, software, and 

integrated systems for their intended use The acceptabllity of the 

delivered item is based on whether the acceptance data provides 

sufflClent evidence that acceptance requirements have been satisfied for 

the corresponding hardware or software delivery. The term "delivery" 







applies to the initial delivery of an item at the time of acceptance, as 

well as any subsequent delivery resulting from modifications, 

maintenance, refurbishment, or any other activity that produces new data 

for the delivered item. 

The ADP requirements estab11shed by th1s DRD shall apply to hardware 

[Production flight hardware, and ground support equipment (GSEll, 

software, and integrated systems. 


CxP 70146 Constellation Program Acceptance Data Package (ADPl 

Requirements for production Units only. 


This DRD estab11shes the requ1rements for the m1n1mum acceptance data 

which is required for Production hardware, software, and integrated 

systems delivered to NASA for the CEV Project. These requirements are 

documented in CxP 70146, Constellation Program Acceptance Data Package 

(ADPl Requ1rements. 

Flight Test Program ADPs utilize Contractor Format Contents (Excel 

spreadsheet l 

Flight Test Hardware Excel spreadsheet conta1ns the following data: 

a. Running/operating time and cycle 

b. Test history log 

c Inspect10n records 

d. Transfer records 

e. Alignment data for cr1t1cal 1tems 

f. Component logbook 

g We1ght & balance logs 

h. Configuration records 

i. Accumulated component time and/or cycles at time of shipment 

j. Software acceptance data and summary status 

k. Copy of proposed DD Form 250 

1. Operations & maintenance documents 

13.4 FORMAT: Electronic format per Section J -2 2.3.2.1. Single searchable PDF 

requirement not applicable. 



required 







I. 

3. 

6. 

7 

PROGRAM' CEV 2. DRDNO.· CEV-T-041 

DATA TYPE' 2 4. DATE REVISED: May 2009 

5. PAGE' 1 

TITLE:CEV Instrumentation plan 


This DRD develops and records the plans and processes for all 

instrumentation development and implementation activities. 

8 DISTRIBUTION' As determined by the Contractl.ng Officer. 



11. REMARKS: 

12. INTERRELATIONSHIP: Parent sow Paragraph(s): 2.6.1. 

Related DRD(s). CEV-T-047 


13.1 SCOPE: 

The instrumentation plan provl.des insl.ght into, and a tool for 

monitoring, the processes to be followed for CEV spacecraft 

instrumentation development and l.mplementation activities. This DRD will 

include the provisions for the calibration of the instrumentation 

transducers and sensors to assure end-to-end error and tolerances are 

within required performance. All technical informatl.on related to the 

instrumentation requirements allocation, trade studies, system analysis, 

design, test, verficatl.on, certification and sustaining engineering shall 

be documented in DRD-T-047, AVl.onics Design and Data Book Volume II - 

Command and Data Handling/Instrumentatl.on Subsystem Data. 



The CEV Instrumentation plan shall include the following processes and 

plans: 

a. A process that identifies and allocates instrumentation and sensor 

requirements across the CEV System includl.ng subsystem engineering and 

operational needs. The process shall l.nclude the roles and 

responsibilities for sensors interface design and the approval of the 

subsystem sensor requirements definition, procurement and testing, and 

the definition and provisioning for the calibration of the 

instrumentation transducers and sensors to assure end-to-end error and 

tolerances are within required performance. 

b. A development process that addresses long lead parts procurement, 

potential obsolescence issues, determl.natl.on of required trade studies, 

prototypl.ng approach and development test, modeling, and analysis aimed 

at reducing technical risks. 

c. A plan that addresses the necessary facl.ll.ties and equipment for 

developing and certifying the CEV instrumentation across the vehicle 

system and wl.thin each subsystem. 

d A ground data reduction process including a description of the 

hardware/software required to support this capability. 

e A metrl.CS plan to measure key aspects of these processes. 





13.4 FORMAT: Electronic format per Section J-2 2.3.2.1. Microsoft® Wordcompatible. 

13 5 MAINTENANCE· Contractor-proposed changes to this document shall be 


required, with changes clearly identified. 







1. 

3. 

PROGRAM: CEV 

DATA TYPE: 2 

DRDNO.: 

DATE REVISED: 

PAGE: 

1 

6. TITLE.CEV Space.Radiation Analysis and Certification Report 

2. 

4. 

5. 

CEV-T-045 

May 2009 


Radiation Analyses w111 be used to describe the internal crew radiation 

exposure resulting from exposure of the CEV to both nomlnal space 

radiation environments and solar particle events. ThlS analysis will be 

used by NASA to ensure that the CEV provides for crew exposures which are 

both below established design limits and which are further maintained As 

Low As Reasonably Achievable (ALARA). For ionizing radiation effects on 

electronic hardware, refer to DRD CEV-T-027, Electrical, Electronic, and 

Electromechanical Parts Eanagement and Implementation Plan. 


9. INITIAL SUBMISSION: Per Data Reqmrements Matrix 


11. REMAJUKS:Active radlatlon lnstrumentation for the vehicle is contractor 

-provided equipment. Passive dosimeters for CEV missions are provided by 

the government. 

12. INTERRELATIONSHIP. Parent SOW Paragraph(s): 2.8.3. 

Related DRD: CEV-T-027 


13.1 SCOPE: 

The contractor shall provide NASA with radiation analyses that describes 

the projected crew radiation exposure based on the vehicle design. 

These analyses will also provide information about the internal CEV 

radiation enviornment relevant to electronic subsystem hardware. 


CXP-70023: Constellation Design Specification for Natural Environments 

(DSNE) (and associated Children documents as specified in 

Attachment J-3, Appllcable, GUldance, and Informatlonal Documents 

List) 

CXP-70024, Section 3.2.7: Constellation Human System Integration 

Requirements (HSIR), Section 3.2.7 

CxP-70044: Constellation Program Natural Environment Definition for 

Design (NEDD) 

National Council on Radiation Protection and Measurements Report No. 132: 

Radiation Protection Guidance for Activities in Low-Earth Orbit 

National Councll on Radiatlon Protection and Measurements Report No. TBD: 

Radiation Protection and Science Goals for Lunar Missions (to be 

published in 2006) 

OSHA Standards 29 CFR: Supplementary Standards 1960.18 


The Space Radiation Analysis and Certification Report shall use the space 

radiation environments descrlbed ln the CXP-70023, Constellation Design 

Specification for Natural Environments (DSNE) (and associated Children 








Informational Documents Llst) , utlllzlng cxP-70044, Constellation Program 

Natural Environment Definition for Design (NEDD), and determine the doses 

and particale spectrums lnternal to the CEV habitable area during 

enhanced space weather conditions (significant solar particle events), 

and nomlnal solar maximum and solar minlmum conditions. 

The Space Radiation Analysis and Certification Report shall detail the 

following: 

- Radiation analysis performed including structural models, materials 

selection, stowage planning (including worst case scenarios where the 

plan is not followed), and design decisions. 

- Transport models 

- Human models 

13.4 FORMAT· Electronic format per Section J-2 2.3.2.1. Microsoft® 

Word/Excel® or Adobe® Acrobat® PDF for textual and graphics information, 

or ASCII dellmited for data. 

13.5 MAINTENANCE. Contractor-proposed changes to this document shall be 


required. 







1. 

3. 

PROGRAM. CEV 

DATA TYPE: 1 

6 TITLE:CEV Data and Command Dictionary 

2. 

4. 

5. 

DRDNO .. 

DATE REVISED: 

PAGE. 

CEV-T-046 

May 2009 

1 


Used to define, manage, and record all data elements that interface with 

the core av~onics software and hardware, the subsystem specific software, 

and the ground systems. Specif~c data elements include: end-to-end 

channelization infor.mat~on, calibration information, sensor range, 

telemetry formats, and command information required to define the entire 

software system/architecture. Th~s DRD must be sortable for use by 

multiple end-user functions, and includes all data used by the flight 

crew, ground operations, and flight operators. 


9 INITIAL SUBMISSION' Per Data Requnements Matrix 


11. REMARKS: 



13.1 SCOPE. 

The CEV Data and Command D~ctionary appl~es to all flight, ground, 

simulation, and test software and hardware on the CEV Project. 


CxP 70022-4 Constellation Program Command, Control, communicat~on, and 

Information (C3I) Interoperab~l~ty Standards Books, Volume 4: Information 

Representation Specif~cation (and assoc~ated Children documents as 

specif~ed in Attachment J-3, Applicable, Guidance, and Informational 

Documents L~st) 


The CEV Data and Command Dictionary shall be a sortable database that 

includes: 

a. Channelizat~on data (e.g., bus mapping, veh~cle wiring mapping, endto-end 

hardware channelizat~on (from sensor/transducer, through signal 

conditioning, and multiplexing, to f~nal destination of measurement) , 

etc.) . 

b. I/O variables. 

c. Rate group data. 

d. Raw and calibrated cal~bration sensor data 

e. Telemetry format/layout and data. 

f. Data recorder format/layout and data. 

g. Command defin~t~on (e.g., on-board, ground, test specific). 

h. Effector command information. 

i. Operational limits (e.g., max1mum/minimum values, launch commit 

criter~a information, etc.). 

j. Mapping to the CEV Nomenclature document. 

k. Sensor reference ~nformation (e.g.. measurement type, signal type, 

subsystem, installation drawing number, part number) . 







13.4 FORMAT: Electronic format per section J -2 2.3.2.1. Electronic, 

XML/XTCE-compatible. 



requl.red. 







1 

3. 

PROGRAM: CEV 

DATA TYPE 3 

6. TITLE: Avionics Design and Data Book 

2. 

4. 

5 

DRDNO.: 

DATE REVISED' 

PAGE' 

CEV-T-047 

May 2009 

1 


This DRD covers design lnformation for the CEV Avionics subsystems, 

including the Command and Data Handling, Instrumentatlon, Communication 

and Tracking, and Displays and Controls subsytems. Software design 

documentation is provided in a separate DRD. This documentation will 

provide insight into the contractor's design and analysis data, as well 

as detailed reference information to support Engineering and Operations 

throughout the life of the CEV. 

8. DISTRIBUTION' As determined by the Contracting Officer 


10. SUBMISSION FREQUENCY: Per Data Requlrements Matrix 

11. REMARKS: 

12. INTERRELATIONSHIP: Parent sow Paragraph(s): 2.6.1, 2.6.2, 2.6.3, 26.4. 

Referenced from sow Paragraph(s): 6.1.3.2, 6.2.3.2, 6.1.3.3, 6.2.3.3, 

6.1.3 4 



13.1 SCOPE: 

Design and analysis data related to the AVlonics subsystem from the 

initial trade studles, requlrements analysis, architecture, math 

modeling, functional and performance analyses, detailed deslgn, deslgn 

analysis, and operations and maintenance strategies. Document also 

covers interfaces with other CEV subsystems, software interfaces, 

external interfaces, and interfaces wlth ground/users Separate volumes 

shall be provided for each avionics subsystem, as specified below. 


CxP 70022-1 Constellation Program command, Control, Communication, and 


Interoperability Specification (and associated Children documents as 




Information (C3I) Interoperability Standards Books, Volume 2: Spectrum 

and Channel Plan 

CxP 70022-3 Constellation Program Command! Control, Communication, and 


Book 


Information (C3I) Interoperability Standards Books, Volume 4: Information 

Representation Specification (and associated Children documents as 






Crew ExploratlOn Vehic1e - (CEV) Modification 65 


Information (C3I) Interoperability Standards Books, Volume 5: Data 

Exchange Protocol Specification 

CxP 70022-8 Constellation Program Command, Control, Communicat1on, and 

Information (C3I) Interoperability Standards Books, Volume 8 Common 

Command and Control Functional requirements (and associated Children 

documents as specified 1n Attachment J-3, Applicable, Guidance, and 


CxP 70070-ANX05, Book 1, Constellation Program Functional Security 

Requirements (and associated children) 


The Avionics DRO shall contain seven volumes as follows: 

Volume I: Avionics System-Level Data 

Volume II: Command and Data Handling/Instrumentation Subsystem Data 

Volume III: Communications and Track1ng Subsystem Data 

Volume IV: Displays and Controls Subsystem Data 

Volume V: Avionics Subsystem - Constellation C31 Interoperability Report 

Volume VI: Avionics Subsystem - Constellation Security Report 

Volume VII. Software Architecture Design Data 

Volumes I - IV shall include, as applicable to the subsystem, the 

information listed below: 

1) Assumpt10ns and groundrules 

2) Subsystem Definition including architecture d1agrams and GFE vs. 

contractor-supplied assumptions 

3) Subsystem Requirements Analyses 

a. Funct10nal decomposition 

b. Funct10nal, performance and interface requirements 

c. Derived requ1rements on other systems/subsystems with analysis 

that yields the requirements 

d. Trade study results 

e. Analysis to show the subsystem meets the requirements 

4) Detailed Design Description 

a. Hardware element descr1pt10ns and principles of operation 

including description of system modes 

b. Math models 

c. Mass and volume properties 

d. Power and Thermal prof1les 

e. Schematics layouts, drawings, and 3-D solid geometric 

representat10ns of components 

f. Interface Requirements and description (internal and external 

hardware interfaces 1ncluding mechanical, electrical and thermal 

interfaces, software interfaces, and human interfaces; includes necessary 

Interface Control Documents) 

g. Bandwidth/throughput/memory/link margin analysis for hardline, 

RF, and optical data systems and processors as app11cable to subsystem 

h. Telemetry/instrumentation 

i. Consumables list 

j. Reconfiguration process 

5) Operational Analyses 

a. Operational scenarios and modes including the subsystem/s 

limitations on any aspect of vehicle flight 

b Performance and Margin analyses 

c Operating EnV1ronments (natural and induced) 

d. Fa1lure modes and redundancy operations including vehicle 

failure modes accommodated by subsystem and failure modes reacting to 

vehicle failures 

e. Fault Detection, Isolation and Recovery 

f. Diagnostic strategies including plans for 1n-flight maintenance 

g. Initialization procedures and parameters 







h. Day of launch parameters and late-load requirements 

i. Abort analysis 

j. Launch scrub turnaround plan 

k. Labeling strategy (consistent with overall CEV labeling 

strategy) 

1. Independent design and performance analyses including worst 

case timing analysls, fault tolerance and hazard 

identificatlon/mltlgatlon. 

6) Maintainability and testlng data 

a. Test requirements including information on Special Test 

Equipment design, operatlons and maintenance, if applicable. 

b. Maintainability strategies including sparing provisions, growth 

and scarring provisions, shelf-life, and long-term storage provisions 

c. Deliverable end item or equipment identification (part number) 

d. Predicted reliability assessment 

e. Component reusability/refurblshment analysis 

7) References and indication of any changes from the previous 

submission 

8) Additional Communications and Tracking Subsystem Analyses Data 

(Volume III) 

a. In addition to the information specified above, Volume III 

shall lnc1ude the following analyses reports, with each report provided 

In a separate section. Each report shall contain the following: 

1. Brief description of the analysis discipline and its 

overall function. 

2. Summary performance matrix listlng each quantitative 

parameter requirement the discipline is to satisfy against a concise 

statement of the analytically predicted performance of the parameter, 

whether or not the parameter requirement is met, and a reference to the 

location in the text where the supporting analysis is described. 

3. Supporting analyses which shall discuss all boundary 

condltions, inputs (including test data), and assumptions used; 

analytical approaches (models, equations, algorithms) used; results; and 

conclusions. 

4 In cases where computer math models or programs are 

utilized, a descrlptlon of the program along with the source code are to 

be delivered. 

b. Required Analysis Reports: 

1. Radio Frequency/Optlcal Link Margin Data book - 

Documents link margin for each RF link. 

2. RF/Optical Coverage Analysis Report - Report of RF link 

availability considerlng vehicle trajectory, antenna patterns, structural 

blockage, planet blockage, and llnk margin. 

3 Radiation Patterns - Documents planned performance at 

PDR and test measurements as available. 

4. Emitter/Receiver pOlntlng analysis - Analysls of 

antenna/laser pointing accuracy and stability considering all sources of 

pointing errors. 

5. RF/Optical Radiation analysis - Analysis to show 

RF/Optical system compliance relating to RF/Optical operations and 

constraints with the launch site, vehicles and facilities. 

6. Tracking analysis - Analysis to show that RF/Optical 

tracking systems meet system requirements. 

7. RF/Optical Interference Analysis - Prov~de analysis or 

measured data showing that no other vehicle subsystems or components 

prevent the recept10n, transmission, or operat10n of RF communication 

subsystems and components. Similarly, provlde analysis or measured data 

showing that no RF communlcatlon subsystem or components interfere with 

the proper operation of other vehlcle subsystems or components. 

8 RF link compatibility analyses - Documents the RF 

compatibility between CEV communication links and between CEV 

communication links and other interfacing elements. 







9. Power Flux Density analysis - Analysis that shows that 

all modes of operation meet Interdepartmental Radio Advisory Committee 

flux density 

volume v shall include: 

1) Description of how the CEV contractor plans to implement: 

CxP 70022-1 Constellation Program Command, Control, Communication, 

and Information (C3I) Interoperabil~ty Standards Books, Volume 1: 





and Information (C3I) Interoperability Standards Books, Volume 2: 

Spectrum and Channel Plan 



Master Link Book 



Information Representation Specification (and associated Children 





Data Exchange Protocol Specification(and associated Children 


Informational Documents List). 


and Information (C3I) Interoperability Standards Books, Volume 8 

Common Command and Control Functional Requirements (and associated 

Children documents as specified in Attachment J-3, Applicable, 

Guidance, and Informational Documents List). 

2) Provides a summation and targeted details of designs for vehicle 

systems that support command, control, and monitoring, including: 

a. Communications protocols 

b. Informat~on model content related to command, control, 

communications, and monitoring 

c. Communications framework supporting collaborative data sharing 

and distribution 

Volume VI shall include: 

1) Descript~on of how the CEV contractor plans to implement: 

- CxP 70070-ANX05, Book 1, Constellation Program Functional Security 

Requirements (and associated children) 

2) Provides a summation and targeted deta~ls of des~gns for veh~cle 

systems that support command t control, and mon~tor1ng, 1ncluding: 

a. Communications protocols 

b. Information model content related to command, control, 

communications, and monitoring 

c. Communications framework supporting collaborative data 

sharing and distribution 

Volume VII shall include: 

System arch~tectural des~gn. Th~s sect~on shall be divided into 

the following paragraphs to describe the CEV System architectural design. 







If part or all of the design depends upon CEV System states or modes, 

this dependency shall be indicated. If design information falls into 

more than one paragraph, it may be presented once and referenced from the 

other paragraphs. Design convent~ons needed to understand the design 

shall be presented or referenced. 

NOTE: For brevity, this sect~on is written in terms of organizing a 

system directly into Computer Software Configuration Items (CSCIs), and 

manual operations, but shall be interpreted to cover organizing a system 

into subsystems, organlzlng a subsystem into CSCIs, and manual 

operations, or other variations as appropriate. 

1. System components. This paragraph shall: 

(a) Identify the components of the system (CSCIs and manual 

operations). Each component shall be assigned a project-unique 

identif~er. Note: a database may be treated as a CSCI or as part of a 

CSCI. 

(b) Show the static (such as 'consists of') relationship(s) of the 

components. Mult~ple relationships may be presented, depending on the 

selected design methodology. 

(c) State the purpose of each component and ~dentlfy the System 

requirements and systemwide design declsions allocated to it. 

(d) Identify each component's development status/type, if known 

(such as new development, existing component to be reused as is, existing 

design to be reused as is, existing deslgn or component to be 

reengineered, component to be developed for reuse, component planned for 

Build N, etc.) For existlng design or components, the description shall 

provide 1dentifying information, such as name, version, documentation 

references, location! etc. 

(e) For each computer system or other aggregate of computer 

hardware resources identlf~ed for use in the System, describe its 

computer hardware resources (such as processors, memory, input/output 

devices, auxiliary storage, and communications/ network equipment). Each 

description shall, as applicable, identify the configuration items that 

will use the resource, descrlbe the allocation of resource util~zation 

with associated margin to each CSCI that will use the resource (for 

example, 20% of the resource's capacity allocated to CSCI 1, 30% to CSCI 

2), describe the conditions under which utilization will be measured, and 

describe the characterlstlcs of the resource. 

2. Concept of execut~on. This paragraph shall describe the concept of 

execution among the system components. It shall include diagrams and 

descriptions showing the dynamic relationship of the components, that is, 

how they will interact during System operation, including, as applicable, 

flow of execution control, data flow, dynamically controlled sequencing, 

state transition diagrams, tlm~ng diagrams, priorities among components, 

handllng of interrupts, timing/sequenclng relat~onships, exception 

handling, concurrent execution, dynam~c allocation/deallocation, dynamic 

creation/deletion of objects, processes, tasks, and other aspects of 

dynamic behavior. 

3. Interface design. Th~s paragraph shall be divided into the 

followlng subparagraphs to describe the interface characteristics of the 

system components. It shall include both interfaces among the components 

and their interfaces with external entities such as other systems, 

configuration items! and users. Note: There is no requirement for these 

interfaces to be completely designed at this level; this paragraph is 

provlded to allow the recording of ~nterface design decisions made as 

part of system architectural design. If part or all of this information 

is contained elsewhere, these sourCes may be referenced. 

(a) Interface ident~f~cation and diagrams. This paragraph shall 

state the project-unique identifier ass~gned to each interface and shall 

identify the interfacing entities (systems, configurat~on items, users, 

etc.) by name, number, version, and documentation references! as 

applicable. The identification shall state which entities have fixed 







interface characteristics (and therefore impose interface requirements on 

interfacing entities) and which are being developed or modified (thus 

hav~ng interface requirements ~mposed on them). One or more ~nterface 

diagrams shall be provided, as appropriate, to depict the interfaces. 

(b) project-unique ~dentifier of interface. Th~s paragraph shall 

ident~fy an interface by project-unique identifier, shall briefly 

identify the interfacing entities, and shall be divided into 

subparagraphs as needed to describe the interface characteristics of one 

or both of the interfac~ng entities. If a given ~nterfacing entity is 

not covered by this ADD (for example, an external system) but its 

interface characteristics need to be mentioned to describe interfacing 

entities that are, these characteristics shall be stated as assumptions 

or as 'When [the ent~ty not covered] does this, [the entity that is 

covered] w~ll .... ' This paragraph may reference other documents (such 

as data dictionaries, standards for protocols, and standards for user 

interfaces) in place of stating the information here. The design 

description shall include the following, as applicable, presented in any 

order suited to the information to be provided, and shall note any 

differences in these characteristics from the point of view of the 

interfacing ent~t~es (such as different expectations about the size, 

frequency, or other characteristics of data elements) : 

(1) priority assigned to the interface by the interfacing 

entity(ies) . 

(2) Type of interface (such as real-time data transfer, storageand-retrieval 

of data, etc.) to be implemented. 

(3) Characteristics of indiv~dual data elements that the 

interfacing entity(ies) will prov~de, store, send, access, receive, etc. 

(e.g., identifiers, data type I size, format! range, accuracy, etc.). 

(4) Characteristics of data element assemblies (records, messages, 

files, arrays, displays, reports, etc.) that the ~nterfacing entity(ies) 

will provide, store, sendt access, recelve, etc. (e.g., identifiers, data 

elements, medium, visual and auditory characteristics, etc.). 

(5) Characteristics of commun~cation methods that the interfacing 

entity(ies) will use for the Interface (e.g., identifiers, links/bands, 

formatting, transfer rates, etc.) 

(6) Characteristics of protocols that the interfacing entity(ies) 

will use for the interface (e.g., identifiers, priority/layer, error 

control, packet~ng, synchronizat~on, etc.). 

(7) Other characteristics, such as physical compatibility of the 

interfacing entity(ies) (dimensions, tolerances, loads, voltages, plug 

compatibility, etc.). 

13.4 FORMAT: Electronic format per section J-2 2.3.2.1. 

13.5 MAINTENANCE· Changes shall be ~dentified and complete re-issue of the 








1. 

3. 

PROGRAM: CEV 

DATA TYPE. 1 

2. 

4. 

5 

6 TITLE: Software Requlrements Specification 

DRDNO.: 

DATE REVISED' 

PAGE 

CEV-T-048 

May 2009 

1 


A document which defines and records the software requirements to be met 

by a computer software configuration item (CSCI). This document 

specifies the requirements for a CSCI and the methods to be used to 

ensure that each requlrement has been met. This document forms the basis 

for design and qualification testing of a CSCI. In addition, this 

document wlll lnclude the display format dictionaries in the display 

software SRS as speclfled in section 13.3 below. 

8. DISTRIBUTION: As determlned by the Contracting Officer. 



11. REMARKS: 

Requirements pertaining to the CSCI's external interfaces may be 

presented in the Software Requirements Specification (SRS) or in one or 

more Interface Requirements Speclflcations (IRS's) referenced from the 

SRS. 



Standard ISO/lEe 12207: 1995, Standard for Information Technology - 

Software life cycle processes 

IEEE/EIA 12207.1-1997 Industry Implementatlon of International 


Software life cycle processes - Llfecycle data 


Referenced from SOW Paragraph(s): 2.5, 2.6.15, 6.1.3.15, 6.2.3.15, 

6.4.3.15 

Related DRD(s): CEV-O-008, CEV-T-035 


13.1 SCOPE: 

The Software Requlrements Specification detalls the software functional, 

performance, interface, operational, and quality assurance requirements. 


NPR 7150.2: NASA Software Engineering Requirements (all shall 

statements/the compllance matrix only, excluding the software safety 

requiremen t) 

13.3 CONTENTS. 

In accordance with NPR 7150 2 NASA Software Englneering Requirements, and 

using IEEE/EIA 12207.1-1997 as gUldance, the Software Requirements 

Specification shall contain. 

a. System overview. 

b. CSCI requirements. 

1. Functional requirements. 

2. Required states and modes. 

3. External lnterface requirements. 







4. Internal interface requirements. 

5. Internal data requirements. 

6. Adaptation requirements. 

7. Safety requirements. 

8. Performance and timing requirements 

9. Security and privacy requirements. 

10. Environment requirements. 

11. computer resource requirements. 

(a). Computer hardware resource utilization requirements. 

(b). Computer software utilization requirements. 

(c). Computer communications requirements. 

12. Software qual1ty characteristics. 

13. Design and implementation constraints. 

14. Personnel-related requirements 

15. Training-related requ1rements. 

16. Logistics-related requirements. 

17. Packaging requ1rements. 

18. Precedence and criticality of requirements. 

19. Operations requirements, including flight-to-flight 

reconfiguration. 

c. Qualification provisions. 

d Requirements traceability and verification method data. 

e. Requirements partition1ng for phased del1very. 

f. Testing requirements that dr1ve software design decis10ns; e.g., 

special system level timing requirements/checkpoint restart. 

In addit10n to the above requirements, the display software SRS shall 

contain an appendix that serves as the display format dictionary to 

document the results of the d1splay format prototyping activity. At the 

discretion of the contractor, each format may be documented in a separate 

appendix. The Display Format Dictionary Appendix shall document the 

results of the display proto typing effort which includes the following 

information at a minimum: 

• Scope 

• Introduction 

• The following information for each display format: 

o General d1scuss10n on the purpose of the display format and its 

associated operat1onal concept (i.e. applicable mi~sion phase or 

scenario) . 

o Graphical representation of each format (may include multiple 

images to cleary reflect mission/phase tailoring or other moding 

behavior) . 

o 

o 

o 

Detailed description of each graphical object 

Description of the dynamic behavior of each dynamic graphical 

object and/or command on the format 1nclud1ng states, limits, 

modes, decluttering, etc, as applicable. 

Required input and output data parameters and data rates, 

including source/destination for each input/output parameter. 

13.4 FORMAT: Electron1c format per Section J-2 2.3.2.1. 

13 5 MAINTENANCE: Contractor-proposed changes to this document shall be 


required with changes clearly identif1ed. 







1. 

3. 

6. 

7. 


DATA TYPE' 1 4 DATE REVISED. May 2009 

5. PAGE 1 

TITLE: Radlo Frequency/Optical ICDs 

DESCRIPTIONIUSE. 

RF/Optical Interface Control documents define the end to end 

communlcations interfaces between CEV and other Constellation Systems 

(lncluding CEV equipment on ISS, and Communlcation and Tracklng Networks 

(CTN) under Space Communicatlons and Navigation (SCAN)). NASA will use 

these ICDs to ensure that all interfaces are compatible and interoperable 

with other Constellation Systems, ISS and communications infrastructure. 




11. REMARKS: 

These documents shall be conslstent with the Constellation Program's 

integrated plans such as CXP-70022, Volumes 1, 2, 3, 4, 5, and 8, 

Constellation Command, Control, Communication, and Information (C3I) 

Interoperablllty Specificatlon (and associated Children documents as 

specified in Attachment J-3, Appllcable, Guidance, and Informational 

Documents List). 

12 INTERRELATIONSIDP: Parent sow Paragraph (s): 2.6.3. 

Referenced from SOW Paragraphs: 6.1.3.3, 6.2.3.3 


13.1 SCOPE' 

RF/Optical ICDs shall be developed for all communlcations links (Space to 

Space and Space to Ground). NASA will lead the development of the 

RF/Optical ICDs with participation from other Constellation Systems, ISS 

and SCAN. Contractor shall participate in the development of the 

RF/Optlcal ICDs. The Contactor shall generate, maintain and 

configuration manage the ICD. After the ICD is baselined, the Contractor 

shall generate change requests for any changes and submit for NASA 

approval. 

At the contractor's discretion, the lCD's can be delivered in different 

volumes - For example, a volume for CEV-CTN lnterface, a volume for CEV 

LSAM interface, etc. 

13 2 APPLICABLE DOCUMENTS 

450-SNUG. Space Network Users' GUlde 












Information (C3I) Interoperability Standards Books, Volume 2: Spectrum 

and Channel plan 



Book 

CxP 70022-4 Constellatl0n Program Command, Control, Communication, and 

Information (C3I) Interoperability Standards Books, Volume 4: Information 

Representation Specification (and assoclated Children documents as 




Informatlon (C3I) Interoperablllty Standards Books, Volume 5: Data 

Exchange Protocol Specification 


Information (C3I) Interoperability Standards Books, Volume 8: Common 

Command and Control Functional Requirements (and associated Children 

documents as speclfied in Attachment J-3, Applicable, GUldance, and 

Informational Documents L1St) 

CxP 70118, Volume 1: Constellatl0n to Communicatl0ns and Tracking 

Networks Interface Requlrements Document, Volume 1 - CEV. 

CxP 70028 CEV to GS IRD 

CxP 70029 CEV to MS IRD 

CxP 70031 CEV to ISS IRD 

CxP 70034 CEV to LSAM IRD 

ICD-GPS-200: Navstar GPS Space Segment/Navigation User Interfaces 

13.3 

CONTENTS· 

The RF/Opticals ICD shall start at Layer 2 (Data Link Layer) for 

transmisSlon end and end at Layer 2 (Data Link Layer) on receivlng end. 

RF link compatibility analyses - Documents the RF compatibility and 

detalled communication lnterfaces between CEV communication links and 

between CEV communication links and other interfacing elements 

The RF/Opticals ICD shall detail the characteristics of the RF 

communication channel between the CEV, ground stations, Communication and 

Tracking Network, (ISS) and other Constellation Systems including: 

- Frequencies of operation 

- Modulation & Channel Coding 

- Transmitter powers, receiver noise temperatures and antenna 

polarization and performance 

- Data formats, frame synchronization, forward error correction coding 

- Data link layer consisting of framlng and link establishment, and 

negotiation protocols. 




required, wlth changes clearly identified. 







1 

3. 

6. 

7 

PROGRAM: CEV 2 DRDNO.: CEV-T-059 


5. PAGE 1 

TITLE: Electrical Power System (EPS) Deslgn and Data Book 


Documents the power system deslgn, including the lnput assumptions, the 

analytical methods used, the results of the analyses and the comparison 

to appllcable quantitatlve requirements. The comprehensive equipment 

documentation will provide detailed reference information to support 

Engineering and Operations throughout the life of the CEV. 

8. DISTRIBUTION As determined by the Contractlng Officer. 



11 REMARKS' 

12. INTERRELATIONSHIP: Parent SOW Paragraph(s): 2.6.5 .. 

Referenced from SOW Paragraphs: 6.1.3.5, 6.2.3 5, 6.4.3.5 


13.1 SCOPE. 

The Electrical Power System Deslgn and Data Book documents the results of 

design, development, and other pertinent studies relating to the 

electrical power system, includlng all power generation, storage, and 

distribution/control equlpment, circuit protection, interior and exterior 

vehicle lighting, and interfaces for ground, mated vehicles, payloads, 

and portable equipment End-to-end functl0nal schematics, engineering 

drawings, and associated lists shall be utilized to the maximum extent 

possible in performing and providing analysis reports. 



volume 1 - Electrical Power System Circuit Protectlon and 

Isolation Plan 

plan and provisions for establlshing, and maintalnlng electrical 

circuit protection for the CEV and CEV interfaces (including human 

safety) with ground maintenance/test facilities, launch 

facilities, in-flight vehicles, recovery, and re-furbishment 

facilitles. Crewed, EVA, and uncrewed operations for both 

'ground' and 'in-fl1ght' activities such as monitoring, testing, 

diagnostlc, safing, fault recovery, and maintenance shall be 

addressed. 

Volume 2 - Electrlcal Power System Requlrements and Design 

Analys2s Reports 

The deliverable shall 2nclude' 

1) Assumptions, groundrules 

2) Subsystem Definit20n 


a. Functional decomposit2on 

b. Functional, performance, and interface requirements 


CEV -T -059 Page 1 on



c. Derived requirements on other systems with analysis that 

yields the requirements 

d. Trade studies results 

e. Analysis to show the subsystem meets the requirements. 

In cases where computer math models or programs are utilized, a 

description of the program along with the source code shall be 

made available to NASA. The following analyses shall also be 

documented: 

1. Electrical Power System Circuit Protection and 

Fault Analyses - Documents the circuit protection analys~s results 

to determine correct circuit protection size and trip 

characteristics. Documents the proper circuit protection sizing 

that is verified by comparing source fault current with wiring and 

c~rcu~t protection specifications. Documents the fault analysis 

in which worst case faults are considered from the standpoint of 

safety or mission compromise to determine if power and circuit 

redundancy is adequate and to assure that there are adequate 

circuit protection margins to preclude upstream fault propagation. 

Documents the analys~s of both line-to-ground and line-to-line 

faults. 

2. Electrical Power System Grounding Analysis - 

Documents the electrical grounding design. Documents the analysis 

results of the electrical grounding design and consistency with 

the performance specifications of the various interfacing elements 

during all phases of ground testing and mission flights. 

3. Electrical Power System Voltage Drop Analysis - 

Documents the analysis results using circuit resistance values 

based on w~re s~ze, wire length, temperature conditions, circuit 

element resistances, and varying load conditions. Documents 

voltage drops on all major c~rcu~ts, loads, and interfaces at 

varying load conditions 

4. Electr~cal Power System Transient Analyses - 

Documents the analys~s results using normal and worst case 

subsystem and system interface conditions (voltage and bus 

transient and ripple), evaluates the design for proper performance 

and compatibility, and assures adequate margins between the source 

and the loads. Also documents the evaluation of power on/off 

switching transient generation for adverse (out-of-spec.) impacts 

to the interfac~ng bus. 

Volume 3 - Electr~cal Power System Architectural Notebook 

Documents the EPS architectural connectivity for all vehicle 

configurations. 

1) This volume shall ~nclude connectivity schematics of: 

a. Power generation, power storage, and 

distribution/control equipment to each other and to each 

electrical consuming equipment, including interior and exterior 

l~ght~ng 

b. Internal and external interfaces for ground 

support, portable equipment, payloads, mated vehicles, and human 

interfaces 

c. Activation/deactivation architecture, dead-facing 

term~nat~on, as well as any temporary or contingency EPS jumpers 

(includes hardware utilizat~on descrlptlon) 

d. Thermal and command/data connectivity to the EPS 

devices. 

e. CEV Electrical Power Consum~ng Equipment List with associated 

power mode and ~ntegration of power channel connectivity data to 

wiring database. 

Volume 4 - Electrical Power System Equipment Description and Performance 

Data 

Comprehensive equipment documentation of the EPS hardware to provide 







detailed reference informatlon for supporting Engineering and Operations. 

1) Detailed Design Description of each EPS devlce shall include: 

a. Hardware descrlption with functional block diagrams 

b. Internal and external hardware interfaces including mechanical, 

optical, electrical, thermal interfaces, software lnterfaces, and human 

interfaces 

c. Mass and volume properties 

d. Equipment location 

e. Hardware math model (where applicable) 

f. Consumables (if applicable) 

g Data bandwidths (data rates); Telemetry; Instrumentation 

descriptlon 

2) Operational Description of each EPS ORU shall include: 

a. Operatlonal modes including default and commanded states 

b Power and thermal profile for each operational mode 

c. Performance and margin capablilty 

d. Natural and lnduced operating and non-operatlng environments 

(examples: min/max pressure and temperature) 

e. Basic summary of operational activation/deactivation procedures 

and limitations 

f. Initialization procedures and parameters 

g. Day of launch parameters and late-load requirements 

h. Launch scrub turnaround procedures 

l. Failure modes and redundancy operations including vehicle 


vehicle failures (includes abort saflng procedures) 

j. Fault Detection, Isolation and Recovery 

k. Diagnostlcs strategies including plans for In-fllght 

maintenance 

1. Labeling strategy (consistent with overall CEV labellng 

strategy) 

3) Maintainability and testlng data shall include: 

a. Test requirements including informatlon on Special Test 

Equipment deslgn, operations and maintenance. 

b. Maintainability strategles lncluding sparing provisions, growth 

and scarring provisions, shelf-life, and long-term storage provisions 

c. Deliverable end item or equipment identification (part number) 

d. Predicted rellablilty assessment 

e. Component reusabillty/refurbishment analysis 

13.4 FORMAT: Electronlc format per Section J-2 2.3.2.1. 

13 5 MAINTENANCE: Contractor-proposed changes to this document shall be 


required. 







1. 

3. 

PROGRAM: CEV 

DATA TYPE. 1 

2 

4 

5. 

DRDNO.· 

DATE REVISED: 

PAGE: 

CEV-T-060 

May 2009 

1 

6. TITLE: Electrical Power Quality Specification Requirements Annex 

Documents 


Establishes the unique electrical power quality and compat~bility 

requirements for the power source interfaces and for the 

~ntegrated/portable electrical load interfaces for the CEV. The 

electrical power quality specification requirements annexes define CEV 

specific power characteristics and the m~n~mum performance and test 

requirements for loads to be compatible w~th these characteristics. 




11. REMARKS: 

This document must be consistent with the Constellation program's 

integrated plans. 

12 INTERRELATIONSHIP: Parent SOW Paragraph(s): 2.6.5. 

Referenced from SOW Paragraphs: 6.1.3.5, 6.2.3.5, 6.4.3.5 


13.1 SCOPE: 

The electrical power quality and compatibility specification requirements 

establish the unique power quality interface requirements for the CEV and 

the CEV power ~nterfaces to ground test facilities, portable loads, and 

other mated vehicles 


CxP 70050-01 Volume 1: Electrical Power Quality Performance for 28 Vdc 

and CxP 70050-02 Volume 2: User Electr~cal Power Quality Performance for 

28 Vdc. 

13.3 CONTENTS 

For each major type of distributed power, two electr~cal power quality 

and compatibil~ty specification requirement volumes shall be generated as 

Annexes to the CxP 70050-01 volume 1: Electrical Power Quality 

Performance for 28 Vdc and CxP 70050-02 Volume 2' User Electrical Power 

Quallty Performance for 28 Vdc. The f~rst volume shall define the power 

source interface(s) and compatibility requirements, and the second volume 

shall define the integrated/portable load





1. 

3. 

PROGRAM: CEV 

DATA TYPE. 2 

6 TITLE Fracture Control plan 

2. 

4 

5. 

DRDNO.: 

DATE REVISED: 

PAGE' 

CEV-T-069 

May 2009 

1 

7. DESCRIPTION/USE' 

The Fracture Control Plan shall define the elements of the fracture 

control program and the associated management and control 

responsibilities. 

8 DISTRIBUTION: As determined by the Contracting Officer, and at a minimum 

shall include the Responsible Fracture Control Authority (RFCA). 



11. REMARKS: 

12. INTERRELATIONSHIP' Parent sow Paragraph(s): 6.2.6 



13.1 SCOPE: 

The Fracture Control plan will provide hardware-specific ~nformation 

detail~ng how applicable fracture control requirements w~ll be 

implemented to prevent catastrophic failure of hardware associated with 

the propagation of cracks or crack-like defects. 


- NASA-STD-(I)-5019: Fracture Control Requirements For Spaceflight 

Hardware 


The fracture control plan shall provide hardware-specific details 

explaining how fracture control requirements and procedures will be 

implemented. The plan shall describe the various fracture control 

approaches that will be applied to all relevant hardware and shall 

address cracks and crack-like defects that may be present during 

fabrication, testing, handling, transportation, and operational life. The 

plan shall contain a listing of all Fracture Critical hardware and parts 

in accordance with NASA-STD-(I)-5019. The plan shall address how 

fracture critical parts that are susceptible to damage such as impact, 

corrosion, material degradat~on, and wear, etc. will be identified. The 

plan shall identify organizational elements and their responsibilities 

for activities required to ~mplement the Fracture Control Plan, including 

reVlews of design and structural lntegrity analyses, configuratl0n 

control, and generation of required documentation such as DRD CEV-T-070, 

Fracture Control Summary Report. 

13.4 FORMAT: Electronic format per Section J-2 2.3.2.1. Microsoft® 

Word/Excel® based, XML, and ASCII, del~mited for data. 







13.5 MAINTENANCE: contractor-proposed changes to this document shall be 


required. 







1. 

3. 

PROGRAM: CEV 

DATA TYPE' 2 

6. TITLE: Fracture Control Summary Report 

2 

4. 

5. 

DRDNO .. 

DATE REVISED: 

PAGE: 

CEV-T-070 

May 2009 

1 

7 DESCRlPTlONIUSE: 

The Fracture Control Summary report is used to demonstrate compliance 

with fracture control requirements 

8. DISTRIBUTION' As determined by the Contracting Officer, and at a minimum 

shall include the Responsible Fracture Control Authority (RFCA). 



11 REMARKS. 

12. INTERRELATIONSHIP' Parent SOW Paragraph(s): 6.2.6 



131 SCOPE' 

The Fracture Control Summary Report will provide detailed hardwarespecific 

fracture control analyses and test reports, demonstrating 

compliance with all applicable fracture control requirements. 

13 2 APPLICABLE DOCUMENTS 

NASA-STD-(I)-5019: Fracture Control Requirements For Spaceflight Hardware 


The report shall comprlse an accounting of all assessed hardware and the 

basls for determinlng fracture control acceptabillty for each. 

Supporting detailed documentatlon such as drawings, calculations, 

analyses, data printouts, inspection plans, records, specifications, 

certifications, reports, and procedures should be submitted as a part of 

the FCSR, but shall be made available for review if requested. 

As a minimum, the following lnformation shall be provided in the FCSR: 

a. Identification of fracture-crltlcal parts and low-risk fracture 

parts, showing the material and heat treatment used and the basis for 

part acceptability (i.e., damage tolerant analysis, test, acceptable 

durability, insignlficant fatigue loading), including the referencing 

of documents which contaln and describe the supporting data required 

to demonstrate fracture control requ~rements of the Agency, 

responsible Center, and Program: 

(1) Fracture-crltlcal parts that are limited life shall be 

specifically identified. 

(2) A statement to the effect that all other parts were examined 

and determined to be non-fracture critical shall be included. 

b A statement as to whether or not the hardware contains pressure 

vessels or fracture-critical rotating equipment. 

c. Identification of the NDE and/or tests applied for fracture 

control purposes to each fracture-critlcal part. 


CEV-T-070Page 1 of2





d Identification of fail-safe parts and a brief statement of the 

basis for classlflcation. Re-flown fall-safe hardware shall have 

verification that any required "between mission" inspections have 

been performed. 

e. A statement that inspections or tests specified for fracture 

control were applied. 

f. A statement that the flight hardware configuration has been 

controlled and verified for all fracture-critical parts. 

g. A statement that materlals usage has been verified for fracturecritical 

parts. 

h. Copies of MUAs for fracture-critical or low-risk parts and a 

summary of the dlscrepancy reviews, or equivalent reviews, of 

anomalies that could affect the performance of fracture-critical 

parts. 

i. If applicable, a summary dlscussion of alternative approaches or 

specialized assessment methodology applied, but not specifically 

covered by guidelines. 

J. If applicable, identlflcation of any special considerations 

involving fracture mechanics properties or data, inspections, 

analysis, or other parameters not covered by the requirements set 

here. 

k. If during the program, no parts or procedures are identifled that 

require informatlon as listed above, a statement to that effect with 

reference to supporting documentation shall be submitted as the FCSR. 

The Contractor shall keep documents supporting the Fracture Control 

Summary Report for the life of the hardware. 

13.4 FORMAT: Electronic format per Sectlon J -2 2.3.2.1. Microsoft® 

Word/Excel® based, XML, and ASCII, dellmited for data. 


submitted to NASA for approval. Complete re-lssue of the document is 

required 







1. 

3. 

PROGRAM. CEV 

DATA TYPE. 3 

2. 

4. 

S. 

6. TITLE: Propulsion Systems Design and Data Book 

DRDNO.· 

DATE REVISED: 

PAGE. 

CEV-T-071 

May 2009 

1 


This documentation is requlred For each unique prop systems (LAS, SM, 

CM), which includes compilation of requirements, design, analysis, test 

reports and operational lnformation: including abort & abort reorientation, 

separation, trajectory insertion, orbital maneuvering, and 

translation and rotation reaction control. This documentation will 

provide insight into the contractor's designs, as well as detailed 

reference informatlon to support Engineering and Operations throughout 

the life of the CEV. 

8 DISTRIBUTION: As determined by the Contractlng Officer. 

9. INITIAL SUBMISSION: Per Data Requlrements Matrix 


11. REMARKS 


CPIA 655: Guidelines for Combustion Stabillty Specifications and 

Verification Procedures for Liquid Propellant Rocket Englnes 

CPIA 469: Principles of Solid Propellant Development. 

12. INTERRELATIONSHIP. Parent sow Paragraph(s): 2.6.10. 

Referenced from sow Paragraphs: 6.1.3.10, 6.2.3.10, 6.4.3.10 

Related DRD(s): CEV-T-OS1 


13.1 SCOPE: 

This set of documents contains the results of design, development, and 

other pertinent studles relating to the various propulsion systems. 

Separate volumes shall be developed and maintained for each unique 

propulsion system on the CEV. 


AIAA-S-OSO: AIAA Standard for Space Systems - Metallic Pressure Vessels, 


AIAA-S-OS1 AIAA Standard for Space Systems - Composite Overwrapped 

Pressure vessels 


Each volume shall include propulsion subsystem information including, but 

not limited to 

1. Subsystem Requlrements Analysis 

(a) Assumptions and groundrules 

(b) Functional decomposition 

(c) Functional, performance, life and interface requirements 

(d) Integrated system level trade studies and subsystem models lncluding 

model assumptions, model technique, input and output data and resulting 

wet/dry mass, power, and volume allocations 

(e) Performance of CEV durlng operation of propulsion sub-systems 

2. Detailed Design Description 







(a) Fluid, electrical, and instrumentation schematics and layouts 

(b) Propulsion performance calculations including fluid, ballistics, 

propellant mean bulk temperature, manufacturing & processing variations, 

thermal and pressure varlation effects. These data need to provided over 

the full range of operational enVlroments for the given system. 

(c) Propulsion Pressure System description: document the design, 

analysis, fabrication, test, inspectlon, operation and maintenance of all 

vessels, lines/ducts/fittings and components, (including external 

components required for operation of the systems such as initiators & 

associated cables for solid motors), as well as the integrated subsystem 

and its assemblies. Included shall be a complete description, material 

properties, drawings, schematlcs, flnite element analysis results (static 

and dynamic loads), factor of safety margins, debris generation & impact 

assessment/mitigation plan, deslgn verification plan and damage control 

plan as appllcable 

(d) Thruster/Engine/Motor deslgn descrlptions and combustion stability 

assessments addressing cycle life and accumulated hot fire duration, 

thermal soak-back wlth environmental effects, restart capability, bubble 

ingestion, propellant saturation effects, propellant formulations; 

mechanical properties of propellants, liner, & lnsulation; ballistics 

propertles of propellants (including but not limited to temperature & 

pressure sensitivities, burn rates, applicable solid propellant 

coefficients & exponents, etc.); definition of types of non-metallic 

materials & their formulas for various appllcations (including but not 

limited to throat inserts, insulation, liner); graln geometries; 

manufacturlng & processing plans for solid motors, valve cycle life, and 

engine/thruster duty cycles limitations as well as required operational 

duty cycle spectrums with associated accumulated durations, fulfilment of 

mission derived detailed performance and operational capabilities 

(including, but not limited to vibration, shock, temperature, aging, 

humidity, salt fog, steady-state and pulse mode Isp and impulse bit 

capablllty over all possible operational conditions) with adequate 

margins for the full range of expected and possible operating conditions 

and life capabilities, and combustion stability, all with correlations to 

test results and corrections for the flight design application 

(e) Component/line sizing including system pressure flow loss 

calculations, nozzle / bore / eXlt area ratio calculations including 

analyses of internal ballistics & fluid flow, pressurant blow down models 

and filtration capacity/sizing analysis, with correlations to test 

results and corrections for the flight design application 

(f) Propellant acquisition and tank discharge analyses under all expected 

operating and mission environments, with correlatlons to test results and 

corrections for the flight design application 

(g) Fluid and solid system transient analyses including activation, 

ignition interval (time to steady state thrust), firing, and safing for 

nominal and contingency modes, with correlations to test results and 

corrections for the flight design application 

(h) Thermal condltioning and maintenance analysis including propellant 

storage quality, feed system and motor/engine/thruster/igniter thermal 

condltlonlng, and bOll off losses for the allowable hot and cold 

envlronmental conditlons as applicable, with correlations to test results 

and corrections for the flight design application 

(i) Component design information including vendor component drawings and 

cross-sections, material usage list, stress analysis and thermal analysis 

(including safety factors, derating factors, safety margins and 

rationale), any test reports (including addressing adequate margin for 

required life capabilities), mill reports, NDE reports, or burst article 

or qualification test reports that may be available, as well as 

development, qualification, and production schedules and associated 

information 

(j) Propellant compatlbillty assessment and associated data lncluding 

exposure duration, propellant vapor migration, corrosion, embrittlement, 

decomposition and leaching effects, hardening, aging effects, humidity 







effects, deterioration of sol1d propellant to liquid phase, with 

correlations to test results and corrections for the flight design 

appl1cat10n 

(k) Instrumentation l1st for flight system and support equipment include 

sensor, range, units accuracy, drift, and sample rate. Provide details, 

models, flight algorithms and associated uncertaint1es for calculated 

quant1ties such as fluid quantity gauging, with correlations to test 

results and corrections for the flight design application 

(1) Overpressure protection design and analysis addressing worst case 

failure conditions and thermal environments, define MDP/MEOP for the 

system with associated rationale and analyses, with correlations to test 

results and corrections for the f11ght design application 

(m) Interface definition (internal and external hardware and subsystem 

interfaces including physical, mechan1cal, electrical and thermal 

interfaces, software interfaces) 

(n) Propulsion system requirements vs. capabilities summary with 

supporting rat10nale and explanations 

(0) Reliability assessment process overview and assumptions as well as 

reliability analysis and process for verifying reliability 

(p) Shelf life and long term storage assessment and rationale 

(q) Useful life assessment and rationale, and disposal approach as 

applicable 

(r) Simulation tool description, source algorithms/code and validation 

report, including benchmarks of test results against model prediction(s), 

cross system operational 1mpacts design, analyses, & performance 

assessments including but not limited to translation of structural 

frequencies, effects of solid motor plume impingement, etc. 

3. Verification Activities not already 1ncluded in the Master 

Verification DRD(s) 

(a) Subassembly, assembly, and system verification article(s) detailed 

design description(s), addressing all engineering deliverables (drawings, 

models, schematics, hardware configuration and selection, interface 

requirements and designs, associated analyses and results, manufacturing, 

assembly, process1ng plans (including non-metallic components such as 

propellants), 1nstallation, and checkout plann1ng, schedules and 

requirements, test instrumentation, etc.), differences from the flight 

configuration and operat10nal conditions and associated rationale(s) 

(b) Flight propulsion system(s) checkout sequencing and associated 

checkout requirements, setup cond1tions, constraints and details, and 

pass/fail criteria as well as associated verification results 

(c) Interface verification approaches and verif1cation results 

(d) Fracture control reports for all propulsion system fracture critical 

hardware, in accordance w1th the Fracture Control Plan DRD 

(e) Cross system operational impacts verification approaches & results 

4. Test plans and Reports not already included in the Master 

Verification DRD(s) 

(a) Development test plans and test reports at the component, assembly 

and system levels 

(b) Propuls1on System Hot Fire and Thermal Conditioning Test Plants) and 

Test Report(s) 1ncluding the test scope, required schedule milestones, 

test obJectives and rationale, test article architecture, 1nstrumentation 

requirements, data acqu~s1t10n requirements, fac111ty requirements, fluid 

requirements, participant roles and responsibilities, a test matrix 

identifying test art1cle configurations, test parameters, test durations, 

number of tests, success criteria, data format requirements, and a 

discussion of how the test data will be interpreted to satisfy the test 

objectives. Raw test data shall be made available to NASA. Reports shall 

document the results of the tests and an assessment of integrated system 

performance, d1fferences from the flight configuration and operat1onal 

conditions and associated rationale(s) and and corrections for the flight 

des1gn application. 





(c) Acceptance test data not 

Package capturing all flight 

component level. 



already included in the Acceptance Data 

system acceptance results down to the 

5. Operatlonal Analyses 

(a) operational scenarlOS and modes including the subsystem's 

llmltations on any aspect of vehicle fllght 

(b) Performance and Margln analyses 

(c) Operatlng Environments (natural and induced) 

(d) Failure modes and redundancy operations including vehicle failure 

modes accommodated by subsystem and failure modes reacting to vehicle 

failures 

(e) Failure detectlon, isolation and recovery design details including 

diagnostic methods and controls with supporting data, correlations to 

test results and corrections for the fllght design application and 

rationale 

(f) Component reusability/refurbishment/recertification analysis and 

maintainability strategy (if applicable) 

(g) Dlagnostic strategies includlng plans for in-flight malntenance 

(h) Initiallzation procedures and parameters 

(l) Day of launch parameters and late-load requirements 

(j) Abort analysis 

(k) Launch scrub turnaround plan 

6) Maintainability and testing data 

(a) Test requirements including lnformation on Special Test Equipment 

design, operations and malntenance. 

(b) Maintainabillty strategies including sparing provisions, growth and 

scarring provisions, shelf-life, and long-term storage provisions 

(c) Deliverable end item or equipment identification (part number) 

(d) Predlcted reliability assessment 

(e) Component reusability/refurbishment analysis 

(f) A record of all test failures, anomalies, and accldents involving 

qualification or potential flight hardware that are not documented in 

PRACA reports. 

(g) The results of all verification testing, analyses, and inspections 

not documented in other test or certlfication reports, lncluding a 

narrative explanation of how the testlng, analysis and inspection results 

obtained satisfy the verificatlon requirements 

Content of each submittal must be sufficient to satlsfy the objectives of 

the milestone review for which it is submitted. 

13.4 FORMAT· Electronic format per Section J -2 2.3.2.1. 

13.5 MAINTENANCE: Changes shall be identifled and complete re-issue of the 








1. 

3. 

PROGRAM. CEV 

DATA TYPE' 3 

2. 

4. 

5. 

DRDNO .. 

DATE REVISED. 

PAGE: 

CEV-T-073 

May 2009 

1 

6. TITLE: Environmental Control and Life Support Design and Data Book 


Documentation for design information for vehicle Environmental Control 

and Life Support systems (ECLSS) including vehlcle Active Thermal Control 

Systems (ATCS). NASA will use this information as a source for insight 

into the contractor's design of the vehicle ECLSS and ATCS. 

8 DISTRIBUTION' As determined by the Contractlng Offlcer. 

9. INITIAL SUBMISSION: Per Data Requuements Matrix 


11. REMARKS. 


MIL-STD-810F: DOD Test Method Standard for Environmental Engineering 

Considerations and Laboratory Tests, Section 5 and Part 2 

MSFC-PROC-1831: The Analysis of Nonvolatile Residue Content 

MSFC-PROC-1832: Sampllng and Analysis of Nonvolatile Residue Content 


MSFC-PROC-404: Gases, Drying and Preservation, Cleanliness Level and 

Inspection 

MSFC-SPEC-164B: Speclflcatlon for Cleanliness of Components for Use in 




12. INTERRELATIONSHIP Parent sow Paragraph(s): 2.6 12. 

Referenced from SOW Paragraph: 6.1.3.12, 6.2.3.12 


13.1 SCOPE: 

The Environmental Control and Life Support Systems Design and Data Book 

provides a summation and targeted details of the contractor's data, 

analysis and selections developed for the designs for vehicle systems 

that provlde and manage the following: 

1. Active thermal control (cabln temperature/humidity, heat acquisition, 

transport and rejection, equipment and vehicle systems active thermal 

control, thermally-controlled storage) 

2. Breathable atmosphere 

3. Cabin pressure 

4. Contaminant control (In the alr, ln fluids and on surfaces) 

5. Emergency oxygen 

6 Fire/smoke detection and suppression 

7. Environmental monltorlng (including active radiation monitoring, 

atmospheric and combustion products monitoring, atmosphere thermal 

properties monitoring and cabin pressure monitorlng) 

8. Water (potable and non-potable) 

9. Waste and trash collection, storage, processing and disposal 

10. Food supply interfaces, processing, preparation and storage 








JSC 20584: Spacecraft Maximum Allowable Concentrations for Airborne 

Contaminants 


1 The deliverable shall include, as applicable, the information listed 

below: 

(a) Assumptions and groundrules 

(b) Subsystem Definition including GFE vs. contractor-suppl~ed 

assumptions 

(c) Subsystem Requirements Analyses 

1. Functional decomposition 

2. Functional, performance and interface requirements 

3 Derived requirements on other systems with analys~s that yields 

the requirements 

4. Trade study results 

5. Analysis to show the subsystem meets the requirements 

(d) Detailed Design Description 

1. Hardware element descriptions 

2. Hardware math models 

3. Mass and volume properties 

4. Power and thermal profiles 

5. Schematic layouts, drawings and 3-D solid geometr~c 

representations of components 

6. Interfaces (internal and external hardware interfaces including 

mechanical, electrical and thermal interfaces, software interfaces, and 

human ~nterfaces; ~ncludes necessary Interface Control Documents) 

7. Consumables list 

8. Data bandwidths (data rates); Telemetry; Instrumentation 

(e) Operational Analyses 

1. Operational scenarios and modes ~ncluding the subsystem's 

lim~tations on any aspect of vehicle flight 

2. Performance and Marg~n analyses 

3. Operating Environments (natural and induced) 

4. Failure modes and redundancy operations including vehicle failure 

modes accommodated by subsystem and failure modes reacting to vehicle 

failures 

5 Fault Detection, Isolation and Recovery 

6 Diagnost~c strateg~es including plans for ~n-flight maintenance 

7. Initialization procedures and parameters 

8. Day of launch parameters and late-load requirements 

9. Abort analysis 

10. Launch scrub turnaround plan 

(f) Maintainabil~ty and test~ng data 

1. Test requirements including ~nformation on Special Test Equipment 

design, operations and ma~ntenance 

2. Maintainability strategies including sparing provisions, growth 

and scarring provisions, shelf-life, and long-term storage prov~sions 

3. Deliverable end item or equipment ~dentification (part number) 

4. Pred~cted reliab~l~ty assessment 

5. Component reusabil~ty!refurb~shment analysis 

(g) References and Ind~cation of any changes from the prev~ous submission 

2. By PDR, the Contractor shall provide to NASA definition of the process 

to be used for cleanliness of components for use in oxygen, fuel and 

pneumatic systems. The process must meet or exceed the requ~rements 

identif~ed in the following documents: 

(a) MSFC-SPEC-164B, Spec~fication for Cleanliness of Components for Use 

in Oxygen, Fuel and Pneumatic Systems (and associated Children documents 

as specified in Attachment J-3, Applicable, Guidance, and Informational 


(b) MSFC-PROC-404, Gases, Drying and Preservation, Cleanliness Level and 

Inspect~on 

(c) MSFC-PROC-1831, The Analysis of Nonvolatile Res~due 

Content 







(d) MSFC-PROC-1832, Sampling and Analysis of nonvolatile Residue Content 


3. By PDR, the Contractor shall ident~fy the standard they intend to use 

for test methods for environmental engineering. Th~s standard shall meet 

or exceed the following standard: 

(a) MIL-STD-810F, DOD Test Method Standard for Environmental Engineering 

Considerations and Laboratory Tests, Section 5, and Part 2 

4 The following special analyses, design and plan development shall be 

performed and documented by the Contractor and delivered to NASA by PDR 

and updated, if needed, by CDR: 

(a) Act~ve thermal control design approach, analyses and models 

(b) An analys~s of atmosphere mixing within the crew cabin and the ISS 

interconnecting module for Block lA and IB; to include an assessment of 

CEV atmosphere control accommodat~ons for the var~at~ons in air flow 

systems of the ISS docking nodes 

(c) An analysis of C02 and humid~ty removal rates vs. airflow rate 

descr~ption of the pp02 control logic 

(d) Trace contaminant control system and CO oxidation system sizing 

analysis and design 

(e) Odor and contaminant removal rate and s~z~ng analysis and design 

(f) Environmental control strategy for Earth entry and post landing 

phases; including off-nominal landing contingencies and environments 

(g) Potable water quality control plan and associated analysis 

13.4 FORMAT Electronic format per Section J -2 2.3.2.1. Microsoft® 

Word/Excel® based and ASCII, delimited for data; SINDA/FLUINT ASCII file, 

Thermal Desktop®/RadCAD®, and XML. 

13.5 MAINTENANCE: Changes shall be identified and complete re-issue of the 

document is requ~red. 







1. 

3 

6. 

7. 

PROGRAM: CEV 2. DRDNO .. CEV-T-075 

DATA TYPE. 3 4 DATE REVISED: May 2009 

5 PAGE 1 

TITLE: Pyrotechnic Subsystem Design and Data Book 


The pyrotechnic Subsystem Deslgn and Data Book shall provide 

documentation of the development, design, testlng, integration, 

verification and operation of the pyrotechnic subsystem for the CEV. 

NASA will use thlS information as a source for insight into the 

Contractor's design of the CEV pyrotechnic subsystem, especially with 

respect to reliability and safety. In addition, this documentation will 

provide detailed reference information to support Engineering and 

Operations throughout the life of the CEV. 

8. DISTRIBUTION. As determined by the Contracting Officer. 



11. REMARKS. 

The Contractor shall plan pyrotechnic systems to be deslgned, fabricated, 

verified, and operated ln accordance with JSC 62809, Constellation 

Spacecraft pyrotechnic Specification. 

12. INTERRELATIONSHIP. Parent SOW Paragraph(s)' 2.6.13. 

Referenced from SOW Paragraphs 6 1.3.13, 6.2.3.13, 6.4.3.13 

13 DATA PREPARATION INFORMATION 

13.1 SCOPE: 

The Pyrotechnics subsystem includes all explosively-operated devices, 

explosive initiators/detonators, pressure cartridges, firing 

units/controllers, and energy transmission lines (excluding vehicle 

wiring) as described in JSC 62809, Constellation Spacecraft Pyrotechnic 

Specificatlon. 

13 2 APPLICABLE DOCUMENTS. 

JSC 62809: Constellatlon Spacecraft Pyrotechnic Specification 


The Pyrotechnic Subsystem Design and Data Book shall provide 

documentation of the development, design, testing, integration, 

verification and operatl0n of the pyrotechnic subsystem. 

It shall lnclude the following data as applicable: 

1) Assumptions and groundrules 

2) Subsystem Definition including GFE vS. contractor-supplied assumptions 


a. Functional decomposition 

b. Functional, performance and interface requirements 

c. Derived requirements on other systems with analysls that yields 

the requirements 

d. Trade study result 

e. Analysis to show the subsystem meets the requirements 

4) Detailed Design Description 







a. Hardware element descriptions including sourcing approach for 

initiators 

b. Mass and volume properties 

c. Power and thermal profiles 

d. Schematic layouts, drawings and 3-D solid geometric 

representations of components 

e. Interface requirements and description (internal and external 

hardware interfaces including mechanical, electrical and thermal 

interfaces, software interfaces, and human ~nterfaces, including safing 

provisions for ground processing, servic~ng and pre-flight operations; 

~ncludes necessary Interface Control Documents) 

f. Consumables list 

g. Data Bandwidth 

h. Telemetry/instrumentation 

5) Operational Analyses 

a. Operational scenarios and modes including the subsystem's 

limitations on any aspect of vehicle fl~ght 

b. Subsystem operational plan and description including command 

and control (arming/firing) approach, nominal and off-nominal operational 

scenarios, servicing and safing procedures, and Day of Launch/Day of 

Landing activities 

c. Performance and Margin analyses 

d. Operating Environments (natural and induced) 

e. Failure modes and redundancy operations ~ncluding vehicle 


vehicle failures 

f. Fault Detect~on, Isolat~on and Recovery 

g. D~agnost~c strategies including plans for in-flight maintenance 

h Init~al~zation procedures and parameters 

i. Abort analysis 

j. Launch scrub turnaround plan 

6) Mainta~nability and testing data 

a. Test requirements and ground test reports and results. 

b. Ma~nta~nability strategies including sparing provisions, shelflife, 

and long-term storage provisions 

c. Deliverable end item or equipment ident~fication (part number) 

d. Pred~cted reliability assessment/analysis 

7) References and Indication of any changes from the previous submission 

13.4 FORMAT' Electronic format per Section J -2 2.3.2.1. Microsoft® Officecompatible 

for data and reports, PDF for drawings/schematics, and XML. 

13 5 MAINTENANCE: Changes shall be identified and complete re-issue of the 








1. 

3. 

PROGRAM. CEV 

DATA TYPE 3 

6. TITLE: CEV Wiring Database and Reports 

2. 

4. 

5. 

DRDNO.: 

DATE REVISED: 

PAGE: 

CEV-T-080 

May 2009 

1 


The CEV Wiring Database stores information defining the electrical and 

optical data, command, and power connect1v1ty 1n the CEV System, and 

enables the export and d1str1but1on of this 1nformation in support of CEV 

design, integration, testing, certification and documentation activities. 

NASA will utilize the CEV Wiring Database and Reports to ensure that the 

contractor's plan for collecting, storing, controlling, implementing and 

reporting W1re harness data 1S acceptable for the accomplishment of CEV 

Project objectives. 

8. DISTRIBUTION: As determined by the Contract1ng Officer. 

9. INITIAL SUBMISSION: Per Data Requuements Matnx 


11. REMARKS. 

12. INTERRELATIONSHIP' Parent sow Paragraph(s) :2.6.16 

Referenced from SOW Paragraphs: 6.1.3.16, 6.2.3.16, 6.4.3.16. 


13.1 SCOPE. 

The CEV Wiring Database is a key component in the implementation of the 

CEV Wiring Plan. The design of the CEV W1r1ng Database must provide for 

the storage, update, retrieval, querying, tracking, reporting and 

exporting of key wiring information for the CEV System as well as its 

electrical and optical interfaces with other Constellation elements and 

external equipment. The CEV Wiring Database will be the primary source of 

information for the fabrication, installation and verification of the 

electrical and optical connections for the spacecraft. 

13 2 APPLICABLE DOCUMENTS' 


The CEV Wiring Database and Reports shall include the following 

provisions: 

a) Security provis10ns to 11mit access and change authority to designated 

personnel 

b) User interface to support the storage, update, retrieval, querying, 

tracking, reporting and exporting of key wiring-related information as 

defined by the contractor in the development of the CEV Wiring Plan. 

c) Fields for the storage of functional and signal path connectivity for 

the wiring Subsystem including signal type, signal description, connector 

designation, signal des1gnat10n and def1n1tion of signal end points by 

component, connector and pin 

d) Fields for the storage of wire harness manufacturing data including 

wire/cable type, wire/ cable length, terminations of conductors and 

shields, parts/materials information, and special manufacturing 

instructions. 

e) L1nkage between the CEV Wiring Database and the CEV Data and Command 







Dictionary to support integration of CEV Wiring Database signal paths 

with software channelization and command data. 

f} Ability to export signal path diagrams in standard drawing formats and 

in PDF. 

g} Ability to export manufacturing drawings and instructions ~n PDF. 

h} Ability to produce harness status reports describing the current 

progress of CEV harness definition, fabrication, installation and 

verification for electr~cal and optical connectivity including 

comparisons with an historical metrics record. 

i} Ability to produce connectivity reports and user-defined reports to 

support the design, test, troubleshoot~ng and operation of the CEV 

System. 

J} Abil~ty to produce status reports describing the progress of CEV 

harness drawing definition, release and modification including 

compar~sons with an historical metr~cs record. 

k} Ab~l~ty to produce connector conf~guration reports that support 

verification of requ~red connector mate/demate status for powered 

test~ng. 

l} Ability to produce harness verification documentation to support 

manual pin-to-p~n continuity checks 

m} Linkage with an automated harness testing system to generate the 

automated harness testing programs, test adapter cables and test 

instructions using the information stored in the wiring database. 

n} Linkage between the CEV Wiring Database and the CEV Spacecraft 

Electrical Equ~pment Loads Dictionary to support integration of CEV 

Wiring Database power paths channelization. 

134 FORMAT:Electronic format per Section J-2 2.3.2.1, native database 

format defined by the Contractor with the ab~lity to export the ent~re 

contents of the database in an industry standard database exchange 

format. Ability to export drawings in standard drawing formats and in 

PDF. Ability to produce manufacturing instructions in PDF. Abil~ty to 

produce connectivity reports ~n Microsoft Excel-compatible format. 

Ability to produce status reports ~n M~crosoft Word-compatible format. 

13 5 MAINTENANCE: Contractor-proposed changes to the database structure or 

report~ng capabilities shall be submitted to NASA for approval. Complete 

re-issue of this document ~s required with changes clearly identified. 






1. 

3. 

PROGRAM: CEV 

DATA TYPE: 1 


2. DRDNO.: CEV-T-082 


5. PAGE: 1 

6. TITLE: Spacecraft Test & Verification Facility System Requirements 

Document 


Define requ~rements for all Contractor-provided test and verification 

facilities, facility systems, support equipment, and associated software 

needed to support module and spacecraft-level qualification, 

certificat~on, and acceptance test activities. 

8. DISTRIBUTION. Per Contract~ng Officer's letter 



11. REMARKS: 

12 INTERRELATIONSHIP. Parent sow Paragraph(s): 10.3.2, 10.3.3. 

Referenced from sow Paragraphs: 6.1.5, 6.2.5, 6.4.5 



13.1 SCOPE' 

Provide requirements for all Contractor-provided test and verification 

facilities, facility systems, support equipment, and associated software 

needed to support module and spacecraft-level qualification, 

certification, and acceptance test act~vities. 



The Spacecraft Test & Verification Facility Requ~rement Document shall 

contain the follow~ng. 

a. Narrative description of the purpose and function of the facility, 

room, and systems. 

b. Hazard ident~fication requirements (e.g. classification of hazards, 

type of propellants, types of vents, types of purges, maximum 

fuel/oxidizer propellant quantities, types of ordinance, power voltages 

and frequencies, noise levels, RF radiation levels). 

c. Env~ronmental requirements (e.g temperature, humidity, particle 

counts, radio frequency shielding, noise attenuation, etc.). 

d. Environmental pollution controls. 

e. Power, ground~ng and lighting requirements, includ~ng the use of 

uninterruptible power systems and supplies for ground operations 

activities. 

f. Backup power and other backup or cont~ngency requirements (chilled 

water, hot water, datal etc.). 

g. Plumbing/venting and commodities requirements for test operations 

activities. 

h. Fire and hazard protection requirements. 

i. communications and data networking systems requirements (e.g., 

required connections to other test and operations facilities needed) . 

j. Special structural needs requirements (e.g. vibration controls, floor 

loading, etc.). 







k. Security requirements (e.g. facllities, facility systems, personnel, 

hardware, software, data, badglng, and access control). 

1. Materlal handling requlrements (e g. crane or hoist requirements). 

m. Consideration of human engineering requirements. 

n. Conflguration management requirements. 

o. Scheduling requirements. 

p. Functional capabilities requirements. 

q. Facillty, facility systems, and support equipment certlfication 

requirements. 

r. Operations requirements, includlng number and type of personnel 

required to operate facility. 

s. Maintenance requirements. 

t. Sustaining engineering and obsolescence planning requ~rements. 

Each document shall contain a section titled 'Verification'. For each 

requirement in the documents, there shall be a corresponding verification 

requirement The document shall contain, in addition to the verification 

requirements, a verification traceability matrix that establishes the 

relationshlp between each System requirement and its verification 

requirements, and contains the methods that will be used to accomplish 

the indicated verification actlons. 


13.5 MAINTENANCE: Changes shall be incorporated by complete reissue. 







1 PROGRAM' CEV 


3 DATA TYPE: 1 

4 DATE REVISED: May 2009 

5. PAGE. 1 

6. TITLE Spacecraft Test & Verification Facllity Certification Package 


To provide the evidence and audit trail requlred by NASA to verify that 

the results from the facility verlfication activities indicate that all 

requirements were met. 

8. DISTRIBUTION Per Contractlng Officer's letter 



11 REMARKS' 

The Contractor shall provide certification results for all Contractorprovided 

test and verification facillties, facility systems, support 

equipment and associated software needed to support module and 

spacecraft-level qualification, certification, and acceptance test 

activities 

12. INTERRELATIONSHIP Parent SOW Paragraph(s): 10.3.2, 10.3.3. 

Referenced from SOW Paragraphs: 6.1.5, 6.2.5, 6.4 5 

Related DRD(s). CEV-T-082, CEV-T-083, CEV-T-084 


13.1 SCOPE' 

The Spacecraft Test & Verification Facility Certificatlon Package 

contains the elements of documentation required to establish that all 

requirements have been met by facillties, facility systems, support 

equipment and associated software. 



The Spacecraft Test & Verification Facility Certification Package shall 

contain the following: 

1. Current version of the Spacecraft Test & Verification Facility 

Requirement Document for the facilities, facility systems, support 

equipment and associated software that is being certified 

2. Current verSlon of the Spacecraft Test & Verification Faclilty 

Certification Plan for the facilities, facility systems, support 

equipment and assoclated software that is being certified, including the 

verification matrix 

3. Verification compllance report, including the verlfication matrix 

mapped to all verificatl0n data. This report shall lnclude: 

a) Test report 

b) List of approved operational controls 

c) Structural integrity verification 

d) Materials lnformation 

e) Electrlcal information 

f) Electromagnetic compatibility information 

g) Temperature valldatlon information 

h) Structural validation information 

i) Pressure systems information 





j) Performance verification information 

k) Verification tracklng log 

1) Inspections reports 

m) Demonstrations reports 

4. Risk informatlon obtained from the FMEA and hazard analysis 

5. Waivers, deviations and non-conformance reports 

6. Dlscrepancy reports and problem closure reports relevant to 

certification 

7. Limited life items list 

8. Engineerlng drawlngs 

9. Software Version Description Document (VDD) 

13.4 FORMAT Electronic format per Section J -2 2.3.2 1. 

13.5 MAINTENANCE: Changes shall be incorporated by complete reissue. 









1. 

3. 

PROGRAM: CEV 

DATA TYPE' 2 

6 TITLE' orion Crew Interface Label Map 

2. 

4. 

5. 

DRDNO.: 

DATE REVISED. 

PAGE: 

CEV-T-089 

May 2009 

1 


The Orion Crew Interface Label Map w1ll detail the content, design (font, 

label size, material, etc.), locat1on, and orientation of all crew 

interface labels for the Orion project (i.e., not all vehicle labels, 

only crew interface labels). This data w1ll be used by NASA to ensure 

that all crew interface labels on the Or1on meet the Constellation 

Program Crew Interface Labeling Standard (CxP 70152) when integrated into 

the design of the vehicle It is not 1ntended to be the approval process 

for every crew interface label drawing One draw1ng can represent 

multiple crew interface labels. The Orion Crew Interface Label Map 

documents the content, orientation, location and drawing number reference 

for each crew interface label. 

8 DISTRIBUTION. As determmed by the Contracting Officer. 

9 INITIAL SUBMISSION. Per Data Requnements Matrix 


11. REMARKS: 

12 INTERRELATIONSHIP: Parent sow Paragraph(s)' 2.8.7 


131 SCOPE: 

The Orion Crew Interface Label Map provides a "map" of technical labeling 

informat10n, including content, design (font, label size, material, 

etc.), location, and orientation, for all crew interface labels as 

integrated into the design of the veh1cle. This includes crew 1nterface 

labels at the vehicle, module, subsystem, and component level. This also 

includes informat10n on ground labeling that 1S in the vicinity of flight 

crew interface label1ng, only for the purpose of showing non-interference 

with the flight labels The Orion Crew Interface Label Map does not 

include information on part-marking, on ground labels not 1n the vicinity 

of flight labels, or any other labels not used by the flight crew during 

nominal operations and maintenance activ1ties. 


CxP 70024, Constellation Human Systems Integration Requirements (HSIR) 

(and associated Ch1ldren documents as specif1ed 1n Attachment J-3, 


CxP 70152, Constellation Program Crew Interface Labeling Standard (This 

document is also an HSIR child document.) 


The Orion Crew interface Label Map shall use the label1ng standards 

defined 1n CxP 70152 to provide crew interface labels for the Orion 

vehicle. The contents of the Crew Interface Label Map shall include, but 

not be limited to, 1) label content (including approved Operations 

Nomenclature), 2) label design details (font, label size, material, 

etc.), 3) label location on the hardware, vehicle, etc., and 4) label 

orientat10n when integrated into the flight vehicle design. The Crew 







Interface Label Map shall include both textual descriptions of the labels 

used, as well as figures that show the label design, and the label 

location and orlentatl0n on the hardware. The Crew Interface Label Map 

shall also contain details on any labeling standards that are not met by 

the Orion design, as well as justlflcatlon for the deviation. Deviations 

should be limited to instances where the implementation of a specific 

labeling standard is not feasible because of limitations created by the 

design (e.g. label real-estate limitations), or a unique implementation 

is agreed upon between NASA and the Contractor for the overall benefit of 

the Crew interface. 

13.4 FORMAT' Electronic format per Section J -2 2.3.2.1. Microsoft® 

Word/Excel® or Adobe® Acrobat® PDF for textual and graphics information, 

or ASCII dellmited for data. 

13.5 MAINTENANCE: Contractor-proposed changes to thlS document shall be 






DATA PROCUREMENT DOCUMENT 

-Refer to Volume VII, Part 2 of 2- 

------~ 

''';;' ,--t\'J"!~"-'~'\;''''!~, ,,~;~r 

", """"~

H' ___ "_"_' 



Attachment J-2 DRD Submission Matrix 


" 

Submission Events 

.. 

Q, 

iii 

III 

0 0:: 

0:: 0:: 

co. 

0- 

e 0:: Q 

>- 

ORO Tille l- II. !;;: !!! II) ~ 

CEV- Financial 3 I 

B-001 Management 30 

Report (533) 

Days 

After 

f------ ---------- ------ 1----- 

CEV- Workforce 3 I 

B-002 Reporting 30 

Days 

After 

------ _._,,_._._. ----- ---_... 

---~------- .. .. --~---- ~---- 

- 

~ ~ 

Q 

Q 

u 

!?::.. 

0:: 0:: 

Q Q 

0:: 

II) 

II) 

Q 

II. 

II) 

II) 

------- _ __ .._--_. .. ------ 

_____ L ___________ 

0:: 

Q 

U 

.. 

~ 

0:: 

0:: 0:: .c 

« ~ S Noles 

U 

-_.. ._.H_.H__.----- 1------_ .._----------_.._ 

The Initial (baseline) NF533Q report shall be 

submitted within 30 days after authonzatlon 

to proceed In addition, NF533 reporting 

shall begin no later than 30 days after the 

Incurrence of cost Submission frequency IS 

monthly for NF533M and Quarterly for 

NF533Q An electrOniC 533M shall be 

delivered 10 working days after calendar 

month end One hardcopy 533M shall be 

delivered two working days later to the 

specified NASA contracts representative 

.._--_.._------ - - ---..- 

U The Initial report shall be submitted within 30 

days after authorization to proceed 

SubmiSSion frequency IS Quarterly for the first 

year, and Annually thereafter 

SubmiSSion shall be by the twelth working 

day of the month follOWing the month end 

----- -------- ---- - --- -------- ------ 

I 

I , 


Page 1 of43

__ ' ____ H _", ... """'_'''_' ___________ • ____ 



Attachment J-2 DRD Submission Matnx 


- 


.. Q. 

'iii 

l!l 

iii:: 

iii:: iii:: 

... D- 

e a: c :c 

DRD Tille ~ D.. !;t !!! II) II) 

-iii:: 

i2' 

c 

C 

D.. 0 

- - 

iii:: 

iii:: 

C iii:: C iii:: 

II) II) 

c Q 

II) 

II) 

D.. 

0 

iii:: 

« 

.. 

~ 

iii:: 

iii:: .c 

IL 5 Noles 

CEV· Cost 3 I F 

8-003 Performance 30 

Report 

Days 

Prior 

----- ---_._-- 1----f--- -------- ----1----- 

CEV· Property 3 I 

8-004 Financial 

Reporting 

--------_ .. _-- - r-"'-'--- ----_._. 

---- 

U 

.....__.- 1------ 

_." 

U 

Proposal submission shall be the IMS portion 

only, per Instructions In Section L 

Initial CPR submission shall be 8 days prior 

tolBR 

Monthlyelectronlc CPR submission shall be 

12 working days after the calendar month 

end following the month being reported 

Format 1 shall be delivered 10 working days 

after calendar month end In conjunction with 

the 533M Formats 2 thru 5 shall be 

delivered within 12 working days following the 

calendar month end being reported 

Slgmflcant EVM system changes shall be 

submitted within 5 worl(lng days of such 

change 

The due date for the first Monthly Property 

Financial Reporting submiSSion IS the 21 st 

day after the close of the month, beginning at 

the first month after contract start 

Subsequent monthly reports shall be due the 

21 st day after the end of the month, for 

example, August 21 for the month ending 

July 31 

" 

The due date for for the first Annual Property 

Reporting via NASA Form (NF) 1018 IS 

November 30 Subsequent annual reports 

shall always be due on November 30 

---------- 


Page 2 of43



Attaclnnent J-2 DRD Submission Matrix 


,-' 

': 

" 

,.' 

. Submission EventS' 

';i'", 

"I, 

; ~ ,-,' 

ORO 

CEV· 

0-1101 

Tille 

.. 'iii:: ' 0:: '0:: 

" 

ii 

II> 

J 

'~,J ") '0:: 

,e 

'8. 

D. 

c 

D. !;;: 

,~ 

~ 

III 

0:: ~~,~;',~u;. 

"






-- - - - 

- 

--- 

I 

I 

c 

(;j 

., !:.. 

0 

., a: 

Co a: a: 

a: 

a. 

c a: 

e ... a: c := I/) 

>- 

c 

~ !!! 

ORO Tille I- D- I/) I/) I/) D- 

~ 

~ 

c 

~ 

a: 

c a: 

I/) 

c 

I/) 

o 

~ 

a: ., 

a: a: 

.

~ ~ 

~ 





---- 


iii 

II> 

0 II:: 

., t:I. II:: II:: 

a. e 

a.. II:: 

>- C ~ 

ORO Title I- D.. !;( !!! II) II) 

CEV· Flight Test 2/3- 

0-002 Article (FTA) 

 

Requirements 

(cont) 

-II:: 

Cl 

c 

C 

D.. ~ 

~ 

II:: 

II:: 

C II:: C II:: 

II) 

II) 

C 

C 

II) II) 

D.. 0 

II:: l;; 

II:: II:: 

« II.. 5 Notes 

I,F,U 

Software ReqUirements Specifications 

Imtlal 30 days pnor to Applicable PTR (PDR 

Level) for all tests (Type 3) 

Final 30 days pnor to Applicable PTR (CDR 


Software Interface ReqUirements 

Specifications 

Imtlal 30 days prior to Applicable PTR (PDR 


Final 30 days prior to Applicable PTR (CDR 


f.---- -------- -_.- - 

CEV· Reserved 

..._... _._-- .- .._.._...._.. _._._._-- .._ 

.. _._ .... _ 

D-003 

[----- .._.H._ ---- --,,-,,_..- [----- -.~.---.. ~~- 

CEV· FlightTest 2 

D-004 Article (FT A) 

Englneenng 

Design Data 

Book 

'--~ 

.._.. 

----.- -_._.._...- - -- ---- -- --.-- 

-.-- _._ ... __ ._--_._----- _. __ . __ ._.- 

All Levels Update as reqUired 

----------- ------- - - - -------- -_. __ . __ ... ,,_.- -- - - -- 

[---._.._.._. ---- ,,---- -- - - -- - - ------------- 

I,F,U 

Imllal 30 days prior to Applicable PTR (PDR 

Level) for all tests (PA-1 - AA-3) 

Update 30 days pnor to Applicable PTR 

(CDR Level) for all tests 

Final 30 days prior to Respecllve Flight Test 

Article System Acceptance ReViews for all 

tests 

Update as required 

--------------- 


Page 5 of43





., 

DRD Title 

Q. 

?:" ~s..)' 

:.>.~ e 

Ci: 

;; 

, , 

CEV· FlightTest 

0-005 Article (FT A) " 

Validation and 

Venflcatlon 

Data Book 

------- ---- -.-~- ------ 

CEV· I FlightTest 2 

'~> ':-. 

D-006 ArtIcle (FT A) 

,,' 

Ground 

Support 

; 

EqUipment 

(GSE) Design 

Data Book 

CEV· I CEVPnme 3 rl 

I .~ ti'*" t 

{,t, 1>", 

M.Q01 Project 

Management ~~, - ii~~ , /'-.:... 

V!"p>:l'k~~,..,t' 

Plan "- ~\ ~" _., ,"01':,.\ 

, 

,".f.JV 

I"~ 

'" ;f~~;:~;:~~~;:r 

':-'. ,"~: ' , 

" 

~ ,.- 

" 

---_.- ----._.- ....:..-:;-f--.,--.. 

,j ,~ , ,'''' - ,1 

~, . 

~~/" ; ,'." 

'~~~~'l < 

,> _ 

',," j !~~ ", • 

~v ,.,!.. 

" 

~< 

~ ,. 

« 

---- 

F 

0 Notes 

Final 30 days pnorto Respective FlightTest 

Article Test Readiness Review for all tests 

(PA-1 - AA-3) 

-------------- 

I,F,U Initial 30 days prior to Applicable PTR (PDR 

, :' Level) for all tests (PA-1 - AA-3) 

',. A 





L ;~---I 

ORO 

CEV· 

M-002 

Title 

Performance 

Assessment 

Plan, Reports 

and 

Management 

ReViews 

1. 

" • } "'r. 

~.! ' 

~ ,,,,,'k 

~.'~ 

~S,.t 

8. "go 

>- (.....' l 

I-- 'a:.'" ' 

!'~~L I 

1/3/3 '~~:'I/, 

/ ' , 

1 ~1 

~,' 

, . 

" 

I.. 

'\' 

" ~. I ' 'IJ ~ 

0- 

!;: 

U 

90 

Days 

After 

" , 

V'1i:: 

"~Ie:! 

,'\-""'}' 

I','>'F' 

0:: 

C 

I/) 

-,4; • 

1,;~~:3:,' 

I "'.1~·'1 ' 

1 'i I,. "0::" 

1:1::~~~~~~:': 

I.,", " 

,:;~'. '~ 

-~ .;' 

Submisii~~: ~vents 

~ 

c 

e: 

o:: 

c 

I/) 

I/) 

, 1~'" '1 .... ,' 

" 

;,1'-' ''',' 

.. ' 

~ 

c 

u 

" 

-':; 

~' ~' 

~ :~' ;.~~~ ~;~~ 

tn ' i Q'.t' , 

tn r ,:t~·:,. - 

~ 

"":! fl,." 

> ,,1, 

.,,¥~,-~ 

,,"'·f 

'~",~" ", 

",,' 

", ' 

. ,i 

j 

s 

U' 

Notes 

Performance Assessment Plan delivery shall 

beat IBR 

The first Monthly Input should support a 

review 20 working days after the Imtlal 

financial month end The first Quarterty Input 

should support a review 20 working days 

after the end of the Imtlal GFY quarter under 

contract Submission frequency IS Monthly 

Reports are due on the 4th Monday of the 

month, and ReView data packages are due 

Quarterty. 

• Plan= Type 1, Reports= Type 3, ReView 

,, 

" ?,. 

Packages=Type3 

;:".' :;J;~,J,,' 

--t 

,I,:, :' ,',. as necessary to Incorporate changes 

Imtlal submiSSion IS ATP + 9O.days, update 

as necessary to Incorporate changes 

't. . "f'I' 

., 

------ '7;::;t. i~' -- S::-::::.; U Imtlal submission IS ATP:;:-OO daYs~~~d-;e-' 


Page 7 of43





ORO Tille 

.. 

... 

>- 

l- 

"1 

~~?~(~ U I Updates as required 

Monthly risk management reports shall be 

submitted by the 15 111 shOWing the status of all 

risk managemenVnsk mitigation efforts The 

report shall highlight new risks that have 

been added smce the last month as well as 

the up to date status of all "high' & "medium" 

nsks 

• Plan= Type 2, Reports= Type 3 

CEV· Contractor's 2 

0-001 CEVConcept 

of Operations 


Page 8 of43





.. 

,~1' 

co. ,~B;F~ l!- \,!{~:.,' e 

ORO Title ~ ~~;g, 

!;: "":,'?;!!;I.• II) 

a()J~,:I';: ~ 

I~\? 

.,,);,(, " 

CEV· Flight 2 I 

0-002 Hardware/Soft c' ''[0 ' 

~ , 

45 

ware 

Days 

i'( " ~~ 

Operallons 

Prior 

.~... 

, ", 

and 

Maintenance 

p, 

ReqUirements 

,,',I





... .. 

ORO Title ~ 

,I 

r 

CEV· CEVStowage 2/3- 

0-0Q6 Capabilities 

and Services 

-m- 

Handbook and 

IDD 

CEV· Range Safety 

0-007 Requirements 

Documents 

CEV· I Ground I 2/3- 

0-008 Systems 

Requirements, 

Plans, Reports 

and Design 

Data 

1 ' 

1 o!s 

Prior 

,------~- 

~ 

u 

" 

u 

Notes 

Update as required after Final delivery 

Services Handbook IS Type 2 

Interface Design Document IS Type 3 

DRD IS also required for flight tests, and thiS 

submiSSion frequency Will be directed by 

COTR 

--+-.. -:,.-.-.+----j- ·-.. T .. ..,: .. +----+---------------.--.- 

Ground Systems Requirements, Plans, 

Reports and Design Data Volume I, Ground 

Systems End Item Requirements Document 

and Report Part 1 of 2 NASA PrOVided 

FaCIlities & FaCIlity System ReqUirements & 

Part 2 of 2 NASA ProVided Ground Support 

Equipment (GSE) Requirements, Volume III, 

Ground Systems Operations and 

Mamtenance Plan and Requirements 

Documentation, and Volume IV' Ground 

Systems Sustaining Engineering Plan' 

Update 45 days pnor to PDR 

All other volumes of CEV-o-OO8 Will not be 

delivered at PDR 

- Reports = Type 3 All other dellvenes = 

Type 2 


Page 10 of43





ORO 

Title 

.. 

. 

~ 

~ 

5 Notes 

CEV-S- Safety and 

001 MIssion 

-----r:--- 

Assurance 

(S&MA) Plan 

CEV-S- FaultT ree 

Proposal - deliver high level plan and 

schedule of DR dellvenes 

------- --- 

002 AnalysIs 

CEV-S- 

003 

Flight System 

Safety Hazard 

Analyses 

70ays 

After 

SOR 

Board 

U 

70ays 

After 

SOR 

.





ORO Title {:' :£i:~.~





DRD 

Tille 

CEV-S- Orbital Debns 

007 Assessment 

t-i t- i' r ~;: r t' ~pij~t;, r 

_.__________ :. --: ___ .._._._____ "'-,,________ C_'_d,-,,-_____ 

CEv-s-1 Sf 

ae 

ty 

an 

d 1 "I: 

"_ 

F :. 

. ' " 

,',," 

,) 

'," ,';, ," ~\,~ 

008 Health Plan "" ',', ,.;;~ , ' .' , Y' "r : 

Noles 

;"p~o;r-f 'r-t: 

";~;~0 -, ,-:-' The ~o~tr';;;~ may re;;;-se the plan at any 

, "', time or at the direction of the Government 

ReVISions are subject to Govemment review 

and approval Dlstnbutlons of approved 

reViSions will be as descnbed above, 

ffi 1 '1~ t t ~'+:1 t"'J t' It' I ~ 

CEV-S- Fallu~;Mod';; --;- {'>~ --',-:-'-' -I~~:;~" '-»---',-;'(j(;k: -"--.;.~~~~.J)~iA'Il(,-I 

~i;.f'i~:l' i:. 

CEV-S- Reliability, 

Itfl I;:' ':3~~,1 I ~(I~~;~I 

011 Maintainability 

'""W:;:- f· ~ "' ";',~ 7 Davs ffJ ~i&L} 

, and 

Supportability 

Integrated 

Report 

1~\iI~"1 1'( :;'il:tfit~, 1 

~>, 'It 

..... ,:>,~ ,.'On· 

;~,-" ,~.. ?, ,~WS,' 

~~ > ,~ 

_I l'lI,q'l 

"'".c/ ~ _ ". 

~t}~~""': i: 

-,,' .-~,,>;.. ,......" 

1;~{i~":;~1 See 1*lntenm delivenes (Type 4) every 6 months 

';',l!IL~ notes after PDR 

r iIf01 (ii' 'I 

~lr§r.~~~ 

I Initial? days after SDR Board, prOViding 

high-level system allocations, 


Page l3 of43





CI) 

IX 

Q. 

>- 

C 

::'~!j~l 

, , ~" 

ORO Tille l- I/) 

CEV-S· Govemment- 112' '> ~ 

'" 

012 IndustlY Data 

Exchange 

Program and 

~ '," 

NASA 

AdVisonesfAL 

,l~", I ...





., 

r::L 

DRD Title ~ 

CEV-S- Cntlcal 

015 Processes 

CEV-S- Mechamcal 2 

016 Parts 

Management 

and 

Implementatlo 

n Plan 

+-----+----+-:--+_ 

CEv..s.i Wo~anshlp 

017 Standards 

, ~ , j" 

~ 

.c: 

S I Notes 

---f--,.-;'-""-f----I--.-\f'i'-~I-----+.·",';_"-. +--1-'--'--+-----1----------------- 

I 

45 

Days 

Prior 

~J r 

.' u Update as required after Final delivery 

I ..... -+---\-. -.·~T-+----I_,_,'·+_'_·-+--,___+' .. -~-. -'I---+"'-'-'-+-----l----- 

:~~~ri~:~j: 

CEV-S- I Software 3 

018 Quality 

Assurance 

~--' < 

(SQA) Audit t: ",~: :ir;;~J{~~/: 

Report 

CEV-T- Integrated 2 

r 

.•• 





DRD 

," 

" , 

",' ; ,)'iI 

, ' 

~(~':"" ~ 

, .' 

It,, 

"{-, 

" 

:;~;i~:~) 

£', 

if CG t 

I;'.,r''" ' " 

CI) 

f~:: ~,·:"t::;~; I 0:: 

-? , '.-1 ~~-,------;i",,""T:;-----~~l";I-'''¢ < '_,,~, 

, .", 'SubinissJon,Events"< . ', ..'" 

'. ._ , .'H-- , "{ ". ", 

; -~~ ,i/::' ~:;:,~~~ 

,,~ ,_~;' \,,~':t:..:!;, 

-1' ',~.: .,tf''_ < • - ;:":~~:~ ",' 

1/" "'~- ,~ ~ ~:-\\_' "~ ~~~"";\;~"~~ 

'it' " ~ t?:Ji:~< ~ :~~~}~(', r~~~~:, 

n \".~ II) I' 'V' Q ' II) ,,' :,"'IQ;~l* __ ~; :~'~p~~' 1;.,:::" 

L ___ -'-_________ -'_--'-- 

.,,'. 

J";-, 

'}:5~: \t~,;', "~;~~~~\:\, ~,~~~~!l~~:\ ~" , 

.',' , , , ,,'Pnor ' :"j~.", .. 

___ --' _'~" _ _ __ ~',~ ____ • ___ ' ,? !:.2~::: . __ _~~:':"'::':' __ ...1. ____ .L ____ ---L-____ ....... ___________________ _ 


Page 16 of43





,; ''r 

I, " ',/ 

.. 

,,~~ 

0:: - 

... 

.~~~ ~., 

~~ F '~l;~;~\ _I~ 

006 Configuration 

Management 

Plan 

J:d[,~~;; 

... 

III 

III 

"~~}~ 

i;':' " :J}.' , ,':; ,;.',,' 

~,' , 

t,,; t '",' 

" .. ' , 

_ r" \ .j 

:' :.~' 

, , , 

' ,~ 

;~ 

',t, 

, , . . , " , 

: 

, " ' '. : ~ 

: 

, , 

" 

, ./'~, ·7· 

I-:~:'t ~~;~r---r L' I ",.", '- 

:





ORO Title .=- 1 

~::r,.,,h' 

~J"(. 

, '.





r ,.-, 

ORO 

I Title 

CEV-T- Master 

015 Venficatlon 

Plan (MVP) 

CD 

a. 

>- 

I- 

I 

'"' .1 l, "'f 

".:' < 

I I· 

; >" ,I I'e 

CEV-T- I Certification 2 

~-," ":" If,,:: 

016 Plans I '.,,}_ ", ,\l 

CEV-T-I Certification 

017 Data Package 

rm· 

1"1 

I' -'I 

I ,; , : I 

'" , 

~.' ~ 

' , 

,,"{ , 

'" 

'"'- " " 

I' "-, I 

,~~Jtl~_" 

I:; ;\;r--ltf:~f:;:;r---~~;~;~i~:i:'1----~i~~~(!ir; 

~f,~t}~~ ~t~r;" :-" ~~M·\i~'''!~~~~·'' ~~:~1:~!~>/: 

I ,';" ':::' .. ,:.1 

.' , I ·Volume 5 ONLY, CEV Software & AVlomcs 

'-,.' ~''''o~_ . 1'1 - -, 

Venflcatlon Plan 

~~;~., 

'e-' , 

Update at PDR + 3 months 

Update at 45 days pnor to CDR 

, ' Final at CDR + 3 months to Include Software 

Venflcatlon Plan updates 

, 

" 

._-----------' 

I ",,'" ;;7i~~;- -, "1 

Imtlal 45 days pnor to PDR for the equipment 

~4S(navs; I - I' " "' 

.Lr '.', 

or facility It addresses Final 45 days pnor to 

,m""r 

CDR for the equipment or facility It 

addresses 

';flti~~~~;:~i: F - ~'~ 

,~,t0~{':'i ~ F Certification Data Pacakges shall be 

o i)j.,~,,,~tl1'"~ I, 45 ~:I- .:;l~~/, ,.;;~ 

~ ""~'('.(': -, ~""." 

completed at the spacecraft, module, 

.. - 

subsystem, and component levels. 

Certification reviews shall be held at each 

level 

·Spacecraft, Module and Subsystem level = 

Type 1 

Component level = Type 3 


Page 19 of43





CD 

a. 

>- 

ORO Title I- 

~~:~,,' Ci II) in '~V:;'; :'b,' ,'\;: ' any lime after final approval Complete re- 

," , , ' .'~ 1. " ' !', , : ~ , "." 

Implementatlo , , ", Pnor" ' '" ' ' " , " ' \ "_:,: ' 

Issue of the document IS required 

CEV-T'I """;-fr-n-i-r-1-1-'T-n-nr-------------- 

l .. ~t -. :J, 

n, and Control 

Plan 

",c ';,',r, ~!" 'I";;' \: ,',' "OF' ' 'V~1F,!1:!: Although the vast maJonty of MUAs will be 

fIt... j '~~" J:. \,.... ~i~,I[,." 

020 Usage ," i',', 

r:"i )\~,; "~,~ts" :,~:,~~: :.I"i~:~ Identified after PDR, the contractor shall 

Agreements 'L J , 

'"" ji:;!,,',~"i;~ ' ~1':", , M" ~,' ,;,,:.1 "~.",,, ,!/~~!~, I""" " -' Id(~ I d entl 'Iy an d prOVide pre I Imlnary MUA s 45 

(MUA) ,~/ ' 

CEv-:r.1 Contamination 

021 Control Plan 

(CCP) 

CEV-T- Materials 2 

022 Identification 

and Usage 

list (MIUL) 

2 

K",cf,.1 

~f§;\:; 

1f.f~"~~1 

y,' , '", >.i\ ""~'





,'( , 

c' ~,' :l,: .. 

~:\' ~~; 

~ )\":' ~~~~~s~t~)~~o~;~~vijnts_ ~(:,> ',; -~-~;St~-::':' 

ORO 

Title 

f f[~f ~I;' f ~~~ g ¥::;'~ ii~ 

~" ';\ 

, 

CD ~!a., ,"t;"H~' ;.!">!/l'l~«r'-'" C 1>,~,,},,\, ~~'i" Q!~ ,'" J')."It"r~ ~'5rlIfJ~ 

Q. 4/0.'·" Q.. I '~~;~, ~"'; ":~~'~'i', f/)' /) ~'D:'~ (I) :~~ C~,rQ ~ 0:: ,.·:~oe' t 

>- ·,·t1 " !;( ,,-,t-m'''' ";~~~~;' t.n "";'/'\>~D:(' (I) 1 

.... }~~_ ,J, Jk~;~,: ,~'C • 

,J 

....... 

~~~I.I;)/ 

,i"';1~;~~,,-1'~~ 

'.J ',"'~f , "





'> 

.',.,.< 

",' 

,'I'" ' 

Subnil\il.iJii:E~~~ts 

e • ~ " , 

~>, ',~ 

" , ~' 

,_ I • t 

,~ ,: 

ORO 

CEV-T- 

026 

Title 

Spectrum 

Management 

Documents 

.~ ?, 

I\~,~~ 

,-- 

I;~;~' 

;;~~" 

~ 1:8'i 

>- ..... '" 

.... 'A"I 

,_"" 

,I ".,'!-, i 

"P, 

... t; '~' 

... ,',Ill, 

ee tl, ,. -, ., 

-' 

II:: 

i ,e" o~ • 

j- .., 

, 

fi~j~t,:, 

['::.~ 

~ 

c " 

I ~ ,;,.~ 

~ '< 

-':"~teS", 

~ 

c 

~ 

II:: 

C 

II) 

II) 

,'" 

'!\ 

..... ! 

,,::,~&:~,"" 

',;;;a,:, 

• -'!' , 

..;."" >A' 

. ::;tt ';, "~,; 

'4s;D'ys" 

I' 'J5iior' 

II:: 





ORO 

CEV-T- 

027 

Tille 

Electneal, 

ElectrOniC, 

and 

Electromecha 

nleal Parts 

Management 

and 

Implementatlo 

n Plan 

CD 

a. 

~ 

~Ev-T- As-BUilt EEE ,-3 

028 Parts List 

J., 

~o;' 

-r:: 

i" 1 1,\, 

; 

;::;,,1',' 

, ~ -, 

;J? 

~?g:f' 

~~,.' 

~ .. ~., 

"- 

!;t 

" 

, ,.J: 

iii:: 

:!!! 

, \ 

0:: 

C 

I/) 

F 

45 

Oays 

Prior 

", '-" 

""\"~~'~' 

;;.1O::~~ J 

''''!''In " "it ., 

':~·~~;/:'r'; 

" 

, ' 

j 

'" 

,,'\ 'Si:ibm\S$i~ri:;;ey~ntS' 

''', 

~"i'1-. ~ 

i2" ~ ;'(', 

c ", 

- ""'»,;} 

i'lc;~~ 

" 

,~\ e' .tl~ 

'J), 

i2" I' ~, 

c 

~ 

0:: 

C 

I/) 

I/) 

-'.: 

" " 

I ~";. , 

t' 

,,~ 

:,' 

,,' 

,f 

I~; i,~';}:~f 

k 

',.," 

'.:' 

~ 

"""\ 

t, l' " 

:\~"~ 

,"0::1 " 

,:"",,~,P'/ 

i"~1 L' L I ~" I I' 

~,-,- - ,-,-'-, -- -,-~~'''. :~-+---- - +::_~~,~-+----+--'-," -:\--- --+-----r ū -- -------, 

The As-Built EEE Parts list shall be 

submitted With each acceptance data 

L _____ -L ____ H _______ ~_ ....J. ____ ...J._ .. __ . ___ I ______ .-1_.-.:. __ .. .:.._._1 _______ 1 __ ~ __ .. _ .. L-__ --1._. _____ L-__ -.l-.. __ .H_H • .l-____ _ 

" ~\ 

Iii 

(5 = 

Noles 

package (CEV-HI40) 


Page 23 of43





., 

DRD Title 

Q. 

~ 

CEV-T- Interface 113 

029 Control see 

Documents notes 

I;; 

.c 

5 I Notes 

I,F,U 

I Onon-GS Volume 5 Onon to CCCE lCD, 

Onon Vehicle to MIssion Systems External 

lCD, Onon Vehicle to ISS Extemal Software 

ICD ISS GN&C MOM Passthru Interface to 

ICCA, Onon Vehicle to ISS Extemal Software 

ICD ISS PCS to Onon Ethemet lCD, Onon 

Vehicle to ISS Extemal Software ICD ISS to 

Onon ICCA Ethemet lCD, Onon Vehicle to 

Lander Extemal ICD (Vol 2), and Onon 

Vehicle to Ares Launch Vehicle Extemal ICD 

(Volume 2) . 

Imtlal PDR + 3 months (Type 1) I,F,U 

Final 45 Days pnorto CDR (Type 1) 

All other Module and ExtemallCDs (Type 1). 

Imtlal 45 days pnor to PDR 

Final 45 days pnor to CDR. 

Subsystem (Includes MGSE, GFE, EGSE & 

Simulator) ICDs (Type 1). 

GFE secllons only of Subsystem ICDs Will be 

delivered at PDR - 45 days 

Final 45 days pnor to CDR 

Software IDDs 

Imtlal PDR + 3 months (Type 3) 

Final CDR + 3 months (Type 1) 

All levels. Update as required after Final 

delivery 

(CEV-T -035) 

J-2 DRD Submission Matrix 

Page 24 of 43





ORO 

CEV·T· 

030 

Title 

CEV/Constella 

tlon Integrated 

Assessment 

Document 

r..~" 

:;':' 

i'" ~", 

'f>;",~" 

" -~ 

-f;. , 

,~:t' 

{O" " 

CD ~ar. 

Q. iO (~ 

~ ~~~~~ 

2 

", ""' 

, ' 

_ ___ --L-_____ -'-___ ---L--:l _____ L 

," 

.\ ,", 

( -,' 

, ~ " 

a.. ~,' ~).1.."'" 

I- :'iir 

II:: 1;-' -"0: " ; 





.. 

c- 

ORD Title ~ 

CEV-T- CEV 1/3' 

031 ReqUIrements 

Specification 

Notes 

Ground and Spacecraft System-level 

Requirements Specifications 

Initial 50 days pnor to CEV SRR 

Final 45 days pnor to SDR 

Module-level Requirements Specifications 

Final 45 days pnor to SDR 

Subsystem-level Reqts Specs (Includes 

GSE) 

Initial 45 days pnor to SDR 

Final 45 days pnor to PDR 

Component-level Reqmts Specs (Includes 

GSE) 

Final concurrent with the Specification 

approval by Lockheed Martin Program 

Management. 

Alileveis Update as required after Final 

delivery 

• System-level, Module-level, and 

Subsystem-level ReqUirements 

Specifications = Type 1 Component-level 

ReqUirements Specifications = Type 3 

(CEV-T-032, CEV-T -(34) 


Page 26 of43





:t 

>- 

DRD Title 

.... ~~:~ :.r: 

,III"" U) .l.f ~'l((ji:'t 'j '~7~~' ,;~ 

rn ;t,~~ F~tl';('\;~ « 

, I"\':'~' ~~2:~t~~ 

0 Notes 

~h':'~-'4,,~~,. ,.r.,h'~";:.ii\I\+l"" I)~ h ~ \rk~,J (' 

' ' , "0" 

CEV-T- CEV 

U 

Ir~~H 

«- ;;\'i/l;!'/tli:·V·,l\ J\\(~"~i=1~ -. ~ ';~tj;~ ~~':" ,~. {,"':t\~~/ with each delivery of the requirements, 

including CEV SRR. (CEV-T-031. CEV-T- 

032) 


Page 27 of43





ORO 

CEV-T- 

035 

Title 

Intemal 

Interface 

Requirements 

Document 

(IIRD) 

»' 

I~' ' 

l/i~: ;;,;, 

\ ",' 

I '~~;".' 

)"""" ,( 

t:oj 

.. ~Q." 

~ ','e'" 

I- ~l/,' 

~,- 

" 

~< ,)< ,;:I~":,~ 

\; '~':'~ ~'~~~(- 

{:~i~~~ 

I }~i,~'; -~ 

"," " 

~ I :/i!{:' 

c:c '~" ""£11":;" 

:~(~~-;::tdl 

, ... , 

i 

~ 1 

, . 

, ' 

, ':'-,





CD 

ry;, 

~),';\'fD:' ., 

D:: 

?:?!l};;1 r' ' ' , I' 

'5, 

('-; " , 

~~,~~\,,}~, , 

1 "',





ORO Tille 

CEV·T· Acceptance 11314' 

040 Data Package 

CD 

a. 

>- 

I- 





DRD Title r= lji;i/I U' 

, 

..' Radiation 

45 " ' '"4s"Days '''45illiSi , ...... J ,. 

AnalYSIS and ~ : "' Days 'Pr,ior: . : JP.tior 

Certification 

Prior 

11,1 !,,< 

~, r~," 

Report 

\r:,~j '~, ~ \ 

, ' '---",'"-\ 

CEV·T· I CEV Data and ,.~ ~. : .:~' I ' ,. 'U. : 

046 Command '4S'/lav .. I;,45lDays :, 

Dictionary 

3 '~-~~:':.< 

-ft-~'m-t1t-~~~ 

,:~:~l~~.:~' ,.': ~ ~





G> 

a. 

... 

ORO Title 

.... 

CEV-T- Software 

048 Requirements 

I ',I I 

., no . 

~,-, - ~~ 

.\, I ,';" ~~ • 

Specification 

1 ',>;",- 4' ,;.: ':: ,~,(: ' mo~l6\i, 

r _, j 

-:-, '- ~ , 

CEV-T-T Monthly 

049 Software 

Metnes Report 

,"'~"' I I~"~::~'\ ',I I,' J~;::':)I I" '''~i I r~,::': '1 

I SRS Final Three (3) months after PDR 

Updates as required to display format 

dlctlonalY though AR 

The Display format and associated 

Simulation Software SRSs to be proVIded In 

NASA approved Increments between PDR 

and CDR The 75% complete verSions of 

these SRSs shall be proVIded by CDR, with 

the final versions provided at 60 days post 

CDR 

Update as reqUired after Final dehvelY 

(CEV-S-018, CEV-T-057) 

13f 3", n";'~n7"i;",)r-r''''''';-r----T-;-;;-;"-r--li'\;'7i7;'r----i:---- 

?:" ,~ ; :'tl\;)~ " ,,~;>'l' ,,,". " ~"':~,' i\; ,. U Other = Monthly by the 22nd of the reporting 

, j _ ;}: i ! ;





CI. 

>- 

ORO Title I- 

CEV·T· Software 5 ;~:,I';(;: 

.,l 

' 

051 Inspection and " 

Peer ReView 

Report 

.. 

'~J/ .::~/,r I/) 

'~~?I~;~~ J 

" , '}'~;;': ,~~ 

" 

052 Plan ~>o , '.' -- ", '; "~'5~1'; . 

CEV:r:tsOftware i~'-r-2Tr--l--' T---r~r1--rJt I 

til 

'" 

Iv "F.:', 

',tseet " 

I 





DRD 

CEV-T- 

054 

CEV-T- 

055 

CEV-T- 

056 

Tille 

Software Test 

Report 

Software 

Maintenance 

Plan 

Software User 

Manual 

! 

2 

-t--+ 

2 

2 

I. "d; 

" !ti, 

it~~;t,:' 

,.e" "'1 

'lfci:"~r 

~~&':" 

ta.i,'~ 

Ife,'~ 

~~~,:; 

>',' 

"- 

!ci: 

,v 

Ii:: 

!!t: 

, ""-?, '~" 

,- ;., ~ ,). 

~ 

Q 

~ 

II:: 

Q 

Z! 

c, 

"." , ' 

·'1 ' '-;' 

~/ 

I:;?~~~': 

'I '(,)" 

"~,)::~ 

(;1: 

'1;':,"1,1;,,"10'" ~ ,,~ .~~~,',~ 

" ~ ~ 

- 

>.,'. ::1:'\,' 

, .~ ,, 

F 

Compfet - 45 

,ionOf Days 

,'fits. 

Prior 

till 

, SIW,;. 

sPi~' 

rereaSe 

litiW 

:CDR 

::.~rd.:. 

~, Nr 

, :~~,:~ 

,. ;manUis' 

jr'rafteiitT 

,::CDR,; 

Zt~~~1 

I' 

,-, ""1.411)1; ' 

~ ',~: -1~i\t; , 

" 

.. , 

il 

o 

u 

Noles 

One document delivered per CSCI 

Redellvered In conjunction with each formal 

software release 

(CEV-T-053) 

1;';;:t~lI'\ I"~ 

~>~+~~:~~'j", 


Page 34 of43





ORO 

Tille 

~ 

Noles 

CEV·T· 

057 

Software 

Version 

Descnptlon 

Document 

3 

-, 

U,F 

Redelivered m conjunction with each formal 

software release (CEV·T -0(8). 

Radio 

FrequencylOp 

tlcallCDs 

Update as required after Final delivery 

CEV·T· 

059 

Electncal 

Power System 

(EPS) Design 

and Data 

Book 

CEV·T· I Electrical 

060 Power Quality 

Specification 

Requirements 

Document 

Design and data books are Intended to be 

liVing documents mamtalned throughout the 

design and development process By 

acceptance review the design and data 

books should transition to operational data 

books 


Page 35 of43





'-,'I 

~ 

.[' .... 

) 

~O;,' D- 

>- ,tt" ' !;( 

DRD Title .... 

il-1~ ',' 

CEV·T· Mechanical 3 (~.'; 

061 Systems 

Design and 

Data Book 

----r----- CEV·T· Stress I --2 

062 AnalYSIS 

Report 

--t----- 

063 Thermal 7 

, ,P'DJIi;' 

. '!&Jiif' 

" /, :; 

CEV·T· Passive 3 I 

:d;::k,;, 

Control 

Design and 

Data Book 

(PTCDDB) 

CEV· T·I Passive 3 

064 Thermal 

Control 

Mathematical 

Models and 

Documentatlo 

n 

Days 

Prior 

t ,~)~'~,~'~ ;::J~~ 

~lii;!~)': 

u {;';:~"~: ,~ 

:.iJf~ 

,',~ 

7 Days 'i/p'~~ '"t~ .\ , 

,,~ , 

Prior ~\~~~~~9~"1 _ 

~"'i . 

'f"l , :sr~" "; 

:¥ ~.,' ,~~, ;,'~ 

tstr~:~1W,! ~ , 

o:: 

« 

U 

45 

Days 

Prior 

Prior 

u 

45 

Days 

Prior 

~~~i$ 

",.af~".).~", 

,,";'$~!" 

!'lf~. '!,.t~ ~'" 

;.~~:~}f:~ 

~~,~m





ORO 

Title 

~ 

.c 

S I Notes 

CEV·T· Thermal 

065 Protection 

System 

Design and 

Data Book 

(TPSDDB) 

I 

3 

' . 

Iv 

': 

, ' 

1 

I_ 'f 

CEV·T· I Thermal 3 I 

066 Protection 45 

System 

Days 

Mathemallcal 

Prior 

Models and 

.' 

Documentatlo 

n 

" 

. 

1 

I: 

" 

1 

I 

7 

Davs 

I"~"; )'1 

u 

,', ;~" , 7 D~ys 

: . Pnor I "._ 

, ~ :'L'- , :J):. 

",~'~!IyS, . 

:'~rior 

Design and data books are Intended to be 

hVlng documents maintained throughout the 


acceptance reVIew the design and data 


books 

-"--.-."---"-----+--''74-----1---------.-------------- 

~!)ay,s 

_'I!ii~r. 

-';' " 

F 

45 

Days 

Prior 

I ' 

" 

CEV·T· Structural 2 

067 Loads Data 

Book 

CEV·T· Structures 3 

068 Mathematical 

Models and 

Documentatlo 

n 

CEV.T·I Fracture 2 

069 Control Plan 


Page 37 of43





ORO 

Title 

CEV·T· Fracture 

070 Control 

Summary 

Report 

-1-' .,....;:1';;--,.,... 071 Systems n-r-n;T~ 

. " , '"'.''' 7 " 

Design and " ' "', Days, 

Data Book " ',' Prior' ," 

CEV·T· TSUIts. EVA 3 

I," 

I 

072 and Survival 7Days 

Crew '\ Prior 

EqUipment 

Support 

,,' 

---n:--r 

' -~ ~ 

Systems 

Design and 

Data Book 

r 

CEV· T· EnVIronmental 3 

I 

~~\, 

073 Control and 

f/' 

7 ~W~"lI 

~~' ~p'~\~.~~~' '~'"" 

• ',1 .~ 

,)1'J?, 1,,)/,,( 

life Support 

,





.. ... 

ORO Title ~ ~:~~~ 

';1 ,~,j 

CEV-T- Habitation 3 

074 AccommodatJ 

ons Design 

.2:' 

and Data 

Book 

CEV-T-/ Pyrotechnic 3 J. 

075 Subsystem 

, 

7 

Design and 

~ ~ j' 

, 





DRD 

CEV·T· 

078 

Tille 

GN&CDeslgn 

and Data 

Book 

:t 

?:: 

3 

( ~;:::~, 

-~, 

~'. 

" 

tt~ " 

It,~< 

:~~' 

'1,~{ 

1",':f"", 

~ct!:1~ 

llO:;r,! 

~JO.~I' ... 

'D= !;( 

Ii=~'i!-, 

~.\,:.. 

;-y 

;~~ " :,'1, 

"~' 

"',' 

•• ", 

1]" 

I'





.. ~~~v 

0:: ;" ~£~ac;)\ ~ 

"0:: 

>- C 

ORO Title IE;"" !;;c III- 

I- 

, ~;'~"\' 

t~'~~,,' 

", ,\ ~' "\ ,t't, ...'i('{~",",h 

", 

CEV·T· launch Abort 3 , 

y\:>':j;-: 

' j':i 

081 System Fi?' 

\ ,,,.,' 

Design and 

" t 

Data Book 

'" 

a. hO>" . 

a.. 

, -, I/) 

~,.' 

, 

,.". 

," . .. . , 

,.,!"; ) 

CEV·T· I Spacecraft 

I 

1:;'1,;; 'I 

082 Test & Ie 

I, ·1 

1-.. " 

.,"" 

45 ,t~:t~~i.~y~:;~ 

~I,.-, 

Venflcatlon 

FaCIlity 

System 

ReqUirements 

Dccument 

,~ ., . 

'!f'i 

tf'!~%j .. ,- 'I 

c 

I/) 

I/) 

See 

.... 

:' ~~~~ 

I/) 

f~6~~: 

I/) 

,?~;~~:~~ 

1 ~'-'~~,~~~j~ 

~ ~" ::i,::~:. ~, See 

f~' J;="~~~;' ,\ 

notes ~457QiVs:, notes ,l45oays 

' Prior,' 

,; ;~ndr) 

." 

'. 

·1 

I' 

~ 

..... 'I 

: ~ I" 

.' ' f ; '- 

. . , " 1 

lilii'·4l ~,~ ~, 

'i~f" '_~ ~~; l 

"0 I, ,j ,'f.. 

\ ~"1~;;~t! ~~ < II 

•.:1 , , 

" ..... , I 

0:: 

« 

U 

45 

Oays 

Prior 

. ;~ 

.. 

~ 

' i;, 0::. .c 

':/t'~h;: 

S 

Notes 

" , 

.. ,' .F Design and data books are Intended to be 

liVing documents maintained throughout the 


acceptance reView the design and data 


I books 

1 

; I 

, ~'! 

t 

._- ----- ----------------_. 

. " . F* *T·082·200 (EEST) Only 

L. '., > Final delivery 22 weeks after PDR Board 


Page 41 of43





DRD Title .:= 

CEV-T- Spacecraft 3 

083 Test & 

Venflcatlon 

Facility 

System 

Design 

Document 

CEV-T-I Spacecraft 2 

084 Test & 

Ven~cafion 

Facility 

Certification 

Plan 

CEV-T-I Spacecraft 

085 Test & 

Verification 

FaCIlity 

Certification 

Package 

CEV-T- I Manufactunng 2 

086 and Assembly 

Plan 

CEV-T- CEVHandling 2 

087 and 

Transportation 

Plan 

'!il';:, :;( .", j~W\,,'~ 

in en ~~ ~~;:~;~~.; ',: 

If'''';:;: _~ 

"~\;~, ';';'}',~f 

{i:~- I" I::;~~:'~ 

~', , 

In 

i:~C.4t~s\ « Notes 

~:q :',~;~~::' ,'''I;" Y 

U 

Update as reqUired after Final delivery 

I -1-----t-c---:l---t.c~--'-r------~~----l--t-' -I--~--:t--li------------- 

~-,_, ',": 1-';,-;: :': ': ';: _~: " '-':-, ,~ :; , " :,: -: ,~", U Update as reqUired after Final delivery 

~~''''''' 

[\2';-;'Y 

r 

'~;v-~'i~' 

~::i~l~;~ 

i;:~~~~"~~~'~ 

;,,'I-\~\;;$..~~'. _" 

1~!.)';),'~"', '~"I(" 

I- ~/, 'f~W':t\lrlt\1}~~~ 

,- ' '.itl':tii~~ ~~''''' 

it/,,~ 

1,;;'''-_ 1:>:lit~ 'I 

~l~~~ 

s~~~::t}¥:: 

~~M:~\l 

', .. :\".;lr~(i/..t~ 

r~' 

~, 

F* *EEST FacIlity Certification Package Only 

NI·, ••:!t-~~ 

45 'i~:;T:~:1:~~~ Final @ EEST 00250 

Days F ':"1, ~-k'i.;ff;'!1f 

. ~:~~;'1JfN~~ 

Prior i>: 

All other FacIlity Certification Packages 

,c,';'f.;" 

,iJ~f(~~ 

Due 45 days pnor to the vehicle acceptance 

~'~;f~;r,'~ 

review 


Page 42 of43

,~,~ , 





,l-. 

:: 'slilf.¥ii~lron;EventS 

,::l:' V'~, ~- 

)~ . 

.,., , 

eo"~ " ' r ,-, 

~. ,". 

DRD 

CEV·T· 

088 

CEV·T· 

089 

Title 

CEV Imagery 

Plan/Imagery 

Dehverables 

".,«:' 

:..;;~~ 





ATTACHMENT J·3 

May 2009 

APPLICABLE, GUIDANCE, AND INFORMATIONAL DOCUMENTS 

LIST 

Note - DRD and reference columns for updated documents are 

not fully defined 


1 of 73





TABLE OF CONTENTS 

1.0 APPLICABLE DOCUMENTS............. . ...................... . 

1.1 APPLICABLE DOCUMENT CHILDREN 

1.2 APPLICABLE ENVIRONMENTAL DATA 

2.0 GUIDANCE DOCUMENTS .................. .. 

3.0 INFORMATIONAL DOCUMENTS ............. .. 

.. ...................................... 3 

............... .. .... 20 

.. ........... .. .... 59 

.................. .. .. 60 

.. ................ 70 


20f73






In addition to the regulations and procedures identified elsewhere In this contract, the Contractor 

shall comply with the following regulations and procedures to the extent that they are employed in 

the Statement of Work (SOW) or Data Requirements Documents (DRDs). Applicable document 

versions that are in effect at CFI release constitute reqUIrements for this contract. Any applicable 

and reference documents embedded in the applicable and gUidance documents listed In this 

attachment shall not be applicable unless overtly specified as applicable in the SOW or DRDs. 

After contract award, the Contractor may request use of alternate applicable documents instead 

of the ones specified in this list, provided the change is in the best Interests of the Government. 

NASA approval is required for a change In applicable documents after review of the contractor's 

rationale A request for a change in applicable documents will be documented in a contract letter. 

NASA approval or disapproval will also be documented In a contract letter. Since NASA cannot 

fully define all engineering and workmanship standards based on program and requirement 

maturity at thiS time, the contractor shall define recommended additional standards to apply to 

Level 3 specifications. The contractor shall Identify these additional standards to NASA for 

approval via contract letter and make these standards available to NASA for review. NASA 

approval or disapproval will also be documented in a contract letter 

Items listed In the Applicable, Guidance, and Informational Documents will contain some items 

that have been determined as export controlled documents. These documents are so marked 

and anyone With access to the documents must comply with the export control law. This includes 

both control and disclosure of any said documents Other documents and data listed may not 

contain any restrictions, however before the release of any Information or data the Contractor 

shall make a determination as to the applicability of U.S. export control laws and regulations. 


30f73

0- 





10 

REFERENCES 

Document 

Version/Date APPLICABLE DOCUMENT TITLE ORO SOW 

-- 

450-SNUG 

AFJMAN 24-204 

AFSPCMAN 91-710, 

Volume 2 and Volume 4 

-- 

AIAA-S-080 

------------ 

ANSIIAIAA-S-081 A-2006 

ANSIIEIA-748-98 

ASMEB46.1 

-- 

-- 

ASMEY14.100 

f-- 

ASMEY14.24 

1-- -- 

ASME Y14.34M 

ASME Y14.35M 

CxP-02007 

1---- 

CXP-70017 

Rev 9 Space Network Users' GUide CEV-T-058 2.6.3 

Aug. 2007- 

Aug. 2012 

12 Oct 2004 Prepanng Hazardous Matenals for MIlitary Air Shipments 2.613 

Suppl1 -1 

Dec 2004 

---~-------- ------------------- ------------- 

1 July 2006 Range Safety User Requirements Manual, Volume 2 and Volume 4 CEV-O-007 

- ---------- 

1999 AIAA Standard for Space Systems - MetalliC Pressure Vessels, CEV-T-071 

Pressunzed Structures, and Pressure Components 

-------------------------------------------- 

2006 AIAA Standard for Space Systems - Composite Overwrapped CEV-T-071 

Pressure Vessels 

-------1-- -------------------- 

1998 Earned Value Management Systems 

1-------c------------- 

CEV-B-003 

-------------- 

Surface Roughness, Wavlnes, and LAV 

f------------------------------------------------ - 

2004 

i-- 

Englneenng Drawing Practices CEV-T-004 

--- ------- 

--- 

Types and Applications Of Englneenng DraWings 

1----------- - 

CEV-T-004 

-------- 

Associated Lists 

CEV-T-004 

-+--- -- 

Englneenng DraWings and Associated Documents 

CEV-T-004 

Draft21 Dec Constellation Nomenclature Plan 

2005 

--r-- - 

Baseline Constellation Program Probabilistic Risk Assessment (PRA) CEV-S-002, 

Release Methodology Document CEV-S-010 

17 Sept. 2007 

+ Errata 

11 Jan. 2008 

26.13,33, 

27.4 

------- 

2 3.(c), 6 1.3, 

6.2.3,643 

1---- 

2.3 (c), 6 1 3, 

6.23,64.3 

1--------- 

1------------ 

26.13h) ---- 

--_._----- 

1.3 (a), 2.6.4, 

2.7.2 


40f73





ID 

CxP-70022-01 

CXP-70022-02 

-------------- 

CXP-70022-03 

Document 

Version/Date 

Revision A 

Release 

20Sep 2007 

+ Errata Rev 

0018/11/08 

Baseline, 

Change 001 

Release 

23Aug 2007 

+ Errata Rev 

001 8/11/08 

Basehne 

Release 

03 Oct 2007 

+ Errata 

1/11/08 

CXP-70022-04 

RevIsion A 

Includes Applicability (Draft) 

Matrix VOL4-REVA- Release 

APPLICABILITY-072118 16 Nov 2007 

CXP-70022-05 

+ Errata 

1/11/08 

Basehne 

Release 

09 Jul 2007 

+ Errata 

8/11/08 

APPLICABLE DOCUMENT TITLE 

Constellation Program Command, Control, CommUnication, and 

Information (C31) Interoperablhty Standards Book, Volume 1: 

Interoperablhty SpeCification 

_. 

Constellation Program Command, Control, CommUnication, And 

Information (C31) Interoperablhty Standards Book, Volume 2: 

Spectrum And Channel Plan 

----------_._---- 

Constellation Program Command, Control, Communication, and 

Information (C31) Interoperablhty Standards Book, Volume 3· Master 

Link Book 

- 

Constellation Program Command, Control, Communication and 

Information (C31) Interoperablhty Standards Book, Volume 4· 

Information Representation Specification 


Information (C31) Interoperablhty Standards Book, Volume 5. Data 

Exchange Protocol SpeCification 

DRD 

CEV-T-026, 

CEV-T-047, 

CEV-T-058 

CEV-T-047, 

CEV-T-058, 

CEV-T-026 

CEV-T-047, 

CEV-T-058, 

CEV-T-026 

----- 

CEV-T-046, 

CEV-T-047, 

CEV-T-058 

- 

CEV-T-047, 

CEV-T-058 

REFERENCES 

SOW 

2.61,2.6.3 

261,263 

r------ - ---- 

261,263 

------- 

2.61,2.63 

2.6.1,2.63 


50f73





Document 

10 Version/Date 


ORO 

REFERENCES 

SOW 

CXP-70022-08 

_.- 

CXP-70023 

Baseline 

Release 

09 Nov. 2007 

+ Errata Rev 

001 8/11/08 

Baseline, 

Change 001 

18 Jul. 2007 

+ Errata 

1/11/08 

CXP-70024 RevIsion A, 

CxP-70026 

-- 

CXP-70028 

Change 001 

Release 

30 Oct 2007 

+ Errata Rev 

0018/11/08 

-------1--_._-------------- 

Baseline 

Release 

8 Oct 2007 

+ Errata Rev 

001 8/11/08 

Baseline 

Release 

09 Oct 2007 

+ Errata 

1/11/08, 

Rev 001 

8/11/08 


Information (C31) Interoperability Standards Book, Volume 8 

Common Command and Control Functional Requirements 

-- 

Constellation Design SpeCification for Natural Environment 

-- 

CEV-T-047, 2.61,263 

CEV-T-048 

- 

CEV-T-044, 2.8.1,282, 

CEV-T-045 283 

-.-(----------_._---- - -+----------------- 

Constellation Human System Integration Requirements (HSIR 

CEV-T-045, 2.6,2.7.1,28.7, ' 

CEV-T-089 2.8 3, 6.1.3, 

623,6.4.3 

anon to Ares I Interface ReqUirements Document 

anon to Ground Systems Interface Requirements Document 

--------~ ._----- 

CEV-T-026, 

CEV-T-058 

23.(a) 

2.3. (a) 

._--- 


60f73





REFERENCES 

ID 

Document 

Version/Date 


DRD 

SOW 

CXP-70029 

-- 

CXP-70031 

-- _._---- 

CXP-70033 

-- 

CXP-70034 

Baseline 

Release 

9 Oct. 2007 

+ Errata-Rev 

001 8/11/08 

Baseline 

Release 

30 Nov. 2007 

+ Errata Rev 

0018/11/08 

Baseline 

Release 

10 Oct. 2007 

+ Errata Rev 

001 8/11/08 

Baseline Draft 

Release 

02 Oct 2007 

+ Errata 

1/11/08 

-- 

CxP-70035 Baseline Draft 

02 Oct 2007 

+ Errata Rev 

0018/11/08 

Onon to MIssion Systems Interface Requirements Document 

--- 

Onon to Intematlonal Space Stafion Interface Requirements 

Document 

- -------------- 

Onon to EVA Systems Interface Requirements Document 

-------------_._------ ------- 

On on to LSAM Interface Requirements Document 

Portable Equipment, Payloads, and Cargo Interface Requirements 

Document 

CEV-T-026, 

CEV-T-058 

CEV-T-026, 

CEV-T-058 

r-- 

-------- 

CEV-T-026, 

CEV-T-058 

2.3 (a) 

2.3. (b), 10.2 3 

--- 

2.3 (a), 2.6 11 

------- 

2.3 (a) 

23 (a), 2 6.12 

- 


7 of 73





Document 



ORO 

REFERENCES 

SOW 

CXP-70036 

CXP-70038 

Revision A 

Release 

05 Sep.2007 

+ Errata 

1/11/08 

--_._---------- 

RevIsion A 

15 Oct. 2007 

+ Errata 

11 Jan. 2008 

c----------------------- - --- 

CxP-70041 

Baseline 

Release 

14 Nov 2007 

I- 

CXP-70043 RevIsion A 

Release 

r--- 

CxP-70044 

11 Oct 2007 

+ Errata 

1/11/08 

Baseline 

Release 

17 Aug 2007 

CXP-70050-01 Rev A, Chg 1 

CxP-70050-02 

30 Nov. 2007 

Rev A 

26Jul. 2007 

Constellation Environmental Qualification and Acceptance Testing 

Requirements (CEQATR) Document 

------ 

Constellation Program Hazard Analyses Methodology 

._._---------------------------_._----- 

Constellation Program NExlOM Standard for Tool, Model, and 

Simulation Data Dellvenes 

-- -- .' ._- 

Constellation Program Hardware Failure Modes and Effects AnalySIS 

and Cntlcalltems List (FMEAlCIL) Methodology 

- 

Constellation Program Natural EnVironment Definition for DeSign 

(NEDD) 

Constellation Program Electncal Power System Specification Volume 

1 Electncal Power Quality Performance for 28VDC 

Constellation Program Electncal Power System Specification, 

Volume 2: User Electncal Power Quality Performance for 28VDC 

CEV-S-003, 

CEV-S-005, 

CEV-S-009, 

CEV-S-011, 

CEV-S-013 

---------- 

CEV-T-001 

CEV-T-002 

------- 

CEV-S-009, 

CEV-S-011 

CEV-T-044, 

CEV-T-045 

- 

1021 

3.2,3.4 

-- 

---------_.- 

24 

~-- 

--- 

28.1,28.2, 

28.3 

------ 


80f73





Document 


CXP-70059 Revision 001 

14 Oct. 2008 


Constellation Program Integrated Safety, Reliability & Quality 

Assurance (SR&QA) Requirements 

ORO 

REFERENCES 

SOW 

-----;------ 

CXP-70065 

Section 3.5 Only 

Baseline 

Release 

11 Oct 2007 

+ Errata 

1/11/08 

-------------- ------- 

CXP-70068-01 

Baseline 

CXP-70068-02 

------------ 

CXP-70068-03 

- 

Change 002 

11/07/08 

Baseline 

Release 

6 Sep. 2007 

Baseline 

Release 

6 Sep. 2007 

-- -- 

CXP-70070-ANX05-01 Baseline 

Release 

22 Aug. 2007 

+ Errata 

Rev 001 

8/11/08 

------ 

Constellation Program Computing Systems Requirements Document 

- ------------_.._---- - ------------------- 

Constellation Program Problem Reporting, AnalYSIS and Corrective 

Action (PRACA) Requirements, Volume 1, Problem Processing 

Requirements 

------ -- 

(Constellation Program Problem Reporting, AnalysIs and Corrective 

Action (PRACA) Requirements, Volume 2, Information Management 

System Requirements 

--- 

Constellation Program Problem Reporting, AnalYSIS and Corrective 

Action (PRACA) Requirements, Volume 3, Appendices 

-- 

Constellation Program, Program Management Plan, Annex 5: 

Security Management Plan; Book 1 Information Technology (IT) 

Functional Secunty ReqUirements 

------1-. - 

CEV-T-005 112 

CEV-S-013 

_._-------- 

CEV-S-013 

------- 

CEV-S-013 

----------- 

CEV-T-047 

-------._._- 

1------------- 

1.5 (b), 1.1 (e) 


9 of 73





ID 

CXP-70076 

Document 

Version/Date 

Baseline 

Release 

19 Dec. 2006 

+ Errata 

1/11/08 

-----------1-------- 

CXP-70080 

Revision A 

Release 

30 Aug. 2007 

+ Errata 

8/11108 

-----------._- ----------- 

CXP-70118-01 

CXP-70130 

CXP-70135 

CxP-70138 

RevIsion A 

Draft 

28 Nov. 2007 

+ Errata 

1/11/08 

Baseline 

27 Jul. 2007 

+ Errata 

1/11/08 

--- --- 

Baseline 

Release, 

Change 002 

05 Dec. 2007 

+ Errata 

Rev 001 

8/11/08 

Baseline 

Release 

25 Sep 2007 


Constellation Program Modeling and Simulation Management 

ReqUirements - Level II 

Constellation Program Electromagnetic Environmental Effects (E3) 


1------------- 

Constellation Program Systems to Communications and Tracking 

Network Interface Requirements Document (IRD), Volume 1: Onon 

1------ 

Constellation Program Extravehicular ActiVity DeSign and Construction 

SpeCification 

---_. 

Constellation Program Structural Design and Venficatlon 

ReqUirements 

Level 2 Coordinate Systems 

--- 

DRD 

CEV-T-001, 

CEV-T-002 

1---- 

CEV-T-026, 

CEV-T-058 

TBD 

CEV-8-016, 

CEV-T-015 

CEV-T-002 

REFERENCES 

2.3 (a) 

SOW 

------------ 

TBD 

1------_.- 

24 


10 of73





Document 



REFERENCES 

--- 

ORO 

SOW 

CXP·70145 

CxP-70146 

Baseline 

Change 001 

9/29/08 

Baseline 

Change 001 

9/29/08 

----_._._------------ 

CXP·70152 

Baseline 

Release 

--------- 

03 Oct 2007 

- 

CXP·72000 

RevIsion B 

-.----------- 

CxP·72008 

CxP·72085 

CxP 72095 

Release 

2/12/2008 + 

Errata Rev 001 

8/11/08 


18 Dec. 2006 

Revision A 

06 Dec. 2007 

Baseline 

March 1, 2007 

-- 

Constellabon Program Contamination Control Requirements 

Constellabon Program Acceptance Data Package (ADP) 

Requirements 

CEV-T-021 

CEV-T-040 

---- -------------------------- 

Constellation Program Crew Interface Labeling Standard 

CEV-T-089 

- ---------_._-------- - --- -------------- 

System Requirements for the Crew Exploration Vehicle Element 

CEV-M-001, 

CEV-M-002, 

CEV-O-001, 

CEV-S-009, 

CEV-T-031, 

CEV-T-034 

- --------- 

Crew Exploration Vehicle Project Plan 

CEV-M-005 

Constellation Program Crew Exploration Vehicle {CEV} Spacecraft 

Outer Mold Line (OML) 

Crew Exploration Vehicle (CEV) Thermal Protection System Design 

Standard 

TBD 

TBD 

-- 

2 2.1c, 22 2c, 

61.4c, 61 4g, 

62.1.1f,64I, 

6 5j, 9.2p, 9.2s 

------_. 

2.8 7 

------ 

Scope, 11,22, 

2.3 (c), 3.1, 

6.13,6.1.61, 

6.23,6.261, 

6.4 3, 6.4 61, 

65.3,2.6 

(b),2.7.2 (e), 

6 1.6.2,6 4.6 2 

Scope, 1 4, 2.1, 

2 3.(c), 24,2.6, 

61.1,62.1, 

64.1,11 (e), 

410 

2.3 (c), 106.6 

6.1.3.8 


11 of73





REFERENCES 

ID 

Document 

Version/Date 


DRD 

SOW 

CxP-72097 

f-------- 

CxP-72166 

Baseline 

01 Mar 2007 

+ Errata 

1/11/08 

Baseline 

4Jan 2007 

----_._-_._------------- 

CxP-72167 

CxP-72168 

CxP-72213 

CXP-72242 

1--- 

CXP-72091 

Latest CPCB 

Approved 

version 

-i--------- 

Latest CPCB 

Approved 

version 

--------- 

Baseline 

Release 

17 Aug 2007 

Draft Baseline 

Release 

14Dec.07 

Baseline 

Release, 

7/1/07 

Crew Exploration Vehicle Master Venficatlon Plan 

Flight Test Vehicle MIssion and Flight Directives 

-- ------ 

Onon AerodynamiC Database (for all phases of flight) 

------- .. _._--------------------- 

Onon Aerothennodynamlc Database (for all flight phases) 

.. ---- ---------------------- 

Onon Ground Safety Requirements Document 

f---- 

15 Oct 2007 

----- 

CxP-72234 

Baseline 

Release 

Integrated Vehicle Ground Vibration Test Task Plan 

CEV Display Fonnat Standards Document 

Constellation Integrated Risk Management Plan 

CEV-T-015 

1---_.- 

CEV-D-002 

-------- 

-_._------ 

10.6.4 

----_._-- 

2 3.(c), 10.6.4 

---------- 

2.3 (c), 106 4 

--.- 

---- 

2.6.9, 6.1.6.2, 

6.2.6.2, 6.4.6.2, 

10.3.6 

2.5 (t), 6.5 2 (g) 

-- 


120f73





REFERENCES 

ID 

Document 

Version/Date 


DRD 

SOW 

FED-STD-H28/20 10 March 1994 

1---- ---c--- 

FIPS 140-2 25 May 2001 

1-- - 

'FTO~Ai=T -FTA-004 

------------ 

12 Apnl2004 

._. 

IEEE 1516 -2000 2000 

---._---1----------- 

IEEE 1516.1-2000 2000 

----_._._--- 

IEEE 1516.2-2000 2000 

- 

IEEE1516.3-2000 2000 

-- 

1132928-103 REVISED 

10/07/2001 

IPC-2221 

IPC-2222 

Screw Thread Standards for Federal Services RevIsion A or Later 

Inspection Section 20 Methods for Acceptability of UN, UNR, UNJ, M, 

and MJ Screw Threads 

Secunty Requirements for Cryptographic Module 

FIPS-197 26 Nov. 2001 Advanced Encryption Standard 

-- 

RevF I-Flight Test Article System ReqUirements Document 

__ 6 Aug. 2008 

1--------- --- 

ICD-GPS-200 Rev 4 

Navstar GPS Space Segment/Navigation User Interfaces 

-- ------------ 

IEEE Standard for Modeling and Simulation (M&S) High Level 

Architecture (HLA) - Framework and Rules 

----- 


Architecture (HLA) Federate Interface Specification 

r-- 

2.6.13 

2.6 3 

-- 

263 

:---------1----------- 

CEV-D-002 10.6.4 

1--------- 

CEV-T-058 263 

._------1-------- 

CEV-T-001 2.4 

------I--------.- 

CEV-T-001 2.4 

- -------- 

CEV-T-001 24 


Architecture (HLA). Object Model Template (OMT) SpeCification 

- +-- 

- ---- 

IEEE Recommended Practice for High Level Architecture (HLA) CEV-T-001 24 

Federation Development and Execution Process (FEDEP) 

Intemational Space Station Program 

REQUIREMENTS FOR INTERNATIONAL PARTNER CARGOES 

TRANSPORTEI) ON RUSSIAN PROGRESS AND SOYUZ 

VEHICLES (ONLY APPLICABLE FOR EFFORTS ASSOCIATED 

SPECIFICALLY WITH THE ISS COMMON COMMUNICATION 

ADAPTER) 

Genenc Standard on Pnnted Board DeSign 

Sectional Design Standard for Rigid Organic Printed Boards 

CEV-S-015, 

CEV-8-017 

CEV-8-015, 

CEV-8-017 

-- 


13 of73





REFERENCES 

ID 

Document 

Version/Date 


DRD 

SOW 

I 

IPC-6011, Performance 

Class 3 

IPC-6012 

------------- ~---_._---- 

JPR8080.5 

Rev A 

15 March 2005 

f--------------- ---_ 

JPR 8080.5, E-14 

Rev A 

JPR 8080.5, E-22 

r----- 

JPR 8080.5, E-24 

~- 

JPR 8080.5, E-6 

.. _-- 

15 March 2005 

1-- 

Rev A 

15 March 2005 

Rev A 

15 March 2005 

Rev A 

15 March 2005 

f--------------1-- 

JPR 8080.5, E-7 

Rev A 

JPR 8080.5, M/S-11 

JSC20431 

15 March 2005 

Rev A 

15 March 2005 

Rev A 

7 Nov. 2002 

JSC20584 June 1999 

Genenc Performance Specification For Pnnted Wlnng Boards 

Qualification and Performance Specification for Rigid Printed Boards 

r---- 

IPC-A-610 

Acceptability of Electronic Assemblies, Performance Class 3 

1-------------1------- 

IPC/EIA J-STD-001 

Performance Class 3 with Space Addendum (Requirements for 

Soldered Electncal and Electronic Assemblies) 

1-- ---------------- 

'------------------------------- 

JSC Design and Procedural Standards (and associated Children 

documents as specified In Attachment J-3, Applicable, GUidance, and 

Informational Documents List) (exclusive of govemment shalls) 

-- 

JSC Design and Procedural Standard, E-14, Electrical Wire Hamess 

Acceptance Testing 

------------------.--- 

JSC Design and Procedural Standards, Section E22, IOnizing 

Radiation Effects 

- --_._------------ 

JSC Design and Procedural Standard, E-24, Electncal Wire and Cable 

Acceptance Test 

JSC Design and Procedural Standard E-6, Corona Suppression 

JSC Design and Procedural Standards, Section E-7, Electncal 

Components - Restnctlons on Use 

JSC Design and Procedural Standards, Section M/S-11, Meteoroid 

and Orbital Debns Protection Levels for Structures 

NASA JSC Neutron Radiography SpeCification 

Spacecraft Maximum Allowable Concentrations for Airbome 

Contaminants 

CEV-S-015, 

CEV-S-017 

CEV-S-015, 

CEV-S-017 

--- 

--- 

--------- 

1-- 

CEV-T-027 

------- 

CEV-T-024 

CEV-T-027 

CEV-T-044 

CEV-T-073, 

CEV-T-074 

2.84 

2.8.4 

-- 

2.6, 2 8.4, 6 1 3, I 

6.2.3, 6.4.3 

._--------- 

284 

2.86 

------ 

------------- 

2.8.4 ! 

---_._--- 

28.4 

2.86 

2.8.2 

2.6.13 

2.612,613.9, 

6.2 3.9, 6 4 6.9 

i 


14 of 73





Document 



ORO 

REFERENCES 

SOW 

NASA-STD-(I)-6016 11 Sep. 2006 

JSC62550 Sept 2006 

------._.__.------- 

JSC62809 

RevC 

23 Jun 2006 

-------_._---------- 

JSC/SKD 26100132 

RevB 

------------------_._--- 

KSC-HB-GP60-3 

Rev- BaSIC 

9 Dec. 2004 

-- ----1--------- 

MIL-DTL-398 

RevD: 

Part1-12 

Dec.1996; 

Part2-17 

Apnl1999 

-- --1--._---- 

MIL-DTL-45444 

Rev C 17 April 

1996; 

Amend. 1: 17 

Apn, 1999 

MIL-HDBK-6870A 28 Aug. 2001 

MIL-L-3055 

RevC 

12 Jan 1993 

Amend. 1-19 

March 1993 

Standard Matenals and Processes RequIrements for Spacecraft 

Strength, DesIgn and Venficatlon Cntena for Glass, CeramIcs and 


---------- 

Constellation Spacecraft Pyrotechnic SpeCIfication 

- --_._---- ---------------------_._----------r----.--------- 

Performance SpeCIfication for NSTS Use of PercussIon Pnmers 

-----------_._-------------._------- 

ASRS Handbook 

._- 

----------_._-----------------_._-----_.- 

RDX (Cyclotnmethylenetnnltramlne) 

H MX (Cyclotetramethylenetetranitramlne) 

------- 

Inspection Program ReqUIrements Nondestructive for AIrcraft and 

MIssile Matenals and Parts 

Type I Lead AzIde 

CEV-T-019, 

CEV-T-020, 

CEV-T-021, 

CEV-T-022, 

CEV-T-023 

----- 

f--------- 

CEV-T-075 

------- 

CEV-O-003 

--------- 

1---- 

CEV-T-023 

----_.- 

2.6.9 

2613,6.1.3.13, 

62.313, 

6.4.313 

f------- 

2.613 

----_._.--- 

2.72 

1-------- 

26.13 

2.613 

2.6.13 


15 of 73





Document 



ORO 

REFERENCES 

SOW 

MIL-L-46225 

RevC 

Aug. 1968 

Amend3-11 

May 1990 

-. --- 

MIL-P-20444C Amend. 1-31 

Aug 2000 

_._----- 

MIL-P-387 

Notice 1 -19 

March 1986 

Notice 2 - 

March 1997 

RevC 

8 Dec. 1976 

Amend. 1-26 

March 1990 

Amend 2-26 

July 1994 

------------ 

MIL-STD-1576 31 July 1984 

-- 

MIL-STD-286 

Notice 1-4 

Sept 1992 

RevC 

8 Aug 1991 

CN 1 -18 Jan 

1994 

MIL-STD-461 E 20 Aug. 1999 

MIL-STD-464A 19 Dec. 2002 

MIL-STD-810 

Lead Azide RD-1333 

2.613 

I-- - +----------1-------- 

Pnmer, Percussion, M42 Parts for and Loading, Assembling and 

Packaging 

---_._------------- 

Pentaerythnte Tetramtrate (PETN) 

---"------- 

Electro ExplOSive Subsystem Safety Requirements and Test Methods 

for Space Systems 

- -- 

MIlitary Standard Propellants, Solid: Sampling Examination and 

Testing; Method 802.1 

Requirements for the Control of Electromagnetic Interference (EM!) 

Charactenstlcs of Subsystems and Equipment 

Electromagnetic Environmental Effects ReqUirements for Systems 

Environmental Test methods and Engineering GUidelines 

--------- 

--------1---------- 

CEV-T-025 

------- 

CEV-T-025 

CEV-T-025 

26.13 

1---------_._._- 

2.6.13 

------- 

2.6.13 

2.85 

2.8.5 

2.6.13 g) 


16 of 73

oo- 

_______ 





Document 



ORO 

REFERENCES 

--c-- 

SOW 

MIL-STD-2073-1 

ML0303-0014 

December 

1999 

RevN 

16June 2004 

r-- -- 

MSFC-STD-3029 

Rev A 

24 Feb. 2005 

1----------------f---------- 

NAS 412 1997 

1-------------1-------- 

NASA TP-2003-21 0788 Apnl2003 

-- ----- 

NASA-STD-4003 8 Sept. 2003 

----- 

NASA-STD-SOOSB 25 Aug. 2006 

r- 

NASA-STD-S009 6 Dec. 2005 

--- -- 

NASA-STD-S017 

Baseline 

Version 13 

June 2006 

-- 

NASA-STD-(I)-S019 12 Sep. 2006 

NASA-STD-8719.9 9 May 2002 

NASA-STD-8739.8 28 July 2004 

Department of Defense Standard Practice for Packaging 

Electncal Wire Harnesses and Coaxial Cables, Installation 

ReqUirements for Electromagnetic Compatibility 

-- --_._- 

GUidelines for the Selection of Metallic Matenals for Stress Corrosion 

1--- .._------_.._--- 

Electncal Bonding for NASA Launch Vehicles, Spacecraft, Payloads, 

and Flight Equipment 

- 

NASA Standard for Ground Support Equipment (and associated 

Applicable Document Children as specified In Attachment J-3, 


------ ------- "------- 

Nondestructive Evaluation ReqUirements for Fracture Control 

Programs 

r--------- 

DeSign and Development ReqUirements for Mechanisms, Sections 1-4 

~- -- 

Fracture Control Requirements for Space Flight Hardware 

NASA Standard for LIfting Devices and EqUipment 

NASA Software Assurance Standard (Chapter 6 and 7) 

CEV-T-025 

-------- 

CEV-T-020 

Cracking Resistance In Sodium Chlonde Environments 

---------- --------- 

Foreign Object Damage/ Foreign Object Debns (FaD) Prevention CEV-T-021 

-------- - ----1-------- 

Meterold/Debns Shielding, 2003, Section 2 for descnblng the MMOD CEV-T-044 

nsk assessment process uSing Bumper code 

--------- 

CEV-T-025 

CEV-D-006, 

CEV-O-008 

--------- 

CEV-T-015, 

CEV-T-023 

------- 

CEV-T-061, 

CEV-T-015 

-- 

CEV-T-023, 

CEV-T-069, 

CEV-T-070 

CEV-S-005 

CEV-S-001, 

CEV-S-018 

2.613 

2.85 , 

28.2 

21.92 

- 

-- 

--------- 

2.8 5 

------- 

2.72.(e), 

6.161,6.2.6.1, 

6.461,1066 

1--------- 

1-------- 

2.6.6, 2.6.9 

3.6,6.5.2 

-- 

I 


17 of73





REFERENCES 

ID 

Document 

Version/Date 


DRD 

SOW 

National Council on 2000 

Radiation Protection and 

Measurements Report 

No. 132 

National Council on 2006 

Radiation Protection and 

Measurements Report 

(TBP) 

No. TBD 

1--. -- ----- 

NPD 8710.38 

National Council on Radiation Protection and Measurements Report 

No. 132. Radiation Protection GUidance for ActivIties in Low-Earth 

Orbit 

Radiation Protection and Science Goals for Lunar MISSions (to be 

published In 2006) 

._-------------- 

Subject NASA Policy for limiting Orbital Debns Generation 

(Revalidated 4/28/04) 

-----_._--- ---1--------1-- ------------- 

NPD 9501.1G 22 May 2000- NASA Contractor Financial Management Reporting System 

22 May 2005 

------ --f--------------------------------- -- --- 

NPD 9501.3A 

3 Aug 2002-3 Earned Value Management 

Aug. 2007 

_._--------- --- 

NPR6000.1G 28 March 2005 ReqUirements for Packaging, Handling, and Transportation of 

-28 March Aeronautical and Space Systems, EqUipment, and ASSOCiated 

2008 Components 

---1----- -- 

NPR 7150.2 27 Sept. 2004 NASA Software Engineering ReqUirements (all shall statements/the 

-27 Sept compliance matnx only, excluding the software safety requirement) 

2007 

NPR8580.1 26 Nov. 2001 - Implementing the National Environmental Policy Act and Executive 

26 Nov 2006 Order 12114 

- 

CEV-T-045 

CEV-T-045 

---------. 

CEV-B-001 

-------- 

CEV-B-003 

1--------- 

CEV-T-011 

-_._---- 

CEV-T-005, 

CEV-T-006, 

CEV-T-029, 

CEV-T-048, 

CEV-T-049, 

CEV-T-050, 

CEV-T-051, 

CEV-T-052, 

CEV-T-053, 

CEV-T-054, 

CEV-T-055, 

CEV-T-056, 

CEV-T-057 

2.8.3 

2 8.3 

--- 

---------- 

--------- 

---_._.------ 

-------- 

1 5- Class 

E,F,G only, 

6 5.2- Chapter 6 

& 7 only, 6 5.3 

ClassC&D 

10.1 

I 


18 of 73





Document 


NPR8715.5 

NPR9501.2D 

NPR9501.3 24 Nov. 2002 - 

24 Nov. 2007 

NSS-1704.14 

f-----.------ _. 

NSTS08307 

Rev A 

6 July 1998 

NTIAManual 

-------------- 

May2003w/ 

May 2004 

RevIsions 

S0300-BT-PRO-010 Nov. 1994 

SSP-50005 


Range Safety Program 

NASA Contractor Financial Management Reporting 

Earned Value Management Implementation Plan on NASA Contracts 

._----- 

GUidelines and Assessment Procedures for Limiting Orbital Debns 

-- 

Space Shuttle Cntena for Preloaded Bolts 

c--- ------------------ 

National TelecommUnications and Information Administration (NTIA) 

Manual of Regulations & Procedures for Federal RadiO Frequency 

Management (May 2003 Edition, May 2005 Revisions) Chapter 10 

OSHA Standards 29 CFR 

Supplementary Standards 1960 18 

----------- 

Range Commanders June 2002 Common Risk Cntena for National Test Ranges 

Council - Range Safety 

Group - Standard 321-02 

-- 

f--- -------------------c---------- 

Government-Industry Data Exchange Program (GIDEP) Operations 

Manual 

International Space Station Flight Crew Integration Standard 

(ONLY APPLICABLE FOR EFFORTS ASSOCIATED SPECIFICALLY 

WITH THE ISS COMMON COMMUNICATION ADAPTER) 

ORO 

REFERENCES 

SOW 

CEV-O-007 2.7.4,33 

CEV-B-001, 

CEV-M-002 

CEV-B-003 

-------_._--- 

CEV-S-007 

------_.- -- 

2.6 9 

------_._-_. ----- 

CEV-T-026 

--------- 

Ce'l S QQa, 

CEV-T-045 

CEV-0-007 

-.- 

CEV-S-001, 

CEV-S-012 

263,285 

-- 

28.3 

--------- 

2.74, 33 

_._------- 

WS5003F 

VB_SSHM July 2007 

Ares IVGVT & Orion 7/17108 

BEA 

-- -- 

Matenal Specification for HNS ExplOSive 

NeXIOM Data Schema 

Ares IVGVT & Orion Bilateral Exchange Agreement for IVGVT 

Support 

- 

J-2 DPD 

2.613 


19 of 73



1.1 APPLICABLE DOCUMENT CHILDREN 



For the following applicable or gUidance documents, their embedded applicable children 

documents Identified in the Approved Children Table are also applicable or to be used as 

guidance depending on the parent document's category or as otherwise indicated: 

• NASA-STD-5005B, NASA Standard for Ground Support Equipment 

• NASA-STD-(l)-5019, Fracture Control Requirements for Space Flight Hardware 

• MSFC-SPEC-164B, Specification for Cleanliness of Components for Use In Oxygen, Fuel 

and Pneumatic Systems 

• CxP-70022, Constellation Program C31 Interoperabllity Standards Books Volumes 1 and 4 

o 

Attachment J-3a provides the phased applicability matrix for CxP-70022 

applicable children documents .. 

• CxP-70023, Constellation Program Design Specification for Natural Environments (DSNE) 

[The DSNE Invokes portions of CP-DOC-00004, Constellation Program Natural 

EnVironment Definition for DeSign (NEDD) where other children documents, models and 

datasets are then subsequently Invoked These NEDD children documents, models and 

datasets are listed as applicable children to the DSNE.] 

• CxP-70059, Constellation Program Integrated Safety, Reliability and Quality Assurance 

(SR&QA) Requirements 

• JPR 8080.5, JSC DeSign and Procedural Standards 

• CxP-70024, Constellation Human Systems Integration Requirements (HSIR) 

• CxP-72000, Systems Requirements for the Crew Exploration Vehicle Element 

• CxP-72008, Crew Exploration Vehicle Project Plan 

• CxP-72234, Integrated Vehicle Ground Vibration Test Task Plan 

• CxP-70026, Crew Exploration Vehicle (CEV) to Crew Launch Vehicle (CLV) IRD 

• CxP-70076, Constellation Program Modeling and Simulation Management ReqUirements - 

Level II 

• CxP-70135 - Structural DeSign and Verification Requirements 

• FTO-AFT-FTA-004, Flight Test Article System Requirements Document 

• Note - Typically children section does not duplicate Section 1 0 Applicable Documents. 


Page 20 of73





ID 

Document 

Version/Date 

APPROVED CHILDREN TABLE 

DOCUMENT TITLE 

DRD 

REFERENCES 

SOW 

, 

PARENT APPLICABLE 

DOCUMENT 

f--- 

f--- - ----------1------ - 

'-ADM-"f--------- --_._----- - 

1--::=:-,------------ 

A1SC 316-89 

f----------- 

1989 

f-=----------- - ------_._._-- 

A1SC 325-01 2001 

'Arsl-SG:&n--- --------- 

'AMS H-6875 

AMS2770 

f-c--·--------- 

AMS2771 

"AMs2772--- 

AMS-H-81200 

ARP 1247 

AS 1097 

AS 8090 

ASMEA13.1 

ASME B30.1 

ASMEB31.3 

1-:=--------.------------------------ 

Cold-Formed Steel Design Manual 

1-----_._-- 

--------------- ----------- ----------- 

f-Heat Treatment of Steel Raw Matenals 

----J-----.---- - 

-- -------_._- ._-------- 

-HeatTreatment"ofWrought Aluminum Alloy Parts 

1-------- 

----_._--- --- 

Heat Treatment of Alummum Alloy Casting 

--_.- 

. -.-t---------_.-._------ 

Heat Treatment of Wrought Aluminum Alloy Raw Matenals 

- - ------------ 

Heat Treatment ofTltamum and Tltamum Alloys 

-+-_. 

PARENT APPLICABLE DOCUMENT: NASA-STD-5005B, NASA 

Standard for Ground Support Equipment 

CEV-D-006, 

CEV-O-008 

NASA-STD-50058 Approved Children 

------------_. ------------1---._._----- 

- ----------------------------- -- ------_ .. _._- 

Aluminum Design Manual 

- -------_._._---t---------- 

Manual of Steel Construction - Vol. 1 (Reference 316-1989) 

AllQwa~e.§Jl!lss De~.!~ __________________ 

LFRD Manual of Steel Construction - Third Edition 

General Requirements for Aerospace Ground Support Equipment, 

Motonzed and Nonmotonzed 

Seal Rmg 37-Degree Flared Tube Fitting End 

Mobility, Towed Aerospace Ground EqUipment, General 

Requirements for 

Scheme for the Identlficabon of Plpmg Systems 

Jacks - Safety Standard for Cableways, Cranes, Demcks, HOISts, 

Hooks, Jacks, and Slings 

Process Pipmg 

-- 

--1-------- 

272.(e), 

6 1 6 1, 6.2 6.1, 

6461,10.66 

--------- 

-_._-------- 

---------- 

-- 

-- 

----_._------- 

----- 


Page 21 of73





10 

Document 

Version/Date 



REFERENCES 

ASME Vessel Code, 

ASME Baller and Pressure Vessel Code, Section IX' Welding and 

I Section IX Procedures Brazing Qualifications /----___-+ 


ASME Bader and Pressure Vessel Code, Section VIII Pressure 

Section VIII, Divisions 1, Vessels DIvISions 1, 2, and 3 

I 2, and 3 ___ _ _________ +_ ________, 

ASTM A269 

Standard Specification for Seamless and Welded Austemtlc Stainless 

~ _ Steel Tubing for General Service ----t---____ 

-------- 

ASTM A325 

Standard Specification for Structural Bolts, Steel, Heat Treated, 

h-=---_______ ._ _________ 120/105 kSI Mlmmum Tensile Strength __________ 

_ ._._-----1-------- 

ASTM A36 

ASTMA490 

Standard Specification for Carbon Structural Steel 

------ --------------------+----------1-------- 

Standard Specification for Structural Bolts, Alloy Steel, Heat Treated, 

~--- ------~ ~~n~~r~~~~~~::~~I~~;~~~~~eld-Strength-, -Quen-c-h-e-d-a-nd-----+-----------'---------· 

ASTM A514/A514M 

I . ________ .Iempered Allay Steel Plate, SUitable for Weld.!!!.9. __________ +- __ ___ 1 _.____ 

ASTM A517/A517M 

Standard Specification for Pressure Vessel Plates, Alloy Steel, Hlgh- 

~--------l__-------.. 

ASTM MANUAL 36 

Strength. Quenched and Tempered - --f----------1 I 

Safe Use of Oxygen and Oxygen Systems: GUidelines for Oxygen 

System Design, Matenals Selection, Operations, Storage, and 

::: ~~::/D1.2M__ T-----~---~---- :~:~_:rta_ :_tl_:n_::_:~_:_~::;_=_:~u::n~:e~ -------~-~-=----~-~-:~---f----- t--=---~~--I- 

AWS 01.6 

Structural Welding Code - Stainless Steel 

-- ----- ---- ------------- ------ --I 

AWS D1/D1.1M 

Steel - Structural Welding Code - Standard for 

____-j._____ I 

-+____ 

eGA C-7 -+----- 

EIA310 

FED-STD-595 

IEEElASTM 5110 

GUide to the Preparation of Precautionary Labeling and Marking of 

Compressed Gas Containers 

Cabinets, Racks, Panels, and Associated Equipment 

Colors Used In Government Procurement 

American National Standard for Use of the Intemational System of 

Units (SI). The Modem Metric System 

ORO 

SOW 


Page 22 of73





ISO 2631-1 

- 

1503382 

ISO 15389 

KSC-C-123 

KSC-E-165 

ID 

KSC-SPEC-E-0029 

-- 

Document 

Version/Date 

RevH 

r-~§ Sept. 1995 

RevD 

22 Feb 1995 

21 Apn11972 

KSC-SPEC-E-0031 --- Rev A 

_,1 0 Aug 1995 

KSC-SPEC-Z-0008 RevC 

13 June 1995 

KSC-SPEC-Z-0009 -- Rev A 

15 Jan. 1991 

~-STD-E-0004 

f--o-=-.= - 

KSC-STD-Z-0005 



MIL-C-22992 

MIL-DTL-16878 

Reve 14 Oct 

1996 

RevEAmend 

6 

8 March 2000 

RevG 

11 Aug. 2000, 

Suppl.1 - 

11 Aug. 2000; 

Amend. 1- 

2 July 2002 



International Standards Orgamzatlon (ISO) Standard 2631-11997 (E) 

"Measurement of the Reverberation Time of Rooms WIth Reference to 

Other Acoustical Parameters" 

Space systems - Flight-to-ground umbilicals 

Surface Cleanliness of FlUid Systems, Specification for 

Electrical Ground Support EqUipment, Fabncatlon, Specification for 

--;:-- - 

Compound, Potting and Molding, Elastomenc, 

,,--- ---------- 

SpeCification fo! 

Cables, Electncal, General SpeCification for 

---_._---- ------------------ 

-------- 

Fabncation and Installation of Flared Tube Assemblies and 

Installation of Fittings and FI~ Assemblies, SpeCification for 

Lubncatlon, Thread, CorroSion-ReSistant Steel and Aluminum Alloy 

-- . - -- 

Tube Fittings, Specification for 

Pneumatic and Hydraulic Mechamcal Components, Electncal DeSign, 

Standard for (IT AR Controlled) 

_ 

Pneumatic Ground-Support EqUipment, DeSign of, Standard for (lTAR 

f-----.. 

-- 

----_._-- 

Controlled) 

Hypergolic Propellants Ground Support EqUipment, DeSign of, 

1------------------- 

Standard for (IT AR Controlled) 

Design of Ground Life Support Systems and EqUipment, Standard for 

Connectors, Plugs and Receptacles, Electncal, Waterproof, QUick 

Disconnect, Heavy Duty Type, General SpeCification for 

Wire, Electncal, Insulated, General SpeCification for 

DRD 

REFERENCES 

SOW 

----------- 

----------- 

-- 


Page 23 of73





MIL-DTL-38999 

MIL-DTL-5015 

MIL-HDBK-149 

MIL-HDBK-17/1 

MIL-HDBK-454 

Document 


Rev K 

BasIc - 17 Dec 

1999; 

Amend 1-5 

May 2001, 

Amend. 2-9 

Apn12002; 

Amend. 3-22 

Aug.2003; 

Suppl. 1 - 

12 JulY 2002 

RevH 

Basic 

document & 

Supplement 1 

18 May 2000 __ 

RevB 

~1984 

RevF 

17 June 2002 __ 

Not In Library 



Connectors, Electncal, Circular, Miniature, High Density, QUick 

Disconnect (Bayonet, Threaded, and Breech Coupling), Environment 

Resistant, Removable Crimp and Hermetic Solder Contacts, General 

SpeCification for 

Connectors, Electncal, Circular Threaded, AN Type, General 

Specification for 

-Rubber 

Composite Matenals Handbook Volume 1: Polymer Matnx 

-:;:- 

Components GUidelines for Charactenzatlon of Structural Matenals 

- 

General GUidelines for Electronic Equipment 

MIL·HDBK-5961 

Rev A 

List of Standard Semiconductor Devices 

5 Nov 1999 __ 

MIL·HDBK·5H 1 Dec. 1998 Metallic Materials and Elements for Aerospace Vehicle Structures 

--I--- 

ORO 

----_._-- 

REFERENCES 

SOW 

--_..._------ 

---- 

--_..-._--- 

MIL·HDBK·6870A 28 Aug. 2001 

MIL·HDBK·700 

MIL·M-8609 

Rev A 

17 March 1975 

RevB 

26 July 1965; 

Notice 1 B -12 

Dec. 1987; 

Notice 2 B- 

28 Aug. 1996 

Inspection Program ReqUirements Nondestructive for Aircraft and 

Missile Matenals and Parts 

Plastics 

Motors, Direct-Current, 28 Volt System, Aircraft (Inactive for new 

design) 

-- 

I-- 

I 


Page 24 of 73





Document 


10 Version/Date DOCUMENT TITLE 

MIL-PRF-39012 RevE Connectors, Coaxial, Radio Frequency, General Specification for 

27 Aonl2005 

MIL-STD-1472 RevF Department of Defense Design Cntena Standard, Human Englneenng 

23Aug 1999 

MIL-STD-1576 13 July 1984 Electroexploslve Subsystem Safety Requirements and Test Methods 

Notice 1 -4 for Space Systems 

~IL-STD-171 

Se[!t. 1992 

RevE 

FInishing of Metal and Wood Surfaces 

23 June1989 

CN 1-19 

Nov 2001 

MIL-STD-461E 20 Aug. 1999 Requirements for the Control of Electromagnetic Interference (EMI) 

Charactenstlcs of Subsystems and Equipment 

----- --=--------- -- 

MIL-STD-889 RevB Dissimilar Metals 

7 July 1976; 

Notice 1 - 21 

Nov. 1979; 

Notice 2- 

4 March 1988, 

Notice 3 - 17 

--- 

May 1993 ---- 

MIL-W-22759 RevE Wire, Electncal, Fluoropolymer-Insulated Copper or Copper Alloy 

31 Dec. 1990 

c---- 

ORO 

REFERENCES 

------------------------------------- - ------------ -------------1---------- 

------- 

-- 

(------- 

-- 

SOW 

- - - --------- 


Page2S of73





Document 




ORO 

REFERENCES 

SOW 

I 

MIL-W-5086 

MSFC-STD-156 

RevC 

(5086C) 

2 Dec 1974, 

RevCAmend 

1 - 1 Dec 

1974 

(Note In 

Parent 

document title 

matches only 

basic 5086 

document 

rev/verslon C 

and Its Amend 

A 1 -Copper or 

Copper Alloy 

Wire 

specification. 

Appl and 

Parent 

document 

folders contain 

additional 

related 

documents- 

5086/1 B, 2C , 

3B, 4B, 5C, 

6C,7Bwhlch 

are for 

different 

composItion 

Wires.) 

2 Apnl1962 

Wire, Electnc, PolYVinyl Chloride Insulated, Copper or Copper Alloy 

Riveting, Fabrication and Inspection, Standard for 

I 

i 

I 

I 

MSFC-SPEC-164B 

RevB 

(For GUidance only) Nov. 1994 

Specification for Cleanliness of Components for Use In Oxygen, Fuel 

and Pneumatic Systems, inclUSive of Specifications In Section 2 1 1 

- 


Page 26 of73




Modification 6S 

Document 


MSFC-SPEC-250A (1977) 1 Oct 1997 

MSFC-STD-486 

MSFC-STD-3029 

NASA-HDBK-1001 

RevB 

Nov. 1992 

Rev A 

24 Feb.2005 

'"NASA-SPEC-5004 

--f-_------- 

Rev A 

-, 25 Aug 2003 

NASA-STD-5008 

Rev A 

21 Jan 2004 


9 Feb. 199B 

NASA-STD-8719.9---- f-c-- 

9 May 2002 

NBS HDBK-105-1 1990 

i-c,-------------~evls~(L--- 

NEMA-ICS2 

NEMA-MG1 

NFPA496 

NFPA50 

NFPA50B 

NFPA 70 

NFPA 780 

No number/ASHRAE 

Handbooks 

No number/Brazing 

Manual 

-----r- 

-- 



Protective Finishes for Space Vehicle Structures and Associated 

Flight EgUiement, General Seeclficatlon For 

Standard, Threaded Fasteners, Torque Limits for 

ORO 

REFERENCES 

SOW 

r-------- 

GUidelines for the Selection of Metallic Matenals for Stress Corrosion 

Cracking Resistance In Sodium Chloride Environments 

Terrestnal Environment (Climatic) Critena Handbook for Use In 

.- 

Aerospace Vehicle Develoement 

__________ 

-------f---------- 

Welding of Aerospace Ground Support Equipment and Related 

f-~onconvential Facilities 

__ ------------------- 

Protective Coating of Carbon Steel, Stainless Steel and Aluminum on 

Launch Structures, FacIlities and Ground Su~~ort EgUl~ment ___ , 

Flammability, Odor, Offgasslng & Compatibility Requirements & Test 

----- 

Procedures for Matenals In Environments That SUQ[lort Combustion 

Standard for Lifting Devices and Equipment 

f-------- ------ 

SpeCifications and Tolerances for Reference Standards a'nd Field 

--1---------- --- I-- 

Standard Weights and Measures 

Industnal Control and Systems: Controllers, Contractors, and 

-----t-- 

-- 

Overload Relays, Rated Not More Than 2000 Volts AC or 750 Volts 

OC 

Information GUide for General Purpose Industnal AC Small and 

t--------- ------------ 

Medium SgUirrel-Cage Induction Motor Standards 

Purged and Pressunzed Enclosures for Electncal EqUipment 

Bulk Oxygen Systems at Consumer Sites 

Liquified Hydrogen Systems at Consumer Sites 

National Electncal Code 

Installation of Lightning Protection Systems 

ASHRAE Handbooks 

Brazing Manual 

--- 

-- 

-- 


Page 27 of73





ID 

No number/Handbook 

Document 

Version/Date 

Handbook for Spnng DeSign 


REFERENCES 

DOCUMENT TITLE DRD SOW 

I for S~ring Design I --+------1-------- 

No numberlSoldering 

Soldenng Manual 

Manual 

NPD 8010.2 14 May 2002 - Use of Metnc System of Measurement In NASA Programs 

INPG =+:14 May 2009 

k~ 8715.3 NASA Safety Manual 

NSS 1740.16 Cancelled Safety Standard for 7 H;-y-;dr-o-g-en-an-d Hydrogen Systems GUidelines for ~------ 

Hydrogen System DeSign, Matenals Selectron, Operations, Storage 

and Transportation 

~~:~~~~o~y ANSI/AI~ I 2004 _______ 1 :~gl~~~~o~~n~y~~:~~ G-095-2004 GUide to Safety of Hydrogen ____________ , _______ _ 

T9074-BD-G1B-010/300---t9Aug 2002 Base Matenals For Cntlcal Applications: ReqUirements For Low Alloy t 

Steel Plate, Forgings, Castings, Shapes, Bars, And Heads Of HY- 

I---- 

_____ +80/100/130 And HSLA-80/100 ------------------_-+ ________ 1-______ _ 

I--PARENT GUIDANCE r-------1 PARENT GUIDANCE DOCUMENT: NASA-STD~O=5019, Fr;ct~-;-t -~--------, 

DOCUMENT 

Control Requirements for Space Flight Hardware 

t=- I NASA-STD-(IJ-5019 Approved Children 

CEV-T-023, 

CEV-T-069, 

CEV-T-070 

--1 _ 

---j------,-------, 

JSC23642 

(for gUidance only) 

MSFC-STD-2594 

(for Quidance only) 

22 Oct. 2001 

Jun. 1997 

JSC Fastener Integrity Testing Program 

MSFC Fastener Management and Control Pracoces 

PARENT GUIDANCE 

DOCUMENT 

PARENT GUIDANCE DOCUMENT: MSFC-SPEC-164B, 

Specification for Cleanliness of Components for Use in Oxygen, 

Fuel and Pneumatic Systems 

I CEV-T-073 

2.6.12 

MSFC-SPEC-164B Approved Children 


PageZS of73

NNJ06TA2SC 




Document 




ORO 

REFERENCES 

SOW 

BB-N-411 

Replaced by A-A-59503 

Cancelled 

KSC/MTB-402 Sept 1988 

MIL-P-27401D 

RevD 

30 Oct 1995 

MIL-T-27602 Notice 1 

20 May 2003 

(Cancellation 

Notice) 

Replaced by MIL-C- MIL-C- 

813020 81302D 

(Rev D) - 16 

Apnl1985 

Notice 1 28 

Oct. 1991 

'MfL-T-81533 

-- 'R"evA 

-- 

26 Sept. 1967 

Notice 1 

29 Oct. 1991 

Type 1, Class 1, Nitrogen 

Replaced by: Commercial Item Descn[!tlon Nitrogen, Technical 

Physical and Chemical Test Results of Plastic Films 

Performance Specification Propellant Pressunzlng Agent, Nitrogen: 

Type 1, Grade A - Nltro~ 

Tnchloroehtylene 

Replaced by. MIlitary Specification Cleaning Compound, Solvent, 

Tnchlorotnfluoroethane: Type 1 Tnchlorotnfluoroethane (CFC 113) 

---I-- 

-- 

-------------------- 

----------- - --------- 

Military Specification 1,1,1-Tnchloroethane (Methyl Chloroform) 

Inhibited, Vapor Degreaslng 

NHB-8060.1 B Sept. 1981 

NHB-8060.1 C 

Apnl1991 

PPP-T-60 

Cancellation 

Notice 6 Dec. 

Replaced by ASTM STD 1995 

Spec 0 5486 

Flammability, Odor, And Offgasslng Requirements And Test 

Procedures For Matenals In Environments That SU[![!ort Combustion 

Flammability, Odor, Offgassing and Compatibility Requirements and 

Test Procedures for Matenals in Environments that Support 

Combustion 

Tape, Packaging, Waterproof 

Replaced by. Standard Specification for Pressure-Sensitive Tape for 

Packaging, Box Closure and Sealing 

I 

, 


Page 29 of73





ID 


DOCUMENT 

f------------.--- 

RFC-4106 

RFC-4868 

--- 

CUrEE 802.3-2005 

RFC-1918 

r-=,---------- 

RFC-3171 

RFC-2131 

RFC-3927 

RFC-1812 

---- 

Document 

Version/Date 

+------ 

---- 

--- -- 

- 

---_. 



PARENT APPLICABLE DOCUMENT: CXP-70022, Constellation 

Program Command, Control, Communication, and Information 

(C31) Interoperability Standards Books, Volume 1 

CxP-70022 V1 Approved Children 

The Use of Gallos/Counter Mode (GCM) In Ipsec Encapsulating 

DRD 

CEV-T-026, 

CEV-T-047, 

CEV-T-058 

--_._------ 

REFERENCES 

SOW 

2.61,26.3 

Secun!}! PaylQad (E~ _ __----------------- 

USing HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 with 

losee 

------- ---------------- 

IEEE Standard for Information Technology-Sectlon 3, 

Telecommunications and information exchange between systems-- 

Local and metropolitan area networks--Specific requirements. Part 

3 Camer Sense Multiple Access with ColliSion Detection (CSMAlCD) 

access method an~!J~!2Y.slcal la:ler sQeclficatlons 

--- 

Address Allocation for Pnvate Intemets (Internet Englneenng Task 

Force (IETF, http://www letf.org» 

.~ectlon 3 - Pnvate Address~ace) __----------- - -------- 

lANA GUidelines for Ipv4 Multicast Address ASSignments (Internet 

Englneenng Task Force (lETF, http://wwwletforg)) 

(Section 2, 3, 4, 5, 6, 7, 8, 9) 

+-- 

DynamiC Host Configuration Protocol (Internet Englneenng Task 

Force (lETF, http·//www.letforgl) 

I 

(Section 3 - The Client-Server Protocol 

Section 4 ~eclficatlon of the DHCP client-server Qrotocol) 

- 

Dynamic Configuration of Ipv4 Link-Local Addresses (Internet 

Englneenng Task Force (IETF, http://www.letf org» 

(Section 2 - Address Selection, Defense and Delivery 

Section 3 - ConSiderations for Multiple Interfaces) 

ReqUirements for IP Version 4 Routers (Internet Engineenng Task 

I 

Force (IETF, http·//www.ietf.org» 

(Section 3 - LINK LAYER 

Section 4 - INTERNET LAYER - PROTOCOLS 

Section 5 - NTERNET LAYER - FORWARDING 

Section 10 - OPERATIONS AND MAINTENANCE) 

_. 

_.- 


Page 30 of 73





Document 


CCSDS 714.0-B-1 May 1999 

CCSDS 727.0-B-3 June 2005 

'5TD-OOOS-;-RFC-791--- -- 

----- ------ 

RFC:~------ 

RFC-3246 

RFC-2474 ------ 



Space Communlcabons Protocol Speclficabon (SCPS}-Transport 

Protocol (TP) and CCSDS 714.0-B-1 Cor 1, Technical 

COrrigendum 1 to CCSDS 714.0-B-1 (Blue Book, Issue 11. 

CCSDS File Dehvery Protocol (CFDP) - Recommended Standard 

(httr;l:IIr;lublic.ccsds.org/r;lubhcatlons/Sr;lacelntServ aSr;lx) Protocol 

(Consultative Committee for S[lace Data Systems 

Internet Protocol (IP) Specification, Vel'Slon 4 {Internet Engineering 

Task Force (IETF, httr;l:lIwww iett.org» 

(Section 1 - INTRODUCTION 

Section 2 - OVERVIEW 

Section 3 - SPECIFICATION 

~-endlx B - Data Transmission Order) 

Internet Control Message Protocol (Internet Englneenng Task Force 

(IETF, httr;l IIwwwlettorg» 

(Message Formats 

Destination Unreachable Message 

Time Exceeded Message 

Parameter Problem Message 

Source Quench Message 

Redirect Message 

Echo or Echo Reply Message 

Timestamp or Timestamp Reply Message 

Information Reguest or Information Re[lly Messag& -- -- 

An Expedited Forwarding PHB (Per-Hop BehaVior) (Internet 

Englneenng Task Force (lETF, httr;l:/Iwww lett org» 

(Section 2 - Definlbon of EF PHB) 

Definition ofthe Differentiated Services Field (DS Field) In the Ipv4 

and Ipv6 Headers (Internet Engineering Task Force (lETF, 

httr;l·lIwww.lett.org» 

(Section 2 - Terminology Used In This Document 

Section 3 - Differenbated SelVlces Field Definition 

Section 4 - Histoncal Codepolnt Definitions and PHB ReqUirements 

Section 5 - Per-Hop BehaVior Standardization GUidelines) 

REFERENCES 

ORO 

SOW 

- - 

----------- 

-- 


Page 31 of73





ID 

Document 

Version/Date 



DRD 

REFERENCES 

RFC-2205 Version 1 Resource ReSerVation Protocol (RSVP) - Version 1 Functional 

Specification Specification (Internet Engineering Task Force (IETF, 

http·//www.lett.oro» 

(Section 2 - RSVP Protocol Mechamsms 

IETF STD-0013 

Section 3 - RSVP Functional Seeclficatlon) 

Domain Name System (Internet Engineenng Task Force (lETF, 

----------------- 

httB·lIwww.lett.org» (RFC-1034 and RFC-1035 onlYL 

1S071EC 15444-3 Part 3 

Motion JPEG 2000 (Part 3) (Intemabonal Standards Orgamzatlon, 

-- -- 

l;CSDS 732.0.13-2--- Section 3--- 

J'!~O, httB://W\'\iW.iso cl"!)l __ 

AOS Space Data Link Protocol (Consultative Committee for Space 

-- ------ -------- 

-- ~ta 

--------- 

Systems, httB IIwww.ccsds.()r.9l- Sec!!Q!l..1 ______ 

'cCSDS 131.0-B-1 

TM Synchronizabon and Channel Coding (Consultative Committee for 

f--------- 

Space Data Systems, http://wwwccsds.org)(Sectlons 6 and 7. 

(Section 6 covers ASM and & covers randomizabon/derandomlzabon» 

__ 

CCSDS f31.1-6~1---- f--- 

--- -- -------f------.-- 

Low Density Panty Check Codes for Use In Near Earth and Deep 

Space Applications (Consultative Committee for Space Data Systems 

http://www ccsds.ora) 

(Section 1 - An overview of LDPC. 

CCSDS 702.1~R--1---- f--------- Section 3 - The selected Rate V. AR4JA code ) 

_______ 

t--------------- 

IP over CCSDS Space Links (Consultative Committee for Space Data 

Systems, http/Iwww.ccsdsoro) 

(Section 2 -IP datagrams over CCSDS links 

Section 3 2 - AOS data link protocol Implementations 

Section 4 7.2 - AOS Virtual Channel Access (VCA) octet-aligned 

-- I-streams) 

"RFc-4361 

Node-specific Client Idenbfiers for Dynamic Host Configuration 

1-- 

Protocol Version Four (DHCPv4) (IETF, http://www lett.ora) 

(Section 6 - Imelementabon) 

RFC2211 

Specification of the Controlled-Load Network Element Service 

(Internet Englneenng Task Force (IETF, http://wwwlett.orgl) 

(Section 2 - End-to-End 

Section 4 - Network Element Data Handling ReqUirements 

Section 5 - Invocation Infonnatlon 

Section 7 - Policing 

Section 8 - Ordenng and Merging) 

SOW 

-- 


Page 32 of73





RFC-2213 

RFC2460 

RFC-4443 

RFC-2644 

Document 


. --------_. 

---- 

STD-0003, RFC-11-22--- ------ 

RFC-4271 



Integrated Services Management Information Base uSing SMIv2 

(Internet Englneenng Task Force (IETF, http /IYNIW.letf org» 

(Section 3 - Definitions} 

Internet Protocol, Version 6 (lpv6) Specification (Internet Engineering 

Task Force (IETF, http/lYNlWletf.oro»)(Section 2 - Terminology 

Section 3 -lpv6 Header Format 

Section 4 - Ipv6 Extension Headers 

Section 5 - Packet Size Issues 

Section 6 - Flow Labels 

Section 7 - Traffic Classes 

Section 8 - Upper-Layer Protocol Issu~L __ 

Internet Control Message Protocol (ICMPv6) for the Internet Protocol 

Version 6 (lpv6) Specification (Internet Englneenng Task Force (IETF, 

http /IYNIW letf.org» 

(Section 2 -ICMPv6 (ICMP for Ipv6) 

Section 3 -ICMPv6 Error Messages 

Section 4 -ICMPv6 Informational Messages) 

Changing the Default for Directed Broadcasts In Routers (IETF, 

http://YNIW.letf org) 

(Section 3 - Recommendation} 

__ 

ReqUirements for Internet Hosts - Communications Layers (Internet 

Engineenng Task Force (IETF, http./IYNIWietf.oro}) 

(Section 2 - LINK LAYER 

Section 3-INTERNET LAYER PROTOCOLS 

Section 4.1 - USER DATAGRAM PROTOCOL - UD~ _______ 

A Border Gateway Protocol 4 (BGP-4) (Internet Englneenng Task 

Force (IETF, http://YNIW.letf.oro)) 

(Section 4 - Message Formats 

Section 5 - Path Attnbutes 

Section 6 - BGP Error Handling 

Section 7 - BGP Version Negotiation 

Section 8 - BGP Finite State Machine (FSM) 

Section 9 - UPDATE Message Handling 

Section 10 - BGP Timers) 

ORO 

REFERENCES 

._---_._._-------- 

----------- 

~- 

SOW 

-- 

1---------- 


Page 33 of73


Crew Exploranon Vehicle - (CEV) 



STD-0056, RFC-2453 

5TD~0054, RFC-2328 

RFC-2427 

Document 




RIP Version 2 (Internet Englneenng Task Force (IETF, 

http IIwww ietf org» 

(SectIon 3 - BasIc Protocol 

__ ~~tion 4 - Protocol Extensions) _ 

Open Shortest Path First (OSPF) Version 2 {Internet Englneenng 

Task Force (IETF, http://wwwletf.org)) 

(SectIon 2 - The Link-state Database: organizatIon and calculatIons 

SectIon 3 - Splitting the AS Into Areas 

Section 4 - Functional Summary 

Section 5 - Protocol data structures 

Section 6 - The Area Data Structure 

SectIon 7 - Bnnglng Up AdjacenCies 

Section 8 - Protocol Packet ProcesSing 

Section 9 - The Interface Data Structure 

SectIon 10 - The Neighbor Data Structure 

Section 11 - The RoutIng Table Structure 

Section 12 - Link State AdvertIsements (LSAs) 

Section 13 - The Flooding Procedure 

Section 14 - Aging The Link State Database 

Section 15 - Virtual Links 

SectIon 16 - There are three OSPF routers (RTA, RTB and RTC) 

Appendix A - OSPF data formats 

Appendix B - Architectural Constants 

Appendix C - Configurable Constants 

Appendix E - An algonthm for assigning Link State IDs 

Appendix F - MultIple Interfaces to the same network/subn~ 

Multlprotocol Interconnect over Frame Relay (lETF, 

http://www.letf.org) 

(SectIon 3 - Frame Format 

SectIon 4 - Interconnect Issues 

SectIon 5 - Data Link Layer Parameter NegotiatIon 

SectIon 6 - Address ResolutIon for PVCs 

SectIon 7 -IP over Frame Relay) 

ORO 

REFERENCES 

SOW 

I 

I 


Page340f73





RFC-2784 

-RFC-3140 

RFC-3626--- 

RFC-2080 

RFC-2740 

RFC-2473 

RFC-2508 

RFC-2734 

RFC-4292 

RFC-4293 

Document 


------ 

-+----.---- 

-------------- 

---- 



Genenc Routing Encapsulation (GRE) (Internet Englneenng Task 

Force (IETF, http://www.lett.ora)) 

(Section 2 - Structure of a GRE Encapsulated Packet 

Section 3 - Ipv4 as a Payload 

Section 4 - l[1v4 as a Delivel)' Protocol) 

Per Hop Behavior Identification Codes (Internet Engineenng Task 

Force (lETF, http //www.lett orgl) 

(Section 2 - Encoding 

Section 3 - Signaling the Class Selector CodepOints . 

Optimized Link State Routing Protocol (OLSR) (Internet Englneenng 

Task Force (LETF, httR/Iwww.lett.org» 

RIPng for Ipv6 (lETF, http//wwwlelf.org) 

(Section 2 - Protocol Specification 

Section 3 - Control Functlon~ 

OSPF for Ipv6 (IETF, http://wwwlett.org) 

(Section 2 - Differences from OSPF for Ipv4) 

Genenc Packet Tunneling in Ipv6 SpeCification {IETF, 

http //www.lett.Q!:9L 

Compressing IP/UDP/RTP Headers for Low-Speed Senal Links 

{Internet Englneenng Task Force (IETF, http/lwwwlettorg» 

(Section 3 - The Compression Algonthm 

Section 5 - Negotiating Compression} 

Ipv4 over IEEE 1394 {Internet Englneenng Task Force (IETF, 

http·IIwww.lett.org» 

(Section 4- LINK ENCAPSULATION AND FRAGMENTATION 

Section 5 - SERIAL BUS ADDRESS RESOLUTION PROTOCOL 

(1394ARP) 

Section 7 - IP UNICAST 

Section 8 -IP BROADCAST) 

IP Forwarding Table MIB (IETF, http Ilwwwlettorg) 

(Section 5 - Definitions) 

Management Information Base for the Internet Protocol (IP) (IETF, 

http://www lett.org) 

(Sec!ion 4 - Updating Implementations 

Section 5 - Definitions} 

- 

DRD 

REFERENCES 

--------- 

-------- - 

SOW 

.. - ---------_. ------._-- 

------------- ------- -------- 

--------------------- , 

--------- 

.. 

-- 


Page 35 of73





Document 




REFERENCES 

ORO 

SOW 

RFC-4113 

RFC-4022 

~FC4301 

RFC-4302 

RFC-4303 

RFC-4835 

RFC-4306 

---- 

. f------,-,. 

1----- 

Management Information Base for User Datagram Protocol (UDP). 

(Internet Englneenng Task Force (IETF, http://WWWietforg)) (Section 

3 - Definitions) 

Management Information Base for Transmission Control Protocol 

(TCP) (Internet Englneenng Task Force (lETF, http://www letf.org». 


__ 

Secunty Architecture for the Internet Protocol (Intemet Englneenng 

Task Force (lETF, httpllwww.letf.org» 

(Section 4 - Secunty Associations 

Section 5 -IP Traffic Processing 

Section 6 - ICMP Processing 

Section 7 - Handhng Fragments (on the protected Side of the Ipsec 

Section 8 - Path MTu/DF ProceSSIni1L- 

IP Authentication Header (AH) (Internet Englneenng Task Force 

(IETF, httl:l//www.letf.org~ ________________ 

f-. 

IP Encapsulating Secunty Payload (ESP) (Internet Engineenng Task 

Force (IETF, htt(:l:/Iwww letf org» 

Cryptographic Algonthm Implementation Requirements for 

Encapsulating Secunty Payload (ESP) and Authentication Header 

(AH) (Internet Engineering Task Force (lETF, http://www.ietf.org)) 

Section 3.1 1: 

Systems must Implement AES-CTR (With 128 and 256-blt keys) and 

AES-CBC With 256-blt keys In addition to the encryption algonthms 

that the RFC states MUST be Implemented Tnple-DES encryption 

does not need to be Implemented. 

Systems must Implement NULL and AES_XCBC_96 authentication 

algonthms In addition to HMAC_SHA1_96 (and do not need to 

Implement HMAC MD5 96). 

Internet Key Exchange (IKEv2) Protocol {Internet Englneenng Task 

Force (IETF, http://WWW.ietf.org)) 

(Section 2 - IKE Protocol Details and Vanatlons 

Section 3 - Header and Payload Formats 

Section 4 - Conformance Requirements) 

----f-.------- 

---- 

------- 

; 

i 

I 

I 


Page 36 of?3





RFC-4307 

'RFC-4309 

RFC-3289 

RFC-3747 

RFC-2959 

STD-0007, RFC-0793 

Document 


----- 



Cryptographic Algonthms for Use in the Intemet Exchange (IKEv2) 

(Internet Englneenng Task Force (IETF, http//www.letf.org» Section 

3 - Algonthm Selection 

Mods to Section 3 1 

Systems must Implement RFC 3526 (2048 MODP group) In add Ilion 

to RFC2409 (1204 MODP group) 

Systems must Implement AES-128-CTR, AES-256-CTR, AES-128- 

CBC, and AES-256-CBC Instead of 3DES. 

Systems must Implement PRF _AES128_CBC In add Ilion to PRF 

HMAC SHA1 (and do not need to Implement PRF HMAC_MD5) 

Systems must Implement AUTH AES XCBC_96 In addition to AUTH 

HMAC SHA1 96 (and do not need to implement AUTH HMAC MD5 

96). 

USing Advanced Encryption Standard (AES) CCM Mode for Ipsec 

Encapsulating Secunty Payload (ESP) (lntemet Englneenng Task 

Force (IETF, httpflwwwletf.org») 

(Section 2 - AES CCM Mode 

Section 3 - ESP Payload 

Section 4 - Nonce Format 

Section 5 - AAD Construction 

Section 6 - Packet Expansion 

Section 7 - IKE Conventions) 

MIB for the Differentiated Services (Internet Englneenng Task Force 

(IETF, http://wwwletf.org)) 

(Section 4 - Convenlions used In thiS MIB 

Section 6 - MIB Definition =-:- 

1-- 

Differentiated Services Configuration MIB (Internet Englneenng Task 

Force (lETF, http //www letf.orgl) 

(Section 5 - The Differentiated Services Configuration MIB Module 

Design 

Section 6 - Template Cloning 

Section 7 - Managed Objects Definitions (MIB Module)} 

Real Time Protocol MIB (Intemet Englneenng Task Force (lETF, 

httl1.:f1www.letf.o'll)) (Section 2 - Overview 

Transmission Control Protocol (Internet Engineering Task Force 

(IETF, http://www.letf.org)) 

(Section 3 - FUNCTIONAL SPECIFICATION) 

,-- 

ORO 

REFERENCES 

SOW 

-- ----.- ----- 


Page 37 of73





STD-0062 

RFC-1323 

ID 

--- 

Document 

Version/Date 

51"0::0006, RFC-076S- f----------- 

STD::006(-RFC-3550 

f---- -----.. 

RFC~3551-------- 1---------- - - _~ectlon 8 - SSRC Identifier Allocation and Use) 

DTN 

Draft 



Structure of Management Information Version 2 (SMIv2) (See rfc- 

3411-rfc3418) 

TCP Extensions for High Performance (Internet Englneenng Task 

Force (IETF, http.//wwwiett.org» 

(Section 2 - TCP WINDOW SCALE OPTION 

Section 3 - RTIM. ROUND-TRIP TIME MEASUREMENT 

Section 4 - PAWS PROTECT AGAINST WRAPPED SEQUENCE 

___.__ 

User Datagram Protocol (Internet Englneenng Task Force (IETF, 

~BER~ 

httR:/!'1NINw.lett:2!9JllForma!.f~..kl~ OnlyL _________________ 

1------ 

RTP: A Transport Protocol for Real-Time Applications (Internet 

Engineenng Task Force (IETF, http://www.lettorgl) 

(Section 3 - Defimtlons 

Section 4 - Byte Order, Alignment, and Time Format 

Section 5 - RTP Data Transfer Protocol 

RTP Profile for Audio and Video Conferences with Mlmmal Control 

(Internet Englneenng Task Force (lETF, http://www.lett Org)) 

Section 4 1 Encoding Independent Rules 

Section 4.2 Operating Recommendations 

Section 4.3 GUidelines for Sample Based Audio Encoding 

Section 4.4 GUidelines for Frame-Based Audio Encoding 

Section 4.5.6 Audio Encoding - G279 

Section 7.0 RTP over TCP and Similar Byte Stream Protocols. 

Section 8.0 Port Assignments 

Section 10 0 Securi~ Assignments) 

DTN, Delay/Disruption Tolerant Networking, SpeCifications, 

http://www.lett.orflintemet-drafts/draft-irtf-





ID 

Document 

VersionlDate 

RFC-1305 Version 3 

f-ytu G.729 ----- ------- 

1-=-------.------------ 

ITU H.264 

"FlPSPUB 197---- -------- 

FIPS PUB 180-2 --- _. ---- 

FIPS PUB 186-2 

'FIPS PUB 198 

--1-:-:- 

CIS T.OO1 Nov 2005 

ReVISion 7 

~RM.633-- 



Network Time Protocol (NTP) Version 3 

(http://wwwletforg/rfc/rfc1305txt) (Internet Englneenng Task Force 

(IETF, http://www.ietforg)) 

(Section 3 - Network Time Protocol 

Section 4 - Filtering and Selection Algonthms 

Section 5 - Local Clocks 

Coding of speech at 8 kbltls uSing conjugate-structure algebralccodeexcited 

linear prediction (CS-ACELP) (International 

Telecommunications Union, (ITU, http'//www itu ch» ______________ 

Advanced Video Coding for Generic Audiovisual Services 

(http //www ItU intlrec/recommendatlon.asp?type=folders&lang=e&par 

ent=T-REC-H.264). (Intematlonal Telecommunications Union, (ITU, 

http:/~ ItU ch» . _______ 

Advanced Encryption Standard (AES) National I nstltute for Standards 

and Techno!.Q.gy (NIST, httll:/~,nlst 9.,0-'!1l -- 

Secure Hash Algonthms (SHA), sections on Secure Hash Algonthms 

(SHA) SHA-1 and SHA-256 Nabonallnstitute for Standards and 

Technology (NIST, http://www nlst.gov» 

_ All sections except 4.1.3, 4 2.3, 5.1.-2, 5.2.2, 5.3.3, 53.4, 6 3~§_4 ___ 

Digital Signature Standard (DSS), sections on Digital Signature 

Algonthm (DSA) National Institute for Standards and Technology 

(NIST, http //www.nlst gov», as amended by Change Notice 1. 

Sections 1 through 4 and Appendices 2 and 3. 

Keyed-Hash Message Authentication Code (HMAC) method National 

Institute for Standards and Technq!QgY1NIST, http·//www.nlst.gov)) 

Specification for Cospas-5arsat 406 MHz Distress Beacons (Sections 

2 and 3) 

TransmiSSion charactenstlcs of a satellite emergency posItion 

indicating radiO beacon (satellite EPIRB) system operating through a 

low polar-orbiting satellite system In the 406 MHz band (International 

TelecommUnications Union, (ITU, http://www itu.ch» (Sections 3 and 

4) 

DRD 

REFERENCES 

---------f---.------- 

----_._--f-.------ --- 

--------- -------------- 

1------------ 

c--'-- 

SOW 

------- 


Page 39 of73





RFC-2507 

ID 

Document 

Version/Date 

f-;;:,...------ - --.----- ----------- 

RFC-3986 

-iU=C-381 0--------- -;--_. 

RevIsion 2 

RFC-2858 

NPO 2570.50 

451-PN CODE-SNIP Revision 1 

MIL-STD-188-181 



IP Header Compression (Internet Englneenng Task Force (IETF, 

http:/twww.letf.ora) 

(Section 2 - Terminology 

Section 3 - Compression method 

Section 4 - Grouping packets Into packet streams 

Section 5 - Size Issues 

Section 6 - Compressed Header Formats 

Section 7 - Compression of subheaders 

Section 8 - Changing context Identifiers 

Section 9 - Rules for dropping or temporarily stonng packets 

Section 11 1 - Reordenng In non-TCP packet streams 

r?ectlon 13 - Demultlplexlng) 

Universal Resource Indicators (URI) - W3C Standard 

(http IIwww gblv.com/protocols/un/rfC/rfc3986 html) Internet 

Englneenng Task Force (IETF, http/twwwletforg) 

(Section 2 - Characters 

Section 3 - Syntax Components 

Section 4 - Usage 

Section 5 - Reference Resolution 

Section 6 - Normalization and Com~f!~Q.nL 

Multicast Listener Discovery Protocol (Internet Englneenng Task 

Force (IETF, http·/twww.letf.org}) 

(Section 3 - The Service Interface for Requesting IP Multicast 

Reception 

Section 4 - Multicast Listening State Maintained by Nodes 

Section 5 - Message Formats 

Section 6 - Protocol Descnptlon for Multicast Address Listeners 

Section 7 - Protocol Descnptlon for Multicast Routers 

Section 9 - List of Timers, Counters, and their Default Values 

Multi-protocol Border Gateway Protocol (Internet Englneenng Task 

Force (lETF, htto:/~.letf.om)) (Sections 2 - 7) 

NASA Electromagnetic (EM) Spectrum Management 

Space Network PN Code Libraries 

Interoperability Standard for Dedicated 5 kHz and 25 kHz UHF 

Satellite Communications Channels 

DRD 

REFERENCES 

SOW 

. ---------- ---------- 

-- 

----------- 

------- 


Page40of73





ID 

IEEE 802.119 

IEEE Std 1394b - 2002 2002 

Document 

VersionlDate 

rsAE-AS5643------ ----------- 

FAA TSOC91a 

-----. 

VV3C Rec.10 December:- 10 Dec. 2062-- 

2002 

W3C Rec. 12 February 12 Feb 2002 

2002 

r-' 

f-- 

ISOIIEC TR 9577: 1992 1992 

ITU-T Q.933,1995 1995 

-- 

IEEE 80211g 



IEEE Standard for a High Performance Senal Bus - Amendment 2 

(Section 4 - Cable PHY Specification 

Section 6 - Link layer specification 

Section 7 - Transaction layer specification 

Section 8 - Senal Bus management specification 

Annex A - Cable environment system properties 

Annex B - External connector pos)!lve_ retention) ---- 

IEEE-1394b Interface ReqUirements for MIlitary and Aerospace 

Vehicle ~tlons 

-------- 

Emergency locator Transmitter (El T) EqUipment 

- -------_._---- 

World Wide Web Consortium (W3C) XMl Encyrptlon Syntax and 

Processing (httll:llwww w3 orgfTRl2002lREC-xmlenc-core- 

200212101) Chapter 3 

World Wide Web Consortium (W3C) XMl Signature Syntax and 

Processing (httllllwww.w3.orgfTRl2002/REC-xmldsig-core- 

20020212/) Chapter 4 and 5 

------- 

THE FOLLOWING DOCUMENTS ARE APPLICABLE 

CHILDREN OF THE C31 CHILDREN DOCUMENTS LISTED 

ABOVE 

Information technology - Telecommunications and Information 

Exchange between systems - Protocol Identification in the Network 

layer, ISOIIEC TR 9577: 1992. - Annex C - Identification of Internet 

protocols 

"Signalling Specifications for Frame Mode SWitched and Permanent 

Virtual Connection Control and Status Momtonng", ITU-T 

Recommendation Q 933, 1995. - Annex E - Multlprotocol 

encapslJlation over frame relliY 

-- 

DRD 

REFERENCES 

SOW 

--------_. r--------.- 

---------- 

------------_._------- 

-------- 

---------- 

-_._------- 

---------- 

--------- 

--------- 

-------- 

-- 


Page 41 of73





ID 

Q.922 1992 

Document 

Version/Date 

'P;f394a-2000 ---------2000, 

Amendment 1 

--------- 

Std 1394-1995 1995 

RFC-1112 

RFC-1191 

RFC-1213 

-- 

- 



"ISDN Data Link Layer Specification for Frame Mode Bearer 

Services", ITU-T Recommendation Q.922, 1992 

Peer-to-peer communication 

(Section 3 - Elements of procedures and formats of fields for data hnk 

layer peer-to-peer communication 

Section 4 - Elements of layer-to-Iayer communication 

Section 5 - Definition of the peer-to-peer procedures of the data hnk 

layer Annex A) 

IEEE P1394a-2000, Standard for a High Performance Senal Bus- 

Amendment 1 






Annex B - External connector posItive retention 

Annex C - Internal device physical Interface 

-~n~~~~11_;~:~;~~~~~~~~~~ro:~~~~~:kormance Senal Bus 






Annex B - External connector posItive retention) 

Host Extensions for IP Multicasting 

(Section 4 - HOST GROUP ADDRESSES 

Section 6 - SENDING MULTICAST IP DATAGRAMS 

Section 7 - RECEIVING MULTICAST IP DATAGRAMS) 

Path MTU Discovery 

(Section 3 - Host specification 

Section 4 - Router specification 

Section 6 - Host Implementation) 

STD-0017 Management Information Base for Network Management 

of TCP/IP-based Internels: MIB-II (Sections 4 and 6) 

DRD 

REFERENCES 

---------- 

SOW 

------_.--------- 


Page42of73





RFC-1519 

f-RFC-1981 

Document 


- 

RFC-2113 

RFC-2119 ------- 

~-2132 

RFC-2210 

RFC-2215 

RFC-2287 

- 

.. _------ 

-- 



Classless Inter-Domain Routing (CIDR). an Address Assignment and 

Aggregation Strategy 

(Section 4 - Changes to Inter-





RFC-2385 

RFC-2461 

RFC-2462 

RFC-2578-------------------- 

RFC-2580 

RFC-2711 

RFC-2790 

RFC-2863 

REFERENCES 

Document 




ORO 

SOW 

Protection of BGP Sessions via the TCP MD5 Signature Option 

(Section 2 - Proposal 

Section 3 - Syntax) 

Neighbor Discovery for IP Version 6 (lpv6) 

------- 

(Section 2 - TERMINOLOGY 

Section 4- MESSAGE FORMATS 

Section 6 - Version Ipv6 nodes on the same link use Neighbor 

Discovery to 

Section 7 - ADDRESS RESOLUTION AND NEIGHBOR 

UNREACHABILITY DETECTION 

Section 8 - REDIRECT FUNCTION 

---------- -;~ectlon 10 - PROTOCOL CONS1.~NTS) 

Ipv6 Stateless Address Autoconfiguration 

--- ---------_._------ 

(Section 4 - PROTOCOL OVERVIEW 

Section 5 - PROTOCOL SPECIFICATIO~L _______________ 

------------------ 

Structure of Management Information Version 2 (SMIv2) 

(Section 2 - Definitions 

Section 3 - Information Modules 

Section 4 - Naming Hierarchy 

Section 5 - Mapping of the MODULE-IDENTITY macro 

Section 6 - Mapping of the OBJECT-IDENTITY macro 

Section 7 - Mapping of the OBJECT-TYPE macro 

Section 8- MapPing of the NOTIFICATION-TYPE macro) 

Conformance Statements for SMIv2 

---_ .._---_. 


Section 3 - Mapping ofthe OBJECT-GROUP macro 

Section 4- MapPing of the NOTIFICATION-GROUP macro 

Section 5 - MapPing of the MODULE-COMPLIANCE macro 

Section 6 - MapPing ofthe AGENT-CAPABILITIES macro) 

Ipv6 Router Alert Option 

(Section 2 - Approach) 

Host Resources MIB 


The Interfaces Group MIB 

(Section 3 - Expenence With the Interfaces Group 

Section 6 -Interfaces Group Definitions) 


Page44of73





Document 

ID 

VersionlDate 

RFC-2983 

RFC-3315 

RFC-4291 

TFC-115S----- --------- 

RFC-1156 

~~3410- 

'RFC-3411 

'RFC-3412 

----_._-._------- 

--- 

--- 

-- .. 



Differentiated Services and Tunnels 

(Section 4 - Ingress Functionality 

Section 5 - Egress Functionality) 

Dynamic Host Configuration Protocol for Ipv6 (DHCPv6) 

(Sections 5,6,7,8,9,13,15, 17, 18~ 

IP Version 6 Addressing Architecture 

(Section 2 - Ipv6 Addressing) 

Structure and Identification of Management Information for TCP/IPbased 

Intemets 

(Section 3 - Structure and Identification of Management Information 

Section 4 - Managed Objects 

Section 6 - Defimbons) 

Management Informabon Base for Network Management of TCP/lPbased 

mtemets 

(Section 4 - Objects 

Section 5 - Object Defimtions 

Section 6 - Definibons) 

Introduction and Applicability Statements for Intemet-Standard 

Management Framework 

(Section 2 - The Intemet Standard Management Framework 

Section 6 - SNMPv3 Framework Module Specifications) 

An Architecture for Descnbmg Simple Network Management Protocol 

(SNMP) Management Frameworks 

(Section 3 - Elements of the Architecture 

Section 5 - Managed Oblect Definitions for SNMP Management 

Frameworks) 

Message Processing and Dispatching for the Simple Network 

Management Protocol (SNMP) 

(Section 3 - Elements of Message Processing and Dispatching 

Section 4 - Dispatcher Elements of Procedure 

Secbon 5 - Definibons 

Section 6 - The SNMPv3 Message Format 

Section 7 - Elements of Procedure for v3MP) 

-- 

DRD 

REFERENCES 

SOW 

-- 

f------------- 

____________ 

1------------r---·----- 

--- 

------ 

, 

- - 

---- 

------- 


Page 45 of73





RFC-3413 

RFC-3414 

ID 

Document 

Version/Date 

----------------- 

RFC-3415 --------- ----- 

--==::-:--------- 1-- 

RFC-3416 

RFC-3417 

RFC-3418 

RFC-919 



Simple Network Management Protocol (SNMP) Applications 

{Section 3 - Elements Of Procedure 

Section 4 - The Structure of the MIB Modules 

Section 5 - Identification of Management Targets In Notification 

Onglnators 

Section 6 - Notification Filtering 

Section 7 - Mangement Target Translation In Proxy Forwarder 

~2Q!!catlonsl 

User-based Security Model (USM) for version 3 of the Simple 

Network Management Protocol (SNMPv3) 

{Section 2 - Elements of the Model 

Section 3 - Elements of Procedure 

Section 4 - DlscovelY 

Section 5 - Definitions 

Section 7 - HMAC-SHA-96 Authentication Protocol 

Section 8 - CBC-DES Symmetnc EnclY~tlon Proto~..2!l ____-:-- 

View-based Access Control Model (VACM) for the Simple Network 


{Section 2 - Elements of the Model 

Section 3 - Elements of Procedure 

Section 4 - DefinitionsL 

Version 2 of the Protocol Operations for the Simple Network 



Section 4 - Protocol Specificatlol!.) 

Transport Mappmgs for the Simple Network Management Protocol 

(SNMP) 


Section 3 - SNMP over UDP over Ipv4) 

Management Information Base (MIB) for the Simple Network 


(Section 2 - Definltions-) 

Broadcasting Internet Datagrams 

(Section 6 - Gateways and Broadcasts 

Section 7 - Broadcast IP AddreSSing - Proposed Standards) 

1--- 

ORO 

------_..- 

REFERENCES 

______________ 

--------- 

---------_.__._--- 

------ 

SOW 

_._----- 

---- 

---------- 


Page 46 of 73





RFC-922 

RFC-950 

RFC-1034 

RFC-1035 

RFC-2207 

RFC-24D4 

~C-2410 

RFC-2747 

RFC-3526 

RFC-3566 

RFC-3602 

ID 

-- 

-- 

Document 

Version/Date 

- -- -- 

--_ 

.. _-_._---- 

- 



Broadcasting Intemet datagrams In the presence of subnets 

(Section 4 - Broadcast Classes 

Section 5 - Broadcast Methods 

Section 6 - Gateways and Broadcasts 

Section 7 - Broadcast IP Addressing - Conventions) 

Internet standard subnetting procedure 

(Section 2.1 -Interpretation of Internet Addresses 

Section 2.2 - Changes to Host Software t2....l?~ort _~ub~!&. 

Domain names - concepts and faCIlities 

------ 

Domain names - implementation and specification 

(Section 3 - DOMAIN NAME SPACE AND RR DEFINITIONS 

Section 4 - MESSAGES 

Section 5 - MASTER FILESL _____ . ___ . _____________ 

RSVP Extensions for IPSEC Data Flows 

(Section 3 - Object Definition 

..,gElctlon 4 - Processing Rules) _ 

------- 

The Use of HMAC-SHA-1-96 Within ESP and AH 

(Section 3 - KeYing Matenal 

r-~ectlon 4 - Interaction With the ESP Clr:!her MechanlsIT!.L _____ 

The NULL Encryption Algonthm and Its Use With Ipsec 

(Section 2 - Algorithm Definition 

Section 3 - ESP NULL Operational Reg~Jlrem.!l.!l~ _________ 

RSVP Cryptographic Authentication 

(Section 2 - Data Structures 

Section 4 - Message Processing) 

More Modular Exponential (MODP) Diffie-Heilman groups for Internet 

Key Exchange (IKE) (Section 3 - 2048-blt MODP Group) 

The AES-XCBC-MAC-96 Algorithm and Its Use With Ipsec 

(Section 3 - BaSIC CBC-MAC With Obligatory 10' Padding 

Section 4 - AES-XCBC-MAC-96) 

AES-CBC Cipher Algorithm and Its Use With Ipsec 

(Section 2 - The AES Cipher Algorithm 

Section 3 - ESP Pa}lload} _._- 

DRD 

REFERENCES 

SOW 

--------_._------ 

._------------ 

._-------- ------------ 

1--._----- ._------ 

-------- 

f------- ---------- 

- 


Page 47 of73





ID 

RFC-3686 

RFC-3748 

-RFC-3948 

RFC-4434 

FiPS-PUB 180-1 

FIPS PUB 197 

RFC-2104 

RFC-3629 

Document 

Version/Date 

---- 

--------- 

- ---. 

----- 

-- 



USing Advanced Encryption Standard (AES) Counter Mode With 

Ipsec Encapsulating Secunty Payload (ESP) 

(Section 2 - AES Block Cipher 

Section 3 - ESP Payload 

Section 4 - Counter Block Fonnat) 

--------- 

Extensible Authentication Protocol (EAP) 

(Section 2 - Extensible Authentication Protocol (EAP) 

Section 3 - Lower Layer Behavior 

Section 4 - EAP Packet Fonnat 

Section 5 -Imtlal EAP Reguest/~~onse Types) _________.___.__ 

UDP Encapsulation of Ipsec ESP Packets 

(Section 2 - Packet Fonnats 

Section 3 - Encapsulation and Decapsulation Proceduresl_ 

The AES-XCBC-PRF-128 Algonthm for the Internet Key Exchange 

Protocol (IKE) 

~tion 2 - The AES-XCBC-PRF-128 AI99J1!L ______________ 

FIPS PUB 180-1· Secure Hash Standard, Apn11995. 

(Section 3 - Message Padding 

Section 6 - Constants Used 

Section 7 - Computing the Message Digest) ____ 

FIPS PUB 197, "Advanced Encryption Standard (AES)," November 

2001. 

(Section 2 - Defimtions 

Section 3 - Notation and Conventions 

Section 5 - Algonthm SpeCification) 

HMAC: Keyed-Hashing for Message Authentication 

(Sections~ 

UTF-8, a transfonnation fonnat of ISO 10646 

(Section 2 - Notational conventions 

Section 3 - UTF-8 defimtlon 

Section 4 - Syntax of UTF-8 Byte Sequences 

Section 5 - Versions of the standards 

Section 6 - Byte order mark (BOM)) 

DRD 

r-------- 

REFERENCES 

1--._._---------------- 

1-------- 

SOW 

------- 

---- 

--_._------ 


Page 48 of73

H- 



Attaclnnent J-3 


ID 

Document 

VersionlDate 

ISO/IEC 10646:2003, December 

December 2003 2003 


DOCUMENT 

-- 

1------------------------ 

i-CCSDS 301.0-S::a----- _ --_._._---- 

Issue 3, 

January 2002 

CCSDS 660.0-R-2 

- 

Draft 

----------- - 

IETF RFC 3280, Section 

4 

~EE-754-------r-------- 

1-jso-1000:1992 

3'" edition, 

1992 

ISO 860f:2000 ----- 2 na edition, 

2000 

OASISXACML 2.0 

OASISSAML 

V20 



Informalton Technology - Universal Mulltple-Octet Coded Character 

Set (UCS) 

(Ap~endlx 0 - UCS TransformatIon Format 8 (UTF':!!)l 

PARENT APPLICABLE DOCUMENT: CxP-70022, Constellation 

C31 Interop-erabili!}, Standard Books, Volume 4 

-- 

CXP-70022 V4 Approved Children 

- ---------- 

I-- 

DRD 

REFERENCES 

- 

SOW 

------ 

1--------------_._--- 

1---- --------- --I-- - - --- - --.. ---_._----- 

Time Code Formats. Recommendalton for Space Data System 

Standards, Blue Book Issue 3. Washmgton, 0 C. CCSDS, January 

2002 

httl,l:.t.lRllPhc_ ccs~s or,g/l,lubhcatlons/arc~l"e'_3q1 xOb3 Rdf ____ 

i--- 

-- 

XML Telemetry and Command Exchange (XTCE) 

Red Book - Draft Recommendation Standard 

c-------------------- 

-Internet X.509 Pubhc Key Infrastructure Certificate and -certifieate-- 

Revocation List (CRL) Profile, Section 4 Cerlificate and Cerlificate 

Extensions Profile 

---- _._-- 

_________ n_. 

IEEE Floatmg Pomt Standard 

htt(l/len.wlkl(ledia.orglwlkIIlEEE 754 

httl,l /lbabbage.cs.gc,edulcourseslcs341II EEE-754references.html 

SI Units and Recommendations for the Use of Their Multiples and of 

Certam Other Units. Internaltonal Standard, ISO 1000.1992. 3rd ed 

Geneva ISO, 1992. 

Data Elements and Interchange Formats, Information Exchange, 

RepresentatIon of Dates and Times InternatIonal Standard, ISO 

8601·2000. 2nd ed. Geneva ISO, 

htt(l:llwww.iso orgliso/en/(lrods-servicesl(lo(lstdsldatesandtlme html 

htto:/lwww cl.cam.ac.uk/-mak25/iso-ltme.html 

XACML 2.0 Speclficalton Set 

SAML V2.0 SpeCificatIon Set 

-- 

~---------- 


Page 49 of 73





ID 

Document 

Version/Date 

Unicode Standard Version 5 0, 

Fifth Edition, 

27 Oct 2006 

f--- PARENT APPLICABLE 

DOCUMENT 

1---------- 

1---- 

~GM1996 1996 

1--=---------- 

GRAM-99 

JWPD ----.-- 

---,-,-,--_._- 

1999 

~:--------- ~--.-. 

LP100K 

MEM 

-- 

____ H. 

-- 

ORDEM2000 2000 

-- 

NASA-HDBK-1001 

~ 

1--- 

RTCAlDO-160D 

(For gUidance only) 

SAE-ARP-5412 


SAE-ARP-5414 




The Unicode Standard, Version 5.0, Fifth Edition, The Unicode 

Consortium, Addison-Wesley Professional, Oct. 27, 2006. ISBN 

0321480910 

PARENT APPLICABLE DOCUMENT: CXP-70023, 

Constellation Program Design Specification for Natural 

Environments (DSNE) 

------ - 

...- 

CXP-70023 Approved Children 

_._-- ------.---------------------._---- 

f-.---------- - ----.--------------.----- 

Earth Gravitational Model 1996 

c-=~-.-------------------.----------- 

MeteorolQ.!=nglneenng Mode~EM) 

________ .. ______ 

Orbital Debns Englneenng Model (ORDEM 2000} 

Terrestnal Environment (ClimatiC) Cntena Handbook for Use In 

I-~erospace Vehicle Development 

Range Reference Atmosphe.!:e (RRA) Model 

Environmental Conditions and Test Procedures for Airborne 

Equipment (Section 22. Lightning Induced Transient Susceptibility 

and Section 23: Lightning Direct Effects) 

Aircraft Lightning Environment 

Aircraft Lightning ZOning 

DRD 

REFERENCES 

---- 

SOW 

--p;= 

CEV-T-044, 2.81,28.2, 

CEV-T-045 2.8 3 

.._._----------t---- - ----- 

--_.__ ! 

.-._---- ------ - - ----- 

--------------_._----- 

------------- 

Global Reference Atmosp!!.enc MO,gel, 1999 Version ~RAM-9~t ___ 

..- 

---.------ 

Jlmosphere Wind Profile Dataset 

._-----[-------------- 

Lunar Pros~ctor 1001Ul::.P1 OO~L Gravl!y Model ._-_._- --- -------_.- 

f---.------ 

--_._---- 

r------ 

- -----_ 

.. _--- 

--------- 

-- 


Page 50 of73





f--. 

Document 



DOCUMENT 

AS9003 

~~--------- 

AS9100B 

-- 

AS91 02 

AS91 03 

AS9110 

AS9120 - 



ORO 

REFERENCES 

PARENT DOCUMENT: CXP-70059, Constellation Program 

Integrated Safety, Reliability, and Quality Assurance 

CEV-S-001, 

CEV-S-014 

3.5 

(SR&QA} Requirements 


-------- --------- 1-. ---- -------- 

------------- 

----- 

---- ---- 

~---.--.-------1--- 

---- 

Inspection and Test Quality System 

-- ---------- 

Quality Management Systems - Aerospace Requirements (SAE) 

---"----- .----- 

Aerospace First Article Inspection Requirement 

-- 

Variation Management of Key Charactenstlcs 

~- - --------- 

Quality Mamtenance Systems - Aerospace - ReqUirements for 

Maintenance Organizations 

----_.- -;- ~-------- 

Quality Management Systems - Aerospace Requirements for Stockist 

Dlstnbutors 

--t-------- 

-- 

SOW 

-------- 

-- - -------- 

-------- 

-----_._---- 

------_._- 

---------_._- 

"PARENT APPLICABLE 

DOCUMENT 

- 

----- 

PARENT DOCUMENT: JPR 8080.5, JSC Design and E-22 CEV-T- 

Procedural Standards 027; 

E-6 CEV-T- 

024 ; 

JPR 8080.5 Approved Children 

E-7 CEV- 

027 ; 

M/S-11 :CEV- 

T-044 

2.6, 2.8 4, 6 1.3, 

6.23,643 

- 

I 

, 

A1AA-S-080 1999 

AIM Standard for Space Systems - Metallic Pressure Vessels, 



Page 51 of73





ID 

Document 

Version/Date 



DRD 

REFERENCES 

SOW 

ANSI/AIAA-S-OS1A-2006 2006 


Section VIII, Divisions 1, 

2, and 3 

f-ASTMA36 

NASA-STD-(I)-6016 09-11-2006 

(replaces JSC-49774A) 

-- --'--- 

NASA-STD-3000, 30Dec_2005 

Volume VIII 

Replaced by CXP-70024 

---- 

NASA-STD-5001 21 June 1996 

NAS 412 (1997) -- [-1997 

1--- 

NSTSOS060 

Replaced by:JSC 62S09 

SAE-ARP-5412 


1-'-- 

SAE-ARP-5413 


SAE-ARP-5414 


SAE-ARP-5415 

(For guidance only) 

RevC 

23 Jun 2006 

---f-- 

AIM Standard for Space Systems - Composite Overwrapped 

Pressure Vessels 

ASME BOiler and Pressure Vessel Code, Section VIII : Pressure 

Vessels DIvIsions 1, 2, and 3 

Standard Specification for Carbon Structural Steel 

---- -----------f-------- 

Standard Matenals and Processes ReqUirements for Spacecraft 

NASA-STD-3000, Volume VIII, Human Systems Integration 

Standards (HSIS), CEV Launch Segment (CEV and CEVLV) 

-- 

----- 

Replaced by: Constellation Human Systems Integration 

ReqUirements (HSIR) 

----------------------------- 

Structural Design and Test Factors of Safety for Space Flight 

hardware 

Foreign Object Damage/Forelgn Object Debns (FOD) Prevention 

-------_._------------------------1------ ------- 

Space Shuttle System Pyrotechnic SpeCification 

Replaced by Constellation Spacecraft PyrotechniC SpeCification 

Aircraft Lightning EnVironment 

- 

Certification of Aircraft Electrical/Electronic Systems for the Indirect 

Effects of Lightning 


Users Manual for Cerbficatlon of Aircraft Electncal/Electronic Systems 

for the Indirect Effects of Lightning 

- 

_.- f----------- 

1------ f------- 

---------- f----------- 

------ 

J 

--f--------____ 

--_._---_._- 

------------. 

! 

- 

i 

i 

I 

I 

AttachmentJ-3 

Page 52 of73





SAE-ARP-5577 


Document 




Aircraft Llghtmng Direct Effects Certification 

ORO 

REFERENCES 

SOW 


DOCUMENT 

----------- 

---------- 

--=-=------------_._----- 

CxP 70152 

Baseline 

Release 

03 Oct. 2007 

JSC-20584 - June 1999 

JSC 63307 June 2007 

ANSIZ136.1 

FAA-HF-STD-001 

Sections 14.1 through 

14.5 

~guidance only) 

FED-STD-595 

(for guidance only) 

ISO 2631-1 

-------------_.- 

-- 

ISO 3382 




NCRP Report #132 

Table 4.2 and Table 4.3 

No Number 

PARENT DOCUMENT: CXP-70024, Constellation Human 

Systems Integration Requirements (HSIR) 

1------- - -- 


I-;; -- 

Constellation Program Crew Interface Labeling Standard 

Spacecraft Maximum Allowable Concentrations for Airborne 

Contaminants 

--- 

Optical Design and Venficatlon Critena for Windows In Human 

~~fl!g!l.!...~hcabons (May 2007) 

Amencan National Standards Institute (ANSI) standard, ANSI Z136.1, 

"Amencan National Standard for Safe Use of Lasers" (2000) 

Federal AViation Admlmstrabon Human Factors DeSign Standard 

Colors Used in Govemment Procurement (12/15/89) 

International Standards Orgamzation (ISO) standard 2631-11997 (E) 

"Measurement of the reverberation time of rooms with reference to 

other acousbcal parameters" 

Volume I, Man-Systems Integration Standards (MSIS), ReVISion B, 

1995, Section 3.3.3. 

National Council on Radiation Protecbon and Measurements (NCRP) 

report number 132 

41-node man model for calculating stored body heat 

- 

Section 3.7 

CEV-T-045 

_. -- 

-- 

----.-------- 

-- 

2.6,2.71,287, 

3.1.6, 6 2.3, 

6.4.3 --------j 

I 

--------_.----_._-- 

---------_----------- 

CEV-T-089 28.7 

------_._. 

---- 

------ 


Page 53 of?3





No Number 

No Number 

No Number 

ID 

Document 

Version/Date 

-- 

No Number 

~- -- ------1------ 

c-- ------ 


DOCUMENT 

f-- 

1--- -- 

1-------- 


JPR8080.5 


NPR8715.5 

JSC62550 

CxP-72085 

NASA-STD-(I)-5019 


B 

September 

2006 



"Human Mental Workload" by Hart, S.G., and Staveland, L.E. (1988). 

Development of NASA-TLX (Task Load Index) results of empincal 

and theoretical research (pp. 139 -183). 

"Usability Engineenng" (1993) by Jakob Nielsen 

"The use of pilot rating In the evaluation of aircraft handling qualities" 

\--gY, Cooper, G E and Ha~er, R.P {1969) Report TN-D-5153 

Wissler model for calculating stored body heat 

PARENT DOCUMENT: CXP-72000, Systems Requirements 

for the Crew Exploration Vehicle Element 

-- 

CxP-72000 Approved Children 

--- 

NASA Standard for Ground Support EqUipment 

c-- 

JSC DeSign and Procedural Standards' 

DeSign Development for Cntlcal Mechanical Systems 

Range Safety Program- 

Strength, Design and Verification Cntena for Glass, Ceramics and 


Crew Exploration Vehicle (CEV) Outer Mold Line 

Fracture Control ReqUirements for Spaceflight Hardware 

Flammability, Odor, Off-GaSSing and Compatibility ReqUirements & 

Test Procedures for Matenals in EnVironments that Support 

Combustion (Superseding NHB-8060 1 C) 

DRO 

REFERENCES 

------1---------- 

CEV-M-001, 

CEV-M-002, 

CEV-O-001, 

CEV-S-009, 

CEV-T-031, 

CEV-T-034 

1--------- 

1---------- 

1--------- 

1----------- 

SOW 

-- 

Scope, 11,22, 

2 3.(c), 31, 

61.3,6.1.6.1, 

6 2.3, 6.2 6 1, 

6 4.3, 6.4 6 1, 

65.3,1066 

----_._---- 

---------- 

------ 


Page 54 of 73


Crew ExploratIon Vehicle - (CEV) 



ID 

Document 

Version/Date 



DRD 

REFERENCES 

SOW 

NPR2810.1 26 Aug. 1999 

NPD 8710.3B 

f---- ---- 

JSC 62809 

Rev C 


23 June 2006 

-----_..- 

------------- ----------- 

SAE-AS-5643 

SAE-AS-5643/1 

f-- -- ------ - ----- 

ANSI/AIAA S-80 1998 

----------- 

ANSI/AIAA S-081A-2006 2006 

-- 

----- 


DOCUMENT 

-- 

Secunty of Infonnational Technology 

Subject NASA Policy for Limiting Orbital Debns Generation 

(Revalidated 4/28/04) 

Constellation Spacecraft Pyrotechnic Specifications 

Standard Manned Spacecraft Requirements for Matenals and 

Processes 

-- 

IEEE-1394b Interface Requirements for MIlitary and Aerospace 

Vehicle Applications 

-----------_. 1---._--- ---------------- 

S400 Copper Media Interface Charactenstics Over Extended 

Distances 

Standard, Space Systems - MetalliC Pressure Vessels, Pressunzed 

Structures, and Pressure Components 

-- 

Standard, Space Systems - Composite Overwrapped Pressure 

Vessels (COPVs) 

-- --- 

_._------ -------------------_.__._------ 

PARENT DOCUMENT: CxP-72008, Crew Exploration 

Vehicle Project Plan 

- -- 

CxP-7200B Approved Children 

H-20 

- - -------_.---------- 

--_._-_.-------_._-- 

------_.__..- .--------- 

CEV-M-005 

------------- 

_.- --------- 

, 

-- -------- 

Scope, 1 4, 2.1, 

23 (c), 2 4, 2.6, 

61 1,62.1, 

641 

ESMD-SBUWI1 Version 1.0 

1 Aug 2007 

Exploration Systems MIssion Directorate (ESMD) Sensitive But 

Unclassified (SBU) Work Instruction 


DOCUMENT 

PARENT DOCUMENT: CxP-72234, Integrated Vehicle 

Ground Vibration Test (GVT) Task Plan 

TBD 

TBD 


Page 55 of73





r-----' 

1--- 

CxP-72226 

CxP-72228 

r-- 

ID 

Document 

Version/Date 

Baseline 

Release, 

1218/07 

-- 

Baseline 

Release, 

12/8/0L ___ 

I-PARENT APPLICABLE 

-_. DOCUMENT 

---------- 

SSP 30240 -- --------_. 

RevE 

(For gUidance Q!!!y~ _ _ 25 July 2003 __ 

MIL-STD-464A 19 Dec. 2002 

-- MIL-STD-461 E 20Aug 1999 

-- 

ML0303-0014 

RevN 

16 June 2004 

NASA-STD-4003 8 Sept. 2003 

ASTM-E595-93 (re- 1993/2003 

al!~roved 2003) 

MSFC-SPEC-250A (1977) 1 Oct. 1997 

JPR8080.5 

SAE-ARP-5412 

liEc>r..guldallc~ only) 

------------------- 

Rev A 

15 March 2005 




Integrated Vehicle Ground Vibration Test (IVGVT) CEVlCLV Interface 

ReqUirements Document (lRD) 

---------- 

IVGVT STEfOnon IRD 

~--------- ---------- 

---PARENT DOCUMENT: CXP-70026, Crew Exploration Vehicle- 

_ ..____-..JCI§..~ Crew Launch Vehicle (CL~ IRD ________ 


f--~----------.------------------------ 

Space Station Grounding Requirements 

Electromagnetic Environmental Effects Requirements for Systems 

ReqUirements fu'r the Control o(Electromagnetic Interference (EMI) 

Characteristics of Subsystems and ~lQI!Ient _ ... - 

Electncal Wire Harnesses and Coaxial Cables, Installation 

ReqUirements for Electromagnetic Compatibility 

Electncal Bonding for NASA Launch Vehicles, Spacecraft, Payloads, 

and Fli!lht ~ulQment 

Standard Test Methods for Total Mass Loss and Collected Volatile 

Condensable Matenals from Outgassln!l In a Vacuum Environment 

Protective Finishes for Space Vehicle Structures and Associated 

Flight EqUipment, General Specification For 

JSC DeSign and Procedural Standards (and associated Children 

documents as speCified in Attachment J-3, Applicable, Guidance, and 

Informational Documents List) (exclusive of government shalls) 

Aircraft lightning EnVironment 

-- 

DRD 

REFERENCES 

- 

SOW 

---------- 

r-----.-----------" 

1------- ---------_.._----- 

23 (a) 

---------------- 

---_.__._------- - --------- 

----------------- 

----------------- 

- -----._-----._-------- 

1------------------ 

--1-------- 


Page 56 of73





ID 

SAE-ARP-5413 

(For QUldance only} 

f-- 

SAE-ARP-5414 

! (For gUidance onl}') 

SAE-ARP-5415 

, (For Quidance onl'll ___ 

SAE-ARP-5416 

Document 

VersionlDate 

lJE9r guidance only} ____ -----_._-- 

SAE-ARP-5577 

(For aUldance .QI:l.IU_._ --------- 

IEEElASTM SI10 

f------ ---- 

--_. __ . 

PARENT APPLICABLE- --_._----- 

DOCUMENT 

.N 

1------_._---___________ 

f---------- -- 


PARENT APPLICABLE' 

DOCUMENT 



Certification of Aircraft ElectncallElectronic Systems for the Indirect 

Effects of liQhtning 


Users Manual for Certification of Aircraft Electrical/Electronic Systems 

for the Indirect Effects of Lightnll!ll...- 

Aircraft Lightning Test Methods 

'-,---- ------- 

Aircraft Lightning Direct Effects Certification 

-Amencan NatiOmil Standard for Use of the International System of 

Units (§!) The Modem Metnc S},stem --------- 

Standards for Models and Simulations 

-- 

I--PARENT DOCUMENT: CXP-70135, Constellation Program 

Structural Design and Verification Requirements 

--1---- 


- 

-_. 

DRD 

REFERENCES 

SOW 

-- 

---------- 

1-- ---_.- 

------------- 

----------- -----_._-- 

1------- ---- -------- 

- PARENT DOCUMENT: CxP~70076, Constellation Program CEV-T-001, 

Modeling and Simulation Management Requirements - CEV-T-002 

--_.- 

Level II 

1-- 


----t----------------------- 

1--------- ---- 

-------------------- 

--------_._---- 

-~------ 

f-- 


NASA-STD-(I)-6016 9/11/06 

NASA-STD-(I)-5019 9-12-2006 

Strength and Life Assessment Requirements for LiqUid Fueled Space 

PropulSion System EnQlnes 

Standard Manned Spacecraft Requirements for Matenals and 

Processes 

Fracture Control ReqUirements for Constellation Spaceflight 

Hardware 


Page5? of?3





JSC-62550 

20M02540 

ID 


MSFC-STD-486 

TAEAS8879 

Document 

Version/Date 

--f----- 

NSTS08123 

MSFC-SPEC-626 

1-----------1----- 

-- 

------ 



Strength, Design and Verification Critena for Glass, Ceramics and 

Windows In Human S!:!ace Flight A!:!!:!lIcations 

Assessment of FleXible Lines for Flow Induced Vibration 

NASA Fastener Integnty 

Standard Torque Limits for Threaded Fasteners 

'-Screw Threads, UNJ Profile, Inch 

--------------c---------- 

c--------- 

"NsTS08307 

-------- 

Cntena for Preloaded Bolts 

ANSIlAlAA-S-080=-1998 Standard for Space SystemS-Metallic Pressure Vessels, Pressunz~ 

-- 

Structures, and Pressure Com~onents 

- ------------- 

ASTM E1417-95a 

Practice for LiqUid Penetrant Examination 

----_.--=------------------- 

'MsFC~RQMT-3479 

Fracture Control ReqUirements for Composite and Bonded Vehicle 

and Payload Structures ---- 

Certification of Flex Hose and Bellows for Flow Induced Vibration 

-- 

Test Control Document for Assessment of FleXible Lines for Flow 

Induced Vibration 

---- 


-PARENT DOCUMENT: FTO-AFT-FTA-004, Flight Test 

DOCUMENT 

Article Sllstem Requirements Document 

FTO-AFT-FTA-004 Approved Children 

1-- -- f--- 

-- 

DRD 

c------------- 

c------------ 

-- 

CEV-D-002 

c---- 

REFERENCES 

SOW 

-------------- 

-------- 

---------- 

--------1----------- - 

- ---------1------------ 

-------- 

-- 

-- 

--------- 

------- 

FTO-AFT -OPS-001 Rev. A Concept of Operations 

19 Jan. 2007 

FTO-AFT -FTA-001 Rev. F Flight Test Arbcle EnVironmental Requirements Document 

25 Nov. 2008 

FTO-AFT-FTA-003 RevB Flight Test Arbcle Geometry & Mass Properties ReqUirements 

29AuQ 2007 Document 

FTO-AFT-FTV-011-PA1 Rev.C Orion Launch Abort Vehicle Developmental Flight Instrumentation 

(For auidance onlv) 22 Feb 2009 Master Measurement List for PA-1 

FTO-AFT-FT A-024-PA1 Rev A DFI to FTA Interface Control Document, PA-1 

27 Feb 2009 

10.6.4 I 

, 


Page 58 of73





ID 

Document 

Version/Date 



REFERENCES 

DRD 

I 

SOW 


Page 59 of73





1.2 APPLICABLE ENVIRONMENTAL DATA DOCUMENTS 

The Contractor shall comply with the following applicable enVIronmental data documents. 

Document Title 

Trajectories 

CLV Reference Design Trajectones (3DOF Nominal) 

CLV Reference Design Trajectories (3DOF Dispersed) 

CL V Reference Design Trajectories (6DOF Nominal) 

CL V Reference Design Trajectories (6DOF Dispersed) 

Aerodynamics 

CAP Aero Database (CxP 72167) 

CAP Aerothermal Database (CxP 72168) 

CAP Aero Database (CxP 72214) 

CAP Aerothermal Database (CxP 72068) 

Loads 

SECO Max Acceleration 

Liftoff Acoustics 

Launch Loads 

Fatigue Spectra (Ascent, Rollout, pre-launch, and hft-off) 

ISS Mated Interface Loads 

Docking Loads 

TLILoads 

CEV Solar Array ISS Plume Loads 

EV AfiV A Loads 

EDS, Altair, CEV mated geometry/mass properties 

CM Water Landing Monte Carlo 

Drogue Chute Deployment Loads 

Document Version 

TR6 

TD6 

TR6 

TD6 

041 

0.501 

ADAC-2B 

TE3 

1-Nov-07 

CxP 72164 (Draft Aug '07) 

LA3 

Initial - DCI-TM-040308-1043-01 

TDS SIG-03-001 

TDS S IG-03-003 

CxP ZF-08-003 

E-mail "Re:Appendage Plume Interface 

Loads for Orion DAC 2 Kick-off" 

E-mail:"IVA loads" 

E-mail:"Re:TLI stack Mass properties", 

22-0ct-07 

3/12/2006; 2 Sigma skipped 1st stage 

drogue deployment 


Page 60 of73



2.0 GUIDANCE DOCUMENTS 



Guidance documents are listed for two purposes 

1) To be used by the contractor as a level of standards that must be met or exceeded If 

alternative standards are recommended by the contractor. If the alternative standards are 

approved by NASA, then the guidance document will no longer be tracked as a contractual 

document 

2) To be used or tailored per direction within a ORO description The resulting new or tailored 

document deliverable will take precedence over the associated guidance document once the new 

or tailored document deliverable is approved by NASA. After the new or tailored document is 

approved by NASA, the original "gUidance document "IS no longer a contractual document. 


Page 61 of73





ID 

Document 

Version/Date 

GUIDANCE DOCUMENT TITLE 

REFERENCES 

DRD 

SOW 

533 DRD-eCCR 

A1A1NAS NA5M20995 

533 Electronic Submission Example 

Wire, Safety or Lock 

CEV-B-001 

12 (a) 

2613 

-- 

AlA NA5 410 

Certification & Qualification of Nondestnctlve Test Personnel 

CEV-T-023 

I 

-- 

._------_..- 

-----.--- 

AN51/A1AA G043-1992 1992/2004 GUidance for Preparation of Operational Concept Documents 

CEV-O-001 27.1 

1--- -- --------- 

AN51/AlAA 5-080-1998 

Space Systems-Metallic Pressure Vessels, Pressunzed Structures, 

and Pressure Components 

1--------------1-------- -- --- 

----------------_._----- 

AN51/AlAA 5-081A-2006 

Space Systems-Composite OvelWrapped Pressure Vessels (COPVs) 

1--- ----------_. 

---------------- 

AN51/A5QC Z1.4 

Sampling Procedures and Tables for Inspection by Attnbutes 

2.6.13 

------f-----------.---.-------------------- 

--- ---- ------_._._- 

AN51/A1AA 5-080-1998 

Space Systems-Metallic Pressure Vessels, Pressunzed Structures, 

and Pressure Components 

--------- --- -----------1-- 

---'" 

AN51/AlAA 5-081A-2006 

Space Systems-Composite OvelWrapped Pressure Vessels (COPVs) 

1-------- - 

----f---------I 

AN51/E5D 520.20-2007 2007 ESD ASSOCiation Standard for the Development of an Electrostatic CEV-S-015, 

Discharge Control Program for Protection of Electncal and Electronic CEV-S-017, 

Parts, Assemblies and EqUipment (Excluding Electncally Initiated CEV-T-025 

Explosive DeVices) 

-_. 1---- 

------- 

AN51/NC5L Z450·1 

Calibration Laboratones and Measunng and Test EqUipment - General 

2.613 

ReqUirements 

A5TME1742 

A5TM E8 

-- 

Standard Practice for Radiographic Examination 

Standard Test Methods of Tension Testing of Metallic Matenals 

ATEC Regulation 385-1 16 Feb. 2005 Army Test and Evaluabon Command (ATEC) Regulation 385-1, ATEC 

Safety Program 

CPIA469 Pr~nc~ples of Sol~d Propellant Development 

CPIA655 

GUidelines for CombusUon Stability Specifications and Venficatlon 

Procedures for Liquid Propellant Rocket Engines 

'---_._------ 

CEV-D-002 

CEV-T-071 

CEV-T-071 

------ 

2.613 

2613 

2.6.10 

-- 


Page 62 of73





Document 



ORO 

REFERENCES 

SOW 

CxP-70065 

Appendix COnly 

Baseline 

Release 

10/11/2007 

Constellation Program Computing System Requirements 

1------- 

CxP-72088 

Revision A 

1------------. 

10 Jul 2007 

-- 

Dept. of the Army 15 Dec 1999 

Pamphlet 385-64 ------- 

DOD 4145.26-M Sept 1997 

r------------- 

FTH 

L.. 

FTO-AFT-FT A-036 

V11 

Aug. 2002 

Rev B 

18 Dec. 2008 

(Agreements 

and 

expectations 

are 

documented 

In FTO-AFT- 

FTA-048 PA- 

1 PyrotechniC 

ReqUirements 

Compliance 

Matnx 

Baseline, 6 

Jan 2009) 

CEVSEMP 

f----- ----------------- 

Department of the Army Phamplet 385-64, Ammunition and 

ExplOSives Safety Standards 

DOD Contractors' Safety Manual for Ammunition and ExplOSives 

-------_._--------------------------- 

Fault Tree Handbook With Aerospace Applications, August 2002, 

version 1.1 (Chapters 1-9) 

----- 

Flight Test Article (FTA) Pyrotechnics Requirements for PA-1 and AA- 

1 

--- 

-- 

----------- 

-------- 

CEV-S-002, 

CEV-S-010 

- ----_._---- 

CEV-D-004 

--- 

-------- 

2.613 

---------- 

3.2 

------ 


Page 63 of73





ID 

Document 

Version/Date 


r- 

ORO 

REFERENCES 

SOW 

IEEElEIA 12207.0-1996 1996 

------ 

IEEE/EIA 12207.1-1997 1997 

ISO 14300-1 15 May 2001 

Industry Implementation of International Standard ISO/IEC 12207: 

1995, Standard for Information Technology - Software life cycle 

processes 

- ---------------- 

Industry Implementation of International Standard ISO/IEC 12207, 

1995, Standard for Information Technology - Software life cycle 

processes - Llfecycle data 

- 

Space Systems - Programme Management - Part 1 Structunng of a 

Program 

CEV-D-002, 

CEV-T-005, 

CEV-T-006, 

CEV-T-04B, 

CEV-T-049, 

CEV-T-050, 

CEV-T-051, 

CEV-T-052, 

CEV-T-053, 

CEV-T-054, 

CEV-T-055, 

CEV-T-056, 

CEV-T-057 

------ 

CEV-D-002, 

CEV-T-005, 

CEV-T-006, 

CEV-T-029, 

CEV-T-035, 

CEV-T-04B, 

CEV-T-049, 

CEV-T-050, 

CEV-T-051, 

CEV-T-052, 

CEV-T-053, 

CEV-T-054, 

CEV-T-055, 

CEV-T-056, 

CEV-T-057 

6.5.2 

._----- ---- 

652 

1.1.(a) 

JPR 1700.1 Rev 1 

July 2002 

JSC Safety and Health Handbook 

CEV-S-OOB 


Page 64 of 73





REFERENCES 

ID 

Document 

Version/Date 


DRD 

SOW 

JSC 17773 

f-- 

JSC20793 

RevC 

Dec 2001 

r----------------- 

KHB 1700.7 

RevC 

19 Aug 1999 

--I-- 

MIL-HDBK-61A 7 Feb 2001 

1-----------1--------_.- 

MIL-P-116 

1--- 

8 Apnl1988 

--1-----_..- 

MIL-S-22473 

RevE 

12 Apnl1983 

1-------.------------- 

MIL-STD-81OF 

RevF 

1 Jan. 2000 

--.-1----------,------------ 

MS20003 5 June 2003 Indicator, Humidity, Card, Three Spot, Impregnated Areas 

1---- 

MSFC-PROC-1831 Jan 1990 The AnalYSIS of Nonvolatile ReSidue Content 

MSFC-PROC-1832 Jan 1990 

MSFC-PROC-404 

MSFC-SPEC-164B 

Rev A 

Oct. 1988 

RevB 

Nov 1994 

MSFC-STD-531 Sept 1978 

-- 

Prepanng Hazard Analyses for JSC Ground Operations 

Crewed Space Vehicle Battery Safety Requirements 

Space Shuttle Payload Ground Safety Handbook 

Military Handbook Configuration Management GUidance 

-- 

Preservation, Methods of 

_.--------_._._---------- 

Sealing, Locking and Retaining Compounds, Single Component 

------ 

DOD Test Method Standard for Environmental Englneenng 

ConSiderations and Laboratory Tests, Section 5 and Part 2 

Sampling and AnalYSIS of Nonvolatile ReSidue Content on Cntlcal 

Surfaces 

-- 

Gases, Drying and Preservation, Cleanliness Level and Inspection 

Specification for Cleanliness of Components for Use In Oxygen, Fuel 

and Pneumatic Systems (and associated Children documents as 

speCified in Attachment J-3, Applicable, Guidance, and Informational 


High Voltage Design Cnteria 

-- 

--- 

CEV-S-008 

CEV-S-001, 

CEV-S-005 

--1---------- 

CEV-M-003 1.3 (a) 

- 

f-------- 

2613 

-- 

2613 

---_. 1------------- 

CEV-T-073 2612, 

61.312, 

62.312 

_._----------------- 

26.13 

------------------- 

CEV-T-073 26.13, 

6.1.3.12, 

62.3.12 

----------------------- 

CEV-T-073 2.6.12 

CEV-T-073 

CEV-T-073 

CEV-T-024 

----------- 

2.612, 

6.1.3.12, 

6.2.3.12 

2.612, 

61312, 

62.312 

28.4 


Page 65 of73





ID 

Document 

Version/Date 


r--- 

DRD 

REFERENCES 

SOW 

NASA-HDBK-700S 13 Mar. 2001 

NASA-STD-8719.7 January 1998 

(applicable only to the 

PA-1 Test Flight) 

NASA-STD-8719.9 May 9, 2002 

(with change 1) 

(applicable on Iy to the 


--------- 

NASA-STD-8719.11 November 19, 

Revision A 2008 



----------- ............. _... - . ---------- 

NASA-STD-8719.17 September 

(applicable only to the 22,2006 


--_.-------- 

NASA-STD-8739.1 6 Aug. 1999 

._. 

NASA-STD-8739.2 31 Aug. 1999 

1--- 

NASA-STD-8739.3 

NASA-STD-8739.4 Feb. 1998 

NASA-STD-8739.S 

L-___ 

Basic-Feb. 

1998 

App.1 

Dynamic Environmental Cnteria 

Facility System Safety Guidebook 

Standard for Lifting Devices and Equipment 

--" ------------------------ 

Safety Standard for Fire Protection 

--- ........................ _.... _........_..._--------------------- ----------- ............................ _........_..._---------------------- ------ 

NASA Requirements for Ground-Based Pressure Vessels and 

Pressunzed Systems (PV/S) 

Workmanship Standards' for Staking and Conformal Coating of 

Printed Wire Boards and Electncal Assemblies 

f-- -- 

Workmanship Standard for Surface Mount Technology 

Soldered Electncal Connections 

Cnmplng, Interconnecting Cables, Harnesses, and Winng 

Fiber Optic Terminations, Cable Assemblies, and Installation 

- 

-- 

CEV-T-015 26.9,6.139. 

6.2.3.9, 6 1 4 9 

CEV-S-001 31 

CEV-S-001 

-------+- 

-----_.- 

CEV-S-001 

------------------- --.--- . -....... . ..... 

CEV-S-001 

--- 

CEV-S-015, 

CEV-S-017 

--- 

CEV-S-015, 

CEV-S-017 

CEV-S-015, 

CEV-S-017 

CEV-S-015, 

CEV-S-017 

CEV-S-015, 

CEV-S-017 

31 

_.--------- 

31 

.. __ ._---_._-- 

31 

- 

. 

I 

I 


Page 66 of 73





Document 



ORO 

REFERENCES 

SOW 

NPD8710.2D Apnl 24,2002 



NPD8710.5C 

September 

(applicable only to the 26,2003 

PA-1 flight test) 

r-- ------- 

NPR 7150.2 27 Sept 2004 

- 27 Sept. 

2007 

-------------- 

NPR8715.1 August 9, 

(applicable only to the 1999 

PA-1 Test Flight) ------------- 

NPR 8715.3A Chapters 

1,2,3,5,7,8, and 9 and 12,2006 

Appendix E 

Septemeber 



r--- 

NSS 1740.12 August 1993 



---- 

OSHA TED 8.4 

PRAPG Version 11 

Aug. 2000 

Range Commanders Sept 1999 



NASA Safety and Health Program Policy 

- 

NASA Safety Policy for Pressure Vessels and Pressunzed Systems 

f---- 

NASA Software Engmeenng Requirements 

----------------------------------- 

NASA Occupational Safety and Health Programs WIth Change 3 

(2/13/06) 

f----------------------------------------- 

NASA General Safety Program Requirements 

------ 

Safety Standard for Explosives, Propellants, and Pyrotechnlques 

-- -- 

Voluntary Protection Programs (VPP) Policies and Procedures 

Manual 

--- 

Probabilistic Risk Assessment Procedures GUide for NASA Managers 

and Practioners, Sections 4 - 14 

Flight Termination Systems Commonality Standard 

CEV-S-001 

CEV-S-001 

CEV-D-002 

CEV-S-001 

---------- 

CEV-S-001 

CEV-S-001 

-- 

CEV-S-008 

CEV-S-010 

CEV-D-002 

3.1 

------- 

3.1 

31 

f--------- 

31 

------ 

31 

I 

I 

I 


Page 67 of73





REFERENCES 

ID 

Document 

VersionlDate 


DRD 

SOW 

Range Commanders June 2002 



RTCAlDO-160D 

-- 

----------f----------- 

SAE-ARP-5412 

-------------f---------- 

SAE-ARP-5413 

f--- 

SAE-ARP-5414 

f--- 

SAE-ARP-5415 

I----.------- 

c----------------------- 

SAE-ARP-5416 

-- 

SAE-ARP-5577 

----------- -------- 

SSP 30240 

RevE 

-- 

SSP 30242 RevG 

WSMR Reg. 385-17 

FAA-HF-STD-001 

Sections 14.1 through 

14.5 


FED-STD-595 


ISO 2631-1 

ISO 3382 


25 July 2003 

25 July 2003 

Common Risk Cntena for National Test Ranges 

I--- 

Environmental Conditions and Test Procedures for Alrbome 

Equipment (Section 22. Lightning Induced Transient Susceptibility 

and Section 23:Llghtnlng Direct Effects) 

-- 

Aircraft Lightning Environment 

--------------------------- 

Certification of Aircraft Electncal/Electronlc Systems for the Indirect 

Effects of Lightning 

-------------_._------ - -------_. __ . __ ._---- 


-----_ 

Users Manual for Certification of Aircraft Electncal/Electronlc Systems 

for the Indirect Effects of Lightning 

.. _---------------------- 

---------- ----- 

Aircraft Lightning Test Methods 

------ ------------------- 

Aircraft Lightning Direct Effects Certification 

-------------------------------- 

Space Station Grounding Requirements 

---- --- 

Space Station CablelWire Design and Control ReqUirements for 

Electromagnetic Compatibility 

---- 

White Sands MIsSile Range Regulations 385-17, Missile Flight Safety 

-- 

~eral AViation Administration Human Factors Design Standard 

Colors Used In Govemment Procurement (12115/89) 

International Standards Organization (ISO) standard 2631-1 :1997 (E) 

"Measurement of the reverberation time of rooms with reference to 

other acoustical parameters" 

CEV-D-002 

CEV-T-025 

-- 

CEV-T-025 

1------------ 

CEV-T-025 

1------------ 

CEV-T-025 

f------ --- - ----. -_._------ 

CEV-T-025 

1--------1------------ - 

CEV-T-025 

1---------1---- ------- 

CEV-T-025 

1-------- -_._---_.- 

CEV-T-025 285 

CEV-T-025 

CEV-D-002 

-------- 

--------- - 

---------- 

1------------ 

2 8.5 

-------- 

------- 


Page 68 of73





REFERENCES 

ID 

Document 

VersionlDate 


DRD 

SOW 


(for guidance onlx) 

Volume I, Man-Systems Integration Standards (MSIS), Revision B, 

1995, Secbon 3.3 3. 

-- 


Page 69 of73





3.0 INFORMATIONAL DOCUMENTS 

Informational documents are listed for information purposes only 

l 

ID Document Informational Document Title 

Version/Date 

CXP-70000 Revision A Constellation Architecture ReqUirements Document (CARD) 

Release 

13 Aug. 2007 

CXP-70007 Revision A Constellation Design Reference MIssions and Operational Concepts 

Change 002 

23 Jui. 2007 

CXP-70008 RevIsion A Constellation Program Master Integration and Venficatlon Plan (MIVP) 

Release 

31 Aug. 2007 

CXP-70009 Baseline Constellation Program Systems Integrated AnalYSIS Plan (SlAP) 

Change 001 

Release 

17 May 2007 

CXP-70012 Baseline Constellation Program Reference Architecture Document (RAD) 

Release 

10 May 2007 

CxP-70013 RevIsion A Constellation Program System Engmeenng Management Plan 

Release, 

30 Nov. 2007 

CXP-70014 Baseline Constellation Program Margin Management Plan (MMP) 

Release 

5 Dec. 2007 

CXP-70061 Baseline Constellation Program Command, Control, Communications, and 

Release Information (C31) Strategic Plan 

19 Dec 2006 

j 

I , 

, 

References 

DRD 

SOW 

10.6.6,103.6 

CEV-T-015 

! 

, 

i 


Page 70 of 73

• _____ H ___ ~_ ,-__ 





CXP-70064 

CXP-70065 

10 Document 

Version/Date 

Baseline 

Release 

5 Sep. 2007 

Baseline 

Release 

11 Oct 2007 

-----r---------- 

! 

, CXP-70067 Baseline 

Release 

24 Jul. 2007 

! CXP-70067-ANX01-01 Baseline 

Release 

I 

24 Jul 2007 

--------_._- --- 

, CXP-70070-ANX05-02 Baseline 

Release 

12 Oct. 2007 

, CXP-70070-ANX08 BaselineSRR 

Release 

TBD 

Draft Matunty 

, 90% as of 

03 Jul. 2007 

i CxP-70072-ANX 01 

Baseline 

I 17 Jan. 2007 

CXP-70074 

Baseline 

Change 001 

16 May 2007 

! CXP-70077 Baseline Draft 

Release 

, 20 Nov. 2007 

Informational Document Title 

Constellation Program Supportability Plan 

Constellation Program Computing Systems ReqUirements Document 

-- -------------- 

Constellation Program Human-Rating Plan 

------ 

Constellation Program Human-Rating Plan, Annex 1 Initial Capability, 

Book 1 SRR Submittal 

1---------------------------- 

Constellation Program, Program Management Plan, Annex 5 

Secunty Management Plan, Book 2. Information Technology (IT) 

Secunty Architecture 

Constellation Program Affordabllity Plan 

Constellation Program Management Systems Plan, Annex 1 Common I CEV-M-001 

Glossary and Acronyms 

Constellation Program Modeling and Simulation Integrated 

Management Implementation Plan 

Constellation Program Architecture Descnption Document 

I 

! 

I 

, 

, 

! 

, 

I 

I 

I 

, 

References 

ORO 

SOW 

2.72 I 

I 

Scope 

2.4 

, 

, 

, 

, 

! 

, 

, 


Page 71 of73

"- 





ID 

Document 

Version/Date 

, CXP-70077-ANX01 Baseline 

Change 003 

Release 

22 Jun 2007 

, CXP-70078 Baseline Draft 

Release 

14 Aug. 2007 

Draft Matunty 

80% 

17 Aug 2007 

i CXP-70085 


i Oct 2006 

CR 160 

Version (not 

released) 

, CXP-70086 Baseline 

Release 

04 Oct 2007 

CXP-70087 

Baselinet 

Release 

22 Aug. 2007 

CXP-70132 


CXP-70133 

CxP-70137 

CXP-70141 

CXP-70144 

Release 

TBD 

Baseline 

Release 

11 Sep.2007 

Baseline 

Release, 

18 Dec 2006 

Baseline 

Release 

23 Aug. 2007 

Baseline 

Release 

17 Jul 2007 


Constellation Program Architecture Description (ADD), Annex l' 

Flight Manifest 

Constellation Program Computmg Systems Architecture Descnptlon 

Document (CSADD) 

Constellation Program Integrated Flight Test Strategy Document 

Constellation Program Software Venfication and Validation Plan 

Constellation Program Reliability, Availability, and Maintainability Plan 

Constellation Program Commonality Plan 

Electncal, ElectroniC, and Electromechanical (EEE) Parts Plan 

Constellation Program Structural Loads Control Plan 

Constellation Program Electromagnetic Environmental Effects (E3) 

Control Plan 

Constellation Program 10nlzmg Radiation Control Plan 

! , 

i 

i 

, 

References 

DRD 

SOW 

CEV-T-027 

28.5,28.6 

2.8.6 

I 

I 

I 

! 

i 


Page 72 of73





ID 

Document 

Version/Date 

CXP-70154 

Baseline 

! Release 

30 AUQ. 2007 

CxP-70158 


! 

Release 

03 Jul 2007 


Constellation Program Contamination Control Plan 

Constellation Program ReqUirements and Interfaces Management 

Plan 

-- 

I 

I 

References 

DRD 

SOW 

--- 


Page 73 of73






GLOSSARY 

May 2009 


Page 1 of 14



Glossary 



Acceptance - The activity perfonned on all production articles generally consistmg of 

inspections, measurements, and tests that demonstrate that each art1Cle was manufactured as 

designed and with acceptable quality and workmanship, perfonns in accordance with specified 

requirements, and is acceptable for delivery. 

Acceptance Review - The Acceptance ReVIew exammes the eqUipment, documentatlOn, and 

data that support verification. An acceptance review is accomplished to assure that equipment (at 

any level of assembly) IS ready to for transfer of ownershIp or custody, or IS ready for mtegration 

into a next-rugher assembly. 

Acceptance Tests - Tests perfonned on flIght hardware and software to confinn equipment 

perfonns as quahfied and IS generally free of latent manufactunng, matenal, or "workmanship" 

defects for delivery of products. For hardware, acceptance testing is typically perfonned at 

operating and non-operating perfonnance and environment limits WIthout intruding into 

quahficatlon margins. For software, acceptance testing ensures the software wi1110ad and 

execute on each serialized hardware platfonn. 

Analysis models - An Analysis Model is a set of one or more engineering analysis tools that 

operate in conjunctlon WIth one another. Analysis models may be capable of automated 

execution or may require user-in-the-loop/interactive operation. The models typically estimate 

system perfonnance accordmg to an engineenng dlsclplme such as aerodynamics or cost. 

However, because a model may involve an engineering analysis tool from more than one 

dlsclplme, the complete model may yield attributes across multlple dlsclplmes. Creatmg such 

multi-tool models IS particularly helpful when multiple dIsciplines within a system strongly 

mteract with each other. The fidehty level of analYSIS model results may be very low (conceptual 

level) or may be very rugh (detailed deSIgn level). 

Certification - A formal document signed by responsible parties (provider, integrator (if 

different), and the Project Office) attestmg to the satisfactory completion of specified 

qualification activities, supported by certification records, and authorizing the use of 

hardware/software for recorded purposes within certified limits. Certification can be 

accomplished at any level of assembly from the component to the integrated system. 

Certification of Flight Readiness - A cOmmltment SIgned by each NASA project manager and 

the respective element contractor stating their readmess for launch. Tills document is signed 

during the Flight Readiness Review (FRR). Prior to FRR, each project manager IS reqUIred to 

assess his readiness for launch by considering vehicle and facility hardware status, problems 

encountered during pre-launch preparation and their resolution, launch constramts, and open 

Items. 

Certification Record - A document or documents Identlfying the certified capability baseline, 

perfonnance limlts and operatlOnal constramts for a hardware/software configuration item. The 

certification record speCIfies the certIfied hmlts that govern usage during its life cycle. The 

certlficatlon record along with the signed certification establishes and illustrates the certified 

baselme. 

Certified Capability Baseline - (a.k.a. As-CertIfied Basehne) The perfonnance characteristics 

and conditions at a given point in time to which specified hardware/software IS certIfied to meet 

progralll reqUirements. The certIfied capablhty baseline is the recognized definition of equipment 


Page 2 of14





and its capabilities, limits, and constraints for the purposes of establishmg flight rules/crew 

procedures, documenting and resolving non-conformances, and sustaining equipment design. 

Qualification margms are not be mtruded upon by production hardware in service and should not 

be reflected by the certified baselme. 

Certified Limits - Parameters (e.g., input parameters such as current, voltage, load, force, 

torque, veloclty, dlsplacement, etc. or enVlronmental condltlons such as vibration, temperature, 

humidity, etc.) that define the bounds of certification of hardware performance or exposure 

during its life cycle. LlmitS may mclude operating time, cycles, or age. Limit conditions may be 

defined for both operational and non-operational hardware states and for individual eqUlpment 

operating modes or system IlliSSlon phases. 

CEV Engineering Models - A CEV Engineering Model is a set of one or more engineering 

analysis tools that operate in conjunction with one another. CEV Engineering Models may be 

capable of automated executlOn or may reqUlre user-m-the-loop/interactive operation. CEV 

Engineering Models typically estimate system performance according to an engineering 

dlsciplme such as aerodynamlCs or cost. However, because a model may mvolve more than one 

dlsclplme engmeenng analysls tool the complete model may Yleld attnbutes across multiple 

disciplines. Creatmg such multl-tool models lS partlCularly helpful when multiple disciplines 

within a system strongly interact wlth each other. The fidelity level of analysis model results may 

be very low (conceptual level) or may be very high (detailed design level). These models mayor 

may not incorporate time as an independent variable. They encompass sensitivity analysis, trade 

space exploration and performance envelope characterization 

CEV System - Includes the spacecraft and all CEV -uruque ground systems needed to support 

standalone and mtegrated operatlOns. 

CEV System Flight Tests - Operating flight tests during the development phase used to qualify 

that the integrated flight vehlcle system (mcludmg the launch vehicle) and ground support 

equipment, as procured and venfied by the acceptance test procedures, conform to the 

Constellatlon program reqUlrements. 

Commercial-Off-The-Shelf (COTS) - Commercially available products that can be purchased 

and integrated with little or no customization 

Component - An aggregate of hardware and/or software that can be characterized by one 

speclfication, lS designed by a single activity to be functionally tested, and is verified as a unlt. 

Computer Software Component (CSC) - A distinct part of a CSC!. A CSC may be further 

decomposed mto other CSC's and CSU's. 

Computer Software Configuration Item (CSCI) - A configuration ltem for computer software 

(l.e., an ldentlfiable, uruque, high-level part of the software that is under configuratlOn 

management). A CSCI may be further decomposed mto CSC's. 

Computer Software Unit (CSU) - An element (i.e., an elementary, basic, or primitive software 

part) speclfied m the design of a CSC that is separately testable. 

Conceptual model - An abstractlOn of the real world that serves as a frame of reference for 

federation development by documentmg slmulation-neutral views of important entities and their 

key actions and interactions. The federation conceptual model descnbes what the federation will 


Page 3 of 14





represent, the assumptions limiting those representations, and other capabilities needed to satisfy 

the user's requirements. Federation conceptual models are bridges between the real world, 

requirements, and design. 

Control Board - The board, panel or forum chartered to have authority over a particular subject 

or Item (ex. Flight Rules Control Board, Crew Procedures Control Board, etc.) 

Crew Activity Scheduling Constraints - Constraints, restrictions or requirements on the 

scheduling of the flight crew. Includes such information such as required amounts of sleep, 

amount crew sleep can be shifted, amount of time for crew meals and exercise, etc. 

Crew Member - Human onboard the spacecraft or space system during a nnssion. 

Crew Operations - The actlVltles performed by the flIght crew willIe in the vehicle or during a 

llliSSlon. A subset of the Flight Operations Execution that begms WIth crew ingress into the CEV 

prior to launch and concludes with the crew egress from the CEV post landing. 

Critical Design Review (CDR) - The CDR discloses the complete system design in full detail, 

ascertains that technical problems and design anomalies have been resolved, and ensures that the 

design maturity justifies the decision to initiate fabrication/manufacturing, mtegratlon, and 

verification of mission hardware and software. 

Depot Operations - The operations performed offline to receive and accept new equipment, to 

perform maintenance, repairs and retests on equipment, or to refurbish and recertify expended 

(end of service life) equipment for reuse. 

Desktop Discrete Event Simulation - A Desktop Discrete Event Simulation varies the inputs to 

Analysis and Part Models in accordance with an anticipated portion of the concept nnsslon. TlIDe 

is the independent variable in a Desktop Discrete Event Simulation. Desktop DIscrete Event 

Simulations incorporate as many AnalYSIS and Part Models as IS needed to predict the total 

performance of a concept during a segment of the anticipated mission. These models are exposed 

to mput sets that represent events as a function oftime. A Desktop Discrete Event Simulation 

predicts the performance of multiple concept entities dunng multiple nnSSIon segments. This type 

of simulation predicts interactions between concept entities and therr enVIronment by 

incorporating the concept elements as well as external elements. 

Design for Manufacturability - The process of proactively designing products to (1) optimize 

all the manufacturing functions: fabrication, assembly, test, procurement, sillppmg, delivery, 

service, and repair, and (2) assure the best cost, quality, reliabIhty, regulatory comphance, safety, 

time-to-market, and customer satisfactIOn. 

Development Tests - Any test that proVIdes data needed to reduce risk, to design hardware or 

software, to define manufacturing processes, to define qualification or acceptance test procedures, 

or to investigate anomalies dIscovered durmg test or operatIOns. 

Engineering Development Unit - Hardware which meets the same functional reqUIrements and 

interfaces/cable connections as the Fhght Umt. The hardware is not required to meet form or fit 

and is not required to utilize flIght rated parts, manufacturing processes, and quality control. 

Electromagnetic Interference (EMI) - What occurs when electromagnetic fields from one 

device interfere WIth the operation of some other deVIce. 


Page 4 of14



Attachment J-S 


Emulator - A device that replicates the command, monitoring, communications, data, and 

electrical power functions of a flight element, for use in interface verification of other flight or 

ground elements. 

Engineering Analysis Tool- An Engineering Analysis Tool is a single, self-contamed computer 

program that produces a smgle set of outputs for a single set of inputs. An Engmeenng Analysis 

Tool makes predictions of system performance or environmental parameters, typically as they 

pertains to a smgle engineering discipline. An Engineering AnalysIs Tool IS the smallest 

executable piece of an engineering computational framework. 

Engineering Simulations - Engmeenng Simulations expose Analysis and Part Models to a set of 

sequential inputs in order to characterize the performance of a concept. These simulations mayor 

may not incorporate time as an independent variable. They encompass senSitivity analysis, trade 

space exploration and performance envelope characterizatIOn. 

Equipment - A genenc term used to refer to hardware at any level-of-assembly from a 

component up through an integrated system. 

Evaluation Factors - Factors by whIch a contractor's proposal will be evaluated to make a 

contract award 

Export Control- U.S. export control laws and regulations, including the InternatIOnal Traffic in 

Arms RegulatIOns (IT AR), and the Export Administration RegulatIOns (EAR) (see FFS 1825) 

Export Licenses - Licenses or other approvals from the Department of State or the Department 

of Commerce related to export of hardware, technical data, or software, or prOVides technical 

assistance to a foreign destination or "foreign person" (see NFS 1852.225-70) 

Extensibility - The potential for a vehicle or system to be adapted or modified to provide 

additional capabilities. 

Facilities - Includes vehicle processmg facilities, mtegration facilities, launch pads, IIDSSlOn 

control centers, launch control centers, control rooms, traimng, test, checkout, and assembly 

facilities with associated data processing and commumcatlOn systems. 

Facility Loading - The level at which a facility is used. For example, if nominal usage is 

defined as 40 hours of simulatIOn support per week and 50 hours are reqUired dunng key periods, 

facility loading would be 125%. This nmnber is used to detennine If a faCIlity is over used and to 

help detenmne If an additional facility is needed to accommodate usage demands. 

Facility Systems - Systems necessary to support the operations of the facility. Examples are 

facility electrical power, water, pnemnatICs, cranes, etc. It does not include ground support 

equipment. 

Federate Application - An application that supports the High Level ArchItecture (HLA) 

interface to a nmtIme infrastructure (RTI) and that is capable of Joining a federation execution. A 

federate application may Jom the same federation execution multiple times or may join multiple 

federation executions. However, each time a federate application joins a federatIOn execution, it is 

creating a new joined federate. 


Page 5 of 14





Federate - An applicatlOn that may be or IS currently coupled with other software applicatlons 

under a FederatlOn Object Model Document Data (FDD) and a runtime infrastructure (RT!). 

Federation - A named set of federate apphcations and a common Federation Object Model that 

are used as a whole to achieve some specific objective. 

Federation Execution - The actual operation, over time, of a set of Jomed federates that are 

interconnected by a runtlme infrastructure (RT!). 

Federation Object Model (FOM) - A specificatlon defining the information exchanged at 

runtIme to achieve a gIven set of federation objectives. This includes object classes, object class 

attributes, mteraction classes, mteraction parameters, and other relevant information. 

Federation Object Model (FOM) Document Data (FDD) - The data and information m an 

FOM document that is used by the Create Federation ExecutIon servIce to initialize a newly 

created federation execution. 

Fit Checks - An engineermg test, where hardware that is to be installed on a future mission, is 

brought together on the ground and structural interfaces are verified by physically mating the 

hardware. 

Flight Controller - A mission operations team member that supports the CEV verucle and flight 

crew anytIme from pre-launch through verucle recovery. A flight controller has a specIfied 

discipline of responsibility and a console from which helshe supports the flIght operations. 

Flight Design & Analysis - The activities performed to desIgn the vehicle flight trajectory, mass 

properties profile, consumables profiles, and other parameters to execute all phases of the ffilSSIon 

without violating any hardware, software, or operational constramts. 

Flight Equivalent Unit - Hardware wruch meets the fit, form and functional requirements as 

defmed in the product specification. The parts, manufactunng processes, and quality control are 

the same as on the Fhght Qualification Units with the exception that they have not been fully 

tested to all environmental acceptance or qualification requirements. 

Flight Operations Execution - Actlvitles associated with the plans, processes, and schedules 

reqUIred for the integrated test and operational flight executlOn. This encompasses real-time 

support for all phases and aspects of mission and crew operatlons beginning with pre-launch 

activities through post-Iandmg egress of the flight crew. 

Flight Operations Products - Documents and analyses used for flight preparation and 

execution. 

Flight Planning - The process of developmg a detailed mission flight plan that satisfies all 

ffilssion requIrements. The requirements are integrated mto a smgle plan for ground and crew 

executIon whIch mcludes flIght design requirements, vehicle operatlOnal constraints (thermal 

conditioning, communications, attitude maneuvers, antenna pointing etc), crew scheduhng 

constraints and payload requirements 

Flight Readiness Review (FRR) - The FRR exanunes tests, demonstrations, analyses, and audIts 

that detennine the system's readiness for a safe and successful launch and for subsequent flIght 

operatIons. It also ensures that all flight and ground hardware, software, personnel, and 

procedures are operationally ready. 


Page 6 of14





Flight Qualification Unit - Hardware which meets the fit, form and functional requirements as 

defmed in the product specification and has been fully tested to all acceptance and qualification 

requirements. The hardware uses the same parts, manufacturing processes, and quality control as 

used on the Fhght Unit. 

Flight Rules - A collection of preplanned decisions to mmimize the amount of real-time 

rationalization required for nominal and off-nominal situations affecting the mission or vehicle 

durmg a flIght. 

Flight Unit - Hardware which meets the fit, form and functional reqUlrements as defined in the 

product specification. The parts, manufacturing processes, and quality control are the same as 

used on the Flight Qualification Units with the exception that they have been fully tested to all 

acceptance requirements, but not all qualification requirements. 

Functional Tests - Operating tests that confirm that a particular hardware or software item 

functions in a way that will permit it to meet allocated requirements. 

Ground Planning - The preparatlOn activItIes for ground processmg and launch operations. 

Ground Processing - The activities performed to prepare the personnel, ground systems and 

flight vehicles during preflight and post-flight operations. 

Ground Systems - The facIhties and facihties systems, ground support equipment hardware and 

software which are required to support integrated test and operational flights. The ground 

systems include those needed for ground operations, and flight operations. 

Ground System Operations - The operation of facilities, facility systems, ground support 

equipment, and associated software when the flight hardware is not present. These operations 

typically include validation of ground systems, preventative mamtenance, and post-launch 

refurbishment operations. Also, mcludes the operatlOn of traming systems, whether for system 

mamtenance and vahdatIon, or for use to certIfY/train FlIght and Ground Operations personnel. 

For operations of Ground Systems when flight hardware is involved, see Ground Operations. 

Ground Tests - Any test performed on system elements or the complete system that does not 

involve flight. Ground testing includes development, functional, integration, qualification, 

acceptance, pre-flIght, and flight-worthiness tests. 

Guidance Document - A docUlllent that the Contractor will use as guidance in developing a 

Data Requirements DocUlllent (DRD) or a subsystem. 

Guidance and Control - The process of directmg the movements of a space vehicle, including 

selection of a flight path and makmg changes in attitude and speed. 

Habitable Volume - Free, pressurized volume, excluding the space required for equipment, 

fixtures, and stowage. 

Habitation - The proviSIon for and management ofthe crew environment (Le., through the use of 

life support systems, thermal control, etc.) in a crewed vehIcle or habItat. 


Page 7 of14





Hardware-in-the-Ioop (HWIL) Tests - Tests conducted with hardware under test, where a 

simulation forms part of the test support equipment. 

High-fidelity, Time-stepped Simulations - H1gh-fidelity, Time-stepped Simulations accomplish 

much the same goals as a Desktop D1screte Event SlmulatlOn, but utilize HLA as a higher fidelity 

1mplementation. The High-fidelity, Time-stepped Simulations slmulate system performance at 

least as fast as real-time. 

Integrated Collaborative Environment (ICE) - The primary means of sharing, reporting, 

collecting, recording and accessmg program information between NASA, CEV Contractor, 

major/cntical subcontractors and authonzed U.S. Government personnel connected w1th the 

Constellatlon Program and Projects. ICE prov1des real-tlme collaboratlve access to a single 

source of management information, product infonnation and technical data. ICE is the principal 

mechanism for mtegratmg a "program" d1g1tal infonnation management enviromnent. 

Integrated Master Schedule (IMS) - The IMS 18 an mtegrated, master schedule containing the 

networked, detailed tasks necessary to support the events, accompilshments, and criteria of the 

IMP. The IMS shall contam all of the contract IMP events, accomplishments, and criteria from 

contract award to completlon of the contract. The IMS shall be a logical network-based schedule 

that correlates to the program WBS, and is vertically and horizontally traceable to the 

cost/schedule reporting instrument used to address variances (such as Cost Performance Report 

(CPR) and 533 Cost Reporting (533M1533Q». 

Integrated Operations - The activities that involve the spacecraft and other flight elements or 

the resources of multlple orgaruzatlOns. 

Integrated Product and Process Development (IPPD) - A management techruque that 

slmultaneously mtegrates all essentlal product development activities through the use of multidisciplinary 

teams to optimize design, manufacturing and supportability processes. It 1S a 

systematic approach to the integrated, concurrent des1gn of products and related processes, 

including manufacturing and support. IPPD is intended to cause designers and developers to 

cons1der all relevant life-cycle elements during the initial and early phases of technology or 

product development 

Integration Tests - Tests conducted to venfy functional performance has been achieved after 

hardware and/or software items are assembled and mterfaces activated. 

Item Tests - Tests at the component or 1tem level (1.e., the lowest element of the system that is 

serialized or otherwise tracked). 

Joined Federate - A member of a federatlOn execution, actualized by a federate application 

invoking the Join Federation Execution service as prescnbed m IEEE Std 1516.1-2000. 

Large-scale System Simulations - A Large-scale System SlmulatlOn predlcts the performance 

of multiple concept entities during multiple misslOn segments. Tills type of simulation predicts 

interactions between concept entities and their enviromnent by incorporating the concept 

elements as well as external elements. 

Launch Operations - The final activities to prepare the ground systems and the integrated 

vehicle for launch, and the launch of the integrated stack. 


Page 8 of14



Life Cycle Cost - See J-5 AppendIx 1. 



Logistics Support - An approach that enables disciplined, unified and iterative management of 

support consideratlOns mto system and eqUIpment deSIgn. Logistics support includes 

development of support requirements that are related to readiness objectives, to design, and to 

each other. Requirements in tum drive acqulSltlOn of required support; logIstics support is then 

employed during the operational phase. 

Mass Properties - The dIstnbution of mass within the component, subsystem, system, or 

vehicle, which can change throughout the nussion due to consumables usage and the transfer of 

hardware. The vehicle mass properties are tracked and managed to aVOld adverse impacts to the 

vehlCle's control characteristics. 

Micrometeoroid and Orbital Debris (MMOD) Penetration - MMOD damage causing loss of 

a critical function or string of functional redundancy that would lead to loss of vemcle or would 

lead to loss of crew. 

Mission Control Centers - The central command and control facIl1ty for MISSIon Operations. 

Mission Operations - The actiVlties performed to plan, direct, manage, and execute the flIght by 

the mission control management, flight controllers, and support orgamzatlOns A subset of the 

Flight Operations Execution that begins at liftoff and ends WIth crew egress after landing. 

Mission Segment Simulation - A Mission Segment Simulation vanes the inputs to Analysis and 

Part Models in accordance with an anticipated portion of the concept mission. Time is the 

mdependent variable m a Mission Segment Simulation. Mission Segment SImulations 

incorporate as many Analysis and Part Models as is needed to predIct the total performance of a 

concept during a segment of the anticipated mission. These models are exposed to input sets that 

represent events as a function of time. 

Mockups - A training system or other faCll1ty WIth a physlCal similarity to flight or ground 

systems hardware for the purpose of training, engineering evaluations, or other studIes. 

Module - A self-contamed unIt of a spacecraft that performs a specific task or class oftasks m 

support of the major function of the craft (e.g., SM, CM, LAS). 

Nominal Operational Scenarios - Cases that descnbe SItuations that are within the planned 

capabIlities of the vehicle (example, CEV docking with the lander across a range of lunar 

altitudes.) 

Non-operating Environment Tests - Tests in environments (shock, vibration, acoustic, and 

temperature) willie the hardware IS not in an operating mode (1.e., WIthout power, mechanical, or 

propulsion systems in operation). Environmental tests on non-operational hardware (Le., WIthout 

power, mechamcal, or propulsion systems in operatlOn) that IS outSIde the normal operating 

environment of the subject hardware (I.e. temperature extremes experienced by bertmng system 

during Earth Orbit to Destmation Vicinity Phase). 

Non Operational Environment - The environment (ground transportatlOn, etc.) in which the 

vehicle wlil be exposed to when it is not intended to be operatlOnal. 


Page 9 of14





Off-Nominal Operations Scenarios - Cases that describe situations that are outside the planned 

operations (example, inability to dock lander to CEV, resulting in a need to perfonn an EVA to 

re-enter the CEV). 

Open System Architecture - A system with common interfaces that facilitate products from 

multiple vendors to operate on. 

Operating Conditions & Environment Tests - Tests of the flIght and support assemblies in 

each operating mode and in the maXImum (worst case) predicted operating and environmental 

conditions. 

Operational Constraint - A limit on the operatIOn of equipment that avoids hazards, precludes 

damage or exceSSIve degradation, and observes the certIfied limits of the equipment. 

Operational Environment - The environment (thennal, pressure, radIation, etc.) in whIch the 

vehicle is intended to be operated 

Operational Flights - The actIVIty phase occurring after the design, development, test, transition 

and deployment of the ExploratIon System to Space Operations MISSIon Directorate for the 

purposes of space exploratIOn and pursuing the Vision. 

Operational Interfaces - Fonnal organizational and personnel interactions reqUIred to 

Implement contract responsibilities and the necessary interfaces to fully mtegrate and coordinate 

activities internal and external to the CEV program. 

Operations - The processes, plans, system requIrements, procedures, and work to be perfonned 

associated With the preparation, launch and flIght execution, and recovery ofthe CEV. The scope 

of Operations concern the activities with eqUipment once it has been delivered to the government 

and are in support of the integrated test and operational flights. ThIs IS applicable to all types of 

operations. 

Part Models - A Part Model descnbes a function-perfornnng component or system. In ItS most 

fundamental fonn, a part model describes the geometry of the part, component or system in 

question. Early in the design process, a part model may be a crudely defined vehicle sub-system. 

As concept development progresses, fidehty IS added regarding the characteristics and 

perfonnance of the part. The difference between a Part Model and an Analysis Model is that a 

Part Model tracks all discipline parameters that are relevant to a particular part/component, while 

an Analysis Model can be executed to detennine the perfonnance of several components for a 

particular discipline or group of disciplines. 

Part Task Trainers - Facilities and equipment that are highly specialized and serve to train a 

speCIfic subset of a larger system. 

Past Performance - The initiative to gather (and use in future source selection) factual 

infomtatlOn about the perfonnance of a contractor against the perfonnance reqUirements in the 

contract. 

Post Landing Operations - The activities required to plan, deploy, prepare the landing sites and 

landing aids for the flight vehicle, aid crew egress and transport, perfonn medical/emergency 

operations, safe flight hardware, and transport/retrieve appropriate parts of the flight system. 


Page 10 of 14




Preflight Operations - All the activities perfonned prior to liftoff of the vehicle. Includes 

ground processing, training, flight deSign, analysis, planning and launch operations. 

Preliminary Design Review (PDR) - The PDR demonstrates that the preliminary design meets 

all system requirements With acceptable risk. It shows that the correct design option has been 

selected, interfaces identified, and verifications methods have been satisfactorily described. It 

also establishes the basis for proceeding With detailed design. 

Probabilistic Risk Assessment - A set of methodologies employed to deterrnme quantitative 

probability a given end state or states (e.g., Loss of Mission, Loss of Crew) Will occur 

Probabilistic Risk Assessment results can be used to develop or validate Fault Trees and Failure 

Modes analysis. They also can be used as a tool for making deSign and logistics decisions. 

Procedure - Set of detailed mstructIons used by the crew, ground operations and flight 

operations personnel to assess status, reconfigure, operate, trouble-shoot, safe, and maintain CEV 

systems under both nominal and off-nominal conditions. The procedures may also be executed 

by spacecraft executor software to fulfill specific tasks. 

Process Integrity Metrics - A measurement of how well a process IS meeting its intended goal. 

Qualification - The activity that proves deSign, manufacturing, and assembly have resulted in 

hardware/software that confonns to deSign and perfonnance reqUirements during or after 

exposure to speCific envIronmental conditions. The qualification activity consists of various tests, 

analyses, demonstratIOns, and mspections as required to verify confonnance of deSign to 

specified requirements. 

Qualification Margin - An increase in the tested, demonstrated, or analyzed conditions beyond 

the most severe occurrence expected during the service life (including acceptance testmg) in 

order to show suffiCient robustness in the deSign. A qualification margin may be an increase in 

operating or non-operatmg level, range, cycles or duration of exposure to environmental 

conditions (such as temperature or vibration) or parameters (such as voltage, current, load, or 

torque). Qualification margm requirements are intended to achieve robustness for: 

• Tolerance of the unit to unit differences m flight articles and the qualification article 

due to allowed or expected variations in parts, manufacturing tolerances, material 

properties, and manufacturing processes. 

• Immunity to degradation such as fatigue, wear, loss of properties, or functionality 

after experiencing a speCified maximum amount of acceptance testing and 

operational usage. 

Qualification Tests - Fonnal tests conducted with defined qualification margin as part of the 

certification program to qualIfy a design, rnanufacturmg process, and acceptance testing program 

to produce eqUipment able to accomplish the full range of perfonnance requirements in all 

predicted operating and non-operatmg service life environments (mcluding acceptance testing). 

Real-Time Support - Level of support that has the personnel, tools, and locale necessary to 

provide immediate response. 

Risk - The uncertainty of attaining a perfonnance outcome or result and IS the function of the 

probability and the consequence of failing to attain the perfonnance outcome or result. 


Page 11 of 14





Risk Management (RM) - The processes for identlfymg, assessing, mitigating, and trackmg 

risks. 

Runtime Infrastructure (RTI) - The software that provides common interface servIces during a 

HIgh Level ArchItecture (HLA) federation execution for synchronization and data exchange. 

Safety-Critical Software - Software is safety-critical If It meets at least one of the followmg 

criteria: 

1. Resides in a safety-critical system (as detenmned by a hazard analysis AND at least one ofthe 

followmg. 

a. Causes or contributes to a hazard. 

b. Provides control or IllitlgatlOn for hazards. 

c. Controls safety-critical functions. 

d. Processes safety-cntical commands or data. 

e. Detects and reports, or takes corrective action, If system reaches hazardous state. 

f. Mitlgates damage if a hazard occurs. 

g. ReSIdes on the same system (processor) as safety-critical software. 

2. Processes data or analyzes trends that lead directly to safety declSlons (e.g., determining when 

to turn power off to a wmd tunnel to prevent system destruction.) 

3. Provides full or partIal venficatlOn or validation of safety-cntlcal systems, including hardware 

or software subsystems. 

Service Life - The life of an equipment Item startmg at the completion of fabncation and 

continuing through all levels of acceptance testing, handling, transportatlOn, storage, pre-launch 

processmg, all phases of flight (launch, on-orbIt, descent, landing), rework/refurbishment, retest, 

and reuse as required or specified. 

Simulator - A traimng system or facility that generates conditions approxlmatmg actual or 

operatlonal conditions to a level commensurate with the function it IS supporting (e.g. training, 

testmg, engineering evaluation). 

Software - Computer programs, procedures, rules, and associated documentation and data 

pertaining to the development and operation of a computer system. Software includes programs 

and operatIonal data. This also includes Commercial-Off-The-Shelf, Government-Off-The-Shelf, 

Mlhtary-Off-The-Shelf, reuse, auto code generated, finnware, and open source software 

components 

Software Requirements Review (SwRR) - A reqmrements review that decomposes the 

subsystem requirements into lower level flight and ground software reqmrements, which are 

documented in a senes of Software RequITements Specifications (SRSs). 

Standalone Operations - The activities that mvolve a single flight element. 

Statement of Work (SOW) - A document that expresses the tasks to be perfonned by the 

contractor. 

Subsystem - A system that is part of some larger system. A spacecraft is fITst broken up into 

modules (if needed), then mto subsystems, and finally mto components 


Page 12 of 14





Sustaining Engineering - Long tenn design engineenng responsibilities and support associated 

with Operational flights. 

System - A set or arrangement of interdependent elements/segments that are used to accomplish 

nusslon objective(s). Exploration systems are Crew Transportation, Cargo Delivery, In-Space 

Support, Destination Surface, Robotic Precursor System, and Ground Support. These Systems 

comprise the ExploratlOn System of Systems. 

System Architecture Model - The combination and coupling of Analysis Model and Part Model 

results is one fonn of a System Architecture Model. It not only defines the complete physical and 

functional configuration, but it also defines composlte perfonnance and charactenstics of the 

system or architecture. A System Architecture Model contains analysis models that are used to 

assess perfonnance parameters. It can be thought of as everything that can be driven, visualized 

and observed in a large-scale system simulation. A second fonn of a System Architecture Model 

is a high-level, functional descnptlon of a system that may at a later date consist of Part and 

Analysis Models. System Architecture Models represents vehicle function, structure and behavior 

m the fonn of function and component hierarcrues, functlonal allocations, process flow diagrams 

and dynamic models. 

System Definition Review (SDR) - The SDR examines the proposed system arcrutecture/design 

and the flowdown to all functional elements of the system. 

System Engineering & Integration (SE&I) - The technical and management efforts for 

directing and controlling the mtegrated engineering effort for the System. 

System Engineering, Integration & Test (SEI&T) - The design, development, integration, and 

test of large and complex systems, where a system is understood to be an assembly or 

combmation of interrelated elements or parts working together toward a common obj ective. 

Systems Management Software - The subset of flight software performing integrated health 

management (mcludmg autOlnated vehicle-level fault detection, isolation and recovery, 

troubleshootmg, and prognostication), onboard resource management (including management of 

redundancy, power, data, thennal, and other finite items), and autonomous operations support. 

These disciplines provide the coordmatlOn of intersystem interactlons, management of 

mtersystem dependencies, monitonng of critical resources, a cautlon and warning data synthesis 

and identification capability, sequencing between distinct operatlOnal phases or system modes, 

and asslstmg the vehicle/crew in overcoming anomahes. 

Technical Performance Parameters (TPP) - Techmcal Perfonnance Parameters are identified 

by the CEV Program Manager for monitoring during the deslgn and development, such as 

margins for Mass Propertles, Power Allocation, Volume, CPU Utilization, 

BandwidthIThroughput. 

Technology Readiness Level (TRL) - A systematic metnc/measurement system that supports 

assessments of the lllaturity of a particular technology and the conslstent comparison of maturlty 

between different types of technology. 

TRL 1: Basic principles observed and reported 

TRL 2: Technology concept and/or application fonnulated 

TRL 3: Analytical and experimental critical functlOn and/or characteristic proof-of-concept 

TRL 4: Component and/or breadboard vahdatlOn in laboratory enVlronment 


Page 13 of14





TRL 5: Component and/or breadboard validation in relevant environment 

TRL 6: System/subsystem model or prototype demonstration m a relevant environment (ground 

or space) 

TRL 7: System prototype demonstration in a space environment 

TRL 8: Actual system completed and "flight qualified" through test and demonstration (ground or 

space) 

TRL 9: Actual system "flight proven" through successful mission operations 

Test-qualified Hardware/Software - Hardware/Software used to support testing of other 

hardware/software that is of sufficient fidelity and validation to conduct a valid test of the 

hardware/software bemg tested. 

Timeline - A sequential series of events that descnbe the CEV operatIOn. A timeline can 

represent the vehicles IlliSSlOn at different levels of detail (ex. overview, SUlllillarY and detailed 

timelines). The tlmelme mcludes mfonnation on trajectory events and scheduled crew activities 

as well as assOCiated ground activities. 

Training Systems - The hardware, software, and facilities reqUired to educate, test, certify, 

qualify, standboard, mamtam proficiency, and otherwise prepare the crew, ground and flight 

operations personnel for successful executIOn of Exploration missions. 

Transition - The handover of the CEV's operation, hardware and software responsibilities from 

the combined developing contractor team and NASA ExploratIOn Space Mission Directorate to 

the NASA Space Operations Mission Directorate's operatIOns, engmeering and management 

teams. 

Unit Testing - The testing of individual hardware components or software components (CSUs) 

to ensure that they operate correctly. 

Validation I - Assessment of a set of requirements demonstrating that the requrrements are 

feasible withm allowable means (cost/schedule/technical capability), are verifiable, and if fully 

met, will produce a product that accomplishes the intended objectives. 

Validation 2 - Proof that the product accomplishes the mtended purpose. May be determined by a 

combination of test, analysis, and demonstration. 

Vehicle MotionIFlight Simulations - A vehicle motion simulation couples a large-scale 

simulation to physical hardware. Tills typically consists of vehicle and facility interiors with flight 

controls, access points and sensory cues. These simulations are used to characterize the 

interaction between human operators and the concept in question. 

Verification - Proof of compliance With speCifications. May be detennmed by a combination of 

test, analysis, demonstration, and mspectton. 


Page 14 of14






AWARD FEE EVALUATION PLAN 

CREW EXPLORATION VEHICLE 

Contract NNJ06TA25C 

Schedule A 

May 2009 

Note: All period of performance and milestone provisional and interim evaluations 

are subject to a final award fee determination to be made by the Government 

after completion of all interim evaluations for all milestones and periods of 

performance. 


Page 1 of 12





I. INTRODUCTION 

In accordance with the provisions of the Federal AcqUisition Regulation (FAR), and NASA and JSC policies, 

a performance evaluation procedure IS hereby established for determination of award fees payable under 

this contract. The award fee IS designed to provide economic motivation for the Contractor to provide 

timely, high quality outputs that exceed the minimum reqUirements of the contract. The intent of this plan IS 

to set up procedures for evaluation of Contractor performance using eXisting data and systems to the 

maximum extent while imposing minimum administrative burden on the Government and Contractor. The 

payment of any award fee is contingent upon compliance with contractual reqUirements and performance to 

the degree speCified below 

This contract IS a hybrtd contract consisting of three schedules, Schedules A, S, and C. Award fee 

evaluation for Schedules A and C are covered by attachments J-7 and J-17, respectively Schedule S 

contains separate Incentives speCifiC to that contract schedule, and IS not subject to award fee provisions. 

Effective with Contract Modification 65, the available Award Fee for Schedule A has been divided Into two 

types of Award Fee pools The first pool is the Period of Performance Award Fee ThiS pool was 

established utilizing 36 4% of the available Award Fee for Schedule A and has set periods of performance 

for each Award Fee pertod In order to faCilitate the evaluation and billing process outlined in this attachment 

and Section G, Clause G.3, respectively The second pool IS the Performance Milestone Award Fee ThiS 

pool was established utilizing 63.6% of the available Award Fee for Schedule A Each Performance 

Milestone has a completion date associated with it as outlined in Enclosure II, Table B 

The Contractor's Intertm performance under Schedule A will be evaluated by NASA at the expiration of 

each pertod specified In Enclosure II, Table A, Pertod of Performance Fee Dlstrtbutlon The evaluation to 

be performed by NASA Will be based on NASA's assessment of the Contractor's accomplishment of the 

various areas of work covered by the Statement of Work, In accordance with the factors, welghtlngs, 

procedures, and other proVISions set forth below 

The amount of available Award Fee in each period is subject to eqUitable adjustments arising from changes 

or other contract modifications as descrtbed In Enclosure III. The amount of the Award Fee to be paid is 

determined by the Government's evaluation of the Contractor's performance in terms of the crtterta stated in 

the contract ThiS determination and the methodology for determining the Award Fee are unilateral 

decisions made solely at the discretion of the Government The Government may unilaterally change any 

areas of thiS plan not otherwise reqUIring mutual agreement under the contract Such changes will be 

made prtor to the beginning of an evaluation pertod to which the changes apply by timely notice to the 

Contractor in writing. The Contractor Will be Informed of any changes to the evaluation criteria or the 

weightlngs prtor to the affected Award Fee period. 

Each award fee evaluation, with the exception of the last evaluation, will be an Intertm evaluation and the 

corresponding fee payment IS provisional only All interim evaluations and provisional fee payments Will be 

superseded by the final evaluatton and fee determination for Schedule A 


Page 2 of12





II. 

ORGANIZATIONAL STRUCTURE 

A. Performance Evaluation Board Integration Team (PEB-IT) 

The PEB-IT will be composed of selected NASA technical and administrative personnel and headed by the 

Contracting Officer's Technical Representative (COTR). The COTR will be the focal pOint for the 

accumulation and development of Award Fee evaluation reports, reviews, and presentations, as well as 

discussions with Contractor management on Award Fee matters The PEB-IT will evaluate the Contractor's 

performance as related to the criteria listed In paragraph III below 

The PEB-IT will furnish the Contractor performance evaluations at a minimum at the midpoint of the interim 

evaluation period. The purpose of these communications is to discuss any speCifiC areas where the 

Contractor has excelled and areas where future improvement IS necessary Routine and timely feedback 

will be provided to the contractor through the Technical Management Representatives (TMR). The routine 

feedback will also be reflected in the midpOint and interim evaluations The Government's failure to prOVide 

interim feedback to the contractor dUring the period shall not preclude the Government from considering 

any defiCiency In the contractor's performance In connection With the performance determination 

The PEB-IT Will prepare an evaluation report for review by the PEB for each evaluation period. This report 

will Include a recommendation to the PEB as to the adjective rating and numerical score (Enclosure 1) to be 

assigned for the Contractor's performance for the perIOd evaluated. 

B. Performance Evaluation Board (PEB) 

The Performance Evaluation Board (PEB) Will be comprised of selected technical and administrative 

personnel of NASA The PEB will assess the Contractor's performance after each evaluation period to 

determine whether, and to what extent, the Contractor's performance during the evaluation period 

(milestone) IS deserving of the interim payment of Award Fee The PEB, at the end of each evaluation 

period, will conSider the PEB-IT report (PEBR) and prepare a summary of the evaluations for review by the 

Fee Determination OffiCial (FDO) This summary Will Include a recommendation to the FDO as to the 

adjective rating and numerical score to be assigned for the Contractor's performance In the preceding 

evaluation period. 

C. NASA Constellation Program Manager (PM) 

After receiving any comments from the Contractor on the evaluation conducted by the PEB, and prior to 

presentation of evaluation results to the FDO, the PEB chairperson will brief the PM on the evaluation 

results. The PM will ensure that due consideration has been given to all programmatic aspects of the 

Contractor's performance, Including areas such as consistency In program assessment of contract 

performance across all Constellation contracts The PM may reqUire the PEB to reconvene to conSider 

additional programmatic Information If reconvened, the PEB Will determine that reviSions to the PEB report 

either are or are not necessary based upon the PEB's analYSIS of the additional information The PEB 

report Will then either be revised or It Will be noted that the PEB did reconvene and the programmatic advice 

received by the PM, along With the PEB dispOSItion of the additional information Will be provided to the 

FDO 

D. Fee Determination Official 

A senior NASA official will be the FDO After considering available pertinent information and 

recommendations, the FDO will make an interim performance determination for each period in accordance 

with the prOVIsions of thiS Attachment J-7 and G 3 "Award Fee for End Item contracts" per the applicable 

schedule The same process will be followed for the final performance evaluation period except the 

determination will be final as defined by the clause 


Page 3 of 12





The FDO will consider the recommendation of the PES, PES-IT Report, information proVided by the 

Contractor, If any, and any other pertinent information in determining the performance score The FDO's 

determination of the score will be stated In a written Award Fee Determination and Will be provided to the 

Contractor by the Contracting Officer within 45 calendar days after the end of the evaluation period. 

III. 

EVALUATION PROCEDURES 

Award Fee Periods 

Schedule "A" DDT&E 

NASA will evaluate this contract schedule in accordance with the clause NFS 1852216-77, Award Fee for 

End Item Contracts Each award fee period Will be based on Enclosure II Table A periods of performance. 

Each interim award fee period and provIsional payment IS based on the period of performance of the 

evaluation period and the Contractor's successful completion of the mllestone(s) during the evaluation 

period as Identified In Enclosure II, Table B The award fee distribution tables contained In Enclosure II, 

Period of Performance Fee Distribution (Table A) and Performance Milestones (Table B), provide the 

Award Fee periods of performance and list of performance milestones along with the available provIsional 

and interim fee for each period of performance and milestone. The award fee distribution table contained in 

Enclosure II, Table C, Indefinite Delivery Indefinite Quantity (IDIQ) Delivery Orders, provides a list of Issued 

delivery orders and the maximum award fee available. In accordance with NFS 1852.216-77, all award fee 

evaluations, with the exception of the last evaluation, Will be interim evaluations. 

Objective and Subjective Criteria 

No later than 30 calendar days prior to the start of each Interim Award Fee evaluation period, the Contractor 

may submit to the Contracting Officer recommended objective performance metrics, weightings, and Areas 

of EmphaSIS (AOE) for conSideration by NASA to be used for the ensuing evaluation period 

NASA will establish performance metrics and AOE for each evaluation period and communicate these to 

the Contractor at least 15 calendar days prior to the start of each evaluation period NASA may unilaterally 

change the welghtings of the cntena from penod to penod However, cost control Will be weighted at no 

less than 25 percent. 

Contractor Self Evaluation and Submissions 

The Contractor shall furnish a self-evaluation for each evaluation penod The self-evaluation must be 

received by the Contracting Officer 5-working days prior to the end of the penod and shall be limited to no 

more than 20 pages At the PEB meeting, the Contractor may proVide a self-evaluation presentation (a 

copy of which shall be prOVided to the PES) not to exceed 30 minutes in length. 

The Contractor Will be furnished a copy of the PES's findings, conclUSions, and fee recommendation The 

Contractor Will be afforded the opportunity to submit for conSideration of the FDO: (a) proposed evaluations 

or conclUSions or (b) exceptions to the evaluations, conclusions, or fee recommendations of the PEB; and 

(c) supporting reasons for such exceptions or proposed evaluations or conclusions The Contractor's 

submiSSions must be made In Writing and must be submitted through the Contracting Officer to the FDO 

within 5-working days from the date of the Contractor's receipt of the PES findings If the Contractor does 

not proVide additional Information to the Contracting Officer Within the time stated above NASA will 

conclude that the Contractor concurs With the evaluation and recommended score. 

In the event the FDO has not received a submiSSion from the Contractor, the performance determination 

will not be executed until expiration of the 5-working day period preSCribed above for Contractor 

submiSSion The Contractor may waive the 5-worklng day waiting period by providing a written statement 

that no response Will be submitted 


Page 4 of12





The Contractor shall submit to the Contracting Officer a Corrective Action Plan (CAP) for any weaknesses 

or falling objective performance areas Identified by NASA as part of the evaluation. The CAP should 

Include a descnption of the non-conformance, determination of the root cause of the non-conformance, 

action required to correct the weakness and prevent recurrences, and the schedule for completion of the 

action. The CAP shall be submitted to the Contracting Officer within 30 calendar days after receipt of the 

each interim performance determination for the evaluation period. Corrective Actions will be closed by 

concurrence from the Contracting Officer and the COTR Failure to submit a CAP within the timeframe 

stated above will result In a weakness In the next evaluation period. 

Interim Feedback to the Contractor 

During the course of a periodic evaluation period, the PEB-IT will communicate with the evaluation monitors 

and others as deemed appropnate to ascertain whether there are any areas of the contractor's performance In 

which significant improvement is required. The PEB-IT will provide prompt written notice to the contractor of 

any such significant areas known to him, and will also highlight other areas of Government concern For each 

such letter Issued, the contractor IS reqUired to respond In a timely manner, setting forth plans for Increasing 

effectiveness in the areas addressed or explaining why It IS not feaSible to do so 

The need for such interim feedback will vary according to the circumstances Involved, such as the length of 

the evaluation penod, the contractor's performance In previous periods, the nature of the work being done 

during the period, etc Hence, the Government's failure to prOVide interim feedback to the contractor during 

the period shall not preclude the Government from consldenng any defiCiency In the contractor's performance 

In connection with the determination of the amount of fee to be awarded to the contractor. TYPically, the 

Government will prOVide feedback to the contractor at every 3 months during the evaluation penod At a 

minimUm, the Government Will proVide feedback at the midpoint of the evaluation penod. 

IV. 

EVALUATION CRITERIA AND WEIGHTINGS 

NASA will use the follOWing subjective factors as a baSIS for arriving at the interim and final award fee 

score: 

Award Fee Evaluation Cntena 

Technical 

Program Management 

Cost 

Small BUSiness/Smail Disadvantaged BUSiness 

Subcontracting Goals 

Weight 

45% 

20% 

25% 

10% 

A. Technical (45%) 

ThiS factor will Include an evaluation of the Contractor's performance In all areas of Technical 

performance, both Intenm and final This includes. 

I Safety and mission assurance, 

II ReqUirements definition and flow down, 

iii. Risk management, 

IV Margin management, and 

v. Innovation. (Innovation, both here and In Program Management, is defined as innovations that 

reduce cost, benefit schedule both from a current and future perspective, or result In Improved 

design, coordination, or communication without adverse effects on performance, cost, or schedule) 

VI Life Cycle Cost 

B. Program Management (20%) 

This factor will Include an evaluation of the Contractor's performance in all areas of Program 

Management performance, both Intenm and final ThiS Includes schedule management, subcontract 

management, responsiveness, Innovation, life cycle cost management, and corporate commitment to 


Page 5 of12





capital Investments and personnel (Corporate commitment to personnel Includes the quantity and 

quality of personnel assigned to the CEV Phase 2 contract. Quantity includes ramp-up and retention of 

qualified personnel at adequate levels to meet schedule, cost and performance objectives Quality of 

personnel Will be evaluated on the Contractor's success In maintaining and replacing key personnel 

Within the CEV Phase 2 contract) 

C. Cost Management (25%) 

This factor will include an evaluation of the Contractor's cost performance under the contract. Earned 

Value Management System data, cost performance reports and other cost data sources will be used in 

the Cost Management assessment for this factor. Cost performance Will be assessed by evaluating the 

cost expended on the actual work performed during the period being evaluated, Including quantitative 

assessment of the award fee period cumulative Cost Performance Index (CPI) In addition, a 

qualitative assessment of appropriate earned value variances, cost implications of the Schedule 

Performance Index (SPI), and other period-specific cost management trend data will be considered. 

D. Small Business/Small Disadvantaged Business Subcontracting Goals (10%) 

The Contractor's performance will be evaluated against the contract goals for small/small 

disadvantaged business subcontracting 

V. SCORING 

The percentage of award fee to be paid for a period is equal to the numerical score assigned. In 

accordance with the Section G clause for award fee, no award fee Will be paid when Contractor 

performance IS determined to be Poor/Unsatisfactory. 

An overall performance evaluation and fee determination of zero shall be made for any evaluation period 

when there is a major breach of safety or security as defined In NFS 1852 223-75, Major Breach of Safety 

or Security. 

VI. 

LIST OF ENCLOSURES 

Enclosure I. 

Enclosure II. 

Enclosure III 

Numencal Ranges and Adjective Definitions 

Award Fee Periods, Milestones and Award Fee Available for Payment and Earned 

Future Contract Changes - Award Fee Distribution Methodology 


Page 6 of 12





Numerical Ranges and Adjective Definitions 

Enclosure I 

This enclosure sets forth the adjective ratings, definitions, and associated numerical ranges to be used to 

define the various levels of performance under the contract 

ADJECTIVE RATING 

RANGE OF 

POINTS 

DESCRIPTION 

Excellent 100 - 91 

Of exceptional merit, exemplary 

performance In a timely, efficient and 

economical manner; very minor (if any) 

deficiencies with no adverse effect on 

overall performance. 

Very Good 90 - 81 

Very effective performance, fully 

responsive to contract, contract 

reqUirements accomplished In a timely, 

efficient and economical manner for the 

most part, only minor deficiencies 

Good 80 -71 

Effective performance; fully responsive to 

contract reqUirements; reportable 

defiCienCies, but with little identifiable 

effect on overall performance. 

Satisfactory 70 - 61 

Meets or slightly exceeds minimum 

acceptable standards; adequate results; 

reportable defiCienCies with identifiable, 

but not substantial, effects on overall 

performance 

Poor/Unsatisfactory 60 - 0 

Does not meet minimum acceptable 

standards In one or more areas, remedial 

action reqUired in one or more areas; 

deficiencies in one or more areas which 

adversely affect overall performance. 


Page 7 of12



Attaclunent J-7 


Enclosure" 

Award Fee Periods. Milestones and Award Fee Available for Payment and Earned 

Provided within this Enclosure are the Tables A, Band C, which reflect, respectively, Period of Performance 

Award Fee Pool, Performance Milestone Award Fee Pool, and 10lQ Award Fee Available. The Award Fee 

periods and milestones, Award Fee available for payment and the Interim Award Fee earned. 

All period of performance and milestone provisional and interim evaluations are subject to a final award fee 

determination to be made by the Government after completion of all interim evaluations for all milestones 

and periods of performance. 

Table A: Period of Performance Award Fee Pool Fee Distribution 

Period of Performance Award Fee periods have been be established and reflected in Table A. These 

periods will remain set as the Award Fee periods to be used for interim award fee evaluations. These 

periods will be used as measurements of performance in accordance with the Award Fee for End Item 

Contracts. 

Available Period 

Award Fee Evaluation Period of Performance Available IDIQ Total Available Interim Earned 

Period Schedule Award Fee Award Fee"" Award Fee Award Fee 

1" 

2 9/1/07 - 4/30/09 

3 5/1109 - 4/30/10 

4 5/1/10 - 4/30/11 

b~ 

5 5/1111 - 4/30/12 

6 5/1112 - 4/30/13 

7 5/1113 - 4/30/14 

8 5/1114 -12/31/14 

Total 

• At the time of Award Fee Period 1 evaluation, all Award Fee was based on Performance Milestones; 

therefore, all Period 1 Award Fee is reflected in Table B of this Enclosure. 

··Starting with Award Fee Period 2, 10lQ Fee is Included in Table A, Period of Performance Fee 

Determination. 

Table B: Performance Milestones Award Fee Pool 

Performance Milestones have been be established prior to contract award. These milestones will be used 

as measurements of performance in accordance with the Award Fee for End Item Contracts. 

For purposes of making provisional milestone award fee payments for completed milestones, this 

agreement recognizes milestone dates for each mission milestone are tied to the final hardware 00250 

dates, With the exception of PA-1, which has two milestones tied to specific hardware 00250 dates. 

Although provisional award fee payments will be made for mission milestones after the 00250 dates within 

whichever POP the hardware is accepted, the interim evaluation and resultant interim award fee payment 

for that same milestone will not be made until the conclusion of the actual POP during which the 

Government is reasonably able to perform a thorough evaluation of the actual mission performance of the 

delivered hardware. 

For purposes of making provisional milestone award fee payments for completed PORlCORlOCR, this 

agreement recognizes milestone completion dates based upon the submission of all OROs required to 

support the actual PORlCORlOCR meetings. Although provisional award fee payments will be made for 

Attaclunent J-7 

Page 8 of 12 

-- 

-- -- 

-- 

--





these milestones after submission of all required DROs, the interim evaluation and resultant interim award 

fee payment for that same milestone will not be made until all completion criteria for the actual 

PDRlCDRlDCR meetings have been met. If the actual review is held and the review's completion criteria 

met during the same period during which all required DRDs for that review were submitted, then the interim 

evaluation and award fee payment for that review milestone will be accomplished at the conclusion of that 

period of performance. However, if the actual review is held or its completion criteria met in a period 

subsequent to the one during which all required DRDs were submitted, the interim evaluation will be 

conducted at the end of the period of performance during which the completion criteria for that review 

milestone is completed. 

f--__ -.:.:.M;.:.:iestor:!~_____II___'M.:.:;i;;.;le:c::s.:..;;to:..:,n:..:;e-=D:;..:a:..:.te=-"__I--'-Avaiiable Fee 

8/31/2007 

IDIO Fee·· 

4/21/2009 

4/18/2009 

8/21/2009 

10/8/2010 

6/1/2010 

8/11/2011 

9/7/2012 

6/3/2013 

1/18/2014 

12/2/2013 L 

6/2/2014 

Total 

"Dates correspond with final hardware DD250 per Attachment J-9, "Deliverable' items List" 

Interim Earned 

Fee 

" "Starting with Award Fee Period 2, 1010 Award Fee is included in Table A, Period of Performance Award 

Fee Pool 


Page 9 of12





Table C: Indefinite Delivery I Indefinite Quantity (IDIQ) Award Fee 

The maximum award fee available for 1010 delivery/task orders is as follows· 

l 

Delivery Order 

Number 

, NNJ07T A26T 

NNJ07TA27T 

NNJ07T A28T* 

NNJ07TA29T 

Award Fee Award Fee Award Fee Award Fee 

Period 1: Period 2: Period 3: Period 4: 

ATP - 8/31/07 9/1/07.4/30/09 5/1/09·4130/10 5/1/10 - 4130/11 

NNJ07TA30T 

NNJ07TA31T* 

NNJ07T A32T* 

NNJ07TA33T* ~ If"\' 

l,f 

NNJ07TA34T* 

NNJ07TA35T , 

NNJ08TA15T* 

NNJ08TA16T 

NNJ08TA17T 

NNJ08TA18T 

NNJ08TA19T 

NNJ08TA20T 

NNJ08TA21T 

NNJ09TAOH 

NNJ09TA02T* 

Task Order 20- 

Task Order 21- 

Total Maximum 

Award Fee 

r 

., • 

-'- 

Award Fee Award Fee 

Period 5: Period 6: 

5/1/11 - 4130/12 5/1/12 - 4130/13 

Award Fee 

Period 7: 

511113 - 4130/14 

Award Fee 

Period 8: 

5/1/14 - 12131/14 

, 

Total 

kJ{ 

I 

, 

*Oue to the period of performance for these dehvery/task orders. award fee IS reflected in multiple award fee periods. 


Page 10 of12





Enclosure III 

Future Contract Changes - Award Fee Distribution Methodology 

This enclosure sets forth the methodology for distributing Award Fee for future contract changes. 

Award Fee dollars will be split 40% to the POP Award Fee (Enclosure II, Table A) and 60% to the remaining 

incomplete Milestones (Enclosure II, Table 8) as described in paragraphs I and II below. 100% of the IDIQ 

Award Fee dollars will be allocated to POP Award Fee (Enclosure II, Table A) evenly by month based on 

the IDIQ period of performance. 

I. POP Award Fee (40%) (Enclosure II. Tables A and C) 

POP Award Fee will be spread among the remaining milestones, proportionately based on the percentage 

for each period. As a period is completed, the aggregate percentages are re-calculated using a ratio based 

on the percentage values of the remaining periods. 

All future IDIIQ Award Fee will be Included in the POP Award Fee pool and split evenly by month based 

upon the awarded Delivery/Task Order period of performance. 

Award Fee Period Period % of Fee Pool 

1* ** 

2 9/1/07 - 4/30/09 

3 5/1109 - 4/30/10 

5/1/10 - 4/30/11 vi( - 

4 

5 5/1/11 - 4/30/12 

6 5/1/12 - 4/30/13 

7 5/1/13 - 4/30/14 

8 5/1114 -12/31/14 

.- 

Total 100.00% 

* ThIS Award Fee Plan was restructured dUring Award Fee PerIod 2. 

At the time of Award Fee Period 1 evaluation, all Award Fee was 

based on Performance Milestones; therefore, all Period 1 Award Fee 

IS ref/ected in Enclosure II, Table 8 of this Enclosure. 

** Denotes Period Complete 

- 

- 

- 

- 


Page 11 of12





II. Milestone Award Fee (60%) (Enclosure II. Table B) 

Milestone Award Fee will be spread among the remaining milestones, proportionately based on the 

basic percentage for each milestone. As a milestone is completed, the aggregate percentages are 

recalculated, using a ratio based on the basic percentage values of the remaining milestones. 

Should a new milestone be added or deleted, based on a contract change or otherwise, the 

milestone percentages would be subject to change based on impact of the additional milestone. 

I- 

r 

I- 

- 

Milestone 

\p~ 

Total 

** 

Denotes Milestone Complete 

Milestone Date 

8/31/2007 

4/21/2009 

4/18/2009 

8/21/2009 

6/112010 

1018/2010 

8111/2011 

9/712012 

6/3/2013 

1/18/2014 

12/2/2013 

61212014 

Allocation 

Percentages 

- 

- 

- 

- 

laf - 

- 

.~ . -------- -... -.. 

100% 

- 

- 

- 

. 


Page 12 of12






DELIVERABLE ITEMS LIST 

May 2009 


Page 1 of 10




DELIVERABLES ITEMS LIST 



The Deliverable Items List (Attachment J-9) contains all deliverables described in the Statement of 

Work (SOW), excluding the DRDs listed in Attachment J-2, Data Procurement Document and the date 

each deliverable is scheduled. This list includes contractor deliverables, including the Ground Support 

Equipment to be delivered in support of spacecraft processing, launch and recovery. 

A deliverable item is defined as, an item which, upon delivery, accountability is transferred to NASA. 

Each deliverable shall be accompanied by the appropriate transmittal documentation (e.g., DD2S0 Form 

or DD149 form, Certificate ofCompletioniCompliance (COC), Letter of Transmittal). 

Unless otherwise marked in the list below, all deliverables shall be submitted via the DD250 Form. 

Note: Items marked with (1) are associated with Schedule B. These delivery dates and vehicle 

designations have not been updated to be consistent with Contract Attachment J-16, and will be revised 

under a separate contract action prior to the date that the Schedule B and C Options are authorized. 


Page 2 of10


Crew Exploration Vehicle (CEV) 




INSTALLATION ACCOUNTABLE 

PROPERTY AND SERVICES 

Guidance for List of Installation-Accountable Property (NFS 

1852.245-71 Alt I Nov 2004) is included in Section G.g of Orion 

Contract 

The J-1 0 IS a listing of tangible property that the Government 

maintains records for and will be made available to LMSSC at a 

NASA facility (for use on the facility) for performance of the On on 

contract. 

Attachment J-1 0 

Page 1 of 1






GOVERNMENT FURNISHED PROPERTY 

Guidance for List of Government -Furnished Property (NFS 1852.245-76 Oct 1988) 

is included in Section G.1 0 of Orion Contract 

The J-11 is a listing of tangible property that the Government transfers to the 

contractor for use off NASA facilities and the contractor maintains records. The list 

will be updated annually during the NF1 018 reporting process to reflect current 

Government assets accountable to the contract at that point in time. 


Page 3 of 1






LIST OF GOVERNMENT FACILITIES 

Guidance for Intallation-Accountable Government Property and Services (NFS 1852245- 

77 Jul 1997) is included in Section G 11 of the Orion Contract. 

The J-12 is a listing of faCilities that the Government maintainS records for and will be 

made available to LMSSC for performance of the Orion contract. 

The "services" provided shall also be listed In this attachment 


Page 43 of 1






INTEGRATED PROJECT SCHEDULE 

May 2009 


Page 1 of4

, OMS Approval" 2700-0042 

1 CONTRACT 10 CODE 

PAGE OF rCHiS 

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT NNJ06TA25C 

I 

1 1 

2 AMENDMENTIMODIFICATlON NO 

4 REOUISITIONIPURCHASE REO NO I 5 ,PROJECT NO (lfappllcable} 

3 AUOCTn~ 

Modi.tication 76 N/A ' N,A 

6 ISSUEDBY CODE BTl 

7 AOMINISTEReD BY (If other lIran 1t.m'iJ) , 

KASA I.yndon B. Johnson Space Center 

Attn: BT j5teve Fletcher 



- 

8 NAME AND ADDRESS OF CONTRACTOR lNo , /lITH1.


Modffic::atioD 76 

Continuation ofblockl4 of the SF30: 

In order to implement the ARRA requirements, the following changes to the contract are made: 

1. Clause B.3, is revised as follows: 

(a) The following changes are made to the Contract value table: 

(b) 

DesCription DeUvery Estimated Muimum Total Cost and 

Order Cost Award Fee Award Fee 

Number 

Completion Not Applicable 

S6, 130,343, 133 

Fonn-non 

W~ b~ 

Recovery 

Effort 

Completion Not Applicable 

Fonn- 

~ Iof 

SI65,900,000 

Recovery 

Effort 

2. Clause F.2, Completion of Work, subparagraph c) is added as follows: 

"c) All recovery related work must be completed no later than September I, 2010. 

3. Section I is amended to include the following FAR clauses and clause updates: 

a) New clauses are hereby included in the by reference clause list and a~ly to Recovery 

items only: 

1. 52.203-15 Whistleblower Protections Under the American Retovery &. 

Reinvestment Act of 2009 (Mar 2009) 

2. 52.204-11 American Recovery &. Reinvestment Act-Reporting Requirements 

(Mar 2009) 

b) Clauses already included in the by reference list are updated as follows: 

1. 52.215-2 Audit and Records-Negotiation (Mar 2009) Alt. I (Mar 2009) [Note 

that Alt I applies to recovery items only J 

2. 52.244-6 Subcontracts for Commercial Items (Mar 2009)[This updated clause 

applies to the entire contract, including both recovery and non-recovery items] 

21Page



I 

I 

I 

4. Section 1. Attachment J-l Statement of Work is revised to add to following innex: 

\ 

"Statemeut of Work Annex for Recovery Funded efforts I 

This statement of work (SOW) is a supplement to the SOW contained in the b8S3' contract in 

Attachment J-l. In as much as the work requirements in this Annex supplemen and do not 

replace the existing SOW, all of the requirements contained in Attachment J-I d elsewhere in 

the contract, remain in full force and effect 

Technical Tasks: 

The contractor shall deliver work in the three categories which are Ground Test ~cles, 

Engineering Design Units, and Technology Development Testing for Improved Crew Safety. 

Tasks are more specifically defined in the table below: ! 

I 

I 

ORION PROJECT Priority Stimulus Tasks 

NAME 

IPT 

Task DeecrfDtlon 

GTA 

Ground Test ArtIcle (GTA) Titanium Heat Crew Complete the development of the 

Shield 

Module 

......."'", ............'''''... m h'" 

shields. Complete the proc rement of long 

lead titanium material for t e Ground Test 

Article (GTA) and engineeri g development 

unit (EDU) heat shields. Per orm 

fabrication of tooling In sup port ofthe GTA 

heat shield. 

Service Module (SM) Ground Test ArtIcle Service perform the developmen of the 

(GTA) Test Article Build & Tooling Module engineering drawings for GTA Service 

Module (SM) Structures roolilN. 

Service Module (SM) Ground Test Article Service Perform the engineering de elopment 

(GTA) Engineering Module activities of the Service Moe uleGround 

Test Article Engineering. 

I 

! 

31Page



EDU 

ASIC for Time Triggered Gigabit Ethemet 

(TTGbe) and Vehicle Master Computer 

Avionics & Software Development & 

qualificstlon tools - Verification Test Boards 

(VTB) 

Communication & Tracking (C& T) early sub 

actlVslion 

Recover CEV Avionics Integration Lab 

(CAlL) Development Costs in FY09 and 

FY10 

Textron Avcoat EDU 

Forward Bay Cover (FBC) Retention & 

Release (R&R) Engineering Development 

Unit 

Avionics & 

Software 

Avionics & 

Software 

Avionics & 

Software 

Avionics & 

Software 

Crew 

Module 

Crew 

Module 

Perform FPGA/board proto f'/pe risk 

mitigation testing. Comple e the activities 

required to turn on the ASII foundry as well 

as perform the build and te t of a prototype 

SCP, NIC Switch, PDU contn lIer with FPGA. 

Integrate completed items ~to a test 

network in a realistic Orion onfiguratlon. 

Validate requirements for c mponents 

prior to ASIC lOR. i 

Develop design speclfic:atio+s, produce 

drawings and parts lists, inf-" and verify 

the Orion Vehicle master c puter Test 

Benches (VTBs) and the Ori n Support 

Software Development Lab (SSDL). Perform 

the procurement of hardw+,e and software 

for the SSDL and the rig har~ware for the 

Orion VTBs. 

I 

COmplete the engineering s ~eclfications, 

request for proposais and 51 urce selection 

of the subcontracts for spec fic 

COmmunication and Tracklrlg components. 

Perform long lead procuren ent for the 

transponder and baseband processor 

EDU's. 

Complete the detailed desii n of CEV 

Avionics Integration lab sof~are, rig 

subsystems and lab Infrast~cture. Perform 

the procurement of initial 'fll 

infrastructure and prototyPlng effort. 

Complete the closeout of th~ Preliminary 

Design Review action item~as well as the 

Design Analysis Cycle 4 dev lopment 

activities for ablative gunnl g and 

inspection and test panel faprlcatlon and 

heat shield EDU manufactu ng. 

Perform the eM Forward B~Y Cover 

retention and release EDU t ardware design 

development and englneerl g drawings for 

parts procurement and fabr cation and test 

fixture design. 

41Page

NNJ06TA2SC 

Modiftcadon 76 

Crew Module (CM)lService Module (SM) 

Retention & Release EDU 

Launch Abort System/Crew Module 

Retention & Release EDU 

Hatches (Docking & Side) Engineering 

Development Unit (EDU) 

Crew Impaet Attenuation System (CIAS) 

Engineering Development Unit (EOU) 

Lexan Windows EDU 

ECLSS (SM) requirement to meet 

qualifiCation deliveries - Included In CM 

ECLSS (CM) requirement to meet 

qualification deliveries· Includes SM 

CMECLSSI 

'oJ( 

Crew 

Module 

Crew 

Module 

Crew 

Module 

Crew 

Module 

Crew 

Module 

Service 

Module 

Crew 

Module 

Crew 

Module 

Perform the CM/SM retention and release 

EDU hardware design development and 

engineering drawings for parts 

procurement and fabrication and test 

fixture des~n. 

Perform the LAS/CM retention and release 

eDU hardware design develqpment and 



flxture design. 

Perform the CM hatch (docking and side) 


engineering drawings for patts 

procurement and fabrlcatio~ and test 


Perform the Crew Impact Attentuation 

System EDU hardware design , development 

and engineering drawings for parts 


flxture desJin. 

Perform the CM lexan window EDU 

hardware design development and 




See CM ECLSS below i 

Perform the CM/SM ECLSS Ebu hardware 

design development and en.lneering 

drawings for parts long lead procurement 

and fabrication for the specltic subsystems 

listed below: C02 and humi~itv control. 

Vent and Temp control. Subl,mator Assy. 

I 

Contingency Gas analvzer. 

perform the CM Umbilical QUick Disconnect 

deSign and analvsls of the mechanical 

devices required to produce engineering 

development unit hardware and 

component qualification hardware. 

I 

51 Page

NNJ06TA2SC 


SMECLSS 

~ 

Station Power Transfer Unit (SPTU) 

~ lead procurement for Hot 

Flow/Cold Flow Testing 

Crew Module Uprlghtlng System (CMUS) 

EDUs & Long Lead Procurement 

Service Module Fairing Separation Test 

Tooling and Panels 

Service Module Propulsion Recovery 

Teebnology Development Tlldag Cor 

Improved Crew SaCety 

Material Testing for Thermal Protection 

System 

Segmented Crew Module (deferred tooling) 

Materials & Processing (M&P) for Titanium 

Fasteners and 2050 Aluminum 

Service 

Module 

Crew 

Module 

Crew 

Module 

Crew 

Module 

Service 

Module 

Service 

Module 

Crew 

Module 

Crew 

Module 

Crew 

Module 

Perform the SM Umbilical Quick Disconnect 

design and analysis ofthe mechanical 

devices required to produc~ engineering 

development unit hardware and 

component qualification hardware. 

Perform service module radiator 

development testing, preliminary design 

and analysis, and engineering required for 

production of hardware reqi.llred for the 

Structure Test Article. 

Perform the CM Station Power transfer unit 


engineering drawings for long lead parts 

procurement. 

I 

Complete the fabrication and delivery of 

the CM reaction control sys~m Cold flow 

development test article (C DTA) and Hot 

Fire Test Article (HFTA). 

Perform the CMUS EDU hardware design 

development and engineering drawings for 

long lead procurement of two Inflation 

tanks (mass emulators) and 1 CMUS EDU. 

Complete the design and d.velopment of 

the speCific tooling and pan~!ls for the 

service module fairing separ'atlon test. 

Perform the engineering an~ drawings for 

the service module pressurization system 

isolation valves and the assqclated 

procurement to support th~ cold gas and 

hot fire tests of the Orion Main ell"nes. 

, 

Perform material testing for, the crew 

module thermal protection $ystem. 

Complete the design and development of 

the specific tooling and hanc~lIng fixtures for 

the segmented crew modulI! design. 

Complete material testing ot titanium 2050 

fasteners for the crew module. 

61 P agc

NNJ06TA15C 

Modifieation 76 

Reporting: 

I 

In addition to the above tasks, there are reporting requirements that are in additio~ to tbose calIed 

for by FAR 52.204-11. The contractor sbalI provide both fmancial reporting as w'ell as technical 

progress reports. The above tasks are more broadly associated with satisfaction ~f established 

contract requiremeIits and deliverables, but are delineated above to provide appr~ate 

segregation for the expenditure of ARRA funding, as well as to facilitate repa' as required by 

the use of the funds. The above tasks are delineated to allow the Contractor to p vide 

information regarding measurable performance against the task schedules and req irements. 

The financial reporting sbalI be in the form of a supplemental report submitted in njunction 

with the NF533. LM sbalI provide the details by Stimulus Category (GTA, EDU, Crew Safety) 

in the 533 format which include labors hours and total cost, which includes subeo tractors and 

materials. The contractor is required to report the CostlHrs in 3 areas (Current a , Cum 

actuals, and Current estimate). Based on Recovery Requirements. dolIars shall tracked, 

reported, and invoiced separately and shall not be comingled with other funding. or 

transparency and traceability, the Stimulus Categories sbalI be identified by was Level 213 in 

order split CostIWYE between by Project CAM. 

The contractor shall also provide monthly Recovery Act progress reports. Thes~ reports must 

describe the cumulative progress made, plans forward and shall also describe any ilifticulties 

encountered. progress made shall be estimated and reported using milestone percent complete 

reporting. The progress reported must not be percent hours exhausted, percent co+t incurred, or 

earned value based. The final report provided shall describe not only work complFte but also 

shall document how this activity has reduced the overall risk to the project and sh+U also 

document the way in which lessons learned as the result of these activities have b4en incorporated 

into the design and manufacturing efforts. 

I 

I 

\ 

I 

71Page

NNJ06TA25C MODIFICATIONS - NASA

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?