Short Form Instructions for Completing JSC Form 2323 &2323A

For more detailed information, see JSC-STD-123.

# DRL IDENTIFICATION

a\. Title -- Enter nomenclature descriptive of activity to which the DRL
pertains, such as project, contract, statement of work, or request for
proposal.

b\. Contract/RFP Number -- Enter contract number or RFP number, if
applicable.

c\. Date -- Enter DRL preparation date as follows: Month-Day-Year.
Subsequent modification dates may also be entered in this block.

LINE ITEM IDENTIFICATION

1\. Line Item No. -- Number line items sequentially, 1 through 999.
Items 1, 2, 3, 4 are preprinted on JSC Form 2323.

2\. DRD Title -- Enter DRD title from block 1 of JSC Form 2341.

3\. Data Type -- Check the appropriate data type. Additional detail
needed to clarify types or define subtypes may be added in block 9,
REMARKS.

\(1\) Written Approval -- Data requiring written approval by the NASA
OPR before implementation into procurement or development program.

\(2\) Mandatory Submittal -- Data submitted to NASA for coordination,
information, review, and/or management control.

\(3\) Submittal Upon Request -- Data prepared and retained by respondent
to be made available to requiring organization upon request.

4\. Frequency -- Enter frequency of submittal code as follows:

[Code Description]{.underline} [Code Description]{.underline} [Code
Description]{.underline}

AD As Directed DA Daily RD As Released

AN Annually DD Deferred Delivery RT One Time and Revisions

AR As Required MO Monthly SA SemiAnnually

BE Biennually (Every other yr.) OT One Time TY Three Per Year

BM Bimonthly (Every other mo.) PV Per Vehicle UR Upon Request

BW Biweekly (Every other week) QU Quarterly WK Weekly

5\. As-Of Date -- If reports are of a recurring nature, give as-of date
(cuttoff date and due date: e.g., 15/1 indicated input cutoff date of
15^th^ and due date of 1^st^). Amplify in Remarks, Item 9, if necessary.

6\. First Submittal -- Enter Month/Day/Year of initial submittal. If
calendar date is not scheduled, enter number of days preceding or
following event to which data requirement is related (e.g., 90 days
prior to launch). Amplify in Remarks, Item 9, if necessary.

7\. Copies -- Complete 7a and 7b as specified below.

a\. Type -- Enter code as follows:

[Code]{.underline} [Definition]{.underline} [Code]{.underline}
[Definition]{.underline}

PRINT Printed Copies MICRO Microfilm Aperture Cards

REPRO Reproducible Copy OTHER Explain Remarks, Item 9

b\. Number -- Enter number of copies required opposite each type of copy
furnished.

8\. DISTRIBUTION -- List current codes or addresses and names of
organizations which are to receive copies of documents generated under
the DRD. If more than one copy is required, so indicate in parenthesis
by recipient's name. Continue on a blank sheet if necessary.

9\. REMARKS -- Enter in this space.

a\. Reference to specific work statement paragraph as applicable to
explain relationship of data to task.

b\. Additional submittal information, if necessary.

c\. Comments which explain an entry made in any block of the DRL.

d\. OPR for a specific DRD, if different from contract COTR.

+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | SA-1-1, Safety and  |            | que | As | s    |        |
| i   | Health (S&H) Plan   | X (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | RT  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 1   |                     | X (2)      | (   |    | Blk  |        |
|     |                     | Mandatory  | See | S  | 9    | See    |
|     |                     | Submittal  | Blk | ee |      | DRD    |
|     |                     |            | 9)  | B  |      |        |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 6  |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            | **  |    |      |        |
|     | BE/NASA Contracting |            | *5. |    |      |        |
|     | Officer             |            | P   |    |      |        |
|     |                     |            | lan |    |      |        |
|     | BE/Seat Contract    |            | m   |    |      |        |
|     | Technical Manager   |            | ust |    |      |        |
|     |                     |            | be  |    |      |        |
|     | JJ12/Chief,         |            | ap  |    |      |        |
|     | Environmental       |            | pro |    |      |        |
|     | Services Office     |            | ved |    |      |        |
|     |                     |            | bef |    |      |        |
|     | NA3/Chief, Health,  |            | ore |    |      |        |
|     | Safety, and         |            | c   |    |      |        |
|     | Environmental       |            | omm |    |      |        |
|     | Compliance Office   |            | enc |    |      |        |
|     | (OPR)               |            | ing |    |      |        |
|     |                     |            | haz |    |      |        |
|     | SD26/Occupational   |            | ard |    |      |        |
|     | Health Officer      |            | ous |    |      |        |
|     |                     |            | op  |    |      |        |
|     |                     |            | era |    |      |        |
|     |                     |            | tio |    |      |        |
|     |                     |            | ns. |    |      |        |
|     |                     |            | Re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | s   |    |      |        |
|     |                     |            | ign |    |      |        |
|     |                     |            | atu |    |      |        |
|     |                     |            | res |    |      |        |
|     |                     |            | are |    |      |        |
|     |                     |            | spe |    |      |        |
|     |                     |            | cif |    |      |        |
|     |                     |            | ied |    |      |        |
|     |                     |            | in  |    |      |        |
|     |                     |            | D   |    |      |        |
|     |                     |            | RD. |    |      |        |
|     |                     |            | 6.  |    |      |        |
|     |                     |            | P   |    |      |        |
|     |                     |            | lan |    |      |        |
|     |                     |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | ted |    |      |        |
|     |                     |            | by  |    |      |        |
|     |                     |            | 1   |    |      |        |
|     |                     |            | 0/1 |    |      |        |
|     |                     |            | af  |    |      |        |
|     |                     |            | ter |    |      |        |
|     |                     |            | i   |    |      |        |
|     |                     |            | nco |    |      |        |
|     |                     |            | rpo |    |      |        |
|     |                     |            | rat |    |      |        |
|     |                     |            | ion |    |      |        |
|     |                     |            | of  |    |      |        |
|     |                     |            | t   |    |      |        |
|     |                     |            | his |    |      |        |
|     |                     |            | req |    |      |        |
|     |                     |            | uir |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nt. |    |      |        |
|     |                     |            | *** |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            | 4.  |    |      |        |
|     |                     |            |   S |    |      |        |
|     |                     |            | ect |    |      |        |
|     |                     |            | ion |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            | 3.2 |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            |   a |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            |  of |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            |   D |    |      |        |
|     |                     |            | RD, |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            |  Ac |    |      |        |
|     |                     |            | cid |    |      |        |
|     |                     |            | ent |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            |   S |    |      |        |
|     |                     |            | umm |    |      |        |
|     |                     |            | ary |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            | Rep |    |      |        |
|     |                     |            | ort |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            |   a |    |      |        |
|     |                     |            | ddi |    |      |        |
|     |                     |            | tio |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            |  su |    |      |        |
|     |                     |            | bmi |    |      |        |
|     |                     |            | tta |    |      |        |
|     |                     |            | ls: |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            | B   |    |      |        |
|     |                     |            | E/S |    |      |        |
|     |                     |            | eat |    |      |        |
|     |                     |            | Co  |    |      |        |
|     |                     |            | ntr |    |      |        |
|     |                     |            | act |    |      |        |
|     |                     |            | Tec |    |      |        |
|     |                     |            | hni |    |      |        |
|     |                     |            | cal |    |      |        |
|     |                     |            | M   |    |      |        |
|     |                     |            | ana |    |      |        |
|     |                     |            | ger |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            | EA/ |    |      |        |
|     |                     |            | Ass |    |      |        |
|     |                     |            | ist |    |      |        |
|     |                     |            | ant |    |      |        |
|     |                     |            | for |    |      |        |
|     |                     |            | I   |    |      |        |
|     |                     |            | nst |    |      |        |
|     |                     |            | itu |    |      |        |
|     |                     |            | tio |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            | O   |    |      |        |
|     |                     |            | per |    |      |        |
|     |                     |            | ati |    |      |        |
|     |                     |            | ons |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Information         |            | que | As | s    |        |
| i   | Technology (I/T)    | X (1)      | ncy | -o | ubm. | a\.    |
| tem | Plan and Reports    | Written    |     | f- | date | Type   |
| no. |                     | approval   | See | da |      | b.     |
|     |                     |            | Blk | te | See  | Number |
| 2   |                     | X (2)      | 9   |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | 5      |
|     |                     | Submittal  |     | ee |      | copies |
|     |                     |            |     | B  |      |        |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | Final versions of   |            | #   |    |      |        |
|     | 8.1.c, 8.1.e,       |            | 4,5 |    |      |        |
|     | 8.2.a,and 8.3.a     |            | and |    |      |        |
|     | shall be            |            | 6:  |    |      |        |
|     | distributed to:     |            | A   |    |      |        |
|     |                     |            | ppr |    |      |        |
|     | BE/NASA Contracting |            | ova |    |      |        |
|     | Officer             |            | ls, |    |      |        |
|     |                     |            | c   |    |      |        |
|     | BE/NASA Technical   |            | onc |    |      |        |
|     | Manager             |            | urr |    |      |        |
|     |                     |            | enc |    |      |        |
|     | EV1/EA Directorate  |            | es, |    |      |        |
|     | IRM Coordinator     |            | and |    |      |        |
|     | (OPR)               |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     | SL/SA Directorate   |            | tal |    |      |        |
|     | IRM Coordinator     |            | in  |    |      |        |
|     | (OPR)               |            | for |    |      |        |
|     |                     |            | mat |    |      |        |
|     | SA/SA Security      |            | ion |    |      |        |
|     | Representative      |            | is  |    |      |        |
|     | (8.3.a only)        |            | d   |    |      |        |
|     |                     |            | ocu |    |      |        |
|     |                     |            | men |    |      |        |
|     |                     |            | ted |    |      |        |
|     |                     |            | wit |    |      |        |
|     |                     |            | hin |    |      |        |
|     |                     |            | the |    |      |        |
|     |                     |            | DRD |    |      |        |
|     |                     |            | or  |    |      |        |
|     |                     |            | in  |    |      |        |
|     |                     |            | the |    |      |        |
|     |                     |            | I/T |    |      |        |
|     |                     |            | Im  |    |      |        |
|     |                     |            | ple |    |      |        |
|     |                     |            | men |    |      |        |
|     |                     |            | tat |    |      |        |
|     |                     |            | ion |    |      |        |
|     |                     |            | Ins |    |      |        |
|     |                     |            | tru |    |      |        |
|     |                     |            | cti |    |      |        |
|     |                     |            | ons |    |      |        |
|     |                     |            | (At |    |      |        |
|     |                     |            | tac |    |      |        |
|     |                     |            | hed |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | the |    |      |        |
|     |                     |            | D   |    |      |        |
|     |                     |            | RD) |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | ***Organization     |            | que | As | s    |        |
| i   | Report***           |  (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | Date | Type   |
| no. |                     | approval   | **  | da |      | b.     |
|     |                     |            | *QU | te | See  | Number |
| 3   |                     | X (2)      | *** |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | **     |
|     |                     | Submittal  |     | ee |      | *Print |
|     |                     |            |     | Bl | \*\* | 3***   |
|     |                     |  (3)      |     | k9 |      |        |
|     |                     | Submitted  |     |    |      | *      |
|     |                     | upon       |     | \* |      | **elec |
|     |                     | request    |     |    |      | tronic |
|     |                     |            |     |    |      | 1***   |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | BE/Contracting      |            | \*  |    |      |        |
|     | Officer (OPR) (1    |            | Due |    |      |        |
|     | complete hardcopy)  |            | 1   |    |      |        |
|     |                     |            | 0th |    |      |        |
|     | BE/Seat Contract    |            | ca  |    |      |        |
|     | Technical Manager   |            | len |    |      |        |
|     | (1 complete         |            | dar |    |      |        |
|     | hardcopy)           |            | day |    |      |        |
|     |                     |            | of  |    |      |        |
|     | BH/Space and Life   |            | the |    |      |        |
|     | Sciences            |            | mo  |    |      |        |
|     | Acquisition Team    |            | nth |    |      |        |
|     | Lead Hardcopy of    |            | fol |    |      |        |
|     | (Part A only)       |            | low |    |      |        |
|     |                     |            | ing |    |      |        |
|     | \* One electronic   |            | the |    |      |        |
|     | file copy of the    |            | q   |    |      |        |
|     | Part A management   |            | uar |    |      |        |
|     | portion shall be    |            | ter |    |      |        |
|     | electronically      |            | be  |    |      |        |
|     | deposited into the  |            | ing |    |      |        |
|     | \"ETAC\" share area |            | rep |    |      |        |
|     | file under the      |            | ort |    |      |        |
|     | NASA/JSC designated |            | ed. |    |      |        |
|     | computer system.    |            | Qua |    |      |        |
|     |                     |            | rte |    |      |        |
|     |                     |            | rly |    |      |        |
|     |                     |            | i   |    |      |        |
|     |                     |            | ncr |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nts |    |      |        |
|     |                     |            | sh  |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | be  |    |      |        |
|     |                     |            | bro |    |      |        |
|     |                     |            | ken |    |      |        |
|     |                     |            | i   |    |      |        |
|     |                     |            | nto |    |      |        |
|     |                     |            | the |    |      |        |
|     |                     |            | G   |    |      |        |
|     |                     |            | ove |    |      |        |
|     |                     |            | rnm |    |      |        |
|     |                     |            | ent |    |      |        |
|     |                     |            | fis |    |      |        |
|     |                     |            | cal |    |      |        |
|     |                     |            | ye  |    |      |        |
|     |                     |            | ar. |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            | \*\ |    |      |        |
|     |                     |            | *Fi |    |      |        |
|     |                     |            | rst |    |      |        |
|     |                     |            | s   |    |      |        |
|     |                     |            | ubm |    |      |        |
|     |                     |            | iss |    |      |        |
|     |                     |            | ion |    |      |        |
|     |                     |            | due |    |      |        |
|     |                     |            | wit |    |      |        |
|     |                     |            | hin |    |      |        |
|     |                     |            | 10  |    |      |        |
|     |                     |            | ca  |    |      |        |
|     |                     |            | len |    |      |        |
|     |                     |            | dar |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | af  |    |      |        |
|     |                     |            | ter |    |      |        |
|     |                     |            | q   |    |      |        |
|     |                     |            | uar |    |      |        |
|     |                     |            | ter |    |      |        |
|     |                     |            | e   |    |      |        |
|     |                     |            | nds |    |      |        |
|     |                     |            | fol |    |      |        |
|     |                     |            | low |    |      |        |
|     |                     |            | ing |    |      |        |
|     |                     |            | i   |    |      |        |
|     |                     |            | nco |    |      |        |
|     |                     |            | rpo |    |      |        |
|     |                     |            | rat |    |      |        |
|     |                     |            | ion |    |      |        |
|     |                     |            | of  |    |      |        |
|     |                     |            | t   |    |      |        |
|     |                     |            | his |    |      |        |
|     |                     |            | req |    |      |        |
|     |                     |            | uir |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nt. |    |      |        |
|     |                     |            | One |    |      |        |
|     |                     |            | e   |    |      |        |
|     |                     |            | lec |    |      |        |
|     |                     |            | tro |    |      |        |
|     |                     |            | nic |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | opy |    |      |        |
|     |                     |            | sh  |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | be  |    |      |        |
|     |                     |            | del |    |      |        |
|     |                     |            | ive |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | (   |    |      |        |
|     |                     |            | see |    |      |        |
|     |                     |            | bl  |    |      |        |
|     |                     |            | ock |    |      |        |
|     |                     |            | 8)  |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Reliability &       |            | que | As | s    |        |
| i   | Maintainability     |  (1)      | ncy | -o | ubm. | a\.    |
| tem | Plan                | Written    |     | f- | date | Type   |
| no. |                     | approval   | AR  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 4   |                     | X (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Print  |
|     |                     | Submittal  |     | ee |      | 1      |
|     |                     |            |     | B  |      |        |
|     |                     |  (3)      |     | lk |      | Elec   |
|     |                     | Submitted  |     | 9  |      | tronic |
|     |                     | upon       |     |    |      | 1      |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | NS2/Safety &        |            | I   |    |      |        |
|     | Mission Assurance   |            | nit |    |      |        |
|     | Technical Manager   |            | ial |    |      |        |
|     | (OPR)               |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | PDR |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | DR, |    |      |        |
|     |                     |            | rev |    |      |        |
|     |                     |            | isi |    |      |        |
|     |                     |            | ons |    |      |        |
|     |                     |            | as  |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | un  |    |      |        |
|     |                     |            | til |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ata |    |      |        |
|     |                     |            | el  |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nts |    |      |        |
|     |                     |            | are |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | let |    |      |        |
|     |                     |            | ed. |    |      |        |
|     |                     |            | Fi  |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | F   |    |      |        |
|     |                     |            | RR. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Space Shuttle GFE   |            | que | As | s    |        |
| i   | Safety Analysis     | X (1)      | ncy | -o | ubm. | a\.    |
| tem | Report (SAR) and    | Written    |     | f- | date | Type   |
| no. | Hazard Report       | approval   | AR  | da |      | b.     |
|     | (HR)\[HR_1\]        |            |     | te | See  | Number |
| 5   |                     |  (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Elec   |
|     |                     | Submittal  |     | ee |      | tronic |
|     |                     |            |     | B  |      | 1      |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      | Print  |
|     |                     | upon       |     |    |      | 1      |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | NS2/Safety &        |            | I   |    |      |        |
|     | Mission Assurance   |            | nit |    |      |        |
|     | Technical Manager   |            | ial |    |      |        |
|     | (OPR)               |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | PDR |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | DR, |    |      |        |
|     |                     |            | rev |    |      |        |
|     |                     |            | isi |    |      |        |
|     |                     |            | ons |    |      |        |
|     |                     |            | as  |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | un  |    |      |        |
|     |                     |            | til |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ata |    |      |        |
|     |                     |            | el  |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nts |    |      |        |
|     |                     |            | are |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | let |    |      |        |
|     |                     |            | ed. |    |      |        |
|     |                     |            | Fi  |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | F   |    |      |        |
|     |                     |            | RR. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Space Station       |            | que | As | s    |        |
| i   | Hazard Reports      | X (1)      | ncy | -o | ubm. | a\.    |
| tem | (HR\'s) / System    | Written    |     | f- | date | Type   |
| no. | Description         | approval   | AR  | da |      | b.     |
|     | \[HR_2\]            |            |     | te | See  | Number |
| 6   |                     |  (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Elec   |
|     |                     | Submittal  |     | ee |      | tronic |
|     |                     |            |     | B  |      | 1      |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      | Print  |
|     |                     | upon       |     |    |      | 1      |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | NS2/Safety &        |            | I   |    |      |        |
|     | Mission Assurance   |            | nit |    |      |        |
|     | Technical Manager   |            | ial |    |      |        |
|     | (OPR)               |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | PDR |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | DR, |    |      |        |
|     |                     |            | rev |    |      |        |
|     |                     |            | isi |    |      |        |
|     |                     |            | ons |    |      |        |
|     |                     |            | as  |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | un  |    |      |        |
|     |                     |            | til |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ata |    |      |        |
|     |                     |            | el  |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nts |    |      |        |
|     |                     |            | are |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | let |    |      |        |
|     |                     |            | ed. |    |      |        |
|     |                     |            | Fi  |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | F   |    |      |        |
|     |                     |            | RR. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Safety Plan         |            | que | As | s    |        |
| i   |                     | (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | RT  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 7   |                     | X (2)      |     |    | b    |        |
|     |                     | Mandatory  |     | S  | lock | Elec   |
|     |                     | Submittal  |     | ee | 9    | tronic |
|     |                     |            |     | b  |      | 1      |
|     |                     |  (3)      |     | lo |      |        |
|     |                     | Submitted  |     | ck |      | Print  |
|     |                     | upon       |     |  9 |      | 1      |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | NS2/Safety &        |            | I   |    |      |        |
|     | Mission Assurance   |            | nit |    |      |        |
|     | Technical Manager   |            | ial |    |      |        |
|     | (OPR)               |            | Sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | PDR |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | DR, |    |      |        |
|     |                     |            | rev |    |      |        |
|     |                     |            | isi |    |      |        |
|     |                     |            | ons |    |      |        |
|     |                     |            | as  |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | un  |    |      |        |
|     |                     |            | til |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ata |    |      |        |
|     |                     |            | el  |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nts |    |      |        |
|     |                     |            | are |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | let |    |      |        |
|     |                     |            | ed. |    |      |        |
|     |                     |            | Fi  |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | FRR |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title Space | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   | Shuttle GFE Failure | type:      | Fre | \. | 1st  | Copies |
| ine | Modes and Effects   |            | que | As | s    |        |
| i   | Analysis(FMEA) and  |  (1)      | ncy | -o | ubm. | a\.    |
| tem | Critical Items List | Written    |     | f- | date | Type   |
| no. | (CIL) \[FMEA_1\]    | approval   | AR  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 8   |                     | X (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Elec   |
|     |                     | Submittal  |     | ee |      | tronic |
|     |                     |            |     | B  |      | 1      |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      | Print  |
|     |                     | upon       |     |    |      | 1      |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | NS2/Safety &        |            | I   |    |      |        |
|     | Mission Assurance   |            | nit |    |      |        |
|     | Technical Manager   |            | ial |    |      |        |
|     | (OPR)               |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | PDR |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | DR, |    |      |        |
|     |                     |            | rev |    |      |        |
|     |                     |            | isi |    |      |        |
|     |                     |            | ons |    |      |        |
|     |                     |            | as  |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | un  |    |      |        |
|     |                     |            | til |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ata |    |      |        |
|     |                     |            | el  |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nts |    |      |        |
|     |                     |            | are |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | let |    |      |        |
|     |                     |            | ed. |    |      |        |
|     |                     |            | Fi  |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | F   |    |      |        |
|     |                     |            | RR. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title Space | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   | Station GFE Failure | type:      | Fre | \. | 1st  | Copies |
| ine | Modes and Effects   |            | que | As | s    |        |
| i   | Analysis(FMEA) and  |  (1)      | ncy | -o | ubm. | a\.    |
| tem | Critical Items List | Written    |     | f- | date | Type   |
| no. | (CIL) \[FMEA_2\]    | approval   | AR  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 9   |                     | X (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Elec   |
|     |                     | Submittal  |     | ee |      | tronic |
|     |                     |            |     | B  |      | 1      |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      | Print  |
|     |                     | upon       |     |    |      | 1      |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | NS2/Safety &        |            | I   |    |      |        |
|     | Mission Assurance   |            | nit |    |      |        |
|     | Technical Manager   |            | ial |    |      |        |
|     | (OPR)               |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | PDR |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | DR, |    |      |        |
|     |                     |            | rev |    |      |        |
|     |                     |            | isi |    |      |        |
|     |                     |            | ons |    |      |        |
|     |                     |            | as  |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | un  |    |      |        |
|     |                     |            | til |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ata |    |      |        |
|     |                     |            | el  |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nts |    |      |        |
|     |                     |            | are |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | let |    |      |        |
|     |                     |            | ed. |    |      |        |
|     |                     |            | Fi  |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | F   |    |      |        |
|     |                     |            | RR. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Parts Control Plan  |            | que | As | s    |        |
| i   |                     | X (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | RT  | da |      | b.     |
|     |                     |            |     | te | SEE  | Number |
| 10  |                     | X (2)      |     |    | B    |        |
|     |                     | Mandatory  |     | S  | LOCK | Repro  |
|     |                     | Submittal  |     | ee | 9    | 2      |
|     |                     |            |     | B  |      |        |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | BE/Seat Contract    |            | 1^  |    |      |        |
|     | Technical Manager   |            | ST^ |    |      |        |
|     |                     |            | Sub |    |      |        |
|     | ND6/Chief Assurance |            | mit |    |      |        |
|     | Program Branch      |            | tal |    |      |        |
|     | (OPR)               |            | 60  |    |      |        |
|     |                     |            | D   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | af  |    |      |        |
|     |                     |            | ter |    |      |        |
|     |                     |            | co  |    |      |        |
|     |                     |            | ntr |    |      |        |
|     |                     |            | act |    |      |        |
|     |                     |            | mod |    |      |        |
|     |                     |            | ifi |    |      |        |
|     |                     |            | cat |    |      |        |
|     |                     |            | ion |    |      |        |
|     |                     |            | i   |    |      |        |
|     |                     |            | nco |    |      |        |
|     |                     |            | rpo |    |      |        |
|     |                     |            | rat |    |      |        |
|     |                     |            | ing |    |      |        |
|     |                     |            | Pa  |    |      |        |
|     |                     |            | rts |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | ont |    |      |        |
|     |                     |            | rol |    |      |        |
|     |                     |            | P   |    |      |        |
|     |                     |            | lan |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | rem |    |      |        |
|     |                     |            | ent |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | NASA and GIDEP      |            | que | As | s    |        |
| i   | Alert Plan          | X (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | RT  | da |      | b.     |
|     |                     |            |     | te | SEE  | Number |
| 11  |                     | X (2)      |     |    | B    |        |
|     |                     | Mandatory  |     | S  | LOCK | Repro  |
|     |                     | Submittal  |     | ee | 9    | 2      |
|     |                     |            |     | B  |      |        |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | BE/Seat Contract    |            | 1^  |    |      |        |
|     | Technical Manager   |            | ST^ |    |      |        |
|     |                     |            | Sub |    |      |        |
|     | ND6/Chief Assurance |            | mit |    |      |        |
|     | Program Branch      |            | tal |    |      |        |
|     | (OPR)               |            | 60  |    |      |        |
|     |                     |            | D   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | af  |    |      |        |
|     |                     |            | ter |    |      |        |
|     |                     |            | co  |    |      |        |
|     |                     |            | ntr |    |      |        |
|     |                     |            | act |    |      |        |
|     |                     |            | mod |    |      |        |
|     |                     |            | ifi |    |      |        |
|     |                     |            | cat |    |      |        |
|     |                     |            | ion |    |      |        |
|     |                     |            | i   |    |      |        |
|     |                     |            | nco |    |      |        |
|     |                     |            | rpo |    |      |        |
|     |                     |            | rat |    |      |        |
|     |                     |            | ing |    |      |        |
|     |                     |            | N   |    |      |        |
|     |                     |            | ASA |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | GI  |    |      |        |
|     |                     |            | DEP |    |      |        |
|     |                     |            | Ale |    |      |        |
|     |                     |            | rts |    |      |        |
|     |                     |            | P   |    |      |        |
|     |                     |            | lan |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | rem |    |      |        |
|     |                     |            | ent |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Limited Life Items  |            | que | As | s    |        |
| i   | List (LLIL)         |  (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | AR  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 12  |                     | X (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Elec   |
|     |                     | Submittal  |     | ee |      | tronic |
|     |                     |            |     | B  |      | 1      |
|     |                     |  (3)      |     | lk |      | Print  |
|     |                     | Submitted  |     | 9  |      | 1      |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | NS2/Safety &        |            | I   |    |      |        |
|     | Mission Assurance   |            | nit |    |      |        |
|     | Technical Manager   |            | ial |    |      |        |
|     | (OPR)               |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | PDR |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | DR, |    |      |        |
|     |                     |            | rev |    |      |        |
|     |                     |            | isi |    |      |        |
|     |                     |            | ons |    |      |        |
|     |                     |            | as  |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | un  |    |      |        |
|     |                     |            | til |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ata |    |      |        |
|     |                     |            | el  |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nts |    |      |        |
|     |                     |            | are |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | let |    |      |        |
|     |                     |            | ed. |    |      |        |
|     |                     |            | Fi  |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | F   |    |      |        |
|     |                     |            | RR. |    |      |        |
|     |                     |            | Sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | an  |    |      |        |
|     |                     |            | e   |    |      |        |
|     |                     |            | lec |    |      |        |
|     |                     |            | tro |    |      |        |
|     |                     |            | nic |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | opy |    |      |        |
|     |                     |            | in  |    |      |        |
|     |                     |            | spe |    |      |        |
|     |                     |            | cif |    |      |        |
|     |                     |            | ied |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | ati |    |      |        |
|     |                     |            | ble |    |      |        |
|     |                     |            | for |    |      |        |
|     |                     |            | mat |    |      |        |
|     |                     |            | for |    |      |        |
|     |                     |            | en  |    |      |        |
|     |                     |            | try |    |      |        |
|     |                     |            | i   |    |      |        |
|     |                     |            | nto |    |      |        |
|     |                     |            | dat |    |      |        |
|     |                     |            | aba |    |      |        |
|     |                     |            | se. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | S&MA Certification  |            | que | As | s    |        |
| i   | Approval Request    | X (1)      | ncy | -o | ubm. | a\.    |
| tem | (SMACAR)            | Written    |     | f- | date | Type   |
| no. |                     | approval   | AR  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 13  |                     | X (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Elec   |
|     |                     | Submittal  |     | ee |      | tronic |
|     |                     |            |     | B  |      | 1      |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      | Print  |
|     |                     | upon       |     |    |      | 1      |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | NS2/Safety &        |            | I   |    |      |        |
|     | Mission Assurance   |            | nit |    |      |        |
|     | Technical Manager   |            | ial |    |      |        |
|     | (OPR)               |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | PDR |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | DR, |    |      |        |
|     |                     |            | rev |    |      |        |
|     |                     |            | isi |    |      |        |
|     |                     |            | ons |    |      |        |
|     |                     |            | as  |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | un  |    |      |        |
|     |                     |            | til |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ata |    |      |        |
|     |                     |            | el  |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nts |    |      |        |
|     |                     |            | are |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | let |    |      |        |
|     |                     |            | ed. |    |      |        |
|     |                     |            | Fi  |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | F   |    |      |        |
|     |                     |            | RR. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Problem Reporting   |            | que | As | s    |        |
| i   | and Corrective      |  (1)      | ncy | -o | ubm. | a\.    |
| tem | Action (PRACA)      | Written    |     | f- | date | Type   |
| no. |                     | approval   | AR  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 14  |                     | X (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Elec   |
|     |                     | Submittal  |     | ee |      | tronic |
|     |                     |            |     | B  |      | 1      |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      | (Per   |
|     |                     | upon       |     |    |      | PRACA  |
|     |                     | request    |     |    |      | DRD)   |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | ISS PRACA Database  |            | Sub |    |      |        |
|     | (OPR Space Station) |            | mit |    |      |        |
|     |                     |            | rep |    |      |        |
|     | JSC PRACA Center    |            | ort |    |      |        |
|     | (OPR Shuttle)       |            | wit |    |      |        |
|     |                     |            | hin |    |      |        |
|     |                     |            | 24  |    |      |        |
|     |                     |            | ho  |    |      |        |
|     |                     |            | urs |    |      |        |
|     |                     |            | of  |    |      |        |
|     |                     |            | p   |    |      |        |
|     |                     |            | rob |    |      |        |
|     |                     |            | lem |    |      |        |
|     |                     |            | i   |    |      |        |
|     |                     |            | sol |    |      |        |
|     |                     |            | ati |    |      |        |
|     |                     |            | on. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Certi               |            | que | As | s    |        |
| i   | fication/Acceptance |  (1)      | ncy | -o | ubm. | a\.    |
| tem | Requirements        | Written    |     | f- | date | Type   |
| no. | Document (CARD)     | approval   | AR  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 15  |                     | X (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Elec   |
|     |                     | Submittal  |     | ee |      | tronic |
|     |                     |            |     | B  |      | 1      |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      | Print  |
|     |                     | upon       |     |    |      | 1      |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | NS2/Safety &        |            | I   |    |      |        |
|     | Mission Assurance   |            | nit |    |      |        |
|     | Technical Manager   |            | ial |    |      |        |
|     | (OPR)               |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | PDR |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | DR, |    |      |        |
|     |                     |            | rev |    |      |        |
|     |                     |            | isi |    |      |        |
|     |                     |            | ons |    |      |        |
|     |                     |            | as  |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | un  |    |      |        |
|     |                     |            | til |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ata |    |      |        |
|     |                     |            | el  |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nts |    |      |        |
|     |                     |            | are |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | let |    |      |        |
|     |                     |            | ed. |    |      |        |
|     |                     |            | Fi  |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | F   |    |      |        |
|     |                     |            | RR. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Space Station       |            | que | As | s    |        |
| i   | Reliability &       |  (1)      | ncy | -o | ubm. | a\.    |
| tem | Maintainability     | Written    |     | f- | date | Type   |
| no. | Predictions Report  | approval   | AR  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 16  |                     | X (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Elec   |
|     |                     | Submittal  |     | ee |      | tronic |
|     |                     |            |     | B  |      | 1      |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      | Print  |
|     |                     | upon       |     |    |      | 1      |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | NS2/Safety &        |            | I   |    |      |        |
|     | Mission Assurance   |            | nit |    |      |        |
|     | Technical Manager   |            | ial |    |      |        |
|     | (OPR)               |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | PDR |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | DR, |    |      |        |
|     |                     |            | rev |    |      |        |
|     |                     |            | isi |    |      |        |
|     |                     |            | ons |    |      |        |
|     |                     |            | as  |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | un  |    |      |        |
|     |                     |            | til |    |      |        |
|     |                     |            | all |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ata |    |      |        |
|     |                     |            | el  |    |      |        |
|     |                     |            | eme |    |      |        |
|     |                     |            | nts |    |      |        |
|     |                     |            | are |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | let |    |      |        |
|     |                     |            | ed. |    |      |        |
|     |                     |            | Fi  |    |      |        |
|     |                     |            | nal |    |      |        |
|     |                     |            | sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | tal |    |      |        |
|     |                     |            | 30  |    |      |        |
|     |                     |            | d   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | F   |    |      |        |
|     |                     |            | RR. |    |      |        |
|     |                     |            | Sub |    |      |        |
|     |                     |            | mit |    |      |        |
|     |                     |            | an  |    |      |        |
|     |                     |            | e   |    |      |        |
|     |                     |            | lec |    |      |        |
|     |                     |            | tro |    |      |        |
|     |                     |            | nic |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | opy |    |      |        |
|     |                     |            | in  |    |      |        |
|     |                     |            | spe |    |      |        |
|     |                     |            | cif |    |      |        |
|     |                     |            | ied |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | omp |    |      |        |
|     |                     |            | ati |    |      |        |
|     |                     |            | ble |    |      |        |
|     |                     |            | for |    |      |        |
|     |                     |            | mat |    |      |        |
|     |                     |            | for |    |      |        |
|     |                     |            | en  |    |      |        |
|     |                     |            | try |    |      |        |
|     |                     |            | i   |    |      |        |
|     |                     |            | nto |    |      |        |
|     |                     |            | dat |    |      |        |
|     |                     |            | aba |    |      |        |
|     |                     |            | se. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Security Reporting  |            | que | As | s    |        |
| i   | Requirements        |  (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | See | da |      | b.     |
|     |                     |            | DRD | te | See  | Number |
| 17  |                     | X (2)      |     |    | DRD  |        |
|     |                     | Mandatory  |     | S  |      | 2      |
|     |                     | Submittal  |     | ee |      | p      |
|     |                     |            |     | D  |      | rinted |
|     |                     |  (3)      |     | RD |      | plus   |
|     |                     | Submitted  |     |    |      | others |
|     |                     | upon       |     |    |      | in DRD |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | BE/NASA Contracting |            |     |    |      |        |
|     | Officer (All items) |            |     |    |      |        |
|     |                     |            |     |    |      |        |
|     | BE/SEAT Contract    |            |     |    |      |        |
|     | Technical Manager   |            |     |    |      |        |
|     | (All items except   |            |     |    |      |        |
|     | in A.2)             |            |     |    |      |        |
|     |                     |            |     |    |      |        |
|     | See DRD for         |            |     |    |      |        |
|     | remaining           |            |     |    |      |        |
|     | distribution        |            |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | DM-397T, Quarterly  |            | que | As | s    |        |
| i   | Printing Report     |  (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | QU  | da |      | b.     |
|     |                     |            |     | te |      | Number |
| 18  |                     | X (2)      |     |    |      |        |
|     |                     | Mandatory  |     |    |      | Print  |
|     |                     | Submittal  |     |    |      | *      |
|     |                     |            |     |    |      | **3*** |
|     |                     |  (3)      |     |    |      |        |
|     |                     | Submitted  |     |    |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | BE/Contracting      |            |     |    |      |        |
|     | Officer             |            |     |    |      |        |
|     |                     |            |     |    |      |        |
|     | GA/JSC Printing     |            |     |    |      |        |
|     | Management Officer  |            |     |    |      |        |
|     | (2 copies) (OPR)    |            |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Monthly Small       |            | que | As | s    |        |
| i   | Disadvantaged       |  (1)      | ncy | -o | ubm. | a\.    |
| tem | Business            | Written    |     | f- | date | Type   |
| no. | Subcontract Report  | approval   | MO  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 19  |                     | X (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Print  |
|     |                     | Submittal  |     | ee |      | 2      |
|     |                     |            |     | B  |      |        |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | BE/ Seat Contract   |            | **  |    |      |        |
|     | Technical Manager   |            | Rep |    |      |        |
|     |                     |            | ort |    |      |        |
|     | BE/ Contracting     |            | due |    |      |        |
|     | Officer             |            | 20^ |    |      |        |
|     |                     |            | th^ |    |      |        |
|     | BD35/ Small         |            | ca  |    |      |        |
|     | Minority Business   |            | len |    |      |        |
|     | Specialist (OPR)    |            | dar |    |      |        |
|     |                     |            | day |    |      |        |
|     |                     |            | of  |    |      |        |
|     |                     |            | ev  |    |      |        |
|     |                     |            | ery |    |      |        |
|     |                     |            | m   |    |      |        |
|     |                     |            | ont |    |      |        |
|     |                     |            | h** |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Logistics           |            | que | As | s    |        |
| i   | Information         |  (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | AR  | da |      | b.     |
|     |                     |            |     | te |      | Number |
| 20  |                     | X (2)      |     |    |      |        |
|     |                     | Mandatory  |     | As |      | Print  |
|     |                     | Submittal  |     |    |      | 4      |
|     |                     |            |     | re |      |        |
|     |                     |  (3)      |     | qu |      |        |
|     |                     | Submitted  |     | ir |      |        |
|     |                     | upon       |     | ed |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | BE/Contracting      |            |     |    |      |        |
|     | Officer (1 copy)    |            |     |    |      |        |
|     |                     |            |     |    |      |        |
|     | JB3/Property        |            |     |    |      |        |
|     | Administrator (3    |            |     |    |      |        |
|     | copies) (OPR)       |            |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 1.  DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Financial           |            | que | As | s    |        |
| i   | Management Report   |  (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | *   | da |      | b.     |
|     |                     |            | *AR | te | 45   | Number |
| 21  |                     | X (2)      | **, |    | days |        |
|     |                     | Mandatory  | Mo  | S  |      | SEE    |
|     |                     | Submittal  |     | ee | a    | DRD    |
|     |                     |            |     | B  | fter |        |
|     |                     |  (3)      |     | lk | a    |        |
|     |                     | Submitted  |     | 9  | ward |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | **Part A,B,& C:     |            | 5\. |    |      |        |
|     | BE/Contracting      |            | **P |    |      |        |
|     | Officer 1 complete  |            | art |    |      |        |
|     | hard copy -         |            | A:  |    |      |        |
|     | monthly) (OPR)**    |            | Rep |    |      |        |
|     |                     |            | ort |    |      |        |
|     | One complete file   |            | due |    |      |        |
|     | copy of Part A, B,  |            | 10^ |    |      |        |
|     | and C shall be      |            | th^ |    |      |        |
|     | electronically      |            | ca  |    |      |        |
|     | deposited to the    |            | len |    |      |        |
|     | \"ETAC\" share area |            | dar |    |      |        |
|     | file under the      |            | day |    |      |        |
|     | NASA/JSC designated |            | o   |    |      |        |
|     | computer system     |            | f** |    |      |        |
|     |                     |            |     |    |      |        |
|     | Part A and B:       |            | **e |    |      |        |
|     | Monthly deposited   |            | ach |    |      |        |
|     | after November 1,   |            | ca  |    |      |        |
|     | 1997                |            | len |    |      |        |
|     |                     |            | dar |    |      |        |
|     | Part C: Weekly      |            | mo  |    |      |        |
|     | deposited           |            | nth |    |      |        |
|     |                     |            | .** |    |      |        |
|     | See DRD for other   |            |     |    |      |        |
|     | distribution        |            | **P |    |      |        |
|     |                     |            | art |    |      |        |
|     |                     |            | B:  |    |      |        |
|     |                     |            | Rep |    |      |        |
|     |                     |            | ort |    |      |        |
|     |                     |            | due |    |      |        |
|     |                     |            | 15^ |    |      |        |
|     |                     |            | th^ |    |      |        |
|     |                     |            | ca  |    |      |        |
|     |                     |            | len |    |      |        |
|     |                     |            | dar |    |      |        |
|     |                     |            | day |    |      |        |
|     |                     |            | of  |    |      |        |
|     |                     |            | eac |    |      |        |
|     |                     |            | h** |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            | *   |    |      |        |
|     |                     |            | *ca |    |      |        |
|     |                     |            | len |    |      |        |
|     |                     |            | dar |    |      |        |
|     |                     |            | mo  |    |      |        |
|     |                     |            | nth |    |      |        |
|     |                     |            | .** |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            | P   |    |      |        |
|     |                     |            | art |    |      |        |
|     |                     |            | C:  |    |      |        |
|     |                     |            | One |    |      |        |
|     |                     |            | (1) |    |      |        |
|     |                     |            | H   |    |      |        |
|     |                     |            | ard |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | opy |    |      |        |
|     |                     |            | del |    |      |        |
|     |                     |            | ive |    |      |        |
|     |                     |            | red |    |      |        |
|     |                     |            | m   |    |      |        |
|     |                     |            | ont |    |      |        |
|     |                     |            | hly |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            | con |    |      |        |
|     |                     |            | cur |    |      |        |
|     |                     |            | ren |    |      |        |
|     |                     |            | tly |    |      |        |
|     |                     |            | w   |    |      |        |
|     |                     |            | ith |    |      |        |
|     |                     |            | P   |    |      |        |
|     |                     |            | art |    |      |        |
|     |                     |            | A   |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            | 1-E |    |      |        |
|     |                     |            | lec |    |      |        |
|     |                     |            | tro |    |      |        |
|     |                     |            | nic |    |      |        |
|     |                     |            | c   |    |      |        |
|     |                     |            | opy |    |      |        |
|     |                     |            | of  |    |      |        |
|     |                     |            | P   |    |      |        |
|     |                     |            | art |    |      |        |
|     |                     |            | A,  |    |      |        |
|     |                     |            | B,& |    |      |        |
|     |                     |            | C   |    |      |        |
|     |                     |            | (   |    |      |        |
|     |                     |            | see |    |      |        |
|     |                     |            | bl  |    |      |        |
|     |                     |            | ock |    |      |        |
|     |                     |            | 8)  |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Quality Manual      |            | que | As | s    |        |
| i   |                     |  (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | RT  | da |      | b.     |
|     |                     |            |     | te | SEE  | Number |
| 22  |                     | X (2)      |     |    | B    |        |
|     |                     | Mandatory  |     | S  | LOCK | Repro  |
|     |                     | Submittal  |     | ee | 9    | 2      |
|     |                     |            |     | B  |      |        |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | BE/Seat Contract    |            | 1^  |    |      |        |
|     | Technical Manager   |            | ST^ |    |      |        |
|     |                     |            | Sub |    |      |        |
|     | ND3/Chief, Product  |            | mit |    |      |        |
|     | and Test Operations |            | tal |    |      |        |
|     | Branch (OPR)        |            | 60  |    |      |        |
|     |                     |            | D   |    |      |        |
|     |                     |            | ays |    |      |        |
|     |                     |            | af  |    |      |        |
|     |                     |            | ter |    |      |        |
|     |                     |            | co  |    |      |        |
|     |                     |            | ntr |    |      |        |
|     |                     |            | act |    |      |        |
|     |                     |            | mod |    |      |        |
|     |                     |            | ifi |    |      |        |
|     |                     |            | cat |    |      |        |
|     |                     |            | ion |    |      |        |
|     |                     |            | i   |    |      |        |
|     |                     |            | nco |    |      |        |
|     |                     |            | rpo |    |      |        |
|     |                     |            | rat |    |      |        |
|     |                     |            | ing |    |      |        |
|     |                     |            | Q   |    |      |        |
|     |                     |            | ual |    |      |        |
|     |                     |            | ity |    |      |        |
|     |                     |            | Man |    |      |        |
|     |                     |            | ual |    |      |        |
|     |                     |            | re  |    |      |        |
|     |                     |            | qui |    |      |        |
|     |                     |            | rem |    |      |        |
|     |                     |            | ent |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |            | *   |    |      |        |
|     |                     |            | **T |    |      |        |
|     |                     |            | his |    |      |        |
|     |                     |            | p   |    |      |        |
|     |                     |            | lan |    |      |        |
|     |                     |            | w   |    |      |        |
|     |                     |            | ill |    |      |        |
|     |                     |            | be  |    |      |        |
|     |                     |            | u   |    |      |        |
|     |                     |            | sed |    |      |        |
|     |                     |            | for |    |      |        |
|     |                     |            | b   |    |      |        |
|     |                     |            | oth |    |      |        |
|     |                     |            | Sp  |    |      |        |
|     |                     |            | ace |    |      |        |
|     |                     |            | S   |    |      |        |
|     |                     |            | hut |    |      |        |
|     |                     |            | tle |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | Sp  |    |      |        |
|     |                     |            | ace |    |      |        |
|     |                     |            | S   |    |      |        |
|     |                     |            | tat |    |      |        |
|     |                     |            | ion |    |      |        |
|     |                     |            | Pro |    |      |        |
|     |                     |            | gra |    |      |        |
|     |                     |            | ms. |    |      |        |
|     |                     |            | *** |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Workmanship         |            | que | As | s    |        |
| i   | Specifications      | X (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | AR  | da |      | b.     |
|     |                     |            |     | te | See  | Number |
| 23  |                     | (2)      |     |    | Blk  |        |
|     |                     | Mandatory  |     | S  | 9    | Print  |
|     |                     | Submittal  |     | ee |      | 1      |
|     |                     |            |     | B  |      |        |
|     |                     |  (3)      |     | lk |      |        |
|     |                     | Submitted  |     | 9  |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | ND2/Chief, Process  |            | Sub |    |      |        |
|     | Certification       |            | mit |    |      |        |
|     | Branch (OPR)        |            | for |    |      |        |
|     |                     |            | ap  |    |      |        |
|     |                     |            | pro |    |      |        |
|     |                     |            | val |    |      |        |
|     |                     |            | 2   |    |      |        |
|     |                     |            | we  |    |      |        |
|     |                     |            | eks |    |      |        |
|     |                     |            | pr  |    |      |        |
|     |                     |            | ior |    |      |        |
|     |                     |            | to  |    |      |        |
|     |                     |            | i   |    |      |        |
|     |                     |            | nit |    |      |        |
|     |                     |            | iat |    |      |        |
|     |                     |            | ion |    |      |        |
|     |                     |            | of  |    |      |        |
|     |                     |            | m   |    |      |        |
|     |                     |            | anu |    |      |        |
|     |                     |            | fac |    |      |        |
|     |                     |            | tur |    |      |        |
|     |                     |            | ing |    |      |        |
|     |                     |            | of  |    |      |        |
|     |                     |            | the |    |      |        |
|     |                     |            | Dev |    |      |        |
|     |                     |            | elo |    |      |        |
|     |                     |            | pme |    |      |        |
|     |                     |            | nt, |    |      |        |
|     |                     |            | V   |    |      |        |
|     |                     |            | eri |    |      |        |
|     |                     |            | fic |    |      |        |
|     |                     |            | ati |    |      |        |
|     |                     |            | on, |    |      |        |
|     |                     |            | and |    |      |        |
|     |                     |            | T   |    |      |        |
|     |                     |            | est |    |      |        |
|     |                     |            | Uni |    |      |        |
|     |                     |            | ts. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | GFE Acceptance Data |            | que | As | s    |        |
| i   | Package             |  (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | AR  | da |      | b.     |
|     |                     |            |     | te |      | Number |
| 24  |                     | X (2)      |     |    |      |        |
|     |                     | Mandatory  |     |    |      | Print  |
|     |                     | Submittal  |     |    |      | 1      |
|     |                     |            |     |    |      |        |
|     |                     |  (3)      |     |    |      |        |
|     |                     | Submitted  |     |    |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | One copy with end   |            |     |    |      |        |
|     | item                |            |     |    |      |        |
|     |                     |            |     |    |      |        |
|     | ***ND3/Chief,       |            |     |    |      |        |
|     | Product and Test    |            |     |    |      |        |
|     | Operations Branch   |            |     |    |      |        |
|     | (OPR)***            |            |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Waiver/Deviation    |            | que | As | s    |        |
| i   | Request             | X (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   | AR  | da |      | b.     |
|     |                     |            |     | te |      | Number |
| 25  |                     | X (2)      |     |    |      |        |
|     |                     | Mandatory  |     |    |      | Print  |
|     |                     | Submittal  |     |    |      | *      |
|     |                     |            |     |    |      | **2*** |
|     |                     |  (3)      |     |    |      |        |
|     |                     | Submitted  |     |    |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
|     |                     |            |     |    |      |        |
|     | > Send Shuttle End  |            | T   |    |      |        |
|     | > Item Request to:  |            | his |    |      |        |
|     | >                   |            | DRD |    |      |        |
|     | > Mary Rose         |            | a   |    |      |        |
|     | >                   |            | ppl |    |      |        |
|     | > Loral             |            | ies |    |      |        |
|     | > Aerospace/F633S   |            | to  |    |      |        |
|     | >                   |            | all |    |      |        |
|     | > Houston, TX 77058 |            | c   |    |      |        |
|     |                     |            | ont |    |      |        |
|     | ***ND35/SR&QA       |            | rol |    |      |        |
|     | Representative      |            | led |    |      |        |
|     | (OPR)***            |            | har |    |      |        |
|     |                     |            | dwa |    |      |        |
|     |                     |            | re. |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Reserved            |            | que | As | s    |        |
| i   |                     |  (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   |     | da |      | b.     |
|     |                     |            |     | te |      | Number |
| 26  |                     |  (2)      |     |    |      |        |
|     |                     | Mandatory  |     |    |      |        |
|     |                     | Submittal  |     |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |  (3)      |     |    |      |        |
|     |                     | Submitted  |     |    |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     | 8\. Distribution    |            | 9\. |    |      |        |
|     | *(Continue on a     |            | R   |    |      |        |
|     | blank sheet if      |            | ema |    |      |        |
|     | needed)*            |            | rks |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Reserved            |            | que | As | s    |        |
| i   |                     |  (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   |     | da |      | b.     |
|     |                     |            |     | te |      | Number |
| 27  |                     |  (2)      |     |    |      |        |
|     |                     | Mandatory  |     |    |      |        |
|     |                     | Submittal  |     |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |  (3)      |     |    |      |        |
|     |                     | Submitted  |     |    |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
|     |                     |            | 9\. |    |      |        |
|     |                     |            | R   |    |      |        |
|     |                     |            | ema |    |      |        |
|     |                     |            | rks |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+
| 1\. | 2\. DRD Title       | 3\. Data   | 4\. | 5  | 6\.  | 7\.    |
| L   |                     | type:      | Fre | \. | 1st  | Copies |
| ine | Reserved            |            | que | As | s    |        |
| i   |                     |  (1)      | ncy | -o | ubm. | a\.    |
| tem |                     | Written    |     | f- | date | Type   |
| no. |                     | approval   |     | da |      | b.     |
|     |                     |            |     | te |      | Number |
| 28  |                     |  (2)      |     |    |      |        |
|     |                     | Mandatory  |     |    |      |        |
|     |                     | Submittal  |     |    |      |        |
|     |                     |            |     |    |      |        |
|     |                     |  (3)      |     |    |      |        |
|     |                     | Submitted  |     |    |      |        |
|     |                     | upon       |     |    |      |        |
|     |                     | request    |     |    |      |        |
+-----+---------------------+------------+-----+----+------+--------+

+-----------------------+------+-----+----------+---+------------------+
| 1\. DRD Title:        | 2\.  |     | 3\. DRL  | R |                  |
|                       | Date |     | Line     | F |                  |
| **SA-1-1, Safety and  | of   |     | Item     | P |                  |
| Health Plan**         | Cur  |     |          | / |                  |
|                       | rent |     | 1        | C |                  |
|                       | Ver  |     |          | o |                  |
|                       | sion |     |          | n |                  |
|                       |      |     |          | t |                  |
|                       | (3/  |     |          | r |                  |
|                       | 97 - |     |          | a |                  |
|                       | repl |     |          | c |                  |
|                       | aces |     |          | t |                  |
|                       |      |     |          | N |                  |
|                       | 1    |     |          | o |                  |
|                       | 0/96 |     |          | . |                  |
|                       | vers |     |          | * |                  |
|                       | ion) |     |          | ( |                  |
|                       |      |     |          | P |                  |
|                       |      |     |          | r |                  |
|                       |      |     |          | o |                  |
|                       |      |     |          | c |                  |
|                       |      |     |          | u |                  |
|                       |      |     |          | r |                  |
|                       |      |     |          | e |                  |
|                       |      |     |          | m |                  |
|                       |      |     |          | e |                  |
|                       |      |     |          | n |                  |
|                       |      |     |          | t |                  |
|                       |      |     |          | c |                  |
|                       |      |     |          | o |                  |
|                       |      |     |          | m |                  |
|                       |      |     |          | p |                  |
|                       |      |     |          | l |                  |
|                       |      |     |          | e |                  |
|                       |      |     |          | t |                  |
|                       |      |     |          | e |                  |
|                       |      |     |          | s |                  |
|                       |      |     |          | ) |                  |
|                       |      |     |          | * |                  |
|                       |      |     |          |   |                  |
|                       |      |     |          | N |                  |
|                       |      |     |          | A |                  |
|                       |      |     |          | S |                  |
|                       |      |     |          | 9 |                  |
|                       |      |     |          | - |                  |
|                       |      |     |          | 1 |                  |
|                       |      |     |          | 9 |                  |
|                       |      |     |          | 1 |                  |
|                       |      |     |          | 0 |                  |
|                       |      |     |          | 0 |                  |
+-----------------------+------+-----+----------+---+------------------+
| 4\. Use: *(Define     |      |     |          |   | 5\. DRD Category |
| need for, intended    |      |     |          |   |                  |
| use of, and/or        |      |     |          |   | > Technical      |
| anticipated results   |      |     |          |   | >                |
| of data)*             |      |     |          |   | > Administrative |
|                       |      |     |          |   |                  |
| Establishes Safety    |      |     |          |   | X SR&QA          |
| and Health Plan for   |      |     |          |   |                  |
| contractors providing |      |     |          |   |                  |
| support to JSC        |      |     |          |   |                  |
| organizations         |      |     |          |   |                  |
|                       |      |     |          |   |                  |
| \*\*\*The Office of   |      |     |          |   |                  |
| Primary               |      |     |          |   |                  |
| Responsibility for    |      |     |          |   |                  |
| this DRD is the JSC   |      |     |          |   |                  |
| Safety, Reliability,  |      |     |          |   |                  |
| and Quality Assurance |      |     |          |   |                  |
| Office                |      |     |          |   |                  |
+-----------------------+------+-----+----------+---+------------------+
| 6\. References:       |      | 7\. |          |   |                  |
| *(Optional)*          |      | I   |          |   |                  |
|                       |      | nte |          |   |                  |
| NHB 1700.1 (VI, as    |      | rre |          |   |                  |
| revised); JPG 1700.1  |      | lat |          |   |                  |
| (as revised)          |      | ion |          |   |                  |
|                       |      | shi |          |   |                  |
|                       |      | ps: |          |   |                  |
|                       |      | *   |          |   |                  |
|                       |      | (e. |          |   |                  |
|                       |      | g., |          |   |                  |
|                       |      | w   |          |   |                  |
|                       |      | ith |          |   |                  |
|                       |      | ot  |          |   |                  |
|                       |      | her |          |   |                  |
|                       |      | DR  |          |   |                  |
|                       |      | Ds) |          |   |                  |
|                       |      | (O  |          |   |                  |
|                       |      | pti |          |   |                  |
|                       |      | ona |          |   |                  |
|                       |      | l)* |          |   |                  |
|                       |      |     |          |   |                  |
|                       |      | See |          |   |                  |
|                       |      | bl  |          |   |                  |
|                       |      | ock |          |   |                  |
|                       |      | 8.  |          |   |                  |
|                       |      | be  |          |   |                  |
|                       |      | low |          |   |                  |
+-----------------------+------+-----+----------+---+------------------+
| 8\. Preparation       |      |     |          |   |                  |
| Information *(Include |      |     |          |   |                  |
| complete instructions |      |     |          |   |                  |
| for document          |      |     |          |   |                  |
| preparation)*         |      |     |          |   |                  |
+-----------------------+------+-----+----------+---+------------------+

[NOTE: UPON NASA APPROVAL, THE CONTRACTOR\'S SAFETY AND HEALTH PLAN
BECOMES A CONTRACTUAL REQUIREMENT.]{.underline}

Frequency of submission. One time only (with the proposal).

Distribution. After the safety and health plan is approved by NASA, the
Contracting Officer will retain the plan in the contract file. The
contractor will send additional copies to each of the following:

NA3/Occupational Safety Office (2 copies)

SD26/Occupational Health Officer (1 copy)

JJ12/Environmental Services (1 copy)

Contracting Officer\'s technical Representative (1 copy)

Subsequent revisions to the safety and health plan. The contractor may
revise the plan at any time or at the direction of the Government.
Revisions are subject to Government review and approval. Distributions
of approved revisions will be as described above.

The requirements for this plan as detailed in the instructions on plan
content below include instructions for specific reports and data to be
submitted to the Government. These instructions are to be included in
the safety and health plan and represent contractual commitments by the
contractor to provide this information.

[Format:]{.underline}

1\. Cover page - to include as a minimum the signatures of Contractor\'s
project manager and designated safety official (if different); NASA
COTR; NA3/Health, Safety, and Environmental Compliance Office; and the
NASA Contracting Officer. Other signatures may be required at the
discretion of the Government.

2\. Table of Contents. To provide for traceability to the Performance
Evaluation Profile, the organization of the contractor\'s safety and
health plan should parallel the content of this data requirement as
detailed below.

3\. Body of plan - as required. Contractor\'s format is acceptable but
should be traceable to the elements of the Performance Evaluation
Profile.

4\. When preparing its safety and health plan, the offeror/contractor is
expected to review all the items below and tailor its plan accordingly.
The plan will clearly identify those resources to be provided by the
contractor and provided by the Government. This review and supporting
rationale is to be made available to the Government as part of this
plan. It can be documented as a checklist or outline, inserted directly
in the body of the plan, or in any format developed by the contractor
that clearly conveys the results of this review including the basis for
any underlying assumptions.

5\. Authority: FAR 52.223-3; NFS 18-52.223-70, 18-52-223-72,
18-52.223-73, 18-52.223-73 (Alt 1); JSCS 52.223-91

[Content:]{.underline}

**1.0 MANAGEMENT LEADERSHIP AND EMPLOYEE PARTICIPATION.**

1.1 Policy. Provide the contractor\'s safety policy statement with the
plan. Compare the contractor\'s policy statement with those of NASA and
OSHA and discuss any differences.

1.2 Goals and Objectives. Describe specific goals and objectives to be
met. Discuss status of safety program using the \"Performance Evaluation
Profile\" as safety performance criteria. Describe the contractor\'s
approach (including milestone schedule) to achieve and maintain level 5
of the Performance Evaluation Profile in all areas.

1.3 Management Leadership. Describe management\'s procedures for
implementing its commitment to safety and health through visible
management activities and initiatives including a commitment to exercise
management prerogatives to ensure workplace safety and health. Describe
processes and procedures to making this visible in all contract and
subcontract activities and products. Include a statement from the
project manager or designated safety official indicating that the plan
will be implemented as approved and that the project manager will take
personal responsibility for its implementation.

1.4 Employee Involvement. Describe procedures to promote and implement
employee (e.g., non-supervisory) involvement in safety and health
program development, implementation and decision making. Describe the
scope and breadth of employee participation to be achieved so that
approximate safety and health risk areas of the contract are equitably
represented.

1.5 Assignment of Responsibility. Describe line and staff
responsibilities for safety and health program implementation. Identify
any other personnel or organization that provides safety services or
exercises any form of control or assurance in these areas. State the
means of communication and interface concerning related issues used by
line, staff, and others (such as documentation, concurrence
requirements, committee structure, sharing of the work site with NASA
and other contractors, or other special responsibilities and support.)
As a minimum, the contractor will identify the following:

> a\. Safety Representative - identify by title the individual who will
> be trained and certified in accordance with JPG 1700.1 to be
> responsive to Center-wide safety, health, environmental, and fire
> protection concerns and goals, and who will participate in meetings
> and other activities related to the JSC Safety and Health program.
>
> b\. Company Physician - to facilitate communication of medical data to
> contractor management, the contractor shall identify a point of
> contact (such as the company physician) by name, address, and
> telephone number to the JSC Clinic, mail code SD22. Prompt
> notification to the JSC Clinic shall be given of any changes that
> occur in the identity of the point of contact.
>
> c\. Building Fire Wardens - to facilitate the JSC fire safety program
> including coordination of related issues with NASA facility managers
> and emergency planning and response officials and their
> representatives.
>
> d\. Designated Safety Official - to identify by title the official(s)
> responsible for implementation of this plan and all formal contacts
> with regulatory agencies and with NASA.

1.6 Provision of Authority. Describe consistency of the plan with
applicable NASA requirements and contractual direction as well as
applicable Federal, state, and local regulations and how this will be
maintained throughout the life of the contract.

1.7 Accountability. Describe procedures for ensuring that management and
employees will be held accountable for implementing their tasks in a
safe and healthful manner. The use of traditional and/or innovative
personnel management methods (including discipline, motivational
techniques, or any other technique that ensures accountability) will be
referenced as a minimum and described as appropriate.

1.8 Program Evaluation. The contractor shall state responsibility and
procedures to determine the significance, intrinsic worth, and
criticality of the contractor\'s hazardous operations in a manner that
proper risk management techniques can be applied and notable safety risk
documented. This includes but is not limited to the following:
identification of the contractor\'s hazardous operations and products;
ranking the risk in a severity classification; approach to identifying
and implementing specific risk evaluation tasks, managing the risks, and
documenting the results; responsibilities and methods for internal
audits and evaluations of the overall safety and health program
including personnel who conduct the audit and evaluation, to whom the
report is made, and the frequency (at least annually) with which it is
performed. These evaluations shall include subcontracted tasks.
Correlation of the program evaluation to the applicable criteria of the
Performance Evaluation Profile will be clearly described. The program
evaluation will be no later than 30 days after the end of each contract
year or at the end of the contract, whichever is applicable.
Distribution of these program evaluations will be the same as that for
the safety and health plan.

1.9 Documentation. The contractor will describe its approach to document
its safety and health program performance. This includes the
identification, acquisition, and processing of safety and health data;
development of procedures; record keeping; statistical analyses
including metrics; and the furnishing of data and reports to the
Government. For contractor activities conducted on NASA property, the
contractor will identify what records it will reproduce and forward to
the Government for centralized recordkeeping in accordance with the
Voluntary Protection Program criteria of OSHA as implemented in JPG
1700.1, \"JSC Requirements Handbook for Safety, Health, and
Environmental Protection\", as revised. For the purpose of this plan,
safety and health documentation includes but is not limited to logs,
records, minutes, procedures, checklists, statistics, reports, analyses,
notes, or other written or electronic document which contains in whole
or in part any subject matter pertinent to safety, health, environmental
protection, or emergency preparedness.

The contractor will acknowledge the following as standing requests of
the Government and to be handled as described below.

a\. [Roster of Terminated Employees.]{.underline} Identify personnel
terminated by contractor. Send to the JSC Occupational Health Officer,
mail code SD26, no later than 30 days after the end of each contract
year or at the end of the contract, whichever is applicable. At the
contractor\'s discretion, the report may be submitted for personnel
changes during the previous year or cumulated for all years. Information
required:

1)  Date of report, contractor identity and contract number.

2)  For each person listed, provide name, social security number, JSC
    badge number, and date of termination.

3)  Name, address, and telephone number of contractor representative to
    be contacted for questions or other information.

b\. [Material Safety Data.]{.underline} The contractor shall prepare
and/or deliver Material Safety Data for hazardous materials brought onto
Government property or included in products delivered to the Government.
This data is required by the Occupational Safety and Health
Administration (OSHA) regulation, 29 CFR 1910.1200, \"Hazard
Communication\", and Federal Standard 313 (or FED-STD-313), \"Material
Safety Data, Transportation Data and Disposal Data for Hazardous
Materials Furnished to Government Activities\", as revised. 1 copy of
each MSDS will be sent upon receipt of the material for use on NASA
property to the JSC Central Repository, Mail Code SD23, along with
information on new or changed locations and/or quantities normally
stored or used. If the MSDS arrives with the material and is needed for
immediate use, the MSDS shall be delivered to the Central Repository by
close of business of the next working day after it enters the site.

c\. [Hazardous Materials Inventory]{.underline}. The contractor shall
compile an annual inventory report of all hazardous materials it has
located on Government property and which is within the scope of 29 CFR
1910.1200, \"Hazard Communication\", and Federal Standard 313 (or
FED-STD-313), \"Material Safety Data, Transportation Data and Disposal
Data for Hazardous Materials Furnished to Government Activities\", as
revised. The call for this annual inventory is issued by the
Occupational Health Officer, mail code SD26. This information shall
provide the following:

> 1\) the identity of the material;
>
> 2\) the location of the material by building and room;
>
> 3\) and the quantity of each material normally kept at each location.
> This inventory will be implemented and provided to the Government as
> directed.

1.10 Government Access to Safety and Health Program Documentation. The
contractor shall recognize in its plan that it will be expected to make
all safety and health documentation (including relevant personnel
records) available for inspection or audit at the Government\'s request.

1.11 The contractor may be requested to participate in the review and
modification of safety requirements that are to be implemented by the
Government including any referenced documents therein. This review
activity will be implemented at the direction of the NASA Contracting
Officer\'s Technical Representative in accordance with established NASA
directives and procedures.

1.12 Procurement. Identify procedures used to assure that procurements
are reviewed for safety considerations and that specifications contain
appropriate safety criteria and instructions. Set forth authority and
responsibility to assure that safety tasks are clearly stated in
subcontracts.

**2.0** **WORKPLACE ANALYSIS**. Hazards shall be systematically
identified through a combination of surveys, analyses, and inspections
of the workplace, investigations of mishaps and close calls, and the
collection and trend analysis of safety and health data such as: records
of occupational injuries and illnesses; findings and observations from
preventive maintenance activities; reports of spills and inadvertent
releases to the environment; facilities related incidents related to
partial or full loss of systems functions; etc. Hazards identified by
any of the techniques identified below shall be ranked and processed in
accordance with JPG 1700.1. All hazards on NASA property which are
immediately dangerous to life or health shall be reported immediately to
the Health, Safety, and Environmental Compliance Office. All safety
engineering products which address operations, equipment, etc., on NASA
property will be subject to JSC SR&QA review and concurrence unless
otherwise specified in the approved safety and health plan. The
contractor is expected to have processes to address similar instances in
contractor facilities utilizing contractor resources to manage such
instances.

2.1 Hazard Identification. Describe the procedures and techniques to be
taken to compile an inventory of hazards associated with the work to be
performed on this contract. This inventory of hazards shall address the
work specified in this contract as well as operations and work
environments which are performed in the vicinity or in close proximity
to contract operations. The results will be reported to the Government
in a manner suitable for inclusion in facilities baseline documentation
as a permanent record of the facility. Specific techniques to be
considered include:

a\. Comprehensive Survey - A \"wall to wall\" engineering assessment of
the work site including facilities, equipment, processes, and materials
(including waste).

b\. Change Analysis - Typically addresses modifications in facilities,
equipment, processes, and materials (including waste); and related
procedures for operations and maintenance. Change analyses periodically
will be driven by new or modified regulatory and NASA requirements.

c\. Hazard Analysis - may address facilities, systems/subsystems,
operations, processes, materials (including waste), and specific tasks
or jobs.

2.2 Inspections -Includes assignments, procedures, and frequency for
regular inspection and evaluation of work areas for hazards and
accountability for implementation of corrective measures. The contractor
will describe administrative requirements and procedures for control of
and regularly scheduled inspections for fire and explosion hazards. The
contractor has the option, in lieu of this detail, to identify policies
and procedures with the stipulation that the results (including
findings) of inspections conducted on NASA property or involving
Government furnished property will be documented in safety program
evaluations or the monthly Accident/Incident Summary reports.
Inspections will identify

a\. Discrepancies between observed conditions and current requirements,
and

b\. New (not previously identified) or modified hazards.

2.3 Employee Reports of Hazards - identification of methods to encourage
employee reports of hazardous conditions (e.g., close calls) and
analyze/abate hazards. The contractor will describe steps it will take
to create reprisal-free employee reporting with emphasis on management
support for employees and describe methods to be used to incorporate
employee insights into hazard abatement and motivation / awareness
activities.

**3.0 ACCIDENT AND RECORD ANALYSIS.**

3.1 Mishap Investigation - identification of methods to assure the
reporting and investigation of mishaps including corrective actions
implemented to prevent recurrence. The contractor will describe the
methods to be used to report and investigate mishaps on NASA property
and on contractor or third party property. The contractor will describe
its procedures for implementing use of NASA forms as specified in JPG
1700.1 and alternate forms used by contractor with emphasis on timely
notification of NASA; investigation procedures; exercise of jurisdiction
over a mishap investigation involving NASA and other contractor
personnel; follow up of corrective actions; communication of lessons
learned to NASA; and solutions to minimize duplications in reporting and
documentation including use of alternate forms, etc. The contractor will
discuss its procedures for immediate notification requirements for
fires, hazardous materials releases, and other emergencies. The
contractor will include appropriate details to address the use of NASA
Form 1627, \"Mishap Report\" (or equivalent), including 24-hour and
ten-day mishap reports to the Occupational Safety Office, mail code NA3.
Note: the NASA Form 1627 is not attached since it is a three part
carbonless form not conducive to reproduction. This form can be obtained
from JSC\'s Printing Services.

3.2 Trend Analysis - describe approach to performing trend analysis of
data (occupational injuries and illnesses; facilities, systems, and
equipment performance; maintenance findings; etc.) Discuss methods to
identify and abate common causes indicated by trend analysis. In support
of site-wide trend analysis to be performed by the Government, the
contractor will discuss method of providing data as follows:

a\. Accident/Incident Summary Report. The contractor shall prepare and
deliver Accident/Incident Summary Reports as specified on JSC Form 288,
\"Accident / Incident Statistics\" (attached), as revised. All new and
open mishaps, including vehicle accidents, incidents, injuries, fires,
and close calls shall be described in summary form along with current
status. Negative reports are also required monthly. Report frequency is
monthly; Date due is the 10th day of the month following each month
reported. Report to be delivered to the JSC Safety, Reliability, and
Quality Assurance Office through the Health, Safety, and Environmental
Compliance Office, mail code NA3.

b.  Log of Occupational Injuries and Illnesses. For each establishment
    on and off NASA property that performs work on this Contract, the
    Contractor shall deliver to the Government a copy of its annual
    summary of occupational injuries and illnesses (or equivalent) as
    described in Title 29, Code of Federal Regulations, Subpart 1904.5.
    Copy of all summaries as required above under Contractor\'s cover
    letter. If contractor is exempt by regulation from maintaining and
    publishing such logs, equivalent data in contractor\'s format is
    acceptable (such as loss runs from insurance carrier) which contains
    the data required by JSC Form 288. Data shall be compiled and
    reported by calendar year and provided to the Government within 45
    days after the end of the year to be reported (e.g. not later than
    February 15 of the year following.)

**4.0 HAZARD PREVENTION AND CONTROL.** Identified hazards must be
eliminated or controlled. In the multiple employer environment of the
center, it is required that hazards including discrepancies and
corrective actions be collected in a center wide information system
(Hazard Abatement Tracking System (HATS) for risk management purposes.
Describe your approach to implementing this requirement.

4.1 Appropriate Controls. Discuss approach to consideration and
selection of controls. Discuss use of hazard reduction precedence
sequence (see JPG 1700.1). Discuss approach to identifying and accepting
any residual risk. Discuss implementation of controls including
verifying effectiveness. Discuss scope of coverage (hazardous chemicals,
equipment, discharges, waste, energies, etc.). Discuss need for
coordination with safety, health, environmental services, and emergency
authorities at NASA.

4.1.1 Hazardous Operations. Establish methods for notification of
personnel when hazardous operations are to be performed in their
facilities or when hazardous conditions are found to exist during the
course of this contract. JPG 1700.1 will serve as a guide for defining,
classifying, and prioritizing hazardous operations. Develop and maintain
a list of hazardous operations to be performed during the life of this
contract. The list of hazardous operations will be provided to JSC as
part of the Safety Plan for review and approval. JSC and the Contractor
will decide jointly which operations are to be considered hazardous,
with JSC as the final authority. Before hazardous operations commence,
the Contractor will develop a schedule to develop written hazardous
operations procedures with particular emphasis on identifying the job
safety steps required. The contractor may implement this requirement as
follows:

a\. Identify contractor policies and procedures for management and
implementation of hazardous operations procedures together with a
statement that NASA will have access on request to any contractor data
necessary to verify implementation; or

b\. In lieu of contractor management and development of such procedures,
identify the method whereby the contractor will identify and submit such
procedures to the JSC Health, Safety, and Environmental Compliance
Office for review and approval.

4.1.2 Written Procedures. Identification of methods to assure that the
relevant hazardous situations and proper controls are identified in
documentation such as inspection procedures, test procedures, etc., and
other related information. Describe methods to assure that written
procedures are developed for all hazardous operations, including
testing, maintenance, repairs, and handling of hazardous materials and
hazardous waste. Procedures will be developed in a format suitable for
use as safety documentation (such as a safety manual) and be readily
available to personnel as required to correctly perform their duties.

4.1.3 Protective Equipment. Set forth procedures for obtaining,
inspecting, and maintaining protective equipment, as required, or
reference written procedure pertaining to this subject. Set forth
methods for keeping records of such inspections and maintenance
programs.

4.1.4 Hazardous Operations Permits. Identify facilities, operations
and/or tasks where hazardous operations permits will be required as
specified in JPG 1700.1. Set forth guidance to adhere to established
NASA JSC procedures. Clearly state the role of the safety group or
function to control such permits.

a\. Operations Involving Potential Asbestos Exposures. Set forth method
by which compliance is assured with JSC Asbestos Control Program as
established in JPG 1700.1, as revised, and JPG 8800.1, \"Asbestos
Control Manual,\" as revised.

b\. Operations Involving Exposures to Toxic or Unhealthful materials.
Such operations must be evaluated by the JSC Occupational Health Office
and must be properly controlled as advised by same. JSC Occupational
Health Office must be notified prior to initiation of any new or
modified operation potentially hazardous to health.

c\. Operations Involving Hazardous Waste. Identify procedures used to
manage hazardous waste from point of generation through disposal.
Clearly identify divisions of responsibility between contractor and NASA
for hazardous waste generated throughout the life of the contract.
Operations which occur on site at JSC or Ellington Field must be
evaluated by the JSC Environmental Services Office and must be properly
controlled as advised by same. JSC Environmental Services Office must be
notified prior to initiation of any new or modified hazardous waste
operation on site at JSC or Ellington Field.

d\. Operations Involving New or Modified Emissions/Discharges to the
Environment. Set forth methods for identifying new or modified
emissions/discharges and coordinating results with the Environmental
Services Office, mail code JJ12. Set forth procedures to minimize or
eliminate environmental pollution. Address management of hazardous
materials; substitution of non-hazardous or less hazardous materials for
hazardous materials; proper segregation of hazardous wastes from
non-hazardous wastes; and other methods described by NASA.. Emphasis
shall be placed on providing for sufficient lead time for processing
permits through the appropriate state agency and/or the Environmental
Protection Agency.

4.2 Discuss your responsibilities for maintaining facilities baseline
documentation in accordance with JSC requirements. The contractor will
implement any facilities baseline documentation tasks (including safety
engineering) as provided in the contractor\'s Safety and Health Plan
approved by NASA or as required by Government direction.

4.3 Preventive Maintenance. Discuss approach to preventive maintenance.
Describe scope, frequency, and supporting rationale for your preventive
maintenance program including facilities and /or equipment to be
emphasized or de-emphasized. Discuss methods to promote awareness in the
NASA community (such as alerts, safety flashes, etc.) when preventive
maintenance reveals design or operational concerns in facilities and
equipment (and related processes where applicable).

4.4 Medical Program. Discuss your medical surveillance program to
evaluate personnel and workplace conditions to identify specific health
issues and prevent degradation of personnel health as a result of
occupational exposures. Discuss approach to Cardiopulmonary
Resuscitation (CPR), first aid, and emergency response.

**5.0 EMERGENCY RESPONSE.** Discuss approach to emergency preparedness
and contingency planning which addresses fire, explosion, inclement
weather, environmental releases, etc. Discuss compliance with 29 CFR
1910.120 (HAZWOPER) and role in JSC Incident Command System (see JPG
1700.1 for details). Discuss methods to be used for notification of JSC
emergency forces including emergency dispatcher, safety hotline,
director\'s safety hotline, etc. Discuss establishment of pre-planning
strategies through procedures, training, drills, etc. Discuss methods to
verify emergency readiness.

**6.0 SAFETY AND HEALTH TRAINING.** Describe the contractor\'s training
program including identification of responsibility for training
employees to assure understanding of safe work practices, hazard
recognition, and appropriate responses including protective and/or
emergency countermeasures. Address management techniques used to
identify and utilize JSC training resources (such as asbestos worker
training/certification, hazard communication, confined space entry,
lockout/tagout, etc.) as appropriate with particular emphasis on
programs designed for the multiple employer work environment on NASA
property. Describe approach to training personnel in the proper use and
care of protective equipment. Discuss tailoring of training towards
specific audiences (management, supervisors, and employees) and topics
(safety orientation for new hires, specific training for certain tasks
or operations). Discuss approach to ensure that training is retained and
practiced. Discuss personnel certification programs. Certifications
should include documentation that training requirements and physical
conditions have been satisfied by one or more of the following: physical
examination, testing, on-the-job performance, etc. All training
materials and training records will be provided for NASA review on
request.

**[JSC DATA REQUIREMENTS DESCRIPTION (DRD)]{.underline}**

1\. DRD TITLE: Information Technology (I/T) Plan and Reports

2\. Date of Current Version: July 23, 1997 RFP/Contract No. NAS 9-19100

3\. DRL Line Item: 2

4\. Use: To document the contractor\'s compliance with Federal and NASA
Information Technology (I/T) Planning and Reporting regulations and
requirements

5\. DRD Category: Technical/Administrative

6\. References: See Section 8.5 of Preparation Information

7\. Interrelationships: SEAT Contract Managed Support Statement of Work,
Information Technology Planning section

8.0 PREPARATION INFORMATION

> The contractor\'s IT plans and reports document the contractor\'s
> compliance with Federal and NASA I/T planning and reporting
> regulations and requirements.

**8.1 I/T Plan and Standards Requirements:**

> a\. De-facto and accepted I/T standards throughout the contract shall
> be documented and processes which will result in contract-wide I/T
> standards shall be established. When implementing the I/T planning
> process and standards, the contractor shall consider that
> informational products delivered to the government shall be delivered
> in a form to be fully useful and able to be manipulated by integrated
> standards in JSC\'s I/T Handbook (NPG 2810). This applies to the
> interoperability sections within NPG 2810. The contractor may elect at
> their option to use JSC and/or JSC organizational standards.
> Furthermore, a summary of the I/T planning process and standards shall
> be presented to the Engineering Directorate (EA) and the Space and
> Life Sciences Directorate (SA) Information Resource Management (IRM)
> Coordinators for concurrence and to the Office of the JSC Chief
> Information Officer (CIO) for approval. In addition, a summary of the
> contractor\'s contract-level I/T planning process and standards shall
> be presented to EA Directorate management. Also, the contractor shall
> be prepared to present their I/T planning process and standards to SA
> Directorate management and the JSC IRM Steering Council. Upon approval
> of the contractor\'s I/T planning process and standards by the JSC
> CIO, the contractor is then authorized by the JSC CIO to use its
> planning process and standards in the preparation of its Level B IT
> plan. **Submission Frequency:** The I/T planning process is submitted
> once and subsequent submittals shall be required only if there are
> significant changes in the process or if required by the JSC CIO.
> Standards are submitted once and subsequent submittals shall be
> required only if there are significant changes or if required by the
> JSC CIO. **Data type: 1**
>
> b\. The contractor IT planning process and standards submittals are
> required prior to the submittal of the Level B I/T plan.
>
> c\. Effective as of the incorporation of the I/T Plan and Reports Data
> Requirements Description into this contract, the contractor shall
> provide a detailed (Level B) I/T Plan for the \"next\" FY only. This
> supports the Annual Operating Plan released by the JSC Chief Financial
> Officer (CFO) to the technical organizations normally during the fall
> of each year requesting more detailed budgetary requirements for the
> upcoming government fiscal year. The Level B I/T Plan shall define the
> I/T purchases to be acquired direct during the year in terms of the
> contractor\'s standards. The contractor\'s IT planning process and
> standards and their Level B IT Plan are two separate documents. The
> approval of the I/T planning process and standards shall occur before
> the IT standards can be used as the basis for their Level B I/T Plan.
> A summary of the Level B I/T Plan shall be presented to the JSC IRM
> Steering Council for approval. Approval of the contractor\'s Level B
> I/T Plan by the JSC IRM Steering Council constitutes delegation to the
> contractor the authority to acquire individual I/T items in their
> level B I/T Plan so long as a Task Order has been approved by the
> Contracting Officer to purchase that item. Concurrence and other
> presentations are documented in the attached I/T
>
> Implementation Instructions. **Submission Frequency:** Level B I/T
> plans shall be submitted annually prior to the beginning of each
> government fiscal year and may be updated or amended as permitted by
> EA or SA management, as appropriate, and the JSC CIO. **Data type: 1**
>
> d\. An approved Level B I/T plan is required prior to any I/T
> acquisition. The contractor shall maintain records of the
> contractor\'s approval for the acquisition of each item of I/T in the
> JSC IRM Steering Council approved contractor\'s Level B I/T Plan The
> records are for the purpose of audit by the EA or SA IRM Coordinators
> as appropriate and/or the JSC CIO for compliance with NASA, JSC, and
> JSC CIO I/T planning and acquisition policies. Should the contractor
> require the acquisition of I/T items in their Level B Plan prior to
> approval of the plan by the JSC IRM Steering Council in order to meet
> mission, contract, or other time critical deadlines or schedules, the
> contractor may request approval for the acquisition of such I/T from
> the organizational IRM Coordinators and JSC CIO on an emergency basis.
> Any I/T approved by the JSC CIO on an emergency basis which was not in
> the Level B Plan shall be documented as an addition to the Level B
> Plan and records of such approvals shall be maintained by the
> contractor.
>
> e\. A 5-year Capital Acquisition Plan (Contractor\'s Information
> Systems Plan) is required and shall be presented to and concurred on
> by the Government. If the Government does not respond within 30 days
> of submittal, the plan will be considered concurred on by the
> Government. The plan shall provide information relating to the
> replacement of the Government Furnished Equipment (GFE) I/T inventory
> identified in the I/T inventory plan in 8.3.a of this DRD.
> **Submission Frequency:** The contractor\'s Capital Acquisition Plan
> shall be delivered annually in conjunction with the GFE I/T Inventory
> Report (See 8.3.a, 8.3.c, and 8.3.d of this DRD). **Data type: 2**
>
> f\. The contractor shall be prepared to interface and coordinate with
> the NASA NAS 9-19100 divisions/offices and directorates at the task
> order level to collect the necessary information for NASA\'s 5-year
> (Level A I/T) plans. This supports the NASA Program Operating Plan
> released by the JSC Chief Financial Officer (CFO) to the JSC technical
> organizations normally during the spring of each year requesting their
> high-level budgetary requirements for the next five fiscal years. The
> Level A Plan is intended to define and justify the major I/T systems
> and initiatives planned for each of the next 5 fiscal years and is a
> summary list of the I/T required to support each initiative. Level A
> plans also include an obsolescence management plan as described in
> NASA CIO Executive Notice 03-95.

**8.2 I/T Security Requirements**

> a\. The contractor shall report on the security status of each
> information technology system under the contractor\'s management
> cognizance which processes information on behalf of the Government
> prior to a system becoming operational, upon significant changes to
> existing systems, or every 3 years, whichever occurs first. Approval
> of the Security Plan shall consist of an EA Directorate and a SA
> Directorate designated approver. The EA Directorate approver is the EA
> Directorate IRM Coordinator. The Security Plan Approver listing will
> be maintained in the ETAC Share Area under path: Data on
> \'Jsc-ifs-02\'/EA/Etac/Gen_Info/Seatmgmt/Interfaces/Security Report
> Approvers. **Data Type 1**.
>
> b\. At a minimum, the contractor shall comply with direction in the
> latest edition of the Office of Management and Budget Circular A-130,
> Appendix III, Security of Federal Automated Information Resources, and
> confirm in writing the following for each applicable system:
>
> 1\) That a knowledgeable individual has been assigned security
> responsibility for the system.
>
> 2\) That a system security plan is published and is in place.
>
> 3\) That a review of security controls is conducted upon significant
> change to the system, or at least every three years, whichever occurs
> first.
>
> 4\) That a NASA management official has authorized processing based
> upon implementation of its security plan prior to being placed in
> service, upon significant change to the system, or at least every
> three years, whichever occurs first.
>
> c\. Initial Submission: Initial security reports submittals are due
> 180 calendar days after the effective date of this requirement.
>
> d\. Submission Frequency: Security reports are required as specified
> in the JSC I/T Security Handbook (JSC 2410.11).

**8.3 I/T Inventory Requirements**

> a\. I/T inventory reports shall be prepared and maintained for all
> existing off-site I/T GFE. Once the inventory item has been surplused
> or replaced by corporate replacement (capital acquisition), the I/T
> inventory shall indicate such surplus or replacement. As a minimum,
> the reports shall include the information itemized in Table 1. These
> I/T inventory reports shall be made available electronically to NASA.
> **Data type 3**
>
> b\. Starting with the effective date of this requirement, I/T
> inventory reports shall be prepared for direct purchased I/T equipment
> under this contract. The I/T inventory shall be maintained until
> transfer of accountability has occurred with NASA. All direct
> purchased I/T items under this contract shall be included in the I/T
> inventory report. As a minimum, the reports shall include the
> information itemized in Table 2. These I/T inventory reports shall be
> made available electronically to NASA. **Data type 3**
>
> c\. **Initial Submission:** Initial I/T inventory report submittals
> are due 120 calendar days after the effective date of this
> requirement.
>
> d\. **Submission Frequency:** All I/T inventory reports submitted
> after the initial are due annually by February 1.

4.  **I/T Resource Status Requirements**

> a\. The contractor shall provide a summary of the I/T resources by
> category and contain the cost (includes all I/T cost and associated
> burden cost) of I/T software, hardware, and maintenance by government
> fiscal year and accumulated for the contract.
>
> b\. **Initial Submission:** Initial I/T Resource Status Report
> submittal is due 30 days after the incorporation of this requirement.
>
> c\. **Submission Frequency:** All I/T Resource Status Reports
> submitted after the initial are due semi-annually.

**Table 1**

  -------------------- -------------- --------------- ---------------------
  **Data**             **Example**    **I/T           **Source of
                                      Category**      Requirement (NASA CIO
                                                      Executive Notices)**

  Facility             JSC, WSTF,     All             01-95, 03-95, 06-95
                       KSC, MSFC, SSC                 

  Organization         NASA, RSOC     All             01-95, 03-95, 06-95

  Category of I/T      Workstation,   All             01-95, 03-95, 06-95
                       Server, Host,                  
                       Network                        

  Mission Critical     Yes or No      All             01-95

  Manufacturer         Compaq, IBM    Workstations,   06-95
                                      Servers         

  CPU                  486/66,        Workstations,   06-95
                       Pentium/133    Servers         

  Accessible By        Public,        Workstations,   02-95
                       NASA.GOV       Servers, Hosts  

  Age                  5 years        All Hardware    03-95
  -------------------- -------------- --------------- ---------------------

**Table 2**

+-----------------+-----------------+------------+-------------------+
| # Data          | **Example**     | **I/T      | **Source of       |
|                 |                 | Category** | Requirement (NASA |
|                 |                 |            | CIO Executive     |
|                 |                 |            | Notices)**        |
+-----------------+-----------------+------------+-------------------+
| Facility        | JSC, WSTF, KSC, | All        | 01-95, 03-95,     |
|                 | MSFC, SSC       |            | 06-95             |
+-----------------+-----------------+------------+-------------------+
| Organization    | NASA, RSOC      | All        | 01-95, 03-95,     |
|                 |                 |            | 06-95             |
+-----------------+-----------------+------------+-------------------+
| Org Mail Code   | MA, OA, AA      | All        | 01-95, 03-95,     |
|                 |                 |            | 06-95             |
+-----------------+-----------------+------------+-------------------+
| Category of I/T | Workstation,    | All        | 01-95, 03-95,     |
|                 | Server, Host,   |            | 06-95             |
|                 | Network         |            |                   |
+-----------------+-----------------+------------+-------------------+
| Date Procured   | 1/5/96          | All        | 01-95, 03-95      |
+-----------------+-----------------+------------+-------------------+
| Date Excessed   | 1/5/96          | All        | 01-95, 03-95      |
+-----------------+-----------------+------------+-------------------+
| Cost            | \$3500, \$300   | All        | 01-95, 03-95      |
+-----------------+-----------------+------------+-------------------+
| Mission         | Yes or No       | All        | 01-95             |
| Critical        |                 |            |                   |
+-----------------+-----------------+------------+-------------------+
| Replaced        | Yes or No       | All        | 01-95, 03-95      |
| Existing I/T    |                 |            |                   |
+-----------------+-----------------+------------+-------------------+
| I/T Reutilized  | Yes or No       | All        | 01-95, 03-95      |
+-----------------+-----------------+------------+-------------------+
| Age             | 5 years         | All        | 03-95             |
|                 |                 | Hardware   |                   |
+-----------------+-----------------+------------+-------------------+
| Quantity        | 100, 10000      | All        | 03-95, 06-95      |
+-----------------+-----------------+------------+-------------------+
| I               | Yes or No       | Wo         | 06-95             |
| nteroperability |                 | rkstations |                   |
| Required        |                 |            |                   |
+-----------------+-----------------+------------+-------------------+
| Use             | Contractor,     | Wor        | 06-95             |
|                 | Lab, Civil      | kstations, |                   |
|                 | Servant, Loaner | Servers    |                   |
|                 | Pool            |            |                   |
+-----------------+-----------------+------------+-------------------+
| Manufacturer    | Compaq, IBM     | Wor        | 06-95             |
|                 |                 | kstations, |                   |
|                 |                 | Servers    |                   |
+-----------------+-----------------+------------+-------------------+
| CPU             | 486/66,         | Wor        | 06-95             |
|                 |                 | kstations, |                   |
|                 | Pentium/133     | Servers    |                   |
+-----------------+-----------------+------------+-------------------+
| RAM             | 8MB, 32MB       | Wor        | 06-95             |
|                 |                 | kstations, |                   |
|                 |                 | Servers    |                   |
+-----------------+-----------------+------------+-------------------+
| Disk            | 800MB,          | Wor        | 06-95             |
|                 |                 | kstations, |                   |
|                 | 1600MB          | Servers    |                   |
+-----------------+-----------------+------------+-------------------+
| Operating       | Windows NT,     | Wor        | 06-95             |
| System          |                 | kstations, |                   |
|                 | MacOS, HP/UX    | Servers    |                   |
+-----------------+-----------------+------------+-------------------+
| Operating       | 3.11, 7.5.1     | Wor        | 06-95             |
| System Version  |                 | kstations, |                   |
|                 |                 | Servers    |                   |
+-----------------+-----------------+------------+-------------------+
| Software Title  | MS Word,        | Wor        | 06-95             |
|                 |                 | kstations, |                   |
|                 | FileMaker Pro   | Servers    |                   |
+-----------------+-----------------+------------+-------------------+
| Software        | 1.1, 2.5b       | Wor        | 06-95             |
| Version         |                 | kstations, |                   |
|                 |                 | Servers    |                   |
+-----------------+-----------------+------------+-------------------+
| Network Names   | JSC-CIO-01,     | Wor        | 02-95             |
|                 |                 | kstations, |                   |
|                 | JSMITH          | Servers,   |                   |
|                 |                 | Hosts      |                   |
+-----------------+-----------------+------------+-------------------+
| Internet Name   | http://ww       | Wor        | 02-95             |
|                 | w.jsc.nasa.gov, | kstations, |                   |
|                 | ftp://          | Servers,   |                   |
|                 | ftp.hq.nasa.gov | Hosts      |                   |
+-----------------+-----------------+------------+-------------------+
| Accessible By   | Public,         | Wor        | 02-95             |
|                 | NASA.GOV        | kstations, |                   |
|                 |                 | Servers,   |                   |
|                 |                 | Hosts      |                   |
+-----------------+-----------------+------------+-------------------+

**8.5** **Reference Documents:**

> 1\) For current I/T planning information, the contractor may refer to
> the I/T Planning Process available on the JSC CIO web page. Such
> information will reflect NASA\'s implementation of the Office of
> Management and Budget\'s (OMB\'s) I/T planning, budgeting, and
> reporting requirements (as based on the Clinger-Cohen Bill, OMB
> Circulars, and applicable portions of OMB\'s Capital Programming
> Guide. The contractor is advised to review both the JSC I/T Planning
> process requirements and the JSC Chief Financial Officer\'s(CFO\'s)
> Program Operating Plan(POP) call.
>
> 2\) JSC memorandum AI-95-090 dated July 11, 1995, subject: Information
> Technology (I/T) Plans.
>
> 3\) JSC memorandum LB-97-13 dated March 11, 1997, subject: \"Program
> Operating Plan (POP) 97\".
>
> 4\) JSC memorandum AI-96-020 dated March 18, 1996, subject: \"FY97
> Information Technology Plans\".
>
> 5\) JSC memorandum AI-96-033 dated April 22, 1996, subject: \"Reminder
> and Clarification on Information Technology (I/T) Orders or
> Acquisition Reviews\".
>
> 6\) Office of Management and Budget Circular A-130.
>
> 7\) JSC\'s I/T Security Handbook (JSC 2410.11).
>
> 8\) Executive Order 12845, Energy-efficient Microcomputers.
>
> 9\) NASA CIO Executive Notices: 01-95 \"Conditional Freeze on purchase
> of I/T\"; 02-95 \"Internet Usage\"; 03-95 \"I/T Obsolescence
> Management\"; 06-95 \"Minimum Office Automation Software Suite
> Interface Standards and Product Standards\"; 07-95 \"Minimum Desktop
> Hardware Configuration\"; 08-95 \"WEB Home Page Naming and
> Ownership\"; and, 09-95 \"WAN Protocol Standard\".
>
> 10\) JSC Information Technology Handbook (NPG 2810).
>
> 11\) I/T Management Reform Act of 1996 (the \"Clinger-Cohen Bill\")

**8.6 Format**: The contractor shall conform to delivery media formats
and electronic data formats as specified in the JSC Information
Technology Handbook (NPG 2810).

**8.7 Maintenance**: Changes shall be incorporated by change page or
complete reissue.

Information Technology (I/T) Technology

Implementation Instructions

for

Data Requirements Description (DRD): I/T Plan and Reports

July 17, 1997

**LEVEL B I/T PLAN**

Figure 1 graphically depicts the I/T Planning Process. The first step in
the preparation of the Level B I/T Plan development is for the
contractor Task Order Managers to work in close coordination with their
NASA counterpart Task Order Monitors to determine the necessary I/T
requirements for the coming fiscal year for their respective task order.
Once the I/T requirements are identified, then through the negotiation
of the task order requirements, the decision of \"who buys\" (either
NASA or contractor ) the necessary I/T items for the task order is made.
NASA may prior to the negotiation of the task orders determine \"who
buys\" the necessary I/T items. If this is the case, the contractor will
be informed of the items that they will be tasked to procure.

Once the decision of \"who buys\" is determined, the contractor shall
review their identified I/T items internally for standards compliance
and adequacy for meeting I/T requirements. After the contractor internal
review for each task order within a division/office is completed, the
contractor shall consolidate their respective I/T requirements to form a
division/office\'s portion of the contractor contract-level Level B I/T
Plan. Each division/office\'s portion of the contractor Level B I/T Plan
shall be submitted to the respective NASA division/office\'s Information
Resource Management (IRM) Coordinator for concurrence. The contractor
shall be prepared to obtain review and concurrence from NASA
Branch-level IRM Coordinators for their respective portion of the
contractor Level B I/T Plan. The division/office-level IRM Coordinators
are itemized in Attachment 1. The IRM Coordinator listing with
individual names will be maintained and will reside in the ETAC Share
Area under path: Data on
\'Jsc-ifs-02\'/EA/Etac/Gen_Info/Seatmgmt/Interfaces/IRM Coordinators.
The contractor shall be prepared to present the division/office level B
plan to the cognizant division/office management for review and
concurrence.

When the NASA division/office IRM Coordinator concurrences are received,
the contractor shall combine the division/office portions to form an
Engineering (EA) Directorate portion of the contractor\'s Level B I/T
Plan and a Space and Life Sciences (SA) Directorate portion of the
contractor\'s Level B I/T Plan. The EA portion of the contractor Level B
I/T Plan shall be presented to the EA Directorate IRM Coordinator for
concurrences. A summary of the EA Directorate portion of the
contractor\'s Level-B I/T Plan shall be presented to EA Directorate
Management for concurrence. The SA portion of the contractor\'s Level B
I/T Plan shall also be presented to the SA Directorate IRM Coordinator
for concurrence. The contractor shall be prepared to present the SA
portion of the contractor\'s Level B I/T Plan to the SA Directorate
Management for review and concurrence. The names of the individual EA
and SA IRM Coordinators will be itemized in the IRM Coordinators listing
along with division/office IRM Coordinators retained on the ETAC Share
Area.

For the SA portion of the contractor\'s Level B I/T Plan, the contractor
shall input their respective SA I/T data into the SA Directorate\'s
Program Information Management System (PIMS). For coordination of this
activity, the contractor is advised to work closely with the SA
Directorate IRM Coordinator. Additionally, the contractor shall be
prepared, in close collaboration with the EA Directorate IRM
Coordinator, to pilot EA I/T data into the PIMS.

Once directorate-level steps and concurrences are complete, a
consolidated contractor\'s contract-level Level-B I/T Plan shall be
prepared. A summary of the contractor\'s contract-level Level-B I/T Plan
shall be presented to the IRM Steering Council and the JSC CIO for final
approval. Presentation of the contractor\'s contract-level Level B I/T
Plan to the IRM Steering Council and the JSC CIO shall be coordinated
through the NASA EA Directorate and SA Directorate IRM Coordinators.

Once all NASA concurrences and approvals have been granted, the JSC CIO
may delegate to the contractor the authority to approve the procurement
of specific I/T items on the contractor\'s contract-level Level B I/T
Plan so long as a SEAT Contract task order authorized by the SEAT
Contract Contracting Officer has been issued to do so regardless of the
government fiscal year the task order is issued.

![](media/image1.png){width="5.948611111111111in"
height="9.479861111111111in"}

+--------------------------------------+-------------------------------+
| Attachment 1                         |                               |
+--------------------------------------+-------------------------------+
| **IRM Coordinators for I/T Plan and  |                               |
| Reports**                            |                               |
|                                      |                               |
| **7/1/97**                           |                               |
+--------------------------------------+-------------------------------+
|                                      |                               |
+--------------------------------------+-------------------------------+
| **Name**                             | **Organization**              |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | EA/EV                         |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | EA/ISO                        |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | BE                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | EA                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | EA4                           |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | EA5                           |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | EC                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | EG                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | EM                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | EP                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | ER                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | ES                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | EV                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | EX                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | X-CRV                         |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | ECCS                          |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | ISC                           |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | SA/SL                         |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | SD                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | SM                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | SN                            |
+--------------------------------------+-------------------------------+
| IRM Coordinator                      | SP                            |
+--------------------------------------+-------------------------------+

<table>
<colgroup>
<col style="width: 28%" />
<col style="width: 6%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 1%" />
<col style="width: 14%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 21%" />
</colgroup>
<tbody>
<tr class="odd">
<td><p>1. DRD Title</p>
<p>Organization Report</p></td>
<td colspan="5"><p>2. Current Version Date</p>
<p>July 24, 1997</p></td>
<td colspan="2"><p>3. DRL Line Item No.</p>
<p>3</p></td>
<td colspan="3"><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>For use by NASA technical personnel to identify manpower reporting
structures, assist in evaluating manpower status, and identify
manpower</p></td>
</tr>
<tr class="odd">
<td colspan="2">5. DRD Category: <em>(check one)</em></td>
<td colspan="2"></td>
<td>Technical</td>
<td colspan="2">X</td>
<td colspan="2">Administrative</td>
<td></td>
<td>SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="3">6. References <em>(Optional)</em></td>
<td colspan="8">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

A. Organization Chart

1\. The Contractor shall submit an organization chart which identifies
the contractor\'s management reporting structure.

2\. The organization chart shall include a contractor data report of
personnel supporting the contract. The report shall include manager
code, employee name, employee code (Prime or subcontractor designation),
building number and site code. Individuals designated as supervisory
shall be indicated. Authorized but unfilled positions shall be noted.
The report shall include totals at the manager code, schedule and
contract levels.

3\. Reports will be submitted by the 10^th^ calendar day after the
reporting period ends on March 31, June 30, September 30, and December
31. Significant changes in key personnel or in the reporting structure
shall be submitted within 15 working days after the implementation of
such changes.

4\. All current personnel shall be listed in the data report.

B. Quarterly Manpower Report

1\. The contractor shall submit a Quarterly Manpower Report which will
contain, as a minimum, a manpower table for each Division/Office
supported, for each Directorate supported, and at a contract level
summary.

2\. The table shall reflect the number of employees, as of the last day
of the reporting period, in each NASA job classification and skill level
hourly rate of pay shall also be reflected for each NASA job
classification and skill level.

3\. Such comments, as may be necessary to convey the significant
personnel management information shall also be submitted. Employee
turnover rate shall be reported.

4\. The report shall be submitted by the 10^th^ calendar day after the
reporting period ends on March 31, June 30, September 30, and December
31.

5\. The quarters reporting shall be evenly divided with the Government's
fiscal year.

<table>
<colgroup>
<col style="width: 30%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 7%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Reliability and Maintainability (R&amp;M)
Plan</strong></p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>8 Oct 96</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>4</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>Used to assure proper implementation of R&amp;M quantitative
requirements. Used by program management to verify predictions,
allocations, etc., are consistent with program requirements.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>X</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4"><p>6. References <em>(Optional)</em></p>
<p>NHB 5300.4 (1D-2)</p></td>
<td colspan="7">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

**[Scope]{.underline}**: Formulate an R&M Plan to serve as a master
planning, program definition, and control document to govern the R&M
quantitative-related activities required for the project.

**[Format]{.underline}**: Each quantitative requirement shall be
addressed in narrative form and in sufficient detail to describe the
philosophy and approach for implementation. Existing policies and
procedures can be used if in total compliance with the requirements
stated below.

**[Contents]{.underline}**: The plan shall identify and define the
following as a minimum:

> a\) The work to be accomplished for each applicable task.
>
> b\) The time phasing and staff loading involved.
>
> c\) The organizational element assigned responsibility and authority
> for implementing the required task.
>
> d\) Lines of communication between the organizational element
> responsible for implementing the task and other interfacing
> organizational elements.
>
> e\) Appropriate NASA-contractor program milestone review points.
>
> f\) Method of control over subcontractor and vendor-related tasks.
>
> g\) The purpose and expected results of each task. Planned methods for
> monitoring, assessing, reporting, and taking appropriate action
> regarding status, accomplishments, and problems.
>
> h\) Specific techniques for allocating quantitative requirements to
> lower level functional elements of the system, subsystem, assembly, or
> components.
>
> i\) Specific techniques for making R&M predictions.
>
> j\) The method of data collection and analysis, and plan for ensuring
> an effective corrective action system.
>
> k\) Data base requirements.
>
> l\) Contents and submittal schedules of the prediction, allocation,
> assessment, and verification reports.
>
> m\) Means by which demonstration and verification will be
> accomplished.

JSC Form 2341 (Rev Dec 91) Page 1 of 1

<table style="width:100%;">
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 7%" />
<col style="width: 6%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 8%" />
<col style="width: 9%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Space Shuttle GFE Safety Analysis Report (SAR) and Hazard
Report (HR)[HR_1]</strong></p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>8 Oct 96</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>5</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>The SAR is used to document the safety analysis performed on a
system. The HR is used to provide program management the change in
risk.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="2">Technical</td>
<td colspan="2"></td>
<td colspan="2">Administrative</td>
<td>X</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="5"><p>6. References <em>(Optional)</em></p>
<p>See "Reference Documents" under item 8. below.</p></td>
<td colspan="6"><p>7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></p>
<p>SMACAR</p></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

Reference Documents:

a\. NHB 5300.4 (1D-2), "Safety, Reliability, Maintainability and Quality
Provisions for the Space Shuttle Program"

b\. JSC 17481A, \"Safety Requirements Document for JSC Space Shuttle
Flight Equipment\"

c\. NSTS 07700, vol. V, \"Information Management\"

SCOPE: A SAR and HR\'s are applicable to all Government-furnished
equipment (GFE) classified flight hardware.

FORMAT: The format of the SAR and HR\'s shall be in accordance with NSTS
22254 "Methodology for Conduct of Space Shuttle Program Hazard
Analyses\"

CONTENTS: The hardware provider shall provide the SAR and HR\'s for
program management visibility.

a\. SAR: A safety analysis shall be performed in accordance with NSTS
22254 and a SAR shall contain the following as a minimum:

> \(1\) System, subsystem, assembly, or item identifier
>
> \(2\) Event and mission phases considered.
>
> \(3\) Page, date, and revision number.
>
> \(4\) Identification of the preparer and approvals with signatures.
>
> \(5\) Description of the type of hazard analysis performed.
>
> \(6\) Analysis of each generic hazard listed in JSC 17481A and unique
> hazards showing applicability or inapplicability, controls, and
> verifications.
>
> \(7\) Safety matrix relating equipment subsystems to generic hazards.
>
> \(8\) Hazard list providing HR number, title, status, and
> classification for any baselined hazards.
>
> \(9\) Summary of open HR\'s with actions required for closure.
>
> \(10\) Summary of candidate accepted risks with acceptance rationale.

The SAR may be sufficed by a properly and completely filled out hazard
analysis worksheet or S&MA Certification Approval Request (SMACAR) in
situations where the system, subsystem, assembly, or item is non
critical, low cost, and not complex in design.

b\. HR\'s: If HR\'s are required based on the safety analysis performed,
the HR\'s shall comply with the requirements of NSTS 07700, volume V and
NSTS 22254. The HR\'s shall contain, by attachment, documentation of
work performed to support closure.

JSC Form 2341 (Rev Dec 91) Page 1 of 1

<table>
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 7%" />
<col style="width: 11%" />
<col style="width: 3%" />
<col style="width: 29%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title:</p>
<p><strong>Space Station Hazard Reports (HR's)/System Descriptions
[HR_2]</strong></p></td>
<td colspan="4"><p>2. Current Version Date:</p>
<p>8 Oct 96</p></td>
<td colspan="2"><p>3. DRL Line Item No.:</p>
<p>6</p></td>
<td><p>RFP/Contract No.:</p>
<p><em>(Procurement completes)</em> NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="10"><p>4. Use: <em>(Define need for, intended use of,
and/or anticipated results of data)</em></p>
<p>Station GFE HR's and System Descriptions are used by the Prime
Contractor to prepare an integrated Stage Hazard Analysis which will
entail the analysis of the interfaces between End Items on-orbit for
each mission in support of the Safety Review Panel and Ground Safety
Review Panel (GSRP).</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>X</td>
<td>SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4">6. References: <em>(Optional)</em></td>
<td colspan="6">7. Interrelationships: <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="4"></td>
<td colspan="6">SMACAR</td>
</tr>
<tr class="even">
<td colspan="10">8. Preparation Information: <em>(Include complete
instructions for document preparation)</em></td>
</tr>
</tbody>
</table>

This requirement shall consist of system descriptions with Hazard
Reports and their supporting data. The hazard reports and system
description will cover each element level end item for all phases.

The System Description shall describe the GFE (FLT, OSE, FSE, & GSE)
end-items and their systems and associated ground systems and support
equipment. The system description shall also include on-orbit assembly,
on-orbit operations and start-up sequences. Top-level
schematics/functional block diagrams that depict safety features shall
be provided.

The flight hazard reports shall address the element level end item
interfaces with PG end items, GFE, and CFE. For each subsequent revisit
to the station, each GFE provider will assess on-orbit configurations
changes to their End Item which may affect the safety of the station and
submit as applicable. A contract letter stating no impact is acceptable.
The GFE and Ground Operations hazard report will cover the Support
Equipment (GSE/TSE) interfacing with flight hardware at KSC as well as
the operations to process the flight hardware through KSC for
integration into the Orbiter.

CONTENT: Flight Hazard Reports and system descriptions shall be
submitted on each end-item and shall address hazards from launch through
return/decommissioning. The Hazard Reports document the results of the
safety analysis which is performed to identify hazards and their causes,
identify specific safety requirements and non-conformances, specify
control methods in the design, and identify verification activities for
each assembly mission.

Ground Hazard Reports and System descriptions shall address all hazards
associated with launch processing.

These submittals shall include the additional forms in Appendix C as
appropriate.

Hazard Reports shall be submitted with a level of maturity commensurate
with the hardware, software, and operations that are being reviewed.

Each review will address products with different levels of maturity. The
following table shall apply:

Product Maturity Review Phase Report Content

PDR I Hazards identified

CDR II Controls documented

Launch - 1 year III Verification complete\*

\* All verifications that are not complete at the Phase III level review
shall be documented in a verification matrix to be provided in block 5
\"status of open work\" of the hazard report.

The final submittal of hazard reports and system descriptions shall be
grouped by assembly mission. This grouping is necessary to support FRR.

Hazard reports and their supporting documentation for contractor
furnished equipment shall be delivered 90 days prior to the phase safety
review for which it is first manifested.

NEED DATE or MILESTONE REQUIRING CONTRACTOR SUPPLIED DATA SUPPORT:

Levels of data maturity referenced herein (Phase I, II, and III) are
defined in SSP 30309 Section 3.1.

1\) For GFE items which are part of flights 1A-6A:

> Phase I data needed 5-1-95
>
> Phase II data needed 9-13-95
>
> Phase III data needed no later than 18 months prior to launch date of
> the particular GFE item

2\) For GFE items which are part of flights 6R-12A:

> Phase I data needed 7-15-95
>
> Phase II data needed no later than 7 months prior to IDR #3
>
> Phase III data needed no later than 18 months prior to launch date of
> the particular GFE item

3\) For GFE items which are part of flights 9R-12R:

> Phase I data needed no later than 7 months prior to IDR #3
>
> Phase II data needed no later than 7 months prior to IDR #4
>
> Phase III data needed no later than 18 months prior to launch date of
> the particular GFE item

4\) For GFE items which are part of flights 1E-15A:

> Phase I data needed no later than 7 months prior to IDR #4
>
> Phase II data needed no later than 7 months prior to IDR #5
>
> Phase III data needed no later than 18 months prior to launch date of
> the particular GFE item

5\) For GFE items which are part of flights 16A-19A:

> Phase I data needed no later than 7 months prior to IDR #5
>
> Phase II data needed no later than 2 months prior to IDR #5
>
> Phase III data needed no later than 18 months prior to launch date of
> the particular GFE item

Note: the only definitive schedule for safety reviews currently
established with NASA is up to IDR#2; therefore, calendar dates are
identified for data needed to support IDR#2. After IDR#2, Contractor
supplied data need dates are defined relative to program milestones.

FORMAT: Formats for the Hazard Reports are contained in appendices to
this DRD. S&MA-4 shall be submitted in hard copy and in Microsoft Word.

Appendix A: Flight Hazard Analysis Report and System Description content

Appendix B: Ground Hazard Analysis Report and System Description content

Appendix C: Additional Forms

Appendix D: Hazard Report Format

**Appendix A**

Flight Hazard Analysis Report and System Description

Format and Content

Flight Hazard Analysis Report and System Description

Format and Content

**1.0 Scope**

Identify the hardware that was analyzed and the maturity (Phase 1, 2, 3)
of the analysis.

**2.0 System Description**

Describe the major end-items and their systems and associated ground
systems and support equipment. The system description shall also include
on-orbit assembly, on-orbit operations and start-up sequences. Top level
schematics / functional block diagrams that depict safety features shall
be provided.

**3.0 Supporting Data**

This section contains data that is important to the analysis and does
not fit in other sections. The contractor may determine how this section
is arranged.

**4.0 Hazard Reports and Substantiating Data**

This section shall include all hazard reports applicable for the
mission, supporting data, and additional forms as defined in Appendix C.

**Appendix B**

Ground Hazard Analysis Report and System Description Report

GROUND HAZARD ANALYSIS REPORT AND SYSTEM DESCRIPTIONS

FOR

PG-X

Prepared By:

*Name of Tier I Subcontractor\
*

Approved By:

  ----------------------------------- -----------------------------------
  Tier I Safety Manager               Tier I Subcontractor

                                      Vehicle AIT Manager

  Date:                               Date:
  ----------------------------------- -----------------------------------

  ----------------------------------- -----------------------------------
                                      Tier Program Manager

                                      Date:
  ----------------------------------- -----------------------------------

Ground Hazard Analysis Report and System Description Format and Content

1.0 Scope. Identify the hardware that was analyzed and the maturity of
the analysis.

2.0 GSE Design and Ground Operations. This section will be completed for
each PG-1 supported launch. This section includes:

1\) Cargo element/launch package description and brief mission scenario.

2\) Descriptions of GSE, cargo element/launch package subsystems that
are safety critical during ground processing, and their ground
operations. Schematics and block diagrams with safety features,
inhibits, etc., identified should be included.

3 Ground operations scenarios or a brief description of the in-line and
off-line sequencing of ground processing tasks, including transport,
receipt, assembly, test/checkout and ultimate usage.

3.0 Supporting Data. This section contains data that is important to the
analysis and does not fit in other sections. Tier 1 contractor may
determine how this section is arranged.

4.0 Hazard Reports and Substantiating Data. This section shall include
all hazard reports applicable for the mission.

**Appendix C**

Additional Forms

**Appendix D**

Hazard Report Form

Format and Content

D-1. Hazard Reports shall be delivered in Microsoft Word format.

D-2. The following format and structure shall apply.

**TEAM NAME**

**International Space Station**

**Hazard Report Number \_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**1. HAZARD TITLE:**

a\. Review Level:

b\. Review Date:

c\. Scope:

**2. HAZARD CONDITION DESCRIPTION:**

**3. CAUSE SUMMARY**

+---------------------------+-------+-------+-------+-------+-------+
|                           | *     | *     | *     | *     | *     |
|                           | *2A** | *3A** | *4A** | *5A** | *6A** |
+---------------------------+-------+-------+-------+-------+-------+
| **Cause 1**               |       |       |       |       |       |
+---------------------------+-------+-------+-------+-------+-------+
| # Control 1               |       |       |       |       |       |
+---------------------------+-------+-------+-------+-------+-------+
| **Control 2**             |       |       |       |       |       |
+---------------------------+-------+-------+-------+-------+-------+
| **Cause 2**               |       |       |       |       |       |
+---------------------------+-------+-------+-------+-------+-------+
| # Control 1               |       |       |       |       |       |
+---------------------------+-------+-------+-------+-------+-------+
| **Cause n**               |       |       |       |       |       |
+---------------------------+-------+-------+-------+-------+-------+
| # Control 1               |       |       |       |       |       |
+---------------------------+-------+-------+-------+-------+-------+
| **Control 2**             |       |       |       |       |       |
+---------------------------+-------+-------+-------+-------+-------+

1\. Title:

SEVERITY: LIKELIHOOD:

2\. Title:

SEVERITY: LIKELIHOOD:

n\. Title:

SEVERITY: LIKELIHOOD:

**4. PROGRAM STAGE(S):**

**5. INTERFACES:**

**6. STATUS OF OPEN WORK: (Phase III Only)**

**7. REMARKS:**

**8. SUBMITTAL CONCURRENCE:**

  ------------------------------------- ---------- ----------------------
                                                   

  Tier 1 Subcontractor Safety Manager              Date

                                                   

  Tier 1 Integrated Product Team                   Date
  Manager                                          

                                                   

  Tier 1 Program Manager                           Date
  ------------------------------------- ---------- ----------------------

**9. APPROVAL:**

  ----------------------------------- -- --------------------------------
                                         

  S&MA Lead/NASA                         S&MA Lead/Boeing Prime
  ----------------------------------- -- --------------------------------

**Hazard Report Number \_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**CAUSE 1**

**1. HAZARD CAUSE DESCRIPTION:**

**SEVERITY: LIKELIHOOD:**

**2. CONTROL(S):**

Control 1.

Control 2.

Control 3.

**3. METHOD FOR VERIFICATION OF CONTROL(S):**

Verification of Control 1

Verification of Control 2

Verification of Control n

**4. SAFETY REQUIREMENT(S):**

Document: Paragraph:

Title:

Document: Paragraph:

Title:

**5. MISSION PHASE(S):**

**\_\_\_\_**Launch Processing:

**\_\_\_\_**Launch:

**\_\_\_\_**Rendezvous/Docking:

**\_\_\_\_**Deployment:

**\_\_\_\_**Orbital Assembly & Checkout:

**\_\_\_\_**On-Orbit Operation:

**\_\_\_\_**On-Orbit Maintenance:

**\_\_\_\_**Return/Decommissioning:

**6. PROGRAM STAGE(S):**

**7. DETECTION AND WARNING METHOD(S):**

**8. CAUSE REMARKS:**

**9. CIL REFERENCE:**

**10. POINT OF CONTACT:**

Name: Telephone:

**Hazard Report Number \_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**CAUSE 2**

**1. HAZARD CAUSE DESCRIPTION:**

**SEVERITY: LIKELIHOOD:**

**2. CONTROL(S):**

Control 1.

Control 2.

Control 3.

**3. METHOD FOR VERIFICATION OF CONTROL(S):**

Verification of Control 1

Verification of Control 2

Verification of Control n

**4. SAFETY REQUIREMENT(S):**

Document: Paragraph:

Title:

Document: Paragraph:

Title:

**5. MISSION PHASE(S):**

**\_\_\_\_**Launch Processing:

**\_\_\_\_**Launch:

**\_\_\_\_**Rendezvous/Docking:

**\_\_\_\_**Deployment:

**\_\_\_\_**Orbital Assembly & Checkout:

**\_\_\_\_**On-Orbit Operation:

**\_\_\_\_**On-Orbit Maintenance:

**\_\_\_\_**Return/Decommissioning:

**6. PROGRAM STAGE(S):**

**7. DETECTION AND WARNING METHOD(S):**

**8. CAUSE REMARKS:**

**9. CIL REFERENCE:**

**10. POINT OF CONTACT:**

Name: Telephone:

[SDRL Specifications:]{.underline}

SEQUENCE NUMBER

TITLE OR DESCRIPTION OF DATA: Hazard Analysis Report and System
Description

CONTRACT NUMBER:

STATEMENT OF WORK PARA:

AUTHORITY: (DID / SDS No.) SMA-4

NASA OFFICE OF PRIME RESPONSIBILITY: S&MA

TRANSMITTAL BY: (DD Form 250 / 1149 / Letter)

NASA DOCUMENT TYPE: (Type 1 / 2 / 3 ) Type 3

ELECTRONIC SUBMITTAL REQUIRED: Y

FREQUENCY:

AS OF DATE:

DATE OF 1ST SUBMISSION:

DATE OF SUBSEQUENT SUBMISSION / EVENT ID:

DISTRIBUTION AND ADDRESSES:

-   Submittal of S&MA-4 is forty-five (45) days prior to each IDR \*.

-   Hazard reports shall be delivered in Microsoft Word\*\*.

-   Hazard reports and their supporting verification documentation for
    each intersite deliverable item shall be delivered ninety (90) days
    prior to the safety review for which it is first manifested \*.

\* Note: Safety reviews will be accomplished during, and in conjunction
with the IDRs.

\*\*Note: Supporting data to each hazard report may be submitted by hard
copy.

<table>
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 1%" />
<col style="width: 12%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 14%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 29%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title:</p>
<p><strong>Safety Plan</strong></p></td>
<td colspan="4"><p>2. Current Version Date:</p>
<p>8 Oct 96</p></td>
<td><p>3. DRL Line Item No.:</p>
<p>7</p></td>
<td colspan="3">RFP/Contract No.:<em>(Procurement completes)</em> NAS
9-19100</td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use: <em>(Define need for, intended use of,
and/or anticipated results of data)</em></p>
<p>Establishes system safety tasks and activities to identify, evaluate,
and eliminate, or control hazards associated with flight hardware and
operations.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="2">Technical</td>
<td colspan="2"></td>
<td colspan="3">Administrative</td>
<td>X</td>
<td>SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="5"><p>6. References: <em>(Optional)</em></p>
<p>See "Reference Documents" under item 8 below.</p></td>
<td colspan="6"><p>7. Interrelationships: <em>(e.g., with other
DRDs)(Optional)</em></p>
<p>SMACAR; HR; RAESR</p></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information: <em>(Include complete
instructions for document preparation)</em></td>
</tr>
</tbody>
</table>

**Reference Documents**:

> JSCM 1700.1, as revised, \"JSC Safety Manual\"
>
> MIL-STD-882B, \"System Safety Program for Systems and Associated
> Subsystems and
>
> Equipment, General Requirements for\"
>
> NHB 5300.4, 1D-2, \"Safety, Reliability, Maintainability, and Quality
> Provisions for the Space Shuttle Program\"
>
> JSC 17773, as revised, \"Instruction for Preparation of Hazard
> Analyses for JSC Ground Operations\"
>
> JSC 17481, as revised, \"Safety Requirements Document for Space
> Shuttle Flight Equipment\"
>
> NSTS 22254, as revised, \"Methodology for Conduct of Space Shuttle
> Program Hazard Analyses\"
>
> SSP 50021 \"Safety Requirements for Space Station\"
>
> SSP 50038 \"Computer Based Control System Safety Requirements\"
>
> SSP 30309 \"Safety Analysis and Risk Assessment Requirements
> Document\"
>
> SSP 30599 \"Safety Review Process for Space Station\"
>
> NHB 1700.1 (V1-B & V2) \"Guidelines for Mishap Investigation\"

**SCOPE**:

The Safety Plan shall addresses safety policy, applicable documents,
task descriptions, products, and processes during the design,
development, test, production, and operational phases of flight
hardware. The Safety Plan shall set forth safety tasks, products, and
processes. It serves as a planning and management tool for ensuring
safety tasks are performed as an integral part of the design,
development, test, production, and operational phases of the end items.
Implementation of the Safety Plan shall assure hazards and their
consequences are identified, evaluated, and controlled throughout all
phases of the program in accordance with NHB 1700.1 (V1-B), \"NASA
Safety Policy and Requirements Document,\" paragraphs 104, 108, and 310.
Safety Plans are to be tailored for individual safety engineering
projects as integral parts of a formal, disciplined system safety
program implemented by NASA and the contractor Safety Plan Requirements.

**FORMAT and CONTENTS**:

1\. **Introduction**

2\. **General**. The Safety Plan shall be documented in narrative format
and shall:

2.a Describe the scope of the project for which the safety engineering
activity is to be tailored.

2.b Describe any interrelationships to other contract requirements,
tasks and functional elements including appropriate cross references to
minimize duplication.

2.c List the contractor and NASA documents which will be applied either
as directives or as guidance in the conduct of the Safety Plan and
related system safety tasks.

2.d Identify the system safety engineering requirements, tasks, and
responsibilities on an item-by-item basis in accordance with the
schedule.

3.0 **Safety Engineering Organization**. The Safety Plan shall describe:

3.0.a The system safety organization or function within the organization
of the contract including charts to show the organizational and
functional relationships and lines of communication.

3.0.b The responsibility, authority, and accountability of system safety
personnel and other contractor organizational elements (including
subcontractors) involved in the system safety effort. Identify each
organizational unit responsible for executing each task. Identify the
authority in regard to resolution of all identified hazards. Include the
title, address, and telephone number of the System Safety Program
Manager.

3.0.c The staffing of the system safety organization for the duration of
the project including manpower loading and qualifications of assigned
key personnel.

3.0.d The procedures by which the contractor will integrate and
coordinate the system safety efforts. Include methods of dissemination
of system safety requirements to action organizations and
subcontractors; coordination of subcontractors\' system safety programs;
integration of hazard analyses; management and engineering reviews;
program status reporting; and the identities and charters of any system
safety groups.

3.0.e. The process through which contractor management decisions will be
made to include notification and subsequent actions for the following:
critical and catastrophic hazards; corrective actions taken; mishaps or
malfunctions; waivers to safety requirements; and program deviations.

3.0.f. The interfaces between the system safety organization and all
other applicable disciplines such as Engineering, Occupational Safety
and Health, Reliability, Quality Assurance, Medical Support, etc., at
all levels of the project (NASA, contractor, and subcontractor.)

3.1 **Safety Project Milestones**. The Safety Plan shall:

3.1.a Identify safety milestones required to accomplish evaluations of
the effectiveness of the system safety effort at critical safety
checkpoints (such as design reviews, self-evaluations, operational
readiness reviews, audits, etc.)

3.1.b Provide a contract schedule of safety tasks showing start and
completion dates, reports, reviews, and manloading, in relationship to
other contract milestones.

3.1.c To preclude duplication, identify integrated system activities
(i.e., design analyses, test, demonstrations, etc.) applicable to the
system safety program but specified within other engineering tasks.
Include as part of this section the estimated system safety manpower
loading required to accomplish these integrated tasks.

3.2 **Safety Requirements**. The Safety Plan shall:

3.2.a Describe or reference the methods that will be used to identify
and apply hazard control requirements and criteria for the design and
operation of equipment, software, and facilities, and for procedures
covering all phases of acquisition specified in the schedule. List the
safety standards and system specifications which are the sources of
safety requirements with which the contractor either is required to
comply or intends to adopt as a requirement.

3.2.b Describe the risk assessment procedures including the hazard
severity categories, hazard probability (or frequency) levels, the
precedence to be followed in satisfying safety requirements. State any
qualitative or quantitative measures of system safety which the
contractor is required to meet, including a description of the
acceptable risk levels. Include system safety definitions which are in
addition to those in JSC documents or are unique to the project covered
by the Safety Plan.

3.2.c Describe the management controls that shall be used to ensure
compliance or justify waivers and deviations with general design and
operational safety criteria and the closed loop procedures to ensure
hazard resolution and control.

3.3 **Hazard Analyses**. The Safety Plan shall describe:

3.3.a The analysis techniques and format that will be used in
qualitative and quantitative analysis to identify hazards, their causes
and effects, and recommended corrective actions.

3.3.b The depth to which each analysis technique will be used within the
system, operation, or scenario being analyzed. This description will
include identification of hazards associated with the system, subsystem,
components, personnel, support equipment, government furnished
equipment, facilities, and their interrelationships in the logistics
support, training, maintenance, transportability, operational
environments, and phase out or disposal.

3.3.c The integration of subcontractor hazard analyses and techniques
within the overall project including contractor hazard analyses.

3.3.d The techniques to be used to establish a single closed loop
tracking system.

3.4 **Safety Data**. The Safety Plan shall:

3.4.a Describe the approach for researching, disseminating, and
analyzing pertinent historical hazard or mishap data.

3.4.b Identify deliverable data and the level of approval required for
customer acceptance. Attach a copy of the appropriate sheets from the
data requirements list (DRL) of the schedule.

3.4.c Identify safety related non-deliverable data and describe the
procedures for accessibility by NASA and the retention of data.

3.5. **Safety Verification and Audits**. The plan shall describe:

3.5.a The verification and audit requirements and procedures for
ensuring that the objectives and requirements of the system safety
program have been adequately demonstrated and implemented.

3.5.b The procedures for ensuring feedback of safety-pertinent
information for management and engineering review and analysis.

3.5.c The review procedures established by the contractor\'s system
safety organization to ensure safe conduct of hazardous tests with
particular emphasis on those involving human test subjects.

3.6 **Training**. Describe techniques and procedures to be used by the
contractor to ensure that the objectives and requirements of the system
safety program are implemented in training for engineers, test subjects,
technicians, operators, and support (including maintenance) personnel.

4.0 **Safety Review Process**.

4.0.a The safety process shall be based on the hardware design and
development schedule. Hardware and safety engineers will work all safety
issues associated with the hardware. Safety analysis begins at the
hardware\'s concept phase and continues through the life cycle of the
hardware.

4.0.b For Prime Contractor integrated hardware items, the safety process
will include safety data deliveries to the Prime in support of the
Safety Review Panel (SRP) and Incremental Design Review (IDR) flight
group schedules. The Prime will perform the integrated safety analysis
for this hardware and present the integrated safety analysis to the
Safety Review Panel (SRP).

4.0.c For Non-Prime hardware items, phase safety data packages will be
delivered 45 days prior to a scheduled SRP meeting.

4.1 **Phase 0 Safety Process**

A Phase 0 Safety Review may be conducted after the Concept Design
Review. The hardware and safety engineers will identify the applicable
safety requirements and estimate the level and amount of documentation
needed with a documentation deliverable schedule. A formal SRP
presentation is not required, but may be beneficial for complex hardware
items.

4.2 **Phase I Safety Process**

4.2.a Prior to the Phase I Safety Review and the Preliminary Design
Review (PDR), the hardware and safety engineers will identify all
potential inherent hazards, fault hazards, operational hazards and
causes for hazards associated with the hardware. The hazards will then
be assessed for severity and likelihood as defined in NSTS 22254 and SSP
30309. Low severity hazards (category III and lower) will result in
documentation in the SAR. High severity hazards will be identified in
the SAR with a formal hazard report written. Controls for hazards will
be employed with preliminary methods identified to verify all hazard
controls.

4.2.b At the PDR, when approximately 10% of the design is complete, all
potential hazards, causes and effects will be documented. Review item
discrepancies will be written when safety requirements have not been met
or adequately controlled. The RID board will disposition the RIDs and
determine if any design change solution is available.

4.2.c Once any changes from the RIDs and other comments have been
incorporated, the SAR and HRs will be taken by the hardware engineer and
the safety engineer to be reviewed by the ISS SRP or the Shuttle System
Safety Review Panel (SSRP). The ISS SRP and the Shuttle SSRP have final
signature authority for acceptance of the hazard reports for the Phase I
level of maturity.

4.2.d The hardware engineer will continue with the design process for
the hardware and perform the necessary iterations of the hazard analysis
as the design matures.

4.3 **Phase II Safety Process**

4.3.1 The Phase II Safety Review is conducted after the Critical Design
Review (CDR) when approximately 90% of the design is complete.

4.3.2 The SAR and HRs shall be completed so that:

4.3.2.a All system level, assembly, operational and interface hazards,
and hazard causes have been identified;

4.3.2.b A means for eliminating, reducing, or controlling the risk has
been defined and implemented; and

4.3.2.c Specific verification methods have been finalized.

4.3.3 The hazard reports will be formally presented during the CDR
presentation. Verification test procedures related to hazard controls
and retention rationale will be reviewed as well.

4.3.4 The RID board will disposition new RIDs and determine if any
design change solution is available. Once any changes from the RIDs and
other comments have been incorporated, the SAR and HRs will be taken by
the hardware engineer and the safety engineer to be reviewed by the ISS
SRP or the Shuttle SSRP.

4.3.4 The ISS SRP and the Shuttle SSRP have final signature authority
for acceptance of the hazard reports for the Phase II level of maturity.

4.4 **Phase III Safety Process**

4.4.a The Phase III Safety Review is accomplished after the Design
Certification Review (DCR). The safety analysis and safety verification
activities should be complete for the hardware to allow safety
certification and program management acceptance.

4.4.b The hardware engineer, safety engineer, and the appropriate review
panel approves the hardware certification report, and signs off the
completed safety documentation.

4.4.c The hardware engineer is responsible for the technical content,
the S&MA engineer verifies the information is correct, and the review
panel provides the management signature.

5.0 **Appendices**

5.1 **Safety Analysis Report (SAR)**: See data requirements description
on \"SARs.\"

5.2 **Hazard Report (HR)**: See data requirements description on
\"HRs.\"

5.3 **Mishap and Investigation Reports**: See data requirements
description on \"Mishap and Investigation Reports.\"

<table>
<colgroup>
<col style="width: 30%" />
<col style="width: 2%" />
<col style="width: 8%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 10%" />
<col style="width: 8%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 25%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Space Shuttle GFE Failure Modes and Effects Analysis (FMEA)
and Critical Items List (CIL)[FMEA_1]</strong></p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>8 Oct 96</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>8</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>To identify to program management the risk associated with design,
use, and failure of systems.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="2">Technical</td>
<td colspan="2"></td>
<td colspan="2">Administrative</td>
<td>X</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="5"><p>6. References <em>(Optional)</em></p>
<p>See "Reference Documents" under item 8. below.</p></td>
<td colspan="6">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

Reference Documents:

a\. NHB 5300.4 (1D-2), "Safety, Reliability, Maintainability and Quality
Provisions for the Space Shuttle Program"

SCOPE: The FMEA and CIL are applicable to all Government-furnished
equipment classified as flight hardware.

FORMAT: Electronic delivery or through data keyed directly into the NASA
application. (JSC will identify the available application.) The format
of the FMEA and CIL shall be in accordance with NSTS 22206 "Instructions
for Preparation of Failure Modes and Effects Analysis FMEA) and Critical
Items List (CIL).

. A suggested format is provided, with the numbers in parentheses
corresponding to the data elements in NSTS 22206, table 3.0 for FMEAs
and table 4.0 for CILs. Other formats are acceptable provided all FMEA
data elements are included.

CONTENTS: The hardware provider shall provide FMEAs and CILs for project
and program management.

An FMEA shall be performed on every system, subsystem, assembly, or item
to identify failure modes and the effects thereof for support of
additional design action, safety analysis, hardware/software interface
analysis, test planning, mission planning, preparation of mandatory
inspection points, fault detection and isolation, maintainability
analysis and planning, maintenance planning, and logistics planning.

The FMEA shall be conducted and prepared in accordance with NSTS 22206.
The FMEA may be sufficed by a properly completed criticality worksheet
alone if the system, subsystem, assembly, or item under analysis is
noncritical.

The CIL is used to identify critical items which require special risk
assessments to support the activities supported by the FMEA and waivers
to program requirements. The CIL shall be conducted and prepared in
accordance with NSTS 22206.

**FAILURE MODE EFFECTS ANALYSIS/CRITICAL ITEMS LIST**

**FMEA NUMBER: ORIGINATOR PROJECT:**

**PART NAME: LRUPART NUMBER: QUANTITY:**

**PART NUMBER: LRU/ORU PART NAME: SYSTEM:**

**LSC CONTROL NO: DRAWING/REF DESIGNATOR: SUBSYSTEM:**

**ZONE/LOCATION: EFFECTIVITY/AFFECT STAGE:**

**[CRITICALITY:]{.underline}**

**CRITICAL ITEM?**

**CRITICALITY CATEGORY\_\_\_\_**

**[REDUNDANCY SCREEN:]{.underline}**

**[ORBITER/SPACE STATION]{.underline}**

**A -**

**B -**

**C -**

**D.-**

**FUNCTION:**

**FAILURE MODE CODE:**

**FAILURE MODE:**

**CAUSE:.**

**FAILURE DETECTION:**

**REMAINING PATHS: EFFECT/ MISSION PHASE:**

**\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_CORRECTIVE
ACTION:**

**-FAILURE EFFECTS-**

**END ITEM/LRU/ORU/ASSEMBLY:**

**SUBSYSTEM/NEXT ASSEMBLY/INTERFACE:**

**SYSTEM/END ITEM/MISSION:**

**CREW/VEHICLE :**

FAILURE MODE EFFECTS ANALYSIS/CRITICAL ITEMS LIST

**FMEA NUMBER: ORIGINATOR PROJECT:**

**PART NAME: LRUPART NUMBER: QUANTITY:**

**PART NUMBER: LRU/ORU PART NAME: SYSTEM:**

**LSC CONTROL NO: DRAWING/REF DESIGNATOR: SUBSYSTEM:**

**ZONE/LOCATION: EFFECTIVITY/AFFECT STAGE:**

**HAZARD INFORMATION:**

**HAZARD: YES\_\_\_ NO\_\_**

**HAZARD ORGANIZATION CODE:**

**HAZARD NUMBER:**

**TIME TO EFFECT:**

**TIME TO DETECT:**

**TIME TO CORRECT:**

**FAILURE DETECTION/FLIGHT:**

**REMARKS:**

**-RATIONALE FOR ACCEPTABILITY-**

**(A) DESIGN:**

**(B) TEST:**

**(C) INSPECTION:**

**(D) FAILURE HISTORY:**

**(E) OPERATIONAL USE:**

**(F) MAINTAINABILITY:**

**PREPARED BY: REVISION:**

**DATE: WAIVER NUMBER**

<table>
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 8%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 7%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 27%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Space Station GFE Failure Modes Effects and Analysis (FMEA)
and Critical Items List (CIL)</strong>
<strong>[FMEA_2]</strong></p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>8 Oct 96</p></td>
<td colspan="3"><p>3. DRL Line</p>
<p>9</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>To identify failure modes and effects, and critical items to support
risk assessment, additional design action, safety analysis,
hardware/software interface analyses, test planning, mission planning,
preparation of mandatory inspection points, fault detection and
isolation, maintainability analyses and planning, maintenance planning
and logistics planning.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>X</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4">6. References <em>(Optional)</em></td>
<td colspan="7">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

SCOPE: Identification of failure modes and effects, and critical items
to support risk assessment, additional design action, safety analyses,
hardware/software interface analyses, test planning, mission planning,
preparation of mandatory inspection points, fault detection and
isolation, maintainability analyses and planning, maintenance planning,
and logistics planning.

The flight hardware and Ground Support Equipment FMEA/CIL shall be
documented in accordance with SSP 30234, \"Instructions for Preparation
of Failure Modes and Effects Analysis (FMEA) and Critical Items List
(CIL) for the International Space Station.\"

FORMAT: The flight hardware FMEA/CIL worksheets shall be prepared in
accordance with SSP 30234. Other information supporting the FMEA/CIL
(summary tables, ground-rules and assumptions, reliability block
diagrams, incomplete design areas) will be part of the R&M Predictions
Report (SS-SM-005).

A Critical Items List (CIL) for Ground Support Equipment (GSE) shall be
submitted in hardcopy form only, in subcontractor format, as part of the
R&M Predictions Report (SS-SM-005).

FMEA/CIL worksheets shall be submitted electronically in a delimited
flat ASCII database file per SSP 30234.

NEED DATE or MILESTONE REQUIRING FMEA/CIL DATA SUPPORT:

The FMEA/CIL data requirements applies to all flight (including OSE,
FSE) hardware and must be assessable in the Vehicle Master Database
(VMDB) 145 days prior to the IDR that covers the first flight deployment
of the hardware.

The data provided for the first applicable IDR may be preliminary data
(data integrity equivalent to that expected at a PDR). If the initial
submittal is preliminary data, final data must be provided to support a
subsequent IDR (data integrity equivalent to that expected at a CDR).

Multiple deliveries of the GFE do not require corresponding data
deliveries.

Note: This DRD also applies to GSE required to support the flight
hardware.

[SDRL Specifications:]{.underline}

SEQUENCE NUMBER:

TITLE OR DESCRIPTION OF DATA: *Failure Modes and Effects Analysis (FMEA)
and Critical Items List (CIL)*

CONTRACT NUMBER:

STATEMENT OF WORK PARA:

AUTHORITY: (DID/SDS No.) 6

NASA OFFICE OF PRIME RESPONSIBILITY: *S&MA*

TRANSMITTAL BY:

NASA DOCUMENT TYPE:

ELECTRONIC SUBMITTAL REQUIRED: *Yes*

FREQUENCY:

AS OF DATE:

DATE OF 1ST SUBMISSION:

DATE OF SUBSEQUENT SUBMISSION / EVENT ID:

DISTRIBUTION AND ADDRESSES:

Remarks:

Applicable Code: Critical item worksheets (Flight Hardware and GSE
Hardware) shall be Type 1. Remainder of document shall be Type 3.

Frequency, Date of first Submission, and Date of Subsequent
Submission/Event ID: Initial Submittal shall be 180 days after contract
start date. Subsequent submittals shall be thirty (30) days prior to
program milestone reviews as determined by program milestone review
plan. Quarterly delivery of working files provided electronically in a
delimited flat ASCII database file per SSP 30234. A Critical items list
(CIL) for Ground Support Equipment (GSE) shall be submitted in hardcopy
form only, in Product Group format.

Note: FMEA/CIL supporting information (summary tables, ground rules and
assumptions, reliability block diagrams, incomplete design areas) are
reported as part of SS-SM-005 (R&M Predictions Report).

**INTERNATIONAL SPACE STATION**

**FAILURE MODE AND EFFECTS ANALYSIS**

**WORKSHEET HEADER PAGE**

**PREPARED BY DESIGN**

**PREPARED BY RELIABILITY**

**FMEA WORKSHEET NUMBER:**

**ORIGINAL DATE:**

**FLIGHT/GSE:\
END ITEM:\
SYSTEM:\
SUBSYSTEM:\
SEGMENT FUNCTION:**

**END ITEM FUNCTION:**

**SOFTWARE INTERFACE:\
ORU NAME:\
ORU NO:**

**CRITICALITY 1 DURING MAINTENANCE:\
SUCCESS PATHS:\
SUCCESS PATHS REMAINING:**

**PART NAME:**

**PART NUMBER:**

**DRAWING NUMBER:**

**LCN/REF.DES:**

**QTY:**

**ITEM FUNCTION:**

**WORKSHEET NUMBER:\
FAILURE MODE CODE:**

**FAILURE MODE TEXT:**

**CRITICAL ITEM (Y/N):\
IS FUNCTION RESTORABLE ON-ORBIT:\
CHECKOUT PRELAUNCH:\
CHECKOUT ON-ORBIT:\
DETECTABILITY GROUND CREW:\
DETECTABILITY FLIGHT CREW:\
LOSS OF REDUNDANCY FROM A SINGLE CAUSE:**

**CAUSE: 1:**

**CAUSE: 2:**

**CAUSE: 3:**

**CAUSE: 4:**

**CAUSE: 5:**

**CAUSE: 6:**

**STAGE(S) AFFECTED:**

**ORU/ASSEMBLY\
MISSION PHASES FAILURE EFFECT**

**A. PRELAUNCH**

**B. TRANSPORTATION**

**C. ASSEMBLY**

**D. OPERATIONS**

**E. RETURN**

**SUBSYSTEM/NEXT ASSEMBLY\
MISSION PHASES FAILURE EFFECT**

**A. PRELAUNCH**

**B. TRANSPORTATION**

**C. ASSEMBLY**

**D. OPERATIONS**

**E. RETURN**

**END ITEM/SEGMENT\
MISSION PHASES FAILURE EFFECT**

**A. PRELAUNCH**

**B. TRANSPORTATION**

**C. ASSEMBLY**

**D. OPERATIONS**

**E. RETURN**

**CREW/ISS/ACRV/ORBITER\
MISSION PHASES FAILURE EFFECT**

**A. PRELAUNCH**

**B TRANSPORTATION**

**C. ASSEMBLY**

**D. OPERATIONS**

**E. RETURN**

**SOFTWARE INTERFACE EFFECT:**

**TIME TO EFFECT: QTY: UNITS:**

**TIME TO DETECT: QTY: UNITS:**

**CRITICALITY: MSN PHASES:**

**CORRECTIVE ACTION:**

**FAILURE DET/VERIF:**

**WORKSHEET REMARKS:**

> **HAZARD:\
> HAZARD DOCUMENT ORGANIZATION CODE:\
> HAZARD NUMBER:\
> HAZARD DOCUMENT TITLE:**

<table>
<colgroup>
<col style="width: 31%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 4%" />
<col style="width: 10%" />
<col style="width: 4%" />
<col style="width: 16%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 19%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Parts Control Plan</strong></p></td>
<td colspan="3"><p>2. Current Version Date</p>
<p>3/26/97</p></td>
<td><p>3. DRL Line Item No.</p>
<p>10</p></td>
<td colspan="3"><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS9-19100</p></td>
</tr>
<tr class="even">
<td colspan="10"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>To describe and document the contractor's system for controlling
flight hardware parts selection; reduction in number of types; parts
controlling specifications system; parts qualification and suitability
for the application; qualified supplier selection and control; receiving
inspection, traceability, and handling controls; and hardware assembly
and as-built documentation.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>x</td>
<td>SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4">6. References <em>(Optional)</em></td>
<td colspan="6">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="10">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

The contractor shall use NHB 5300.4 (1D-2) and SSP 30312 as the
requirements documents when preparing their plan. The contractor plan
must implement the intent of these documents.

1\. Parts Selection: The Parts Control Plan shall describe a concurrent
engineering process, integrated with hardware design, in which parts are
selected for use in hardware on the basis of suitability for the
intended application. The plan shall identify parts that are considered
standard and how other (nonstandard) parts will be evaluated and
controlled. As a cost-control initiative and without overly limiting the
designer\'s ability to select emerging technologies, the plan will
address how the system will limit the number of different part types and
the number of nonstandard parts used in hardware design.

2\. Controlling specifications: Parts shall be controlled by
specifications which delineate as a minimum:

> a\. Complete identification of the part.
>
> b\. Physical, environmental, and performance specifications.
>
> c\. Reliability requirements, including inspections and tests for
> qualification, acceptance, and lot sampling.
>
> d\. Special handling, packaging, and storage requirements.
>
> e\. Documentation, data retention, and submittal requirements.

3\. Part Qualification:

> a\. Parts shall be qualified to the requirements of the controlling
> specification. Part qualification must demonstrate that the part meets
> its ratings, that it is suitable for the application, and that the
> manufacturer is using materials, processes, design, and quality
> controls that will produce a reliable, high quality device.
>
> b\. Where adequate qualification data are not available, the plan
> shall describe the process of qualification testing to demonstrate
> that the part meets its ratings and that it is suitable for the
> application.
>
> c\. Parts shall be requalified in the event of manufacturer process
> changes, or when a new lot of qualified parts is procured and it
> cannot be documented that the parts manufacturer has not changed the
> materials or processes used to manufacture the part.
>
> d\. The plan shall address how the contractor will document and
> maintain the documentation to support the \"qualified status\" of
> parts and the respective suppliers.

4\. Design Configuration Acceptability and Control: The plan must
address how the selected parts for a design are reviewed for suitability
for the application and environment, how the parts quality and
reliability will meet the operational performance requirements, and if
the parts are being used within the specific device ratings (including
the NASA derating policy). The selection process, technical
acceptability of devices, and 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 (including radiation effects), and nonstandard parts
acceptability assessments.

5\. Parts Procurement: The plan must address how the contractor will
select, qualify, control, and monitor parts manufacturers. The
procurement must address the contractor\'s source inspections, receiving
inspection (including destructive physical analysis), and stocking and
handling procedures prior to and during assembly. These procedures must
address how the contractor will avoid the procurement and any subsequent
installation of parts or \"lots\" of parts subject to conditions
identified in GIDEP and NASA ALERT\'s. This section of the plan must
ensure that the selection and use of the parts will not have an
\"obsolescence\" issue.

6\. Radiation Effects: The Parts Control Plan must include the following
requirements:

> a\. It must be shown by analysis or test that Single Event Upset (SEU)
> or total dose radiation effects will not cause Electrical, Electronic,
> or Electromechanical (EEE) parts to fail or malfunction in such a
> manner as to cause a safety hazard or loss of a mission.
>
> b\. EEE parts that are used to control a hazard, or as part of a
> subsystem that controls a hazard must be immune to the SEU and total
> dose radiation environment to which they will be exposed. This
> requirement can be waived in the event that a radiation hard, or
> purely mechanical (for example, a fuse, circuit breaker, mechanical
> thermostat, or pressure relief valve) device is used as a backup
> hazard control.

7\. Commercial Off The Shelf (COTS) hardware: The plan shall address the
use of COTS hardware for which insufficient parts information is
available. In these cases, parts used in COTS hardware may be qualified
by environmental and accelerated life testing of a complete COTS
assembly.

8\. The plan must define the contractor\'s electronic (preferred) or
paper documentation system, data supporting milestone and design
reviews, and NASA\'s access to the parts electronic data base and files.

9\. The as-designed and as-built shall be provided to JSC via the
Acceptance Data Package. The other documentation is subject to JSC
review in order to assure compliance to the approved plan and NASA
policies.

<table style="width:100%;">
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 8%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>NASA and GIDEP ALERT Plan</strong></p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>4/4/97</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>11</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>This DRD defines the contractors responsibilities in the area of NASA
and GIDEP alerts</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>x</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4">6. References <em>(Optional)</em></td>
<td colspan="7">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="4"></td>
<td colspan="7"></td>
</tr>
<tr class="even">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

This documentation is to provide a controlled method of ALERT
initiation, investigation and response. The plan must include the
following.

1\. Provisions to preclude the use of parts or materials subject to NASA
or GIDEP ALERTs. ALERTed parts or materials may only be used when an
application review, showing that use of such parts or materials is
acceptable for a particular application, is accepted by NASA.

2\. The requirement and procedures necessary to initiate an ALERT when
the contractor encounters a significant defect in a part or material.
Contractor initiated ALERTs shall be submitted to the NASA-JSC ALERT
Coordinator.

3\. The requirement to respond, and procedures for responding to all
NASA and GIDEP ALERTs.

<table style="width:100%;">
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 8%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 8%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Limited-Life Item List</strong></p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>29 Mar 96</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>12</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>Identify and control limited-life items.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="2">Technical</td>
<td colspan="2"></td>
<td colspan="2">Administrative</td>
<td>x</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="5"><p>6. References <em>(Optional)</em></p>
<p>See "Reference Documents" under item 8 below.</p></td>
<td colspan="6">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

**Reference Documents**:

> a\. NHB 5300.4, 1D-2, \"Safety, Reliability, Maintainability, and
> Quality Provisions for the Space Shuttle Program\"
>
> b\. JSC 17057, \"GFE Limited Cycle Time/Age Life Items Requirements\"

**SCOPE**: Identify time/cycle-sensitive components and age-controlled
items and related requirements for inspection, maintenance, and
replacement of these items. Limited-life items include limited-shelf
life, limited-operating life, time-action control sensitive items, or a
combination of these. Maintain time/cycle historical log evaluation of
accrued time to determine remaining life.

**FORMAT**:

Electronic tables for entry into NASA databases.

**CONTENT**:

a\. Items shall be identified by part name and number, life limit, life
limiting parameter, or part/material; its function; any limitations on
number of refurbishments; and any data related to operational use, test,
handling, or inspection.

b\. Requirements for maintenance of historical equipment data and
records to verify that time/cycle- and age-sensitive items are
controlled within acceptable limits. Entries to the equipment data
records shall be complete and self-explanatory, and shall include, but
not be limited to, the following:

Part Data:

Shuttle & Station:

-   Part Name

-   Part Number

-   Serial number

-   Date of manufacture

-   Time (age) limit/cycle limit

Station only:

-   Cage Code

-   Shelf Life Quantity

-   Shelf Life Units

-   Life Limiting Parameter

-   Material

-   Function

-   Limitation of Refurbishments

-   Restrictions

Part instance limited-life data:

-   Next higher assembly part number

-   Part instance location code

-   Part instance Logistics Control Number (LCN)

-   Life-limit cycles

-   Life-limit mean time between failures

-   Mean time between failure units (e.g., hrs.)

-   Beginning of life-limit accrual criteria

-   Part instance \"birthday\"

Serialized Part Life Accrual Data:

-   Next higher assembly part number

-   Part instance location code

-   Part instance Logistics Control Number (LCN)

-   Accrued cycles

-   Accrued In-service Time

-   Date/Time of last accumulation

-   Projected cycles remaining

-   Projected life remaining

-   Absolute life end date

c\. The status reports shall include the accrued time and cycles for
each item by part and/or serial number, location, and remaining life.

d\. Waiver reports are required to document instances where an item has
exceeded its time/cycle limit and rationale for accepting an item for
flight or in support of flight. The waiver shall include item name,
number, serial number, time or cycle limit, reason the item has (or
will) exceed its time/cycle limit, and contractor rationale for
accepting the item for flight or proposed action.

e\. The Limited-Life Items List data requirements applies to all flight
hardware. For Station, Limited-Life Items List data must be accessable
in the Vehicle Master Database (VMDB) 145 days prior to the IDR that
covers the first flight deployment of the hardware.

**MAINTENANCE**: Update as required. Multiple deliveries of the GFE do
not require corresponding data deliveries.

<table>
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 9%" />
<col style="width: 0%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 10%" />
<col style="width: 7%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 25%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Safety &amp; Mission Assurance Certification Approval Request
(SMACAR)</strong></p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>016 Aug 96</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>13</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>The SMACAR is the approval form for flight hardware
certification.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>x</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4">6. References <em>(Optional)</em></td>
<td colspan="7"><p>7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></p>
<p>SAR; C/ARR</p></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

SCOPE: The SMACAR, with attached documentation, meets the information
requirement for a certification approval request (CAR) as submittal and
approval of the hardware certification. The SMACAR may serve as the
certification report, when a formal certification report document is not
submitted. The SMACAR may also serve as the certification requirements
(CR), commonly documented in the program requirements document and the
certification plan, when pre-approved as such.

CONTENTS: All sections shall be filled out unless they are marked N/A.
As used in the SMACAR, "Test" document shows the test was done and
verified. All documents listed in the SMACAR as verification of a
requirement or specification must be attached to the SMACAR as part of
this certification report.

FORMAT: The SMACAR was created using Microsoft Word for Windows 6.0. The
form has also been converted for Macintosh Word 4.1. Conversion to other
formats is available upon request. These forms and instructions are
availab*l*e *upon request*.

+---------------+------------------+------------------------+---------+
| **SAFETY &    |                  |                        | Page    |
| MISSION       |                  |                        |         |
| ASSURANCE     |                  |                        | 1 of    |
| CERTIFICATION |                  |                        |         |
| APPROVAL      |                  |                        |         |
| REQUEST**     |                  |                        |         |
|               |                  |                        |         |
| NASA -        |                  |                        |         |
| Johnson Space |                  |                        |         |
| Center        |                  |                        |         |
+---------------+------------------+------------------------+---------+
| Part Number   | Part Name        | System                 |         |
+---------------+------------------+------------------------+---------+

+-------------+---+---------------+---------+---------+------+-------+---+
| Assemblies  |   |               |         |         |      |       |   |
| (Part       |   |               |         |         |      |       |   |
| Number      |   |               |         |         |      |       |   |
| **\|** Part |   |               |         |         |      |       |   |
| Name) for   |   |               |         |         |      |       |   |
| Ce          |   |               |         |         |      |       |   |
| rtification |   |               |         |         |      |       |   |
| and         |   |               |         |         |      |       |   |
| Shipping    |   |               |         |         |      |       |   |
+-------------+---+---------------+---------+---------+------+-------+---+
|             |   |               |         |         |      |       |   |
+-------------+---+---------------+---------+---------+------+-------+---+
| Manifest    |   | Change        | Certif  | Requi   | ICD  | C     |   |
| Change      |   | Control       | ication | rements | \#   | ritic |   |
| Directive   |   | Authority     | Plan    | D       |      | ality |   |
|             |   | (Board Name)  |         | ocument |      |       |   |
| and         |   |               |         |         |      | Func  |   |
| Board/Panel |   |               |         |         |      | /Hdwr |   |
+-------------+---+---------------+---------+---------+------+-------+---+

<table style="width:100%;">
<colgroup>
<col style="width: 14%" />
<col style="width: 8%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 2%" />
<col style="width: 11%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 7%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 9%" />
<col style="width: 2%" />
<col style="width: 3%" />
<col style="width: 18%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="10">SSM/PE:</td>
<td colspan="7">Phone #:</td>
<td>Mail Code:</td>
</tr>
<tr class="even">
<td># of Missions Certified</td>
<td colspan="3">1st Flight</td>
<td colspan="2">Limited Life</td>
<td colspan="3">Weight</td>
<td colspan="5">Dimensions</td>
<td colspan="2"><p>FMEA/CIL</p>
<p>Document #</p></td>
<td colspan="2">Safety Analysis Report Document #</td>
</tr>
<tr class="odd">
<td colspan="18">Criticality Rationale Summary:</td>
</tr>
<tr class="even">
<td colspan="18"><strong>Does test hardware configuration differ from
flight hardware configuration?</strong></td>
</tr>
<tr class="odd">
<td colspan="5"><strong>Installation Information:</strong></td>
<td colspan="3">Mounted:</td>
<td colspan="5">Locker Stowed:</td>
<td colspan="5">Stowed Other:</td>
</tr>
<tr class="even">
<td colspan="2"><strong>Launch Location:</strong></td>
<td colspan="5">Crew Cabin:</td>
<td colspan="5">Payload Bay:</td>
<td colspan="3">Space Lab/Hab:</td>
<td colspan="3">Other:</td>
</tr>
<tr class="odd">
<td colspan="18"><strong>Landing Location:</strong> <em>Same or list
other</em></td>
</tr>
<tr class="even">
<td colspan="3"><strong>Operational Location:</strong></td>
<td colspan="5">Crew Cabin:</td>
<td colspan="3">Payload Bay:</td>
<td colspan="4">Space Lab/Hab:</td>
<td colspan="3">Other:</td>
</tr>
<tr class="odd">
<td colspan="18"><strong>General Operational Information</strong>:</td>
</tr>
<tr class="even">
<td colspan="18"><strong>Operational Performance
Requirements</strong>:</td>
</tr>
<tr class="odd">
<td colspan="18"><strong>Crew Procedures</strong> Data Book:</td>
</tr>
<tr class="even">
<td colspan="18"><strong>Flight Rules</strong> (List all by FR# and
Title):</td>
</tr>
</tbody>
</table>

**Approvals:**

  ----------------------------------- -----------------------------------
  Subsystem Manager                   Battery Manager

                                      

  Materials Control Manager           Structures

                                      

  SR&QA Structures                    NS/Flight System Safety and Mission
                                      Assurance

                                      
  ----------------------------------- -----------------------------------

JSC Form 1296

  ---------------- ------------------- ------------------------- ----------
  **SAFETY &                                                     Page
  MISSION                                                        
  ASSURANCE                                                      
  CERTIFICATION                                                  
  APPROVAL                                                       
  REQUEST**                                                      

  NASA - Johnson                                                 2 of
  Space Center                                                   

  Part Number      Part Name           System                    

                                                                 
  ---------------- ------------------- ------------------------- ----------

+---------+----+---------+------------+-----------+-----------------+
| **Mater | J  |         |            | **MATL    | MUA Numbers:    |
| ials:** | SC |         |            | -**       |                 |
|         | M  |         |            |           |                 |
|         | at |         |            |           |                 |
|         | er |         |            |           |                 |
|         | ia |         |            |           |                 |
|         | ls |         |            |           |                 |
|         | C  |         |            |           |                 |
|         | er |         |            |           |                 |
|         | ti |         |            |           |                 |
|         | fi |         |            |           |                 |
|         | ca |         |            |           |                 |
|         | ti |         |            |           |                 |
|         | on |         |            |           |                 |
|         | M  |         |            |           |                 |
|         | em |         |            |           |                 |
|         | or |         |            |           |                 |
|         | an |         |            |           |                 |
|         | du |         |            |           |                 |
|         | m: |         |            |           |                 |
|         |    |         |            |           |                 |
|         | (S |         |            |           |                 |
|         | ig |         |            |           |                 |
|         | na |         |            |           |                 |
|         | tu |         |            |           |                 |
|         | re |         |            |           |                 |
|         | Re |         |            |           |                 |
|         | qu |         |            |           |                 |
|         | ir |         |            |           |                 |
|         | ed |         |            |           |                 |
|         | if |         |            |           |                 |
|         | no |         |            |           |                 |
|         | Me |         |            |           |                 |
|         | mo |         |            |           |                 |
|         | #) |         |            |           |                 |
+---------+----+---------+------------+-----------+-----------------+
| Ma      |    | IVA:    | EVA:       | Other:    |                 |
| terials |    |         |            |           |                 |
| comp    |    |         |            |           |                 |
| atible: |    |         |            |           |                 |
+---------+----+---------+------------+-----------+-----------------+

+------------------+-----------------+----------------+---------------+
| **Electrical     |                 |                |               |
| Interfaces**:    |                 |                |               |
|                  |                 |                |               |
| (List all power  |                 |                |               |
| and signal       |                 |                |               |
| interfaces to    |                 |                |               |
| the Orbiter or   |                 |                |               |
| other equipment, |                 |                |               |
| including        |                 |                |               |
| battery size and |                 |                |               |
| type if          |                 |                |               |
| applicable).     |                 |                |               |
+------------------+-----------------+----------------+---------------+
| Power Interface  | Orbiter Circuit | Hardware       | Bonding       |
| Location:        |                 | Nominal        |               |
|                  | Protection:     |                | Verification: |
| (D&C Panel #)    |                 | Amps:          |               |
+------------------+-----------------+----------------+---------------+
| Hardware Circuit | Batteries:      |                | Other:        |
|                  |                 |                |               |
| Protection:      |                 |                |               |
+------------------+-----------------+----------------+---------------+

  ----------------------------- -----------------------------------------
  **Electromagnetic             
  Compatibility Information:**  

  EMC/EMI TEST                  24V to 32VDC Power Performance Test
  ----------------------------- -----------------------------------------

  -------------------------- -------- --------------------- --------------
  **Temperature                                             
  Validation:**                                             

  QTT Range:                 QTT                            Cycles:
                             Test:                          

  QTVT Range:                QTVT                           Cycles:
                             Test:                          

  Non-operating Temperature           Operating Temperature 
  Limits:                             Limits:               

  Survivable Mission                                        
  Operational Time Limit:                                   

  Touch Temperature Test:                                   
  -------------------------- -------- --------------------- --------------

  -------------------------- ----------------------------- ---------------
  **Acceptance Thermal:**                                  

  ATT Range:                 ATT Test:                     Cycles:

  QATT Range:                QATT Test:                    Cycles:

  ATVT Range:                ATVT Test:                    Cycles:

  QATVT Range:               QATVT Test:                   Cycles:
  -------------------------- ----------------------------- ---------------

+-----------+------------+--------+---+---+--------+---+---------------+
| **S       |            |        |   | * |        |   |               |
| tructural |            |        |   | * |        |   |               |
| Vali      |            |        |   | F |        |   |               |
| dation:** |            |        |   | a |        |   |               |
|           |            |        |   | c |        |   |               |
| **Factor  |            |        |   | t |        |   |               |
| of Safety |            |        |   | o |        |   |               |
| for       |            |        |   | r |        |   |               |
| Test:**   |            |        |   | o |        |   |               |
|           |            |        |   | f |        |   |               |
|           |            |        |   | S |        |   |               |
|           |            |        |   | a |        |   |               |
|           |            |        |   | f |        |   |               |
|           |            |        |   | e |        |   |               |
|           |            |        |   | t |        |   |               |
|           |            |        |   | y |        |   |               |
|           |            |        |   | f |        |   |               |
|           |            |        |   | o |        |   |               |
|           |            |        |   | r |        |   |               |
|           |            |        |   | A |        |   |               |
|           |            |        |   | n |        |   |               |
|           |            |        |   | a |        |   |               |
|           |            |        |   | l |        |   |               |
|           |            |        |   | y |        |   |               |
|           |            |        |   | s |        |   |               |
|           |            |        |   | i |        |   |               |
|           |            |        |   | s |        |   |               |
|           |            |        |   | : |        |   |               |
|           |            |        |   | * |        |   |               |
|           |            |        |   | * |        |   |               |
+-----------+------------+--------+---+---+--------+---+---------------+
| S         |            |        |   |   | Stress |   |               |
| tructural |            |        |   |   | Ana    |   |               |
| Integrity |            |        |   |   | lysis: |   |               |
| Ver       |            |        |   |   |        |   |               |
| ification |            |        |   |   |        |   |               |
| Plan:     |            |        |   |   |        |   |               |
+-----------+------------+--------+---+---+--------+---+---------------+
| Fracture  |            |        |   |   | Fr     |   |               |
| Control   |            |        |   |   | acture |   |               |
| Summary   |            |        |   |   | Plan:  |   |               |
| Report:   |            |        |   |   |        |   |               |
+-----------+------------+--------+---+---+--------+---+---------------+
| QVT       |            | QVT    |   |   |        |   | Duration:     |
| A         |            | Test:  |   |   |        |   |               |
| mplitude: |            |        |   |   |        |   |               |
+-----------+------------+--------+---+---+--------+---+---------------+
| 20G Crash |            |        | S |   |        |   |               |
| Test:     |            |        | h |   |        |   |               |
|           |            |        | o |   |        |   |               |
|           |            |        | c |   |        |   |               |
|           |            |        | k |   |        |   |               |
|           |            |        | T |   |        |   |               |
|           |            |        | e |   |        |   |               |
|           |            |        | s |   |        |   |               |
|           |            |        | t |   |        |   |               |
|           |            |        | : |   |        |   |               |
+-----------+------------+--------+---+---+--------+---+---------------+
| Limit     |            |        | L |   |        |   |               |
| Loads:    |            |        | i |   |        |   |               |
|           |            |        | m |   |        |   |               |
|           |            |        | i |   |        |   |               |
|           |            |        | t |   |        |   |               |
|           |            |        | L |   |        |   |               |
|           |            |        | o |   |        |   |               |
|           |            |        | a |   |        |   |               |
|           |            |        | d |   |        |   |               |
|           |            |        | s |   |        |   |               |
|           |            |        | T |   |        |   |               |
|           |            |        | e |   |        |   |               |
|           |            |        | s |   |        |   |               |
|           |            |        | t |   |        |   |               |
|           |            |        | : |   |        |   |               |
+-----------+------------+--------+---+---+--------+---+---------------+
| Life      |            |        | L |   |        |   |               |
| Cycles:   |            |        | i |   |        |   |               |
|           |            |        | f |   |        |   |               |
|           |            |        | e |   |        |   |               |
|           |            |        | C |   |        |   |               |
|           |            |        | y |   |        |   |               |
|           |            |        | c |   |        |   |               |
|           |            |        | l |   |        |   |               |
|           |            |        | e |   |        |   |               |
|           |            |        | T |   |        |   |               |
|           |            |        | e |   |        |   |               |
|           |            |        | s |   |        |   |               |
|           |            |        | t |   |        |   |               |
|           |            |        | i |   |        |   |               |
|           |            |        | n |   |        |   |               |
|           |            |        | g |   |        |   |               |
|           |            |        | : |   |        |   |               |
+-----------+------------+--------+---+---+--------+---+---------------+
| Captive   |            |        | F |   |        |   |               |
| Fastener  |            |        | a |   |        |   |               |
| Cycle     |            |        | s |   |        |   |               |
| Life:     |            |        | t |   |        |   |               |
|           |            |        | e |   |        |   |               |
|           |            |        | n |   |        |   |               |
|           |            |        | e |   |        |   |               |
|           |            |        | r |   |        |   |               |
|           |            |        | L |   |        |   |               |
|           |            |        | i |   |        |   |               |
|           |            |        | f |   |        |   |               |
|           |            |        | e |   |        |   |               |
|           |            |        | T |   |        |   |               |
|           |            |        | r |   |        |   |               |
|           |            |        | a |   |        |   |               |
|           |            |        | c |   |        |   |               |
|           |            |        | e |   |        |   |               |
|           |            |        | a |   |        |   |               |
|           |            |        | b |   |        |   |               |
|           |            |        | i |   |        |   |               |
|           |            |        | l |   |        |   |               |
|           |            |        | i |   |        |   |               |
|           |            |        | t |   |        |   |               |
|           |            |        | y |   |        |   |               |
|           |            |        | P |   |        |   |               |
|           |            |        | e |   |        |   |               |
|           |            |        | r |   |        |   |               |
|           |            |        | : |   |        |   |               |
+-----------+------------+--------+---+---+--------+---+---------------+

  ----------------- ----------------- ------------------------------------
  **Pressure                          
  Systems:**                          

  Proof Pressure:   Burst Pressure:   System Operational Pressure Range:
  ----------------- ----------------- ------------------------------------

JSC Form 1296

  ---------------- ------------------- ------------------------- ----------
  **SAFETY &                                                     Page
  MISSION                                                        
  ASSURANCE                                                      
  CERTIFICATION                                                  
  APPROVAL                                                       
  REQUEST**                                                      

  NASA - Johnson                                                 3 of
  Space Center                                                   

  Part Number      Part Name           System                    

                                                                 
  ---------------- ------------------- ------------------------- ----------

  -------------- ------------------ ------------------------- ----------- --------
  **Acceptance                                                            
  Vibration:**                                                            

  AVT Amplitude: *.04* g^2^/Hz      AVT Test:                 Duration:   *1 min*
                 ([+]{.underline}                                         
                 X,Y,Z)                                                   

  QAVT           *.067* g^2^/Hz     QAVT Test:                Duration:   *5 min*
  Amplitude:     ([+]{.underline}                                         
                 X,Y,Z)                                                   
  -------------- ------------------ ------------------------- ----------- --------

  ------------------------ ----------------------------------------------
  **Acoustics/Noise:**     

  O/A dB Level             Acoustics Test
  ------------------------ ----------------------------------------------

  ------------------------------------ ----------------------------------
  **Performance Verification:**        

  Acceptance Testing Functional        Interface Verification Test:
  Checkout Procedure, ATP, or other    IVT/SAIL/OMRSD/CEIT/etc.

                                       

  Pre-flight Functional Checkout       Other Functional performance
  Procedure PIA/OMI/OMRSD/etc.         testing

                                       
  ------------------------------------ ----------------------------------

  ------------------------------------ ----------------------------------
  **Waivers or Requirements            
  Deviations**:                        

  Requirement Waived:                  CR#
  ------------------------------------ ----------------------------------

  -----------------------------------------------------------------------
  **If this certification is NOT for 100 Missions:**

  Give the reason here for the limitation, and indicate which flights the
  hardware is approved for.
  -----------------------------------------------------------------------

  --------------- --------------------- ---------------------------------------
  If no **SAR**                         
  or **HAW**,                           
  list potential                        
  hazards,                              
  controls, and                         
  verification                          

  Materials       Flammability,         Verified Controlled per Materials memo
                  Toxicity, Offgassing  .

  Mechanical      Impact/Structural     Verified Controlled per Stress Analysis
                  Failure               and testing listed.

  Physiological   Sharp                 Verified Radius requirement from ( JSC
                  Edges/Corners/Pinch   17481) listed on drawings
                  Points                

  Physiological   Acoustical Noise      Verified controlled per acoustic test
                                        above

  Electrical      EMI/EMC               Verified Controlled per test data
                                        listed

  Physiological   Hot/Cold Surfaces     Verified Controlled per test data
                                        listed

                  Contamination         Verified Controlled per Materials memo
                                        and

                  Electrical            Verified Controlled per
                  Discharge/Shock       

                  Explosion             Verified Controlled per

  Other                                 

  Other                                 

  Other                                 
  --------------- --------------------- ---------------------------------------

**To be completed by JSC FSS&MA:**

Did you inspect this hardware?

Did you review the drawings?

Is hazard analysis or certification mission specific?

> If Yes, give reason why and list how this will be identified as open
> for other missions.

JSC Form 1296

**Instructions for the Safety and Mission Assurance Certification
Approval Request.**

The SMACAR is the approval form for certification. The SMACAR, with
attached documentation, meets the NSTS 07700 Vol. V information
requirement for a certification approval request (CAR) as submittal and
approval of the hardware certification. The SMACAR may also serves as
the certification report, when a formal certification report document is
not submitted. The SMACAR may also serve as the certification
requirements (CR), commonly documented in the program requirements
document and the certification plan, when pre-approved as such. The form
is submitted by Engineering to FSS&MA for review and approval. All
sections must be filled out unless they are marked N/A. As used in the
SMACAR, \"Test\" document may be a TPS or equivalent document, or a
procedure, which shows the test was done and stamped off by Quality
Assurance. All documents listed in the SMACAR as verification of a
requirement or specification must be attached to the SMACAR as part of
this certification report.

The SMACAR was created using Microsoft Word for Windows 6.0. The form
has also been converted for Macintosh Word 4.1. Conversion to other
formats is available upon request. These forms and instructions are
available on the SR&QA file server BHFS03\\SHUTTLE\\SMACAR, or from JSC
FSS&MA, Mail Code NS. Questions concerning data elements of this form
should be directed to the FSS&MA subsystem engineer (SSE) responsible
for that hardware, the SSEs Lead Engineer, the NS2 Section Lead, or any
other NS2 SSE.

  -----------------------------------------------------------------------
  Assemblies (Part Number **\|** Part Name) for Certification and
  Shipping

  -----------------------------------------------------------------------

List all assemblies and subassemblies that are covered by this
certification. These are the only part numbers that will go into the
SR&QA database and be approved for shipment. If it\'s not in this list,
it\'s not certified.

+--------------+-----------+--------+----------+----------+----------+
| Manifest     | Change    | C      | Requ     | ICD \#   | Cri      |
| Change       | Control   | ertifi | irements |          | ticality |
| Directive    | Authority | cation | Document |          |          |
|              | (Board    | Plan   |          |          | F        |
| and          | Name)     |        |          |          | unc/Hdwr |
| Board/Panel  |           |        |          |          |          |
+--------------+-----------+--------+----------+----------+----------+
| Give the     | Give the  | Type   | Type the | Type the | Type the |
| directive \# | board     | the    | PRD      | i        | highest  |
| such as CCBD | re        | c      | number   | nterface | crit     |
| G4114, which | sponsible | ertifi | or other | control  | icality, |
| manifests    | for       | cation | document | doc.     | function |
| this         | conf      | plan   | which    | number   | and      |
| hardware,    | iguration | doc.   | defines  | if there | h        |
| along with   | control   | n      | the      | is one.  | ardware, |
| the board or | or change | umber, | requi    |          | as       |
| panel name   | control.  | or     | rements. |          | de       |
| that is      |           | what   |          |          | termined |
| responsible. |           | do     |          |          | by the   |
|              |           | cument |          |          | FMEA.    |
|              |           | is     |          |          |          |
|              |           | used   |          |          |          |
|              |           | for    |          |          |          |
|              |           | this.  |          |          |          |
+--------------+-----------+--------+----------+----------+----------+

  ------------------------------------- -------------------- -------------
  SSM/PE:                               Phone #:             Mail Code:

  ------------------------------------- -------------------- -------------

Type the name, phone \# and mail code of the Subsystem Manager or
Engineering Project Manager Responsible for the hardware.

+---------+------+---------+-----+--------+---------+---------------+
| \# of   | 1st  | Limited | Wei | Dime   | F       | Safety        |
| M       | Fl   | Life    | ght | nsions | MEA/CIL | Analysis      |
| issions | ight |         |     |        |         | Report        |
| Ce      |      |         |     |        | D       | Document \#   |
| rtified |      |         |     |        | ocument |               |
|         |      |         |     |        | \#      |               |
+---------+------+---------+-----+--------+---------+---------------+
| Type    | Type | List    | L   | Type   | Type    | Type the SAR  |
| how     | the  | the     | ist | the    | the     | document      |
| many    |      | limited | the | dime   | FMEA    | number        |
| m       | fl   | life    | ha  | nsions | d       |               |
| issions | ight | d       | rdw | and    | ocument | or indicate   |
| the     | nu   | ocument | are | units  | number  | if an HAW or  |
| design  | mber | or all  | w   | (      |         | other         |
|         | for  |         | eig | inches | or      |               |
| is      | the  | items   | ht. | or     | i       | data is       |
| ce      | f    | which   |     |        | ndicate | attached. The |
| rtified | irst | do not  |     | cm\)   | wor     | last page of  |
| for     | fl   | meet    |     | of the | ksheets |               |
|         | ight | the 10  |     | har    | or      | the SMACAR    |
|         | of   |         |     | dware. |         | may be used   |
|         | the  | ye      |     |        | other   | to substitute |
|         | h    | ars/100 |     |        | for the | for a SAR.    |
|         | ardw | m       |     |        | data.   |               |
|         | are. | issions |     |        |         |               |
|         |      | design  |     |        |         |               |
|         |      | life.   |     |        |         |               |
+---------+------+---------+-----+--------+---------+---------------+

+-----------------------------------------------------------------------+
| Criticality Rationale Summary:                                        |
|                                                                       |
| Type the rationale for the criticality listed above.                  |
+-----------------------------------------------------------------------+

  -----------------------------------------------------------------------
  **Does test hardware configuration differ from flight hardware
  configuration?** (Yes or No and indicate difference if no)

  -----------------------------------------------------------------------

  ---------------- -------- -------- ---------- -- -- --------- --------- -- -- -- ---------- ---------- --------- -- --- -------- --------------
  **Installation                     Mounted:                   Locker                                   Stowed                    
  Information:**                                                Stowed:                                  Other:                    

  **Launch         Crew                               Payload                                 Space                       Other:   
  Location:**      Cabin:                             Bay:                                    Lab/Hab:                             

  **Landing                                                                                                                        
  Location:**                                                                                                                      
  *Same or list                                                                                                                    
  other*                                                                                                                           

  **Operational             Crew                                Payload            Space                                  Other:   
  Location:**               Cabin:                              Bay:               Lab/Hab:                                        
  ---------------- -------- -------- ---------- -- -- --------- --------- -- -- -- ---------- ---------- --------- -- --- -------- --------------

Choose the correct category to indicate how the hardware is installed,
the launch, landing, and operational location. More than one category
may be used for systems that are located in more than one location.

+-----------------------------------------------------------------------+
| **General Operational Information**:                                  |
|                                                                       |
| Type the operational description of the hardware, crew interaction,   |
| activation, mission use, etc. This information is a detailed          |
| management summary of the hardware and operations that the            |
| certification covers.                                                 |
+-----------------------------------------------------------------------+

+-----------------------------------------------------------------------+
| **Operational Performance Requirements**:                             |
|                                                                       |
| Type the operational performance requirements that are verified.      |
| These should be found in the Program requirements document or other   |
| specifications.                                                       |
+-----------------------------------------------------------------------+

  ----------------- -----------------------------------------------------
  **Crew            Type the flight data file number where crew
  Procedures** Data procedures are located.
  Book:             

  **Flight Rules**  
  (List all by FR#  
  and Title): Type  
  the flight rules  
  by flight rule    
  number and title. 
  Ideally, this     
  section will be   
  the entire rule,  
  pasted from the   
  flight rules      
  document located  
  on the JSCDA8     
  file server.      
  ----------------- -----------------------------------------------------

<table>
<colgroup>
<col style="width: 18%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 3%" />
<col style="width: 18%" />
<col style="width: 13%" />
<col style="width: 13%" />
</colgroup>
<tbody>
<tr class="odd">
<td><strong>Materials:</strong></td>
<td colspan="6"><p>JSC Materials Certification Memorandum:</p>
<p>(Signature Required if no Memo #)</p></td>
<td><h1 id="matl--">MATL -</h1></td>
<td>MUA Numbers:</td>
<td></td>
</tr>
<tr class="even">
<td>Materials compatible:</td>
<td>IVA:</td>
<td></td>
<td>EVA:</td>
<td></td>
<td>Other:</td>
<td colspan="4"></td>
</tr>
</tbody>
</table>

Type the material approval memo (ex. MATL-95-105) and any MUA\'s for the
hardware. Also, indicate the environment the material is approved for.

If there is no approval memo, a signature from the JSC Materials Manager
is required.

<table>
<colgroup>
<col style="width: 9%" />
<col style="width: 1%" />
<col style="width: 12%" />
<col style="width: 10%" />
<col style="width: 10%" />
<col style="width: 8%" />
<col style="width: 10%" />
<col style="width: 1%" />
<col style="width: 7%" />
<col style="width: 27%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="10"><p><strong>Electrical Interfaces</strong>: N/A if not
applicable.</p>
<p>(List all power and signal interfaces to the Orbiter or other
equipment, including battery size and type if applicable).</p></td>
</tr>
<tr class="even">
<td colspan="2"><p>Power Interface Location:</p>
<p>(D&amp;C Panel #)</p></td>
<td>Type the Orbiter panel number for the switches, outlets, and circuit
protection.</td>
<td>Orbiter Circuit Protection:</td>
<td>Type the rating of the fuse or breaker to protect the Orbiter
wiring.</td>
<td>Hardware Nominal Amps:</td>
<td>Type the nominal operating current for the hardware.</td>
<td colspan="2">Bonding Verification:</td>
<td>Type the documented test number or procedure which verifies
Electrical bonding.</td>
</tr>
<tr class="odd">
<td>Hardware Circuit Protection:</td>
<td colspan="2"><strong>Type the hardware circuit protection such as
built in fuses or breakers.</strong></td>
<td>Batteries:</td>
<td colspan="4">Type the quantity of cells, type of cells (D-cell),
chemistry, voltage of battery pack,</td>
<td>Other:</td>
<td>Type other pertinent electrical interface information not described
in the other data fields.</td>
</tr>
</tbody>
</table>

  ------------------- ----------------- ---------------------- -------------------
  **Electromagnetic                                            
  Compatibility                                                
  Information:** N/A                                           
  if not applicable.                                           

  EMC/EMI TEST        Type in the test  24V to 32VDC Power     Type in the test
                      document number   Performance Test       document number
                      that performed                           that performed the
                      the EMC test.                            Voltage swing test
                                                               and verified the
                                                               hardware was
                                                               operational at the
                                                               required limits.
  ------------------- ----------------- ---------------------- -------------------

  --------------- ------------- ------------- ----------- ------------- ------- ------------- ----------------- ------------- --------- ---------------
  **Temperature                                                                                                                         
  Validation:**                                                                                                                         
  N/A if not                                                                                                                            
  applicable.                                                                                                                           

  QTT Range:      Type the                                              QTT                   Type in the test                Cycles:   Type the number
                  temperature                                           Test:                 document number                           of cycles
                  range                                                                       that performed                            
                                                                                              the test.                                 

  QTVT Range:     Type the                                              QTVT                  Type in the test                Cycles:   Type the number
                  temperature                                           Test:                 document number                           of cycles
                  range                                                                       that performed                            
                                                                                              the test.                                 

  Non-operating                 Type the                                        Operating                       Type the                
  Temperature                   survivable                                      Temperature                     survivable              
  Limits:                       temperature                                     Limits:                         temperature             
                                limits for                                                                      limits for              
                                the hardware                                                                    the hardware            
                                when not                                                                        when                    
                                activated.                                                                      activated.              

  Survivable                                              Type the                                                                      
  Mission                                                 worst case                                                                    
  Operational                                             mission time                                                                  
  Time Limit:                                             limit for                                                                     
                                                          operation of                                                                  
                                                          the hardware                                                                  
                                                          based on                                                                      
                                                          temperature                                                                   
                                                          limits.                                                                       

  Touch                                       Type in the                                                                               
  Temperature                                 test                                                                                      
  Test:                                       document                                                                                  
                                              number that                                                                               
                                              performed                                                                                 
                                              the test.                                                                                 
  --------------- ------------- ------------- ----------- ------------- ------- ------------- ----------------- ------------- --------- ---------------

  -------------- ------------- ------------- -------- ------------------ --------- ---------------
  **Acceptance                 N/A if not                                          
  Thermal:**                   applicable.                                         

  ATT Range:     Type the                    ATT      Type in the test   Cycles:   Type the number
                 temperature                 Test:    document number              of cycles
                 range                                that performed the           
                                                      test.                        

  QATT Range:    Type the                    QATT     Type in the test   Cycles:   Type the number
                 temperature                 Test:    document number              of cycles
                 range                                that performed the           
                                                      test.                        

  ATVT Range:    Type the                    ATVT     Type in the test   Cycles:   Type the number
                 temperature                 Test:    document number              of cycles
                 range                                that performed the           
                                                      test.                        

  QATVT Range:   Type the                    QATVT    Type in the test   Cycles:   Type the number
                 temperature                 Test:    document number              of cycles
                 range                                that performed the           
                                                      test.                        
  -------------- ------------- ------------- -------- ------------------ --------- ---------------

<table style="width:100%;">
<colgroup>
<col style="width: 11%" />
<col style="width: 1%" />
<col style="width: 3%" />
<col style="width: 12%" />
<col style="width: 0%" />
<col style="width: 9%" />
<col style="width: 9%" />
<col style="width: 4%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 8%" />
<col style="width: 5%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 5%" />
<col style="width: 22%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="17"><p><strong>Structural Validation:</strong> N/A if not
applicable.</p>
<p><strong>Factor of Safety for Test:</strong> Type the required Factor
of Safety <strong>Factor of Safety for Analysis:</strong> Type the
required Factor of Safety</p></td>
</tr>
<tr class="even">
<td colspan="4">Structural Integrity Verification Plan:</td>
<td colspan="7">Type Document #</td>
<td colspan="4">Stress Analysis:</td>
<td colspan="2">Type Document #</td>
</tr>
<tr class="odd">
<td colspan="4">Fracture Control Summary Report:</td>
<td colspan="7">Type Document #</td>
<td colspan="2">Fracture Plan:</td>
<td colspan="4">Type Document #</td>
</tr>
<tr class="even">
<td colspan="2">QVT Amplitude:</td>
<td colspan="4">Type the spectrum information for the X,Y, &amp; Z axis
vibration spectrum.</td>
<td>QVT Test:</td>
<td colspan="7">Type in the test document number that performed the
test.</td>
<td colspan="2">Duration:</td>
<td>Type the duration of the vibration test per axis. (ex. 1
min/axis)</td>
</tr>
<tr class="odd">
<td colspan="2">20G Crash Test:</td>
<td colspan="6">Type in the test document number that performed the
test.</td>
<td colspan="9">Shock Test: Type in the test document number that
performed the test.</td>
</tr>
<tr class="even">
<td colspan="2">Limit Loads:</td>
<td colspan="6">Type the "certified to" load limits information
pertinent to the use of the hardware.</td>
<td colspan="9">Limit Loads Test: Type in the test document number that
performed the test.</td>
</tr>
<tr class="odd">
<td colspan="2">Life Cycles:</td>
<td colspan="6">Type the "certified to" life cycle limits.</td>
<td colspan="9">Life Cycle Testing: Type in the test document number
that performed the test.</td>
</tr>
<tr class="even">
<td colspan="2">Captive Fastener Cycle Life:</td>
<td colspan="7">Indicate any cycle life limited items, such as captive
fasteners, and how many cycles are acceptable.</td>
<td colspan="3">Fastener Life Traceability Per:</td>
<td colspan="5">Indicate how the installation/removal of limited cycle
items, such as fasteners, are tracked.</td>
</tr>
<tr class="odd">
<td colspan="3"><strong>Pressure Systems:</strong></td>
<td colspan="14">N/A if not applicable.</td>
</tr>
<tr class="even">
<td>Proof Pressure:</td>
<td colspan="4">Type the pressure rating indicating PSIG or PSIA and the
test that verified this.</td>
<td>Burst Pressure:</td>
<td colspan="4">Type the pressure rating indicating PSIG or PSIA and the
test that verified this.</td>
<td colspan="4">System Operational Pressure Range:</td>
<td colspan="3">Type the pressure rating indicating PSIG or PSIA and the
test that verified this. Type in the relief valve or burst disc
information and other safety related system information.</td>
</tr>
</tbody>
</table>

  -------------- ------------------ ------------- ------- --------------- ----------- ------------
  **Acceptance                      N/A if not                                        
  Vibration:**                      applicable.                                       

  AVT Amplitude: *.04* g^2^/Hz                    AVT     Type in the     Duration:   Type the
                 ([+]{.underline}                 Test:   test document               duration of
                 X,Y,Z) Type in the                       number that                 the
                 acceleration                             performed the               vibration
                 amplitude if                             test.                       test per
                 different from the                                                   axis. (ex. 1
                 normal AVT levels.                                                   min/axis)

  QAVT           *.067* g^2^/Hz                   QAVT    Type in the     Duration:   Type the
  Amplitude:     ([+]{.underline}                 Test:   test document               duration of
                 X,Y,Z) Type in the                       number that                 the
                 acceleration                             performed the               vibration
                 amplitude if                             test.                       test per
                 different from the                                                   axis. (ex. 1
                 normal QAVT                                                          min/axis)
                 levels.                                                              
  -------------- ------------------ ------------- ------- --------------- ----------- ------------

  ---------------------- ----------------------- ----------- -------------------------
  **Acoustics/Noise:**   N/A if not applicable.              

  O/A dB Level           Type the O/A level      Acoustics   Type in the test document
                         determined by the       Test        number that performed the
                         acoustic test.                      test.
  ---------------------- ----------------------- ----------- -------------------------

+------------------+-----------------+---------------------------------+
| **Performance    | N/A if not      |                                 |
| Verification:**  | applicable.     |                                 |
+------------------+-----------------+---------------------------------+
| Acceptance       |                 | Interface Verification Test:    |
| Testing          |                 | IVT/SAIL/OMRSD/CEIT/etc.        |
| Functional       |                 |                                 |
| Checkout         |                 | Type in the test document       |
| Procedure, ATP,  |                 | number that performed the       |
| or other         |                 | interface verification test.    |
|                  |                 |                                 |
| Type in the test |                 |                                 |
| document number  |                 |                                 |
| that performed   |                 |                                 |
| the acceptance   |                 |                                 |
| test.            |                 |                                 |
+------------------+-----------------+---------------------------------+
| Pre-flight       |                 | Other Functional performance    |
| Functional       |                 | testing                         |
| Checkout         |                 |                                 |
| Procedure        |                 | Type in the test document       |
| PI               |                 | number that performed the test. |
| A/OMI/OMRSD/etc. |                 |                                 |
|                  |                 |                                 |
| Type in the test |                 |                                 |
| document number  |                 |                                 |
| that performed   |                 |                                 |
| the pre-flight   |                 |                                 |
| verification     |                 |                                 |
| test.            |                 |                                 |
+------------------+-----------------+---------------------------------+

  --------------- --------------------- ----- ------------------------------
  **Waivers or                                
  Requirements                                
  Deviations**:                               
  N/A if not                                  
  applicable.                                 

  Requirement     Type requirement that CR#   Type in the Change Request
  Waived:         was waived.                 number which documents the
                                              waiver approval.
  --------------- --------------------- ----- ------------------------------

+-----------------------------------------------------------------------+
| **If this certification is NOT for 100 Missions:**                    |
+-----------------------------------------------------------------------+
| Give the reason here for the limitation and indicate which flights    |
| the hardware is approved for.                                         |
|                                                                       |
| If the hardware is certified for one or more missions, but less than  |
| 100, indicate if the design is limited or each serial number is       |
| limited, and list the flights that the hardware is approved for. An   |
| example is if the hardware is certified for 1 mission, indicate if    |
| the design is limited to one specific mission or if each serial       |
| number is limited to one flight. (An item may be certified for one    |
| mission based on specific mission environmental or operational        |
| information and has only been tested or analyzed for that specific    |
| mission. This type of certification is a mission specific             |
| certification and the certification will be revoked after that        |
| mission. An item may be certified for one mission based on other      |
| factors such as qualification testing which only encompassed one      |
| missions worst case exposure. This type of certification is not       |
| mission specific and any serial number may be flown for one mission.  |
| This would be a limited life item that can be tracked.                |
+-----------------------------------------------------------------------+

  --------------- --------------------- ----------------------------------------
  If no **SAR**                         
  or **HAW**,                           
  list potential                        
  hazards,                              
  controls, and                         
  verification                          

  Materials       Flammability,         Verified Controlled per Materials memo.
                  Toxicity, Offgassing  

  Mechanical      Impact/Structural     Verified Controlled per Stress Analysis
                  Failure               and testing listed.

  Physiological   Sharp                 Verified Radius requirement from ( JSC
                  Edges/Corners/Pinch   17481) listed on drawings
                  Points                

  Physiological   Acoustical Noise      Verified controlled per acoustic test
                                        above

  Electrical      EMI/EMC               Verified Controlled per test data listed

  Physiological   Hot/Cold Surfaces     Verified Controlled per test data listed

                  Contamination         Verified Controlled per Materials memo
                                        and

                  Electrical            Verified Controlled per
                  Discharge/Shock       

                  Explosion             Verified Controlled per

  Other                                 

  Other                                 

  Other                                 
  --------------- --------------------- ----------------------------------------

A SAR is required for all hardware. The Safety Section above is only
used when a SAR has not been provided as a separate document. The
information contained in the SMACAR should provide verification of most
hazard controls. If there is no SAR or HAW or other Safety analysis
documentation submitted, the SMACAR can serve as the documentation but
all information must be provided. Examples of the generic hazards to
explore are indicated in the table above. List other hazards as
appropriate and provide the verification of the controls.

**Acronyms**

ATP - Acceptance Test Procedure

ATT - Acceptance Thermal Test (See JSC-SP-T-0023)

AVT - Acceptance Vibration Test (See JSC-SP-T-0023)

CEIT - Crew Equipment Interface Test

D&C - Display and Control

EMC - Electromagnetic Compatibility (See JSC-SL-E-0001 and SL-E-0002)

EMI - Electromagnetic Interference (See JSC-SL-E-0001 and SL-E-0002)

EVA - Extravehicular activity

ICD - Interface Control Document

IVA - Intravehicular activity

IVT - Interface Verification Test

MUA - Materials usage agreement.

OMRSD - Operations Maintenance Requirements Specification Document

PDA - Pre Delivery Acceptance

PIA - Pre Installation Acceptance

QATT - Qualification Acceptance Thermal Test (See JSC-SP-T-0023)

QAVT - Qualification Acceptance Vibration Test (See JSC-SP-T-0023)

QTT - Qualification Thermal Test (See JSC-SP-T-0023)

QTVT - Qualification Thermal Vacuum Test (See JSC-SP-T-0023)

QVT - Qualification Vibration Test (See JSC-SP-T-0023)

TPS - Test preperation sheet

<table style="width:100%;">
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 8%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Problem Reporting and Corrective Action
(PRACA)</strong></p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>16 Aug 96</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>14</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>To report problems (as defined below) and describe their
resolutions.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>x</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4"><p>6. References <em>(Optional)</em></p>
<p>JSC 24636</p></td>
<td colspan="7">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

**Reference Documents**:

> a\. SSP 30223, \"Problem Reporting and Corrective Action for the Space
> Station Program\"
>
> b\. SSP 30524, \"Problem Reporting and Corrective Action (PRACA) Data
> System (PDS) Requirements Definition Document (RDD)\"
>
> c\. NSTS 08126, \"Space Shuttle Problem Reporting and Corrective
> Action (PRACA) System Requirements\"
>
> d\. JSC 24636, \"JSC Orbiter and Government Furnished Equipment (GFE)
> Problem Reporting and Corrective Action (PRACA) Requirements\"

**SCOPE**:

PRACA reportable problems are defined as functional failures, overstress
or potential overstress of hardware, unsatisfactory conditions, and
unexplained anomalies which occur on flight products, flight-like
products, or ground support equipment (GSE) during qualification testing
(Shuttle and Shuttle/Station common use only) and during or subsequent
to acceptance testing (Shuttle, Station, and common use). GSE reporting
is limited to GSE problems which could result in loss of personnel
capability or loss of vehicle systems.

**CONTENTS**:

A. Initial notification/report shall occur within 24 hours after
isolation to the Line Replaceable Unit/Orbital Replacement Unit level or
lower and shall include the following data:

> 1\. A uniquely identifiable report number;
>
> 2\. The date the problem occurred if known, if unknown the date it was
> detected;
>
> 3\. The location at the time of occurrence/detection;
>
> 4\. The non-conforming LRU/ ORU product identification:
>
> a\. part name;
>
> b\. part number;
>
> c\. serial number, logistical control number, lot number, or version
> number (if applicable);
>
> d\. manufacturer.
>
> 5\. The test or operation (code)\* being performed at time of
> occurrence;
>
> 6\. The prevalent condition (code)\* at time of occurrence;
>
> 7\. The failure mode (code)\* experienced;
>
> 8\. Brief narrative description of nonconformance, including
> comparison of expected events with actual events (or results);
>
> 9\. A brief title;
>
> 10\. Technical point of contact name;
>
> 11\. Technical point of contact phone number;

12\. System/ Subsystem(s) affected (if known);\
13. Vehicle effectivity;

> 14\. LRU criticality;
>
> 15\. Logistics Control Number (Station only);
>
> 16\. Fracture Critical Indicator (Station only

B. Additional preliminary data shall be delivered within 5 working days
after the initial notification. Data shall include any
additions/modifications to previous submittal plus:

> 1\. Next higher assembly (as applicable) identification:
>
> a\. part number;
>
> b\. part name;
>
> c\. serial number, logistical control number, or version number;
>
> d\. manufacturer.
>
> 2\. FMEA number (if applicable);
>
> 3\. Nonconforming product manufacturer\'s CAGE code;
>
> 4\. Time/cycles in use (if applicable);
>
> 5\. FMEA criticality

C. The final resolution (close-out) shall include the following
additional data:

> 1\. Resolution narrative which includes
>
> a\. Corrective action that has been established including reference to
> released documentation establishing this corrective action, or
>
> b\. When not establishing corrective action to preclude recurrence of
> the problem provide a narrative explanation which documents the
> rationale. This narrative shall also include the following:
>
> (1.) Effects on mission, if nonconformance recurred, and recommended
> operational work around procedures;
>
> (2.) Methods of detecting the problem inflight/on-orbit. Indicate how
> the crew will be made aware of the problem or what automatic system
> detects or corrects the problem;
>
> (3.) When last test of product, prior to mission, is performed;
>
> (4.) Assurance that explanations using redundancy and/or alternate
> modes of operation as one of the elements do not negate each other;
>
> 2\. All end items and/or missions that may be affected by the problem;
>
> 3\. Previous history of nonconforming product;
>
> 4\. Problem report numbers related to the same problem;
>
> 5\. Cause (code)\* which indicates what action caused the failure;
>
> 6\. Defect (code)\* which indicates what defect caused the failure;
>
> 7\. Material (code)\* which indicates the material that failed;
>
> 8\. Recurrence control (code)\* which indicates what action was taken
> as a result of the nonconformance;
>
> 9\. Indication as to whether or not the problem will cause a revision
> to a CIL;
>
> 10\. Related document identification (waiver number, CCB directive,
> etc.);
>
> 11\. Date of resolution.
>
> 12\. The non-conforming Shop Replaceable Replacement Unit (assembly
> within LRU) product identification:
>
> a\. part name;
>
> b\. part number;
>
> c\. serial number, logistical control number, lot number, or version
> number (if applicable);
>
> d\. manufacturer.
>
> 13\. The non-conforming article (lowest traceable) product
> identification:
>
> a\. part name;
>
> b\. part number;
>
> c\. serial number, logistical control number, lot number, or version
> number (if applicable);
>
> d\. manufacturer.

\*Codes are per: SSP 30524, D.1-3.1, Table F Type Element Code
Translations (Station Program GFE)

> JSC 24636, Appendix B, PRACA Codes (Shuttle Program GFE)

**FORMAT**:

Reportable problems on all hardware common to both the Shuttle Program
GFE and Station Program GFE as well as problems on hardware which is
unique to Station Program GFE are entered initially into the ISS PRACA
system. The ISS PRACA system can be accessed via the World Wide Web. To
access PRACA reports or to submit failure reports use the PRACA on the
WEB home page using the following address:

<http://issa-www.jsc.nasa.gov/ss/issapt/praca_on_the_web.html>

If a message comes back \"Forbidden\" then apply for Space Station Team
Page Bulletin Board access using the following URL address:

<http://issa-www.jsc.nasa.gov/ss/admin/ro.html>

Reportable problems on all hardware which is unique to Shuttle Program
GFE shall be reported as follows:

> Reports shall be sent to: JSC PRACA Center
>
> NASA/JSC NS43/Bldg 17
>
> Houston, Texas 77058
>
> voice: Primary 713-244-1937
>
> Secondary 713-244-1941
>
> facsimile mail: Primary 713-244-1848
>
> Secondary 713-244-18
>
> hours of operation: 8:00 a.m. - 4:30 p.m. Central, Monday thru Friday

**MAINTENANCE**: Update as required.

<table style="width:100%;">
<colgroup>
<col style="width: 31%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 7%" />
<col style="width: 10%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 27%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3">1. DRD Title<br />
<strong>Certification/Acceptance Requirements</strong> <strong>Document
(CARD)</strong></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>17 Mar 97</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>15</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>To provide JSC cognizance of plans for hardware certification and
acceptance, and results thereof.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>x</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4"><p>6. References <em>(Optional)</em></p>
<p>NHB 5300.4 (1D-2)</p></td>
<td colspan="7"><p>7. Interrelationships<em>(e.g., with other DRDs)
(Optional)</em></p>
<p>SMACAR</p></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

**[Scope]{.underline}**: The C/ARR is a two part document. Part one
addresses hardware definition, verification requirements, and acceptance
and certification environmental requirements. Part two is the report at
completion of all analyses and required testing. The requirements
document (part one) is submitted for approval in the Preliminary Design
Review and Critical Design Review timeframe. The report (part two) is
submitted within 30 days after completion of required certification
activities.

**[Format]{.underline}**: The report format shall be as defined in the
report contents below.

**[Contents]{.underline}**:

a\. [General Description]{.underline}. This includes a brief outline of
projected testing and procedures. Existing procedures expected to be
used in this activity shall be cited.

b\. [Schedule]{.underline}. This section provides the schedule of
projected events. Include events such as Test Readiness Reviews, Quality
Site Approvals, etc., as applicable.

> c\. [Hardware definition]{.underline}.
>
> 1\) Part name and number of articles being certified
>
> 2\) Serial and part number of specimens to be tested
>
> 3\) Dispositions of test specimens

d\. [Verification Methods]{.underline} (matrix to be provided).
Verification methods to verify the hardware meets the technical
requirements of the applicable contract end-item specification shall be
defined in a verification matrix which shall be prepared in accordance
with the form shown in figure 1 (included in the C/ARR) except when the
requirements are included in the specification assembly drawing.

> 1\) Type of tests to be conducted
>
> 2\) Analyses to be performed
>
> e\. [Test Requirements]{.underline}.
>
> 1\) Environmental acceptance test requirements
>
> 2\) Certification environmental requirements
>
> a\) Life-cycle requirements
>
> b\) Test duration

**[Contents]{.underline}**: (continued)

> e\. [Test Requirements]{.underline} (continued)
>
> 2\) Certification environmental requirements (continued)
>
> c\) Operational mode (on/off) of the equipment
>
> d\) Pass/fail criteria and tolerance
>
> e\) Functional test prior to, during, and after testing
>
> f\) Retest requirements
>
> g\) Allowable maintenance, if any
>
> f\. [Report]{.underline}.
>
> 1\) Engineering analyses
>
> a\) Requirements
>
> b\) Analysis objectives
>
> c\) Analysis details and logic
>
> 2\) Test results
>
> a\) Test objective (from part one of the document)
>
> b\) Test setup
>
> c\) As-run test procedure with proper validation
>
> d\) Failures and resolution data
>
> e\) Other test results
>
> f\) Reduction of test data
>
> g\) Laboratory notes with proper validation (when appropriate)
>
> h\) Conclusions

**[Maintenance]{.underline}**: Update as required.

<table>
<colgroup>
<col style="width: 30%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 8%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Space Station Reliability and Maintainability Predictions
Report</strong></p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>22 Aug 96</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>16</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>To status quantitative R&amp;M characteristics of Space Station
functions, capabilities, and equipments.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>X</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4"><p>6. References <em>(Optional)</em></p>
<p>-SSP 41000, "System Specification for the International Space
Station," paragraph 3.2.4</p>
<p>-MIL-STD-756</p></td>
<td colspan="7"><p>7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></p>
<p>FMEA;CIL</p></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

**SCOPE**: Report shall consist of the Reliability and Maintainability
predictions for Space Station flight hardware.

**CONTENT**: The report shall consist of three volumes, as follows. Each
volume may be submitted and approved independently. The volumes may be
further subdivided according to subsystem architecture and/or end items,
as appropriate.

[Volume I]{.underline}

1\) General and programmatic information

2\) Top-level groundrules and assumptions used in performing the R&M
analyses.

[Volume II]{.underline}

1\) R&M source data in accordance with Table 1.

2\) Failure Detection Isolation and Recovery Assessment Information (see
Table 2).

3\) Perform Preventative Maintenance Assessment per decision matrix (see
Figure 1).

[Volume III]{.underline}

FMEA/CIL summary information per SSP 30234, including summary tables
(index), list of critical items, and identification of incomplete design
areas.

**FORMAT**: See R&M Source Data field definitions in Table 1. R&M Source
Data shall be submitted in an electronic table (see Table 3) to be
entered into the ISSP Vehicle Master Database (VMDB).

**NEED DATE or MILESTONE REQUIRING R&M PREDICTIONS REPORTS SUPPORT**:

The R&M Predictions Report data requirements applies to all flight
hardware and must be assessable in the Vehicle Master Database (VMDB) 7
days prior to the IDR that covers the first flight deployment of the
hardware.

The data provided for the first applicable IDR may be preliminary data
(data integrity equivalent to that expected at a PDR). If the initial
submittal is preliminary data, final data must be provided to support a
subsequent IDR (data integrity equivalent to that expected at a CDR).

![](media/image2.png){width="6.59375in" height="8.625in"}

![](media/image3.wmf)

**TABLE 1**: R&M SOURCE DATA FIELD DEFINITION TABLE

Col DESCRIPTION

**A.** **Item Name** - R&M attributes shall be entered for each item
which is to be maintained on orbit. The Vehicle Master Data Base (VMDB)
nomenclature shall be used for all R&M reporting. R&M is not responsible
to develop the Item Name but shall use it as a reference for reporting
R&M parameters.

**B.** **Drawing/Part Number -** R&M attributes shall be referenced to
the Drawing/Part number in the VMDB. R&M is not responsible to develop
the Drawing/Part number but shall use it as a reference for reporting
R&M parameters.

**F. Reliability Class -** Reliability classification. The six
reliability class codes are as follows:

> CODE DESCRIPTION
>
> 1 Electronic - equipment which primarily contains digital or low power
> analog electronics. Moving parts are high power electrical equipment
> normally constitute less than 5% of the item failure rate in the
> classification. Electronic type will typically have a fairly high
> level of Built-In-Testing (BIT).
>
> 2 Electrical - equipment which performs electrical power distribution,
> power storage, signal distribution, and/or radio frequency radiation
> functions. Moving parts or low power electronics normally constitute
> less than 5% of the item failure rate in this classification.
> Electrical types will typically have a low level of BIT.
>
> 3 Electro-Mechanical - equipment which contains electrical/electronic
> and mechanical parts, including devices which use electrical power to
> produce mechanical motion, and devices which use mechanical motion to
> produce electrical power or signals. Electro - Mechanical items should
> contain more than 5% electrical/electronic and more than 5% mechanical
> parts by failure rate contribution in this classification.
>
> 4 Mechanical - equipment which primarily consists of moving parts,
> fluid handling equipment(including thermal systems), and or seals.
> High power electrical equipment or low power electronics normally
> constitute less than 5% of the failure rate in this classification.
>
> 5 Structural with Crew Contact - equipment which is primarily
> structural but encounters planned crew contact or provides equipment
> protection. This type specifically includes doors, covers, panels,
> hatches, micro meteoroid/debrise shields, and thermal blankets.
>
> 6 Structural with no crew Contact - equipment which is load bearing.
> Moving parts, electronics, and electrical equipment normally
> constitute less than 5% of the failure rate in this classification.
> Structural items should not normally encounter planned crew contact.

**G. IVA/EVA/Robotics Code** - The code which describes the level of
robotic compatibility of the equipment. The codes are as follows:

> **CODE DESCRIPTION**
>
> **0** Equipment located in pressurized area.
>
> **1** Equipment can be maintained only by EVA crew member. No robotic
> support is required or intended.
>
> **2** Equipment can be maintained using SPDM without EVA. Equipment is
> SPDM compatible. Compatibility consists of Equipment to SPDM
> interface. EVA can provide maintenance support in a backup role.
>
> **3** Equipment can be maintained using SSRMS without EVA. Equipment
> is SSRMS compatible. Compatibility consists of Equipment to SSRMS
> interface. Equipment must be equipped with SSRMS grapple fixture. EVA
> can provide maintenance support in a backup role.
>
> **4** Equipment requires combined SPDM/EVA operations for maintenance.
>
> **5** Equipment requires EVA crew member to be positioned on SSRMS for
> access to the worksite. Equipment requires no robotic compatibility.
>
> **6** Equipment requires the Mobile Servicing System/SSRMS for
> transportation to the EVA worksite. Dimensions or mass of equipment to
> be replaced are not compatible with EVA/CETA translation. Equipment
> must be equipped with SSRMS grapple fixture.

**J MTBF** - Mean Time Between Failures (\"Hot\" or \"operating\" MTBF).
The estimated average time in hours between failures due to random
effects under nominal operating conditions at the maintainable equipment
level. Redundancy within the maintainable equipment item which is not
necessary to meet failure tolerance requirements (e.g., component
redundancy used for reducing maintenance demand) shall be modeled so as
to improve the reported MTBF. Worst case estimates shall not be used.
Failures of components which are used only during installation or
removal (such as deployment motors and mechanisms) shall be excluded
where maintenance would not be caused by the components failure.
Failures of components which cause degradation of the equipment within
the specified limit shall also be excluded. For complex items having
components operating at different duty cycles, the operating MTBF may be
adjusted to a duty cycle of 1.0. MTBF does not include failures due to
Micrometeoroid/Orbital Debris (MM/OD).

**K Deleted**

**L** **Wearout Life** - Expected time to failure (in calendar years at
the stated average duty cycles) due to wear-out, degradation, or fatigue
conditions in the absence of random failures for age or cycle life
limited items. Wearout life should be used as an estimate of
characteristic life (L Char) in the algorithms (Table 3). Best available
data and engineering judgment should be used to estimate wearout life as
the time when 63 percent of a population would have failed due to
wearout/aging conditions alone. Minimum design life shall not be
reported as the wearout life. No life limit should be reported if the
expected wearout life is 20 years or greater.

**M MTBPM: Removal/Replacement** - Mean Time Between Preventive
Maintenance for Removal & Replacement - The average time in calendar
hours between all preventive maintenance (PM) replacements. Care should
be given when determining if preventive maintenance replacements should
be performed in place of waiting until maintenance is required due to
gradual performance degradation and eventual wearout (life limits).

**Col DESCRIPTION**

**N MTBPM - Inspect/Service -** Mean Time Between Preventive Maintenance
for Inspection - The average time between PM inspections and/or
servicing expressed in calendar hours. A single MTBPM - Inspect/Service
parameter shall be developed for any equipment items requiring multiple
servicing and/or inspection actions.

**Q CM IVA MTTR** - Mean Time to Repair - Nominal elapsed IVA crew hours
at the worksite. The MTTR includes remove, replace and fault detection
time. Computed for zero-g using task standards. In situations where
developer does not control elemental task time enter N/A as the task
time.

**R Detection Percentage** - Percentage of ORU failure modes detected by
BIT or other diagnostic techniques.

**TABLE 2: FAILURE DETECTION DATA DEFINITION TABLE**

**Description**

**Function** - Identify the function supported by the ORU.

**ORU** - Identify the ORU associated with the failure mode code.

**Failure Mode Code** - Reference the failure mode code for each ORU
failure mode as identified in the FMEA.

**Cat/Crit Hazard \< 24 Hours (Y/N)** - May a critical or catastrophic
hazard occur in less than 24 hours as a result of the failure mode (Yes
or No)

**Detection: A/M/N** - Specify whether **A**utomatic, **M**anual or
**N**o detection is provided for the failure mode.

**Detection: Failure Signature Algorithms** - Describe the algorithm
(including sensor/system states) used to detect the failure mode.

**Detection: SRS/LSAR Reference** - Provided a reference to the SRS that
documents automatic detection, and/or the LSAR that documents manual
detection procedures.

**Safe: A/M/N** - Specify whether **A**utomatic, **M**anual or **N**o
on-orbit safing is provided for the failure mode.

**Safe: Algorithms** - Describe the algorithm (including sensor/system
states) used to safe a hazard that results from the failure mode.

**Safe: SRS/LSAR Reference** - Provided a reference to the SRS that
documents automatic safing, and/or the LSAR that documents manual safing
procedures.

**TABLE 3: R&M Source Data Format To Be Entered Into the ISSP Vehicle
Master Database (VMDB).**

**[Input Col. \# Input Column Name]{.underline}**

1 Part Number

2 Mfg. Cage Code

3 Maintainability Serial Number

4 Failure Mode Code

5 Maint. Item Name

6 Maint. Distrib. System Name

7 Maint. Subsystem Name

8 Maint. ORU Function

9 Maint. ORU Des.

10 Maint. Location

11 Maint. Quantity

12 Reliability Class Code

13 Robotics Code

14 Avg. Duty Cycle Prior AC

15 Avg. Duty Cycle After AC

16 MTBF Hot

17 MTBF Cold

18 MTBCF

19 Wearout Life Amount

20 MTBPM RR

21 MTBPM IS

22 CM EVA MTTR

23 CM EVA Crew Size

24 CM IVA MTTR

25 CM IVA Crew Size

26 CM EVR MTTR

27 PM RR EVA MTTR

28 PM RR EVA Crew Size

29 PM RR IVA MTTR

30 PM RR IVA Crew Size

31 PM RR EVR MTTR

32 PM IS EVA MTTR

33 PM IS EVA Crew Size

34 PM IS IVA MTTR

35 PM IS IVA Crew Size

36 PM IS EVR MTTR

37 Manifest Flight

38 Activation Flight

39 EVA RMAT Overhead Code

40 EVR RMAT Overhead Code

41 IVA RMAT Overhead Code

42 EVA Total Maint. Crew Time

43 IVA Total Maint. Crew Time

44 EVR Total Maint. Crew Time

45 Total Maint. Actions

46 Auto 24 Des.

47 Crit. Hazard 24 Hr. Des.

48 Criticality Code

49 Detection Automation Code

50 Detection Algorithm

51 Detection SRS LSAR Ref

52 Isolation Ambiguity Level Mnt.

53 Isolation Automation Code

54 Isolation Algorithm Mnt.

55 Isolation SRS LSAR Ref Mnt.

56 Isolation Automation Code Reco

57 Isolation Algorithm Reco

58 Isolation SRS LSAR Ref Reco

59 Recovery Automation Code

60 Recovery Algorithm

61 Recovery SRS LSAR Ref

62 Safe Automation Code

63 Safe Algorithm

64 Safe SRS LSAR Ref

**JSC DRD REQUIREMENTS DESCRIPTION (DRD)**

<table>
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 3%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 10%" />
<col style="width: 8%" />
<col style="width: 2%" />
<col style="width: 3%" />
<col style="width: 25%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Security Reporting Requirements</strong></p></td>
<td colspan="3"><p>2. Current Version Date</p>
<p>6/20/97</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>17</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="10"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>Identifies reporting requirements to JSC Security which affect the
contractor's facility and/or personnel and also ensures compliance with
applicable NASA and DOD security regulations involving industrial,
information, personnel, and administrative/program security.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="2">Technical</td>
<td>X</td>
<td colspan="2">Administrative</td>
<td></td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="10">6. References <em>(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="10">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

**A. Provide the following information, in writing (reports, letters,
notification), in accordance with the security regulations identified as
applicable documents in item C. of this DRD:**

1\. [Industrial, Information, & Personnel Security:]{.underline}

a\. Visit request letters for cleared employees.

b\. Annual renewal visit request letters for cleared employees.

c\. Changed conditions affecting the contractor\'s facility security
clearance (i.e., OODEPs-Officers, Owners, Directors & Executive
Personnel; FOCI-Foreign Ownership, Control, or Influence, etc.).

d\. Change in a cleared employee\'s status and/or an employee
participating in special access programs such as the Mission Critical
Space Systems Personnel Reliability Program (PRP), NASA Resource
Protection (NRP) Program, and Information Technology (IT/AIS) Security
Program (i.e., name; marital status; citizenship; death; termination of
employment or clearance; different position or work
assignment/relocation; employee becomes a representative of a foreign
interest, etc.).

e\. Adverse information reports on all non-US. employees, employees with
personnel security clearances, and employees participating in the NRP,
PRP, and/or IT programs at JSC.

f\. Copies of any written reports submitted to the FBI regarding
information coming to the contractor\'s attention concerning actual,
probable, or possible espionage, sabotage, or subversive activities at
any of its locations.

g\. Security Violations or Incidents including, but not limited to, the
following:

> \(1\) Any loss, compromise, or suspected compromise of classified
> information, foreign or domestic, shall be reported as follows:
>
> \(a\) Initial report \-- information obtained during the contractor\'s
> preliminary inquiry that confirms that a loss, compromise, or
> suspected compromise of any classified information has occurred.

(b) Final report \-- information based on the completed investigation
    which contains all employee data and relevant facts pertaining to
    the employee(s) primarily responsible for the incident; statement of
    corrective action taken to preclude a recurrence; any disciplinary
    action taken against the responsible employee(s); and specific
    reasons for reaching the conclusion that loss, compromise, or
    suspected compromise occurred or did not occur.

> \(2\) Any \"FOUO\" (For Official Use Only) information released
> outside a contractor\'s facility, except to NASA representatives.
>
> \(3\) Suspicious contacts \-- efforts by any individual to obtain
> illegal or unauthorized access to classified information and all
> contacts by cleared employees with known or suspected intelligence
> officers from any country (or any contact which suggests that the
> employees concerned may be the target of an attempted exploitation by
> the intelligence services of another country.
>
> \(4\) Security equipment vulnerabilities, disposition of classified
> material terminated from accountability, and/or unauthorized receipt
> of classified material,

2\. [Administrative/Physical Security:]{.underline}

In compliance with established internal procedures, the contractor FSO
or security manager shall submit a \"Contractor Termination Letter\" to
JSC Security for each

affected employee which includes certification that the following
government property and/or program participation were returned,
destroyed, or canceled:

a\. Badge(s)

b\. CAA (Controlled Access Area) Card(s)

c\. Decal(s)

d\. Key(s)

e\. Employee\'s Participation in PRP, NRP, and/or AIS \-- Identify
program(s)

3\. [Other Reportable Incidents (Information Required)]{.underline}

1\. Felonies committed by contractor personnel.

2\. Espionage or Sabotage.

3\. Bombing incidents at contractor facilities or threats which severely
impact contract or center activities.

4\. Actual demonstrations/strikes (in or outside JSC gates) or planned
demonstrations or strikes where violence is threatened involving
contractor personnel.

5\. Workplace violence (shootings or other violent acts).

6\. Any type of incident occurring on NASA/JSC property which results in
the death of a person.

7\. Security-related incidents in which the media has become involved
and negative publicity is expected.

8\. An adverse event in an automated systems environment that would be
of concern to NASA management due to a potential for public interest,
embarrassment, interruption to computer/network services or protective
controls, damage, disaster, discovery of a new vulnerability, etc.

9\. Threats against NASA property and personnel.

10\. Threats that shall impact NASA missions.

11\. Any other type of incident which might have security implications.

**B. The requested information (reports, letters, notification)
identified in A. shall be delivered as necessary, except A.1.b. which
shall be delivered on an annual basis. Delivery instructions are as
follows:**

1\. Mail/deliver information listed in A.1.a. through A.1.f. to the
NASA/JSC Industrial Security Specialist, Mail Code JB2.

2\. Mail/deliver information listed in A.1.g. to the NASA/JSC
Information Security Specialist, Mail Code JB2; cc the JSC Industrial
Security Specialist.

3\. Mail/deliver information listed in A.2. to the NASA/JSC Badging
Manager, Mail

Code JB2; cc JSC Personnel Security (Mail Code JB2) and Security Help
Desk

(Building 110).

4\. Mail/deliver information listed in A.3 to the NASA/JSC Security
Branch Chief,

Mail Code JB2.

**C. Applicable Documents**

NHB 1620.3, NASA Security Handbook

JHB 1600.3, JSC Security Handbook

DOD 5220, 22-M, National Industrial Security Program Operating Manual
(NISPOM)

<table>
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 8%" />
<col style="width: 10%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p>Report, Quarterly Printing</p></td>
<td colspan="4">2. Current Version Date</td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>18</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>To document compliance with Table XX of the contract and with
Government Printing and Binding Regulations</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td></td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4">6. References <em>(Optional)</em></td>
<td colspan="7">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

The report will be submitted each quarter to the Installation Printing
Management Officer (IPMO/JM8). It will list all jobs in the categories
below that were not processed through the Information Services
OFFICE/GA/BT4. Information provided for each category should contain
name of job, number of originals and copies, cost, and production source
and date.

> a\. All printing produced from film negative(s).
>
> b\. All documents using reinforced Die cut dividers.
>
> c\. All printing using more than one color of ink.
>
> d\. All printing and reproduction of a single page in excess of 5,000
> copies.
>
> e\. All printing and reproduction on pages having an image area larger
> than 10 ¾\" X 14 ¼.\"
>
> f\. All printing and reproduction of multiple page documents when the
> total production pages exceed
>
> 25,000.
>
> g\. Production of perfect bound documents.

<table>
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 7%" />
<col style="width: 10%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p>Monthly Small Disadvantage Business (SDB) Contracting Report</p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>1/95</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>19</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>Each Monthly, SDB Subcontracting Report will be used by NASA to
monitor the contractor's awards to SDB's</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td>X</td>
<td colspan="2">Administrative</td>
<td></td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4"><p>6. References <em>(Optional)</em></p>
<p>Article H.6 NASA Plan for Socially and Economically</p></td>
<td colspan="7"><p>7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></p>
<p>Attachment J-3 Small Business (SB) and SDB Subcontracting
Plan</p></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

Beginning January 1, 1994, the contractor shall submit three copies of
the SDB Subcontracting Report each month by the 20^th^ calendar day
after the end of the reporting month.

Reports shall include the following:

a\. Provide monthly and cumulative total dollars awarded to SDB\'s
commencing January 1, 1994, according to the requirements of the
approved SB/SDB Plan. (Add totals of b, c, and d below.)

b\. Provide the total dollars awarded to SDB\'s by the prime contractor,
excluding those awards made to those subcontractors contributing to the
prime contact level-of-effort described in article H.4. Provide the SDB
incurred costs for those SDB subcontractors contributing to the prime
contract level-of-effort.

c\. Provide the total dollars awarded by SB Subcontractors to SDB.

d\. Provide the total dollars awarded by Large Business Subcontractors
to SDB\'s.

e\. Provide a consolidated listing of awards (made by the prime and
subcontractors) to SDB\'s valued at \$25,000 or more during the quarter
reported, excluding those awards made to those subcontractors
contributing to the prime contract level-of-effort. List the incurred
costs for each of the SDB subcontractors contributing to the prime
contract level-of-effort. Listing to include: Purchase order number,
vendor name, NASA JSC division or office supported, description of what
is being acquired, cost element under which the prime will report costs
on the NASA Form 533, dollars awarded, delivery date, or period of
performance. SDB awards of less than \$25,000 shall be summarized.

f\. Provide a brief description of planned SDB awards for the following
month in order to track the contractor\'s planned activities against
achievement of those activities.

g\. Provide a brief description of planned awards for the following
month to SDB concerns in order to track the contractor\'s planned
activities against achievement of those activities and the SDB estimated
dollar awards.

<table>
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 8%" />
<col style="width: 10%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p>Logistics Information</p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>December 1991. Revised January 1995</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>20</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>To provide logistics reports relating to the JSC.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td></td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4"><p>6. References <em>(Optional)</em></p>
<p>See DRL</p></td>
<td colspan="7">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

**A. RESERVED**

**B. LOGISTICS REPORTS**

The following reports are required to be prepared when on site storage
of material exceeds \$20,000 for stores or standby stock or \$75,000 for
program stock in one location.

**1. \*Data Input for NASA Form 1324, Semi-annual Report of Personal
Property Management Operations**.

This semi-annual report defines the following line item data elements as
of 3/15 and 9/15 of each year:

> Material Inventory Status
>
> Material Inventory Activity
>
> Material Acquisition Activity
>
> Material Receiving Activity
>
> Logistics Personnel Resources Report
>
> Reference: NHB 4100
>
> Due Dates: 3/25 and 9/25

**2. \*Data Input for NASA FMD 1489, Semi-annual Analysis of Fixed
Inventory Assets\"**

This semi-annual report defines the following monetary data elements as
of 3/15 and 9/15 of each year:

Starting Price; Price of Receipts, Price of Issues, Ending Price

Note: This will be reported by each Object Class code stocked in the
storeroom. Separate reports are required for Stores, Program, and
Standby stock. (See the JSC Stores Stock Catalog for a detailed
explanation of these codes.

Reference: NHB 4100

Due Date: 3/25 and 9/25

\*Forms for DATA Input are available through JB3/Contract Property
Group.

**3. NASA Form 1619, Physical Inventory of Materials Annual Report**.

This annual report identifies the sampling inventory actions completed
by the contractor. This report contains the following data by Object
Class code: (See the JSC Stores Catalog preface for detailed explanation
of these codes).

Line items and dollar value of items inventoried; number of line items
with variance: dollar value of discrepant items, including overage,
storage and gross discrepancies.

Identify whether inventory items are stores, program or standby stock,
and also identify the staff hours and dollar value expended in
accomplishing and reconciling the inventory.

A brief explanation of cause of discrepancies and actions to minimize
the change for recurrence.

Reference: NHB 4100

Due Date: 9/25

NOTE: All the above are to treat Contractor-Acquired Material (CAM) and
Government-Furnished Material (GFM) as one lot.

**4. Quarterly Report of Contractor-Acquired Material (CAM)**

This report will consist of two transfer documents (DD Form 1149) that
identify material purchased and received by the Contractor for on-site
use. The two documents will be differentiated as follows:

a\. Items bought for direct consumption on site.

b\. Items issued to storeroom(s) that will impact the dollar value of
assets on hand.

The DD Forms 1149 will be transferring accountability of these to NASA
and will be accompanied by requisitions, issue documents, test
preparation sheets (if flight material destined for a bond room), or any
other similar form approved for use by the JSC Property Administrator.
The DD Form 1149 will identify total number of line items and total
value.

Reference: JSCM 5151 (current version)

Quarterly Due Dates: [Reporting Period]{.underline} [Due
date]{.underline}

12/16 through 3/15 3/25

3/16 through 6/15 6/25

6/16 through 9/15 9/25

9/16 through 12/15 12/25

NOTE: All of these reports are to be submitted to JB3/JSC Property
Administrator.

**C. TRANSPORTATION REPORTS**

Transportation reporting requirements are specified below:

**1. Reserved**

**2. Mileage Report**

a\. A mileage report (ref. JSCM 6000-A) shall be submitted for all
Government vehicles assigned to the contractor. The report shall
identify each vehicle by license tag number and odometer reading. It
shall be submitted by the third day of each month to the Logistics
Division, Transportation Branch. JB7.

b\. The mileage that is reported should be the mileage recorded from the
21^st^ of the previous month through the 20^th^ of the report month.

**3. Vehicle Rejustification Request**

An annual rejustification (See paragraph 6.300 of JSCM 6000-A.) shall be
submitted on JSC Form 971 for all general purpose vehicles assigned to
the contractor. These requests shall be submitted on June 15 of each
year to the JSC Transportation Office, JB7.

**D. LOGISTICS OPERATING PLAN**

The contractor shall develop a logistics plan (LOP) that will include
procedures and the plan for providing the required reports.

\*\*The procedures, which require Government approval (JB3/Property
Administrator), shall encompass the following Federal Acquisition
Regulations (FAR) (plus NASA FAR Supplements and JSC Supplements)
provisions:

**\_\_\_\_**Property responsibilities - FAR 45.502

**\_\_\_\_**Property Records and Reports - FAR 45.505

**\_\_\_\_**Property Identification - FAR 45.506

**\_\_\_\_**Property Segregation - FAR 45.507

**\_\_\_\_**Physical Inventories - FAR 45.508

**\_\_\_\_**Property Care, Maintenance, Use - 45.509

**\_\_\_\_**Property in possession of Subcontractor - FAR 45.510

**\_\_\_\_**Property Disposal - FAR 45.6

**\_\_\_\_**Property Documentation - FAR 53 plus DD 250 for acceptance,
DD 1149 for transfer of accountability.

**\_\_\_\_**Property acquiring, shipping, receiving, transporting,
packaging, warehousing, and issuing - No FAR part.

**\_\_\_\_**Property provisioning (if applicable) - No FAR part.

\*\*DENOTES CHANGE

**JSC DATA REQUIREMENTS DESCRIPTION**

(Based on JSC-STD-123)

<table style="width:100%;">
<colgroup>
<col style="width: 30%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 7%" />
<col style="width: 10%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p>Financial Management Report</p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>July 23, 1997</p></td>
<td colspan="3">3. DRL Line Item 21</td>
<td><p>RFP/Contract No.</p>
<p>NAS9/19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use <em>(Define need for, intended use of, and/or
anticipated results of data)</em></p>
<p>Provide a basis for reporting and evaluating cost and expenditure in
support of this contract.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td>X</td>
<td colspan="2">Administrative</td>
<td></td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4"><p>6. References <em>(Optional)</em></p>
<p>NHB 9501.2c</p></td>
<td colspan="7">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information <em>(Include complete
instructions for document preparation)</em></td>
</tr>
</tbody>
</table>

**A. NF 533 Report**

> The contractor shall submit form 533M prepared in accordance with
> instructions contained in the NHB 9501.2C as amended or revised. Cost
> shall be identified and recorded in the period of time when the
> benefit is received or incurred without regard to the date of payment.
> Each monthly report is due no later than the 10th calendar day of the
> month. The following description outlines the intent of the government
> to combine the requirements of the NF533 on ETA and SPDEO into one
> NF533 document that can be used on both schedules, however, the
> details of the elements reported are included in attachment A: Formats
> for contract 533, Summary, Task Order, and STO level reports.
>
> 1\. A \"Contract\" summary page shall be required where all elements
> of cost referenced shall be shown.
>
> 2\. A separate \"Schedule\" summary page shall be required for each
> schedule where all elements of cost referenced shall be shown.
>
> 3\. A separate summary page reflecting total cost shall be required at
> the division/office, and directorate levels for each of the following
> categories: True Completion Form (TCF), Completion Form Task Orders
> (CFT\'s) and Level of Effort task orders (LOET\'s).
>
> 4\. Under schedule B: a separate report identifying costs by mission
> shall be required for each task order prior to October 1, 1996.
>
> 5\. A Task Order and subtask order level report shall be required to
> report referenced cost elements at the task order/subtask order level
> for each division/office supported under schedule A and for each
> contract segment under schedule B. This section of the 533 shall
> include TCF, CFT\'s, and LOET\'s.
>
> 6\. Distribution:
>
> a\. After November 1, 1997, one complete file copy of the 533 shall be
> electronically deposited into a secured electronic system namely the
> \"ETAC\" share area file under the NASA/JSC designated computer system
> on a monthly basis on the due date. All other hard copy deliveries
> shall cease except for 6.b. and 6. c. below.
>
> b\. Two complete hard copies of the NF 533 shall be delivered on a
> monthly basis on or before the due date. One shall be delivered to the
> BE/SEAT Contracting Officer and the other shall be delivered to the
> BE/SEAT Contract Business Manager
>
> c\. One hard copy of the NF 533 SEAT Contract-level Summary shall be
> delivered to LF6/Cost Accounting.

**B. Variance Analysis Report**

> The contractor shall provide variance reports as describes below no
> later than the 15^th^ calendar day of the month.
>
> 1\. A Contract level variance Analysis report as previously provided
> as Exhibit 1 under the ETA contract.
>
> 2\. A Schedule level variance Analysis report as previously provided
> as Exhibit 1 under the ETA contract.
>
> 3\. By schedule, a variance report for each Task Order or STO,
> whichever pertains, with tolerances to be determined by the
> contractor.
>
> 4\. Distribution:
>
> a\. After November 1, 1997, one complete file copy of the Variance
> Analysis Report shall be electronically deposited into a secured
> electronic system namely the \"ETAC\" share area file under the
> NASA/JSC designated computer system on or before the due date. All
> other hard copy deliveries shall cease except for 4.b. and 4.c. below.
>
> b\. One complete hard copy of the Variance Analysis Report shall be
> delivered on a monthly basis on or before the due date to the BE/SEAT
> Contracting Officer.
>
> c\. Two hard copies the Variance Analysis Report Contract-level
> Summary (Exhibits 1&2 for Schedule A&B) shall be delivered. One copy
> shall be delivered to the BE/SEAT Contract Business Manager and the
> other copy shall be delivered to LF6/Cost Accounting.

**C. Task Order Status Report**

> The Task Order Status Report is a Functional Division/Office summary
> report of authorized task order resource information used for
> monitoring approved resources and costs and tracking task order
> approval status on a weekly basis
>
> 1\. The order Status Report entries shall include:
>
> a\. Task order number, subtask order number, and amendment identifier.
>
> b\. Task order title.
>
> c\. Contractor task order manager.
>
> d\. NASA technical monitor and organization code.
>
> e\. Authorized labor hours.
>
> f\. Authorized equivalent persons (EPs).
>
> g\. Authorized unburdened material dollars.
>
> h\. Authorized unburdened travel dollars.
>
> i\. Authorized total cost.
>
> j\. Approval date.
>
> k\. Indication of fiscal years approved.

NOTE: There should be a distinction made to identify between a task
order and subtask order.

> 2\. The Task Order Status Report shall be sorted by each Functional
> Division/Office supported by the contract. Within each Functional
> Division/Office sort, the report shall be sorted in ascending order of
> task number, subtask order number, and also sorted by the type: true
> completion form (TCF), completion form task orders (CFTs), followed by
> level-of-effort task orders (LOETs).
>
> 3\. A total calculation of authorized labor hours, EPs, material
> dollars, travel dollars, and total dollars shall be provided at the
> Functional Division/Office levels, at the Directorate level, and at
> the contract level with subtotals for the TCF, CFTs, and LOETs.
>
> 4\. Total number of approved task orders and subtask orders, by CFT
> and LOE, for each Functional Division/Office, Directorate, and total
> contact shall be included.
>
> 5\. Percentages of TCF, CFT\'s, and LOET\'s shall be computed and
> reflected on the report by authorized labor hours, authorized total
> cost, number of task orders, and number of subtask orders, for each
> Functional Division/Office, Directorate, and total contract.
>
> 6\. Reporting precision shall be to the \$1 for travel, material, and
> authorized costs and to the nearest 1/10 EP for EPs. All labor hours
> authorized shall be reported.
>
> 7\. Sufficient title, date, and other reference information to
> properly identify and utilize the Task Order Status Report shall be
> included.
>
> 8\. Distribution:
>
> a\. One complete file copy of the Task Order Status Report (TOSR)
> shall be electronically deposited into a secured electronic system
> namely the \"ETAC\" share area file under the NASA/JSC designated
> computer system on a weekly basis. Also, a monthly TOSR that coincides
> with the monthly NF 533 shall be deposited into a secured electronic
> system namely the \"ETAC\" share area on the same date as the NF 533
> is delivered.
>
> b\. One complete hard copy of the TOSR shall be delivered to the
> BE/Contracting Officer on a monthly basis concurrently with the NF533
> report on or before the due date.

**[REPORT DISTRIBUTION LIST]{.underline}**

**[Hardcopy or Electronically]{.underline}**

BE/Contracting Officer (1 Total Contract Level )

BE/Technical Administrator (1 Total Contract Level)

BE/Contract Business Manager (1 Total Contract Level)

BE/Engineering Business Management Office (1 Applicable Division Level
separated by Division)

BE/Engineering Alternate Technical Manager (1 Applicable Directorate
Level)

BL/Space and Life Sciences Directorate Business Management Office (1
Applicable Division Level separated by

Division)

EA4/Systems Engineering Office ( 1 Applicable Division Level)

EA5/Biomedical Hardware Development and Engineering Office TMR (1
Applicable Division Level)

EC/Crew and Thermal Systems TMR (1 Applicable Division Level)

EG/Aerosciences and Flight Mechanics TMR (1 Applicable Division Level)

EM/Manufacturing and Process Technology TMR (1 Applicable Division
Level)

EP/Propulsion and Power TMR (1 Applicable Division Level)

ER/Automation, Robotics, and Simulation TMR (1 Applicable Division
Level)

ES/Structures and Mechanics TMR (1 Applicable Division Level)

EV/Avionics Systems TMR (1 Applicable Division Level)

EX/Advanced Development Office ( 1 Applicable Division Level)

HA/Technology Transfer and Commercialization Business Manager (1
Applicable Division Level)

HA/Technology Transfer and Commercialization TMR (1 Applicable Division
Level)

LF6/Cost Accounting (1 Contract Summary and Each Schedule Summary level
separated)

MV3/Space Shuttle Vehicle Engineering Office (1 Applicable Division
Level)

OZ/Payload Planning and Resources Office TMR (1 Applicable Division
Level)

SD/Medical Sciences Division ( 1 Applicable Division Level)

SM/Science Payloads Management TMR (1 Applicable Division Level)

SN/Solar System Exploration TMR (1 Applicable Division Level)

SN5/Space and Life Sciences Alternate Technical Manager (1 Applicable
Directorate Level)

Names associated with positions identified on this listing shall be
updated and retained electronically on the \"ETAC\" share area under the
NASA/JSC designated computer system

<table>
<colgroup>
<col style="width: 18%" />
<col style="width: 6%" />
<col style="width: 7%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 8%" />
<col style="width: 7%" />
<col style="width: 8%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 8%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="13"><strong>SUMMARY LEVEL REPORT</strong></td>
</tr>
<tr class="even">
<td></td>
<td>1</td>
<td>2</td>
<td>3</td>
<td>4</td>
<td>5</td>
<td>6</td>
<td>7</td>
<td>8</td>
<td>9</td>
<td>10</td>
<td>11</td>
<td>12</td>
</tr>
<tr class="odd">
<td></td>
<td><p>Prior Mt</p>
<p>Actual</p></td>
<td><p>Prior Mth</p>
<p>Plan</p></td>
<td><p>Cum</p>
<p>Actual</p></td>
<td><p>Cum</p>
<p>Plan</p></td>
<td><p>Current Mth</p>
<p>Plan</p></td>
<td><p>Next Mth</p>
<p>Plan</p></td>
<td><p>Balance</p>
<p>of Contract</p></td>
<td><p>GFY</p>
<p>EAC</p></td>
<td><p>GFY</p>
<p>Auth</p></td>
<td><p>Total</p>
<p>Contract</p>
<p>EAC</p></td>
<td><p>Total</p>
<p>Contract</p>
<p>Value</p></td>
<td><p>Unfilled</p>
<p>Orders</p>
<p>Outstanding</p></td>
</tr>
<tr class="even">
<td><strong>Reporting Category</strong></td>
<td><strong>7a</strong></td>
<td><strong>7b</strong></td>
<td><strong>7c</strong></td>
<td><strong>7d</strong></td>
<td><strong>8a</strong></td>
<td><strong>8b</strong></td>
<td><strong>8c</strong></td>
<td></td>
<td></td>
<td><strong>9a</strong></td>
<td><strong>9b</strong></td>
<td><strong>10</strong></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>LM Base Hours</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>LM Overtime Hours</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><blockquote>
<p>Direct Labor Hours-LM</p>
</blockquote></td>
<td></td>
<td colspan="11">1. Actual cost for month being reported</td>
</tr>
<tr class="odd">
<td>Subcontractor Hours</td>
<td></td>
<td colspan="11">2. Contract Baseline plan for month being reported (not
sum of T.O. Baseline)</td>
</tr>
<tr class="even">
<td><blockquote>
<p>Total Hours</p>
</blockquote></td>
<td></td>
<td colspan="11">3. Contract to Date actual cost</td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="11"></td>
</tr>
<tr class="even">
<td>LM Base Labor</td>
<td></td>
<td colspan="11">4. Contract Baseline to Date (not sum of T.O.
Baseline)</td>
</tr>
<tr class="odd">
<td>LM Overtime</td>
<td></td>
<td colspan="11">5. Contractor Estimate for month following “7a”</td>
</tr>
<tr class="even">
<td><blockquote>
<p>Direct Labor Dollars-LM</p>
</blockquote></td>
<td></td>
<td colspan="11">6. Contractor Estimate for month following “8a”</td>
</tr>
<tr class="odd">
<td>Subcontractor Labor</td>
<td></td>
<td colspan="11">7. Contractor Estimate for all months beyond “8b”</td>
</tr>
<tr class="even">
<td>Overtime Premium</td>
<td></td>
<td colspan="11">8. GFY cum actual and remaining GFY estimate</td>
</tr>
<tr class="odd">
<td>Travel</td>
<td></td>
<td colspan="11">9. GFY Total Burdened Cost authorized on Task
Order</td>
</tr>
<tr class="even">
<td>Material</td>
<td></td>
<td colspan="11">10. 7c + 8a + 8b + 8c</td>
</tr>
<tr class="odd">
<td>Administrative Service Center</td>
<td></td>
<td colspan="11">11. Negotiated Contract Value</td>
</tr>
<tr class="even">
<td>Procurement Service Center</td>
<td></td>
<td colspan="11">12. Purchase Orders place but material not
received</td>
</tr>
<tr class="odd">
<td>Facility Service Center</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>CMS/HAO1</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Material Handling</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Other Direct</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Total: Direct Cost</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Overhead</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>G&amp;A</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Total: Indirect Cost</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Cost of Money</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Total: Cost</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Award Fee</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Incentive Fee</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Total: Cost Plus Fee</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Discount</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Total: Net Cost</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Options</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Total: Contract</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Cost Per EP</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>

533 Format:summary level

<table>
<colgroup>
<col style="width: 16%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 7%" />
<col style="width: 6%" />
<col style="width: 7%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 7%" />
<col style="width: 7%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="14"><strong>TASK ORDER LEVEL REPORT</strong></td>
</tr>
<tr class="even">
<td></td>
<td>1</td>
<td>2</td>
<td>3</td>
<td>4</td>
<td>5</td>
<td>6</td>
<td>7</td>
<td>8</td>
<td>9</td>
<td>10</td>
<td>11</td>
<td>12</td>
<td>13</td>
</tr>
<tr class="odd">
<td></td>
<td><p>Prior Mth</p>
<p>Actual</p></td>
<td><p>Prior Mth</p>
<p>Plan</p></td>
<td><p>Cum</p>
<p>Actual</p></td>
<td><p>Cum</p>
<p>Plan</p></td>
<td><p>GFY</p>
<p>Cum</p>
<p>Actual</p></td>
<td><p>Current Mth</p>
<p>Estimate</p></td>
<td><p>Next Mth</p>
<p>Estimate</p></td>
<td><p>Balance</p>
<p>of Task</p></td>
<td><p>Task</p>
<p>Order</p>
<p>EAC</p></td>
<td><p>Task</p>
<p>Order</p>
<p>Auth</p></td>
<td><p>GFY</p>
<p>EAC</p></td>
<td><p>GFY</p>
<p>TO</p>
<p>AUTH</p></td>
<td><p>Unfilled</p>
<p>Orders</p>
<p>Outstanding</p></td>
</tr>
<tr class="even">
<td><strong>Reporting Category</strong></td>
<td><strong>7a</strong></td>
<td><strong>7b</strong></td>
<td><strong>7c</strong></td>
<td><strong>7d</strong></td>
<td><strong>7e</strong></td>
<td><strong>8a</strong></td>
<td><strong>8b</strong></td>
<td><strong>8c</strong></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td><strong>10</strong></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Base Hours</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Overtime Hours</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><blockquote>
<p>Total Hours</p>
</blockquote></td>
<td></td>
<td colspan="12">1. Actual cost for month being reported</td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="12">2. Task Order Baseline Plan for month being
reported</td>
</tr>
<tr class="even">
<td>Total EPs</td>
<td></td>
<td colspan="12">3. Contract to Date actual cost</td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="12">4. Task Order Baseline Plan to Date</td>
</tr>
<tr class="even">
<td>Labor</td>
<td></td>
<td colspan="12">5. Cumulative Actual Cost for current fiscal year</td>
</tr>
<tr class="odd">
<td>Travel</td>
<td></td>
<td colspan="12">6. Contractor Estimate for month following “7a”</td>
</tr>
<tr class="even">
<td>Material</td>
<td></td>
<td colspan="12">7. Contractor Estimate for month following “8a”</td>
</tr>
<tr class="odd">
<td><blockquote>
<p>Total Direct Cost</p>
</blockquote></td>
<td></td>
<td colspan="12">8. Contractor Estimate for remaining period of
performance for Task Order – may be multiyear Task Order</td>
</tr>
<tr class="even">
<td>Total Burden Costs</td>
<td></td>
<td colspan="12">9. 7c + 8a + 8b + 8c</td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="12">10. Total Burdened Cost authorized on Task Order - may
be multiyear Task Order</td>
</tr>
<tr class="even">
<td>Total Cost</td>
<td></td>
<td colspan="12">11. “7e” + Contractor Estimate for fiscal year
remaining</td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="12">12. Total GFY Burdened Cost authorized for Task
Order</td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td colspan="12">13. Purchase Orders place but material not
received</td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>

533 Format:task order level

<table style="width:100%;">
<colgroup>
<col style="width: 19%" />
<col style="width: 8%" />
<col style="width: 9%" />
<col style="width: 8%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 9%" />
<col style="width: 8%" />
<col style="width: 9%" />
<col style="width: 5%" />
<col style="width: 9%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="11"><strong>SUB-TASK ORDER LEVEL REPORT</strong></td>
</tr>
<tr class="even">
<td></td>
<td>1</td>
<td>2</td>
<td>3</td>
<td>4</td>
<td>5</td>
<td>6</td>
<td>7</td>
<td>8</td>
<td>9</td>
<td>10</td>
</tr>
<tr class="odd">
<td></td>
<td><p>Prior Mth</p>
<p>Actual</p></td>
<td><p>Prior Mth</p>
<p>Plan</p></td>
<td><p>Cum</p>
<p>Actual</p></td>
<td><p>Cum</p>
<p>Plan</p></td>
<td><p>GFY</p>
<p>Cum</p>
<p>Actual</p></td>
<td><p>Current Mth</p>
<p>Estimate</p></td>
<td><p>Next Mth</p>
<p>Estimate</p></td>
<td><p>Balance</p>
<p>of Subtask</p></td>
<td>EAC</td>
<td><p>Unfilled</p>
<p>Orders</p>
<p>Outstanding</p></td>
</tr>
<tr class="even">
<td><strong>Reporting Category</strong></td>
<td><strong>7a</strong></td>
<td><strong>7b</strong></td>
<td><strong>7c</strong></td>
<td><strong>7d</strong></td>
<td><strong>7e</strong></td>
<td><strong>8a</strong></td>
<td><strong>8b</strong></td>
<td><strong>8c</strong></td>
<td></td>
<td><strong>10</strong></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Base Hours</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td>Overtime Hours</td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td><blockquote>
<p>Total Hours</p>
</blockquote></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="9" rowspan="12"><p>1. Actual cost for month being
reported</p>
<p>2. Subtask Baseline Plan for month being reported</p>
<p>3. Contract to Date actual cost</p>
<p>4. Subtask Baseline Plan to Date</p>
<p>5. Cumulative Actual Cost for current fiscal year</p>
<p>6. Contractor Estimate for month following “7a”</p>
<p>7. Contractor Estimate for month following “8a”</p>
<p>8. Contractor Estimate for remaining period of performance for
subtask</p>
<p>9. 7c + 8a + 8b + 8c</p>
<p>10. Purchase Orders place but material not received</p></td>
</tr>
<tr class="even">
<td>Total EPs</td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Labor</td>
<td></td>
</tr>
<tr class="odd">
<td>Travel</td>
<td></td>
</tr>
<tr class="even">
<td>Material</td>
<td></td>
</tr>
<tr class="odd">
<td><blockquote>
<p>Total Direct Cost</p>
</blockquote></td>
<td></td>
</tr>
<tr class="even">
<td>Total Burden Costs</td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
</tr>
<tr class="even">
<td>Total Cost</td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
</tr>
<tr class="even">
<td></td>
<td></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="9"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td colspan="9"></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="9"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td colspan="9"></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="9"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td colspan="9"></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="9"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td colspan="9"></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="9"></td>
</tr>
<tr class="even">
<td></td>
<td></td>
<td colspan="9"></td>
</tr>
</tbody>
</table>

533 Format:subtask level

  ----------- ------------------ -----------------------------------------------
  **SUBTASK                      
  AND TASK                       
  ORDER LEVEL                    
  REPORT**                       

                                 

              **Reporting        **Calculation**
              Category**         

                                 

  A           Base Hours         Includes prime and subcontractor hours

  B           Overtime Hours     Includes prime hours

              Total Hours        Summation

  C           Labor              Includes prime and subcontractor cost without
                                 LM burden -- Includes OT Premium

  D           Travel             Unburdened by LM burden

  E           Material           Unburdened by LM burden

  F           Total Direct Cost  C + D + E

  G           Total Burden Cost  Includes: OH, G & A, Svc Cnr, CMS, HA01,
                                 Relocation, COM, MHX, Award Fee, Incentive Fee

  H           Total Cost         F + G

                                 

                                 

              This assumes HA01  
              will not be        
              included as level  
              of effort          
  ----------- ------------------ -----------------------------------------------

533 Format:subtask level

<table>
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 10%" />
<col style="width: 1%" />
<col style="width: 7%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Quality Manual</strong></p></td>
<td colspan="3"><p>2. Current Version Date</p>
<p>29 Mar 96</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>22</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="10"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>The Quality Manual is used to document the details of the
contractor's Quality Management System (QMS) including management
commitment to quality, system elements, policy, and practice.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="2">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>x</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4"><p>6. References <em>(Optional)</em></p>
<p>See "Reference Documents" under item 8. below.</p></td>
<td colspan="6">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="10">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

[Scope]{.underline}:

The Quality Manual shall be in accordance with the requirements of
ANSI/ASQC Q9001-1994.

[Format]{.underline}:

Contractor format is acceptable.

[Contents]{.underline}:

Each element of the contractually imposed QMS requirements, including
supplements to ANSI/ASQC Q9001-1994 elements shall be addressed
sequentially in narrative form (supplements addressed separately is
acceptable), and in sufficient detail to describe the philosophy and
approach for implementation.

Existing policies and procedures may be utilized where contractual
requirements can be met. The manual shall include traceability from the
quality elements of ANSI/ASQC Q9001-1994 to the specific contractor
procedures which support those elements.

[Maintenance]{.underline}:

Update as required. All updates shall consist of notes or changes to the
Quality Manual, clearly identified as to where applicable (i.e., system
element, page/paragraph number, etc.)

<table>
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 2%" />
<col style="width: 8%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>Workmanship Specifications</strong></p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>3/31/97</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>23</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>To document workmanship specifications to ensure compliance with
applicable standards from the Statement of Work</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>x</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4">6. References <em>(Optional)</em></td>
<td colspan="7">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

The contractor shall submit a workmanship specifications to the ND/2
Chief, Process Certification Branch, for approval two weeks prior to
initiation of manufacturing of the Development, Verification, and Test
Units.

The workmanship specification shall be in accordance with NHB
5300.4(3A-2), NAS 5300.4(3G-1), NAS 5300.4(3H), NAS 5300.4(J-1), NAS
5300.4(3M), and JHB 5300.

The contractors internal workmanship specifications should be used where
possible. As a minimum, the Workmanship Specifications shall address:

a\. Soldering

b\. Crimping

c\. Wire Harnesses

d\. Connectors

e\. Printed Circuit Boards - layout and fabrication

f\. Electrostatic Discharge

g\. Conformal Coating

h\. Surface Mount Technology

i\. Staking

j\. Marking

k\. Cleaning

l\. Bonding

m\. Shipping

n\. Packaging

<table>
<colgroup>
<col style="width: 29%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 10%" />
<col style="width: 2%" />
<col style="width: 7%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p><strong>GFE Acceptance Data Package</strong></p></td>
<td colspan="3"><p>2. Current Version Date</p>
<p>29 Mar 97</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>24</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS9-19100</p></td>
</tr>
<tr class="even">
<td colspan="10"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>The ADP provides documentation required to verify as-built
configuration and degree of compliance with specification
requirements.</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="2">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>x</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4"><p>6. References <em>(Optional)</em></p>
<p>See "Reference Documents" under item 8. below.</p></td>
<td colspan="6">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="10">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

Reference Documents:

SSP 30695, \"Acceptance Data Package Requirements\"

SN-D-0007, \"Space Shuttle Program Acceptance Data Package
Requirements\"

SCOPE: The Acceptance Data Package (ADP) is an accumulation of
documentation that provides a verified and complete status of
deliverable hardware/software needed by the procuring/using organization
to ascertain \"as-built\" configuration and to continue applicable data
maintenance. An ADP shall be submitted with shipment/transfer of each
hardware/software end item.

FORMAT: The ADP shall be divided into separate sections with each
containing specific data. Each ADP will be assembled per SSP 30695\*.

CONTENTS: The ADP, consisting of the applicable data items, shall be
accumulated by the contractor/supplier during the
fabrication/development and testing of each deliverable end item. The
ADP shall reflect the status of the hardware/software at the time of
acceptance and shall be delivered concurrently with the
hardware/software end item. Data items and elements are listed in SSP
30695\*.

The number of sections to be contained in a specific ADP shall be
determined by the number of applicable data items required for the
subject hardware/software being delivered (i.e., one or more data items
may not be applicable to the item being delivered; in that event, only
those sections which are applicable would be included in the ADP with
the proper notation on the Index Page.).

MAINTENANCE: Updated as required.

\* SN-D-0007 is an acceptable alternative for hardware items.

<table>
<colgroup>
<col style="width: 30%" />
<col style="width: 2%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 7%" />
<col style="width: 10%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 28%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><p>1. DRD Title</p>
<p>Waiver/Deviation Request</p></td>
<td colspan="4"><p>2. Current Version Date</p>
<p>1/27/97</p></td>
<td colspan="3"><p>3. DRL Line Item No.</p>
<p>25</p></td>
<td><p>RFP/Contract No. (Procurement completes)</p>
<p>NAS 9-19100</p></td>
</tr>
<tr class="even">
<td colspan="11"><p>4. Use (Define need for, intended use of, and/or
anticipated results of data)</p>
<p>To document workmanship specifications to ensure compliance with
applicable standards from the Statement of Work</p></td>
</tr>
<tr class="odd">
<td>5. DRD Category: <em>(check one)</em></td>
<td></td>
<td colspan="3">Technical</td>
<td></td>
<td colspan="2">Administrative</td>
<td>x</td>
<td colspan="2">SR&amp;QA</td>
</tr>
<tr class="even">
<td colspan="4">6. References <em>(Optional)</em></td>
<td colspan="7">7. Interrelationships <em>(e.g., with other DRDs)
(Optional)</em></td>
</tr>
<tr class="odd">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

Waiver/Deviation requests shall be prepared and submitted to NASA/JSC
for review and acceptance of nonconformances. A waiver is requested to
authorize use or acceptance of hardware which does not meet specified
requirements. A waiver is requested after the fact. A deviation is
requested to authorize departure from particular requirements of
specifications or related documents. Affected processing, testing,
acceptance, or shipment of applicable hardware shall not proceed until
notification of approval of the waiver/deviation.

Each waiver/deviation request shall contain the following as a minimum:

> a\. Identification of the request as a waiver or a deviation.
>
> b\. Equipment name, part number, applicable serial numbers, function,
> criticality, and effectivity.
>
> c\. Identification of the requirement to be waived or deviated from.
>
> d\. If applicable the name, part number, serial number, and function
> of affected components.
>
> e\. Salient differences between design baseline and the requested
> configuration.
>
> f\. Technical justification, including impact, supporting approval of
> the request.
>
> g\. The contractor\'s reliability evaluation of the request.