AppendiX 2: Data REQUIREMENTS Description Sheets

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** 2.1.1-a **ISSUE:** Initial 2. **DRL LINE ITEM NO.:**

3\. **DATA TYPE:** 1 4. **DATE REVISED**:

5\. **PAGE:** 1/1

6\. **TITLE:** Integrated Management Plan

7\. **DESCRIPTION/USE**: To describe the contractor\'s integrated
management approach, organization, and systems.

8\. **[DISTRIBUTION:]{.smallcaps}** Formatting and electronic
distribution per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Draft with proposal; final version 60 days
after the end of the phase-in period.

10\. **SUBMISSION FREQUENCY:** Updates as required.

11\. **REMARKS:**

12\. **INTERRELATIONSHIP:** SOW 2.1.1

13\. **DATA PREPARATION INFORMATION:**

13.1 **[SCOPE]{.underline}:** The Integrated Management Plan shall
describe the basis for the contractor management approach, organization,
and systems for accomplishing and managing all services and functions
described in the SOW. It shall provide a comprehensive integration of
all management systems of the prime, subcontractors, and major vendors,
including Small and Small Disadvantaged business goals. The systems will
include those specifically required to accomplish the Statement of Work,
as well as those systems and procedures that are to be set in place by
the contractor.

13.2 **[APPLICABLE DOCUMENTS]{.underline}:**

13.3 **[CONTENTS]{.underline}:** The Integrated Management Plan shall
address the contractor\'s plans for work definition and authorization,
schedules and scheduling, budgeting, data accumulation, safety and
mission assurance, corrective action, subcontract/material control,
indirect cost management, baseline control, and organization structure
identifying key personnel, information management. The plan should
address the approach for utilizing commercial-off-the-shelf products and
tools where appropriate.

13.4 **[FORMAT:]{.underline}** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** 2.1.1-b **ISSUE:** Initial 2. **DRL LINE ITEM NO.:**

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE:** 1/1

6\. **TITLE**: Contract Work Breakdown Structure (CWBS) and Dictionary

7\. **DESCRIPTION/USE**: To organize the tasks to be accomplished in
this contract in a service oriented structure. The CWBS and dictionary
shall provide the framework for structuring the program implementation
plans, establishing and tracking budgets, preparing schedules,
developing work force and material estimates, preparing work
authorization documents, and reporting contract performance.

8\. **[DISTRIBUTION:]{.smallcaps}** Formatting and electronic
distribution per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Draft with proposal; final version at end of
contract phase-in.

10\. **SUBMISSION FREQUENCY**: Updates as required.

11\. **REMARKS:**

12\. **INTERRELATIONSHIP**: SOW 2.1.1 and 2.1.4

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: The CWBS shall encompass all the services
required to achieve all the requirements of this contract. The CWBS
shall subdivide the work to be accomplished into elements that serve as
the basis for detailed planning and control, and in addition, permit
collection of cost and schedule data for each element.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[CONTENTS]{.underline}**: The CWBS shall graphically depict the
CWBS tree. The dictionary contains a concise description of contract
tasks to be performed and products to be delivered, subdivided by CWBS
element. A CWBS element may represent an identifiable product, a set of
data, a service, a task, or a budget function. The structure shall be at
least at one level of detail lower than that specified in the RFP SOW
with additional levels as required by the contractor. Lower levels of
detail, which the contractor uses for its own management purposes to
validate information reported to NASA, shall be compatible with NASA
requirements and be accessible by NASA. The relationship between the
CWBS and the contractor\'s internal organizations and processes should
also be provided.

13.4 **[FORMAT:]{.underline}** The CWBS tree is to be in organization
chart format and the associated CWBS narrative (CWBS Dictionary) in text
form and arranged as stated in 13.3 of this DRD. The CWBS tree and
dictionary shall be provided in both electronic and hard copy form. See
Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: The CWBS and CWBS Dictionary shall
be updated to reflect contract changes as they affect the CWBS coverage.
Revisions shall be incorporated by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO**.: 2.1.1-c **ISSUE:** Initial 2. **DRL LINE ITEM NO**.:

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Consolidated Space Operations Contract Transition Plan

7\. **DESCRIPTION/USE**: To provide an approach and rationale for
transition of Space Operations activities to the CSOC.

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Draft with proposal; final version at end of
contract phase-in.

10\. **SUBMISSION FREQUENCY**: Updates as required.

11\. **REMARKS:**

12\. **INTERRELATIONSHIP**: SOW 2.1.1, 2.1.2

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: The CSOC Transition Plan provides plans
for the transfer of all anticipated operations activities to the CSOC
along with supporting logic and rationale.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[CONTENTS]{.underline}**: The Transition plan shall describe the
overall plan for transition. As a minimum, it shall address:

a.  Schedule with key milestones

b.  Approach and rationale for implementing the plans, procedures, and
    processes required for performance of the contract, including
    property, personnel, facilities, and security

c.  Metrics used to determine progress for contract transition

d.  Property control transfer

e.  Facilities responsibility transfer

f.  Mission assurance considerations

g.  Security considerations

h.  Classified document control transfer

i.  Risk mitigation strategy

j.  Configuration management considerations

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO**.: 2.1.1-d **ISSUE:** 1 2. **DRL LINE ITEM NO**.:

3\. **DATA TYPE**: 1 4. **DATE REVISED**: 10-11-00

5\. **PAGE**: 1/2

6\. **[TITLE]{.smallcaps}**: Firm Fixed Price
(FFP)/Fixed-Price-Incentive (FPI) Proposal.

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide the Government a
proposal to convert all or part of the contract to FFP/FPI.

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Per page 2 of the DRD

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: N/A.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.1.1

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The proposal shall identify the portions
of the SOW that can reasonably be converted to FFP/FPI, with rationale
for those portions. For those portions, a full price proposal shall be
submitted with supporting data. Any impacts to the technical performance
of the contract shall be addressed as well as impacts to the terms and
conditions of the contract.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: To be mutually identified
by the SOMO/CSOC Restructure Team prior to submittal.

13.4 **[[FORMAT:]{.underline}]{.smallcaps}** Contractor required format
is acceptable. See Contracting Officer's letter BN-02-062 dated June 14,
2002.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** 2.1.1-e **ISSUE:** Initial 2. **DRL LINE ITEM NO.:**

3\. **DATA TYPE:** Plan = 1 4. **DATE REVISED**:

Report = 2 5. **PAGE:** 1/1

6\. **TITLE:** Small, Small-Disadvantaged, and Small Woman-Owned
Business Subcontracting Plan and Reports

7\. **DESCRIPTION/USE**: To describe the contractor\'s planned approach
to Small, Small-Disadvantaged, and Small Woman-Owned Business
Subcontracting and their reporting against this plan.

8\. **[DISTRIBUTION:]{.smallcaps}** Formatting and electronic
distribution per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Draft plan with proposal; final version 60
days after the end of phase-in..

10\. **SUBMISSION FREQUENCY:** Report is quarterly.

11\. **REMARKS:**

12\. **INTERRELATIONSHIP:** N/A

13\. **DATA PREPARATION INFORMATION:**

13.1 **[SCOPE]{.underline}:** The Small, Small-Disadvantaged, and Small
Woman-Owned Business Subcontracting Plan shall separately address
subcontracting with small business concerns, small disadvantaged
business concerns, and small woman-owned business concerns with a
separate part for the basic contract and separate parts for the 5-year
option. The reporting shall be against the goals depicted in this plan.

13.2 **[APPLICABLE DOCUMENTS]{.underline}:** FAR 52.219.8 and 52.219.9
and NASA FAR Supplement (NFS) 1952.219-75, 1952.219-76 and 1952.219-79.

13.3 **[CONTENTS]{.underline}:** The Small, Small-Disadvantaged, and
Small Woman-Owned Business Subcontracting Plan shall be in compliance
with FAR 52.219.9. The Small Business, Small Disadvantaged Business, and
Small Woman-Owned Business Subcontracting Reporting shall be in
compliance with NFS 1952.219-75.

13.4 **[FORMAT:]{.underline}** Contractor format is acceptable for the
plan the; reporting shall be in compliance with NFS 1952.219-75. See
Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: N/A.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO**.: 2.1.2 **ISSUE:** Initial 2. **DRL LINE ITEM NO**.:

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/4

6\. **[TITLE]{.smallcaps}**: Reports/Reviews

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide information necessary
for NASA's insight function.

8\. **[DISTRIBUTION:]{.smallcaps}** Formatting and electronic
distribution per Contracting Officer's letter.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: 1) Reports, at the end of the
first reporting period after contract award; 2) Documentation, as
specified below; 3) Reviews/meetings as specified below.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: As described in item \#
13.6.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.1.2

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: This DRD establishes the activity
reporting for the Contractor's progress and accomplishments as well as
performance and utilization of facilities/systems.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The report shall include
quantitative descriptions of overall technical and administrative
progress, and status, of significant activities relating to the
accomplishments of the contractual objectives. Risks to the
accomplishment of contractual objectives shall also be identified. The
report shall also include performance and utilization data for major
facilities and systems. Activity Report items covered shall included
significant accomplishments, problems encountered, quality assurance
results, corrective actions. Metrics Report items shall be in accordance
with DRD 2.1.4. All reports shall be of sufficient depth and clarity to
permit understanding and evaluation of progress made. Supporting data in
the form of charts, graphs, etc. may be included as appropriate.

Documentation - To be determined by mutual agreement with the COTR and
TMR.

Reviews/Meetings - To be determined by mutual agreement with the COTR
and TMR.

13.4 **[[FORMAT:]{.underline}]{.smallcaps}** The content and format will
be determined by mutual agreement with the COTR and TMR. See Contracting
Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

DRD 2.1.2 Page 2/4

**DRD Continuation Page**

13.6 **[FREQUENCY OF SUBMISSION]{.underline}**:

DRD 2.1.2 Reports/Reviews

  ---- ----------------------------- ---------------- ----------------------
       TITLE                         FREQUENCY        COMMENTS

       [Reports]{.underline}                          

  1    Activity Report               Weekly           

  2    Facility Status               Weekly           

  3    Progress Report               Monthly          

  4    DSN Significant Events        Weekly           JPL-specific

  5    Availability Report           Monthly          

  6    Metrics Report                Monthly          

  7    Status of DRDs                Monthly          

  8    AMMOS Significant Events      Weekly           JPL -specific

  9    STDN Significant Events       Weekly           GSFC -specific

  10   WFF Significant Events        Weekly           GSFC -specific

  11   STDN Daily Report             Daily            GSFC -specific

  12   WFF Daily Report              Daily            GSFC -specific

                                                      

       [Documentation]{.underline}                    

  13   Launch Window Analysis        As necessary     GSFC -specific

  14   Coverage Analysis             As necessary     GSFC -specific

  15   Mission Requirements Request  L-1 year         GSFC -specific

  16   Detailed Mission Requirements L-6 months       GSFC -specific

  17   Mission Operations Support    L-3 months       GSFC -specific
       Plan                                           

  18   Network Operations Support    L-1 month        GSFC -specific
       Plan                                           

  19   Interface Control Documents   As necessary     GSFC -specific
  ---- ----------------------------- ---------------- ----------------------

DRD 2.1.2 Page 3/4

**DRD Continuation Page**

  ---- -------------------------------- ---------------- ----------------------
       TITLE                            FREQUENCY        COMMENTS

                                                         

       [Reviews/Meetings]{.underline}                    

  20   Project Status Reviews           Monthly          

  21   SOMO Program Management Review   Monthly          Presentation is to be
                                                         electronically
                                                         distributed to all
                                                         centers and JPL.

  22   Flight Programs Review           Quarterly        JPL -specific;
                                                         presentation is
                                                         electronically dist.

  23   SLA status                       Quarterly        

  24   SLA Progress Meetings            Monthly          
  ---- -------------------------------- ---------------- ----------------------

NOTES:

  ----------- -----------------------------------------------------------
  NUMBER      TITLE & DESCRIPTION

  1           Activity Report - This report should include high level run
              reports for simulations, tests, etc., as well as
              significant facility problems or mishaps.

  4           DSN Significant Events Report - This report is to describe
              significant events that occur in the DSN. The events can be
              both positive and negative. This report is to cover all
              operational elements of the DSN, including the overseas
              tracking stations located in Canberra, Australia; and
              Madrid, Spain.

  8           AMMOS Significant Events Report - This is to describe
              significant events that occur in the AMMOS. The events can
              be both positive and negative.

  21          Program Management Review - This monthly review documents
              accomplishments; changes in plans; problems being worked
              and proposed solutions consistent with the requirements of
              DRD 2.1.4. The discussion of plans, progress and problems
              shall include variance analysis and reporting of cause,
              impact, and corrective action. Technical issues shall be
              covered in terms of performance goals (metrics), exit
              criteria, schedule progress, and/or cost impact. The review
              shall include current status, year-end estimate, and cover
              upcoming major events.

  22          Flight Programs Review - This quarterly status report for
              the Enterprise sponsor documents past three months
              performance and next three months' plans

  9           STDN Significant Event Report - This report is to describe
              significant events that occur in the STDN. The events can
              be both positive and negative. This report is to cover all
              operational elements of the STDN, including the tracking
              stations located in Bermuda, UK; Merritt Island/Ponce de
              Leon, FL; and WSC, New Mexico.

  10          WFF Significant Event Report - This report is to describe
              significant events that occur in the WFF (i.e., AWOTS, MGS,
              PFOTS, and other mobile orbital tracking assets). The
              events can be both positive and negative. This report is to
              cover all operational elements of the WFF.

  11          STDN Daily Report - This report is to describe the
              customers and time supported, support anomalies, equipment
              status, and upcoming events (e.g., tests, ECs, training)
              for the STDN on a daily basis.

  12          WFF Daily Report - This report is to describe the customers
              and time supported, support anomalies, equipment status,
              and upcoming events (e.g., tests, ECs, training) for WFF
              assets on a daily basis.
  ----------- -----------------------------------------------------------

DRD 2.1.2 Page 4/4

**DRD Continuation Page**

  ----------- -----------------------------------------------------------
  13          Launch Window Analysis - - This report is in conjunction
              with launch vehicle contractor and mission support. The
              analysis determines available orbital injection conditions
              and launch times based upon mission constraints. Data is
              generated for numerous launch vehicle injection conditions.
              Contingency analysis is provided to correct any and all
              launch vehicle contingencies and off-nominal conditions of
              the propulsion systems onboard once separation occurs.

  14          Coverage Analysis - This report is to describe the tracking
              station coverage analysis, including coverage by the TDRSS.
              Various levels of support can be provided, from accurate
              studies using station and ground masks from the FDD station
              geodetics data base to quick estimates using user-defined
              elevation station masks.

  15          Mission Requirements Request - This is a parent document
              generated by a customer organization describing in general
              terms the overall mission requirements.

  16          Detailed Mission Requirements - This is a corresponding
              document to the Mission Requirements Request document
              elaborating each customer requirement to the next level of
              detail.

  17          Mission Operations Support Plan - This document describes
              the approach to meeting the mission operations and data
              processing requirements outlined in the Detailed Mission
              Requirements.

  18          Network Operations Support Plan - This document describes
              the approach to meeting the tracking and data acquisition
              requirements outlined in the Detailed Mission Requirements.
  ----------- -----------------------------------------------------------

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO**.: 2.1.2.1 **ISSUE:** Initial 2. **DRL Line Item No.:**

3\. **DATA TYPE**: 3 4. **DATE REVISED:**

5\. **PAGE:** 1/5

6\. **TITLE:** Wage/Salary and Fringe Benefit Data

7\. **DESCRIPTION/USE:** The Wage/Salary and Fringe Benefit Data will be
used by the NASA Contracting Officer and the Industrial Labor Relations
Office to provide the necessary data for submittal of Standard Form (SF)
98, Notice of Intention to Make a Service Contract and Response to
Notice, to the Department of Labor, and to assist in the monitoring of
Service Contract Act compliance.

8\. **DISTRIBUTION:** Per Contracting Officer's letter.

9\. **INITIAL SUBMISSION:** Start date of contract, at end of phase-in.

10\. **SUBMISSION FREQUENCY:** Annually based on the start date of
contract.

11\. **REMARKS:**

13\. **INTERRELATIONSHIP:** FAR 52.222-41

13 **DATA PREPARATION INFORMATION:**

13.1 **[SCOPE:]{.underline}** The Wage/Salary and Fringe Benefit Data
must be submitted by the contractor, and any subcontractors which are
subject to the provisions of the Service Contract Act, to the
Contracting Federal Agency. In accordance with FAR regulations 22.1007
and 22.1008, the Contracting Officer is required to submit a SF 98 to
the Department of Labor, Wage and Hour Division.

13.2 **[APPLICABLE DOCUMENTS:]{.underline}** None

13.3 **CONTENTS:** The Wage/Salary and Fringe Benefit Data should
contain the data included in the enclosed DRD forms, titled "Wage/Salary
Rate Information", "Fringe Benefit for Service Employees", and Fringe
Benefits per Collective Bargaining Agreement". The Wage/Salary Rate
Information shall contain a listing of all exempt and nonexempt labor
classifications working on the contract. Separate forms should be
utilized for classifications working in different geographic areas and
for each subcontractor. Wage determination numbers, appropriate labor
organization names, and subcontractor names, must be reflected. All
nonexempt labor classifications must be matched to wage determination
classes or to CBA classifications for represented classes. Annotate
exempt or nonexempt and union or nonunion. The current hourly rates
should reflect the actual lowest and highest paid employees, along with
a computed average rate. State the number of employees working in each
labor category. Separate Fringe Benefit forms should be completed for
nonrepresented classifications and for each separate CBA. A separate
form must be completed for the prime and each subcontractor. Three
copies of each Collective Bargaining Agreements are required.

13.4 **FORMAT:** The Wage/Salary and Fringe Benefit Data should be in a
format substantially the same as enclosed with this DRD. (Forms 2, 3,
and 3A) See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **MAINTENANCE:** Changes shall be incorporated as required by
change page or complete reissue.

DRD 2.1.2.1 Page 2/5

**DRD Continuation Page**

+---------------+---------------+--------+-------+-----------+--------+
| FORM 2        |               |        |       |           |        |
|               |               |        |       |           |        |
| WORK SHEET    |               |        |       |           |        |
| FOR SF-98     |               |        |       |           |        |
| DATA          |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
| WAGE RATE     |               |        |       |           |        |
| INFORMATION   |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
| CONTRACTORS   | WAGE          | EXEMPT | UNION | CURRENT   | MYE NO |
| LABOR         | DETERMINATION | OF     | OR    | HOURLY    | OF     |
+---------------+---------------+--------+-------+-----------+--------+
| [C            | [C            | [NONE  | [N    | [RATE]{.u | [EMPL  |
| LASSIFICATION | LASSIFICATION | XEMPT] | ONUNI | nderline} | OYEES] |
| ]{.underline} | ]{.underline} | {.unde | ON]{. |           | {.unde |
|               |               | rline} | under |           | rline} |
|               |               |        | line} |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
| Illustration  |               |        |       |           |        |
| of required   |               |        |       |           |        |
| data:         |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
| Project       | Not Required  | E      | N     | \$25.00   | 1      |
| Manager       |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
| Supervisor    | Not Required  | E      | N     | \$20.00   | 1      |
+---------------+---------------+--------+-------+-----------+--------+
| Electrical    | Not Required  | E      | N     | \$16.50 - | 3      |
| Engineer      |               |        |       | \$20.00   |        |
+---------------+---------------+--------+-------+-----------+--------+
| Technician,   | Elect Tech    | N      | U     | \$12.78 - | 12     |
| Jr            | Main 1        |        |       | \$15.50   |        |
+---------------+---------------+--------+-------+-----------+--------+
| Technician,   | Elect Tech    | N      | U     | \$18.20 - | 4      |
| Sr            | Main II       |        |       | \$20.00   |        |
+---------------+---------------+--------+-------+-----------+--------+
| Secretary     | Secretary I   | N      | N     | \$11.11 - | 2      |
|               |               |        |       | \$12.50   |        |
+---------------+---------------+--------+-------+-----------+--------+
| File Clerk    | General Clerk | N      | N     | \$8.29    | 1      |
|               | II            |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
| Clerical Data | Word          | N      | N     | \$9.25 -  | 3      |
| Entry         | Processor I   |        |       | \$10.90   |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
| Submit data   |               |        |       |           |        |
| in the above  |               |        |       |           |        |
| illustrated   |               |        |       |           |        |
| format for    |               |        |       |           |        |
| all labor     |               |        |       |           |        |
| cl            |               |        |       |           |        |
| assifications |               |        |       |           |        |
| used, or      |               |        |       |           |        |
| planned to be |               |        |       |           |        |
| used, on this |               |        |       |           |        |
| contract.     |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
| All           |               |        |       |           |        |
| contractor    |               |        |       |           |        |
| labor         |               |        |       |           |        |
| cl            |               |        |       |           |        |
| assifications |               |        |       |           |        |
| must be       |               |        |       |           |        |
| matched to    |               |        |       |           |        |
| wage          |               |        |       |           |        |
| determination |               |        |       |           |        |
| classes       |               |        |       |           |        |
| listed in     |               |        |       |           |        |
| CBA\'s        |               |        |       |           |        |
| represented   |               |        |       |           |        |
| classes       |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
| or classes    |               |        |       |           |        |
| shown in WD   |               |        |       |           |        |
| 94-2516 for   |               |        |       |           |        |
| n             |               |        |       |           |        |
| onrepresented |               |        |       |           |        |
| classes.      |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
| CONTRACTORS   | WAGE          | EXEMPT | UNION | CURRENT   | MYE NO |
| LABOR         | DETERMINATION | OF     | OR    | HOURLY    | OF     |
+---------------+---------------+--------+-------+-----------+--------+
| [C            | [C            | [NONE  | [N    | [RATE]{.u | [EMPL  |
| LASSIFICATION | LASSIFICATION | XEMPT] | ONUNI | nderline} | OYEES] |
| ]{.underline} | ]{.underline} | {.unde | ON]{. |           | {.unde |
|               |               | rline} | under |           | rline} |
|               |               |        | line} |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+
|               |               |        |       |           |        |
+---------------+---------------+--------+-------+-----------+--------+

DRD 2.1.2.1 Page 3/5

**DRD Continuation Page**

FORM 3

Page 1 of 2

FRINGE BENEFITS PER COLLECTIVE BARGAINING AGREEMENT

For period from \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ to
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Contractor:

Contract Number:

Number of employees in bargaining unit
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Total number of employees on contract
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

1\. Shift Differential: (Describe any pay over and above base rates for
2nd, 3rd, weekend, or other shifts.)

2\. Health and Welfare Items and Other Fringe Items: (Indicate whether
or not coverage is provided to employees and state current average
hourly cost per employee covered by a Collective Bargaining Agreement.)

**Coverage Average**

**Item Provided Hourly Cost**

**(Yes or No)**

a\. Life Insurance

b\. Accidental Death

c\. Disability

d\. Medical and Hospital

e\. Dental

f\. Retirement Plan

g\. Savings/Thrift Plan

h\. Sick Leave

i\. Tuition

j\. Other (Describe)

TOTAL

DRD 2.1.2.1 Page 4/5

**DRD Continuation Page**

FORM 3

Page 2 of 2

3\. Paid Absences:

Service Requirement Days per Year

a\. Vacation

b\. Holiday

c\. Sick Leave

d\. Jury Leave

e\. Funeral Leave

f\. Military Leave

g\. Other (Describe)

4\. Severence Pay: (Briefly describe terms and amounts.)

5\. Other Fringe Benefits: (Describe any other fringe benefits not
included above, and show average hourly cost.)

6\. Premium Pay: (Discuss all premium pay provisions not previously
shown on this form.)

­­­­­­­­­­­\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_

Signature of Company Representative Date

DRD 2.1.2.1 Page 5/5

**DRD Continuation Page**

FORM 3A

Page 1 of 1

FRINGE BENEFITS FOR SERVICE EMPLOYEES

For Period from \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_ to
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Contractor:

Number of nonexempt employees on contract:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Total number of employees on contract:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

1\. Health and Welfare Items and Other Fringe Items:

(Indicate whether or not coverage is provided to employees and state
current average hourly cost per service employee.)

**[Item]{.underline} Coverage Average**

**[Provided]{.underline} [Hourly Cost]{.underline}**

a\. Life Insurance

b\. Accidental Death

c\. Disability

d\. Medical & Hospital

e\. Dental

f\. Retirement Plan

g\. Savings/Thrift Plan

h\. Sick Leave

i\. Tuition Reimbursement

j\. Other (Describe)

2\. Paid Absences

**[Service Requirement]{.underline} [Days per Year]{.underline}**

a\. Vacation

b\. Holidays

c\. Sick Leave

d\. Jury Leave

e\. Funeral Leave

f\. Military Leave

g\. Other (Describe)

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Signature of Company Representative Date

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD No**.: 2.1.3 **ISSUE:** Initial 2. **DRL LINE ITEM No**.:

3\. **DATA TYPE**: Initial Baseline Reports: 1 4. **DATE REVISED**:

NASA Forms 533M/Q: 2

5\. **PAGE**: 1/4

6\. **TITLE**: Financial Management Reports

7\. **DESCRIPTION/USE**: To provide financial management reports for
planning, monitoring, and controlling project resources; accounting for
the contract\'s accumulated expenditures and other liabilities;
evaluating contractor cost performance; and projecting/forecasting cost
and work force resource requirements which realistically support the
schedule requirements.

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter.

9\. **INITIAL SUBMISSION**:

NASA Form 533Q - Within 30 days after authorization to proceed.

NASA Form 533M - No later than 30 days after the incurrence of cost.

Initial Baseline Reports - An initial NF533 report is required in the
NF533Q format to be used as a baseline for the life of the contract. The
initial (baseline) NF533Q shall be submitted by the contractor within 30
days after authorization to proceed has been granted. The initial report
shall reflect the original contract value detailed by negotiated
reporting categories and shall be the original contract baseline plan.

10\. **SUBMISSION FREQUENCY**:

> 533M - Monthly, no later than the 10th operating day following the
> close of the contractor's accounting period.
>
> 533Q - Quarterly, no later than the 15th day of the calendar month
> preceding the quarter being reported.
>
> The due dates reflect the date the NF533 reports are received by
> personnel on the distribution list

11. **REMARKS**: The NASA Form 533 (NF533) reports provide data
    necessary for the following:

1\. Projecting costs and hours to ensure that dollar and labor resources
realistically support project and program schedules.

2\. Evaluating contractors\' actual cost and fee data in relation to
negotiated contract value, estimated costs, and budget forecast data

3\. Planning, monitoring, and controlling project and program resources.

4\. Accruing cost in NASA\'s accounting system, providing program and
functional management information, and resulting in liabilities
reflected on the financial statements.

Cost is a financial measurement of resources used in accomplishing a
specified purpose, such as performing a service, carrying out an
activity, acquiring an asset, or completing a unit of work or project.
NASA Contractor Financial Management Reporting, NASA Procedures and
Guidelines (NPG) 9501.2C, or its most current revision, identifies the
cost reporting requirements for a contract.

NASA is required by law to maintain accrual accounting, which requires
cost to be reported in the period in which benefits are received,
without regard to time of payment.

DRD 2.1.3 Page 2/4

**DRD Continuation Page**

Examples of accrual accounting for common cost elements reported on the
NF533 follow:

**[Cost Element]{.underline}**

*Labor* Reported to NASA as hours are incurred.

*Equipment & Materials* Generally reported to NASA when received and
accepted by the

*(commercial off the shelf)* contractor.

> *Manufactured Equipment* Defined as any equipment that is produced to
> specific requirements that make it useless to anyone else without
> rework. Cost should be reported to NASA as the equipment is being
> manufactured. The straight-line method for estimating accrued costs or
> the use of supplemental information obtained from the vendor are
> acceptable methods used to calculate the cost accrual amount.

*Leases* Reported to NASA using a proration over the life of the lease.

*Travel* Reported to NASA as costs are incurred.

> *Subcontracts* Actual and estimated costs reported by prime
> contractors shall include subcontractors\' incurred costs for the same
> accounting period. Where subcontract costs are material, they should
> be separately identified on NF533 reports. The prime contractor shall
> include in the total cost of each subdivision of work the accrued cost
> (including fee, if any) of related subcontractor effort.
> Subcontractors should, therefore, be required to report cost to the
> prime contractor, using the accrual method of accounting. If the G&A
> and fee reported by a subcontractor are at the total subcontractor
> level, these costs must be allocated to specific sub-divisions of
> work. Data submitted by the subcontractor should be structured similar
> to the prime contractor\'s NF533 to enable the prime contractor to
> properly report to NASA. For Firm Fixed Price subcontracts with a
> contract value greater than \$500,000, the prime contractor is
> required to document the methodology used to generate the
> sub-contractor costs reported and provide this information to the
> Contracting Officer and Center Deputy Chief Financial Officer
> (Finance).
>
> *Unfilled Orders* Reported as the difference between the cumulative
> cost incurred to date and amounts obligated to suppliers and
> subcontractors.

DRD 2.1.3 Page 3/4

**DRD Continuation Page**

> *Fee* Should be accrued as earned using a consistent and auditable
> method to determine the amount. For example: an acceptable method
> would be to use historical data to determine the amount to accrue each
> month. Fee should be reported on the NF533 following the \"Total
> Cost\" line. Award fee must be reported by the following categories:
> Base Fee, Fee Earned, Interim Fee, Provisional Fee, Potential
> Additional Fee, and Total Fee. If any of the above fee categories do
> not pertain, they should not be included in the NF533.
>
> *Prompt Payment Discounts* Cumulative cost reported to NASA should be
> the full incurred cost. The prompt payment discount amount taken
> should be reported as a separate line item on the NF533 below the
> cumulative cost amounts for the contract.
>
> The NF533 reports are the official cost documents used at NASA for
> cost type, price redetermination, and fixed price incentive contracts.
> The data contained in the reports must be auditable using Generally
> Accepted Accounting Principles. Supplemental cost reports submitted in
> addition to the NF533 must be reconcilable to the NF533.
>
> Uncompensated overtime hours worked should be reported on NF533
> reports as a separate line item or in the footnotes.
>
> For contracts which have multiple schedules, a summary NF533 is
> required to provide a cumulative from inception cost for the contract,
> regardless of schedule.
>
> Column 7b (planned cost incurred/hours worked for the month) and 7d
> (cumulative planned cost incurred/hours worked) of the NF533M
> represent the negotiated baseline plan for the contract. There may not
> be a relationship between the estimates provided in columns 8 of the
> NF533M to columns 7b and 7d. Columns7b and 7d represent the legally
> binding contract negotiated baseline plan plus all authorized changes.
>
> Short and long-term cost estimates, which include all data entered in
> columns 8 and 9a on the NF533M and NF533Q reports, shall be based on
> the most current and reliable information available.
>
> Prior period cost adjustments should be reported in column 7a and 7c
> of NF533M and column 7a of the NF533Q with a footnote discussing the
> reasons for and amounts of the adjustments.
>
> Monthly NF533 reporting is no longer required once the contract is
> physically complete, provided the final cost report includes actual
> cost only (no estimates or forecasts). The contractor must continue to
> submit monthly NF533 reports as long as estimates for the following
> period are included. If the final cost of a contract changes after the
> submission of the \"final\" contractor cost report, the contractor
> must submit a revised NF533 report in the month the cost change is
> recognized

12\. I**NTERRELATIONSHIP**: SOW 2.1.3, Clauses 1852.242-73.

All data shall be reconcilable between the NASA Forms 533M, 533Q, and
the Performance Measurement System (DRD 2.1.4) reports.

DRD 2.1.3 Page 4/4

**DRD Continuation Page**

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: The Report shall provide data on
accumulated costs and funding projections for management of the contract
and shall serve as the basis for contractor communication with NASA
concerning financial planning and control.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**

NFS 1852.242-73 NASA Contractor Financial Management Reporting

NMI 9501.1 NASA Contractor Financial Management Reporting Systems

> NPG 9501.2C NASA Contractor Financial Management Reporting

13.3 [**CONTENTS**:]{.underline}

As defined in NPG 9501.2C, NMI 9501.1, and NFS 1852.242-73. Both the
initial baseline reports and the subsequent reports should be submitted
at the same level of detail.

13.4 **[FORMAT:]{.underline}** The reports shall be prepared in
accordance with NPG 9501.2C or its most current revision, NMI 9501.1,
and NFS 1852.242-73 and as defined in the statement of work and by
contracting officer's letter. All reports shall be provided
electronically and in hard copy form. The contractor shall report cost
and hours via electronic submission or diskette and must be compatible
with Microsoft Excel. A hardcopy of the data must accompany either
method and shall be signed by the same person who signs the hard copy
NF533. The totals of the submitted data shall agree with the NF533
totals. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: 2.1.4 ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: Plans --1; Reports -- 2 4. DATE REVISED:

5\. PAGE: 1/2

6.  TITLE: Performance Measurement Plan and Reports

7.  DESCRIPTION/USE: The Performance Measurement Plan shall measure and
    assess the contractor's effective management of all contract
    requirements and SOW elements in an integrated and time-correlated
    cost, schedule, content, and quality (technical metrics) system.
    This plan shall include a surveillance plan that defines technical
    metrics reporting for SOW (including FSAs) Expectations and
    Standards for Excellence. This plan shall describe both the
    technical metrics (technical metrics reports) and the
    cost/schedule/content metrics (cost performance reports) and how
    these reports are integrated into a comprehensive management
    performance assessment process. This plan shall describe how the
    contractor uses these reports and the underlying data to effectively
    manage the work. These reports will be used by the Government to
    assess the contractor's performance.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION: Draft plan with proposal; final version 60 days
    after the end of phase-in. Approved report formats with actual data
    shall be submitted beginning 60 days after end of phase-in.

10. SUBMISSION FREQUENCY: Plan shall be update as required. Reports
    shall be monthly. Technical metrics shall be no older than 21 days.
    Cost, schedule, and content metrics shall be no older than 10 days.

11. REMARKS: For the technical metrics use as a reference guide the
    following JSC documents: JSC-26010 DA3 Software Sustaining
    Engineering Metrics; JSC-25519 DA3 Software Development Metrics;
    JSC-36112 DA3 Development Project Metrics; and JSC-26458 DA3/SSO
    Sustaining and Operations Performance Management Metrics.

12. INTERRELATIONSHIP: SOW 2.1.4, 2.1.3 and DRD 2.1.3 Financial
    Management Reports

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} The Performance Measurement Plan shall
        describe the system, processes, and reports that the contractor
        will utilize to measure an integrated and time-correlated cost,
        schedule, content, and quality performance and will utilize for
        accomplishing and managing all services and functions described
        in the statement of work. This plan will provide a comprehensive
        integration of all metrics/measurement and management systems of
        the prime, subcontractors, team arrangements, and major vendors.

> The Performance Measurement Reports shall provide the quality metrics,
> cost, and schedule information in accordance with the Performance
> Measurement Plan. These reports shall be the same metrics and
> cost/schedule information used by the contractor to effectively
> measure performance and to manage the work of all services and
> elements of the SOW. The level of detail in these reports to the
> government will normally be limited to the SOW WBS reporting level, as
> negotiated and finalized in the plan, except for level of detail
> required to explain variances exceeding reporting thresholds.

DRD 2.1.4 Page 2/2

### DRD Continuation Page

2.  [APPLICABLE DOCUMENTS:]{.underline} In accordance with NASA Policy
    Document (NPD) 9501.3 and 9501.4 in Section 2 of JSC 27450,
    Performance Measurement System Handbook.

3.  [CONTENTS:]{.underline} In accordance with JSC 27450, Performance
    Measurement System Handbook Performance Measurement System
    Plan/System Description Document - NPD 9501.3 and 9501.4, Earned
    Value Performance Management.

> Performance Measurement System Plan/Performance Metrics and
> Surveillance Reports shall use as a guide the metrics handbooks listed
> under the "Remarks" section of this DRD. These documents shall include
> definition of metrics and thresholds for variance analysis to identify
> cause, impact, and corrective action for any out of limit conditions.
> The definition of metrics shall be an integrated, time-correlated and
> uniform set that are applicable across all centers, services,
> products, subcontractors, and major vendors. Thresholds may vary
> depending upon types of services, level of service, locations, and
> user requirements.
>
> The contractor shall develop and report standard units of service
> performance assessment metrics and fully loaded costs for all
> services. These standard units of service metrics and costs shall be
> used to compare actual versus planned performance by service level
> agreement. Additionally, the contractor shall develop and report
> customer service satisfaction metrics. For customer satisfaction, a
> survey will be solicited monthly from a broad base of service users.
> The survey will encompass the following areas:
>
> a\) Quality of service
>
> b\) Quantity of service
>
> c\) Responsiveness of service
>
> d\) Quality of personnel communications (interface)
>
> e\) Ease of use (user friendliness)
>
> f\) Access (frequency of contact required to schedule service)

13.4 [FORMAT:]{.underline} In accordance with JSC 27450 Performance
Measurement System Handbook

Cost Performance report - Reference DOD DI-F-6000C and ANSI ASC X.12
Electronic Format

Technical Performance Metrics and Surveillance Reports - Reference
metrics handbooks listed under applicable documents as a guide. See
Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 [MAINTENANCE:]{.underline} Changes shall be incorporated by change
pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO**.: 2.1.5 **ISSUE:** Initial 2. **DRL LINE ITEM NO**.:

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Government Property Management Plan

7\. **DESCRIPTION/USE**: To describe the method of administering
Government personal property.

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Draft 90 days after contract award; final
version 6 months after contract award.

10\. **SUBMISSION FREQUENCY**: Initial, with updates as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 2.1.5 and Clause 52.245-5

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: The Government Property Management plan
defines the contractor\'s use, maintenance, repair, protection, and
preservation of Government personal property. It shall describe the
contractor's approach to receiving, handling, stocking, maintaining,
protecting, and issuing Government property.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

Federal Acquisition Regulation (FAR) Part 45

NASA FAR Supplement (NFS) Part 1845

13.3 **[CONTENTS]{.underline}**: This plan shall consist of those
procedures which constitute the contractor\'s Property Management Manual
and shall include at a minimum the following categories:

a\. Property Management f. Movement

b\. Acquisition g. Storage

c\. Receiving h. Physical Inventories

d\. Identification i. Reports

e\. Records j. Consumption

13.3 **[CONTENTS]{.underline}**: (Continued)

k\. Utilization p. Reconcile Contractor

l\. Maintenance Records with Financial

m\. Subcontractor Control Records

n\. Disposition q. Center-Unique

o\. Contractor Closeout Considerations

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: 2.1.6-a ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: 1 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Service Element Management Plan

7.  DESCRIPTION/USE: The Service Element Management Plan will be used to
    provide insight into the contractor's approach for Service Element
    Management.

8.  DISTRIBUTION: Per Contracting Officer's Letter.

9.  INITIAL SUBMISSION: Draft with proposal; final version 60 days after
    the end of phase-in.

10. SUBMISSION FREQUENCY: Updated by August 1 of each year.

11. REMARKS:

12. INTERRELATIONSHIP: SOW 2.1.6

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} The Service Element Management Plan shall
        describe the contractor's approach to managing service element
        responsibilities in support of the CSOC, except for Real
        Property, which is covered in DRD 2.1.6-b.

    2.  [APPLICABLE DOCUMENTS:]{.underline} None

    3.  [CONTENTS:]{.underline} The plan shall identify the contractor
        approach for maintaining and/or operating and where applicable,
        sustaining the service elements included in the FSAs of the SOW.
        The plan shall include the recommended government insight
        metrics to verify the levels of performance as outlined in the
        SOW.

    4.  [FORMAT:]{.underline} Contractor format is acceptable. All
        documents must be provided in both electronic and hard copy. See
        Contracting Officer's letter BN-02-062 dated June 14, 2002.

    5.  [MAINTENANCE:]{.underline} Updated annually or as required by
        change page or new revision.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** 2.1.6-b **ISSUE:** Initial 2. **DRL LINE ITEM NO.:**

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE:** 1/2

6\. **TITLE**: Real Property Management Plan

7\. **DESCRIPTION/USE**: The Real Property Management Plan will be used
to provide insight into the contractor's approach for managing real
property responsibilities.

8\. **[DISTRIBUTION:]{.smallcaps}** Per Contracting Officer's Letter.

9\. **INITIAL SUBMISSION**: Draft 30 days after contract award; final
version 60 days after the end of phase-in.

10\. **SUBMISSION FREQUENCY**: Updated by August 1 of each year.

11\. **REMARKS:**

12\. **INTERRELATIONSHIP**: SOW 2.1.6.

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: The Real Property Management Plan shall
describe the contractor's approach to managing facility responsibilities
in support of the CSOC and shall include a 5 year plan which identifies
the facility projects required, regardless of ultimate fund source, for
each year for the five fiscal years beginning three years from the
commencement date of the current fiscal year. This plan shall document
contractor processes and implementation approach for real property
management to include environmental compliance and restoration
requirements. The plan shall address the long range goals for the
transition of real property management responsibilities in the future.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

NHB 8820.2 Appendix C Facility Project Implementation Handbook

NHB 7234.2 Facilities Utilization Program

> NPD 8400.1 Management of Facility Maintenance
>
> NPG 8400.2 Facilities Maintenance and Energy Management Handbook
>
> (Applicable to those facilities where CSOC will provide "brick and
> mortar" services)
>
> NMI 8800.14 Policies and Procedures for Real Propery Management
>
> NHB 8800.15 Real Estate Management Program Implementation Standards
>
> GHB 4400.3 Tracking Station and Property Procedures
>
> GHB 8250.2 Independent Financial Control of Real Property

DRD 2.1.6.b Page 2/2

**DRD Continuation Page**

13.3 **[CONTENTS]{.underline}**: The plan shall identify the contractor
approach to the coordination of real property responsibilities and
budget priorities to optimize maintenance, repair, and replacement
projects for facilities and facility systems and environmental
compliance and restoration requirements across the CSOC Government owned
locations. Provide a real property management plan that will encompass
facility space utilization planning and integrated facility project
planning and reporting requirements. The management structure, processes
and reporting requirements, techniques and formats must be established
and/or defined and documented to insure adequate visibility and insight
for NASA Space Operations Program Management and Center Facility
Management.

The plan shall also address the following:

\(1\) Process for environmental assessments and permit applications for
constructed and modified facilities and processes.

\(2\) Process to insure facility system drawings and as-builts are kept
current for contractor generated changes and all changes are
incorporated as required. Contractor shall impose a self-audit with the
results reported annually.

\(3\) Incorporation of local Government facility project approval
process and standardization requirements that are in place at affected
sites. (e.g., Air Force, Army, TAL sites, KSC, etc.).

\(4\) Propose general guidelines to establish boundaries or limits of
acceptable facility actions that may be accomplished without Contracting
Officer involvement. These guidelines must be approved by the
Contracting Officer prior to use.

\(5\) Process and management structure to implement facility projects.

\(6\) Completion milestone definitions for management and reporting of
projects.

\(7\) Procedure to allow for in-progress audit and final evaluation of
project completion and documentation.

\(8\) Plan for conducting a facility condition assessment.

13.4 **[FORMAT:]{.underline}** Contractor format is acceptable. All
documents must be provided in both electronic and hard copy. See
Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Updated annually or as required by
change page or new revision.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO**.: 2.1.6-c **ISSUE:** Initial 2. **DRL LINE ITEM NO**.:

3\. **DATA TYPE**: 2 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Real Property Project Reporting Requirements

7\. **DESCRIPTION/USE**: The real property project reports will be used
to provide insight into the scope, cost, schedule and performance of
real property projects.

8\. **DISTRIBUTION:** Per Contracting Officer's Letter.

9\. **INITIAL SUBMISSION**: As required.

10\. **SUBMISSION FREQUENCY**: As required.

11\. **REMARKS:**

12\. **INTERRELATIONSHIP**: SOW 2.1.6

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: The project requirements documents shall
be provided in sufficient detail to allow for an independent cost
estimate of all scope and related issues identified to accomplish the
project. The other project documentation shall be submitted for each
facility project as required.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: NHB 8820.2, Appendix C.

13.3 **[CONTENTS]{.underline}**:

The contractor shall submit facility project documentation and reporting
as follows:

\(1\) Facility projects greater than \$50K and less than \$200K (for
documentation purposes).

\(a\) NASA Form 1509 and 1510 (prior to project start).

\(2\) Facility projects greater than \$200K.

\(a\) Facility project description, justification and cost estimate
(NASA Form 1509, 1510) annually and as required for revisions/updates).

\(b\) Project requirements document (include all requirements and costs
associated with a completed project).

\(c\) Flash bid reports (NASA Form 1579) (after bid opening).

\(d\) Facilities Project Implementation Schedule (after award of
project).

\(e\) Final acceptance certificate including a recap of all funding
(after project completion).

\(3\) Facility projects greater than \$5M (in addition to the above
reporting requirements).

\(a\) Project Management Plan (prior to design start).

\(b\) Facility Project Pre-Advertisement Review Checklist (NASA Form
1580) (after design completion/prior to advertisement).

\(4\) A Facilities Construction Completion Report shall be submitted no
later than thirty (30) days following the financial completion of the
facility project and transferred to appropriate Center's real property
records for accountability.

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable. All
documents must be provided in both electronic and hard copy form. See
Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Project documentation shall be
updated as required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** 2.1.6-d **ISSUE:** Initial 2. **DRL LINE ITEM NO.:**

3\. **DATA TYPE**: 1 (Plan) 4. **DATE REVISED:**

2 (Reports) 5. **PAGE:** 1/3

6\. **TITLE**: Information Technology (IT) Plan and Reports

7\. **DESCRIPTION/USE**: To document the contractor's compliance with
Federal and NASA IT Planning and Reporting regulations and requirements.

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Initial Master Plan submittals are due 90
days after contract award I/T standards are due 60 days after contract
award and are required prior to the submittal of any I/T plans. I/T
plans are required prior to any I/T acquisition. Initial I/T inventory
report submittals are due on February 1 of each year.. Prior to any I/T
acquisition, a summary of the I/T planning and standards process shall
be presented to the JSC CIO, as well as a summary of Level A and Level B
I/T Plans to the JSC Information Resources Management Steering Council

10\. **SUBMISSION FREQUENCY**: I/T plans, and associated process and
plan summaries (see 13.3 below) are required twice annually (POP-1 and
POP-2 time frames). Reports and Master Plans are required once annually.
Security reports are required as specified in the JSC I/T Security
Handbook (JPG 2810.1). Other updates as required.

11\. **REMARKS:** The following are reference documents for I/T
planning**:**

\(a\) Current JSC CIO instructions/guidelines for I/T plans.

\(1\) JSC memorandum AI-95-090 dated July 11, 1995, subject "Information
Technology Plans"

\(2\) NASA Headquarters (CIO) memorandum dated October 5, 1995, subject
"Annual Request for Information Resources Strategic Implementation
Plans"

\(3\) NASA Headquarters (CIO) memorandum dated October 12, 1996, subject
"Annual Request for Information Technology Plans"

\(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\) JSC memorandum AI-96-035 dated April 30, 1996, subject "Proposed
Policy on

Applicability of NASA Information Technology (I/T) Standards to
Contractors"

\(b\) MOD Standard Facilities Practices and Technologies Handbook (JSC
27201)

\(c\) Office of Management and Budget Circular A-130

\(d\) Computer Security Act of 1987

\(e\) JSC's I/T Security Handbook (JPG 2810.1)

\(f\) Executive Order 12845, Energy-efficient Microcomputers

\(g\) 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"

\(h\) KSC memorandum dated June 7, 1996, subject: "Final Recommendations
of Agency wide Facilities Maintenance Metrics"

\(i\) IT Management Reform Act of 1996 (the "Cohen Bill")

DRD 2.1.6.d Page 2/3

**DRD Continuation Page**

12\. **INTERRELATIONSHIP:** SOW 2.1.6, 2.3, 2.4.

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: The Information Technology Plan and
reports document the contractor's compliance with Federal and NASA I/T
planning and reporting regulations and requirements.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

13.3 **[CONTENTS]{.underline}**:

\(a\) The I/T plan shall contain an integrated overview of the
facilities and systems, current architecture, current processes, current
standards, as well as future plans for changes in architecture,
processes, and/or standards. Guidelines for an accepted process are
described in the JSC/MOD Standard Facilities Practices and Technologies
Handbook (JSC 27201).

\(b\) An annual, contract-wide I/T Plan, per current NASA and JSC CIO
instructions/guidelines. For FY reporting requirements, refer to the I/T
Planning Process available on the JSC CIO Home Page. Reporting
requirements will reflect NASA's implementation of OMB's I/T planning,
budgeting and reporting requirments (as based on the Clinger-Cohen Bill,
the OMB Dirculars referenced above, and applicable portions of OMB's
Capital Programming Guide.) In general, the scope of these requirements
may be determined by reviewing both the JSC I/T Plan process and the
above referenced NASA Headquarters' memorandums concerning Annual I/T
Plans. Included in the NASA Headquarters Annual I/T Plans request are
the instructions for completing the A-11 portion of the budgeting
activity. Instructions/guidelines are:

\(1\) In concert with the POP-1 each year, a high-level (Level A)
multi-year plan is required. This plan will define and justify the major
I/T systems and initiatives planned for each of the POP-required fiscal
years,

with a corresponding list of I/T (i.e., hardware and software) platforms
required to support

each initiative. Level A plans also include an obsolescence management
plan as

described in NASA CIO Executive Notice 03-95.

\(2\) In concert with the POP-2 each year, a more detailed Level B I/T
Plan for the "next" FY

only is required, as well as any updates to the Level A plan. Level B
will describe I/T purchases by platform standards (in support of

approved Level A initiatives) to be acquired during the year.

\(c\) De-facto and accepted I/T standards throughout the contract will
be documented, and processes which will result in contract-wide I/T
standards will be established. Included in this report will be how the
contractor is complying with AI-96-035.

\(d\) I/T inventory reports according to NASA CIO Executive Notices. At
a minimum, the reports shall include the data specified on the JSC CIO
Home Page under "Inventory Report Requirements."

\(e\) The contractor shall report on the security status of each
information technology and telecommunication system under the
contractor's management 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.
These reports shall conform to the types and frequencies of those
required by the NASA Center under whose guidance the system is operated.

DRD 2.1.6.d Page 3/3

**DRD Continuation Page**

At a minimum, the contractor shall comply with direction in the latest
edition of 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 as been assigned security
responsibility for the system.

\(2\) That a system security plan 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 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.

13.4 **[FORMAT]{.underline}**: Contractor shall conform to delivery
media formats and electronic data formats as per the JSC I/T
Architecture Handbook. See Contracting Officer's letter BN-02-062 dated
June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** 2.1.6-e **ISSUE:** Initial 2. **DRL LINE ITEM NO.:**

3\. **DATA TYPE:** 1 4. **DATE REVISED**:

5\. **PAGE:** 1/1

6\. **TITLE:** Service Element Table

7\. **DESCRIPTION/USE**: The Service Element Table will be used to
specify the Government provided service elements to be used in
performing the CSOC contract.

8\. **[DISTRIBUTION:]{.smallcaps}** Per Contracting Officer's Letter.

9\. **INITIAL SUBMISSION**: Draft table with proposal; final version at
end of contract phase-in.

10\. **SUBMISSION FREQUENCY:** Annually based on the start date of
contract.

11\. **REMARKS:**

12\. **INTERRELATIONSHIP:** SOW 2.1.6.

13\. **DATA PREPARATION INFORMATION:**

13.1 **[SCOPE]{.underline}:** The Service Element Table will be used to
specify the Government provided service elements to be used in
performing the CSOC contract.

13.2 **[APPLICABLE DOCUMENTS]{.underline}:** None

13.3 **[CONTENTS]{.underline}:** The table shall identify the service
element to be utilized, its location, and the related responsibilities
(i.e., maintenance, operations, sustaining engineering).

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable. All
documents must be provided in both electronic and hard copy. See
Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Updated annually or as required by
change page or new revision.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** 2.1.6-f **ISSUE:** Initial 2. **DRL LINE ITEM NO.:**

3\. **DATA TYPE:** 1 4. **DATE REVISED**:

5.  **PAGE:** 1/1

6\. **TITLE:** Emergency Preparedness and Disaster Recovery Plan

7\. **DESCRIPTION/USE**: To describe the contractor\'s approach for
emergency preparedness and disaster recovery.

8\. **[DISTRIBUTION:]{.smallcaps}** Formatting and electronic
distribution per Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Final version 60 days after the end of
phase-in..

10\. **SUBMISSION FREQUENCY:** Updates as required

11\. **REMARKS:**

12\. **INTERRELATIONSHIP:** Statement of Work 2.1.6

13\. **DATA PREPARATION INFORMATION:**

13.1 **[SCOPE]{.underline}:** The Disaster Recovery Plan shall identify
critical facilities/systems that require backup or alternate sites.

2.  **[APPLICABLE DOCUMENTS]{.underline}:**

NMI 1040.3 Emergency Preparedness Program

QS-EPP-95-001 NASA Emergency Preparedness Plan

GMI 1040.6 GSFC Emergency Preparedness Plan

JSC-05900 JSC Emergency Preparedness Plan

KHB 1040.1F KSC Emergency Preparedness Plan

KHB 1040.1F KSC Hurricane Preparation and Recovery (Appendix H)

MMI 1040.3E MSFC Emergency Preparedness Plan

13.3 **[CONTENTS]{.underline}:** The Disaster Recovery Plan shall
include, as applicable, the following: a risk analysis of all critical
facilities/systems; identification of specific equipment/facilities that
require backup or alternate sites; identification of backup strategies;
emergency response plans; backup facility/alternate sites operating
plans.

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO**.: 2.1.7 **ISSUE:** Initial 2. **DRL LINE ITEM NO**.:

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **TITLE**: Configuration Management Plan

7\. **DESCRIPTION/USE**: To describe the contractor\'s method for
accomplishing the configuration management requirements of the contract.

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Draft with proposal; final version 60 days
after the end of phase-in..

10\. **SUBMISSION FREQUENCY**: Initial, with updates as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 2.1.7

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: The plan shall describe the contractor's
management approach and planned implementation methods for accomplishing
the configuration management requirements of the contract.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[CONTENTS]{.underline}:** The plan shall prescribe the
configuration management processes for hardware, software, firmware, and
documentation to be implemented and methods to be used for configuration
identification, interface control, change control, documentation, status
accounting, and configuration verification. The plan shall describe the
contractor's CM organization, policies, procedures, implementation
approach, and control systems that are to be used to ensure proper
performance of all required contract CM activities.

The plan shall also describe the configuration management activities,
processes and systems to be employed to support the NASA change
evaluation and control process for the approval of requirements.

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO**.: 2.1.8 **ISSUE:** Initial 2. **DRL LINE ITEM NO**.:

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/2

6\. **TITLE**: Security Management Plan

7\. **DESCRIPTION/USE**: The plan will be used to define the CSOC
security management task and will include separate annexes/appendices
for COMSEC procedures and Secure Operations Procedures.

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Final version 60 days after the end of
phase-in..

10\. **SUBMISSION FREQUENCY**: Initial, with updates as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 2.1.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}:** The Security Management Plan will describe
the Contractor's approach for meeting and maintaining the security
integrity of the security baseline. The plan will address the security
requirements for facilities, systems, equipment, personnel, information,
classified automated information systems, and communications, as well as
COMSEC and Secure Operations Procedures. This plan establishes the
security procedures, Government/contractor relationships and assigns
responsibilities for all physical, personnel, and ITS security required
for the activity specified in the SOW. It is applicable to all
contractor and subcontractor personnel.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

OMB Circular A-130, Appendix III, Security of Federal Automated
Information Resources

FAR 52.204-2

NISPOM National Industrial Security Program Operating Manual

JSC COMSEC Maintenance Support Plan

COMSEC Logistics Control Guide

STS COMSEC Key Control Agreement

COMSEC Security Procedures (STSOC-PR-001033B)

International Program Security Requirements Handbook

Arms Export Control Act (AECA)

Executive Order 12958: National Security Information

National Security Decision Memorandum (NSDM) 119

Export Administration Regulations (EAR)

TEMPEST Countermeasures for Facilities (NTISSI 7000)

NASA Security handbook 1620.3 Chapter 46

NASA COMSEC Manual NHB 1600

Space Network Security Classification Guide

DRD 2.1.8 Page 2/2

**DRD Continuation Page**

13.3 **[CONTENTS]{.underline}**: The management structure, processes and
reporting requirements, techniques and formats must be established,
defined, and documented to ensure adequate visibility and insight for
Government personnel. The Security Management Plan shall include:

a.  A description of the contractor's security management structure and
    assignment of responsibilities.

b.  The approach for integrating security requirements into functions as
    described in the SOW , including interfacing with subcontractors.

c.  Identification of the security interfaces with NASA, DoD, and other
    government agencies, and contractors.

d.  Description of the security baseline configuration management
    program.

e.  The methodology for obtaining certifications and re-certifications.

f.  Process for developing security implementation plans as requested by
    NASA for new/expanded, classified systems/facilities and security
    programs.

g.  COMSEC procedures which include, but are not limited to:

```{=html}
<!-- -->
```
1.  Issuance and transfer of COMSEC material

2.  COMSEC personnel responsibilities

3.  Opening and closing procedures for COMSEC facilities

4.  Insecurity reporting procedures

5.  Maintenance and operations procedures

6.  Inventory

7.  Emergency procedures

Secure Operations Procedures which include, but are not limited to:

1.  AUTODIN AND SPADOC message transmission, receipt, storage and
    delivery

2.  Classified facsimile message procedures

3.  Opening and closing procedures for message centers

4.  Insecurity reporting procedures

5.  Maintenance and operations procedures

6.  Emergency procedures

The ITS Security Plan shall be a separate section and shall be in
accordance with OMB Circular A-130, Appendix III.

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

> 1\. **DRD NO**.: 2.1.9-a **ISSUE:** Initial 2. **DRL LINE ITEM NO**.:
>
> 3\. **DATA TYPE**: 1 4. **DATE REVISED**:
>
> 5\. **PAGE**: 1/9
>
> 6\. **TITLE**: Safety and Health Plan
>
> 7\. **DESCRIPTION/USE**: This DRD is controlled by the JSC Safety,
> Reliability, and Quality Assurance Office in accordance with JMI
> 2314.1, "JSC Data Requirements Descriptions," as revised.

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter. (Note: Distribution will be to each
Center/Sites' Safety, Health, and Environmental Compliance Offices).

9\. **INITIAL SUBMISSION**: Draft with proposal; final version 60 day
after the end of phase-in..

10\. **SUBMISSION FREQUENCY**:

11\. **REMARKS:**

12\. **INTERRELATIONSHIP:** SOW 2.1.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: When preparing its safety and health plan,
the offeror/contractor is expected to determine whether the items below
are applicable to its contract performance and tailor its plan
accordingly. This determination 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 determination.

13.1.1 Policy. A safety policy statement will be included in the plan.

13.1.2 Authority and Accountability. The plan will state that it will be
maintained as required to be consistent with applicable NASA
requirements and contractual direction as well as applicable Federal,
state, and local regulations. The plan will 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.

13.1.3 Management Structure. Clearly define line and staff
responsibilities for safety, health, and environmental protection.
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).

13.1.4 Safety Program Management. Identify all personnel assignments and
basic techniques to be applied to accomplish the safety program goals.
As a minimum, the following details shall be provided:

13.1.4.1 Assignment of specific safety roles and responsibilities to
individuals by title. The following information will be provided as a
minimum:

DRD 2.1.9-a Page 2/9

**DRD Continuation Page**

13.1.4.1.1 Designated Safety Official (or equivalent). Identify by title
the official(s) responsible for implementation of this plan and all
formal contacts with regulatory agencies and with NASA.

13.1.4.2 Identification of 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).

13.1.4.3 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 NASA training resources (such as asbestos worker
training/certification, hazard communication, etc.) as appropriate with
particular emphasis on programs designed for the multi-employer work
environment on NASA property.

13.1.4.4 Assignments, procedures, and frequency for regular inspection
and evaluation or work areas for hazards and accountability for
implementation of corrective measures. 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 contractor self evaluations, risk evaluations, or
the monthly Accident/Incident Summary reports.

13.1.4.5 Identification of methods to assure the reporting and
investigation of mishaps and close calls and corrective actions
implemented to prevent recurrence. Discuss use of NASA Form 1627 and
alternate forms used by contractor with emphasis on timely notification
of NASA; investigation procedures; exercise or 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. Discuss immediate
notification requirements for fires, hazardous materials releases, and
other emergencies.

13.1.4.6 Establishment of administrative procedures and responsibilities
for emergency preparedness plans and procedures.

13.1.4.7 Participation in the review, updating, and modifications of
safety requirements identified in this plan 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.

13.1.4.8 Management techniques and criteria used to determine the need
for safety engineering tasks and the methods for identification and
control of hazards associated with work performed. All safety
engineering products which address operations, equipment, etc., on NASA
property will be subject to DISC SR&QA review and concurrence in
accordance with DRD 2.1.9-b unless otherwise specified in the approved
safety and health plan.

DRD 2.1.9-a Page 3/9

**DRD Continuation Page**

13.1.5 Procurement and Contract Safety. 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.

13.1.6 Hazardous Materials, Hazardous Items, and Hazardous Waste.

13.1.6.1 Hazardous Material. State what controls over procurement,
storage, issuance, and use of hazardous materials are currently in
place. Describe method by which material safety data will be provided to
NASA.

13.1.6.2 Potentially Hazardous Items. Describe how the controls over
procurement, storage, issuance, and use of potentially hazardous items
operate. Identify any training/certification requirements as
appropriate. State method by which hazards associated with potentially
hazardous items will be documented and provided to NASA.

Potentially Hazardous Items are defined as "An end item, element,
system, subsystem, article, or component with the potential for exposure
of personnel, facilities, equipment, or the environment to hazards
arising from performance of work, use, handling, manufacturing,
packaging, transportation, storage, inspection, or disposal."

13.1.6.3 Hazardous Waste. Set forth controls over the generation,
storage, handling, and disposal of hazardous waste. Identify
training/certification requirements as appropriate.

13.1.7 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. JHB 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 NASA as
part of the Safety Plan for review and approval. NASA and the Contractor
will decide jointly which operations are to be considered hazardous,
with NASA as the final authority. Before hazardous operations commence,
the Contractor will develop a schedule to perform the following and
submit it for NASA concurrence:

13.1.7.1 Hazardous Operations Procedures. Written hazardous operations
procedures will be developed and approved for all hazardous operations
with particular emphasis on identifying the job safety steps required.
The contractor may implement this requirement as follows:

13.1.7.1.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

13.1.7.1.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 appropriate NASA Health, Safety, and
Environmental Compliance Office for review and approval.

DRD 2.1.9-a Page 4/9

**DRD Continuation Page**

13.1.7.2 Training and Certification. A training and certification
program will be developed and implemented for personnel involved in
hazardous operations such as confined space entry and lockout/tagout.
Set forth procedures for training and certification of personnel who
will perform tasks which have been determined to be hazardous by NASA or
the contractor. 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.

13.1.7.3 Hazardous Operations Permits. Identify the following permits:

13.1.7.3.1 Operations Involving Toxic Materials or Health Hazards. Set
forth method by which onsite work exposures related to potentially toxic
or health hazardous chemical or physical agents will be identified. Such
operations must be evaluated by the appropriate NASA Occupational Health
Office and must be properly controlled as advised by same. The
Occupational Health Office must be notified prior to initiation of any
new or modified operation potentially hazardous to health.

13.1.7.3.2 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 any NASA site must be evaluated
by the appropriate Environmental Services Office and must be properly
controlled as advised by same. The Environmental Services Office must be
notified prior to initiation of any new or modified hazardous waste
operation on any NASA site.

13.1.7.3.3 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 appropriate
Environmental Services Office. Emphasis shall be placed on providing for
sufficient lead time for processing permits through the appropriate
state agency and/or the Environmental Protection Agency.

13.1.8 Fire Prevention. Set forth administrative requirements and
procedures for control of and regularly scheduled inspections for fire
and explosion hazards.

13.1.9 Pollution Prevention. 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 (including but
not limited to the following: JMI 1710.9, JMI 8800.3, JMI 8800.4, and
JMI 8837.1).

13.1.10 Protective Equipment. Set forth procedures for obtaining,
inspecting, and maintaining protective equipment, as required, or
reference written procedure pertaining to this subject. Describe
approach to training personnel in the proper use and care of protective
equipment. Set forth methods for keeping records of such inspections and
maintenance programs.

DRD 2.1.9-a Page 5/9

**DRD Continuation Page**

13.1.11 Risk Evaluation. The contractor shall state responsibility and
procedures to determine the significance, intrinsic worth, and
criticality of the contractor operations in a manner that proper risk
management techniques can be applied and notable safety risk reported to
the appropriate Health, Safety, and Environmental Compliance Office. The
contractor will discuss ranking the risk in a severity classification.
Risk evaluation will apply to the operations and products of the
contractor's operation. The approach to identifying and implementing
specific risk evaluation tasks, managing the risks, and documenting the
results will be discussed.

13.1.12 Self Evaluations and Reporting. Set forth responsibilities and
methods for internal audits and evaluations of the overall safety and
health program. Identify 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.

Government Furnished Data. JHB 1700.1, Safety Requirements Handbook for
Safety, Health, Environmental Protection, and Emergency Preparedness
(formerly JHB 1700.1, JSC Safety Manual), as revised (including all
subsequent revisions during the life of the contract).

13.1.13 Site Specific Requirements. Address the following for all work
performed at the designed NASA Center.

13.1.13.1 Johnson Space Center (JSC). This includes JSC, Ellington
Field, White Sands Test Facility, and other JSC prime contractor
locations.

13.1.13.1.1 Safety Representative. Identify by title the individual who
will be trained and certified in accordance with JMI 1710.4, "JSC Safety
Representatives," 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.

13.1.13.1.2 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.

13.1.13.1.3 Facility Baseline Documentation. Assignment of
responsibility for maintaining facilities baseline documentation in
accordance with JSC Management Instruction (JMI) 8830.1, "Facilities
Baseline Documentation." 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 contractual or technical direction.

13.1.13.1.4 Hazardous Material. State method by which compliance with
JSC's Hazard Communication Program (as defined in JHB 1700.1) and JMI
1710.9, "Control of Hazardous Materials," will be accomplished.

DRD 2.1.9-a Page 6/9

**DRD Continuation Page**

13.1.13.1.5 Hazardous Operations Permits. Identify facilities,
operations and/or tasks where hazardous operations permits will be
required as specified in JHB 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.

13.1.13.1.6 Asbestos Exposure. Set forth method by which compliance is
assured with JSC Asbestos Control Program as established in JHB 1700.1,
as revised, and JHB 8800.1, "Asbestos Control Manual," as revised.

13.1.13.1.7 Fire Prevention. State compliance with JMI 1713.2, "JSC Fire
Safety Program," as revised, and JMI 1713.3, "Building Fire Wardens," as
revised.

13.1.13.2 Goddard Space Flight Center (GSFC)

13.1.13.2.1 Describe the work to be performed on site (including unique
hazards likely to be encountered).

13.1.13.2.2 List the Safety Point of Contact (on site) for the company.

13.1.13.2.3 Define GSFC emergency procedures, including instructions on
Emergency console activation.

13.1.13.2.4 This section of the safety plan must make reference to the
following documents:

a\. NHB 1700.1 NASA Basic Safety Manual

b\. NMI-8621.1E Mishap Reporting and Investigation

c\. GHB 1040.1E GSFC Emergency Preparedness Manual

d\. Occupational Safety and Health Administration Standards, 29 CFR 1910
or 1926

as appropriate.

e\. Any state, county, and/or local safety codes which may be
applicable.

f\. FAR clauses 52.223-3, "Hazardous Material Identification and
Material Safety Data \--

Alternate I as prescribed by FAR 23.301

g\. NASA FAR Supplement Clauses 18-52.223-70, "Safety and Health" as
prescribed by

NFS 18-23.7004(c)

h\. NASA FAR Supplement Clauses 18-52.223-73, "Safety and Health Plan"
or Alternate I

i\. NASA FAR Supplement Clauses 18-52.223-72, "Potentially Hazardous
Items"

j\. GSFC 52.223-92, "Government Property\--Compliance with Safety
Standards"

k\. GSFC 52.223-91, "Safety and Health\--Additional Requirements"

13.1.13.3 Jet Propulsion Laboratory (JPL)

13.1.13.3.1 Safety and Health

\(a\) This schedule provision supplements and implements Clause
18-52.223-70, Safety and Health.

\(b\) [General]{.underline}. The safety and health plan required to be
submitted by the Contractor pursuant to paragraph (a) of the aforesaid
Clause 18-52.233-70 shall implement the requirements of Clause
18-52.233-70 and of the standards and specifications of paragraph (c) of
this provision and shall describe the means to be employed by the
Contractor to monitor and enforce said requirements. The plan shall
include the Contractor's standards and criteria for imposing safety and
health standards upon its subcontractors of any tier and its plans and
procedures for monitoring compliance with such standards. The Contractor
shall submit a safety and health plan in accordance with item #9 of this
DRD.

\(c\) [Standards]{.underline}. The following safety and health
standards, specifications, issuances, and reporting requirements are
prescribed pursuant to paragraph (a) of Clause 18-52.233-70:

DRD 2.1.9-a Page 7/9

**DRD Continuation Page**

\(1\) General Standards and Specifications: The Contractor shall comply
with applicable provisions of the Occupational Safety and Health
Standards of the Occupational Safety and Health Act of 1970, Rules and
Regulations of the Department of Labor issued pursuant thereto and
regulations of states provided for under the Act. The Government
acknowledges the Contractor is required to comply with safety
requirements established by the State of California but will use NHB
1700.1(VI-B), NASA Safety Policy, as a general policy guide.

\(2\) Aviation Safety: NASA Handbook (NHB) 7900.3(V2), Mission
Management Aircraft Operations Manual (March 1992) including reporting
requirements contained therein.

\(3\) Flight Project Safety: The Contractor shall include in each
Project Plan prepared for a flight project the safety needs and special
safety monitoring required for the flight project. The Project Plan
containing such requirements will be referenced in the flight project
task order issued by the Contracting Officer (CO) and the Contractor
shall comply with those requirements.

\(4\) Nuclear Safety: Radioactive material will be handled in accordance
with appropriate State of California, Department of Energy and/or
Nuclear Regulatory Commission requirements and in accordance with
National Aeronautics and Space Council document, "Nuclear Safety Review
and Approval Procedures for Minor Radioactive Sources in Space
Operations." Additionally, when radioactive material is to be used in
space launches, they shall meet the requirements of the Interagency
Nuclear Safety Review Panel (INSRP) as directed by the President of the
United States.

\(5\) Environmental Matters: Environmental controls shall be in
accordance with applicable NASA and other Federal, State, and local
regulatory requirements and in accordance with applicable Executive
Orders of the President. The Contractor shall also use its best efforts
to comply with the intent of NMI 8800.13B "Prevention, Abatement and
Control of Environmental Pollution."

\(6\) Propulsion Safety: Chemical Propulsion Information Agency
Publication No. 194, Chemical Rocket/Propellant Hazards, Volumes II and
III and DOD Manual 4145.26M, Contractor's Safety Manual for Ammunition
and Explosives, March 1986 shall be used as guides in establishing
propulsion safety requirements to be included in the safety and health
plan to be submitted in accordance with paragraph (b) above.

\(7\) Ammunition and Explosive Safety: DOD Manual 4145.26M, Contractor's
Safety Manual for Ammunition and Explosives, March 1986 and CAL/OSHA and
Federal OSHA regulations, shall be used in establishing ammunition,
explosive and related safety standards.

\(d\) [Illness, Incident, and Injury Experience Reports]{.underline}.
The following illness, incident, and injury experience reports are
prescribed pursuant to paragraph (c) of Clause 18-52.233-70:

\(1\) Experience Reports: The Contractor shall prepare and submit to the
Contracting Officer or CO representative reports of occupational related
illness, incidents and injury experience in paragraph 13.1.4.5 of this
DRD.

DRD 2.1.9-a Page 8/9

**DRD Continuation Page**

\(2\) Investigative Reports: The Contractor shall furnish reports of
investigation of individual incidents or accidents in formats approved
by the Contracting Officer or CO representative, provided, however, that
the Contractor shall not be required to furnish personally identifiable
information concerning Contractor or subcontractor employees.

\(3\) The Contractor shall immediately notify and furnish such other
reports as the Contracting Officer or C0 representative determines to be
related to the Contractors' safety and health program and its
experiences thereunder.

\(4\) Nothing herein shall be construed as diminishing the Contracting
Officer's rights pursuant to this contract.

13.1.13.4 Marshall Space Flight Center (MSFC)

13.1.13.4.1 This section of the safety plan must make reference to, and
state commensurate compliance with, the following documents:

a.  MMI 1040.3 - MSFC Emergency Plan

b.  MMI 1700.1 - Fire Prevention Program

c.  MMI 1700.4 - Safety and Environmental Health Standards

d.  MMI 1700.10 - Maintenance of Fire Surveillance and Suppression
    System

e.  MMI 1700.11 - Protection for Personal Property

f.  MMI 1700.14 - Safety Coordinations and Safety Monitors for MSFC
    Buildings and Structures

g.  MMI 1700.16 - Safety and Health Program

h.  MMI 1710.1 - Safety Review and Approval of Hazards and Potential
    Hazardous Facilities

i.  MMI 1710.4 - Safety Permits

j.  MMI 1710.6 - MSFC Program for Personnel Certification

k.  MMI 1711.2 - Mishap Reporting and Investigation

l.  MMI 8621.1E

13.1.13.5 Kennedy Space Center (KSC)

13.1.13.5.1 This section of the safety plan must make reference to, and
state commensurate compliance with, the following documents:

a.  KMI 1800.1 - Environmental Health Program

b.  KMI 1800.2 - KSC Hazard Communication Program

c.  KMI 1810.1 - KSC Occupational Medicine Program

d.  KMI 1860.1 - KSC Radiation Protection Program

e.  KHB 1711.1 - Reporting and Investigation of Mishaps

f.  KHB 1820.3 - KSC Hearing Conservation Program

g.  KHB 1820. 4 - Respiratory Protection Program

13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

DOL OSHA Standards, 29 CFR 1910 & 1926

NMI 1800.4 NASA Occupational Safety and Health

NMI 8621.1 Mishap Reporting and Investigation

NFPA Fire Code (NFPA Standards)

13.3 **[CONTENTS]{.underline}**:

DRD 2.1.9-a Page 9/9

**DRD Continuation Page**

13.4 **[FORMAT:]{.underline}** See Contracting Officer's letter
BN-02-062 dated June 14, 2002.

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

13.4.2 Table of Contents.

13.4.3 Body of plan as required (contractor's format acceptable).

Authority: FAR 52.223-3; NFS 18-52.223-70, 18-52.223-72, 18-52.223-73,

18-52.223-73 (Alt. 1).

13.4.4 Contractor format is acceptable; electronic availability
required.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO**.: 2.1.9-b **ISSUE:** Initial 2. **DRL LINE ITEM NO**.:

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/4

6\. **TITLE**: System Safety Program Plan

7\. **DESCRIPTION/USE**: This DRD is controlled by the JSC Institutional
Safety and Quality Division in accordance with JSCMD 2314.1K, "JSC Data
Requirements Descriptions," paragraph 5.b."

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter. (Note: Distribution will be to each
Center/Sites' Safety, Health, and Environmental Compliance Office).

9\. **INITIAL SUBMISSION**: Draft with proposal; final version 60 days
after the end of phase-in..

10\. **SUBMISSION FREQUENCY**: Initial, with updates as required.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 2.1.9 and DRD 2.1.9-a

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}:** Detailed System Safety requirements differ
according to different institutional and flight programs. The elements
of a System Safety Program Plan as outlined below are generic; refer to
the appropriate applicable references listed above for specific program
requirements.

System Safety Program 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.

13.1.1 Source Documents. The initial issue of the documents cited herein
(including those of any applicable amendments and revisions) shall be as
reflected in the contract schedule.

13.1.2 General. The System Safety Program Plan shall be documented in
narrative format and shall:

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

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

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

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

DRD 2.1.9-b Page 2/4

**DRD Continuation Page**

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: Applicable references for
this DRD are as follows:

NHB 1700.1, Volume 1, as revised, "NASA Safety Policy and Requirements
Document."

JHB 1700.1, "Requirements Handbook for Safety, Health, Environmental
Protection and Emergency Preparedness."

MIL-STD 882B, "System Safety Program for Systems and Associated
Subsystems and Equipment, General Requirements."

NHB 5300.4, 1D-2, as revised, "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 1700.7, as revised, "Safety Policy and Requirements for Payloads
Using the Space Transportation System."

NSTS 22254, as revised, "Methodology for Conduct of Space Shuttle
Program Hazard Analyses."

SSP 30000, Section 9, as revised, "Product Assurance Requirements."

SSP 30309, as revised, "Instructions for Preparation of Hazard Analyses
for the Space Station."

JSC 31000, Volume 3, as revised, "Product Design and Development
Requirements,"

paragraph 3.1.9, Safety

JSC 31000, Volume 4, as revised, "Product Assurance Requirements."

13.3 **[CONTENTS]{.underline}**:

13.3.1 System Safety Engineering Organization. The SSPP shall describe:

13.3.1.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.

13.3.1.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.

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

13.3.1.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.

13.3.1.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.

DRD 2.1.9-b Page 3/4

**DRD Continuation Page**

13.3.1.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).

13.3.2 System Safety Project Milestones. The SSPP shall:

13.3.2.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.)

13.3.2.b Provide a contract schedule of safety tasks showing start and
completion dates, reports, reviews, and man-loading, in relationship to
other contract milestones.

13.3.2.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.

13.3.3 System Safety Requirements. The SSPP shall:

13.3.3.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.

13.3.3.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 NASA documents or are unique to the project covered
by the SSPP.

13.3.3.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.

13.3.4 Hazard Analyses. The SSPP shall describe:

13.3.4.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.

13.3.4.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.

DRD 2.1.9-b Page 4/4

**DRD Continuation Page**

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

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

13.3.5 System Safety Data. The SSPP shall:

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

13.3.5.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.

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

13.3.6 Safety Verification and Audits. The plan shall describe:

13.3.6.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.

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

13.3.6.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.

13.3.7 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.

Authority. NFS 18-52.223-70, 18-52.223-72, 18-52.223-73, 18-52.223-73
(Alt 1).

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO**.: 2.1.10 **ISSUE:** **Rev. 1** 2. **DRL LINE ITEM NO**.:

3\. **DATA TYPE**: 1 4. **DATE REVISED**: 6/21/00

5\. **PAGE**: 1/1

6\. **TITLE**: Quality Manual

7\. **DESCRIPTION/USE**: 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.

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter.

9\. **INITIAL SUBMISSION**: Draft with proposal; initial version 60 days
after end of phase-in

10\. **SUBMISSION FREQUENCY**: **Initial, with updates as required. Full
version with complete compliance to paragraph 13.1 SCOPE shall be
submitted by October 31, 2000.**

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: SOW 2.1.10

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}:** The Quality Manual shall be in accordance
with the requirements of ANSI/ASQC Q9001-1994. The CSOC quality system
scope shall include products and services produced by Program
Management, Customer Services, Operations, Engineering, Maintenance,
Program Integration, and Performance Measurement.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[CONTENTS]{.underline}**: Each element of the contractually
imposed QMS requirements, including supplements to ANSI/ASQC Q9001-1994
elements shall be addressed 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.

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[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.)

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: 2.2 ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: Plans = 1 4. DATE REVISED:

Agreements = 1 5. PAGE: 1/2

Database = 2

6.  TITLE: Service Level Agreement Plan, Service Level Agreements, and
    Service Level Agreements Database

7.  DESCRIPTION/USE: To describe the contractor's Project and Contract
    Service Level Agreement/Factory Service Agreement (PSLA and
    CSLA/FSA) development and maintenance management plan, to deliver
    PSLAs and CSLAs/FSAs, and to develop and maintain the Service Level
    Agreements (SLAs) Database.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION: Draft plan with proposal; final version 60 days
    after the end of phase-end.; Draft CSLAs with proposal; final CSLAs
    at BAFO submission; SLA database 60 days after end of phase-in.

10. SUBMISSION FREQUENCY:

> Plan, Update as necessary
>
> CSLAs/FSAs, yearly with the Program Operating Plan process and updates
> as required
>
> PSLAs as necessary
>
> SLA Database updated with each proposed and approved PSLA and CSLA/FSA

11. REMARKS:

12. INTERRELATIONSHIP: SOW 2.2

13. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} SLAs are the main method to order SOMO and
contract services. The contractor will play an integral role in the SLA
development, maintenance, and tracking. Space Operation Directives
Agreements (SODA) CSLAs/FSAs will be generated by the Government.

13.2 [APPLICABLE DOCUMENTS:]{.underline} Space Operations Management
Plan (JSC-27527)

DRD 2.2 Page 2/2

### DRD Continuation Page

1.  [CONTENTS:]{.underline}

> SLA Plan: The SLA Plan defines the contractor's PSLA and CSLA/FSA
> development and maintenance management approach. The plan shall
> include the process, service reporting, associated government insight
> metrics, SLA integration approach, cost reporting (including the
> CSLA/FSA cost to PSLA cost allocation methodology), and address
> customer, government, and external (i.e. other government contracts or
> countries) interfaces.
>
> SLAs: The SLAs consist of both CSLAs/FSAs & PSLAs. Each PSLA defines
> the customer specific project Space Operations Services agreements
> with the standard services from the service catalog and project unique
> requirements. Each CSLA/FSA aggregates the PSLA requirements between
> CSOC Data, Mission, and Center Unique Services. CSLAs/FSAs shall
> contain the following at a minimum:
>
> Overview - General description of the work covered in the CSLA/FSA.
>
> Service Requirements - Reference to the SOW requirements that are
> needed to fulfill the CSLA/FSA. Additional information to clarify each
> requirement should be added, if needed. This section should also
> include Performance Standards.
>
> Integrated Table - This table correlates the customer's requirements
> being fulfilled, the SOW requirements being met, and the service
> elements that are being used.
>
> CSOC Interfaces - This section contains the CSOC/contractor interface
> requirements, roles, and responsibilities.
>
> SLA Database: The SLA database contains all preliminary and approved
> PSLAs and CSLAs/FSAs. The database shall generate SLA summary, cross
> reference, status, and metric reports.

13.4 [FORMAT:]{.underline} SLA Database - Offeror's proposal. CSLA/FSA
format - draft formats are provided in the RFP, Contractor format is
acceptable; Electronic availability and formatting as required by
Contracting Officer's letter. See Contracting Officer's letter BN-02-062
dated June 14, 2002.

13.5 [MAINTENANCE:]{.underline} SLA changes shall be incorporated by
change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DRD NO.]{.smallcaps}**: 2.3 **ISSUE:** Initial 2. **[DRL LINE
ITEM NO.]{.smallcaps}**:

3\. **[DATA TYPE]{.smallcaps}**: 1 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/2

6\. **[TITLE]{.smallcaps}**: Systems Engineering Plan

**[7. DESCRIPTION/USE]{.smallcaps}**: To describe the contractor's
implementation approach for providing end-to-end Mission and Data
service systems engineering.

8\. **[DISTRIBUTION:]{.smallcaps}** Hard copies and electronic
distribution availability and formatting as required by Contracting
Officer's letter.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Draft plan with proposal;
final version within 60 after end of phase-in.. The initial Operations
Concept submission within the draft systems engineering plan shall
contain the CSOC Operations Concept and define the interfaces with the
operations concepts of other SOMO elements. The initial submission shall
be structured and have the capability to add other SOMO Operations
Concepts after contract award.

10\. **SUBMISSION FREQUENCY:** As required.

11\. **REMARKS:** Refer to NMI 7120, Management of Major System Programs
and Projects; and DOD 5000.2, Defense Acquisition Program Procedures for
additional information on risk management plan contents.

12\. **INTERRELATIONSHIP:** SOW 2.3, 2.4, DRDs 2.3-a, 2.3-b, 2.3-c,
2-3-d

13\. **DATA PREPARATION INFORMATION:**

13.1 **[SCOPE]{.underline}**: The systems engineering plan is an
integrated plan describing the contractor's approach for:

-   Operations Concepts (CSOC and Other SOMO Ops Concepts))

-   generating and maintaining the standard services catalog

-   architecture baseline configuration management

-   spacecraft/service element trade-offs

-   integrating mission and data service systems

-   providing development integration services

13.2 **[APPLICABLE DOCUMENTS]{.underline}:** NMI 8074.1 Data Systems
Standards

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The Systems Engineering
Plan contains the contractor's systems engineering processes for
providing end-to-end mission and data services integration. The plan
also contains the contractor's processes for incorporating systems and
subsystems developed by other contractors or NASA, into the service
elements and for measuring the systems integration task success,
including evaluating customer satisfaction.

DRD 2.3 Page 2/2

**DRD Continuation Page **

The Systems Engineering Plan will contain the following sub-elements:

a)  **Operations Concepts** - Presents a phased operations philosophy
    that matches the evolution of the architecture. It should also
    include any innovation efforts necessary to enable the commercial
    practices incorporation, and any new development or technology
    insertion required to effect the selected operations concept.
    Additionally, it should discuss concepts for standardizing the
    following aspects, the Operations approaches, the architectural
    elements and processes, and the approaches associated with
    influences to spacecraft design.

b)  **Services Catalog Plan -** The Service catalog plan contains the
    processes associated with the service catalog development, service
    unit and cost determination, relationship to the architecture
    baseline, and configuration management. The Service Catalog shall
    contain and integrate CSOC services at contract award and other SOMO
    services post award.

c)  **Architecture Baseline Plan -** The architecture baseline plan
    contains the Space Operations architecture baseline development,
    standards, and maintenance approach. The Architecture Baseline shall
    contain and integrate CSOC and Other SOMO provided service elements.

d)  **Spacecraft/Service Element Trade-off Analysis Plan** - The
    spacecraft/service element trade-off analysis plan describes the
    contractor approach for spacecraft/service element trade-off
    analysis to include spacecraft solutions into the architecture
    baseline, standards to be used, and standard operating processes.
    The plan also includes the strategic plan for migrating spacecraft
    towards an integrated operations approach with service elements. The
    Spacecraft/Service Element Trade-off Analysis plan addresses:

-   future or spacecraft in phase A/B - preliminary analysis and
    definition

-   Spacecraft/Service elements in Phase C/D - design and development

-   Spacecraft/Service elements in phase E - operations

e)  **Advanced Technology Development Plan** - The advanced technology
    development plan will describe the contractor approach for advanced
    technology development and insertion into space operations.

f)  **Risk Management** - Present a structured, integrated risk
    management and abatement approach that correlates with the proposed
    integrated architecture evolution. The approach should address the
    risk sources, magnitude and mitigation, and actions directed toward
    its elimination or reduction to an acceptable level. The approach
    should take into account technical, programmatic, supportability,
    cost and schedule concerns for the solution implementation, and it
    should take into consideration impacts due to external influences,
    e.g., major schedule delays, NASA funding cuts, mission set
    adds/deletes. \[See Section 11, Remarks\]

The products for these sub-elements are defined in the following DRDs:

a.  Services Catalog

b.  Architecture Baseline

c.  Spacecraft/Service Element Trade-off Analysis Report

d.  Advanced Technology Development Report

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DRD NO.]{.smallcaps}**: 2.3-a **ISSUE:** Initial 2. **[DRL LINE
ITEM NO.]{.smallcaps}**:

3\. **[DATA TYPE]{.smallcaps}**: 1 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/2

6\. **[TITLE]{.smallcaps}**: Services Catalog

7\. **[DESCRIPTION/USE]{.smallcaps}**: The Service Catalog will serve
two purposes. First, it will provide a means to advertise Space
Operations capabilities to customers. Second, it will be a project
operations planning tool to evaluate operations requirements and their
associated implementation with cost estimates. The Service Catalog will
document the mission, data and center unique services

8\. **[DISTRIBUTION:]{.smallcaps}** Hard copies, electronic
availability, and formatting as required by Contracting Officer's
letter.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: The initial submission shall
contain the CSOC portion of the Service Catalog. The initial submission
shall be structured and have the capability to add the other SOMO
services after contract award. A draft Services Catalog shall be
submitted with the offeror's proposal. The final Services Catalog shall
be submitted 90 days after contract award.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Update Annually with the
POP process and as necessary to include updates from Other SOMO service
providers .

11\. **REMARKS:**

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.2, 2.3, 2.4

13\. **DATA PREPARATION INFORMATION:**

13.1 **[SCOPE]{.underline}**: The Services Catalog defines the detailed
services which the government and the contractor may provide to Space
Operations customers. The Services Catalog contains CSOC and other SOMO
provided services. The Service Catalog will be used by the government to
assist project planning activities and define the current and planned
space operations capabilities to potential customers.

13.2 **[APPLICABLE DOCUMENTS]{.underline}:** None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The Services Catalog will
contain all SOMO provided services (i.e. CSOC and non-CSOC provided
services). The Service Catalog shall provide both a customer view and
implementers view. The customer view will concentrate on the service
requirements and will not provide implementation details. The following
is an example to show the expected level of detail for a service list
consists of:

Mission Control - Telemetry Management:

-   Frame Service (at least one lower level would be required)

-   Packet Service (at least one lower level would be required)

-   Spacecraft health and safety monitoring

-   Payload/Instrument health and safety monitoring

    DRD 2.3-a Page 2/2

    **DRD Continuation Page **

    The customer view shall define the basic services and the standard
    options available within that service. The customer view will also
    contain packaged services which can provide turnkey solutions and
    packaged services which provide subsets of services which solve
    common problems. The implementers view provides more detailed
    service information used by the government and the contractor to
    determine the best solution to meet the user requirements (i.e.
    identifies which service elements provide this service and it's
    availability, unit cost, standards, constraints, and providing
    organization).

    The Service Catalog will contain at a minimum a detailed services
    list, service description, the service architecture, the nominal
    service performance level, service standards and constraints,
    service providing organization(s), service providing service
    element(s) and their availability, the service price per nominal
    performance level, points of contact to order services from, and the
    service ordering process.

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: The Service Catalog
will be updated within thirty days of a change to service units or unit
pricing. Changes shall be incorporated by change pages or complete
reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DRD NO.]{.smallcaps}**: 2.3-b **ISSUE:** Initial 2. **[DRL LINE
ITEM NO.]{.smallcaps}**:

3\. **[DATA TYPE]{.smallcaps}**: 1 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/2

6\. **[TITLE]{.smallcaps}**: Architecture Baseline

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe the Space Operations
Integrated Architecture that provides the space operations services and
manage it's planned evolution over time.

8\. **DISTRIBUTION:** Per Contracting Officer\'s letter; hard copies and
electronic availability and formatting as required by Contracting
Officer's letter.

9\. **INITIAL [SUBMISSION]{.smallcaps}**: The initial submission shall
contain the CSOC portion of the Architecture Baseline. The initial
submission shall be structured and have the capability to add the other
SOMO elements after contract award. The Architecture Baseline shall be
submitted at end of contract phase-in.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Update annually with
proposed changes at the Program Project Review (PPR). Final document 90
days after PPR.

11\. **REMARKS:** "Tool" is used as a broad term that can refer to any
custom or COTS software, hardware, or firmware, or a composition of
those elements that make up a system.

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.3, 2.4

13\. **DATA PREPARATION INFORMATION:**

13.1 **[SCOPE]{.underline}:** The Integrated Architecture baseline
defines the Space Operations architecture and is under configuration
management as described in the Systems Engineering plan. The
Architecture Baseline contains CSOC and other SOMO provided service
elements. Architecture configuration management includes facility
consolidation, architecture reuse/consolidation & integration, standards
implementation, and technology insertion.

13.2 **[APPLICABLE DOCUMENTS]{.underline}:**

13.3 **[CONTENTS]{.underline}:** The Architecture baseline will include,
at a minimum, the following:

-   service element evolution into a consolidated and integrated
    architecture which includes the integrated architectures interaction
    with spacecraft. This includes a functional level description for
    each evolution phase, a service elements cross-reference map
    containing present, intermediate steps, and final views.

-   spacecraft vs. ground system implementation tradeoff assessments
    functional area candidates

```{=html}
<!-- -->
```
-   high level service elements description and their customers

-   service elements functional designs

-   service elements key top level/driving functional requirements

-   external interface definition

-   standards in use and proposed future standards

-   relationships between architecture and services catalog

-   identify commercialized, outsourced, or privatized elements

-   identify "tool" consolidation (See Section #11, Remarks), automation
    and artificial intelligence

    **DATA REQUIREMENTS DESCRIPTION (DRD)**

    1\. **[DRD NO.]{.smallcaps}**: 2.3-c **ISSUE:** Initial 2. **[DRL
    LINE ITEM NO.]{.smallcaps}**:

    3\. **[DATA TYPE]{.smallcaps}**: Report Plan = 1 4. **[DATE
    REVISED]{.smallcaps}**:

    Report = 3 5. **[PAGE]{.smallcaps}**: 1/1

    6\. **[TITLE]{.smallcaps}**: Spacecraft/Service Element Trade-off
    Analysis Report Plan/Report

    7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe and report the
    contractor's approach for each spacecraft/service element trade-off
    analysis.

    8\. **[DISTRIBUTION:]{.smallcaps}** Per Contracting Officer\'s
    letter; hard copies and electronic availability and formatting as
    required by Contracting Officer's letter.

    9\. **[INITIAL SUBMISSION]{.smallcaps}**: An initial Spacecraft/
    Service Element Trade-off Analysis Report Plan shall be submitted 2
    weeks after Contracting Officers request.

    10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: The report shall be
    submitted and updated according to the approved Report Plan.

    11\. **REMARKS:**

    12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.3.1, DRD 2.3

    13\. **DATA PREPARATION INFORMATION:**

    13.1 **[SCOPE]{.underline}**: The Spacecraft/Service Element
    Trade-off Analysis Report Plan/Report documents the contractor's
    approach and results.

    13.2 **[APPLICABLE DOCUMENTS]{.underline}:** None

    13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The
    spacecraft/service element trade-off analysis Report Plan describes
    the report schedule and key assumptions.

    The spacecraft/service element trade-off analysis report will
    document the contractor's spacecraft operations lifecycle cost,
    spacecraft/service element trade-off analysis, and recommendations.
    This report shall contain the following:

```{=html}
<!-- -->
```
-   Assumptions/Guidelines/Groundrules

-   Draft PCDs (if required)

-   Standards to be used

-   Spacecraft/Service elements design and process trade-offs and
    lifecycle cost benefit analysis

-   Implementation plan (e.g. life cycle cost, schedule, content,
    approach)

-   Risk assessment

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DRD NO.]{.smallcaps}**: 2.3-d **ISSUE:** Initial 2. **[DRL LINE
ITEM NO.]{.smallcaps}**:

3\. **[DATA TYPE]{.smallcaps}**: 1 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Advanced Technology Development Report

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe the contractor's
technical achievements in supporting advanced technology development for
mission and data services.

8\. **[DISTRIBUTION:]{.smallcaps}** Per Contracting Officer\'s letter;
hard copies and electronic availability and formatting as required by
Contracting Officer's letter.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: An initial Advanced Technology
Development Report shall be submitted 30 days after task inception. A
final Advanced Technology Development Report shall be submitted 30 days
after task completion.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Updates every month during
the conduct of an Advanced Technology Development task .

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.3.3

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The Advanced Technology Development Report
defines the contractor's progress in supporting advanced technology
development tasks.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The Advanced Technology
Development Report will contain the contractor's technical achievements,
lessons learned, and suggestions for further investigation or
development.

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DRD NO.]{.smallcaps}**: 2.3.2 **ISSUE:** Initial 2. **[DRL LINE
ITEM NO.]{.smallcaps}**:

3\. **[DATA TYPE]{.smallcaps}**: 1 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1

6\. **[TITLE]{.smallcaps}**: Risk Management Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe the contractor's
implementation approach for performing and reporting risk management of
the Consolidated Space Operations Contract.

8\. **DISTRIBUTION:** Per Contracting Officer\'s letter; hard copies and
electronic availability and formatting as required by Contracting
Officer's letter.

9\. **INITIAL [SUBMISSION]{.smallcaps}**: The initial submission shall
contain the previously approved portions from related DRDs as re-stated
in paragraph 13. The Risk Management Plan shall be submitted by November
24, 1999.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Updates as necessary.

11\. **REMARKS:**

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.1, 2.2, 2.3, and 2.4

13\. **DATA PREPARATION INFORMATION:**

13.1 **[SCOPE]{.underline}:** The risk management plan defines the
contractor's method to accomplish proactive end-to-end risk analysis
management and abatement contract wide throughout CSOC. Risk management
includes risk:

13. identification

14. analysis

15. handling

16. mitigation

17. tracking

18. controlling

19. risk communication

13.2 **[APPLICABLE DOCUMENTS]{.underline}:**

13.3 **[CONTENTS]{.underline}:** Present a structured, integrated risk
management and abatement implementation approach that correlates with
the proposed integrated architecture evolution. The plan should address
the risk sources, magnitude and mitigation, and actions directed toward
its elimination or reduction to an acceptable level. The plan should
take into account technical, programmatic, supportability, cost and
schedule concerns for the solution implementation, and it should take
into consideration impacts due to external influences, e.g., major
schedule delays, NASA funding cuts, mission set adds/deletes. The plan
shall specify how the risks are documented, communicated, and reported
to the contractor and NASA management.

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

5.  **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
    incorporated by change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DRD NO.]{.smallcaps}**: 2.4.1.8 -a **ISSUE:** Initial 2. **[DRL
LINE ITEM NO.]{.smallcaps}**:

3\. **[DATA TYPE]{.smallcaps}**: Development Process Plans = 1 4.
**[DATE REVISED]{.smallcaps}**:

Development Products = 2 5. **[PAGE]{.smallcaps}**: 1/2

6\. **[TITLE]{.smallcaps}**: Development Process Plan and Products

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe the contractor's
process and deliverables for development.

8\. **[DISTRIBUTION:]{.smallcaps}** Per Contracting Officer\'s letter;
hard copies and electronic availability and formatting as required by
Contracting Officer's letter.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Development Plan - The initial
plan shall be submitted within 30 days of contract award. Development
Products - Per contractor's development plan

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Development Plan - As
required

Development Products - Per contractor's development plan

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.4.1.8; SOW 2.4.2.9

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The Development Process Plan will describe
the Contractor's approach for development of new mission and data
services capabilities and/or systems. The Development Products are
utilized to provide government insight into the development process. The
deliverables are provided by development task and are tailored for each
task , to provide the necessary processes, products, and review/reports
for the associated task.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: Requirements documents as
defined for each task, NMI 7120

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**:

The Development Process Plan should address, at a minimum:

-   Software/Hardware Development and Management Approach (COTS &
    custom)

-   Standards to be applied

-   Installation and Integration

-   Test and Verification

-   Configuration Management

-   Security Management

-   Risk Management

-   Reliability/Quality

-   Documentation

-   Products to be delivered

-   Ops Transition (Transition from the development phase to operations)

    The following is an example set of products to be delivered for a
    development project. The Development Process Plan should describe
    how products will be tailored for each project. The individual
    Project Commitment Documents (PCDs) DRD 2.4.1.8-b, should specify
    the products to be delivered for that project.

    DRD 2.4.1.4-a Page 2/2

    **DRD Continuation Page **

-   Products

-   Schedules/PMS

-   Test Procedures

-   Interface Control Documents (ICD's)

-   Requirements

-   As-Built Specifications

-   Operational Concepts

-   Hardware/software/firmware licensing agreements

-   Users/M&O Manuals

-   Software/Firmware source code

-   Hardware

-   Equipment Lists

-   Reports/Reviews

-   Functional Requirements Review/Report

-   Functional Design Review/Report

-   Final Acceptance Review/Report

-   Discrepancy Review/Report

-   Operations-ready product(s)

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
Electronic availability and formatting as required by Contracting
Officer's letter. See Contracting Officer's letter BN-02-062 dated June
14, 2002.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DRD NO.]{.smallcaps}**: 2.4.1.8-b **ISSUE:** Initial 2. **[DRL
LINE ITEM NO.]{.smallcaps}**:

3\. **[DATA TYPE]{.smallcaps}**: 1 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Project Commitment Document (PCD)

7\. **[DESCRIPTION/USE]{.smallcaps}**: The PCD provides the project plan
for project justification, commitment, and tracking through the project
life cycle or until the project capabilities are included into the
standard services catalog or service elements.

8\. **[DISTRIBUTION:]{.smallcaps}** Per Contracting Officer\'s letter;
hard copies and electronic availability and formatting as required by
Contracting Officer's letter.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: A draft PCD providing project
justification shall be submitted with each new significant task or
project request.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: A revised complete PCD
shall be provided 30 days prior to Make or Buy Decision Meeting. Further
updates shall be provided annually with Program Operating Plan and
significant funding changes.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.4.1.8, SOW 2.4.2.9

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

**[SCOPE]{.underline}**: The PCD defines the project justification,
strategy, and plans for major in-scope

projects and tasks. It is used initially to justify projects prior to
the Make or Buy decision process and during the Program Operating Plan
process. Then during the project or task's life cycle, it will be
updated annually to reflect programmatic changes and track project
progress. The level of detail is to be commensurate with the mission
criticality, associated risk & effort size.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: NMI 7120

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The PCD shall define what
the project objects/goals, schedule/need, and implementation approach.
As a minimum, the PCD shall contain:

-   Project justification/vision/goals

-   Top level requirements

-   Functional description

-   Project manager (Name/Center)

-   Implementation strategy

-   Schedule/major milestones

-   Recommended Government Insight (Project Metrics)

-   Prime implementer(s)

-   Life Costs - Project baseline and baseline log

-   Critical Issues/Risk Analysis

-   External Dependencies

-   Deliverables

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by PCD log entry with attachments/appendices if needed.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** 2.4.2.7 **ISSUE:** Initial 2. **DRL LINE ITEM NO.:**

3\. **DATA TYPE**: 3 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **[TITLE]{.smallcaps}**: Network and Service Utilization Data

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe the contractor's
collection and presentation of utilization data for the Space Flight
Tracking and Data Network (STDN), the Wallops Flight Facility (WFF)
Network, the Deep Space Network (DSN) and the NASA Integrated Services
Network (NISN).

8\. **[DISTRIBUTION:]{.smallcaps}** Per Contracting Officer\'s letter;
hard copies and electronic availability and formatting as required by
Contracting Officer's letter.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: 30 days after end of
phase-in..

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Utilization data updated
monthly within 3 calendar days of the end of the month.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.4.2.7

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: To capture the utilization of the STDN,
WFF Network, DSN and the NISN by customer on a monthly basis.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: The industry
telecommunications standards shall be adhered to as appropriate.

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: Contains utilization data
associated with the scheduled and actual use of the STDN, WFF Network,
DSN and NISN for each customer.

> For the STDN, WFF Network and the DSN, the data shall associate the
> quantity of support for each customer by resource used by calendar
> day.
>
> For the NISN, the data shall associate the amount of service usage for
> each customer by resource used on a monthly basis.

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** B.1.1 **ISSUE:** Initial 2. **DRL LINE ITEM NO.:**

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **[TITLE]{.smallcaps}**: GSFC Operations Readiness Review

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe the contractor's
operations readiness for a spacecraft launch, early orbit and
operational support, including nominal and contingency/emergency.

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: 90 - 120 days prior to the 1st
spacecraft launch supported by CSOC for GSFC, including WFF. 3 - 30 days
prior to local WFF operations supported by CSOC. 30 - 90 days prior to
field WFF operations supported by CSOC.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: 90 - 120 days prior to
every launch supported by CSOC for GSFC, including WFF. 3 - 30 days
prior to every local WFF operations support by CSOC. 30 - 90 days prior
to every field WFF operations supported by CSOC.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.4.1, CSLA B.1.1, CSLA
B.2.1

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The GSFC (including WFF) Operations
Readiness Review shall describe the operational readiness of all
facilities, personnel, procedures, hardware, firmware, software and
documentation required to support a specific launch.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: GSFC Project Management
Policy and the NASA System Engineering Handbook (SP-6105)

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The GSFC Operations
Readiness Review shall contain all information required to document the
operational readiness of all facilities, hardware, firmware, software,
personnel, and documentation to support missions. This GSFC Operations
Readiness Review shall contain status of: Operator Training and
Certification, Test Results, Discrepancy Reports, system development
RID's, I.T.S. Physical Security, and Facility readiness.

13.4 **[[FORMAT:]{.underline}]{.smallcaps}** Contractor Required Format
is acceptable; on-line availability required. See Contracting Officer's
letter BN-02-062 dated June 14, 2002.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: N/A

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** B.1.2 **ISSUE:** Initial 2. **DRL LINE ITEM NO.:**

3\. **DATA TYPE**: 1 4. **DATE REVISED**:

5\. **PAGE**: 1/1

6\. **[TITLE]{.smallcaps}**: JPL Readiness Review

7\. **[DESCRIPTION/USE]{.smallcaps}**: To report DSN and AMMOS readiness
to support a mission or a mission critical event to a Readiness Review
Board.

8\. **DISTRIBUTION:** Formatting and electronic distribution per
Contracting Officer's letter.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Five days before first
scheduled DSN and AMMOS Readiness Review Board meeting.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Five days before each
scheduled DSN and AMMOS Readiness Review Board meeting.

11\. **[REMARKS]{.smallcaps}**: The contractor will be notified fifteen
days before each scheduled DSN and AMMOS Readiness Review Board meeting.

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 2.4.1, 2.4.2, CSLA B.1.2,
CSLA B.2.2

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: To provide the contractors assessment of
the DSN and AMMOS readiness to support a mission.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The report give the
status of mission related personnel training and highlight any problems
and their corrective action. It shall also give the status of mission
related testing and highlight any system or subsystem problems and their
corrective actions. Any schedule conflicts should also be identified.
Finally, the report should state the contractors assessment of the DSN
and AMMOS readiness to support the mission.

13.4 **[FORMAT]{.underline}:** Contractor format is acceptable;
electronic format and availability as required by Contracting Officer's
letter. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: N/A

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: B.1.3-a ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: 2 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Certificate of Flight Readiness Endorsement

7.  DESCRIPTION/USE: To certify the completion or disposition of all
    contractor tasks and planned work required to prepare the ground
    systems (i.e., ground hardware and software; support facilities and
    equipment; and service operators) to safely support a specific
    mission in accordance with NSTS 08117 and SSP 50108.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION: First launch after contract award.

10. SUBMISSION FREQUENCY: Each Flight Readiness Review, approximately 14
    days prior to launch countdown Call-to-Station

11. REMARKS:

[]{.mark}

12. INTERRELATIONSHIP: SOW 2.4.1, FSA B.2.1.3

[]{.mark}

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} The Certificate of Flight Readiness
        Endorsement defines contractor's responsibilities as well as
        product and process status for certifying readiness for launch,
        mission and landing operations.

    2.  [APPLICABLE DOCUMENTS:]{.underline}

NSTS 08117 Certification of Flight Readiness Requirements

SSP 50108 Certification of Flight Readiness for Space Station

3.  [CONTENTS:]{.underline} Data shall include integrity metrics for all
    processes and products specified in the applicable documents, as
    well as necessary supporting data, required to satisfy the
    contractor's responsibilities and readiness to support the launch,
    mission and landing operations as defined in applicable documents.

4.  [FORMAT:]{.underline} In accordance with NSTS 08117 (Certificate of
    Flight Readiness Requirements) and SSP 50108 (Certification of
    Flight Readiness for Space Station). See Contracting Officer's
    letter Bn-02-062 dated June 14, 2002.

5.  [MAINTENANCE:]{.underline} N/A

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: B.1.3-b ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: Plan = 1 4. DATE REVISED:

Metrics = 2 5. PAGE: 1/1

6.  TITLE: Flight Operations Process Integrity Plan

7.  DESCRIPTION/USE: To define the health and stability of the processes
    and facilities defined in SOW 2.1, for Government insight into
    processes, and for determining audit requirements.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION: 30 days after contract award. The initial
    delivery of process integrity metrics shall be no later than 60 days
    after contract award, then shall continue monthly.

10. SUBMISSION FREQUENCY: Updates shall be made as new processes and
    projects require additional metrics. The metrics provided by this
    plan shall be provided monthly, no later than the 21st day of the
    calendar month following the end of the contractor's accounting
    period.

11. REMARKS:

12. INTERRELATIONSHIP: SOW 2.4.1, FSA B.2.1.3

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} The contractor shall provide and maintain
        process integrity metrics for all work involved in the flight
        operations processes. Special projects and tasks shall have
        process integrity metrics as agreed to between NASA and the
        contractor.

    2.  [APPLICABLE DOCUMENTS:]{.underline} None

    3.  [CONTENTS:]{.underline} Metrics shall include discrepancy report
        metrics, availability metrics, certification metrics, and any
        additional metrics that define the health and stability of the
        facilities defined in this SOW. Metrics shall support all
        performance measurements for required services included in this
        SOW.

> The Process Integrity Plan shall provide for objective evaluation
> criteria as agreed to between NASA and the contractor.

4.  [FORMAT:]{.underline} Contractor format is acceptable. See
    Contracting Officer's Letter BN-02-062 dated June 14, 2002.

5.  [MAINTENANCE:]{.underline} Changes shall be incorporated as required
    by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: B.1.4 ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: 2 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Payload Flight Readiness Reports

7.  DESCRIPTION/USE: To report the contractor's flight readiness status
    for Payload Operations.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION: First readiness review after contract
    initiation.

10. SUBMISSION FREQUENCY: Five days prior to each scheduled support
    readiness review.

11. REMARKS:

12. INTERRELATIONSHIP: SOW 2.4.1, FSA B.2.1.4

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} The report shall provide visibility and
        commitment of the readiness of the hardware, software, and
        support personnel to support a test, simulation, or mission.

    2.  [APPLICABLE DOCUMENTS:]{.underline} MSFC configuration
        management procedures.

    3.  [CONTENTS:]{.underline} The contractor shall provide readiness
        reports to Payload Readiness Review Boards or Critical Review
        Boards which are responsible for assessing MOL readiness and
        flight operations. The readiness status shall include
        accomplished level of training, completeness of testing, and the
        readiness status of hardware and software systems necessary for
        the mission support function. Status of major anomalies
        discovered during testing, training, or operations activities
        shall be provided along with any necessary restrictions or
        work-around.

13.4 FORMAT: Contractor format is acceptable; electronic format and
availability as required by Contracting Officer's letter. See
Contracting Officer's letter BN-02-062 dated June 14, 2002.

13.5 MAINTENANCE: N/A

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: B.1.5.a-a ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: 1 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: KSC Readiness Review

7.  DESCRIPTION/USE: To report CLCS readiness to support a test or a
    mission critical event to a Readiness Review Board.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION: Daily for routine testing and Five days before
    first scheduled Readiness Review Board meeting for Critical
    Integrated test and launch.

10. SUBMISSION FREQUENCY: Daily for routine testing and Five days before
    first scheduled Readiness Review Board meeting for Critical
    Integrated test and launch.

11. REMARKS: Daily test support formality will be minimal and an
    appropriate readiness documentation mechanism will be established
    between the CSOC and KSC personnel at the time of option execution.

12. INTERRELATIONSHIP: SOW 2.4.1, FSA B.2.5.1

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} To provide the contractor's assessment of
        the CLCS readiness to support a test or mission.

    2.  [APPLICABLE DOCUMENTS:]{.underline} None

    3.  [CONTENTS:]{.underline} The report give the status of CLCS
        related hardware, software network and interface subsystems and
        systems, including personnel support issues and Shuttle Data
        Center and simulation supporting elements. Any schedule
        conflicts should also be identified. Finally, the readiness
        report should state the contractor's assessment of CLCS
        readiness to support the test or mission.

    4.  [FORMAT:]{.underline} Contractor format is acceptable;
        electronic format and availability as required by Contracting
        Officer's letter. See Contracting Officer's letter BN-02-062
        dated June 14, 2002.

13.5 [MAINTENANCE:]{.underline} N/A

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** B.1.5.a-b **ISSUE:** Initial 2. **DRD LINE ITEM NO.:**

3\. **DRD TYPE:** 2 4. **DATE REVISED:**

5\. **PAGE:** 1/1

6.  **TITLE:** CLCS performance data

7.  **DESCRIPTION/USE:** To evaluate the performance of the CLCS system,
    as well as identify hardware reliability trending information.

8.  **DISTRIBUTION:** Formatting and electronic distribution per
    Contracting Officer's letter.

9.  **INITIAL SUBMISSION:** First launch after option execution

10. **SUBMISSION FREQUENCY:** Each Flight Readiness Review,
    approximately 14 days prior to launch countdown Call-to-Station

11. **REMARKS:**

12. **INTERRELATIONSHIP:** SOW 2.4.1, **FSA B.2.5.1**

13. **DATA PREPARATION INFORMATION**:

    1.  **[SCOPE:]{.underline}** This report will cover all CLCS
        subsystems and software elements.

    2.  **[APPLICABLE DOCUMENTS:]{.underline}** None

    3.  **[CONTENTS:]{.underline}** Data shall be provide which
        characterizes the CLCS system performance in acquiring
        measurements, processing commands and control messages, and
        recording test data. Included in this report should be
        identification of all hardware and software problems and their
        status and impacts, error rate data throughout the system,
        failure rate information for subsystem components,
        mean-time-to-repair times, and set usage statistics.

    4.  **[FORMAT:]{.underline}** Contractor format is acceptable;
        electronic format and availability as required by Contracting
        Officer's letter. See Contracting Officer's letter Bn-02-062
        dated June 14, 2002.

**13.5 [MAINTENANCE:]{.underline}** N/A

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: B.2.2-a ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: 1 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: DSN Network Operations Plan

7.  DESCRIPTION/USE: Documents the planning data, configurations, and
    procedures necessary to support each mission that are used by
    personnel providing operational support.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION: 180 calendar days prior to the first mission
    launch.

10. SUBMISSION FREQUENCY: 180 calendar days prior to each launch. A
    revised document is to be submitted whenever there is a major
    addition or deletion. Updated as required through end of mission.

11. REMARKS: Revisions may be submitted via electronic media with hard
    copy to follow.

12. INTERRELATIONSHIP: SOW 2.4.1, FSA B.2.2.3

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} This report is to cover all operational
        elements of the DSN, including the overseas tracking stations
        located in Canberra and Madrid.

    2.  [APPLICABLE DOCUMENTS:]{.underline} Detailed Mission
        Requirements (DMR) document.

    3.  [CONTENTS:]{.underline} Mission description, mission unique
        system configurations, procedures and training plans.

    4.  [FORMAT:]{.underline} Contractor format is acceptable;
        electronic format and availability as required by Contracting
        Officer's letter. See Contracting Officer's letter dated June
        14, 2002.

    5.  [MAINTENANCE:]{.underline} Changes shall be incorporated by
        change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: B.2.2-b ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: 1 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: DSN Initial Acquisition Plan

7.  DESCRIPTION/USE: Documents the planning data and procedures
    necessary to perform the initial acquisition of a spacecraft by the
    tracking stations in the DSN. It is used by persons providing
    operational support.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION:

> Earth Orbiter Missions:

a.  Preliminary plan 60 calendar days prior to the first mission launch.

b.  Final plan 30 calendar days prior to the first mission launch.

> Deep Space Missions:
>
> a\) Preliminary plan 90 calendar days prior to the first mission
> launch.
>
> b\) Final plan 60 calendar days prior to the first mission launch.

10. SUBMISSION FREQUENCY:

> Earth Orbiter Missions:

a.  Preliminary plan 60 calendar days prior to each mission launch.

b.  Final plan 30 calendar days prior to each mission launch.

> Deep Space Missions:
>
> a\) Preliminary plan 90 calendar days prior to each mission launch.
>
> b\) Final plan 60 calendar days prior to each mission launch.

11. REMARKS: Revisions may be submitted via electronic media with hard
    copy to follow.

12. INTERRELATIONSHIP: SOW 2.4.1, FSA B.2.2.3

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} The document shall include all operational
        elements of the DSN, including the overseas tracking stations
        located in Canberra and Madrid.

    2.  [APPLICABLE DOCUMENTS:]{.underline} Detailed Mission
        Requirements (DMR) document.

    3.  [CONTENTS:]{.underline} This document shall contain the time
        sequence of events for the initial acquisition of the
        spacecraft, as well as an analysis and supporting data link
        margins based on spacecraft and ground station capabilities. It
        should also include nominal and contingency plans and procedures
        for launch and early orbit phases.

    4.  [FORMAT:]{.underline} Contractor format is acceptable;
        electronic format and availability as required by Contracting
        Officer's letter. See Contracting Officer's letter BN-02-062
        dated June 14, 2002.

    5.  [MAINTENANCE:]{.underline} Revised whenever there is a
        significant addition or deletion.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: B.2.4 ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: NISN Readiness Reports

7.  DESCRIPTION/USE: To report the contractor's network and services
    readiness status for NISN.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION: First readiness review after contract
    initiation.

10. SUBMISSION FREQUENCY: Five days prior to each scheduled support
    readiness review.

11. REMARKS:

12. INTERRELATIONSHIP: SOW 2.4.2, FSA B.2.2.4

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} The report shall provide visibility and
        commitment of the readiness of the network, services, and
        support personnel to support a test, simulation, or mission.

    2.  [APPLICABLE DOCUMENTS:]{.underline} MSFC configuration
        management procedures, and 542-006-V1 and V2 NASA Communications
        Operating Procedures (NASCOP Vol. I and Vol. II)

    3.  [CONTENTS:]{.underline} The contractor shall provide readiness
        reports to NISN Configuration Control Board, which is
        responsible for the network and service readiness status. The
        readiness status shall include accomplished level of training
        and completeness of testing. Status of major anomalies
        discovered during testing, training, or operations activities
        shall be provided along with necessary restrictions or
        work-around.

    4.  [FORMAT:]{.underline} Contractor format is acceptable;
        electronic format and availability as required by Contracting
        Officer's letter. See Contracting Officer's letter BN-02-062
        dated June 14, 2002.

13.5 [MAINTENANCE:]{.underline} N/A

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: B.2.5 ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: 1 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: ELV Telemetry Station Support Operations Readiness Review

7.  DESCRIPTION/USE: To describe the contractor's operations readiness
    to support expendable launch vehicle pre launch tests and launches
    at CCAS and VAFB.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION: 15 - 30 days prior to each ELV launch supported
    by CSOC for KSC (including VAFB launches).

10. SUBMISSION FREQUENCY: 15 - 30 days prior to every launch supported
    by CSOC for KSC (including VAFB launches).

11. REMARKS:

12. INTERRELATIONSHIP: SOW 2.4.2, FSA B.2.5

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} The KSC (including VAFB) Operations
        Readiness Review shall describe the operational readiness of all
        assigned facilities, personnel, procedures, hardware, firmware,
        software, and documentation required to support a specific ELV
        launch.

    2.  [APPLICABLE DOCUMENTS:]{.underline} NASA Systems Engineering
        Handbook (SP-6105)

    3.  [CONTENTS:]{.underline} The KSC Operations Readiness Review
        shall contain all information required to document the
        operational readiness of all assigned facilities, hardware,
        firmware, software, personnel, and documentation to support ELV
        missions.

    4.  [FORMAT:]{.underline} Contractor format is acceptable; on-line
        availability required. See Contracting Officer's letter
        BN-02-062 dated June 14, 2002.

13.5 [MAINTENANCE:]{.underline} N/A

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **DRD NO.:** B.3.5 **ISSUE:** Initial 2. **DRD LINE ITEM NO.:**

3\. **DRD TYPE:** 1 4. **DATE REVISED:**

5\. **PAGE:** 1/1

6.  **TITLE:** KSC Communications Operational Readiness Review

7.  **DESCRIPTION/USE:** To describe the contractor's operations
    readiness for KSC Ground Support communications systems to support
    launch and landing functions. Including nominal and
    contingency/emergency.

8.  **DISTRIBUTION:** Formatting and electronic distribution per
    Contracting Officer's letter.

9.  **INITIAL SUBMISSION:** 45 days prior to the 1st launch supported by
    CSOC.

10. **SUBMISSION FREQUENCY:** Three working days prior to each KSC
    Ground Support Readiness Review meeting. KSC Ground Support
    Readiness Review meetings are held approximately 10 days prior to
    launch countdown Call-to-Station

11. **REMARKS:**

12. **INTERRELATIONSHIP:** SOW 2.4.2, **FSA B.2.3.5**

13. **DATA PREPARATION INFORMATION**:

    1.  **[SCOPE:]{.underline}** The KSC Communications Operational
        Readiness Review shall describe the operational readiness of all
        facilities, personnel, procedures, hardware, firmware, software,
        and documentation required to support a specific launch.

    2.  **[APPLICABLE DOCUMENTS:]{.underline}**

> NSTS 08117 Certification of Flight Readiness Requirements
>
> SSP 50108 Certification of Flight Readiness for Space Station

3.  **[CONTENTS:]{.underline}** The KSC Communications Operational
    Readiness Review shall contain all information required to document
    the operational readiness of all facilities, hardware, firmware,
    software, personnel, and documentation to support KSC launch and
    landing services. KSC Communications Operational Readiness Review
    shall contain status of: Operator Training and Certification, System
    Validation Results, Discrepancy Reports, Open Work, Corrective
    Actions, I.T.S. Physical Security, and Facility readiness.

4.  **[FORMAT:]{.underline}** Contractor format is acceptable; on-line
    availability required. See Contracting Officer's letter BN-02-062
    dated June 14, 2002.

**13.5 [MAINTENANCE:]{.underline}** N/A

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: B.3.5-b ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: 2 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: KSC Communications System Documentation

7.  DESCRIPTION/USE: To describe the current configuration, operational
    procedures and readiness for all KSC Ground Support communications
    systems to support processing, launch, and administrative functions,
    including nominal and contingency/emergency.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION: Current drawings and documentation to be CSOC
    responsibility from the first date of KSC support.

10. SUBMISSION FREQUENCY: To be complete and current at all times
    showing current system configuration and operational configurations
    as applicable. Drawing packages and operational procedures to be
    completed and approved prior to initiating any system change or
    addition.

11. REMARKS:

12. INTERRELATIONSHIP: SOW 2.4.2, FSA B.3.5

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} KSC Communications System Documentation
        shall describe the configuration of all facilities, procedures,
        hardware, firmware, software, and documentation required to
        support a specific launch or routine activities.

    2.  [APPLICABLE DOCUMENTS:]{.underline}

> GP-435 Vol. 1 & 2: Engineering Drawing Practices
>
> KSC-DF-107: DE Technical Document Style Guide

3.  [CONTENTS:]{.underline} KSC Communications System Documentation
    shall describe the configuration of all facilities, procedures,
    hardware, firmware, software, and documentation required to support
    a specific launch or routine activities. KSC Communications System
    Documentation shall contain: top level system functional block
    diagrams, detailed functional system configuration, facility
    configurations, physical diagrams including part numbers as
    applicable, and operational configurations and schedules as
    applicable for systems which have dynamic configurations per
    operational requirements.

4.  [FORMAT:]{.underline} Drawings to meet KSC standards, for other
    support documents Contractor required format is acceptable; on-line
    availability required. See Contracting Officer's letter BN-02-062
    dated June 14, 2002.

13.5 [MAINTENANCE:]{.underline} Continuous

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DRD NO.: B.3.5-c ISSUE: Initial 2. DRD LINE ITEM NO.:

3\. DRD TYPE: 2 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: KSC Communications System Maintenance Documentation

7.  DESCRIPTION/USE: To describe the current maintenance schedule,
    maintenance procedures, and CSOC maintenance performance metrics for
    all KSC Ground Support communications systems that support
    processing, launch, landing, and administrative functions, including
    nominal and contingency/emergency.

8.  DISTRIBUTION: Formatting and electronic distribution per Contracting
    Officer's letter.

9.  INITIAL SUBMISSION: Current maintenance documentation shall be the
    CSOC responsibility from the first date of KSC support. New
    documents shall be initially submitted within 60 calendar days from
    the start of KSC CSOC support.

10. SUBMISSION FREQUENCY: Maintenance procedures and schedules shall be
    submitted yearly. Performance status reports shall be submitted
    monthly.

11. REMARKS:

12. INTERRELATIONSHIP: SOW 2.4.2, FSA B.2.3.5

13. DATA PREPARATION INFORMATION:

    1.  [SCOPE:]{.underline} KSC Communications System Maintenance
        Documentation shall describe the current maintenance schedule,
        maintenance procedures and CSOC maintenance performance metrics
        for all KSC Ground Support communications systems that support
        processing, launch, landing, and administrative functions,
        including nominal and contingency/emergency.

    2.  [APPLICABLE DOCUMENTS:]{.underline}

> Original Equipment Manufacturer (OEM) documentation

3.  [CONTENTS:]{.underline} Yearly KSC Communications System Maintenance
    Documentation shall describe the maintenance schedule and
    maintenance procedures of all facilities, hardware, firmware,
    software, and documentation for KSC communication systems. Yearly
    KSC Communications System Maintenance Documentation shall contain:
    top level system functional block diagrams, equipment listings,
    maintenance requirements per item, planned maintenance schedule,
    maintenance procedures and migration path for functionally or
    technically obsolete equipment. Monthly KSC Communications System
    Maintenance Documentation shall contain detailed status as to the
    current maintenance performance level of CSOC, enumerated shortfalls
    with corrective action plans included, special
    occurrences/situations, and system or element migration status.

4.  [FORMAT:]{.underline} Contractor Required Format is acceptable;
    on-line availability required. See Contracting Officer's letter
    BN-02-062 dated June 14, 2002.

5.  [MAINTENANCE:]{.underline} Maintenance plan shall be revised
    annually. All maintenance status reports shall be updated monthly.

<table style="width:100%;">
<colgroup>
<col style="width: 30%" />
<col style="width: 5%" />
<col style="width: 2%" />
<col style="width: 11%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 2%" />
<col style="width: 11%" />
<col style="width: 6%" />
<col style="width: 2%" />
<col style="width: 23%" />
</colgroup>
<tbody>
<tr class="odd">
<td><ol type="I">
<li><p>DRD Title</p></li>
</ol>
<p>SA-1-1, Safety and Health Plan</p></td>
<td colspan="4">2. Current Version Date</td>
<td colspan="3">3. DRL Line Item No.</td>
<td colspan="3">RFP/Contract No. (Procurement completes)</td>
</tr>
<tr class="even">
<td></td>
<td colspan="4"><p>4/01 (replaces</p>
<p>1/01 version)</p></td>
<td colspan="3"></td>
<td colspan="3"></td>
</tr>
<tr class="odd">
<td colspan="11">4. Use (Define need for, intended use of, and/or
anticipated results of data)</td>
</tr>
<tr class="even">
<td colspan="11"><p>Establishes Safety, Health, and Environmental
Compliance Plan for contractors providing support to JSC
organizations</p>
<p>***The Office of Primary Responsibility for this DRD is the JSC
Safety, Reliability, and Quality Assurance Office</p></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2">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="odd">
<td colspan="2"></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td></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">NPG 8715.3 (as revised); JPG 1700.1 (as revised)</td>
<td colspan="7">See block 8. below</td>
</tr>
<tr class="even">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

[NOTE: UPON NASA APPROVAL, THE CONTRACTOR'S SAFETY, HEALTH, and
ENVIRONMENTAL COMPLIANCE PLAN (\"The Plan\") BECOMES A CONTRACTUAL
REQUIREMENT.]{.underline}

[Frequency of submission]{.underline}. One time only (with the
proposal).

[Distribution.]{.underline} After the 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:

NS/Safety and Test Operations Division (2 copies)

SD26/Occupational Health Officer (1 copy)

JA131 / Environmental Services (1 copy)

Contracting Officer's technical Representative (1 copy)

[Subsequent revisions to the plan.]{.underline} 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.

[Other deliverables.]{.underline} 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 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; JSC Occupational Safety Branch; and the NASA Contracting
    Officer. Other signatures may be required at the discretion of the
    Government.

2.  Table of Contents. See content below.

3.  Body of plan - as required. Contractor's format is acceptable but
    should be traceable to the elements of the content below.

4.  When preparing its 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-1 through -5, -10; NFS 18-23.70, 18-52.223-70,
    18-52.223-73.

6\. See Contracting Officer's letter BN-02-062 dated June 14, 2002.

[Content:]{.underline}

I.  **[Management Leadership and Employee Participation.]{.smallcaps}**

    A.  Policy. Provide the contractor's safety, health, and
        environmental compliance policy statement with the plan. Compare
        the contractor's policy statement with those of NASA and OSHA
        and discuss any differences.

    B.  Goals and Objectives.

        1.  Describe specific safety and health 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 to continuous
            improvement** (including milestone schedule) using level 5
            of the Performance Evaluation Profile **as a guideline**.

        2.  Describe Environmental Goals & Objectives to be met for the
            following:

            a.  Pollution Prevention and Source Reduction of:

                1.  Hazardous and Industrial Solid Wastes

                2.  Solid Wastes (trash, refuse)

                3.  Wastewater Discharges (sanitary sewerage)

                4.  Air Emissions

                5.  Medical & Radiological Discharges

            b.  Affirmative Procurement (Purchase of Environmentally
                Preferable Materials IAW Executive Order)

            c.  Hazardous Materials
                Handling/Purchasing/Reduction/Replacement

            d.  Elimination from Specifications and Standards
                requirements for the use of Hazardous/Toxic Substances &
                Materials

            e.  Use of an Environmental Planning Checklist to review &
                document Impacts of New and Modified Programs, Projects,
                Activities and Operations.

            f.  Life cycle analysis and costing

            g.  Incorporating Environmental Requirements in Subcontracts

            h.  Participation in JSC Recycling

            i.  Outreach programs

    C.  Management Leadership. Describe management's procedures for
        implementing its commitment to safety, health, and environmental
        compliance 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.

    D.  Employee Involvement. Describe procedures to promote and
        implement employee (e.g., non-supervisory) involvement in
        safety, health, and environmental compliance 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.

    E.  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:

        1.  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.

2\. Company Physician/Occupational Injury/illness case manager -
identify a point of contact who is responsible for the transfer or
receipt of company medical data and who will be the primary contact for
the company in the event any employee suffers a work related injury or
illness (such as the company physician) by name, address, and telephone
number to the JSC Clinic, mail code SD22. This will facilitate
communication of medical data to contractor management. Prompt
notification to the JSC Occupational Health/ Clinic shall be given of
any changes that occur in the identity of the point of contact. **A
letter to the JSC Occupational Health Office can accomplish initial
identification of point of contact and subsequent updates with a copy
sent to the Contracting Officer. The initial letter is to be received by
the Government prior to contract start.**

3.  Building Fire Wardens - provide a roster of fire wardens (their
    names, phone numbers and pagers, and mail codes). Contractor fire
    wardens are needed 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. Fire wardens will be trained in accordance with JPG
    1700.1. **The roster shall be maintained by letter to the Safety and
    Test Operations Office, mail code NS2, with copies to the
    Contracting Officer and Contracting Officer\'s Technical
    Representative. The initial letter shall be received by the
    Government not later than 15 days after contract start.**

4.  Designated Safety Official - identify by title the official(s)
    responsible for implementation of this plan and all formal contacts
    with regulatory agencies and with NASA.

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

    B.  Accountability. Describe procedures for ensuring that management
        and employees will be held accountable for implementing their
        tasks in a safe and healthful and environmentally compliant
        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.

    C.  Program Evaluation. The program evaluation consists of:

        1.  Participation in a Performance Evaluation Profile (PEP)
            survey at the request of the Government. The PEP survey
            normally will be scheduled and administered at the
            discretion of the Government. **If the Government chooses
            not to do the PEP in a given year, the contractor may at its
            option initiate its own PEP by contacting the Safety and
            Test Operations Office, code NS2, for assistance. The
            contractor will not be required to take two or more PEP
            surveys in any contract year.**

        2.  Monthly statistical information. The contractor shall
            prepare and deliver monthly statistical information as
            specified on JSC Form 288, "Statistical Information -
            Contractor Safety and Health Program", as revised**, or
            other approved report.** Negative reports are also required
            monthly. Report due date is the 10^th^ day of the month
            following each month reported. Report to be delivered to the
            JSC Safety, Reliability, and Quality Assurance Office
            through the Safety and Test Operations Office, NS2, by fax
            to 281-483-3801 or electronically as instructed by
            representatives of the Occupational Safety Branch.

        3.  A written self-evaluation report to be delivered by Sept 30
            of each year. The self-evaluation shall follow the VPP
            program evaluation report format found in OSHA TED 8.1,
            Revised Voluntary Protection Programs (VPP) Policies and
            Procedures Manual, Appendix H, \"Format for Program
            Evaluation Report\", **as mandated by the cognizant OSHA
            regional office. Contractors who have submitted a written
            self-evaluation as a VPP site may submit their original
            report to OSHA in lieu of writing a new self -evaluation
            provided that all action plans and status are updated. The
            self evaluation shall as a minimum cover the elements of the
            approved safety and health plan.**

        4.  Miscellaneous Reports. 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 SD13, 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, 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", EPA "Emergency Planning and Community Right-to-Know
> (EPCRA, ref. 40 CFR 302, 311, 312); and the Texas Department of Health
> (TDH, ref. Chapters 505-507 of the Health and Safety Code), 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, Occupational Health and Test Support, Mail
> Code
>
> SD13, 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.

a)  [Hazardous Materials Inventory]{.underline}. The contractor shall
    compile an inventory report of all hazardous materials it has
    located on Government property not less than annually, 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 and instructions for delivery will be issued by the
    JSC Occupational Health and Test Support Office, mail code SD13.
    This information shall use the format used by JSC for chemical
    inventory compilation to provide the following:

    1.  the identity of the material;

    2.  the location of the material by building and room;

    3.  the quantity of each material normally kept at each location

    4.  peak quantity stored

    5.  actual or estimated rate of annual usage of each chemical

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.)

    A.  Government Access to Safety and Health Program Documentation.
        The contractor shall recognize in its plan that it will be
        expected to make all safety, health, and environmental
        documentation (including relevant personnel records) available
        for inspection or audit at the Government's request. Electronic
        access by the Government to this data is preferred as long as
        Privacy Act requirements are met and Government safety and
        health professionals and their representatives have full and
        unimpeded access for review and audit purposes. For contractor
        activities conducted on NASA property, the contractor will
        identify what records it will make available to the Government
        in accordance with the Voluntary Protection Program criteria of
        OSHA as implemented in JPG 1700.1, "JSC Safety and Health
        Handbook", as revised. For the purpose of this plan, safety,
        health, and environmental compliance 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.

    B.  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.

    C.  Procurement. Identify procedures used to assure that
        procurements are reviewed for safety, health and environmental
        compliance 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.

    D.  Certified Professional Resources. Discuss your access to
        certified professional resources for safety, health, and
        environmental protection. Discuss their roles in
        motivation/awareness, worksite analysis, hazard prevention and
        control, and training.

**[II. Worksite Analysis.]{.smallcaps}** 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 on hazardous substance 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 Occupational Safety Office. All safety
engineering products that address

> operations, equipment, etc., on NASA property will be subject to JSC
> SR&QA review and concurrence unless otherwise waived by the JSC
> Occupational Safety Office.

A.  Industrial Hygiene. Describe your industrial hygiene program and how
    it will be coordinated with the JSC government provided resources
    for industrial hygiene. In the event corporate resources are used to
    determine workplace exposures, copies of all monitoring data shall
    be provided to JSC Occupational Health within 15 days of receipt of
    results.

B.  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 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:

    1.  Comprehensive Survey -- A "wall to wall" engineering assessment
        of the work site including facilities, equipment, processes, and
        materials (including wastes -- (TNRCC/EPA solid & hazardous,
        radioactive, explosives, medical-infectious-biological)).

    2.  Change (Pre-use) 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.

    3.  Hazard Analysis -- may address facilities, systems/subsystems,
        operations, processes, materials (including waste), and specific
        tasks or jobs. Analyses and report formats will be in accordance
        with JSC 17773, \"Preparing of Hazard Analyses for JSC Ground
        Operations.\"

C.  Inspections.

    1.  Routine 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.  Protective Equipment. Set forth procedures for obtaining,
        inspecting, and maintaining all appropriate protective
        equipment, as required, or reference written procedure
        pertaining to this subject. Set forth methods for keeping
        records of such inspections and maintenance programs.

D.  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.

E.  Accident and Record Analysis[.]{.smallcaps}

    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 JSC Occupational
        Safety Branch, mail code NT2. 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.

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:

**[III. Hazard Prevention and Control.]{.smallcaps}** 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.

A.  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.

B.  Hazardous Operations and Processes. Establish methods for
    notification of personnel when hazardous operations and processes
    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; 29 CFR 1910.119 will be the guide for
    hazardous processes. Develop and maintain a list of hazardous
    operations and processes to be performed during the life of this
    contract. The list of hazardous operations and processes will be
    provided to JSC as part of the plan for review and approval. JSC and
    the Contractor will decide jointly which operations and processes
    are to be considered hazardous, with JSC as the final authority.
    Before hazardous operations or processes commence, the Contractor
    will develop a schedule to develop written procedures with
    particular emphasis on identifying the job safety steps required.
    NASA will have access on request to any contractor data necessary to
    verify implementation. For all identified operations or processes
    that may have safety or health implications outside contract
    operations, the contractor shall identify such circumstances to the
    JSC Occupational Safety Branch and Occupational Health and Test
    Support Office who will provide additional instructions for further
    NASA management review and approval.

C.  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.

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

E.  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.

F.  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.

G.  Environmental Operations & Activities

    1.  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 that occur on site at JSC,
        SCTF, 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 operations,
        equipment, systems, or activities generating new hazardous
        wastes or where the chemicals change or there are volume
        increases of 25% or more on site at JSC, SCTF, or Ellington
        Field.

2\. 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 JA131. Set forth a plan of procedures to
conduct pollution prevention, waste minimization or source
reduction/elimination of environmental pollution. Address management and
continuous improvement for the reduction 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 , EPA, , GSA, and Executive Order
> recycled content / affirmative procurement purchases . The
> JA131/Environmental Office is the single point of contact for
> coordinating all JSC environmental permits Emphasis shall be placed on
> providing for sufficient lead time for processing permits through the
> appropriate state agency and/or the Environmental Protection Agency.

H.  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 plan
    approved by NASA or as required by Government direction.

I.  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).

J.  Medical (Occupational Healthcare) Program. Discuss your medical
    surveillance program and injury /illness case management 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 , return to work policies and
    the use of government provided medical and emergency facilities for
    the initial treatment of occupational injuries/illnesses.

K.  Hazard Correction and Tracking. Discuss your system for correcting
    and tracking safety, health, and environmental hazards with
    particular emphasis on integration with JSC\'s Hazard Abatement
    Process (found online at
    [http://wwwsrqa.jsc.nasa.gov/HATS]{.underline}/). **(The scope is
    restricted to establishments at JSC, Sonny Carter Training Facility,
    and Ellington Field.)** This includes the following:

    1.  Personnel awareness of hazards. Discuss your approach to
        communicate unsafe conditions and approved countermeasures to
        your employees. Discuss your approach to communicating such
        conditions to the Government and other contractors whose
        personnel may be exposed to such unsafe conditions. Discuss
        communications with facility managers. Discuss use of the NASA
        Lessons Learned Information System for both obtaining lessons
        from other sources and as a repository for lessons learned
        during performance of the contract.

    2.  Interim and Final Abatement Plans. Describe how you will
        approach interim and final abatement of hazards. Describe how
        you will provide data to the JSC Hazard Abatement Tracking
        System for all hazards that are not finally abated (all interim
        and final abatement actions completed) within 30 days of
        discovery. Discuss your approach to posting such plans using JSC
        Form 1240, \"JSC Notice of Safety or Health Hazard and Action
        Plan\", or equivalent. Discuss compatibility of your system with
        JSC\'s the role of facility managers in abatement planning,
        implementation, and verification.

L.  Disciplinary System. Describe your system for ensuring safety and
    health discipline in your personnel (including subcontractors).
    Describe your approach to modifying personnel behaviors when
    personnel are exhibiting discrepant safety and health performance.

M.  Emergency Preparedness. Discuss approach to emergency preparedness
    and contingency planning which addresses fire, explosion, inclement
    weather, environmental spill /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.

**[IV. Safety and Health Training.]{.smallcaps}** 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 for
protective and/or emergency countermeasures, including training to meet
federal, state, and local regulatory requirements. In doing so, the
contractor will factor parallel requirements found in other mandates
such as environmental protection \[example: 29 CFR 1910.38 for emergency
action plans and fire prevention plans versus EPA Resource Conservation
& Recovery Act (RCRA) for Emergency Planning and Community Right-to-know
(EPCRA).\] Describe approach to identifying training needs including
traceability to exercises such as job safety analyses, performance
evaluation profiles, hazard analyses, mishap investigations, trend
analyses, etc. Describe approach to training personnel in the proper use
and care of protective equipment (PPE). 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 (examples include physical
examination, testing, and on-the-job

performance). Address utilization of JSC safety and health 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. All training
materials and training records will be provided to NASA, and other
federal, State, and local agencies for their review upon request. If the
contractor wishes to train their personnel in any regulatory mandated
training, an agreement will be secured with JSC Occupational Safety
Branch and Occupational Health and Test Support office prior to
beginning training. The agreement will ensure that safety and health
training resources available from NASA are utilized where appropriate
and to ensure that contractor-supplied training is in agreement with JSC
safety and health processes.

**JSC DATA REQUIREMENTS DESCRIPTION (DRD)**

(Based on JSC STD-123)

  ----------------------- -- ----------- ----------- -------------------- -- ---------------- -------- --- ------- -------------------
  1\. DRD Title                          2\. Current                                          3\. DRL              RFP/Contract No.
                                         Version                                              Line                 (Procurement
                                         Date                                                 Item No.             completes)

  Safety and Health                      04/01                                                SA-1-3               
  Program Self Evaluation                (replaces                                                                 
                                         01/01                                                                     
                                         version)                                                                  

  4\. USE (Define need                                                                                             
  for, intended use of,                                                                                            
  and/or anticipated                                                                                               
  results of data)                                                                                                 

  Self evaluation of                                                                                               
  Contractor\'s safety                                                                                             
  and health program                                                                                               
  performance.                                                                                                     

  5\. DRD Category:          Technical                                       Administrative            X   SR&QA   
  *(check one)*                                                                                                    

  6\. References                                     7\.                                                           
  *(Optional)*                                       Interrelationships                                            
                                                     *(e.g., with other                                            
                                                     DRDs) (Optional)*                                             

  JPG 1700.1 (as revised)                            .                                                             

  8\. Preparation                                                                                                  
  Information (Include                                                                                             
  complete instructions                                                                                            
  for document                                                                                                     
  preparation)                                                                                                     
  ----------------------- -- ----------- ----------- -------------------- -- ---------------- -------- --- ------- -------------------

1\. The Contractor shall conduct an annual self-evaluation of its safety
and health program as required by its safety and health plan.

2\. Information required:

2.a. The internal assessment of safety and health program effectiveness
during the report period (i.e., the previous year) indicating the status
of goals or objectives previously established and areas of strength and
weakness in Contractor safety program performance.

2.b. Safety and health concerns and resolutions relating to JSC
operations which may have been identified during the report period.

2.c. Unresolved safety and health concerns relating to JSC operations
which the Contractor feels merit attention of JSC safety and health
management.

2.d. The goals and objectives of the Contractor safety and health
program for the next report period.

2.e. An analysis of the contractor\'s performance **at JSC-administered
establishments** in each of the 32 Voluntary Protection Program
sub-elements as found in the Federal Register of July 24, 2000
(available at the following link):

http://www.osha-slc.gov/FedReg_osha_data/FED20000724A.html***.***

2.f. Action plans shall be attached for identified problem areas. Action
plans shall include schedule for periodic progress reports to the
Government. Frequency of status reports shall to be agreed to by the
Government and the Contractor for each problem area.

3\. Format to be as specified in OSHA TED 8.1, \"Revised Voluntary
Protection Programs (VPP) Policies and Procedures Manual\", Appendix H
(Program Evaluation Report), Attachment 2 (VPP Onsite Evaluation Format
for Safety and Health Programs) for a STAR work site which is found at
the following link:

> http://www.osha-slc.gov/OshDoc/Directive_data/TED_8_1A.html,

as mandated by the cognizant OSHA regional office. Contractors who have
submitted a written self-evaluation as a VPP site may submit their
original report to OSHA in lieu of writing a new self -evaluation
provided that all action plans and status are updated.

See Contracting Officer's letter BN-02-062 dated June 14, 2002.

4\. Report due September 30^th^ of each year.

**JSC DATA REQUIREMENTS DESCRIPTION (DRD)**

(Based on JSC STD-123)

<table style="width:100%;">
<colgroup>
<col style="width: 33%" />
<col style="width: 2%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 7%" />
<col style="width: 8%" />
<col style="width: 2%" />
<col style="width: 1%" />
<col style="width: 27%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><ol type="I">
<li><p>DRD Title</p></li>
</ol>
<p>SA-1-14, , Monthly Safety and Health Metrics</p></td>
<td colspan="4">2. Current Version Date</td>
<td colspan="3">3. DRL Line Item No.</td>
<td>RFP/Contract No. (Procurement completes)</td>
</tr>
<tr class="even">
<td colspan="3"></td>
<td colspan="4"><p>04/01 (replaces</p>
<p>01/01 version)</p></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="11">4. Use (Define need for, intended use of, and/or
anticipated results of data)</td>
</tr>
<tr class="even">
<td colspan="11"><p>Establishes selected Safety and Health Program
metrics</p>
<p>***The Office of Primary Responsibility for this DRD is the JSC
Safety, Reliability, and Quality Assurance Office</p></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<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="odd">
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></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">DRD SA-1-1</td>
</tr>
<tr class="even">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

Frequency of submission. Monthly by 10^th^ of month following month
being reported.

Distribution.

NT2/Occupational Safety Branch (2 copies)

SD26/Occupational Health Officer (1 copy)

Contracting Officer's Technical Representative (COTR) (1 copy)

[Format:]{.underline} electronic to NT2, SD26; hard copy to COTR. Send
as Excel spreadsheet or in tables compatible with MS Word. See
Contracting Officer's letter BN-02-062 dated June 14, 2002.

[Definitions]{.underline}. Refer to JPG 1700.1 and OSHA requirements for
definitions of terms below.

**[Scope.]{.underline} The scope of the information required is limited
to the JSC-administered establishments of Houston Texas at NASA Road
One; Sonny Carter Training Facility; and Ellington Field.**

[Content.]{.underline}

I. Management Commitment and Employee Involvement.

<table style="width:100%;">
<colgroup>
<col style="width: 10%" />
<col style="width: 11%" />
<col style="width: 9%" />
<col style="width: 6%" />
<col style="width: 10%" />
<col style="width: 10%" />
<col style="width: 10%" />
<col style="width: 10%" />
<col style="width: 10%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="2"><p>Date of Management</p>
<p>Safety Committee Meeting</p></td>
<td colspan="2">Type/Title of Meeting</td>
<td colspan="2">No. of Managers attending</td>
<td colspan="2">No. of supervisors attending</td>
<td colspan="2">No. of non-supervisory attending</td>
</tr>
<tr class="even">
<td>This month</td>
<td>Year to date</td>
<td></td>
<td></td>
<td>This month</td>
<td>Year to date</td>
<td>This month</td>
<td>Year to date</td>
<td>This month</td>
<td>Year to date</td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>

Include **electronic** copies of minutes **or representative
information**

  ---------- -------- ------------ -- ----------- --------------- ---------------------- ----------
  No. of              Type/Title      No. of                      No. of                 
  Employee            of Meeting      Employees                   managers/supervisors   
  Safety                              attending                   attending              
  Meeting                                                                                

  This month Year to                  This month  Year to date    This month             Year to
             date                                                                        date

                                                                                         

                                                                                         

                                                                                         

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

Include **electronic** copies of minutes **or representative
information**

**JSC DATA REQUIREMENTS DESCRIPTION (DRD)**

(Based on JSC STD-123)

II\. Worksite Analysis. Refer to JPG 1700.1 for definitions of terms.

  ---------- ---------- ------ ----------- ------ ---------- ------ ----------- ------ ------------- ------ ----------- ------
  Division   No. of                               No. of Job                           No. of                           
             Hazard                               Safety                               Routine                          
             Analyses                             Analyses                             Inspections                      

             Required          Performed          Required          Performed          Required             Performed   

             This month Year   This month  Year   This month Year   This month  Year   This month    Year   This month  Year
                        to                 to                to                 to                   to                 to
                        Date               Date              Date               Date                 Date               Date

                                                                                                                         

                                                                                                                         

   Total                                                                                                                 
  ---------- ---------- ------ ----------- ------ ---------- ------ ----------- ------ ------------- ------ ----------- ------

> III\. Hazard Prevention and Control - hazards below were found during
> routine and special inspections, close calls, mishap investigations,
> etc., and require correction.

  --------- ------- ------ --------- ------- ------ --------- --------- ------- ------ --------- ------- ------ ---------
  No. of                   No. of                   No. of    No. of                   No. of                   No. of
  Hazards                  Hazards                  Hazards   Hazards                  Hazards                  JF1240s
  found                    closed                   open \<30 open \>30                closed                   in place
                           \<30 days                days      days                     \>30 days                

  Prior to  This    Year   Prior to  This    Year             Prior to  This    Year   Prior to  This    Year    
  month     month   to     month     month   to               month     month   to     month     month   to     
                    date                     date                               date                     date   

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

> Attach copies (electronic ok if sent by e-mail) of JF 1240\'s **(or
> equivalent)** including monthly updates. Mark JF 1240\'s where
> abatement has been completed as closed.
>
> IV\. Safety and Health Training - List courses specific to **loss
> control initiatives (such as slips/trips falls, material handling;
> etc.) Report other training as \"Generic safety training not otherwise
> specified\" (examples include** Hazard Communication, Confined Space
> entry, HAZWOPER, system safety, job safety analysis, etc.) Do not
> include job proficiency course work where safety is an issue (such as
> radiography, welding, painting, etc.)

  ---------------------------------------- ----------- --------- ----------
  Course Title                             No. to be   No.       On
                                           Trained     Trained   Schedule

                                                                 

                                                                 

                                                                 

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

**JSC DATA REQUIREMENTS DESCRIPTION (DRD)**

(Based on JSC STD-123)

<table>
<colgroup>
<col style="width: 35%" />
<col style="width: 2%" />
<col style="width: 6%" />
<col style="width: 4%" />
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 8%" />
<col style="width: 9%" />
<col style="width: 2%" />
<col style="width: 1%" />
<col style="width: 21%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="3"><ol type="I">
<li><p>DRD Title</p></li>
</ol>
<p>SA-1-15, Lessons Learned</p></td>
<td colspan="4">2. Current Version Date</td>
<td colspan="3">3. DRL Line Item No.</td>
<td>RFP/Contract No. (Procurement completes)</td>
</tr>
<tr class="even">
<td colspan="3"></td>
<td colspan="4">01/2001</td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="11">4. Use (Define need for, intended use of, and/or
anticipated results of data)</td>
</tr>
<tr class="even">
<td colspan="11"><p>Obtains Lessons learned from Contractor for possible
publication in NASA Lessons Learned Information System (LLIS)</p>
<p>***The Office of Primary Responsibility for this DRD is the JSC
Safety, Reliability, and Quality Assurance Office</p></td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<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="odd">
<td></td>
<td></td>
<td colspan="3"></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></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">DRD SA-1-1, paragraphs 2.5.1 and 3.11.2</td>
</tr>
<tr class="even">
<td colspan="11">8. Preparation Information (Include complete
instructions for document preparation)</td>
</tr>
</tbody>
</table>

Criteria for Selecting Lessons Learned. Uncommon insight arising from
any event or observation that will benefit from sharing with a larger
community of interested parties. Lessons learned are intended to prevent
recurrence of undesirable events and to allow NASA and its team members
to capitalized to the greatest extent practical on unique successes.

Frequency of submission. 30 days after triggering event or 30 days after
mishap investigation or hazard analysis / evaluation is completed.

Distribution.

NT2/Occupational Safety Branch (1 electronic copy including photographs,
drawings, etc., in web-ready format such as HTML or JPG)

Contracting Officer's Technical Representative (COTR) (1 copy) See
Contracting Officer's letter BN-02-062 dated June 14, 2002.

[Content:]{.underline}

Subject - one line subject of the lesson.

Lesson Learned - usually one sentence that describes insight gained

Description of Event - narrative of what happened.

Recommendations - may be an action plan, suggestion, etc., that was
adopted at event source.

Supporting documentation - as needed to give clear picture of lesson
(photographs, illustrations, drawings, etc.)

Contact name and e-mail address (for follow up by Government prior to
publication of lesson)

[Definitions]{.underline}. Refer to NASA LLIS at
http://llis.gsfc.nasa.gov/ for definitions of terms used.