DATA REQUIREMENTS DESCRIPTION (DRD)

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** Rev. 1 2.
[**DRD NO**.]{.smallcaps}: **1.1.1.1-a**

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

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

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

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe the contractor's
management organization, approach and systems.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Within 10 days of contract
Authority to Proceed (ATP)

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

-   [Annually, unless update is waived by the NASA OPR]{.underline}

-   [Within 45 days after the addition/deletion of major content to the
    SFOC]{.underline}

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

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The Management Plan shall
describe the basis for the contractor management organization, approach
and systems. It shall provide a comprehensive integration of all
management systems of the prime, subcontractors, and major vendors. 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}]{.smallcaps}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The Management Plan shall
address the contractor's plans for work definition and authorization,
scheduling, budgeting, data accumulation, Safety and Mission Assurance,
Program recovery process, subcontract/material control, indirect cost
management, baseline control, and organization structure.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.1.1.1-b**

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

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

6\. **[TITLE]{.smallcaps}**: Work Breakdown Structure (WBS) and
Dictionary

7\. **[DESCRIPTION/USE]{.smallcaps}**: To organize the tasks to be
accomplished in this contract in a product-oriented structure. The WBS
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}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION]{.smallcaps}**: 30 days after contract
Authority to Proceed (ATP)

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

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.1.1.1, 1.1.2.1 and
1.1.2.2; DRD's 1.1.1.1-g, 1.1.2.1-a, and 1.1.2.2-a.

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

13.1 **[SCOPE]{.underline}**: The WBS shall encompass all the products
required to achieve all the requirements of this contract. The WBS 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}**:]{.smallcaps} None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The WBS shall depict a
family tree composed of all the work required by the contract. The
dictionary contains a concise description of contract tasks to be
performed and products to be delivered, subdivided by WBS element. A WBS
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 the
level of detail in the RFP SOW with additional levels as required by the
contract. 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 to NASA. The
relationship between the WBS and the contractor's internal organizations
and processes should also be provided.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: The WBS tree is to be in
organization chart format and the associated WBS narrative (WBS
Dictionary) in text form and arranged as stated in 13.3 of this DRD. The
WBS tree and dictionary shall be provided in both electronic and hard
copy form.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** Rev. 1]{.smallcaps} 2.
[**DRD NO**.]{.smallcaps}: **1.1.1.1-c**

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

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

6\. **[TITLE]{.smallcaps}**: Space Flight Operations Contract Transition
Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide a planning logic and
baseline for transition of all Space Flight Operations activities to the
SFOC and insight into planning for cost reduction initiatives across the
contract.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Incorporated into basic
contract (for Phase 1 of transition activities)

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Pursuant to Clause H.30,
contracting officer direction for any Phase II contract incorporation
shall specifically require an update to be included with the contract
transition proposal.

11\. **REMARKS:**

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The Space Flight Operations
Transition Plan provides plans for the transfer of all anticipated
operations activity to the SFOC along with supporting logic and
rationale. These plans will include an assessment of the transition of
Government responsibilities for the transferred effort.

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

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

> a\. Schedule for transition and implementation of the plans,
> procedures and processes required for performance of the contract.
>
> b\. Metrics used to determine progress for contract transition.
>
> c\. Metrics used for identification of process improvement or
> requirements changes.
>
> d\. Plan for integration of new effort into SFOC management systems.
>
> e\. Recommended contract arrangements (e.g., assume existing
> contract).
>
> f\. Transition of Government involvement.
>
> g\. Proposed SFOC contract language changes/additions.
>
> h\. Cost reduction initiatives for scope already included in or being
> added to SFOC.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** RFP 2.
[**DRD NO**.]{.smallcaps}: **1.1.1.1-d**

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

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

6\. **[TITLE]{.smallcaps}**: Privatization Development Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide a plan for potential
privatization of operations systems and services and/or involvement of
commercial customers of the Space Shuttle.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Contract Authority to Proceed
(ATP) plus one year, or upon NASA

request

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Annually or upon NASA
request

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

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The plan describes how the
contractor will implement initiatives to stimulate private sector
involvement in operations services and as paying customers of Space
Shuttle transportation services.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The plan shall include,
but not be limited to the following information:

a\. Method for implementing initiatives to stimulate private sector
customers for operations systems and services.

b\. Method for implementing a potential Government decision to accept
operations systems and services from commercial entities.

c\. Method for implementing a potential Government decision to accept
commercial customers of the SSP and/or ISS.

d\. Method by which the estimated cost for such initiatives may be
derived.

e\. Type of management interfaces that would be required.

f\. Anticipated relationships among the commercial entity, NASA, and the
contractor.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.1.1.1-e**

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

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

6\. **[TITLE]{.smallcaps}**: Contingency Plans

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document contractor
requirements, responsibilities, processes and implementation approach
for specified contingencies.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an on-going
requirement; no break in existing submission schedule

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Update annually

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

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

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

13.1 **[SCOPE]{.underline}**: Contingency Plans define the contractor\'s
responsibilities and implementation processes and procedures to satisfy
contingency requirements.

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

See Exhibit 1.1.1.1 to the Statement of Work

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The contractor shall
develop and maintain (update) contingency plans as listed in Exhibit
1.1.1.1. The contractor is encouraged to standardize and consolidate
similar documentation provided the scope and contents of the existing
plans are retained and the appropriate NASA approval is obtained.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page (revision level and date) or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
[**DRD NO**.]{.smallcaps}: **1.1.1.1-f**

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

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

6\. **[TITLE]{.smallcaps}**: Space Flight Operations Product Development
Plans

7\. **[DESCRIPTION/USE]{.smallcaps}**: To establish the schedule, the
metrics, and baseline all of the plans, procedures, and processes
required for the performance and delivery of operations and flight
support and Shuttle certification products.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Contract Authority to Proceed
(ATP) plus six months

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Updates annually, as
required

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

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The Space Flight Operations
Product Development Plans define all planned operations and flight
support and Shuttle certification activities transitioned to the Space
Flight Operations Contract. The contractor plans, procedures, processes,
and products will be audited when deemed necessary by the Government.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The plans shall provide a
detailed characterization of the work efforts required to deliver
products obligated under this contract. It shall include, but is not
limited to:

a\. Identification of plans, procedures and processes required for
contract implementation.

b\. Product descriptions and applications, customers, organizational
hand-offs, math models, databases, schedules, tools, and product
assurance management systems.

c\. Metrics used to determine compliance with Government requirements.

d\. Metrics used for the identification of process improvement or
requirements changes.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** RFP 2.
[**DRD NO**.]{.smallcaps}: **1.1.1.1-g**

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

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

6\. **[TITLE]{.smallcaps}**: Organizational Breakdown Structure

7\. **[DESCRIPTION/USE]{.smallcaps}**: To identify the contractor's
organization for performing this contract.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Ten days after contract
Authority to Proceed (ATP)

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: (See 13.5)

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.1.1.1, 1.1.2.1 and
1.1.2.2; DRD's 1.1.1.1-b, 1.1.2.1-a, and 1.1.2.2-1

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The OBS shall encompass all
elements of the contractor's organization involved in performing the
requirements of this contract.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: For each organizational
element information shall include the title of the organization and the
name of the incumbent manager (headcount is provided in DRD 1.1.2.1-e),
and a cross-reference to each WBS element where work is performed.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Complete reissue as
required; otherwise, annually.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.1.1.1-h

3\. [DATA TYPE]{.smallcaps}: 2 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

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

7\. [DESCRIPTION/USE]{.smallcaps}: To describe the method of
administering Government personal property.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: Preliminary three months after
Authority to Proceed (ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Final one year after ATP

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: Paragraph (e)(2) of Clause
52.245-5, SOW 1.1.6.2, DRD 1.4-c

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

13.1 [SCOPE]{.underline}: The Government Property Management Plan
defines the contractor\'s acquisition use, protection recording and
reporting requirements of Government personal property.

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

Federal Acquisition Regulation (FAR) Part 45

NASA FAR Supplement (NFS) Part 1845

NMI 4000.3 *Supply and Equipment Management*

NHB 4100.1 *NASA Materials Inventory Management Manual*

NHB 4200.1 *NASA Equipment Management Manual*

NHB 4200.2 *Equipment Management User's Handbook for Property
Custodians*

NHB 4300.1 *NASA Personal Property Disposal Manual*

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

a Property management. i. Reports.

b\. Acquisition. j. Consumption.

c\. Receiving. k. Utilization.

d\. Identification. l. Maintenance.

e\. Records. m. Subcontractor control.

f\. Movement. n. Disposition.

g\. Storage. o. Contractor close-out.

h\. Physical Inventories. p. Reconcile contractor records with

NASA\'s financial records.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor format is
acceptable.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.1.1.1-i**

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

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

6\. **[TITLE]{.smallcaps}**: New Technology Reporting

7\. **[DESCRIPTION/USE]{.smallcaps}**: Provides NASA with detailed
technical information relating to inventions, discoveries, improvements,
and innovations made by the contractor in the performance of work under
this contract for the purpose of identifying NASA-supported new
technology, and promoting its commercialization and public availability,
and also to ensure that the Government obtains sufficient rights in such
technology to meet its needs.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: See Submission Frequency

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: (1) [REPORTABLE
ITEMS]{.underline} (New Technology Reports) shall be submitted to the
Contracting Officer within two months after the inventor discloses it in
writing to Contractor personnel responsible for the administration of
the New Technology clause or, if earlier, within six months after the
Contractor becomes aware that a reportable item has been made, but in
any event for subject inventions before any on sale, public use, or
publication of such invention known to the Contractor. (2) [INTERIM
REPORTS]{.underline} shall be submitted every 12 months from the date of
this contract. (3) The [FINAL REPORT]{.underline} shall be submitted to
the Contracting Officer within 3 months after completion of the
contracted work. The TMR\'s will determine the format for the Interim
and Final Reports. Data shall be provided on electronic media.

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: NFS 1852.227-70, New
Technology Clause

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

13.1 SCOPE: The Contractor shall establish and maintain active and
effective procedures to assure that reportable items are promptly
identified and disclosed to Contractor personnel responsible for the
administration of this New Technology clause within six months of
conception and/or first actual reduction to practice, whichever occurs
first in the performance of work under this contract. These procedures
shall include the maintenance of laboratory notebooks or equivalent
records and other records as are reasonably necessary to document the
conception and/or the first actual reduction to practice of the
reportable items, and records that show that the procedures for
identifying and disclosing reportable items are followed. Upon request,
the Contractor shall furnish the Contracting Officer a description of
such procedures for evaluation and for determination as to their
effectiveness. The contractor shall submit "Reportable Items," or New
Technology Reports, describing any invention, discovery, improvement, or
innovation of the Contractor, whether or not the same is or may be
patentable or otherwise protectible under the U.S. Patent Laws,
conceived or first actually reduced to practice in the performance of
any work under this contract or in the performance of any work that is
reimbursable under any clause in this contract providing for
reimbursement of costs incurred prior to the effective date of this
contract. Contractor shall also submit Interim Reports and a Final
Report providing summary information.

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

NFS 18-52.227-70 *New Technology Clause*

####### DRD Continuation Sheet

**[TITLE]{.smallcaps}**: New Technology Reporting **[DRD
NO.]{.smallcaps}**: **1.1.1.1-i**

**[DATA TYPE]{.smallcaps}**: 3 P**[AGE]{.smallcaps}**: 2/2

13\. DATA PREPARATION INFORMATION (CONTINUED):

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

I. [REPORTABLE ITEMS]{.underline} (New Technology Reports). These
reports shall include the following elements as appropriate. NASA Form
666A (April 1985) may be used in accordance with instructions on the
reverse of the form. Use of this form is optional, provided all
information listed below is included in each report:

a\. Name and address of the contractor submitting the report.

b\. The contract number of the contract under which the report is being
submitted.

c\. Title of the item reported.

d\. Brief description (abstract)of the item reported.

e\. Detailed description in the following order:

1\. General purpose of the item (if not explained in the brief
description, or abstract).

2\. Improvement and/or advantage over prior methods, materials, or
devices.

3\. Detailed description of the item, sufficiently complete in technical
detail to convey a clear understanding, to the extent known at the time
of the disclosure, of the nature, purpose, operation, and physical,
chemical, biological, or electrical characteristics. Technical data,
drawings, and sketches should be included as required to fully describe
the item.

4\. Feature of the item believed to be new.

5\. Additional information needed to fully describe the item.

f\. Applications: Include potential commercial and other non-aerospace
uses and users. Identify specific industries, processes, or products in
which the "Reportable Item" might find application or to which it might
be related.

g\. Description of possible extensions, or alternate embodiments of this
item.

h\. Degree of development and use. Indicate applicable stage:

1\. Concept only.

2\. Development completed, prototype available.

3\. Limited production.

4\. Date of first actual use, or date of first planned use.

i\. Innovator\'s name(s) and social security number(s), mailing address,
and telephone number.

j\. Identification of any previous publication of the disclosure. List
publications, manuscripts submitted for publication, or reports
pertaining to this item, together with relevant dates. If
company-originated, state where they may be obtained; if not
company-originated, indicate source and where publication may be
obtained, if known.

> k\. Technical supervisor or innovator(s).

II\. INTERIM REPORTS shall list reportable items during that period, and
certify that all reportable items have been disclosed (or that there are
no reportable items) and that the procedures set forth in Section 13.1
above have been followed.

III\. The FINAL REPORT shall list all reportable items or certify that
there were no such reportable items, and list all subcontracts at any
tier containing a new technology or patent rights clause or certify that
there were no such subcontracts.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats in accordance with
NASA Form 666A (April 1985) or per Contracting Officer approval.

5.  **[[MAINTENANCE]{.underline}]{.smallcaps}**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.1.1.1-j**

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

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

6\. **[TITLE]{.smallcaps}**: SHUTTLE GROUND PROCESSING
PLANS/INSTRUCTIONS

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe and baseline the
contractor\'s standardized technical and operational plans and
instructions required for the performance of the nine core processes for
Ground Operations and definition of the required Government interfaces.
This DRD defines specific action applicable only to the KSC Ground
Operations portion of the SFOC. It is intended to be used at KSC in lieu
of DRD 1.1.1.1-f, Space Flight Operations Product Development Plan.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Contract Authority to Proceed
(ATP) plus six months

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Updates annually, as
required

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.1.1.1 and DRD 1.1.1.1-f

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

13.1 **[SCOPE]{.underline}**: The Ground Processing Plans/Instructions
shall document the contractors planned implementation of and/or support
to the nine Ground Operations core processes identified in the SFOC
Program Management Plan (PMP) Section 7.0 and other appropriate
Government requirements.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: Identification of
baseline plans and processes required for contract implementation
including process descriptions, data flow diagrams and process flow
charts; applications, customers and organizational hand-offs; and
process verification/integrity assurance methodology. The Ground
Processing Plans/Instructions shall address the contractor\'s plans to
implement the Government\'s requirements as a minimum in the following
Ground Processing core processes: 1) work flow planning, 2) work
instruction generation, 3) personnel training; 4) parts, material and
services provisioning; 5) facilities and support equipment maintenance;
6) ground processing task execution, 7) ground processing information
provisioning; 8) surveillance, and 9) requirements control. It is
NASA\'s objective to transition away from explicit Government approval
on these documents during the SFOC transition except for those plans
involving critical ground processes or in-line functions performed by
NASA personnel. The contractor shall consolidate and reduce existing
processing plans and instructions that document like processes within
these specific core processes.

DRD Continuation Sheet

**[TITLE]{.smallcaps}**: Shuttle Ground Processing Plans/Instructions
**[DRD NO.]{.smallcaps}**: **1.1.1.1-j**

**[DATA TYPE]{.smallcaps}**: 1 **[PAGE]{.smallcaps}**: 2/2

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE:]{.smallcaps} REVISION 1 2. [DRD
NO.]{.smallcaps}: 1.1.1.1-k

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. TITLE: Notification of Significant Program Management Decisions

[7. DESCRIPTION/USE]{.smallcaps}: The purpose of the DRD is to document
potentially significant contractor program management decisions such
that NASA program management will have timely and appropriate insight
prior to their implementation.

8\. [DISTRIBUTION]{.smallcaps}: MA/Space Shuttle Program Manager;
MA/SFOC COTR; MM/Space Shuttle Business Manager; BV/Space Shuttle
Program Procurement Officer, BV2/Procuring Contracting Officer

9\. [INITIAL SUBMISSION]{.smallcaps}: As required by the contractor to
meet the DRD intent, but no later than the SFOC CMR following approval
of this DRD.

[10. SUBMISSION FREQUENCY]{.smallcaps}: As required by the contractor to
meet the DRD intent of allowing NASA insight prior to implementation of
applicable decisions.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.1.1

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

[13.1 [SCOPE]{.underline}]{.smallcaps}: The purpose of the DRD is to
inform the Shuttle Program Manager of significant program management
decisions prior to their implementation and thus support proactive
insight into these decisions. Target decision areas to be addressed
would include significant or critical resource allocation changes
(including reductions, increases or re-distributions); decisions to make
major investments in Program processes, systems, property or facilities;
or decisions to change the workforce size and/or composition or major
organizational/functional restructuring. While not an absolute criteria,
"significant" and "major" for purposes of this DRD would be expected to
encompass decisions impacting budget plans by more than \$5 million or
impacting manpower plans involving more than 50 employees.

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

[13.3 [CONTENTS]{.underline}]{.smallcaps}: The following information may
be delivered in the form of a presentation or a white paper. At a
minimum, the package shall contain the following information:

-   A description of the circumstances which lead to this decision.

-   A discussion of the change being planned and the implementation
    schedule.

-   An analysis of anticipated productivity improvements, if applicable

-   An impact analysis that the decision will have on contract
    performance including potential safety, quality, schedule,
    workforce, and cost issues.

-   A risk assessment performed to support each decision.

    13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
    delivery media formats and electronic data formats per DRD
    1.1.4.1-e, Data Management Plan, or per Contracting Officer
    approval.

    13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required

    DATA REQUIREMENTS DESCRIPTION (DRD)

    1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2.
    [DRD NO.]{.smallcaps}: 1.1.1.2.3

    3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED:
    09/01/98]{.smallcaps}

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

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

    7\. [DESCRIPTION/USE]{.smallcaps}: To certify the completion or
    disposition of all contractor tasks and planned work required to
    prepare for flight readiness in accordance with NSTS 08117 and SSP
    50108.

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

    9\. [INITIAL SUBMISSION:]{.smallcaps} First launch after contract
    award

    10\. [SUBMISSION FREQUENCY]{.smallcaps}: Prior to each Flight
    Readiness Review

    11\. [REMARKS]{.smallcaps}:

    12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.1.2.2

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

    13.1 [SCOPE]{.underline}: The Flight Readiness Review and statements
    document the readiness of each function in support of the
    contractor's Certification of Flight Readiness (CoFR).

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

    NSTS 08117 *Requirements and Procedures for Certification of Flight
    Readiness*

    SSP 50108 *Certification of Flight Readiness for Space Station*

    13.3 [[CONTENTS]{.underline}]{.smallcaps}: Data shall include the
    contractor's internal Flight Readiness report with readiness
    statements that coverall processes and products specified in the
    applicable documents, as well as any necessary supporting data,
    required to satisfy the contractor\'s responsibilities and readiness
    to support launch, mission and landing operations as defined in the
    applicable documents.

    13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
    delivery media formats and electronic data formats per DRD
    1.1.4.1-e, Data Management Plan, or per Contracting Officer
    approval.

    13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: A historical file of
    the Flight Readiness Report and Statements shall be maintained by
    the contractor. Archives shall be maintained and archival materials
    dispositioned in accordance with NASA and Federal Records Management
    regulations and procedures.

    **DATA REQUIREMENTS DESCRIPTION (DRD)**

    1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
    [**DRD NO**.]{.smallcaps}: **1.1.1.4-a**

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

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

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

    7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide a comprehensive
    plan to manage and document risk associated with operations of the
    Space Shuttle Program (SSP).

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

    9\. **[INITIAL SUBMISSION]{.smallcaps}**: Six months after Authority
    to Proceed (ATP)

    10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Update annually or as
    required by NASA.

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

    12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.1.1.4, 1.3

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

    13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The Risk Management Plan
    shall address safety, reliability, maintainability, quality, cost,
    schedule and mission success.

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

    13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The SSP Risk
    Management Plan shall describe how the contractor proposes to manage
    risk throughout the program. It shall describe how the contractor
    will identify, assess and mitigate/control risks associated with
    each decision or process. This plan shall include the following:

    a\. Information which illustrates the functional relationships and
    lines of communication, including the involvement of subcontractors
    and major vendors.

    b\. Descriptions of the risk management function within the
    organization including the process through which management
    decisions will be made. This will include a description of
    interfaces with NASA organizations and the NASA decision process for
    areas such as critical and catastrophic hazards, corrective actions,
    mishaps, safety variances/waivers, cost, schedule, and mission
    success.

    c\. Description of the management controls that will be used to
    ensure compliance with the risk mitigation process.

    13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall
    conform to delivery media formats and electronic data formats per
    DRD 1.1.4.1-e, Data Management Plan, or per Contracting Officer
    approval.

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

    DATA REQUIREMENTS DESCRIPTION (DRD)

    1\. [DPD NO.]{.smallcaps}: 821 [ISSUE:]{.smallcaps} REVISION 1 2.
    [DRD NO.]{.smallcaps}: 1.1.1.4-b

    3\. [DATA TYPE]{.smallcaps}: 3 4. DATE REVISED: 09/01/98

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

    6\. [TITLE]{.smallcaps}: Risk Assessment Documentation9

    7\. [DESCRIPTION/USE]{.smallcaps}: To provide a documented risk
    assessment to Space Shuttle Program (SSP) management when the
    contractor is either a requested evaluator on a formal, documented
    change request, or when the contractor initiates a formal,
    documented change request to be dispositioned at a Space Shuttle
    Program Board.

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

    9\. [INITIAL SUBMISSION]{.smallcaps}: See Submission Frequency
    below.

    10\. [SUBMISSION FREQUENCY]{.smallcaps}: A risk assessment will be
    provided with each formal, documented change evaluation provided by
    the contractor in response to formal, documented change requests
    from Space Shuttle Program Boards. When less than 2 working days are
    available for evaluation, a verbally expressed risk assessment will
    be provided at the review forum (this may include expedited items).
    Documentation of the risk assessment will follow. A risk assessment
    will also be provided for change requests initiated by the
    contractor and presented to a Space Shuttle Program Board. If
    insufficient time is available to assess risk prior to the
    disposition of an item, this will be so stated with a recommendation
    for deferral.

    11\. [REMARKS]{.smallcaps}: For purposes of this DRD, Space Shuttle
    Program Boards are those defined in NSTS 07700, Vol. IV, Book 1,
    Section 4.3.2, 'Program Boards', with the exception of the MRB and
    PMRB.

    12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.1.4, SOW 1.3.

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

    13.1 [[SCOPE]{.underline}]{.smallcaps}: The documented risk
    assessment provides a formal means to identify risks, assess risks
    and identify options for mitigating risks associated with safety,
    mission success, schedule, supportability, and/or cost. A risk
    assessment including analytical, quantitative or qualitative methods
    as appropriate will be developed and provided with each change
    evaluation provided by the contractor in response to formal,
    documented change requests from Space Shuttle Program Boards, or
    change requests initiated by the contractor and presented to Space
    Shuttle Program Boards for disposition

    13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}: NSTS 07700,
    Vol. IV, Book 1, Section 4.3.2, 'Program Boards'.

    [13.3 [CONTENTS]{.underline}]{.smallcaps}: The assessment content
    shall vary based upon the consequence/likelihood of risks imposed by
    a change item.

    If no significant increase in risk is identified for a proposed
    change item, the assessment shall include:

    a\. A statement indicating 'no significant increase in risk'

    b\. Justification for assessment as necessary*.*

    c\. Identification of any impact to baselined risk controls (hazard
    reports & CILs)

    DRD CONTINUATION SHEET

    [TITLE]{.smallcaps}: Risk Assessment Documentation [DRD
    NO.]{.smallcaps}: 1.1.1.4-b

    [DATA TYPE]{.smallcaps}: 3 [PAGE]{.smallcaps}: 2/2

    If a proposed change poses at least one risk whose
    consequence/likelihood combination indicates a significant increase
    in risk, the assessment shall include:

    a\. Identification of the potential risk(s)/impact associated with
    the change, and the causes of these risk(s).

    b\. Impact assessment (consequence & likelihood) to safety, mission
    success, schedule, supportability, and/or costs in the event the
    identified risk(s) were to occur.

    c\. Options for mitigating the identified risk(s) including the
    contractor's recommendation.

    d\. Impacts to baselined risk controls (hazard reports & CILs).

    13.4 [[FORMAT]{.underline}]{.smallcaps}: Formal delivery of risk
    assessments shall be made via the change proposal or change
    evaluation submittal processes as defined by each SSP board.

    13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required.

    **DATA REQUIREMENTS DESCRIPTION (DRD)**

    1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
    [**DRD NO**.]{.smallcaps}: **1.1.1.4-c**

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

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

    6\. **[TITLE]{.smallcaps}**: Anomaly Disposition Approval Requests

    7\. **[DESCRIPTION/USE]{.smallcaps}**: To document contractor
    requests for NASA approval of contractor's proposed resolution of a
    significant anomaly.

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

    9\. **[INITIAL SUBMISSION]{.smallcaps}**: The contractor shall
    submit anomaly dispositions to NASA for approval when preparation of
    proposed actions and supporting rationale are complete.

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

    11\. **[REMARKS]{.smallcaps}**: The contractor may assume the
    schedule risks associated with continued processing prior to
    obtaining NASA approval of an anomaly disposition.

    12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.1, 1.3, 1.4, 1.5

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

    13.1 **[[SCOPE]{.underline}]{.smallcaps}**: NASA approval is
    required for anomaly dispositions which:

    a\. Involve the first-time occurrence of a failure mode.

    b\. Limit hardware life.

    c\. Restrict hardware or software use.

    d\. Affect the performance or reliability of safety or mission
    success critical hardware functions.

    e\. Affect hazard control.

    f\. Result in a weight change in excess of two pounds (equivalent
    weight to orbit).

    g\. Affect flight or ground operating procedures that are controlled
    by the Government.

    h\. Change hardware or software configuration.

    i\. Allow use of hardware that does not meet performance
    specifications, exceeds certification limits, or surpasses time,
    age, or cycle life limits (waivers).

    j\. Close or defer resolution of an unexplained anomaly.

    k\. Require government design element analysis or assistance.

    l\. Affect critical hardware manufacture or repair processes.

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

    NSTS 07700 Volume IV *Configuration Management Requirements*

    NSTS 07700 Volume X *Space Shuttle Flight and Ground Systems
    Specification*

    NSTS 07700-10-MVP-01 *Space Shuttle Master Verification Plan*

    NSTS 08126 *Problem Resolution and Corrective Action Requirements*

    NSTS 08171 File I *Operational Maintenance Requirements and
    Specifications*

    13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: Detailed minimum
    requirements for disposition content are provided in the applicable
    documents. Requests for NASA approval of an anomaly disposition
    shall include all information used to develop the contractor's
    recommendation and supporting rationale.

    DRD Continuation Sheet

    **[TITLE]{.smallcaps}**: Anomaly Disposition Approval Requests
    **[DRD NO.]{.smallcaps}**: **1.1.1.4-c**

    **[DATA TYPE]{.smallcaps}**: 1 **[PAGE]{.smallcaps}**: 2/2

    13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall
    conform to delivery media formats and electronic data formats per
    DRD 1.1.4.1-e, Data Management Plan, or per Contracting Officer
    approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** [REVISION
3]{.smallcaps} 2. [**DRD NO**.]{.smallcaps}: **1.1.2.1-a**

3\. **[DATA TYPE]{.smallcaps}**: Initial 533 Baseline Reports: 1 4.
**DATE REVISED: 12/02**

NASA Forms 533M/Q: 3 5. **[PAGE]{.smallcaps}**: 1/3

6\. **[TITLE]{.smallcaps}**: Financial Management Reports

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

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**:

Initial Baseline 533 Reports - 30 days after contract Authority to
Proceed (ATP).

NASA Form 533M - No later than the 15^th^ calendar day of the month in
which ATP is issued.

NASA Form 533Q - Quarterly, no later than the 20^th^ day of the month
preceding the quarter being reported on.

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

Initial baseline 533 reports - at time of initial submission, and when
the Contracting Officer requires additional detail as necessary such as
when options are exercised.

533M - Monthly, by the 15^th^ working day, but no later than the 23rd
calendar day, of the calendar month following the end of the
contractor\'s accounting month.

533Q - Quarterly, by the 20^th^ working day, but no later than the
30^th^ calendar day, of the month preceding the quarter being reported
on.

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.1.1.1, 1.1.2.1; DRD's
1.1.1.1- a & b, 1.1.2.1-b , 1.1.2.2-a & b; All data shall be
reconcilable with data from all of the reports required by this DRD, the
reports required by DRD 1.1.2.1-b, and the Performance Measurement
System (DRD 1.1.2.2-a & b).

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The Report provides 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}**:]{.smallcaps}

NFS 1852.242-73 *NASA Contractor Financial Management Reporting*

NMI 9501.1 *NASA Contractor Financial Management Reporting System*

NPG 9501.2C *NASA Contractor Financial Management Reporting*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The 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 report 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. In addition to the initial (baseline) report,
monthly NF533 reporting shall begin no later than the 15^th^ calendar
day of the month in which contract ATP is issued.

DRD CONTINUATION SHEET

**[TITLE]{.smallcaps}**: Financial Management Reports **[DRD
NO.]{.smallcaps}**: **1.1.2.1-a**

**[DATA TYPE]{.smallcaps}**: Initial Baseline Reports: 1
**[PAGE]{.smallcaps}**: 2/3

NASA Forms 533M/Q: 3

[13.]{.smallcaps} [**DATA PREPARATION INFORMATION
(CONTINUED)**:]{.smallcaps}

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

Columns 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 column 8 of the NF533M to
columns 7b and 7d. Columns 7b 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 adjustments should be reported in columns 7a and 7c of
NF533M and column 7a of the NF533Q with a footnote discussing the
reasons for and amounts of the adjustments.

Uncompensated overtime hours worked should be reported on NF533 reports
as a separate line item or in the footnotes.

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 contract 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" contract cost report, the contractor must submit a
revised NF533 report in the month the cost change is recognized.

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. For cost accrual purposes, data shall
be reported by NASA specific primary work codes (PWCs), including but
not limited to, the following:

-   Orbiter & Integration Operations (250-10)

-   Propulsion (250-40)

-   Mission and Launch Operations (250-90)

-   MEDS (260-03)

-   Orbiter Improvements (260-10)

-   Flight Operations and LSE Upgrades (260-90)

-   CLCS (260-96)

-   Advanced Control Center Technical Support (260-98)

-   Station Development (475-00)

-   Station Government Furnished (477-72)

-   Station ISS Configuration Management (478-11)

-   Payload Training Complex (479-42)

-   Station Operations - Logistics & Maintenance (575-13)

-   Station Operations - Planning & Cargo Integration (575-14)

-   Station Operations - Sustained Engineering (575-15)

-   Station Operations - Support (575-81)

-   Station Operations - Launch Site Processing (575-82)

-   ICM Implementation (599-20)

-   Station/Shuttle Integration (580-00)

-   Shuttle Orbiter MIR Support (508-20)

-   Shuttle Integration MIR Support (508-30)

```{=html}
<!-- -->
```
-   

-   

-   

-   

-   

-   

-   

-   

-   

-   

-   

-   

-   

-   

-   

-   

-   

-   

-   

-   

-   **DRD CONTINUATION SHEET**

    **[TITLE:]{.smallcaps}** [Financial Management Reports]{.smallcaps}
    **[DRD NO.]{.smallcaps}: 1.1.2.1-a**

    **[DATA TYPE]{.smallcaps}**: Initial 533 Baseline Reports: 1
    **[PAGE]{.smallcaps}:** 3/3

    NASA Forms 533M/Q: 3

    [13.]{.smallcaps} [**DATA PREPARATION INFORMATION
    (CONTINUED)**:]{.smallcaps}

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

```{=html}
<!-- -->
```
-   RLV Ground Based Program (242-20)

-   Advanced Space Trans. Operation/Software Tech. (242-40)

-   Payload Processing & Support (264-00)

-   Advanced Space - EVA Optional Services (906-30)

-   Spacelab (926-22)

-   Payload Utilization (947-88)

-   Construction of Facilities (Cof F)

-   Other NASA Programs (RE-ONP)

-   Reimbursables - Non NASA Programs (RE-NNP)

This data shall be provided in the NF533 format. Data shall identify
price and workforce. Variance analyses will be required for those PWCs
(cumulative to date and monthly) as follows:

All variances greater than \$1 Million

All variances +/- 10% and over \$100K

> The cost elements shall be reported as follows:

a\. Direct and indirect elements of cost, fee, subtotal price,
anticipated changes with fee and total price at WBS level 2 and lower
levels as directed for specific areas of the WBS.

b\. Equivalent personnel (EP) at WBS level 3 and lower level as directed
for specific areas. EP's shall be reported for column 7a (current month
actuals) and column 8a (next month's estimate).

c\. Price will be reported at WBS level 3 and lower levels as directed
for specific areas.

d\. Price performance summary narratives at WBS level 4 and lower levels
as directed for specific areas. The narratives shall include cost
performance variance analyses and recovery plans. Variance Analyses will
be required for actual cost incurred versus plan (negotiated baseline)
as follows:

All variances greater than \$1 Million

All variances +/- 10% and over \$100K

> For WBS 1.1.6.1, Facilities, projects greater than \$500,000 shall be
> reported uniquely using the NASA project identification number and
> title. The project identification number will have a suffix of P for
> Preliminary Engineering Report, D for Design, or C for Construction.
> (The preceding requirements are being satisfied by SFOC DRD's
> 1.1.2.1-b, Resources Reporting Management System (FMS) and the project
> reporting activities outlined in the SFOC Facility Management Plan DRD
> 1.1.6.1-a.)
>
> Example: 95001 - P - Repair Roof - Building 1
>
> 95001 - D - Repair Roof - Building 1
>
> 95001 - C - Repair Roof - Building 1
>
> The report will include a subtotal line for all projects valued at
> \$500K and over.
>
> A summary cost report split by suffix is required for projects valued
> at less than \$500K, except that all environmental specific projects
> shall be reported at the project level.
>
> A total line will be used which includes all of the facility projects.

Any cost that is not reported within 60 days of the completion of the
project should also be explained.

13.4 **[FORMAT]{.underline}**: These reports shall be prepared in
accordance with NPG 9501.2C and NFS 1852.242-73, and be provided in hard
copy form.

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

-   

-   

-   

-   

-   

-   

-   

-   

-   5.  DATA REQUIREMENTS DESCRIPTION (DRD)

        1\. [DPD NO.]{.smallcaps}: 821 [ISSUE:]{.smallcaps} REVISION
        1 2. [DRD NO.]{.smallcaps}: 1.1.2.1-b

        3\. [DATA TYPE]{.smallcaps}: Initial Submission: 1 4. [DATE
        REVISED: 09/01/98]{.smallcaps}

        Subsequent Submissions: 3 5. [PAGE]{.smallcaps}: 1/2

        6\. [TITLE]{.smallcaps}: Resources Management Reporting System

        7\. [DESCRIPTION/USE]{.smallcaps}: To provide resources
        management reports for planning, monitoring, and controlling
        project resources based on the NASA budget with respect to
        program operating plans (POP), fiscal year operating plans,
        monthly plan vs. actual statusing, and any special request
        reporting as specified by NASA.

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

        9\. [INITIAL SUBMISSION]{.smallcaps}:

        POP - TBD (Reference section 13.3 of this DRD - a, b, c, d, e,
        f, g, h, i) Operating plan - TBD (Reference section 13.3 of this
        DRD - a, b, c, d, e, f, g, h, i) Plan vs. actual status - No
        later than the 15^th^ calendar day of the month in which ATP is
        issued.

        10\. [SUBMISSION FREQUENCY]{.smallcaps}:

        POP - as required (Reference section 13.3 of this DRD - a, b, c,
        d, e, f, g, h, i)

        Operating plan - as required (Reference section 13.3 of this
        DRD - a, b, c, d, e, f, g, h, i)

        Plan vs. actual status - only required if the approved FY
        Operating Plan differs from the Contract Value Baseline Plan
        required for DRD 1.1.2.1-a. If required, then submission will be
        monthly, by the 15^th^ working day, but no later than the 23^rd^
        calendar day, of the calendar month following the end of the
        contractor's accounting month accounting month (Reference
        section 13.3 of this DRD - a, g, h, i, j, k).

        Special requests - as required

        11\. [REMARKS]{.smallcaps}:

        12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.1.1., 1.1.2.1;
        DRD's 1.1.1.1 - a & b, 1.1.2.1 - a & c, 1.1.2.2 - a & b. All
        data shall be reconcilable between the resources management
        reports, the NASA Forms 533M and 533Q (DRD 1.1.2.1 - a), and the
        Performance Measurement System (DRD 1.1.2.2 - a & b)

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

        13.1 [[SCOPE]{.underline}]{.smallcaps}: These reports shall be a
        source of Contractor program operating plans, fiscal year
        operating plans, monthly plan vs. actual statusing, and any
        special request reporting as specified by NASA. Source data
        shall be at the lowest level collected by the contractor. Data
        to be reconcilable to the contract value.

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

        13.3 [[CONTENTS]{.underline}]{.smallcaps}: The contents of the
        report will generally include the following elements; however,
        additional data may be included to meet specific guidelines:

        a\. Price (labor/non-labor separately identified) and workforce
        (e.g. - headcount, EP)

        b\. Direct and indirect rate assumptions

        c\. Workforce/non-labor requirements assumptions

        d\. Statement of work/task descriptions (required for selective
        WBS(s) only)

        e\. Product detail for tasks -product listing with DRD number,
        schedule delivery date (required for selective WBS(s) only)

        f\. Schedule assumptions

        g\. Sort by TMR

        DRD CONTINUATION SHEET

        TITLE: Resources Management Reporting System DRD NO: 1.1.2.1-b

        DATA TYPE: Initial Submission: 1 PAGE: 2/2

        Subsequent Submissions: 3

        [13. DATA PREPARATION INFORMATION (CONTINUED):]{.smallcaps}

        13.3 [CONTENTS (CONTINUED):]{.underline}

        h\. NASA specific primary work codes (PWC's), including but not
        limited to the following:

```{=html}
<!-- -->
```
-   Orbiter & Integration Operations (250-10)

-   Propulsion (250-40)

-   Mission and Launch Operations (250-90)

-   MEDS (260-03)

-   Orbiter Improvements (260-10)

-   Flight Operations and LSE Upgrades (260-90)

-   CLCS (260-96)

-   Advanced Control Center Technical Support (260-98)

-   Station Development (475-00)

-   Station Government Furnished (477-72)

-   Station ISS Configuration Management (478-11)

-   Payload Training Complex (479-42)

-   Station Operations - Logistics & Maintenance (575-13)

-   Station Operations - Planning & Cargo Integration (575-14)

-   Station Operations - Sustained Engineering (575-15)

-   Station Operations - Support (575-81)

-   Station Operations - Launch Site Processing (575-82)

-   ICM Implementation (599-20)

-   Station/Shuttle Integration (580-00)

-   Shuttle Orbiter MIR Support (508-20)

-   Shuttle Integration MIR Support (508-30)

-   RLV Ground Based Program (242-20)

-   Advanced Space Trans. Operation/Software Tech. (242-40)

-   Payload Processing and Support (264-00)

-   Advanced Space - EVA Optional Services (906-30)

-   Spacelab (926-22)

-   Payload Utilization (947-88)

-   Construction of Facilities (Cof F)

-   Other NASA Programs (RE-ONP)

-   Reimbursables - Non NASA Programs (RE-NNP)

i\. Variance analysis (cumulative to date and monthly)

All variances greater than \$1 million

All variances +/-10% and over \$100K

j\. Periodic year-end analysis

k\. Other (Master Control Record, Operations Centers, etc.)

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
Government-approved style and layout formats per DRD 1.1.4.1-e, Data
Management Plan, or per Contracting Officer approval. Electronic data
shall be formatted and delivered per Government standards as specified
in section J-5, paragraph 2.5, or per Contracting Officer approval. In
cases where format requirements conflict, Contractor shall obtain
resolution from Contracting Officer.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** [REVISION
3]{.smallcaps} 2. **[DRD NO.]{.smallcaps}**: **1.1.2.1-d**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED:
12/02]{.smallcaps}**

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

6\. **[TITLE]{.smallcaps}**: Energy Utilization and Consumption Report

7\. **[DESCRIPTION/USE]{.smallcaps}**: This report shall serve as a
source of information for direct charges to the appropriate programs or
other users. The energy consumption data included in this report will
serve as a metric for energy reduction goals. This report will also be a
source of information for each Center's Energy Efficiency and Water
Conservation Plans and Progress Assessments submitted by each NASA
Center annually.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: 30 days after Authority to
Proceed (ATP)

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: DRD submissions consist of
Monthly, Quarterly, and Annual reports. The Annual serves in place of
the Quarterly report for the 4^th^ Quarter and serves in place of the
Monthly for month of September (Sept. data to be included in annual).
The Quarterly reports serve in place of the Monthly for December, March,
and June with data for those month's included in the Quarterly reports.
Monthly reports shall be submitted in October, November, January,
February, April, May, July, and August. As such, there will be 12
submissions annually comprised of 1 Annual, 3 Quarterlies, and 8
Monthlies. Submissions shall be published by the end of the following
month.

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

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: This report shall identify
and document essential energy utilization and cost data on which NASA
can base energy management and conservation decisions. In addition, data
from this report will be utilized for the purpose of energy cost phasing
and as a metric for contractor performance in the area of energy
management. The report shall include a subset of data for each location
(i.e. KSC/Launch Operations, Downey, Palmdale, JSC, etc., as required).
Certain data requested may be site specific as defined below.

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

NASA Procedures and Guidelines (NPG) 8570.1

Energy Efficiency and Water Conservation Technologies and Practices

10 CFR 434

10 CFR Part 436

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The contractor shall, as
a minimum, submit the following parts:

a\. Energy Consumption Report: Report by commodity volume and
consumption per gross square foot. (KSC cost data will be based on rate
information provided by the institution contractor.)

[Frequency]{.underline}: Monthly\--Individual Facility Consumption
(where metered): metered electricity and fuel consumption, and cost for
individual govt. owned facilities.

[Frequency]{.underline}: Quarterly---accumulative consumption for the
quarter.

b\. Variance Analysis: Comparisons shall be made between the planned and
actual electricity, fuel, propane and natural gas consumption and cost.
Includes a narrative explaining all factors (new facilities, rate
changes, energy conservation measures, increased processing, etc.) that
have impacted the totals, when compared to the same time period of the
previous year.

[Frequency]{.underline}: Quarterly

DRD CONTINUATION SHEET

**[TITLE]{.smallcaps}**: Energy Utilization and Consumption Report
**[DRD NO.]{.smallcaps}**: **1.1.2.1-d**

**[DATA TYPE]{.smallcaps}**: 3 **[PAGE]{.smallcaps}**: 2/2

[13.]{.smallcaps} [**DATA PREPARATION INFORMATION
(CONTINUED)**:]{.smallcaps}

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

c\. Forecasts: The forecasts shall support the budget cycle and include
the current fiscal year and the four succeeding fiscal years. These
forecasts, (excluding facilities that are reimbursable to NASA), shall
project consumption and cost for electricity, fuel oil #2, propane and
natural gas. The forecast shall include a listing and description of the
projects or activities which may significantly impact (positively or
negatively) energy consumption. (The institution contractor will provide
fuel consumption data to the SFOC at KSC.)

[Frequency]{.underline}: Quarterly (KSC only)

[Frequency]{.underline}: Annually (all others)

d\. Energy Projects and Initiatives: Status of current energy projects
and initiatives with implementation costs in excess of See Note. As a
minimum, each entry shall include a project description, point of
contact, planned-versus-actual cost estimate, planned and actual energy
and cost avoidance (in base units, BTU's, and dollar), and planned and
actual completion dates. Actual energy and cost avoidance data shall be
reported for the first two years after project is complete.

[Frequency]{.underline}: Quarterly

e\. Annual Report and Compliance Summary: Shall list and describe
accomplishments (including implemented energy conservation measures and
initiatives, with measured energy savings) from the preceding fiscal
year. Also, graphical and tabular data shall be shown to compare
planned-versus-actual energy consumption, consumption per gross square
foot, and cost. Tabulations shall also include actual energy reduction,
for the past 12 months, from the baseline year (presently 1985). Any
adjustments necessary to the baseline year shall be fully justified and
documented.

[Frequency]{.underline}: Annually

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.1.2.1-e**

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

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

6\. **[TITLE]{.smallcaps}**: On-site and Off-site Headcount Report

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide on-site and off-site
headcount data which is used to provide NASA headquarters required
workforce reports and for future planning for housing requirements.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: January 17, 1997

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Quarterly, by the 17th of
the month

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

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: This report provides on-site
and off-site end-of-quarter headcount data containing the breakouts
shown under 13.3 for each NASA Center.

[Definition of Terms]{.underline}

> a\. [On site]{.underline} - Those personnel performing on the contract
> occupying physical space on a NASA Center. KSC includes Cape Canaveral
> Air Force Station (CCAFS). It includes those personnel temporarily
> absent from assigned duty stations (e.g., on leave without pay,
> annual/sick leave, TDY).
>
> b\. [Off site]{.underline} - Total of those personnel on the contract
> but physically located outside the environs of a NASA Center.
>
> 1\. [Dispossessed]{.underline} - Those personnel who normally would
> occupy physical space within the environs of a NASA Center, but who
> have been located outside due to nonavailability of space.
>
> 2\. [Others off-site]{.underline} - Those personnel within total
> contract headcount who are not planned to occupy physical space within
> the environs of a NASA Center.
>
> c\. [Construction subcontractors]{.underline} - Those personnel
> performing on the contract within the environs of a NASA Center.
> Include a brief description or title of the effort.

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

KMI 1710.1 *Center-wide Manpower Reports*

DRD Continuation Sheet

**[TITLE]{.smallcaps}**: On-site and Off-site Headcount Report **[DRD
NO.]{.smallcaps}**: **1.1.2.1-e**

**[DATA TYPE]{.smallcaps}**:4 **[PAGE]{.smallcaps}**: 2/2

13\. DATA PREPARATION INFORMATION (CONTINUED):

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

+--------------------------+-----------+------------+---------+-------+
| **END OF QUARTER         |           |            |         |       |
| CONTRACTOR HEADCOUNT     |           |            |         |       |
| REPORT**                 |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+
| CONTRACT                 | ON-SITE   | OFF-SITE   | O       | TOTAL |
|                          |           | DI         | FF-SITE |       |
|                          |           | SPOSSESSED | OTHER   |       |
+--------------------------+-----------+------------+---------+-------+
| TOTAL PER NASA CENTER    |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+
| PRIME                    |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+
| TOTAL OF SUBCONTRACTORS  |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+
| SUBTOTAL OF              |           |            |         |       |
| SUBCONTRACTORS           |           |            |         |       |
|                          |           |            |         |       |
| (Other than              |           |            |         |       |
| constructions            |           |            |         |       |
| subcontractors)          |           |            |         |       |
|                          |           |            |         |       |
| List each subcontractor  |           |            |         |       |
|                          |           |            |         |       |
| (Include only those with |           |            |         |       |
| on-site personnel)       |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+
| SUBTOTAL OF CONSTRUCTION |           |            |         |       |
| SUBCONTRACTORS           |           |            |         |       |
|                          |           |            |         |       |
| List each construction   |           |            |         |       |
| subcontractor            |           |            |         |       |
+--------------------------+-----------+------------+---------+-------+

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** Revision 2]{.smallcaps}
2. **[DRD NO.]{.smallcaps}**: **1.1.2.1-f**

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

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

6\. **[TITLE]{.smallcaps}**: Geographical Economic Impact Report

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide cost and workforce
geographical economic impact data which is used to respond to NASA and
Congressional requests.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: January, 1997

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Annually, 15 working days
after request for report.

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.1.2.1; data shall be
reconcilable to end of fiscal year NASA Forms 533M.

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The Geographical Economic
Impact Report provides actual SFOC total cost and workforce geographical
economic impact data for each fiscal year per the breakouts shown under
13.3, or as modified by request.

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

KMI 1710.1 *Center-wide Manpower Reports*

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

+-----------------------------------+----------------+----------------+
| **Location and Performer**        | Workforce      | Total Cost     |
|                                   | (DEQs\*)       | (\$K)          |
+-----------------------------------+----------------+----------------+
| Each NASA Center                  |                |                |
|                                   |                |                |
| Prime                             |                |                |
|                                   |                |                |
| Each Subcontractor                |                |                |
|                                   |                |                |
| Each major vendor                 |                |                |
|                                   |                |                |
| Others as required                |                |                |
+-----------------------------------+----------------+----------------+
|                                   |                |                |
+-----------------------------------+----------------+----------------+
| Each State                        |                |                |
|                                   |                |                |
| Prime                             |                |                |
|                                   |                |                |
| Each Subcontractor                |                |                |
|                                   |                |                |
| Each major vendor                 |                |                |
|                                   |                |                |
| Others as required                |                |                |
+-----------------------------------+----------------+----------------+
| Each Country                      |                |                |
|                                   |                |                |
| Prime                             |                |                |
|                                   |                |                |
| Each Subcontractor                |                |                |
|                                   |                |                |
| Each major vendor                 |                |                |
|                                   |                |                |
| Others as required                |                |                |
+-----------------------------------+----------------+----------------+

\*DEQ = Direct Full-time Equivalents

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** Revision 2]{.smallcaps}
2. **[DRD NO.]{.smallcaps}**: **1.1.2.1-f**

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

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

The following is a KSC Specific Report that may be requested separately
from the rest of the data requirements outlined in this document.

+------------------------------------------+---------------------------+
| ### Florida Contracts and Purchases      | Totals (\$)               |
+------------------------------------------+---------------------------+
| # Amount Spent in Brevard County         |                           |
|                                          |                           |
| USA-Florida Labor                        |                           |
|                                          |                           |
| Contractors Operating On-site at KSC     |                           |
|                                          |                           |
| Off-site Businesses in Brevard County    |                           |
|                                          |                           |
| # Brevard Subtotal                       |                           |
+------------------------------------------+---------------------------+
|                                          |                           |
+------------------------------------------+---------------------------+
| Amount Awarded to Florida Businesses     |                           |
| Outside Brevard                          |                           |
+------------------------------------------+---------------------------+
| # Florida Totals                         |                           |
+------------------------------------------+---------------------------+
| Out of State Totals                      |                           |
+------------------------------------------+---------------------------+
| ## GRAND TOTALS                          |                           |
+------------------------------------------+---------------------------+

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

**1. DPD NO.: ISSUE:** BASIC **2. DRD NO.: 1.1.2.1-g**

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

**5: PAGE: 1/1**

**6. TITLE:** Notification of Potential Labor Dispute and Contingency
Strike Plan

**7. DESCRIPTION/USE:** The Notification of Potential Labor Dispute and
Contingency Strike Plan will be used by the NASA Contracting Officer and
the Industrial Labor Relations Office to facilitate the coordination of
activities between the contractor and the affected NASA operational
directorates to ensure that necessary steps are taken to prepare for any
potential strike situations and to prevent the disruption of work.

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

**9. INITIAL SUBMISSION:** In accordance with 13.1.

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

**11. REMARKS:**

**12. INTERRELATIONSHIP:** FAR 52.222.1

**13. DATA PREPARATION INFORMATION:**

**13.1 [SCOPE]{.underline}:** A Notification of Potential Labor Dispute
must be submitted at the first indication of potential labor unrest
which could delay the timely performance of the contract. The
Notification shall describe the situation which has the potential of
impacting the contract and describe the corrective action initiated. A
Contingency Strike Plan must be submitted 45 calendar days prior to the
expiration of any collective bargaining agreement covering employees
working under this contract for the prime and any subcontractors and/or
immediately following any indication of potential labor unrest.

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

**13.3 [CONTENTS:]{.underline}** The Notification of Potential Labor
Dispute shall describe the situation which has the potential of
impacting the timely performance of the contract and describe the
corrective action initiated. Notification should be made prior to the
expiration of collective bargaining agreements, prior to any significant
changes to existing working conditions or pay practices, or any
situation which could impact the performance of the contract through
labor unrest. The Contingency Strike Plan shall describe the
contractor's plan for assuring the timely performance of the work under
this contract during a strike or work stoppage situation. As a minimum,
contents should include; information on implementation of the strike
plan, a pre-strike checklist for managers and supervisors, a description
on how critical work will be performed, phone numbers of key management
personnel, and standards of conduct policies during the strike.

**13.4 [FORMAT:]{.underline}** Contractor format is acceptable.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

**1. DPD NO.: ISSUE:** BASIC **2. DRD NO.: 1.1.2.1-h**

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

**5: PAGE: 1/4**

**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:** July 1, 1997

**10. SUBMISSION FREQUENCY:** Annually, on July 1

**11. REMARKS:**

**12. INTERRELATIONSHIP:** SOW 1.1.2.1 and 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:]{.underline}** The Wage/Salary and Fringe Benefit Data
should contain the data included in the enclosed DRD forms, titled
"Wage/Salary Rate Information", "Fringe Benefits 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.

**13.4 [FORMAT:]{.underline}** The Wage/Salary and Fringe Benefit Data
should be in a format substantially the same as enclosed with this DRD.

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

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

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\. Severance 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

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)

TOTAL

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\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 2]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.1.2.2-a

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 01/2002]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Performance Measurement System Reports
(Development and Production)

7\. [DESCRIPTION/USE]{.smallcaps}: To provide technical, cost and
schedule performance summary and assessment based on an earned value
performance measurement system for development and production
activities.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: 6 months after contract Authority
to Proceed (ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: No later than the 25^th^ day of
the calendar month.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.1.1, 1.1.2.1, 1.1.2.2;
DRD's 1.1.1.1-b & 1.1.2.1-a; and clause H.31. All data shall be
reconcilable between the NASA Forms 533M & 533Q (reference DRD
1.1.2.1-a) and the Performance Measurement System (PMS) Reports.

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

13.1 [[SCOPE]{.underline}]{.smallcaps}: The reports shall provide
technical, cost, and schedule performance data and assessments and shall
serve as the basis for contractor communication with NASA concerning
earned value performance management.

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

*NPD 9501.3, Attachment A*

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

The PMS system and reporting shall be in accordance with Attachment A of
NASA Policy Directive 9501.3, dated February 18, 1997. The definition of
cost accounts is to be mutually agreed upon by the contractor and NASA.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue. G-1, G-2,
and G-3

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 3]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.1.2.2-b

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 01/2002]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Performance Measurement System Reports
(Operations)

7\. [DESCRIPTION/USE]{.smallcaps}: To provide technical, cost and
schedule performance summary and assessment based on a performance
measurement system for all operations activities (i.e.,
non-development/non-production activities).

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

9\. [INITIAL SUBMISSION]{.smallcaps}: Following first full month of
performance after contract Authority to Proceed (ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: No later than the 25^th^ day of
the calendar month.

11\. [REMARKS]{.smallcaps}: In addition to the mutually agreed upon
metrics provided routinely by this DRD, NASA will have access to lower
level contractor metrics for audits and insight into problem areas.

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.1.1, 1.1.2.1, 1.1.2.2;
DRD's 1.1.1.1-b & 1.1.2.1-a; and clause H.31. All data shall be
reconcilable between the NASA Forms 533M & 533Q (reference DRD
1.1.2.1-a) and the Performance Measurement System (PMS) Reports.

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

13.1 [[SCOPE]{.underline}]{.smallcaps}: The reports shall provide
technical, cost, and schedule performance data and assessments and shall
serve as the basis for contractor communication with NASA concerning
performance management.

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

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

General: The PMS data and baseline updates shall be reported by
significant third level WBSs as agreed between the contractor and the
appropriate NASA TMRs. Changes or additions shall be by mutual agreement
between the contractor and NASA. Provisions shall be made to separately
identify, account for, and forecast resource requirements for special
projects. The following report packages shall be provided:

a\. [SFOC Program Overview Status]{.underline} - Provide an overall
program status in brief narrative form, indicating the progress on all
major items. Include summary status of technical, schedule, and cost
performance. Identify any significant problems and corrective actions.

b\. [Performance Metrics Packages]{.underline} - Provide metrics as
agreed between the contractor and the NASA TMRs that reflect the key
areas of concern for performance.

\(1\) Metrics will address safety, quality, work content, schedule,
efficiency, cost, and other areas, as appropriate.

\(2\) Variance analysis for each metric for deviations beyond
established thresholds shall be provided. In addition, corrective
actions will be enumerated for unfavorable variances beyond established
thresholds.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
[**DRD NO**.]{.smallcaps}: **1.1.3.2-a**

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

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

6\. **TITLE:** Small, Small Disadvantaged, and Women-Owned Small
Business Subcontracting Report

**[7. DESCRIPTION/USE]{.smallcaps}**: To report contractor's efforts and
progress toward meeting the contractor's small, small disadvantaged, and
women-owned small business subcontracting goals established in Clause
G14.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: November 15, 1997

**[10. SUBMISSION FREQUENCY]{.smallcaps}**: Quarterly, due no later than
the 45^th^ day after the close of the quarter.

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: Clause G.14

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

[13.1 **[SCOPE]{.underline}**]{.smallcaps}: To document prime contract
and subcontractor efforts and progress to foster subcontracting
opportunities for small, small disadvantaged, and women-owned small
businesses.

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

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

a\) Metrics - The report will provide the contractor's metrics providing
actual expenditures for the preceding quarter, inclusive of lower-tier
subcontractor actuals. Breakdown will include metrics by category as
indicated in G. 14.

b\) Reporting of actions taken and a description of efforts expended by
contractor and subcontractors toward enhancing small business, small
disadvantaged business, and women-owned business utilization.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
[**DRD NO**.]{.smallcaps}: **1.1.3.2-b**

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

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

6.  **[TITLE]{.smallcaps}**: Small, Small Disadvantaged and Women-Owned
    Small Business

Subcontracting Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: To update the contractor's
subcontracting plan in accordance with FAR 19.702(a)(1).

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: February 1, 1998

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Semiannually on February
1^st^ and August 1^st^ of each year. The revision submitted on February
1^st^ shall incorporate all reportable actions from July 1^st^ to
December 31^st^ of the previous year. The revision submitted on August
1^st^ shall incorporate all reportable actions from January 1^st^ to
June 30^th^ of the present year. A reportable action is defined as a
modification to NAS 9-20000 which increases the contract value by
greater than \$500,000.

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: Clause 52.219-9

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: To document prime contract
and subcontract efforts to foster subcontracting opportunities for
small, small disadvantaged, and women-owned small businesses.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The contents of the
revised subcontracting plan shall be in accordance with paragraph (d) of
FAR clause 52.219-9.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.1.4.1-a

3\. [DATA TYPE]{.smallcaps}: 2 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

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

7\. [DESCRIPTION/USE]{.smallcaps}: To provide a description of the
contractor's information system.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: Preliminary 90 days after
Authority to Proceed (ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Final submittal for baselining
one year after ATP, updated utilizing the same schedule for Phase II and
Phase III

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.4.1 and clause H.19

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

13.1 [SCOPE]{.underline}: The Information Management Plan describes the
entire information system and the contractor\'s overall implementation
of the data management requirements specified in the contract as
integrated by the prime contractor and subcontractors and as planned for
each phase of contracted activity.

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

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Information Management
Plan shall contain the following sections:

a\. Information System: This section shall describe the information
flows and requirements analysis and functional requirements in the
following areas: network communications, electronic mail, scheduling
system, documentation system, budget planning, engineering databases,
CAD/CAE, teleconferencing/video conferencing, workstations, user
support, management information center(s), maintaining current status,
and configuration management data bases. Also, this section should
include the system architecture design, implementation schedules, and
resource requirements.

b\. Conversion to Commercial Off-the-Shelf (COTS) Systems: This section
shall identify alternative COTS management information systems (MIS) to
be substituted for non-COTS MISs pursuant to clause H.19, Access to
Contractor Data, and implementation plans. This shall include system
descriptions, rationale for the COTS system identified as a replacement
(or, as appropriate, for not replacing the non-COTS system), schedule,
estimated cost, impact on the Shuttle Program and related MISs
occasioned by the conversion, and how negative impacts will be
mitigated.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor format is
acceptable.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** [Rev.
2]{.smallcaps} 2. **[DRD NO.]{.smallcaps}**: **1.1.4.1-b**

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

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

6\. **[TITLE]{.smallcaps}**: Information Technology (I/T) Plan and
Reports

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document the contractor\'s
compliance with Federal and NASA Information Technology (I/T) Planning
and Reporting regulations and requirements

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**:

\(a\) I/T plans are required prior to any I/T acquisition.

\(b\) I/T standards plan submittals are required prior to the submittal
of any I/T plans.

\(c\) Initial I/T inventory report submittals are due on February 1,
1997.

\(d\) Initial security reports and Master Plan submittals are due at
contract authority to proceed plus 90 days.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: I/T plans are required
twice annually (POP-1 and POP-2 timeframes), I/T inventory reports are
required upon request but no more than once annually. Security reports
are required as specified in the JSC I/T Security Handbook (JPG 2810.1).

11\. **[REMARKS]{.smallcaps}**: I/T plans and reports shall be presented
to the Space Shuttle Program (SSP) Chief Information Officer (CIO) for
subsequent submittal to the JSC CIO.

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.1.4 and 1.6.4, and
clause H.11

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

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

13.2 **[[REFERENCE DOCUMENTS]{.underline}]{.smallcaps}**:

a\) Current JSC CIO instructions/guidelines for I/T Plans. As of the
contract start date, the JSC CIO instructions include the following:

1\) JSC memorandum AI-95-090 dated July 11, 1995, subject: Information
Technology (I/T) Plans.

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

3\) JSC memorandum AI-96-020 dated March 18, 1996, subject: \"FY97
Information Technology Plans\".

4\) JSC memorandum AI-96-033 dated April 22, 1996, subject: \"Reminder
and Clarification on Information Technology (I/T) Orders or Acquisition
Reviews\".

5\) 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\) JSC Information Technology Architecture Handbook (JHB 2410.15).

i\) I/T Management Reform Act of 1996 (the \"Cohen Bill\")

DRD CONTINUATION SHEET

**[TITLE]{.smallcaps}**: Information Technology Plan and Reports **[DRD
NO.]{.smallcaps}**: **1.1.4.1-b**

**[DATA TYPE]{.smallcaps}**: 1/3 **[PAGE]{.smallcaps}**: 2/2

[13.]{.smallcaps} [**DATA PREPARATION INFORMATION
(CONTINUED)**:]{.smallcaps}

> 13.3 **[[CONTENTS]{.underline}]{.smallcaps}**:
>
> a\) [NO LONGER REQUIRED AS OF May 1, 2002:]{.underline} For JSC MOD
> managed facilities, provide a Master Plan that is a consolidated,
> 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).
> **Data type: 1**
>
> b\) An annual, contract-wide I/T Plan, per current JSC CIO
> instructions/guidelines. For FY97 requirements, refer to the FY97 I/T
> Planning Process "Road Show" available on the JSC CIO home page:

1\) In concert with the POP-1 each year, a high-level (Level A) 5-year
plan is required. This plan will define and justify the major I/T
initiatives planned for each of the 5 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. **Data type: 1**

> 2\) In concert with the POP-2 each year, a more detailed Level B I/T
> Plan for the "next" FY only is required. Level B will describe I/T
> purchases by platform standards (in support of approved Level A
> initiatives) to be acquired during the year. **Data type: 1**
>
> 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. **Data type: 1**

c)  

> d\) I/T inventory reports from available data according to NASA CIO
> Executive Notices. (Data type: 3)
>
> 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 I/T inventory reports from available
> data according to NASA CIO Executive Notices. As a minimum, the
> reports shall include the types and frequencies of those required by
> the NASA Center under whose guidance the system is operated (**Data
> Type: 3**).
>
> 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 has 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]{.smallcaps} **[[FORMAT]{.underline}]{.smallcaps}**: Contractor
shall conform to delivery media formats and electronic data formats per
DRD 1.1.4.1-e, Data Management Plan, or per Contracting Officer
approval.

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

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

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

                                                     

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

DRD CONTINUATION SHEET

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

                                                     

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

a.  

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.1.4.1-c

3\. [DATA TYPE]{.smallcaps}: 4 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Data Accession List

7\. [DESCRIPTION/USE]{.smallcaps}: To provide an index of data that is
available on request. It is a medium for identifying contract internal
data which have been generated by the contractor in compliance with the
work effort described in the statement of work and other contract
requirements.

10\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

11\. [INITIAL SUBMISSION]{.smallcaps}: 30 days after contract award

12\. [SUBMISSION FREQUENCY]{.smallcaps}: Quarterly

13\. [REMARKS]{.smallcaps}:

14\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.4.1 and clause H.19

15\. [DATA PREPARATION INFORMATION]{.smallcaps}:

15.1 [[SCOPE]{.underline}]{.smallcaps}: The Data Accession List shall be
a cumulative listing of all contractor-generated documentation.

> 15.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}: None

15.3 [[CONTENTS]{.underline}]{.smallcaps}: The Data Accession List shall
provide a listing of all data requirement response documentation plus
other project-pertinent documents including drawings through the fourth
generation breakdown level. The format and content of these data shall
be prepared by the contractor to document compliance with the statement
of work and other contract requirements. The list shall be a cumulative
listing of contractor-generated data response documentation generated to
date, data released during the past quarter, and data submitted to NASA.
In addition to other types of data, the list shall reflect type 4 and 5
project documentation not otherwise covered by specific DRD's and shall
describe procedures for obtaining the listed information. The list shall
include a cross-reference to the related section of the statement of
work, number and document identification (DRD number if applicable),
document number, title, date, and revision.

15.4 [FORMAT:]{.underline} Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

15.5 [MAINTENANCE]{.underline}: On-line access to the data listing can
be provided in lieu of hard copy listings.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.1.4.1-d**

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

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

6\. **[TITLE]{.smallcaps}**: Reprocurement Data Package

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide for maintenance of
reproducible masters of updated technical and process documentation.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: As required

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

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: Clause H.30, Incorporation of
Phase II contracts

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

13.1 **[SCOPE]{.underline}**: This requirement encompasses all technical
and process documentation agreed to by the parties as necessary for this
Reprocurement Data Package.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The Reprocurement Data
Package shall include reproducible masters of the following
documentation, with the understanding that this list will be updated as
Phase II contracts are transitioned into SFOC:

[DOCUMENTATION]{.underline} [DRD OR IRD]{.underline}

[Program Plans]{.underline}

a\. Management Plan 1.1.1.1-a

b\. Government Property Management Plan 1.1.1.1-h

c\. Information Management Plan and Reports 1.1.4.1-a

d\. Configuration Management Plan 1.1.5.1

e\. Verification Management Plan 1.1.5.2-a

f\. Space Flight Operations Product Development Plans 1.1.1.1-f

g\. Space Flight Operations Transition Plan 1.1.1.1-c

Interface Control Documents (ICD\'s)

h\. Interface Revision Notice (IRN) to Element Interface Control
Documents (ICD\'s) 1.2.2.5

i\. Payload Interface Control Documents (ICD\'s and Installation
Requirements 1.2.2.5

Documents (IRD\'s)

j\. Primary Avionics Software System (PASS)/Backup Flight System (BFS)
1.4.3.3-p

Interface Control Documents (ICD\'s)

k\. Interface Control Documents 1.6.4-c

l\. MSFC Interface Control Document (ICD) Contractual Index and Status
SE-1697T9

DRD Continuation Sheet

**[TITLE]{.smallcaps}**: Reprocurement Data Package **[DRD
NO.]{.smallcaps}**: **1.1.4.1-d**

**[DATA TYPE]{.smallcaps}**: 4 **[PAGE]{.smallcaps}**: 2/2

Engineering Drawings and Specifications

m\. Acceptance Data Package (ADP) (one for each vehicle) 1.3.3.1

n\. Master Measurement Lists (MML) (most recent at time of request)
1.4.1.6.1-f

o\. Equipment Inventory Report 1.4.9.2

p\. Systems Products Handbook & Product Glossary 1.6.2.3-d

q\. KSC Work Authorization Documents (Category I) 1.4-c

r\. Facility and Equipment Maintenance Plan and Supporting Data 1.5.5.2

s\. Shuttle Ground Processing Plans/Instructions 1.1.1.1-j

t\. Logistics Performance Reports 1.4-c

u\. Ground Support Equipment Inventory Report MA-605T9

v\. Vehicle Integrated Schematics OM-029T9B

w\. Subcontractor Engineering Drawings & Associated Lists for GSE
OM-226T9A

x\. Critical Items List (CIL) RA-364T9A

y\. Failure Mode Effects Analysis (FMEA) RA-267T9A

z\. EEE Parts As-Designed (Where Used) & Qualifications Status
Electronics RA-271T9A

Database

aa. EEE Part Drawings and Specifications RA-273-T9B

ab. Thermal Protection System (TPS) Maintenance Specifications \`
SE-1866T9A

ac. Space Shuttle System Drawing Reports SE-1933T9B

ad. Drawing, Orbiter/ISS Avionics Control Schematic SE-2018T9

ae. Engineering Drawings & Associated Lists SE-497T9A

af. Subcontractor Engineering Design Drawings & Associated Lists
SE-566T9

ag. Master Dimensions Specification (MDS) Manual SE-873T9

ah. Vehicle End Item (VEI) Specification TM-258T9

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Various formats, in
accordance with the DRD\'s under which the documentation is generated.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Documentation included
in this package shall be maintained current, in accordance with the
DRD\'s under which the documentation is generated.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.1.4.1-e

3\. [DATA TYPE]{.smallcaps}: 2 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

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

7\. [DESCRIPTION/USE]{.smallcaps}: To provide a description of the
contractor's tracking system.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: Preliminary 90 days after
Authority to Proceed (ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Final submittal for baselining
one year after ATP, updated utilizing the same schedule for Phase II and
Phase III

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.4.1 and clause H.19

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

13.1 [SCOPE]{.underline}: The Data Management Plan describes the
contractor\'s overall implementation of the data management requirements
specified in the contract as integrated by the prime contractor and
subcontractors and as planned for each phase of contracted activity.

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

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Data Management Plan
shall contain the following sections:

> a\. Data Management: This section shall define the scope and depth of
> the contractor's efforts including management, organization, planning,
> and the relationship of the data management program to the
> contractor\'s other administrative and technical organizations. The
> plan shall specify the contractor\'s management policies and identify,
> by specific reference, standard practices and detailed work
> instructions to be used in implementing the data management program.
> The plan shall include the following elements: management
> organization, control procedures, storage and retrieval procedures,
> subcontractor control procedures, and special restrictions. The plan
> shall include a preliminary data submittal schedule for fulfilling
> submittal of data in the specified quantities, specific media
> (electronic, paper, other), and due dates required.
>
> b\. Document Development: This section defines the procedures,
> policies, and formats used to produce and distribute document contract
> deliverables. The section shall include specifics on document
> numbering schema; and shall reference the contractors\' documentation
> which are used to define internal layout and format requirements, and
> specific document setup practices that ensure appropriate hard-copy
> and/or electronic output.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor format is
acceptable.

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

**NASA Year 2000**

**Quarterly Status Report**

**For May 15 Report**

**[Section A. Metrics Information]{.underline}**

**A1. Inventory of Mission Critical Systems and Non Mission Critical
Systems**

This very large spreadsheet titled, "Inventory" includes all Mission
Critical (MC) and Non-Mission Critical (NMC) systems which are being
repaired, retired, or replaced.

Update the "Systems Inventory" spreadsheet to reflect current
information. For mission critical systems, columns B to AJ must be
updated. For non-mission critical systems, columns B to Y, and column AJ
must be updated. For non-mission critical systems, cost per system is
not required.

Highlight any changed cells in COLOR. In a separate narrative, describe
significant changes, if any, from previous quarter submission
(additions, deletions, deviations or changes to planned and actual
schedule or costs).

**A2. Inventory of Compliant Systems**

The spreadsheet titled, "Compliant MC" includes all mission critical
systems which were initially assessed as Y2K compliant. The spreadsheet
titled, "Compliant NMC" includes all non-mission critical systems which
were initially assessed as Y2K compliant.

Update the "Compliant MC" and "Compliant NMC" spreadsheets to reflect
current information. Highlight any changed cells in COLOR. In a separate
narrative, describe significant changes, if any, from previous quarter
submission (additions, deletions, modifications).

**A3. Inventory of Implemented Systems**

Update the "Implemented Systems" spreadsheet to reflect current
information. Highlight any changed cells in COLOR. In a separate
narrative, describe significant changes, if any, from previous quarter
submission (additions, deletions, modifications).

**A4. Status of Mission Critical Systems**

The spreadsheet titled, "Status of Mission Critical Systems" provides
summary metrics reflecting current status of mission critical systems.
Update the "Status of Mission Critical Systems" spreadsheet to reflect
current information. In a separate narrative, describe any significant
changes, if any, from previous quarter submission.

**A5. Status of Non-Mission Critical Systems**

The spreadsheet titled, "Status of Non-Mission Critical Systems"
provides summary metrics reflecting current status of non-mission
critical systems. Update the "Status of Non-Mission Critical Systems"
spreadsheet to reflect current information. In a separate narrative,
describe any significant changes, if any, from previous quarter
submission.

**A6. Year 2000 Costs**

The spreadsheet titled, "USA Year 2000 Costs" provides summary cost
information for Y2K work. Update the "USA Year 2000 Costs" to reflect
current information.

If total the Contractor\'s costs have significantly changed from the
previous quarter submission, provide a detailed explanation. Annotate
any requirement to reallocate funding between fiscal years (e.g.,
forward funding of FY99 funds to accelerate work in FY98).

**[Section B. Narrative Information]{.underline}**

**B1. Description of Progress**

Describe where significant progress has been made in addressing the Y2K
problem since the previous quarterly report. Please be as specific as
possible and provide examples where appropriate.

**B1a.** [Mission Critical Systems]{.underline} - For
**[each]{.underline}** mission critical system (**or group of related
systems, where appropriate)**, summarize the current status and describe
specific progress that has been made since the previous quarterly
report. Highlight any best practices or significant accomplishments
which have been made. Describe any issues or problems and corrective
actions which you have taken where progress is not being made as quickly
as planned.

**B1b.** Non-Mission Critical Systems - For non-mission critical systems
in general, summarize the current status and describe specific progress
that has been made since the previous quarterly report (specifics on
individual non-mission critical systems is not required). Highlight any
best practices or significant accomplishments which have been made.
Describe any issues or problems and corrective actions which you have
taken where progress is not being made as quickly as planned. In
addition, specifically describe progress in addressing the following
types of non-mission critical systems:

-   **Facilities**

-   **Non-Information Technology Systems**

    **B2. Accountability and Performance**

    **B2a.** Provide a brief description of the Project Management
    review process used by the Contractor for Y2K and what program
    controls you have implemented to assure internal accountability.

    **B2b.** Describe quantitative measures and other methods to track
    performance in addition to those addressed in quarterly report.

    **B2c**. Describe the management actions taken and by whom, when a
    responsible organization falls behind schedule.

    **B3. Validation and Verification**

    **B3a**. Describe the process used by the Contractor to verify
    internal performance reports - specifically processes to ensure
    information being reported is accurate and well-supported.

    **B3b.** Describe your approach for Y2K compliance testing and
    certification.

    **B3c.** Describe the approaches used to ensure independent
    validation of test plans, test results, and/or certifications.
    Provide examples of systems where independent validation and
    verification processes or approaches have been applied.

    **B4. Risk Management and Contingency Plans**

    **B4a.** Describe your approaches for risk management and
    contingency planning for system-specific or overall Year 2000
    project activities.

    **B4b.** Describe any criteria used to decide which systems will
    have contingency plans and timeframes for when plans will be in
    place.

    **B4c.** Indicate any mission critical systems which are/have been
    remediated which do not have a contingency plan in place. Provide
    examples of systems where risk management and contingency planning
    processes or approaches have been applied.

    **B5. Reserved**

    **B6. Personnel**

    Describe any problems associated with acquiring and retaining
    skilled personnel required to address the Year 2000 problem and any
    corrective action you have taken, where necessary.

    **B7. Exception Report on Mission Critical Systems.**

    For any mission critical system where repair or replacement cannot
    be implemented by the March 31, 1999 deadline, report the following:

-   An explanation of why the system cannot be implemented by March 31,
    1999

-   A description of the funding and other resources being devoted to
    completing the replacement or fixing the system.

-   A description of the contingency plan for the system or when a
    contingency plan will be in place.

    For any mission critical system which is not Year 2000 compliant
    that is either being (1) replaced and has fallen behind schedule by
    2 months or more at the time of this report; or (2) repaired and has
    fallen behind Agency milestones, report the following:

-   An explanation of why the effort to fix or replace the system has
    fallen behind and what is being done to accelerate the effort

-   The new schedule for replacement or completion of the remaining
    phases

-   A description of the funding and other resources being devoted to
    completing the replacement or fixing the system.

-   A description of the contingency plan for the system or when a
    contingency plan will be in place.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.1.5.1**

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

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

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

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

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: 30 days after contract
Authority to Proceed (ATP)

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Updated annually or as
required.

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

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

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

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}]{.smallcaps}**

> NSTS 07700 Volume IV *Configuration Management Requirements*
>
> SSP 41170 *Configuration Management Requirements*
>
> *JSC 09082 Orbiter Projects Office Configuration Management Plan*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The plan shall address
each of the following essential elements of CM:

\(1\) configuration identification, (2) configuration control, (3)
configuration status accounting, and (4) configuration verification. The
plan shall describe in relation to these essential elements of CM 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. In addition,
satisfaction of all the requirements of the applicable documents in 13.2
shall be addressed within the CM plan.

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 program requirements.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.1.5.2-a**

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

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

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

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe the contractor's
method for accomplishing the verification management requirements of the
contract.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: 30 days after contract
Authority to Proceed (ATP)

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Update as required.

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

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

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

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

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

NSTS 07700 Volume XI *Systems Integrity Assurance Program Plan*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The plan shall describe
the contractor's program to ensure and demonstrate that the
hardware/software processing requirements have been correctly
implemented and to ensure and demonstrate that the hardware/software
as-built configuration is in accordance with the approved requirements
documents and the approved engineering. The plan shall also describe how
identified "deltas" between the approved requirements/engineering will
be handled including documenting the authority for any approved deltas.

The plan shall describe the contractor's VM organization, policies,
procedures, implementation approach, and control systems that are to be
used to ensure proper performance of all required contract VM
activities. In addition, satisfaction of all the requirements of NSTS
07700, Volume XI shall be addressed within the VM plan.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.1.5.2-b**

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

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

6\. **[TITLE]{.smallcaps}**: Mission Configuration Product Plan (MCPP)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document, as a mission
requirements control system (MRCS) dataset, the individual Shuttle
elements\' configurations based on the flight requirements per Space
Shuttle Program (SSP) direction.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an on-going
requirement; no break in existing submission schedule

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Baselined for each flight
at Cargo Integration Review (CIR) plus 10 days, Launch Site Requirements
Review (LSRR) plus 18 days, Orbiter Roll-out Review (ORR) plus 14 days,
Flight Readiness Review (FRR) plus 14 days, Launch plus 30 days.

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

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

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

13.1 **[SCOPE]{.underline}**: The MCPP consists of documentation and an
MRCS Dataset documenting all system-level drawing requirements and
possible ferry flight requirements with all required modification
records for Orbiter, External Tank (ET), Solid Rocket Booster (SRB),
Reusable Solid Rocket Motor (RSRM), Space Shuttle Main Engine (SSME),
Mission Kit Equipment, and Payloads.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: System-level drawings
(including Engineering Orders (EO\'s)), reflecting mission
reconfiguration (i.e., installation and removal) requirements, and
modifications required to satisfy SSP requirements.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Continuously update in
MRCS database.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.1.5.2-d**

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

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

6\. **[TITLE]{.smallcaps}**: Configuration Requirements Application
Support/Software Design Documents

7\. **[DESCRIPTION/USE]{.smallcaps}**: To define the modification to
existing software prior to development for configuration requirements
application support software.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: For first software development
activity

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Prior to development of
each software release

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

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The Configuration
Requirements Application Support/Software Design Documents define the
software requirements, design data elements, database tables and
baseline release contents for configuration requirements application
support software.

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

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

a\. [Software requirements and design documentation]{.underline} shall
contain the following:

1\. Introduction.

2\. Applicable documents.

3\. Proposed system including, but not limited to:

\(a\) Data flow.

\(b\) Logic flows.

\(c\) Screen layouts.

\(d\) Report layouts.

\(e\) Table/database layouts.

\(f\) Security.

\(g\) Interfaces.

\(h\) Interrelationships.

\(i\) Performance requirements.

b\. [Software data element and table definition
documentation]{.underline} shall contain the following:

1\. Introduction.

2\. Database table definition.

c\. [Software baseline release contents documentation]{.underline} shall
contain a list of existing change sheets to include number, title and
estimated time for completion.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue. Status any
modifications to software baseline release contents documentation
approved by NASA.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** REVISION 2
2. **[DRD NO.]{.smallcaps}**: **1.1.6.1-a**

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

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

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

7\. **[DESCRIPTION/USE]{.smallcaps}**: The Facility Management Plan will
be used to provide insight into the contractor's approach for facility
management.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Contract award plus 30 days.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: By February 1 each year
(updated or complete reissue).

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.1.6.1, 1.5.5.2

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

13.1 **[SCOPE]{.underline}**: The Facility Management Plan shall
describe the contractor's approach to managing facility responsibilities
in support of the SFOC 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 facility management
to include environmental compliance and restoration requirements and
real property reporting and accountability. The plan shall address the
long range goals for the transition of facility management
responsibilities in the future.

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

> NPG 8820.2, Appendix C *Facility Project Implementation Handbook*

NPD 8800.15 *Real Estate Management Program and Implementation Handbook*

NPD 8800.14 *Policy for Real Property Management*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The plan shall identify
the contractor approach to the coordination of facility responsibilities
and budget priorities to optimize maintenance, repair, and replacement
projects for facilities and facility systems and environmental
compliance and restoration requirements across the SFOC Government owned
locations. Provide a facility management plan that will encompass
facility space utilization planning and integrated facility project
planning and reporting requirements and real property responsibilities.
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 Shuttle Program
Management and Center Facility Management.

**DRD CONTINUATION SHEET**

**[TITLE]{.smallcaps}**: Facility Management Plan **[DRD
NO.]{.smallcaps}**: **1.1.6.1-a**

**[DATA TYPE]{.smallcaps}**: 1 **[PAGE]{.smallcaps}**: 2/2

[13.]{.smallcaps} [**DATA PREPARATION INFORMATION
(CONTINUED)**:]{.smallcaps}

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

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

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable. All documents must be provided in both electronic and hard
copy.

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

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** Revision 1
2. **[DRD NO.]{.smallcaps}**: **1.1.6.1-b**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:
12/02

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

6\. **[TITLE]{.smallcaps}**: Facility Project Reporting Requirements

7\. **[DESCRIPTION/USE]{.smallcaps}**: The facility project reports will
be used to provide insight into the scope, cost, schedule and
performance of facility projects.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: As required.

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

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

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

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

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}**: NPG 8820.2 Appendix C

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

> The contractor shall submit facility project documentation and
> reporting as follows:
>
> \(1\) Facility projects greater than \$50K and less than \$ 500 K (for
> documentation purposes)
>
> \(a\) NASA Form 1509 and 1510 (prior to project start)
>
> \(2\) Faciltiy Projects Greater than \$500 K
>
> \(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 ) Facilities Project Implementation Schedule (after award of
> project)
>
> \(d\) 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}]{.smallcaps}**: Contractor format is
acceptable. All documents must be provided in both electronic and hard
copy form.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE:]{.smallcaps} REVISION 1 2. [DRD
NO.]{.smallcaps}: 1.1.6.3-a

3\. [DATA TYPE]{.smallcaps}: 1 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

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

7\. [DESCRIPTION/USE]{.smallcaps}: The plan will be used to define the
SFOC security management task.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: 90 days after effective date of
contract.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Update annually and TBD days
prior to each subsequent transition phase. (NOTE: "TBD" will be
determined prior to the initiation of each subsequent phase.)

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.6.3 and 1.1.4.1

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

13.1 [SCOPE]{.underline}: The Security Management Plan shall 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 (i.e. MCC, LCC, etc.).

13.2 [APPLICABLE DOCUMENTS]{.underline}:

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)

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

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 Shuttle Program
Management and Center Security Management. The Security Management Plan
shall include:

A description of the contractor's security management structure and
assignment of responsibilities. The approach for integrating security
requirements into functions as described in the SOW (including
interfacing with subcontractors). Identification of the security
interfaces with NASA, DoD, and other government agencies and
contractors. A description of the security baseline configuration
management program. The methodology for obtaining certifications and
re-certifications.

DRD CONTINUATION SHEET

[TITLE]{.smallcaps}: Security Management Plan [DRD NO.]{.smallcaps}:
1.1.6.3-a

[DATA TYPE]{.smallcaps}: 1 [PAGE]{.smallcaps}: 2/2

[13. DATA PREPARATION INFORMATION (CONTINUED):]{.smallcaps}

13.3 [[CONTENTS (CONTINUED]{.underline}):]{.smallcaps}

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

COMSEC procedures which include, but are not limited to:

a.  Issuance and transfer of COMSEC material

b.  COMSEC personnel responsibilities

c.  Opening and closing procedures for COMSEC facilities

d.  Insecurity reporting procedures

e.  Maintenance and operations procedures

f.  Inventory

g.  Emergency procedures

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

a.  AUTODIN and SPADOC message transmission, receipt, storage and
    delivery

b.  Classified facsimile message procedures

c.  Opening and closing procedures for message centers

d.  Insecurity reporting procedures

e.  Maintenance and operations procedures

f.  Emergency procedures

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor format is
acceptable.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes to the plan shall
be incorporated as required by change page (revision level and date) or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.1.6.3-b**

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

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

6\. **[TITLE]{.smallcaps}**: Technology Protection Control Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: The plan will be used to define
the SFOC technology protection mechanisms for all SSP development and
operations activities.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: 120 days after requirement is
added to contract.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Update annually and **TBD**
days prior to each subsequent transition phase. (NOTE: "TBD" will be
determined prior to the initiation of each subsequent phase.)

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

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

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

13.1 **[SCOPE]{.underline}**: The Technology Protection Control Plan
shall describe the Contractor's approach for meeting and maintaining
baseline requirements for the protection and control of classified
controlled information, unclassified controlled information, hardware,
software and services (including export controlled and proprietary
data). The plan and the requirements contained therein apply to all
industry and academic partners, elements, activities, and locations
including operational facilities where SSP hardware, software, and data
is developed, produced, analyzed, modeled, simulated, tested,
maintained, transported, stored and operated.

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

Federal Acquisition Regulation (FAR)

> NASA FAR Supplement
>
> NISPOM National Industrial Security Program Operating Manual

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)

International Traffic in Arms Regulation (ITAR)

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

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 Shuttle Program
Management, Center Security Management, and Center Export Control
Management. The Technology Protection Control Plan shall include:

A description of the contractor's technology protection management
structure and assignment of responsibilities. The approach for
integrating security, export control and proprietary data requirements
into functions as described in the SOW (including interfacing with
subcontractors). Identification of the interfaces with NASA, DoD, DOS,
DOC and other government agencies and contractors. A description of the
technology

DRD CONTINUATION SHEET

**[TITLE]{.smallcaps}**: Technology Protection Control Plan **[DRD
NO.]{.smallcaps}**: **1.1.6.3-b**

**[DATA TYPE]{.smallcaps}**: 1 **[PAGE]{.smallcaps}**: 2/2

[13. **DATA PREPARATION INFORMATION (CONTINUED)**:]{.smallcaps}

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

> protection baseline configuration management program. The methodology
> for obtaining licenses and agreements. The methodology for the use of
> risk assessment and the processes to be implemented for export control
> compliance.

Technology Protection Control Plans will include, but are not limited
to:

a.  Procedures for integrating Security, Export Control and Proprietary
    Data requirements/regulations

b.  Technology Protection personnel responsibilities

c.  Methodology for the application of Risk Assessment

d.  Methodology for developing, submitting and executing licenses with
    the DOC and DOS

e.  Training of employees

f.  Methodology for the communication of regulations/requirements and
    also their influence on schedule with (1) employees, (2)
    subcontractors, and (3) NASA

g.  Process for determining the category of data and procedures for
    handling different categories

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes to the plan shall
be incorporated as required by change page (revision level and date) or
complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.1.7-a**

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

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

6\. **[TITLE]{.smallcaps}**: Manifest Products

7\. **[DESCRIPTION/USE]{.smallcaps}**: Used by the Space Shuttle Program
Office in the development of NASA flight manifest and top-level program
schedules.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: With contract Authority to
Proceed (ATP)

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Twice monthly or as
required

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

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

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

13.1 **[SCOPE]{.underline}**: Manifest Products provide data needed to
support NASA manifest and top level schedules.

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

JSC 25187, Appendix A *Flight Production Generic Template*

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

Type 1: Schedule Baseline Change Request

Type 2: Space Shuttle Program Schedules, Consolidated Analysis, Flight
Assignment Working Group (FAWG) Minutes Manifest Chart, Cargo Definition
for Trajectory Design Data Package (TDDP)

Type 3: Flight Production Schedules Working Group (FPSWG) Package, Space
Shuttle and FPSWG Planning Calendars, Manifest Decision Chart, Composite
Schedule History.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.1.7-b

3\. [DATA TYPE]{.smallcaps}: 1/2/3/4 4. [DATE REVISED:
09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Integrated Ground and Flight Operations
Schedules

7\. [DESCRIPTION/USE]{.smallcaps}: To provide accurate and reliable
implementation planning, scheduling and assessment tools for operational
use at JSC and KSC.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: In accordance with Item 13.3g

10\. [SUBMISSION FREQUENCY]{.smallcaps}: See Item 13.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.7

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

13.1 [SCOPE]{.underline}: The Integrated Ground and Flight Operations
Schedules define required scheduling information in support of Shuttle,
ISS and Payload-to-Shuttle integration operations, and assess progress
at achieving these schedules.

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

13.3 [[CONTENTS]{.underline}]{.smallcaps}: General Criteria:

a\. The contractor shall develop, maintain (update), provide and ensure
a consistent, accurate, and stable scheduling approach that provides for
the identification, coordination, sequencing, control, implementation
and tracking of all operational activities and is easily auditable by
the Government.

b\. The approach shall provide the ability to fully identify, analyze,
mitigate and control scheduling risks and impacts; accurately identify,
coordinate and optimize facility and resource utilization; identify and
analyze critical path activities; and allow its users to easily measure
the progress towards achieving the intended plan.

c\. The scheduling approach shall not only represent the scheduled work
for that operation, but also the requirements commitment from all the
supporting organizations.

d\. The contractor is encouraged to utilize modern manufacturing
resource planning, industrial engineering techniques and other
approaches, (e.g., job standardization, resource leveling and
optimization, critical path analysis, standardized processing flow
approaches, etc.) to ensure schedule stability, accuracy, reliability,
predictability, and achievability.

e\. *Schedule consistency* shall be defined as the degree to which the
contractor utilizes standardized scheduling approaches between similar
processing activities and flows. *Accurate scheduling* shall be defined
as the accurate representation of work content and tasks duration
(predicted vs. actuals). A *stable schedule* shall refer to the degree
to which daily schedule changes are minimized and limited to unforeseen
hardware/software problems or NASA-directed changes.

f\. Scheduling approaches shall address the following information as a
minimum:

1\. Scheduling symbology that is consistent with that particular
operational area.

2\. Predicted task duration/labor standards derived from accurate and
objective prediction methodologies.

3\. Indications of activities by appropriate nomenclature that clearly
delineates the task to be performed and any associated Work
Authorization Documents.

4\. Identification of who is responsible for doing the actual work.

5\. Required supporting activities or support from other contractors,
outside organizations, agencies or centers.

DRD CONTINUATION SHEET

[TITLE]{.smallcaps}: Integrated Ground and Flight Operations Schedules
[DRD NO.]{.smallcaps}: 1.1.7-b

[DATA TYPE]{.smallcaps}: 1/2/3/4 [PAGE]{.smallcaps}: 2/3

13\. DATA PREPARATION INFORMATION (CONTINUED):

13.3 [CONTENTS (CONTINUED)]{.underline}:

6\. Identification of critical resource requirements.

7\. Clear depiction of the interrelationships and constraints among
related tasks.

8\. Identification of the critical path, priorities, high risk
activities and other significant activities.

9\. NASA-approved milestones and Cargo-to-Shuttle interface activity and
need dates.

10\. Major facility/system outages/modifications/O&M activities.

11\. Special test activities or requirements.

12\. Identification of hazardous operations and special safety
requirements.

g\. Required data:

KSC Ground Operations.

Shall cover as a minimum the following activities in addition to the
above information:

+-----------------------+-----------------------+-----------------------+
|                       | Initial Submission    | Frequency             |
+-----------------------+-----------------------+-----------------------+
| a\. LC-39 Overall     | At contract Authority | No more than one      |
| Integrated Processing | to Proceed (ATP)      | official product a    |
| Schedules (Type 4)    |                       | day.                  |
+-----------------------+-----------------------+-----------------------+
| b\. Detailed Element  | 10 days prior to LSFR | Per flow basis        |
| Level Assessments     |                       |                       |
| (Type 3)              |                       |                       |
+-----------------------+-----------------------+-----------------------+
| c\. OPF Flow          | 2 weeks prior to LSFR | Per flow basis.       |
| Processing Milestone  |                       |                       |
| Schedule (Type 3)     |                       |                       |
+-----------------------+-----------------------+-----------------------+
| d\. Flow Integrated   | 2 weeks prior to LSFR | Per flow basis.       |
| Operations Assessment |                       |                       |
| Summary Schedule      |                       |                       |
| (Type 1)              |                       |                       |
+-----------------------+-----------------------+-----------------------+
| e\. Integrated Test   | First integrated flow | 5 work days prior to  |
| Schedules             | after contract award  | test                  |
|                       |                       | Call-to-Stations, but |
| (Type 3)              |                       | no less than 3 days   |
+-----------------------+-----------------------+-----------------------+
| f\. Integrated Launch | First integrated flow | 8 work days prior to  |
| and Landing Schedules | after contract award  | Call-to-Stations      |
| (Type 1)              |                       |                       |
+-----------------------+-----------------------+-----------------------+
| g\. Assessment of all | First integrated or   | Biweekly              |
| planned, baselined    | element flow after    |                       |
| turnaround processing | contract award        |                       |
| tasks against the     |                       |                       |
| as-run schedule       |                       |                       |
| performance (Type 4)  |                       |                       |
+-----------------------+-----------------------+-----------------------+
| h\. Comparison of     | First integrated or   | Biweekly              |
| total predicted       | element flow after    |                       |
| resource (direct      | contract ATP          |                       |
| labor hours) usage    |                       |                       |
| for planned work      |                       |                       |
| versus actual         |                       |                       |
| resources utilized    |                       |                       |
| throughout each       |                       |                       |
| element and           |                       |                       |
| integrated flow and   |                       |                       |
| reported in           |                       |                       |
| conjunction with the  |                       |                       |
| above schedule        |                       |                       |
| progress (Type 4)     |                       |                       |
+-----------------------+-----------------------+-----------------------+
| i\. Planned versus    | First integrated or   | Per Flow Basis        |
| actual number of days | element flow after    |                       |
| to achieve major      | contract ATP          |                       |
| program level         |                       |                       |
| milestones            |                       |                       |
+-----------------------+-----------------------+-----------------------+

DRD CONTINUATION SHEET

[TITLE]{.smallcaps}: Integrated Ground and Flight Operations Schedules
[DRD NO.]{.smallcaps}: 1.1.7-b

[DATA TYPE]{.smallcaps}: 1/2/3/4 [PAGE]{.smallcaps}: 3/3

13\. DATA PREPARATION INFORMATION (CONTINUED):

13.3 [CONTENTS (CONTINUED)]{.underline}:

JSC Flight Operations Schedules (Data Type 3)

Shall cover as a minimum the following activities in addition to the
above information:

  ----------------------- ----------------------- -----------------------
                          Initial Submission      Frequency

  Integrated Simulation   1200 Thursday           Weekly
  Schedule                                        

  SMS Schedule            10 AM Friday            Weekly

  SSTF Schedule           10 AM Friday            Weekly

  SST Schedule            10 AM Friday            Weekly

  PTT Schedule            10 AM Friday            Weekly

  Other Facility          10 AM Friday            Weekly
  Schedules                                       

  Crew Training Schedules 10 AM Friday one week   Weekly
                          prior to training start 
  ----------------------- ----------------------- -----------------------

JSC Flight Crew Schedules (Data Type 3)

Shall cover as a minimum the following activities in addition to the
above information:

  ----------------------- ----------------------- -----------------------
                          Initial Submission      Frequency

  a\. Astronaut Candidate Friday 10 AM or last    Weekly
  Weekly Schedules        workday of week         

  b\. Non-assigned        Friday 10 AM or last    Weekly
  Astronaut Weekly        workday of week         
  Schedules                                       
  ----------------------- ----------------------- -----------------------

JSC ISS Program Operations Scheduling Products (Data Type 3)

Shall cover as a minimum the following activities in addition to the
above information:

  ----------------------- ----------------------- -----------------------
                          Initial Submission      Frequency

  a\. Mission Operations  First month after       Monthly
  Integrated Schedules    contract ATP, on the    
  (including electronic   first Monday of month   
  scheduling interfaces                           
  to the ISS Program).                            

  b\. Deliverable         First month after       Monthly
  dependencies based on   contract ATP, on the    
  facility and product    first Monday of month   
  development schedules.                          
  ----------------------- ----------------------- -----------------------

JSC MOD Flight Management and Schedules Scheduling Products (Data Type
3)

Shall cover as a minimum the following activities in addition to the
above information:

  ----------------------- ----------------------- -----------------------
                          Initial Submission      Frequency

  a\. Mission Operations  First week after        Weekly
  Shuttle Flight          contract ATP            
  Preparation Schedules                           

  b\. Mission Operations  First month after       Monthly
  Space Station Flight    contract ATP            
  Preparation Schedules                           
  ----------------------- ----------------------- -----------------------

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor format is
acceptable.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** Rev. 1]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.1.7-c**

3\. **[DATA TYPE]{.smallcaps}**: 2 4. **[DATE REVISED]{.smallcaps}**:
02/00

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

6\. **[TITLE]{.smallcaps}**: KSC Schedule and Status Summary (Gray Book)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To display current KSC schedules
and summary information on aspects of the near-term manifest for Shuttle
flights.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an on-going
requirement; no break in existing submission schedule

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Updated as follows:

Volume I -- Monthly (May be cancelled or replaced by an alternate

version of the Grey Book, as requested by NASA-KSC)

Executive Edition -- Weekly (May be cancelled or replaced by an
alternate version of the Grey Book, as requested by NASA-KSC)

> Volumes II -- Quarterly (May be cancelled as requested by NASA-KSC)

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

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

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

13.1 **[SCOPE]{.underline}**: The KSC Schedule and Status Summary
integrates KSC planning of near-term and long range hardware,
facilities, and other resources to support schedules and manifest.

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

NSTS 08178 *Space Shuttle Program Schedules*

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

a\. Schedule and Status Summary, Volume I Executive Summary\--Current
planning schedules and summary information for near-term flights, focus
on Orbiter and Integrated SSV processing.

b\. Schedule and Status Summary, Volume I\--Same as above, but includes
mission processing status, stand-alone element and MLP status, near-term
follow-on flights, facility schedules, and as-run data summaries.

c\. Schedule and Status Summary, Volume II\--KSC standard processing
factors, assumptions and other information used for KSC manifest
planning support. Also contains schedule enhancement analysis efforts
and as-run data summaries.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable with NASA approval.

**[[13.5 MAINTENANCE]{.underline}]{.smallcaps}**: Changes, as required
based on manifest changes, shall be incorporated by change page or
complete reissue. The Contractor is encouraged to minimize like
documentation and consolidate like planning documentation and processes.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE:]{.smallcaps} REVISION 1 2. [DRD
NO.]{.smallcaps}: 1.1.7-d

3\. [DATA TYPE]{.smallcaps}: 1 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. TITLE: Flight-Specific TV Plan

[7. DESCRIPTION/USE]{.smallcaps}: The flight-specific TV Plan documents
the timeline and the configuration and operation requirements necessary
to satisfy planned video and audio events. Test and operation of new
technology/capabilities are also included.

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

[9. INITIAL SUBMISSION]{.smallcaps}: Upon contract incorporation as
formal Data Requirement

[10. SUBMISSION FREQUENCY]{.smallcaps}: Prior to each Flight, the
requirements are submitted for approval by Launch minus 2-days (L-2
days).

11\. [REMARKS]{.smallcaps}:

[12. INTERRELATIONSHIP]{.smallcaps}: SOW 1.1.7

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

[13.1 [SCOPE]{.underline}]{.smallcaps}: The contractor is responsible
for collecting and documenting audio and video requirements for each
Shuttle mission.

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

NSTS 08240 *Space Shuttle Program (SSP) TV Plan*

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

The specific product to be delivered is documented in the NSTS 0824 and
is as follows:

Flight-specific TV Plan

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Electronic and paper
copies of all Flight-specific TV Plans are retained in files by the
contractor.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.1.7-f**

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

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

6\. **[TITLE]{.smallcaps}**: Flight Requirements Documents (FRDs)

7\. **[DESCRIPTION/USE]{.smallcaps}**: The flight specific FRDs (NSTS
17462-XX) document Space Shuttle Program (SSP) authorized requirements
for each flight. The FRD Blank Book (NSTS 17462) is used as a guide
during preparation of the flight specific FRDs. Implementation of the
specifications defined within the FRD Blank Book ensures a consistent
definition and format for flight requirements. The FRD ISS Standard
(NSTS-17462-ISS) contains the PRCB-approved requirements for a
standardized ISS flight and is used for the preparation of the flight
specific FRDs for space shuttle flights to the ISS.

8\. **[DISTRIBUTION]{.smallcaps}**: The flight specific FRDs, the FRD
Blank Book, and FRD ISS Standard shall be delivered electronically by
posting the baseline documents and revisions to the SSP Intranet (SSP
Web.) In addition, hardcopies will be sent per the distribution list.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: As required following approval
of administrative contract modification.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: After the normal review
process a basic flight specific FRD shall be provided for approval
immediately following the baselining of a space shuttle mission in the
Flight Definition and Requirements Document (FDRD), NSTS 07700, Vol.
III, Table 4.1. Revisions to each document shall be performed as defined
below in Section 13.5, "Maintenance".

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

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

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

13.1 **[SCOPE]{.underline}**: The flight specific FRD shall define
within, or by reference, requirements to be implemented on a specific
space shuttle flight. All flight preparations shall be consistent with
the requirements specified within the FRD.

13.2 [**[APPLICABLE DOCUMENTS]{.underline}**:]{.smallcaps} NSTS
17462-XX, NSTS 17462-ISS, NSTS 17462-107 through -999.

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The content of the flight
specific FRD is defined by the FRD Blank Book (NSTS 17462-XX) and the
FRD ISS Standard (NSTS 17462-ISS) documents and approved flight-specific
change requests.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: The format of the flight
specific FRD is defined by the FRD Blank Book (NSTS 17462-XX) and the
FRD ISS Standard (NSTS 17462-ISS) documents.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Revisions to each
flight specific FRD shall be made as necessary to maintain the currency
of the flight specific FRDs. Revisions to the FRD Blank Book and the FRD
ISS Standard shall be made as necessary to maintain the validity of
these documents as a reference during the preparation of the flight
specific FRDs.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.2.1.1-a**

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

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

6\. **[TITLE]{.smallcaps}**: Flight Derived Dispersions Database Update

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide statistically
reconstructed flight data for preflight analyses that require Flight
Derived Dispersions.

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

9\. **INITIAL SUBMISSION**: Assumption of ongoing requirement; no break
in existing submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: The Flight Derived
Dispersion database shall be reviewed and updated once a year.

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

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

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

13.1 **[SCOPE]{.underline}**: The database shall provide Flight Derived
Dispersions for future preflight analyses.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: This database shall
contain statistically calculated reconstructed flight data that protect
for Flight Derived Systems dispersions effects. (The database is updated
after the completion of each post-flight assessment with AFSIG approval.
Updates to the Flight Derived Dispersion database used for pre-flight
and day-of-launch assessments are approved by the ICB and PRCB.)

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor\'s format is
acceptable.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: The electronic
database shall be updated once a year and maintained by Rockwell.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.2.1.3-a**

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

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

6\. **[TITLE]{.smallcaps}**: Mission-Specific Shuttle Thermal and
Structural Math Models

7\. **[DESCRIPTION/USE]{.smallcaps}**: Models are required as input data
for analyses of specific Space Shuttle payloads and cargo
configurations.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Per Payload request

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Per Payload request for
each payload on each Shuttle flight.

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

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

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

13.1 **[SCOPE]{.underline}**: This document includes Shuttle Integrated
Thermal Math Models (ITMM), Integration Geometric Math Models (IGMM),
and Payload Thermal Math Models for specific Space Shuttle payloads and
cargo configurations. The Shuttle Thermal and Structural Math Models
provide the Space Shuttle quasi-static and dynamic structural math
models and forcing functions for specific Shuttle/Payload/Cargo
configurations for all phases of Space Shuttle missions. Models are in
compliance with the documents listed in 13.2.

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

STS81-064 *STS Dynamic Math Models (M6.OZA) for Payload Loads Analysis,
July 1988*

ES3-76-1 *Orbiter Midsection Payload Bay Thermal Math Model Description,
May 1991*

ES3-77-3 *390 Node Atmospheric Orbiter Midsection Payload Bay Thermal
Math Model Description, May 1991*

ES3-77-3 *Simplified 136 Node Atmospheric Orbiter Midsection Payload Bay
Thermal Math Model Description, June 1995*

ES3-76-1 *Simplified 136 Node On-Orbit Orbiter Midsection Payload Bay
Thermal Math Model Description*, *June 1995*

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

a\. Open-door ITMM(s). a. Modal data.

b\. Closed-door ITMM(s). b. Forcing functions.

c\. Open-door IGMM(s). c. Orbiter flexibility and quasi-static

d\. Closed-door IGMM(s). deflections, if applicable.

e\. Payload Thermal Math

Model(s).

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue. Generic
model updates require NASA approval.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.2.1.3-b**

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

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

6\. **[TITLE]{.smallcaps}**: Cargo Thermal and Loads Verification
Analyses

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide passive and
active/Environmental Control and Life Support System (ECLSS) thermal
verification analyses or assessments for every Space Shuttle mission
payload/cargo configuration for the planned mission timeline; structural
dynamic loads verification analysis for every Space Shuttle mission
payload/cargo configuration; and analyses used by payloads for
verification of Shuttle compatibility.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Passive thermal data dump
due seven months prior to launch (L-7); report due six months prior to
launch (L-6). Active/ECLSS report due five months prior to launch (L-5).
Passive and active/ECLSS final documentation due one month prior to
launch (L-1). Loads data dump due seven months prior to launch (L-7).
Loads report due five and one-half months prior to launch (L-5.5).
Delivery schedules may be adjusted if Government-supplied payload models
are not received in time to support or as otherwise authorized by the
Contracting Officer's Technical Representative (COTR) or designated
representative.

11\. **[REMARKS]{.smallcaps}**: Payload math models will be government
furnished and provided to the contractor at approximately 12 months
prior to launch (L-12).

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

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

13.1 **[SCOPE]{.underline}**: Results of passive and active/ECLSS
thermal interface analyses of the interface(s) between the Space Shuttle
and the designated payloads/cargoes for each mission, both in the
payload bay and in the Orbiter cabin. Results of structural dynamic and
quasi-static loads analyses of the Space Shuttle and payloads/cargo for
each mission.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: Thermal analyses shall
include the following elements:

a\. Summary of the Orbiter/payload/cargo/spacecraft models utilized (as
applicable in the analysis).

b\. Summary of the selected analysis mission phases (may include
prelaunch, launch, on-orbit, entry, and post-landing).

c\. Pertinent temperature data/history plots for the analyzed mission
phases.

d\. Assessment of the thermal interface compatibility of the
Orbiter/payload/cargo/ spacecraft for the planned mission timeline.

e\. For cargoes where the results of previous thermal analyses are
applicable and integrated thermal compatibility analysis can be
eliminated, the documentation shall consist of a description of the
previous and current configurations, a summary of previous analytical
results, and an assessment of the Orbiter/payload/cargo/spacecraft
thermal compatibility.

DRD Continuation Sheet

**[TITLE]{.smallcaps}**: Cargo Thermal and Loads Verification Analyses
**[DRD NO.]{.smallcaps}**: **1.2.1.3-b**

**[DATA TYPE]{.smallcaps}**: 3 **[PAGE]{.smallcaps}**: 2/2

13\. DATA PREPARATION INFORMATION (CONTINUED)

Each loads verification analysis shall include:

a\. Modal coupling of the Space Shuttle and payloads/cargo for lift-off
and landing configurations.

b\. Modal and coupled Orbiter/payload lift-off and landing load
responses.

c\. Orbiter/payload attachment points loads and payload loads.

d\. Quasi-static load and deflection analysis for all selected
conditions.

e\. On-orbit and coupled loads if applicable.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. **DPD NO.:** 821 **ISSUE:** REVISION 1 2. **DRD NO.:** 1.2.1.3.-c

3\. **DATA TYPE:** 3 4. **DATE REVISED:** 05/2001

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

6\. **TITLE:** Safety Evaluation of Orbiter Services for Payload Use

7\. **DESCRIPTION / USE:** Safety evaluations of payload planned use of
Orbiter-provided services to identify possible payload-to-Orbiter
interface hazards. The evaluations are based on payload customer Safety
Assessment Reports and are used by the cargo integration member of the
Safety Review Panels.

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

9\. **INITIAL SUBMISSION:** Assumption of an ongoing requirement; no
break in existing submission schedule.

10\. **SUBMISSION FREQUENCY:** Five (5) working days prior to the
scheduled meeting of Payload Safety Review Panel (PSRP) / ISS Safety
Review Panel (SRP).

11\. **REMARKS:** The Shuttle / ISS Payload Safety Assessment Reports
will be Government-furnished.

12\. **INTERRELATIONSHIP:** SOW 1.2.1.3

13\. **DATA PREPARATION INFORMATION:**

a.  **[SCOPE]{.underline}:** Provides an evaluation of possible payload
    hazards across the payload-to-Orbiter interfaces and assesses the
    potential impact to the Orbiter and Station.

b.  **[APPLICABLE DOCUMENTS]{.underline}**: Payload/Station safety
    documentation and ICD/IDDs

c.  **[CONTENTS]{.underline}**: Each Safety Evaluation of payload
    planned use of Orbiter-provided payload services for safety critical
    functions shall:

```{=html}
<!-- -->
```
a.  Interpret payloads possible hazards across the interface and assess
    impact to the Orbiter and Station.

b.  Review and determine if payload/Station hazard reports clearly
    identify safety-critical interfaces with the Orbiter (i.e., hazard
    controls / hazard control monitors).

    a.  If safety critical interfaces are implied in the safety data
        package or other documentation, those interfaces are to be
        listed in the hazard report as items for the payload
        organization to clarify.

    b.  The evaluation will mention that the safety-critical interfaces
        were not clearly identified.

c.  State whether or not the Station/payload-to-Orbiter Interface
    Control Document (ICD) or the Interface Definition Document (IDD) is
    available.

    a.  If the ICD / IDD is available, document the title, ICD / IDD
        number, and the date / revision.

        i.  Make a correlation between the identified safety-critical
            interfaces in the ICD / IDD to the payload hazard reports or
            determine if a correlation cannot be made.

        ii. Evaluate to ensure that all Orbiter payload services and
            interfaces identified in the payload hazard reports are
            included in the ICD / IDD. If they are not included, list
            the incompatibilities in the evaluation.

    b.  If the ICD / IDD is not yet available, then state that it is not
        available in the evaluation and provide an estimated date as to
        when it will be available.

d.  Evaluate to assure that Orbiter failure modes and fault tolerances
    are interpreted correctly by Space Shuttle users. Determine if the
    Station/Payload Safety Assessment Reports correctly describe the use
    of Orbiter payload services required for hazard control /
    monitoring. The required Orbiter payload services that are correctly
    described are to be listed in the evaluation.

e.  Provide an overall evaluation of the completeness of the
    Station/Payload Safety Assessment Report with deficiencies
    identified.

DRD CONTINUATION SHEET

**[TITLE]{.smallcaps}**: Safety Evaluation of Orbiter Services for
Payload Use **[DRD NO.]{.smallcaps}**: 1.2.1.3-c

**[DATA TYPE]{.smallcaps}**: 3 **[PAGE]{.smallcaps}**: 2/2

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes to the plan
shall be incorporated as required by change page (revision level and
date) or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE:]{.smallcaps} REVISION 1 2. [DRD
NO.]{.smallcaps}: 1.2.1.3-d

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Payload Environmental Impact Statement

7\. [DESCRIPTION/USE]{.smallcaps}: The payload complement for each
Shuttle mission is assessed for potential environmental impact to the
earth\'s atmosphere or population. This evaluation supports NASA
Headquarters' statements as listed in 13.2 regarding potentially adverse
environmental impacts of each Shuttle space flight mission.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: Assumption of an ongoing
requirement; no break in existing submission schedule

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Submittal provided L-9 weeks
prior to launch.

11\. [REMARKS]{.smallcaps}: The Payload Safety Assessment Reports are
Government-furnished.

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.2.1.3

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

13.1 [SCOPE]{.underline}: The Payload Environmental Assessment relies on
the Payload Safety Assessment Report compliance data packages submitted
by each payload organization. These are examined with respect to the use
of materials which would negatively impact local or global air, land, or
water quality, as well as have predictable unfavorable effects on human
health. Additional insight into the hazardous components of each payload
is provided by the NASA Interagency Nuclear Safety Review Panel and the
JSC Toxicology Group.

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

HDQ Ltr, MZ, 2/21/95 *Payload Impact Assessments (PIA) for STS Missions*

SSP, JSC, Ltr, MS3-95-054, 4/28/95 *Payload Impact Assessments (PIA) for
Space Transportation System (STS) Missions*

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

a\. Flight summary.

b\. Primary and secondary payload identification. Detailed Test
Objectives and Detailed Supplementary Objectives reviewed for potential
impact.

c\. Data source title and date.

d\. Brief payload description identifying substances of potential impact
in each payload.

e\. Statement regarding the environmental threat from each payload.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: A report is prepared for
each mission. Corrections/updates are issued as revisions as required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.2.1.5-a**

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

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

6\. **[TITLE]{.smallcaps}**: Space Shuttle Program (SSP) Drawing Release
Change Request (CR)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To authorize release of the Space
Shuttle Systems Drawings for each flight.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Submitted no later than 18
days following CIR, or as otherwise authorized by the Contracting
Officer's Technical Representative (COTR) or designated representative

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.2.1.5 and 1.4.1

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

13.1 **[SCOPE]{.underline}**: Identify discrete configuration for each
flight and ferry flight in accordance with NSTS 07700, Volume IV, Book
1:

a\. For Flight:

V072-000001-XXX Space Shuttle System

SGD32100XXX-XXX Crew Compartment Configuration Drawing

V072-200XXX-XXX Mission Equipment Cargo Support - Launch Site
Installation

b\. For Ferry Flight:

V072-000001-XXX Space Shuttle System (Ferry Flight)

SGD32100XXX-XXX Crew Compartment Configuration Drawing (Ferry Flight)

V072-200XXX-XXX Mission Equipment Cargo Support - Launch Site
Installation (Ferry Flight)

V072-300XXX-XXX Orbiter/Shuttle Carrier Aircraft (SCA) Ferry
Configuration

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

NSTS 07700, Volume IV, *Configuration Management Requirements*

Book 1

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The SSP Drawing Release
Change Request contains program drawing release to baseline vehicle
configuration.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Revisions to be made
as required to support contractor's engineering releases.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE:]{.smallcaps} REVISION 1 2. [DRD
NO.]{.smallcaps}: 1.2.1.5-b

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Engineering Drawings

7\. [DESCRIPTION/USE]{.smallcaps}: To provide flight-specific cargo
integration information necessary for contractor and payload customers
to evaluate the compatibility of the flight cargo mix with the
designated Orbiter. To provide the final cargo integration engineering
drawings required for Orbiter reconfiguration.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: Assumption of ongoing requirement;
no break in existing submission schedule

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Once per flight, with updates
as required

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.2.1.5

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

13.1 [SCOPE]{.underline}: Drawings are prepared in conformance with the
contractor\'s Drawing Requirements Manual and serve as the controlled
source of physical and functional information necessary to:

> a\. Maintain physical and functional compatibility between the
> Orbiter, payload(s), and related payload integration hardware.
>
> b\. Communicate applicable coordinated payload agreements with
> subsystem disciplines.
>
> c\. Document cargo configuration of each mission/flight configuration.

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

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Engineering drawings shall
include the following:

> a\. Mission Equipment Cargo Support - Launch Site Installation
> (V072-200XXX-XXX).
>
> b\. Cargo Arrangement Drawing (VA72-200XXX).
>
> c\. Electrical Interface Diagram (VD72-200XXX).
>
> d\. Integrated Schematic (VS72-200XXX).
>
> e\. Installation Technical Orders (M072-XXXXXX).
>
> f\. Retention Schematic Diagram (VS70-540XXX)

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Revisions to be in
accordance with contractor\'s engineering and change control system.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.2.1.6-a**

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

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

6\. **[TITLE]{.smallcaps}**: Launch Systems Evaluation Advisory Team
(LSEAT) Flight-Specific Products

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide flight-specific
products to LSEAT for assessment.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: First flight following
contract award

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Each flight as required

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

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

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

13.1 **[SCOPE]{.underline}**: These products provide all required LSEAT
flight-to-flight verification results, DOL comparison results, preflight
readiness statements, and mission-specific database definition.

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

NSTS 08349 *Integrated Mission Support Plan*

NSTS 08211 *LSEAT Integrated Support Plan*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The specific products to
be delivered are documented in NSTS 08211 and are as follows (Data Type
1 unless indicated otherwise):

a\. LSEAT Database Change Request (CR) (Data Type 1).

b\. LSEAT Verification Test Cases (Data Type 1).

c\. Dolilu End-to-End Test (L-3 weeks) (Data Type 1).

d\. LSEAT L-7 Readiness Briefing (Data Type 3).

e\. Dolilu End-to-End Test (L-3 Days) (Data Type 1).

f\. LSEAT Day-of-Launch Data Pack (Data Type 3).

g\. LSEAT Post Flight Report (Data Type 3).

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: All technical
assessment results retained in LSEAT historical files for actual
launches. Launch attempt data and pre-launch test results deleted after
actual launch occurs. Generic math model updates require NASA approval.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.2.1.6-b**

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

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

6\. **[TITLE]{.smallcaps}**: Launch Systems Evaluation Advisory Team
(LSEAT) Non Flight-Specific Products

7\. **[DESCRIPTION/USE]{.smallcaps}**: To support periodic block updates
for LSEAT software and resolution of Rockwell involved LSEAT anomalies.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: As required

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: As needed to support LSEAT
software updates and resolution of anomalies

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

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

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

13.1 **[SCOPE]{.underline}**: These products provide definition and
delivery of the Rockwell software and database updates associated with
LSEAT block updates and anomaly resolution.

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

NSTS 08211 *LSEAT Integrated Support Plan*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The specific products to
be delivered are documented in NSTS 08211 and are as follows:

a\. LSEAT block update support.

b\. LSEAT block update definition inputs.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format for
briefings; Space Station Program (SSP) Change Requests (CR's) and data
format per NSTS 08211, Appendix A.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Contractor briefings
maintained in LSEAT Working Group files until first flight of block
update. SSP CR's maintained by meeting support group.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.2.1.7-a**

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

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

6\. **[TITLE]{.smallcaps}**: Integrated Data Processing System (DPS)
Principles of Operation (POO) Document Updates

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document the design,
interfaces, and POO of the Shuttle Integrated DPS, including
Multi-functional Electronic Display Subsystem (MEDS), for knowledge
capture, analysis, and training purposes.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an ongoing
requirement; no break in existing submission schedule.

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

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

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

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

13.1 **[SCOPE]{.underline}**: The document shall provide a detailed
description of the DPS of the Space Shuttle Avionics (including MEDS),
including major element interfaces, controls, and user operations of the
subsystem.

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

MEDS POO

DPS Flight Support Manual

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The update shall consist
of three sections:

a\. Overview, providing the necessary orientation and background.

b\. Definition of the configuration, modes of operation, and performance
characteristics of the modified DPS System with the emphasis on user
operations characteristics.

c\. Description of the characteristics of the DPS User Operations
Interface.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval..

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Documentation is to be
updated as required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.2.1.7-c**

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

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

6\. **[TITLE]{.smallcaps}**: Integrated Data Processing System (DPS)
Flight Support Manual

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide a reference handbook
for use by DPS engineering on-station during launch countdown which will
provide clarification of error codes, fault annunciation, and other data
useful in formulating a GO/NO GO decision for the DPS.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an ongoing
requirement; no break in existing submission schedule.

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

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

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

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

13.1 **[SCOPE]{.underline}**: This manual is applicable to the DPS
displays and data used during launch countdown. The first release of the
document will be for the set of integrated DPS displays currently in
use. The second submittal will include fault indications and definitions
unique to the Multi-functional Electronic Display Subsystem (MEDS). This
information will also be used to formulate new DPS prelaunch Launch
Commit Criteria (LCC) flight support display pages for MEDS monitoring
and evaluation.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The Flight Support Manual
will include figures and explanations of the displays used on
day-of-launch by DPS engineers. The manual will also include a
cross-referenced table allowing engineers quick access to meanings and
implications of error codes or fault annunciation.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.2.2.1-a**

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

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

6\. **[TITLE]{.smallcaps}**: Shuttle Weight, Performance, and Integrated
Mass Properties Database and Status Reports

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide integrated mass
properties database and reports necessary to support mission-specific
vehicle weight statements and provide management insight for each
mission in process, selected reference missions, and special requests.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of ongoing
requirement; no break in existing submission

schedule

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Weekly and/or as required

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

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

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

13.1 **[SCOPE]{.underline}**: The contractor shall combine mass property
submittals from each element/project and maintain an integrated vehicle
mass properties database. The contractor reports integrated vehicle
center-of-gravity, down weights, ascent performance, and other important
mission parameters.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The contractor shall
develop and maintain the following items:

a\. Integrated mass properties database, including all vehicle and
mission-kit installation mass properties, estimated and calculated mass
properties to support mission planning, upweights, downweights, and
performance-margin data for each approved mission/flight/payloads
configuration.

b\. Electronic file reports accessible to all Shuttle Integrated
Accounting Status System (SIASS) users including:

1\. Weekly Space Shuttle Vehicle (SSV) weight and performance database
updates.

2\. Quarterly Shuttle Systems weight and performance status report (NSTS
09095).

3\. Weekly flight dynamics mission summary.

4\. Generic and mission specific Reusable Solid Rocket Motor (RSRM)
performance data page for Trajectory Design Data Packages (TDDP's).

5\. Assessment mass properties updates for Cargo Integration Review
(CIR) and Flight Planning and Stowage Review (FPSR).

6\. Launch Site Requirements Review (LSRR) and Launch Site Flow Review
(LSFR) mass property briefings.

The contractor shall publish mission management report containing
designated mission parameters.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Contractor shall
maintain integrated mass properties database on an on-going basis, using
submitted mass property data, comments discrepancy information,
problem/resolutions inputs, and mission kit data. Hard copies of each
weekly update will be maintained for at least one year.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.2.2.2-a & -b

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Trajectory Design Data Package (TDDP) and
Change Notices

7\. [DESCRIPTION/USE]{.smallcaps}: To document selected mission
configuration, ground rules, vehicle performance characteristics, and
data for various flight design organizations.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: Production of TDDPs is the
assumption of ongoing requirement; no break in existing submission
schedule. Submission of Change Notices (CN\'s) will be as required

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Normally, seven TDDP's are
scheduled for each mission. The initial document is published 18 months
before a launch. In addition, special mission and study TDDP's may be
required. Schedule is defined by the Flight Production Schedules Working
Group on a per-mission basis. CN's as required.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.2.2.2

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

13.1 [SCOPE]{.underline}: The TDDP contains pertinent mission and
vehicle information used to start the flight design process as well as
special design studies and assessments. The TDDP ensures all simulation
groups use the same initiation data, constraints, and Shuttle Program
direction. CN's update pertinent mission and vehicle information
contained in a previously released TDDP.

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

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Typical information included
is: Vehicle summary weight statement (mass properties), Space Shuttle
Main Engine (SSME) tag data, Redesigned Solid Rocket Motor (RSRM)
performance data, Main Propulsion System (MPS) propellant inventories,
dynamic pressure constraints, Q-alpha constraints, current mission
requirements and appropriate references. Other information is included
as needed per customer direction.

Change notices shall be issued as information updates between scheduled
TDDP's.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Document preparation
software is updated semi-annually, with critical revisions made as
requested by the customer. All TDDP's will be maintained by CN\'s and
archived. Archives shall be maintained and archival materials
dispositioned in accordance with NASA and Federal Records Management
regulations and procedures.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** revision 1]{.smallcaps}
2. **[DRD NO.]{.smallcaps}**: **1.2.2.3-a**

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

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

6\. **[TITLE]{.smallcaps}**: Adjusted Reusable Solid Rocket Motor (RSRM)
Pre-flight Computer Files

7\. **[DESCRIPTION/USE]{.smallcaps}**: To generate adjusted RSRM block
motor characteristics for trajectory simulations.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of ongoing
requirement; no break in existing submission

schedule

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

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

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

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

13.1 **[SCOPE]{.underline}**: Adjusted RSRM Pre-flight Computer Files
adjust MSFC-provided RSRM-specific characteristics based on
reconstructed flight history .

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: Computer dataset with
RSRM-specific characteristics.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: A historical file
shall be maintained by the contractor.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.2.2.3-b**

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

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

6\. **[TITLE]{.smallcaps}**: Main Propulsion System (MPS)
Inventory/Budget Update and Documentation

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document the loading and
consumption of MPS propellants in the External Tank.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of ongoing
requirement; no break in existing submission

schedule

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

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

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

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

13.1 **[SCOPE]{.underline}**: MPS inventory/budget documents the loading
and consumption of MPS propellants in the External Tank.

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

NSTS 08209, Vol. I *Shuttle Performance Assessment Data Book*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: MPS loading and
consumption for NOM, AOA/Trans-Atlantic Landing (TAL), and Return to
Launch Site (RTLS).

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: NSTS 08209, Volume 1,
will be updated by the contractor as required to provide current
inventory as well as historical cross-reference of MPS inventory versus
Shuttle Transportation System (STS) mission. Archives shall be
maintained and archival materials dispositioned in accordance with NASA
and Federal Records Management regulations and procedures.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.2.2.4-a**

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

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

6\. **[TITLE]{.smallcaps}**: Annex 1 - Payload Data Package

7\. **[DESCRIPTION/USE]{.smallcaps}**: To be used by contractor and
payload customer as an agreed-to source for the payloads configuration,
weight and mass properties, avionics, and physical function data for
installation, deployment, and/or retrieval of the payload as related to
the Orbiter. Annex substantiates the agreed-to design interfaces as
described in the payload unique ICD.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Once per payload per
flight, update as required

11\. **[REMARKS]{.smallcaps}**: Drawings referenced in the payload annex
shall be maintained in a central payload data facility for review and
distribution of reference payload data.

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

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

13.1 **[SCOPE]{.underline}**: This package provides annexes for all
payloads and payload equipment flying in the cargo bay.

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

NSTS 21000-A01 *Payload Data Package Blank Book Annex 1*

NSTS 21067 *Instruction Manual for Annex 1*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: Annex 1 - Payload Data
Package shall contain:

a\. Payload Configuration.

b\. Weight and Mass Properties.

c\. Payload Physical Function Data.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by change page or complete reissue. Changes to NSTS
21000-A01 require NASA approval.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE:]{.smallcaps} REVISION 1 2. [DRD
NO.]{.smallcaps}: 1.2.2.5

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Interface Revision Notice (IRN) to Element
Interface Control Documents (ICD's)

7\. [DESCRIPTION/USE]{.smallcaps}: To define changes to ICD's.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: Assumption of an ongoing
requirement; no break in existing submission schedule

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Following each NASA-approved
IRN

11\. [REMARKS]{.smallcaps}: ICD's define the technical interfaces
between the Shuttle System and other systems, and between elements of
the Shuttle System.

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.2.2.5

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

13.1 [SCOPE]{.underline}: The IRN\'s define changes to functional and/or
physical interfaces (1) between the Shuttle System, or elements thereof,
and other systems, or elements thereof, and (2) between Shuttle System
elements involving two or more major program participants, i.e., NASA
Centers, System Contractor, Associate/Element Contractors, Payloads.
IRN's are limited to the applicable documents listed in 13.2.

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

ICD-13M15000 *Space Shuttle Orbiter Vehicle/Main Engine*

ICD-2-0A001 *Shuttle System/Launch Platform Stacking and VAB Servicing*

ICD-2-0A002 *Space Shuttle Launch Pad & Platform*

ICD-2-0A003 *Flight Vehicle/LPS Computational Systems Interfaces*

ICD-2-0A004 *Space Shuttle System/KSC RF Communications & Tracking
Checkout*

ICD-2-0D003 *JSC/USAF Space Shuttle/SCF RF Communications & Tracking*

ICD-2-0D004 *JSC/GSFC Space Shuttle RF Communications & Tracking*

ICD-2-0H001 *Shuttle Vehicle/Ground Range Safety System*

ICD-2-00001 *Shuttle Vehicle Mold Lines and Protuberances*

ICD-2-1A001 *Orbiter/KSC Landing Station*

ICD-2-1A002 *Orbiter Processing Facility/Orbiter Maintenance & Checkout
Facility*

ICD-2-1A003 *Orbiter /Hypergolic Station*

ICD-2-1D003 *Orbiter Landing/Safing & Deservicing Stations*

ICD-2-1D004 *Orbiter & Carrier Aircraft/Mate-Demate Interfaces*

ICD-2-12001 *Orbiter Vehicle/External Tank*

ICD-2-14001 *Orbiter Vehicle/Solid Rocket Booster*

ICD-2-17001 *Orbiter Vehicle/Carrier Aircraft*

ICD-2-2A001 *External Tank/Receiving, Storage & Checkout Station*

ICD-2-24001 *External Tank/Solid Rocket Booster*

ICD-2-4A001 *Solid Rocket Booster/Receiving Processing Station*

ICD-2-4A002 *Solid Rocket Booster Retrieval Station*

ICD-2-19001 *Shuttle/Orbiter/Cargo Standard Interfaces*

NSTS21000-IDD-ISS *International Space Station Interface Definition
Document*

NSTS21000-IDD-MDK *Shuttle/Payload Interface Definition Document Middeck
Accommodations*

NSTS 21000-IDD-SML *Shuttle/Payload Interface Definition Document for
Small Payload Accommodations*

DRD CONTINUATION SHEET

[TITLE]{.smallcaps}: Interface Revision Notice (IRN) to Element [DRD
NO.]{.smallcaps}: 1.2.2.5

Interface Control Documents (ICD's)

[DATA TYPE]{.smallcaps}: 3 [PAGE]{.smallcaps}: 2/2

13\. DATA PREPARATION INFORMATION (CONTINUED):

13.3 [CONTENTS]{.underline}: IRN\'s shall contain functional and/or
physical interface requirements and rationale in sufficient detail to
provide an adequate baseline for planned design efforts by the
interfacing elements. Design requirements/constraints contained in the
IRN\'s are limited to only those necessary to define and control the
subject interface(s).

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: ICD's to be maintained by
IRN incorporation or total reissuance as applicable.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE:]{.smallcaps} REVISION 1 2. [DRD
NO.]{.smallcaps}: 1.2.2.6

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Payload Interface Control Documents (ICD\'s)
and Installation Requirements Documents (IRD\'s)

7\. [DESCRIPTION/USE]{.smallcaps}: ICD\'s - To define the technical
interfaces agreed to between the Space Shuttle Vehicle (SSV) and the
unique payload or on-orbit assembly. ICD\'s provide necessary
requirements for interface definition to support integration hardware
design, payload design and flight product development and include
development of a payload avionics control schematic.

IRD\'s - To define the installation assembly requirements for the
installation of payload to payload elements within the Orbiter by the
Space Shuttle Program. (An IRD is not required for payloads that are
fully assembled prior to installation into the Orbiter.)

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

9\. [INITIAL SUBMISSION]{.smallcaps}: Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Once per payload

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.2.2.6

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

13.1 [SCOPE]{.underline}: The payload-unique ICD\'s provide definition
of the technical interfaces between the Space Shuttle Vehicle and the
unique payload for selected configurations of the payload as applicable.
The payload IRD\'s provide definition of the installation and assembly
requirements of payload to payload interfaces in the Orbiter. ICD's and
IRD's are derived from the applicable documents as appropriate. The
payload avionics control schematic is derived from the payload unique
ICD.

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

NSTS-07700, Volume IV, Book 1 *Configuration Management Requirements
Standard Interfaces*

NSTS-07700, Volume XIV *Shuttle Orbiter/Cargo Standard Interfaces*

Attachment I (ICD-2-19001)

NSTS-21000-IDD-SML *Shuttle/Payload Interface Definition Document for
Small Payload Accommodations*

NSTS-21000-IDD-MDK *Shuttle/Payload Interface Definition Document for
Middeck Accommodations*

NSTS-21000-IDD-ISS *International Space Station Interface Definition
Document*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The contents are based on the
applicable documents as appropriate.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Maintenance shall consist
of revisions by Interface Revision Notice (IRN) and subsequent reissue
of all or part upon IRN incorporation. IRN\'s which incorporate
exceedances outside the experienced data base, waivers, or deviations
require NASA approval. The payload avionics control schematic revisions
to be in accordance with the contractor's engineering and change control
system.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.2.2.7

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Payload Operations Maintenance Requirements
Specification (OMRS) Test Requirements

7\. [DESCRIPTION/USE]{.smallcaps}: To provide the OMRS Board pre- and
post-mate test requirements for verification of Space Station Program
(SSP) hardware interfaces with the payload to satisfy NSTS 14046,
Section 5.3.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: Assumption of an on-going
requirement; no break in existing submission schedule

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Per Flight: Basic release 315
days prior to launch (L-315 days). Cargo Integration Review (CIR) update
release at L-260 days. Baseline release determined by Payload OMRS
Board.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.2.2.7

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

13.1 [SCOPE]{.underline}: The Integration OMRSD File II, Volumes II, IV,
and VI cover requirements for verification of interfaces and related
operational requirements of installed hardware supporting Payload and
Developmental Test Objective/Risk Mitigation Experiments (DTO/RME)
requirements, Human Exploration and Development of Space Technology
requirements, and applicable Requirements Change Notices (RCN's).

13.2 [APPLICABLE DOCUMENTS]{.underline}

NSTS-08171, Files I, II and III *Operations and Maintenance Requirements
and Specification Document*

NSTS 14046 *Payload Verification Requirements*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: RCN's for the OMRSD shall
include requirement numbers, descriptions, measurement/stimuli
identification, specification (pass/fail criteria) and
internal/constraints/ remarks information as defined in NSTS 08171, File
I.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: The OMRSD is to be
changed/maintained using RCN\'s as described in NSTS 08171, File 1.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.2.2.10-a**

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

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

6\. **[TITLE]{.smallcaps}**: Technical Revision to SL-E-0001 and
SL-E-0002

7\. **[DESCRIPTION/USE]{.smallcaps}**: Management and maintenance of
SL-E-0001 and SL-E-0002 will be conducted by the Technical Area Manager
with approval from the Integration Control Board (ICB) and/or Shuttle
Avionics Systems Review (SASR).

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an ongoing
requirement; no break in existing submission schedule.

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

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

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

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

13.1 **[SCOPE]{.underline}**:

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

SL-E-0001 *Specification Electromagnetic Compatibility Requirements*

SL-E-0002 *Specification Electromagnetic Interference Characteristics,
Requirements for Equipment*

Book 1 - Existing Hardware

Book 2 - New or Modified Hardware

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The contractor shall
conduct Technical Interchange Meetings to establish new requirements.
Appropriate change requests shall be documented and processed through
the appropriate Space Station Program (SSP) board/panel.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.2.2.10-b**

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

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

6\. **[TITLE]{.smallcaps}**: Element Avionics Interface Databook Updates

7\. **[DESCRIPTION/USE]{.smallcaps}**: To update information in the
Element Avionics Interfaces Databook, Day-of-Launch Support Databook,
and Post-Flight Data Processing Procedures.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an ongoing
requirement; no break in existing submission schedule.

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

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

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

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

13.1 **[SCOPE]{.underline}**: Updates consist of design or operational
changes approved by the program that impact information contained in the
Element Avionics Interfaces Databook, Day-of-Launch Support Databook, or
Post-Flight Data Processing Procedures.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: Element Avionics
Interface Databook Updates consist of updates to the documents due to
changes in design or operational requirements approved by the program.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.2.2.10-c**

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

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

6\. **[TITLE]{.smallcaps}**: Element Avionics Interface Design Review
Assessment Report

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document avionics technical
hardware and software assessments of proposed element interface avionics
design changes.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: As required

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

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

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: This report provides
technical assessments of design changes that affect element hardware and
software elements avionics design changes.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: Technical assessment
shall include review of design changes, document all discrepancies and
include verification of compliance with Space Station Program (SSP)
requirements.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.3**

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

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

6\. **[TITLE]{.smallcaps}**: Safety and Health Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe the contractor's
safety and health plan for each NASA site.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Contract award plus 30 days

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

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: Clause H.22

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: Applicable to all NASA
centers and sites where the contractor is operational.

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

NHB 1700.1 (VI)-B *NASA Safety Policy and Requirements Document*

29 CFR 1910 *Department of Labor, Occupational Safety and Health
Standards*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The plan shall describe
tasks and activities of safety and health management at each site where
the contractor is operational to assure the identification, evaluation
and elimination/control of safety and health concerns. The plan shall
include the following:

a\. Organization charts(s) which illustrate the functional relationships
and lines of communication between safety, Health and other
organizational elements.

b\. Descriptions of the Safety and Health management function within the
organization including the process through which management decisions
will be made, including notification of the local NASA Safety and Health
organization of critical and catastrophic hazards, corrective actions,
mishaps and deviations or waivers to NASA safety and health
requirements.

c\. Description of the responsibility, authority, and accountability of
safety and health personnel, other contractor organizational elements
involved in the safety and health effort and subcontractor safety and
health personnel. Include the organizational unit responsible for the
execution of safety and health tasks and the position with the authority
to resolve all identified safety and health issues.

d\. Description of the management controls that will be used to ensure
compliance with safety and health regulations.

e\. Cross-reference of safety program requirements (e.g., OSHA, NASA,
local NASA Center) and contractor procedures to avoid duplication of
effort.

f\. Description of the safety program measurement system, including
measurements, metrics, and trend analysis methods. The performance
measurement system should describe responsibility for identifying and
implementing remedial action, recurrence control, and corrective actions
that are necessary to improve performance as indicated by the
performance measurement system.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.3.1.2-b**

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

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

6\. **[TITLE]{.smallcaps}**: Safety Summary Report (SSR)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide information to each
NASA location on accidents affecting the contractor\'s performance.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: By the 15th of the first month
after contract award

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Monthly, on or before the
15th of each month, for the previous month

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

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

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

13.1 **[SCOPE]{.underline}**: The Safety Summary Report provides
information on accidents affecting the contractor's performance.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The SSR shall contain the
following information for each NASA location monthly:

a\. Number of man-hours worked.

b\. Number of new lost-time injury cases.

c\. Number of lost-time days for the month (including previous month\'s
cases).

d\. Number of medical treatment cases.

e\. Number of first aid cases.

f\. Number of miles driven in Government-provided vehicles.

g\. Number of vehicle accidents with damage greater than \$1000.

h\. Total damage cost due to motor vehicle accidents resulting in damage
[\> \$1,000]{.underline}.

i\. Number of accidents which resulted in NASA property damage greater
than \$1000.

j\. Total damage cost to NASA property as a result of accident resulting
in damage [\>]{.underline} \$1,000.

k.  Incident Reports (NASA form 1627 or equivalent) for incidents which
    occurred during the reporting period.

l.  Status on all open incident reports from previous months

m.  Report on any OSHA or EPA violations or inspections.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.3.1.2-c**

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

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

6\. **[TITLE]{.smallcaps}**: Pressure Vessel/System Recertification

7\. **[DESCRIPTION/USE]{.smallcaps}**: Data required to demonstrate
implementation of NMI 1710.3 using the guidelines of NHB 1700.6, on
ensurance that all ground-based pressure vessels and pressurized systems
are certified safe to operate and are recertified periodically.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: 30 days after contract award

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Annually

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

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

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

13.1 **[SCOPE]{.underline}**: The Pressure Vessel/System Recertification
covers all ground-based pressure vessels and pressurized systems under
the contractor's responsibility.

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

NMI 1710.3 *Safety Program for Pressure Vessels and Pressurized Systems*

NHB 1700.6 *Guide for Inservice Inspection of Ground-Based Pressure
Vessels and Systems*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: In accordance with
guidelines in NHB 1700.6.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.3.3.1**

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

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

6\. **[TITLE]{.smallcaps}**: Acceptance Data Package (ADP)

7\. **[DESCRIPTION/USE]{.smallcaps}**: The ADP is an accumulation of
documentation that provides a verified, complete, and current status of
deliverable hardware/software needed by the procuring/using organization
to enable the continuation of required activities.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Submitted with
shipment/transfer of each hardware item or software delivery.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Required with each delivery
of hardware or software from a manufacturer/developer to a using site or
deliveries between using sites.

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

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

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

13.1 **[SCOPE]{.underline}**: ADP\'s are required for all deliverable
hardware items and program software products (and their approved
changes).

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

SN-S-0008 *Software Deliverable Data Package Requirements Specification*

SN-D-0007 *Acceptance Data Package Requirements*

SSP 30695 *Acceptance Data Package Requirement Specification*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The ADP shall be prepared
in accordance with SN-S-0008, SN-D-0007, and SSP 30695, as appropriate.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.4-a**

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

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

6\. **[TITLE]{.smallcaps}**: KSC Work Authorization Documents
(Category 1) Development and Maintenance Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: To define and document
standardized processes, formats, and responsibilities required for
developing, maintaining, approving, and changing KSC Work Authorization
Documents (WAD\'s).

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an on-going
requirement; no break in existing submission schedule

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Submission of each WAD will
be established in accordance with the approval of the Operations and
Maintenance Documentation (OMD) Control Board and will be revised in
accordance with the approved WAD change processes and plans.

11\. **[REMARKS]{.smallcaps}**: NAS10-10900, DRL items 13, 33, and 34

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4 and 1.5

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

13.1 **[SCOPE]{.underline}**: The KSC Work Authorization Documents
(Category 1) Development and Maintenance Plan shall define contractor
responsibilities for the development and maintenance of Category 1
Shuttle processing procedures.

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

S00000-2, File 1 *Technical Operations Procedure Preparation Handbook*

KHB 1710.12 *Technical Operation Procedures Policy*

KVT-HB-0002 *OIS Call Sign/Word Handbook*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The KSC Work
Authorization Documents (Category 1) Development and Maintenance Plan
shall:

> a\. Describe the standardized approach to maintain, update, and
> control the configuration of existing and future WAD\'s (as a minimum
> Category 1) required for each planned flight hardware turnaround
> activity, as well as for support equipment for which the contractor
> has O&M responsibility in accordance with S00000-2, File 1.
>
> b\. Define how Operational Intercommunication System (OIS) call signs
> and call words will be used during operational Shuttle processing.
> This approach shall cover the scope and content of the existing OIS
> Call Sign/Word Handbook (KVT-HB-0002).

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

5.  **[[MAINTENANCE]{.underline}]{.smallcaps}**: Revision level and
    date.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps} 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4-c

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Logistics Performance Report

7\. [DESCRIPTION/USE]{.smallcaps}: To provide trend analyses of key
logistics performance indicators to ensure the infrastructure is capable
of sustaining contract requirements.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: 90 days after contract award

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Monthly Reports

11\. [REMARKS]{.smallcaps}: Frequency of report may be adjusted as
proposed by the contractor.

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4, 1.4.1.2, 1.4.7.2,
1.5.5.4, 1.6

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

13.1 [SCOPE]{.underline}: This report shall cover the total logistics
support of all areas of the SFOC.

13.2 [APPLICABLE DOCUMENTS]{.underline}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The monthly report shall be
submitted in writing and upon request shall be presented as an oral
briefing. The contractor shall maximize the use of electronic data
transfer. The contractor shall provide NASA with electronic access to
the supporting data. The elements of the report are:

> A. Executive summary of performance trending, issues, concerns, and
> recommendations.
>
> B. Program enhancements and major initiatives which are in work by the
> contractor.
>
> C. General overview of monthly expenditures for manpower and material.
>
> D. Performance against standards designated in the SOW.
>
> E. Additional performance indicators:
>
> 1\. Logistics actual work force versus budgeted work force (EP).
>
> 2\. Transportation, Shipping, and Receiving: Hardware damage due to
> transportation.
>
> 3\. Transportation and Receiving: Dock to stock time.
>
> 4\. Provide data/results of Inventory audits/Inventory accuracy
> levels. Copy of submit to NASA property is acceptable.
>
> 5\. Active inventory items at zero balance.
>
> \(a\) Number of Orbiter active inventory items at zero balance.
>
> \(1\) Number of Reparable inventory items at zero balance.
>
> \(A\) Number of Reparable inventory items at zero balance with
> quantity due-out to customer.
>
> \(B\) If data is available, list recurring items at zero balance with
> quantity due-out to customer.
>
> \(2\) Number of Non-reparable inventory items at zero balance.
>
> \(A\) Number of Non-reparable inventory items at zero balance with
> quantity due-out to customer.
>
> \(B\) If data is available, list recurring items at zero balance with
> quantity due-out to customer.

DRD CONTINUATION SHEET

[TITLE]{.smallcaps}: Logistics Performance Report [DRD NO.]{.smallcaps}:
1.4-c

[DATA TYPE]{.smallcaps}: 3 [PAGE]{.smallcaps}: 2/2

[13. DATA PREPARATION INFORMATION (CONTINUED):]{.smallcaps}

13.3 [[CONTENTS (CONTINUED)]{.underline}:]{.smallcaps}

> 5\. (b) Number of Ground active inventory items at zero balance.
>
> \(1\) Number of Reparable inventory items at zero balance.
>
> \(A\) Number of Reparable inventory items at zero balance with
> quantity due-out to customer.
>
> \(B\) If data is available, list recurring items at zero balance with
> quantity due-out to customer.
>
> \(2\) Number of Non-reparable inventory items at zero balance.
>
> \(A\) Number of Non-reparable inventory items at zero balance with
> quantity due-out to customer.
>
> \(B\) If data is available, list recurring items at zero balance with
> quantity due-out to customer.
>
> 6\. Provide the number of non-stock listed demands and the number of
> total demands.
>
> 7\. Integrated Logistics shall provide MTAR and ATLAS documents or a
> streamlined/combined equivalent.
>
> 8\. Provide insight and/or access to all working level metrics
> utilized in the performance of SFOC.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: Revisions as required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.4-d**

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

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

6\. **[TITLE]{.smallcaps}**: Government Furnished Material (GFM) and
Propellants Requirements Forecast

7\. **[DESCRIPTION/USE]{.smallcaps}**: To assure adequate propellant and
GFM supply and distribution planning in support of this contract.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: 90 days after Authority to
Proceed (ATP)

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Six months (beginning after
initial submission)

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4 and Attachment J-9

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

13.1 **[SCOPE]{.underline}**: See item 13.3 and Attachment J-9.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The contractor shall
prepare three-year propellant and GFM forecast. The forecasts shall be
derived from user inputs and historical data.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Revision and date.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE:]{.smallcaps} REVISION 1 2. [DRD
NO.]{.smallcaps}: 1.4-e

3\. [DATA TYPE]{.smallcaps}: 2 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Loss of Capabilities and Corrective Action
Report

7\. [DESCRIPTION/USE]{.smallcaps}: To report a loss of repair, failure
analysis, and production capabilities and to plan corrective action for
flight and/or flight GSE hardware.

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

9\. [INITIAL SUBMISSION]{.smallcaps}: See Submission Frequency

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Government notification as soon
as the Contractor is aware of a loss of repair, failure analysis, and
production capability. Otherwise, monthly submission of DRD report.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4

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

13.1 [SCOPE]{.underline}: This report shall cover the total Logistics
support of all areas of the SFOC.

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

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The contractor shall:

a\. Provide immediate notification in writing, or electronically, to
NASA OPR loss of repair, failure analysis, and production capabilities.
Provide written notification in the next DRD report submission with
preliminary plan of corrective action.

b\. Provide a recovery plan within six months of notification or sooner
for loss of repair, failure analysis, and production capabilities. The
plan shall, as a minimum, include the capability lost, corrective
action, and projected resolution date for each piece of hardware
affected.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Revision and date.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.1.1-b**

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

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

6\. **[TITLE]{.smallcaps}**: Change Requests (CR's) and Reviews

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document proposed changes to
the contractor or baseline effort, including applicable program
requirements.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: As required

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

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000, IRD
CM-097T9A.

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.1.1.1, 1.4.1.5.1,
1.4.1.5.2

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The contractor shall:

a\. Submit a CR to revise any contract-referenced requirement, or to
submit Class 1 engineering design change proposals (EDCP's) or reusable
hardware flight authorizations (RHFA's) for NASA review and approval.

b\. Comment upon NASA-provided CR's originating outside this contract
relating to flight elements.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: A CR submitted to revise
a contract-referenced requirement shall comply with the change content
guidelines listed in the affected requirement. A CR submitted for
approval of Class 1 EDCP's or RHFA's may include briefings, schematics,
drawings, or other documentation deemed appropriate by the contractor.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.1.1-c**

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

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

6\. **[TITLE]{.smallcaps}**: Specification Change Notice

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document the approval of
changes to specific contract controlling specifications.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: As required to correct or
update contract-referenced specifications

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: As required to correct or
update contract-referenced specifications.

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000, IRD
CM-096T9.

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: A Specification Change
Notice details specific changes to contract controlling specifications.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: A Specification Change
Notice shall include the following information, as applicable:

a\. Contractor's name, address, and identification code.

b\. Specification change tracking references, including the number and
revision level of the affected specification, a sequence number and
revision letter serially assigned uniquely for changes to the affected
specification, a contract revision number, engineering change proposal
number, or program change identification number, the configuration item
number covered by the affected specification, and the serial number(s)
of the article(s) affected by the change.

c\. Verbatim changes to be made to the text, tables, or figures in the
affected specification.

d\. Contractual change authority reference added upon approval of the
change.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.1.2-a**

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

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

6\. **[TITLE]{.smallcaps}**: Special Action Requirement (SAR)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To establish requirements for
special action by field sites.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: As required to provide
authority for accomplishing a special action on hardware or software end
items

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

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000, IRD
OM-255T9A.

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: A SAR shall be issued to
establish requirements for problem-related troubleshooting, inspections,
nondestructive evaluation (NDE), transfer of critical hardware, or other
one-time-only tests or operations.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: A SAR shall describe the
system involved, action required, pass/fail criteria, retest
requirements, action effectivity, and rationale supporting the action
requirement as applicable. The SAR shall include a title, tracking
number, date, point-of-contact, and a record of approval signatures.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.1.3-a**

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

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

6\. **[TITLE]{.smallcaps}**: Operational Maintenance Requirements and
Specifications Document Changes

7\. **[DESCRIPTION/USE]{.smallcaps}**: To implement creation, revision
or deletion of Shuttle system operational maintenance requirements and
specifications in accordance with Master Verification Plan requirements.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: As required to support launch
site test planning or as otherwise authorized by the Contracting
Officer's Technical Representative (COTR) or designee

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

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000 IRD
OM-212T9A.

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

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

13.1 **[SCOPE]{.underline}**: The Operational Maintenance Requirements
and Specifications Document (OMRSD) establishes the checkout,
validation, servicing, and maintenance retest requirements for Space
Shuttle Vehicle and ground support equipment as detailed in NSTS 08171
OMRSD File I. OMRSD changes shall be submitted as required by applicable
documents to reflect Master Verification Plan changes, modifications,
and mission unique configurations. OMRSD changes may also be submitted
in response to experience gained from prior turnaround testing,
acceptance testing, or anomaly resolution activities.

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

NSTS 07700-10-MVP-01 *Space Shuttle Master Verification Plan*

NSTS 08171 *Operational Maintenance Requirements and Specifications
Document (OMRSD)*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: OMRSD change content
requirements are detailed in NSTS 08171 OMRSD File I.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated into the OMRSD in accordance with NSTS 08171 OMRSD File I
requirements.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.5.1-a**

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

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

6\. **[TITLE]{.smallcaps}**: Requirement Definition Documents for
Modifications, Mission Kits and GSE

7\. **[DESCRIPTION/USE]{.smallcaps}**: To establish and control the
design, performance, and verification requirements for system
modifications, Orbiter and payload integration mission kits, and ground
support equipment from preliminary design through delivery.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Initial Requirement Definition
Document drafts are submitted one month prior to preliminary design
review.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Revisions submitted as
required

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000 IRD
SE-1437T9A.

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.1.5.1, 1.4.1.5.2,
1.2.1.4.

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

13.1 **[SCOPE]{.underline}**: A Data Type 1 Requirement Definition
Document is required for new modification, mission kit, and GSE designs
which provide or impact a critical flight or ground function. A Data
Type 2 Requirement Definition Document is required for non-critical
designs and designs which are to be certified by similarity with
certified and proven hardware.

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

NSTS 07700, Volume IV *Configuration Management Requirements*

NSTS 07700 Volume X *Space Shuttle Flight and Ground Systems
Specification*

NSTS 07700-10-MVP-01 *Space Shuttle Master Verification Plan*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: A Requirement Definition
Document shall contain a definition including system requirements for
capability, performance, configuration, operation, interfaces, safety,
reliability, life, storage, verification. The document shall also
include a list of design and review documentation products required for
certification.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.5.1-b**

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

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

6\. **[TITLE]{.smallcaps}**: Certification Requirement (CR)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To define the testing and/or
analysis required to certify the design of a hardware item or subsystem.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Certification requirement - no
later than 60 days prior to the scheduled start of certification
testing. Hardware certification requirement - no later than 90 days
prior to the scheduled submittal of certification analysis reports when
certification is by analysis in lieu of testing.

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

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000, IRD
RA-278T9.

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.1.5.1, 1.4.1.5.2,
1.2.1.4

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

13.1 **[SCOPE]{.underline}**: A CR is submitted to define the test
and/or analysis required to certify the design of a new hardware item or
subsystem. A certification requirement change is submitted to revise or
define any new test and/or analysis required to certify the design of an
existing or modified hardware item and subsystem. Certification
requirements for a hardware item or subsystem shall comply with the
requirements specified in the applicable documents.

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

NSTS 07700 Volume IV *Configuration Management Requirements*

NSTS 07700 Volume X *Space Shuttle Flight and Ground System
Specification*

NSTS 07700-10-MVP-01 *Shuttle Master Verification Plan*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: A certification
requirement shall contain the following information, as applicable:

a\. Certification requirement reference and tracking information,
including a certification requirement number, certified part or
subsystem name(s) and number(s), vehicle location(s), vehicle
effectivity.

b\. Certification method (test or analysis) including sequence and
environment (shall include supporting rationale for analysis instead of
test).

c\. Testing requirements (as applicable), including pretest functional
verification requirements, test type, test duration, test constraints,
test article operating mode, pass/fail criteria and tolerances, and
post-test functional verification requirements.

d\. Test article information (as applicable) including test part
serial/lot number(s); the number of test specimens and test allocations;
and test request, procedure, and report references and tracking
information.

e\. Description and explanation of any differences between test parts
and certified parts.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.5.1-c**

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

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

6\. **[TITLE]{.smallcaps}**: Certification Approval Request
(CAR)/Qualification Site CAR

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document certification testing
and analysis results, and the approval of certification of a hardware
item or subsystem design. A qualification site CAR, used for high cost
or sophisticated certification tests, documents test results for review
prior to test teardown and the tentative approval of certification of a
hardware item or subsystem design pending formal report preparation,
submittal, and approval.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: CAR - no later than 60 days
after completion of certification testing and analysis, but no less than
60 days prior to the event constrained by item certification.
Qualification site CAR may be submitted prior to test teardown and
formal report preparation.

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

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000, IRD's
RA-280T9, RA-281T9, RA-282T9, and RA-283T9.

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.1.1.1, 1.4.1.5.1,
1.4.1.5.2, 1.2.1.4

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: A CAR is submitted with all
associated test or analysis reports to request approval of certification
of the design of a new or modified hardware item or subsystem. A CAR for
qualification site approval pending preparation and submittal of formal
reports may be utilized for high cost or sophisticated certification
tests where test is constraining program milestones.

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

NSTS 07700 Volume IV *Configuration Management Requirements*

NSTS 07700 Volume X *Space Shuttle Flight and Ground System
Specification*

NSTS 07700-10-MVP-01 *Shuttle Master Verification Plan*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: CAR's shall contain the
following information, as applicable:

a\. Certification reference and tracking information, including the
associated certification requirement number, certified part or subsystem
name(s) and number(s), vehicle location(s), and vehicle effectivity.

b\. Certified item supplier information, including supplier name,
supplier part number(s), and supplier purchase order number.

c\. Test reports (as applicable), including test agency name and
location, test objectives, test hardware and setup description including
drawings and photographs, test start and completion dates, validated
as-run test procedures and variance descriptions, validated test
results, data, laboratory notes, and associated analysis results, and
test anomaly and test hardware failure descriptions, analyses, and
resolutions.

d\. Analysis reports (as applicable), including analysis objectives,
detailed analysis logic, and analysis results and conclusions.

e\. Formal certification recommendations.

DRD Continuation Sheet

**[TITLE]{.smallcaps}**: Certification Approval Request (CAR)/ **[DRD
NO.]{.smallcaps}**: **1.4.1.5.1-c**

Qualification Site CAR

**[DATA TYPE]{.smallcaps}**: 1 **[PAGE]{.smallcaps}**: 2/2

13\. DATA PREPARATION INFORMATION (CONTINUED):

CAR's for qualification site approval pending preparation and submittal
of formal reports shall contain the following information, as
applicable:

a\. Certification reference for tracking information, including the
associated certification requirement number, certified part or subsystem
name(s) and number(s), vehicle location(s), and vehicle effectivity.

b\. Test reports, including test agency name and location, test
objectives, test hardware and setup description, test start and
completion dates, test environments and sequence descriptions,
verification of calibration, adjustment, and proper operation of test
facilities or instruments, key test results (parametric) and associated
test evaluations, and test anomaly and test hardware failure
descriptions, evaluations, and resolutions.

c\. Formal certification recommendations.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.5.2**

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

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

6\. **[TITLE]{.smallcaps}**: Cargo Integration Hardware User
Documentation

7\. **[DESCRIPTION/USE]{.smallcaps}**: To define payload user
information necessary for payload design.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Upon payload request

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: As needed per payload
request

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

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

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

13.1 **[SCOPE]{.underline}**: Documentation as required to provide users
with information on how the hardware operates, its capabilities, and if
necessary how the hardware should be maintained. Existing documentation
is listed in 13.2.

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

NSTS 07700 Vol. XIV, Appendix 10 *System Description and Design Data*

*Integration Hardware*

STS 86-0186C *Payload Integration Hardware Summary*

JSC-23004 *Remotely Operated Electrical Umbilical Users Manual*

SSD95D0593 *Middeck Accommodations Rack (MAR) Users Manual*

NSTS 21000-IDD-MAR *Shuttle/MAR/Payload Interface Definition Document*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: Cargo Integration
Hardware User Documentation shall contain:

a\. Definition.

b\. Interfaces.

c\. Performance/Physical characteristics.

d\. Cleaning and maintenance.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes incorporated
by updates or complete revisions as required. Changes to NSTS 07700 Vol.
XIV, Appendix 10 and NSTS 21000-IDD-MAR require NASA approval.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.6.1-a**

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

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

6\. **[TITLE]{.smallcaps}**: Inputs to JSC 08934, Shuttle Operational
Data Book (SODB)

7\. **[DESCRIPTION/USE]{.smallcaps}**: The Shuttle Operational Data Book
(SODB), a part of the Operational Data Exchange System, is the single
authoritative flight planning and operations support source for
validated Orbiter performance, configuration, mass property, and
emergency rescue data. SODB inputs consist of updates reflecting
configuration or system performance changes for specific vehicles or
missions, and responses to requests for off-nominal performance
characteristics or constraints data.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: As required

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Updates submitted as
required to assure current and accurate configuration and system
performance data are available for flight planning and operations
support.

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000, IRD
SE-492T9.

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

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

13.1 **[SCOPE]{.underline}**: SODB updates are required to reflect
modifications and mission-specific configuration and system performance
characteristics. SODB updates are also required to incorporate pertinent
Shuttle operational data developed in response to NASA requests.

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

JSC 08934 *Shuttle Operational Data Book*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: SODB updates shall
contain data as follows:

a\. Volume I updates shall contain Shuttle flight performance
characteristic, system limitation, and operational constraint revisions
by system and by vehicle.

b\. Volume II updates shall contain Orbiter and payload mass property
revisions by vehicle and by flight.

c\. Volume III updates shall contain off-nominal system performance
characteristic revisions.

d\. Volume IV updates shall contain Orbiter configuration, hazard,
ground operation, and requirement revisions for crew rescue following
landing. Orbiter configuration shall include vehicle structure,
subsystems, plumbing, wiring, mission kits, and cargo. Volume IV part 1
updates shall include source reference document revisions for Orbiter
landing emergency rescue data, and part 2 updates shall include changes
to crew rescue and emergency situation quick-reference guides for
contingency response teams.

e\. Volume V updates shall contain Orbiter flight capability envelope
revisions.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Volume changes shall
be incorporated by page change or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.6.1-d**

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

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

6\. **[TITLE]{.smallcaps}**: Non-Flight Constraint (NFC) Disposition

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document a determination for
each vehicle and each flight that an open anomaly does not constrain
flight.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Within 10 working days of
problem confirmation

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Prior to each flight for
each open anomaly

11\. **[REMARKS]{.smallcaps}**: References made to NAS9-19000, IRD
SE-1667T9.

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

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

13.1 **[SCOPE]{.underline}**: Refer to NSTS 08126 to determine which
open anomalies require NFC dispositions.

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

NSTS 08126 *Problem Reporting and Corrective Action Requirements*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: NFC dispositions shall
include all information used to develop the contractor's recommendation
and supporting rationale. NFC dispositions shall comply with NSTS 08126.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.6.1-e**

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

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

6\. **[TITLE]{.smallcaps}**: Orbiter Payload Bay and Mission Kit
Configuration Data

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide a Computer-Aided
Design (CAD) database of the Orbiter payload bay configuration with
payloads and mission kits installed for use in flight operations
assessments including RMS proximity operations and clearance analyses.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Submitted as required by the
standard system requirements and verification schedule, the
payload-unique documentation and analysis schedule, or as requested by
the Contracting Officer's Technical Representative (COTR) or the COTR's
designee.

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

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000, IRD
SE-1724T9A.

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

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

13.1 **[SCOPE]{.underline}**: The CAD database shall be prepared for
planned RMS-use missions and as requested by NASA. The CAD database
shall be transmitted to NASA electronically.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The CAD database shall
include mission-specific Orbiter payload bay configuration information,
including installed payloads and mission kits.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by transmission of revision.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.6.1-f**

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

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

6\. **[TITLE]{.smallcaps}**: Master Measurement Lists (MML)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document the measurements and
stimuli (M/S) needed for flight and ground operations data flow between
the Space Shuttle Vehicle (SSV) elements (Orbiter, ET, SSME, SRB),
payloads, ground equipment, and facilities.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Each flight as required to
support ground turnaround and flight operations

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

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000, IRD
DM-141T9A.

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

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

13.1 **[SCOPE]{.underline}**: MML's shall be prepared for each flight
covering the measurements and stimuli generated during the applicable
operational or processing activity as follows:

a\. Shuttle Operational Instrumentation - measurements and stimuli
generated on Shuttle flight hardware elements and payloads which are
needed by the flight crew or ground personnel during flight operations
or ground processing operations including performance evaluation,
verification testing, maintenance, servicing, and safing activities.

b\. Orbiter Ground Measurement List - Orbiter-related ground equipment
measurements and stimuli.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: MML's shall include:

a\. Measurement and stimuli identified by number (coded by SSV
element/payload, subsystem, type, signal format, general sensor
location, and ground equipment element as applicable).

b\. Title.

c\. Usage (displayed, recorded, telemetered, routed to ground support
equipment, etc., as applicable).

d\. Vehicle/ground equipment effectivity as applicable.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.4.1.6.1-g**

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

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

6\. **[TITLE]{.smallcaps}**: Instrumentation Program and Components
Lists (IPCL's)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To identify measurement
channelization, signal routing, and probable measurement inaccuracies,
and control the configuration of the Orbiter Instrumentation System for
each Orbiter flight.

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

9\. **[INITIAL SUBMISSION]{.smallcaps}**: 45 days prior to each Orbiter
flight, or as otherwise authorized by the Contracting Officer Technical
Representative (COTR) or designee

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

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000, IRD
DM-142T9.

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

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

13.1 **[SCOPE]{.underline}**: IPCL's shall for each Orbiter flight shall
describe and control the configuration of sensors, signal conditioners,
and data acquisition equipment encompassing both Operational
Instrumentation (OI) and Modular Auxiliary Data Systems (MADS)
Instrumentation. IPCL's do not cover sensors or signal conditioners
unique to a subsystem or those functions uniquely transferred between
computer(s) and the Pulse Code Modulator (PCM) system.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: IPCL documents shall be
divided into the following major sections and shall include a legend
explaining headings, fields, and codes used in the document.

a\. Equipment List - identifies the location, part numbers, sensor
reference designators, and installation drawings of sensors and signal
conditioners used to implement OI and DFI measurements.

b\. Signal Conditioner and Telemetry Loading - presents details of
signal conditioners, defines signal routing from sensor to signal
conditioner to Multiplexer/Demultiplexer (MDM) or PCM Multiplexer
(PCM-MUX) or Frequency Division Multiplexer (FDM), Displays and Controls
(D&C) and recorder data acquisition equipment. Also provides
MDM/FDM/PCM-MUX channel identification.

c\. PCM-MUX and Downlink Format - includes details on MDM/FDM loading
and PCM downlink formats.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE**: BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.2.1-a**

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

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

6\. **[TITLE]{.smallcaps}**: SRB Failure Modes and Effects Analysis
(FMEA)

[7. **DESCRIPTION/USE**]{.smallcaps}:

> a\. To determine the possible modes of each failure, and the effects
> of each failure.
>
> b\. To classify the criticality of all hardware.

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

9.  **[INITIAL SUBMISSION]{.smallcaps}**:

> a\. SRB and Range Safety Command Destruct System Level FMEA - One time
> with revisions
>
> b\. Component Level FMEA - One time with revisions

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

> a\. SRB and Range Safety Command Destruct System Level FMEA
>
> \- Immediate updates six (6) weeks prior to Flight Readiness Review
> (FRR)
>
> \- Periodic updates a minimum of once per year
>
> b\. Component Level FMEA
>
> \- Submitted with Critical Design Review (CDR) data package, revisions
> as required
>
> \- Initial submission four (4) weeks prior to transfer of first flight
> article

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: DRD 1.4.2.1-b

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

13.1 **[SCOPE]{.underline}**: This DRD establishes the content, format,
maintenance, and submission requirements for the SRB and Range Safety
Command Destruct System Level FMEA's and Component Level FMEA's.

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

> NSTS 5300.4(1D-2) *Safety, Reliability, Maintainability and Quality
> Provisions for the Space Shuttle Program*
>
> NSTS 22206, Rev. A *Instructions for Preparation of Failure Modes and
> Effects Analysis (FMEA) and Critical Items List (CIL)*

[13.3 **[CONTENTS]{.underline}**]{.smallcaps}: The FMEA's shall document
qualitative reliability analyses, identify failure modes and effects,
and classify failure mode criticalities.

a\. The SRB and Range Safety Command Destruct System Level FMEA shall
meet the intent of the NSTS 5300.4(1D-2) and shall be performed using
NSTS 22206, Rev. A as a guide.

b\. The Component Level FMEA's shall be prepared and/or updated on
criticality 1, 1R, and 3 hardware under the Contractor's design
responsibility. The Component Level FMEA's shall meet the intent of NSTS
5300.4(1D-2) and shall be performed using NSTS 22206, Rev. A as a guide.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: As specified in NSTS 22206,
Rev. A or as mutually agreed to by the Contractor.

[13.5 **[MAINTENANCE]{.underline}**]{.smallcaps}:

> a\. The System Level FMEA shall be revised as necessary for each
> flight. All applicable changes shall be incorporated. Changes shall be
> accomplished by change pages or a complete reissue.
>
> b\. The Component Level FMEA shall be revised by the Contractor or his
> vendor whenever a design change that can affect the FMEA's is
> performed.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE**: BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.2.1-b**

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

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

6\. **[TITLE]{.smallcaps}**: SRB and Range Safety Command Destruct
System Critical Items List (CIL)

[7. **DESCRIPTION/USE**]{.smallcaps}: To provide a listing of all
criticality category 1, 1R, and 3 hardware identified in the SRB and
Range Safety Command Destruct System Level FMEA.

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

9.  **[INITIAL SUBMISSION]{.smallcaps}**: One time with revisions
    four (4) weeks prior to transfer of first flight articles.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: One time with revisions:
(a) Immediate updates six (6) weeks prior to Flight Readiness Review
(FRR); and (b) Periodic updates a minimum of one (1) per year.

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

12\. **[INTERRELATIONSHIP]{.smallcaps}**: DRD 1.4.2.1-a

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

13.1 **[SCOPE]{.underline}**: This DRD establishes the content, format,
maintenance, and submission requirements for the SRB CIL.

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

NSTS 5300.4(1D-2) *Safety, Reliability, Maintainability and Quality
Provisions for the Space Shuttle Program*

NSTS 22206, Rev. A *Instructions for Preparation of Failure Modes and
Effects Analysis (FMEA) and Critical Items List (CIL)*

[13.3 **[CONTENTS]{.underline}**]{.smallcaps}: The CIL shall document
and provide rational for retention for the critical SRB and Range Safety
Command Destruct System failure modes and effects identified in the SRB
and Range Safety Command Destruct System Level FMEA.

> The CIL shall meet the intent of NSTS 5300.4(1D-2). The CIL shall be
> prepared using NSTS 22206, Rev. A, Instructions for Preparation of
> Failure Modes and Effects Analysis (FMEA) and Critical Items List
> (CIL).

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: As specified in NSTS 22206,
Rev. A or as mutually agreed to by the Contractor.

[13.5 **[MAINTENANCE]{.underline}**]{.smallcaps}: The SRB and Range
Safety Command Destruct System CIL shall be revised as necessary for
each flight. All applicable changes shall be incorporated. Changes shall
be accomplished by change pages or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE**: BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.2.1-d**

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

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

6\. **[TITLE]{.smallcaps}**: SRB Mass Properties Status Report

[7. **DESCRIPTION/USE**]{.smallcaps}: To provide necessary mass
properties data for test, flight evaluation, and recovery.

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

9.  **[INITIAL SUBMISSION]{.smallcaps}**: Beginning with first flight
    after Authority to Proceed (ATP) and in accordance with the
    frequency stated in Block 10.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: A Preflight Status Report
will be delivered for each flight. The report date is contingent upon
flight schedule dates. Quarterly status reports will be submitted within
ten (10) working days after receipt of Solid Rocket Motor (SRM) data.

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

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

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

13.1 **[SCOPE]{.underline}**: This DRD establishes the requirements for
mass properties evaluations and reporting.

13.2 [**[APPLICABLE DOCUMENTS]{.underline}**:]{.smallcaps} All SRB
documentation for test and flight hardware.

[13.3 **[CONTENTS]{.underline}**]{.smallcaps}: The content shall comply
with the content established in the initial preparations of the
evaluations and reports.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: The format shall comply
with the format established in the initial preparations of the
evaluations and reports.

[13.5 **[MAINTENANCE]{.underline}**]{.smallcaps}: The reports shall be
supported by detailed backup data from the computer base and associated
Mass Properties tape.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE**: REV. 1]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.2.1-e**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:
05/2002

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

6\. **[TITLE]{.smallcaps}**: SRB Final Flight Evaluation Report

[7. **DESCRIPTION/USE**]{.smallcaps}: To provide a report which contains
results of the SRB/Shuttle Range Safety System (SRSS) flight performance
evaluation.

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

9.  **[INITIAL SUBMISSION]{.smallcaps}**: See Block 10.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Deliver within 65 days
after a shuttle launch.

11\. **[REMARKS]{.smallcaps}**: The subject document consists of results
from the flight data evaluation and post flight damage assessment.

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

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

13.1 **[SCOPE]{.underline}**: This DRD establishes the requirements to
prepare a detailed report specifying SRB/SRSS flight performance in the
following areas:

a\. SRB Mass Properties

> b\. SRB Thrust Vector Control (TVC) System
>
> c\. SRB Structures and Loads
>
> d\. Pressure, Vibration and Acoustic Environments
>
> e\. SRB Ascent, Reentry and Ascent Base Aerodynamic Heating
>
> f\. SRB Temperature and Thermal Protection System (TPS) Performance
>
> g\. SRB Electronics and Instrumentation
>
> h\. SRB Separation, Reentry and Recovery Subsystems
>
> i\. SRB Hardware Assessment
>
> j\. Shuttle Range Safety System (SRSS)

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

MSFC-PLAN-1228 *Operational Space Shuttle Flight Evaluation Plan*

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

The report shall contain, but not be limited to the following
information:

a\. Evaluation of SRB hardware performance and operational
characteristics

b\. Correlation of data with ground test results and design analysis in
support of system requirements

c\. Effects on overall system performance and operational
characteristics

d\. Verification of performance of configuration modifications for the
SRB

e\. Identification of performance trends associated with SRB operation,
which might lead to a future problem or issue

f\. History of previous hardware performance and/or problems, issues and
In-Flight Anomalies (IFA's)

g\. Post-flight inspection results

[13.4 **[FORMAT]{.underline}**]{.smallcaps}: The Contractor's format is
acceptable.

[13.5 **[MAINTENANCE]{.underline}**]{.smallcaps}: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE**: BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.2.1-f**

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

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

6.  **[TITLE]{.smallcaps}**: Solid Rocket Booster (SRB) Project
    Management Plan

7.  **[DESCRIPTION/USE]{.smallcaps}**: To provide a description of the
    Contractor's methods for accomplishing the SRB Program requirements.

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

9.  **[INITIAL SUBMISSION]{.smallcaps}**: Preliminary 60 days after
    assumption of SRB Element under Space Flight Operations Contract
    (SFOC).

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Updates as required to
reflect current management philosophy.

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

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

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

13.1 **[SCOPE]{.underline}**: This DRD establishes the content, format,
maintenance, and submission requirements for the SRB Management Plan.
The plan shall be summary in nature with references to the internal
procedures and shall describe the Contractor's practice and approach
for, managing and controlling the SRB Program Tasks, management
interfaces, time phased relationships of tasks and program elements and
the criteria against which performance may be judged.

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

10CEI-0001 *Contract End Item Specification, Part 1 Integrated Solid
Rocket Booster (ISRB) Operational Flights (BI007 and Subsequent
Flights)*

NSTS 07700, Volume V *Space Shuttle Information Management Requirements*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The plan shall summarize
the Contractor's methods for accomplishing and managing the SRB Program
tasks. In addition, the plan shall describe those management systems
utilized in defining and delegating task assignments and define the
organizational relationships of the Contractor and the Government. The
plan includes Class I Change and Out-of-family definitions. Any
organizational consolidation and/or horizontal integration activities
shall be documented in the plan.

[13.4 **[FORMAT]{.underline}**]{.smallcaps}: The Contractor's format is
acceptable.

[13.5 **[MAINTENANCE]{.underline}**:]{.smallcaps} The plan shall be
maintained current by page revision or complete reissue, to reflect all
approved program changes.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. **DPD NO:** 821 **ISSUE:** BASIC 2. **DRD NO: 1.4.2.1-g**

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

5\. **PAGE:** 1

6\. **TITLE:** SRB and Range Safety command Destruct System Flight
Hazard Analysis

7\. **DESCRIPTION/USE:** To document SRB flight hazards and to provide
status of their resolution.

8\. **DISTRIBUTION:** Per Prime Contractor's letter.

9\. **INITIAL SUBMISSION:** See below.

10\. **SUBMISSION FREQUENCY:** One time and revisions, updated annually
or prior to each flight if mandated by NSTS 22254 criteria for mission
updates.

11\. **REMARKS:**

12\. **INTERRELATIONSHIP:** DRD 1.4.2.1-a, SRB Failure Modes and Effects
Analysis (FMEA), and DRD 1.4.2.1-b, SRB and Range Safety Command
Destruct System Critical Items List (CIL)

13\. **DATA PREPARATION INFORMATION:**

13.1 **SCOPE:** This DRD establishes the preparation, maintenance, and
submission requirements for the Hazard Analysis Report.

13.2 **APPLICABLE DOCUMENTS:**

> NHB 5300.4(1D-2) *Safety, Reliability, Maintainability and Quality
> Provisions for the Space Shuttle Program; System Safety*
>
> NSTS 22254 *Methodology for Conduct of NSTS Hazard Analysis*

13.3 **CONTENTS:** The Hazard Analysis Report shall contain hazard
reports and hazard fault trees. The hazard reports shall meet the
requirements as defined in NSTS 22254.

13.4 **FORMAT:** As mutually agreed upon by the Prime Contractor and the
Subcontractor.

13.5 **MAINTENANCE:** The SRB and Range Safety, Command Destruct System
Flight Hazard Analysis shall be revised annually or as necessary for
each flight. All applicable changes shall be incorporated. Changes shall
be accomplished by change pages or complete reissue of the document.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.1-a

3\. [DATA TYPE]{.smallcaps}: 4 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Software User\'s
Manuals for Software Support Tools

7\. [DESCRIPTION/USE]{.smallcaps}: To define procedures for assisting
the user in execution of the BFS software support tools.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10 [SUBMISSION FREQUENCY]{.smallcaps}: As required; products will be
submitted at CI for each OI system.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.1

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

13.1 [[SCOPE]{.underline}]{.smallcaps}: The documents provide procedures
for executing the BFS support tools during the FSW development builds
and reconfiguration processes.

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

JSC-20183 *Flight Software Build and Reconfiguration Support Tools*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Deliverable documentation is
specified in JSC-20183, Flight Software Build and Reconfiguration
Support Tools. These documents shall contain:

a\. Reference documents.

b\. Execution instructions.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.1-b

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Software
Requirements and Specifications Documents for Software Support Tools

> 7\. [DESCRIPTION/USE]{.smallcaps}: These documents define the
> requirements and specifications for BFS software support tools used to
> perform FSWAT development.

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

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission

schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As required; products will be
submitted at CI for each OI system.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.1

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

13.1 [[SCOPE]{.underline}]{.smallcaps}: The documents cover the
requirements and specifications for BFS software support tools used for
FSWAT development.

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

JSC-20183 *Flight Software Build and Reconfiguration Support Tools*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Deliverable documentation is
specified in JSC-20183, Flight Software Build and Reconfiguration
Support Tools. These documents shall contain:

a\. Programming requirements.

b\. Design requirements.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.1-c

3\. [DATA TYPE]{.smallcaps}: 4 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Software Design
Document (SDD) for Software Support Tools

7\. [DESCRIPTION/USE]{.smallcaps}: To document the detailed design of
the BFS software support tools.

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

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission

schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As required; products will be
submitted at CI for each OI system.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.1

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

13.1 [[SCOPE]{.underline}]{.smallcaps}: This document provides a
high-level description of the software program and a description of each
procedure in the program.

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

JSC-20183 *Flight Software Build and Reconfiguration Support Tools*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Deliverable documentation is
specified in JSC-20183, Flight Software Build and Reconfiguration
Support Tools. These documents shall contain:

a\. System requirements.

b\. Program overview.

c\. Program language.

d\. Program interfaces.

e\. Limitations.

f\. Procedures.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.1-d**

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

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

6\. **[TITLE]{.smallcaps}**: Software Quality Report, Backup Flight
System

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide management and
customer visibility into the status of the software quality for the
Shuttle Backup Flight Software Program.

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

9**. INITIAL SUBMISSION:** Assumption of an ongoing requirement; no
break in existing

submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Products shall be submitted
as authorized by the Contracting Officer Technical Representative
(COTR), or designated representative, with planned submittal
semi-annually - no later than 21 days following close of reporting
period.

11\. **[REMARKS]{.smallcaps}**: Reference is made to contract
NAS9-19000/IRD SE-1616T9

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The Software Quality Report
covers activities occurring during a period of six months (January
through June and July through December).

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The report shall contain
the following:

a\. Part 1 - Summary of Software Quality Assurance (SQA) activities
during the reporting period. These activities include:

1\. Software procedural and method enhancements.

2\. Quality and configuration audits.

3\. Product release verifications.

4\. Program change control.

5\. SQA quality metrics summary.

b\. Part 2 - Summary of quality metrics for the reporting period. These
metrics trend analysis charts with information on early detection
percentages and process and product error rates for Operational
Increments (OI\'s). Corrective actions to the software process are
included for the post First Article Configuration Inspection (FACI) and
post Configuration Inspection (CI) product errors. Previous reported
corrective actions are tracked until closure.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.1-g**

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

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

6\. **[TITLE]{.smallcaps}**: Backup Flight System (BFS) Software
Authorization Sheet (SAS) and Patches

7\. **[DESCRIPTION/USE]{.smallcaps}**: To formally release software
developed to satisfy testing, training, and mission objectives in the
laboratory environment.

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

9\. **INITIAL SUBMISSION:** Assumption of an ongoing requirement; no
break in existing submission

schedule.

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

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

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

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

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: SAS is a form utilized to
request a patch (modify software) to support facility testing. It is
submitted/requested through the Test and Operations (T&O) Board.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: SAS\'s shall contain:

a\. Descriptive title.

b\. SAS number.

c\. Software system affected.

d\. Originator.

e\. Need date of change.

f\. Type change.

g\. Type patch.

h\. Reason for change.

i\. Concurrence.

j\. Authorized facility.

k\. Description of change.

l\. General Purpose Computer (GPC) configuration.

m\. Mass Memory Unit (MMU) areas affected.

n\. Type release - restricted/unrestricted.

o\. Engineering Orders (EO\'s)

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.1-k**

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

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

6\. **[TITLE]{.smallcaps}**: Measurement Stimulus Identification (MSID)
Assignment and Integration (Downlist/Downlink)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To establish Measurement Stimulus
Identification (MSID) numbers and channelization for vehicle hardware
and software measurements.

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

9\. **[INITIAL SUBMISSION:]{.smallcaps}** As required.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Products shall be submitted
as authorized by the Contracting Officer\'s Representative (COTR) or
designated representative.

11\. **[REMARKS]{.smallcaps}**: Reference is made to NAS9-19000/IRD
SE-1616T9

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

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

13.1 **[SCOPE]{.underline}**: Upon request from CR and DCR initiators,
and subsystem users, MSID numbers and channelization are assigned for
all vehicle hardware and software parameters.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: Master Change Records
(MCR\'s), Software Change Requests (SCR\'s), Program Requirements
Control Board Directives (PRCBD), and the Data Integration Plan (DIP),
volume III.

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The measurement numbers
are assigned from the MSID log book per the requirements in the Data
Integration Plan (DIP), volume III. The measurements and channelization
are assigned per the requirements of the modification and the
engineering configuration drawings.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by MCR\'s, SCR\'s and PRCBD\'s.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.1-n

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Telemetry Format Load/Decommutation Format
Load/Fetch Pointer Load (TFL/DFL/FPL) Universal Patch Format (UPF)
Patches

7\. [DESCRIPTION/USE]{.smallcaps}: To revise the TFL/DFL/FPL contents of
the Mass Memory Unit (MMU) after a MMU build.

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

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission

schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Patch to be delivered no later
than seven working days following approval of the authorizing Change
Request (CR) by the Shuttle Avionics Software Control Board (SASCB) or
per SASCB negotiated schedules.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.1

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

13.1 [[SCOPE]{.underline}]{.smallcaps}: The patch contains revised
TFL/DFL/FPL contents with associated MMU memory locations.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}: Software Change
Requests \[SCR\'s\]

JSC 08338 *Shuttle Avionics Mass Memory Unit Computer Program
Integration Plan (MIP)*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Release of TFL/DFL/FPL UPF
patch includes products specified in the Shuttle Avionics Mass Memory
Unit Computer Program Integration Plan (MIP), JSC 08338, as deliverables
for each patch. Explicit patch contents are defined in the MIP.

13.4 [[FORMAT]{.underline}]{.smallcaps}: The patch format is controlled
through the MIP, JSC 08338. The patch is delivered in an electronic
dataset.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.1-q

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Develop/Evaluate MAST II/STAR Reconfiguration
Data Change Requests (DCRs)

7\. [DESCRIPTION/USE]{.smallcaps}: To request a change to the Flight
Software reconfigurable data.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
required to support Flight Software reconfiguration schedules.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.1

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

13.1 [SCOPE]{.underline}: MAST II/STAR DCRs are used to request a change
to the Flight Software reconfigurable data including vehicle, payload,
system management, booster, main engine, and remote manipulator system
(RMS).

13.2 [APPLICABLE DOCUMENTS]{.underline}:

NSTS 10784 *Space Shuttle Telemetered and Recorded Data Format
Requirements*

JSC 20201 *Operational Shuttle Data Reconfiguration*

JSC 18206 *Shuttle Data Integration Plan Volumes I and III*

SCR 89053 *SASCB Process Documentation: MAST II/STAR Reconfiguration*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The following DCRs are
included:

> a\) Vehicle Definition (VDF)
>
> b\) Vehicle Occurrence (VOC)
>
> c\) Mission Definition (MDF)
>
> d\) Mission Occurrence (MOC)
>
> e\) MAST II Mission Build Specification
>
> f\) STAR SM Mission Build Specification
>
> g\) System management (SM) VE/VEH
>
> h\) Cargo Element ( payload unit)
>
> i\) Cargo Bay Mission (CBM)
>
> j\) Orbiter Interface Unit (OIU) Recon Tables
>
> k\) Telemetry Occurrence (TOC)
>
> l\) RMS Level C paper DCR\'s
>
> m\) SME paper DCR\'s
>
> n\) SRB/SRM Calibration paper DCR\'s
>
> o\) Data Integration Plan (DIP) paper DCR\'s
>
> p\) Special KSC payload/vehicle paper DCR\'s
>
> q\) Shuttle Data Processing (SDP) Calibration Mod Update paper DCR\'s

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.2-a

3\. [DATA TYPE]{.smallcaps}: 1 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Integrated Hardware and Software Test
Implementation Plan

7\. [DESCRIPTION/USE]{.smallcaps}: This document establishes the
preliminary plan for allocating all hardware and software changes to
Shuttle Avionics Integration Laboratory (SAIL) test cases or other
alternative verification method.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Draft Plan Launch minus 349 days
(L-349) and Final Plan Launch minus 293 days (L-293) prior to first
flight.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Once per Operation Increment
(OI); update as required

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.2

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

13.1 [SCOPE]{.underline}: This plan establishes the method and
responsible organization for verification of each hardware and software
changes associated with the OI software release for which it was
developed. A hardware change that is not associated with a specific OI
release will be submitted with the OI that it will be first flown.

13.2 [APPLICABLE DOCUMENTS]{.underline}: OI content listings for Primary
Avionics Software System (PASS) and Backup Flight System (BFS); Software
Change Requests (CR\'s) and Discrepancy Report (DR\'s); Program
Requirements Control Board (PRCB) directives.

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The plan shall include a
table of all hardware and software changes cross-referenced with
verification test cases or alternative verification methods, responsible
organizations, and PASS/BFS applicability. The following information
shall be given for each hardware or software change: title, reference
CR\'s/DR\'s, flight software modules affected if applicable, reason for
change, and test requirements. Each proposed test case shall describe
the events necessary to assure verification of the changes addressed in
the test. Anticipated unique SAIL configuration or math model
requirements will also be identified.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.2-b

3\. [DATA TYPE]{.smallcaps}: 1 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Integrated Avionics Verification Test
Requirements Matrix

7\. [DESCRIPTION/USE]{.smallcaps}: To document the test requirements for
the Shuttle Avionics Software Control Board (SASCB) to baseline.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Engineering Cycle: Draft - Launch
minus 272 days (L-272), Final - Launch minus 251 days (L-251). Flight
Cycle: Draft - Launch minus 140 days (L-140), Final - Launch minus 112
days (L-112)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Engineering Cycle: once per
Operational Increment (OI) release. Flight Cycle: once per flight

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.2

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

13.1 [SCOPE]{.underline}: This document identifies the test cases to be
performed in a test series.

13.2 [APPLICABLE DOCUMENTS]{.underline}: Change Requests (CR\'s),
Discrepancy Reports (DR\'s), General Purpose Computer Memory Patches
(GMEM\'s), Program Requirements Control Board (PRCB) Directives, and
Developmental Test Objectives (DTO\'s). Data will be available in
databases, FACI/CI datapacks and PRCB minutes.

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The document shall contain a
listing of all test cases to be performed. Included is supporting
rationale for the test including cross-reference to CR\'s, DR\'s,
GMEM\'s, DTO\'s, or PRCB directive. Each CR, DR, GMEM, and applicable
PRCB directive shall be cross-referenced to a Shuttle Avionics
Integration Laboratory (SAIL) test case or alternative verification
method. Responsible organizations and individuals shall be identified
for each test case.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes will be updated as
required by page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.2-c**

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

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

6\. **[TITLE]{.smallcaps}**: Shuttle Avionics Integration Laboratory
(SAIL) Test Data Requirements Document

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide requirements for the
generation and processing of SAIL test data.

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

9\. **INITIAL SUBMISSION:** Assumption of an ongoing requirement; no
break in existing submission

schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Update as required

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

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

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

13.1 **[SCOPE]{.underline}**: This document defines SAIL test data
products and Orbiter Data Reduction Complex (ODRC) processing
requirements.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The document shall define
post data products, a data matrix format for requesting these products,
and data processing requirements.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.2-d

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Integrated Avionics Test Requirements Document

7\. [DESCRIPTION/USE]{.smallcaps}: To establish the detailed plans for
integrated system level avionics verification, site acceptance, and
regression testing. This document is used to support planning and
execution of test cases.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Engineering Cycle: Launch minus
237 days (L-237). Flight Cycle: Launch minus 105 days (L-105).

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Once each Operational Increment
(OI) and updated for each flight or as required

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.2

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

13.1 [SCOPE]{.underline}: This document establishes specific content for
Shuttle Avionics Integration Laboratory (SAIL) test cases or alternate
evaluation methods to be applied in verifying integrated hardware and
software changes to the Space Shuttle.

13.2 [APPLICABLE DOCUMENTS]{.underline}: OI content listings for Primary
Avionics Software System (PASS) and BUS; Software Change Requests
(CR\'s) and Discrepancy Reports (DR\'s); Developmental Test Objectives
(DTO\'s) and unique mission configuration or operational changes; SAIL
modifications and math model changes. Data will be available in
databases, MICB minutes, Program Requirements Change Board (PRCB)
minutes, or in SAIL.

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The document shall identify
all SAIL verification test cases to be performed. Supporting rationale
is provided, including cross-reference to applicable CR\'s, DR\'s,
DTO\'s, General Purpose Computer Memory Patches (GMEM\'s), flight
hardware changes, site modifications, or regression objects. Alternative
verification methodologies are identified where applicable, and
responsible organizations and individuals are identified for each test
case.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor format is
acceptable.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.2-f

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Avionics Anomaly Reporting and Resolution

7\. [DESCRIPTION/USE]{.smallcaps}: To report and coordinate resolution
of anomalies observed during Shuttle Avionics Integration Laboratory
(SAIL) testing.

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

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As Required

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.2

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

13.1 [SCOPE]{.underline}: This documentation encompasses flight hardware
and software discrepancy and interim discrepancy reports, including
information necessary to resolve and disposition the anomalies.

13.2 [APPLICABLE DOCUMENTS]{.underline}: SAIL anomaly logs, status
reports, and verification test data

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The documentation shall
include anomaly logs and status reports, preliminary resolution analysis
findings, and anomaly closure actions.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor format is
acceptable.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.2-g

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Integrated Avionics Verification Test and
Analysis Report

7\. [DESCRIPTION/USE]{.smallcaps}: To document the test results for all
verification, site acceptance, and regression testing.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Engineering cycle reports will be
submitted 90 days following completion of flight cycle testing for the
1st flight of a new OI. Flight cycle reports will be submitted prior to
Launch minus 4 days (L-4).

10\. [SUBMISSION FREQUENCY]{.smallcaps}: One after each set of
Operational Increment (OI) tests and one after each set of flight tests

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.2

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

13.1 [SCOPE]{.underline}: These reports shall present test results,
analysis results, and conclusions for all test cases or alternate
analysis methods used for verification, site acceptance, or regression
testing.

13.2 [APPLICABLE DOCUMENTS]{.underline}: Shuttle Avionics Integration
Laboratory (SAIL) IDR log, SAIL verification test data.

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The reports shall summarize
test and analysis results by flight phase. Each phase includes a
detailed description of the results and conclusions for each test or
analysis performed. Sufficient data should be presented to verify that
the verification objectives have been met.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.2-h

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Integrated Avionics Verification Readiness

7\. [DESCRIPTION/USE]{.smallcaps}: To provide a summary of the
verification status at the Software Readiness Review (SRR).

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Launch minus 28 days (L-28)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Each flight

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.2

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

13.1 [SCOPE]{.underline}: This report presents a status of the
verification objectives for a given mission.

13.2 [APPLICABLE DOCUMENTS]{.underline}: Shuttle Avionics Integration
Laboratory (SAIL) IDR log, SAIL verification test data, Software
Production Facility (SPF) data

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The report summarizes the
status of each verification test case, identifies all known issues
resulting from the test, and presents a plan of resolution for
outstanding issues to be resolved prior to flight.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor format is
acceptable.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.3-c

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Prioritization Recommendation for New
Operational Increment (OI) Build

7\. [DESCRIPTION/USE]{.smallcaps}: Recommendation is used by NASA in
final determination of the OI content. The input is also used in
development of the Shuttle Avionics Software Control Board (SASCB)
Three-Year Plan presented to the Program Requirements Control Board
(PRCB).

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with planned submittal annually.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.3

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

13.1 [SCOPE]{.underline}: The Recommendation considers program goals and
directives to ensure long range flight software planning is in support
of program plans and goals.

13.2 [APPLICABLE DOCUMENTS]{.underline}: SASCB Three-Year Plan;
applicable PRCB directives

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Recommendation includes
individual flight software change proposals (FCP\'s), software change
requests (SCR\'s), SCR corrections for software discrepancies (DR\'s),
and priority rationale for each change, including recommendation for
applicability to Primary Avionics Software System (PASS) and/or Backup
Flight System (BFS).

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.3-e

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Flight Cycle Initialization Load (I-Load)
Verification Report

7\. [DESCRIPTION/USE]{.smallcaps}: To ensure I-Load values in the Flight
Software (FSW) are compatible with specific mission objectives and
program constraints.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with planned submittal within five
weeks following baseline of I-Loads at the Shuttle Avionics Software
Control Board (SASCB). Launch minus 81 days (L-081).

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.3

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

13.1 [SCOPE]{.underline}: The audit addresses flight cycle I-Load values
for each shuttle mission. A full audit of all I-Loads is performed on
the first flight of a new Operational Increment (OI). A delta audit is
performed on subsequent flight within an OI for which FSW patches were
required.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

SCR 89054 *SASCB Process Documentation: I-Load Data Change Request
(DCR)*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The report contains the
approval of each I-Load owner involved in the audit and identifies any
discrepancies found between the SASCB-baselined I-Load values and the
as-built IDS to be applied to the Flight Cycle Mass Memory Unit (MMU).

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.3-f

3\. [DATA TYPE]{.smallcaps}: 4 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Level 6/7/8 Flight Software Test Plan
Recommendation

7\. [DESCRIPTION/USE]{.smallcaps}: Used to enhance Level 6/7/8 Test Plan
content, and incorporate verification objectives that can be satisfied
using Software Production Facility (SPF) test cases.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As required

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.3

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

13.1 [SCOPE]{.underline}: The Recommendation encompasses all SPF Level
6/7/8 testing performed for a new Operation Increment (OI).

13.2 [APPLICABLE DOCUMENTS]{.underline}: Preliminary SPF Level 6/7/8
Test Plan

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Recommendations are by test
case and include adjustments to simulation conditions or scenarios.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.3-g

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Initialization Load (I-Load) Selection and
Comparison Report

7\. [DESCRIPTION/USE]{.smallcaps}: The I-Load selection and comparison
report identifies any differences in selection between I-Load owners and
initiates the resolution process. Resolution of differences is made
prior to Shuttle Avionics Software Control Board (SASCB) I-Load
approval.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with planned submittal within one
week of the I-Load Mission Definition Data Change Request (DCR)
submittal.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.3

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

13.1 [SCOPE]{.underline}: I-Load selection comparison is performed on
the first engineering cycle of an OI and also for each flight cycle.

13.2 [APPLICABLE DOCUMENTS]{.underline}: I-Load selections for the
Mission Definition DCR

SCR 89054 *SASCB Process Documentation: I-Load Data Change Request
(DCR)*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Comparison includes callout
of all miscompares between independent I-Load selections for each
category.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.3-o

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Program Requirements
Documents (PRD\'s)

7\. [DESCRIPTION/USE]{.smallcaps}: To establish the software
requirements for the BFS.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with planned complete release
approximately 12 weeks following Operational Increment (OI) content
baseline by the Shuttle Avionics Software Control Board (SASCB).

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.3

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

13.1 [SCOPE]{.underline}: The documents cover the software requirements
for the BFS program.

13.2 [APPLICABLE DOCUMENTS]{.underline}: The Government shall furnish
the latest update of the software change request (SCR) implementation
baseline.

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The documents contain the
following:

> a\. Functional description.
>
> b\. Operational flight program requirements:
>
> 1\. BFS overview.
>
> 2\. Backup System Services (BSS).
>
> 3\. Guidance, Navigation, and Control (GN&C).
>
> 4\. GN&C flight control.
>
> 5\. GN&C hardware interface programs.
>
> 6\. System Management/Special Processes (SM/SP), Payloads (PL).
>
> 7\. Sequencing (SEQ).
>
> c\. Glossary.
>
> d\. Appendices.
>
> e\. Engineering Orders (EO\'s)

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Revisions are to be in
accordance with contractor\'s engineering release and change control
system.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.3-p**

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

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

6\. **[TITLE]{.smallcaps}**: Primary Avionics Software System
(PASS)/Backup Flight System (BFS) Interface Control Documents (ICD\'s)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To establish the specific
technical requirements of the functional interface between the PASS and
the BFS, Display Electronics Unit (DEU) with the General Purpose
Computer (GPC), and the interface between the Contractor-developed GPC
Initial Program Load (IPL) software and any data systems produced by
contract agencies.

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

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

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

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

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

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

13.1 **[SCOPE]{.underline}**: These documents cover the technical
requirements of the interfaces in the following areas:

a\. Functional interface between the PASS and the BFS.

b\. Interface between the DEU and the GPC.

c\. Interface between the General Purpose Computer Initial Program Load
(GPCIPL) software and data systems or portions produced by contracted
agencies. The contracted agency developed systems include:

1\. The IPL Bootstrap Loader - PASS.

2\. Pass System Software Loader (SSL) - PASS.

3\. BFS Backup System Loader (BSL) - BFS.

4\. Mass Memory Build System.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: The Government shall
furnish the latest update of the Software Change Request (SCR)
implementation baseline CR or applicable report.

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: These documents shall
contain the following, as applicable:

a\. Functional overviews.

b\. General requirements.

c\. Interfaces.

d\. Software loading requirements.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.3-q

3\. [DATA TYPE]{.smallcaps}:3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Functional Subsystem Software Requirements
(FSSR\'s) Documents

7\. [DESCRIPTION/USE]{.smallcaps}: To define flight software
requirements for development team use.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted in
accordance with the System Requirements and Verification Schedule, or as
otherwise authorized by the Contracting Officer\'s Technical
Representative (COTR), or designated representative, with planned
release approximately 12 weeks following Operational Increment (OI)
content baseline by the Shuttle Avionics Software Control Board (SASCB).

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.3

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

13.1 [SCOPE]{.underline}: These documents are applicable to Primary
Avionics Software System (PASS) Flight Software (FSW) requirements and
Cathode Ray Tube (CRT) display requirements for both PASS and Backup
Flight System (BFS).

13.2 [APPLICABLE DOCUMENTS]{.underline}: Software Change Requests
(CR\'s) constituting OI baseline.

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The documents contain the
following:

> a\. Overview.
>
> b\. Detailed requirements:
>
> 1\. GN&C, Part A, Entry Through Landing Guidance.
>
> 2\. GN&C, Part A, Guidance Ascent/RTLS.
>
> 3\. GN&C, Part A, Guidance On-Orbit/De-Orbit.
>
> 4\. GN&C, Part B, Entry Through Landing Navigation.
>
> 5\. GN&C, Part B, Navigation Ascent/Return to Launch Site (RTLS).
>
> 6\. GN&C, Part B, On-Orbit Navigation.
>
> 7\. GN&C, Part C, Flight Control Entry - GRTLS.
>
> 8\. GN&C, Part C, Flight Control, Volume 1, Ascent Flight Phase;
> Volume 2, Ascent.
>
> 9\. GN&C, Part C, Flight Control Orbit DAP.
>
> 10\. GN&C, Part D, Redundancy Management.
>
> 11\. and 12. Not applicable.
>
> 13\. GN&C, Part E, Inertial Measurement Unit Subsystem Operating
> Program.
>
> 14\. GN&C, Part E, Volume 1, Navigation Aids Subsystem Operating
> Program; Volume 2, Star Tracker Subsystem Operating Program.
>
> 15\. GN&C, Part E, Subsystem Operating Programs, Flight Cycle (FC)
> Sensor/Controller.
>
> 16\. GN&C, Part E, Subsystem Operating Programs, FC Effector.
>
> 17\. Remote Manipulator System.
>
> 18\. and 19. Not applicable.
>
> 20\. Volume 1, Displays and Controls; Volume 2, Systems Management;
> Volume 3, Appendices A, B, and F.
>
> 21\. through 25. Not applicable.
>
> 26\. GN&C, Sequencing.
>
> c\. Supplemental Material.
>
> d\. Appendices.

DRD CONTINUATION SHEET

[TITLE]{.smallcaps}: Functional Subsystem Software Requirements [DRD
NO.]{.smallcaps}: 1.4.3.3-q

(FSSR\'s) Documents

[DATA TYPE]{.smallcaps}:3 [PAGE]{.smallcaps}: 2/2

[13. DATA PREPARATION INFORMATION (CONTINUED):]{.smallcaps}

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

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

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.3-s

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Initialization Load (I-Load) Selection Criteria
Databook

7\. [DESCRIPTION/USE]{.smallcaps}: To establish contractor\'s selection
criteria for I-Load usage within a given Operational Increment (OI).

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with planned submittal once per
OI.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.3

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

13.1 [SCOPE]{.underline}: The document encompasses all GN&C and
Sequencing I-Loads.

13.2 [APPLICABLE DOCUMENTS]{.underline}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Databook shall contain
I-Load categories and occurrences with historical information, rationale
for selection, and interrelationships between I-Loads and categories.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.3-t**

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

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

6\. **[TITLE]{.smallcaps}**: Parameter Database

7\. **[DESCRIPTION/USE]{.smallcaps}**: To maintain consistency between
flight data parameters.

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

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: As requested

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

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

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

13.1 **[SCOPE]{.underline}**: The database includes all flight software
parameters and measurements.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: Shuttle Avionics Software
Control Board (SASCB) approved changes which affect data or measurement
characteristics

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The database includes
input/output parameters by principal function, with data type,
frequency, precision, and parameter title.

13.4 **[[FORMAT]{.underline}:]{.smallcaps}** Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by SASCB approval of Change Requests (CR\'s)
changing parameters.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.3-u**

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

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

6\. **[TITLE]{.smallcaps}**: Flight Software Logic Documentation

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document, in flowchart form,
the logic design of the Primary Avionics Software System (PASS) and
Backup Flight System (BFS) GN&C Sequencing and Redundancy Management
(RM) Flight Software (FSW).

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

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Products shall be submitted
as authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with planned submittal for each
FSW Operational Increment (OI) baseline release.

11\. **[REMARKS]{.smallcaps}**: Reference is made to contract
NAS9-19000/IRD SE-1616T9.

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

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

13.1 **[SCOPE]{.underline}**: The document shall provide a detailed
description, in logic flowchart form, of the PASS and BFS GN&C
Sequencing and RM FSW. Logic flowcharts depicting the FSW design for
each release will be provided.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: Initial copy of electronic
files of the three documents reflecting current configuration.

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

a\. PASS GN&C Sequencing:

1\. Section 1: Introduction.

2\. Section 2: Summary.

3\. Section 3: Sequencing principle.

4\. Section 4: Change history.

b\. BFS GN&C Sequencing:

1\. Section 1: Introduction.

2\. Section 2: Summary.

3\. Section 3: BFS sequencing functions.

4\. Section 4: Backup event controller.

5\. Section 5: Change history.

c\. RM FSW:

1\. Section 1: Introduction.

2\. Section 2: Summary/overviews.

3\. Section 3: Detailed sequencing principle functions.

4\. Section 4: Change history.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.3-v**

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

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

6\. **[TITLE]{.smallcaps}**: Payload and Command and Data Annex-4

7\. **[DESCRIPTION/USE]{.smallcaps}**: This document defines and
documents the Shuttle payload command and data software requirements for
use by Mission Operations Directorate, the payload customer, and the
flight software community to develop and verify flight software.

8\. **[DISTRIBUTION]{.smallcaps}**: Per contracting officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Per mission template

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Once per payload per
flight: (pre-CIR baseline-L-360 days, engineering cycle update-L-245
days, and flight cycle update-L-140 days)

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

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

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

13.1 **[SCOPE]{.underline}**: This document defines the shuttle payload
command and data software requirements provided by the payload customer
and JSC payload operations personnel. These requirements shall be
provided in accordance with NSTS-21000-A04-Standard Integration Plan
(SIP) Annex-4 Command and Data Requirements.

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

Standard Integration Plan (SIP) Annex-No. 4 Command and Data
Requirements,

NSTS 21000-A04

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: This document shall
contain the nineteen command and data annex tables as reflected in
section 2.0 of appendix F of NSTS-21000-A04 Standard Integration Plan
(SIP)

Annex-4 Command and Data Requirements.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: To be prepared in
accordance with NSTS-21000-A04, \"SIP Annex No. 4 Command and Data
Requirements.\"

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes will be
updated as required by page change notice (PCN\'s) or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.3-w

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

5\. PAGE: 1/1

6\. TITLE: Space Shuttle Computer Program Development Specifications
(Six Volumes)

7\. DESCRIPTION/USE: Primary Avionics Software System (PASS) flight
software Level A (System)and Level B (Functional) requirements.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission

schedule.

10\. SUBMISSION FREQUENCY: Once per Operational Increment(OI) of the
flight software to be published by FACI with subsequent updates as
required to maintain a document with current requirements.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.3

13\. DATA PREPARATION INFORMATION: Delivery may be by publication of the
complete document or Page Change Notice (PCN) depending on the magnitude
of the changes.

13.1 [SCOPE]{.underline}: Defines the PASS Level A( System)and Level
B(Functional) software requirements for the Orbiter General Purpose
Computers.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS:]{.underline} Contains the PASS flight software
requirements for the System Software- Operating System and User
Interface, Downlist/Uplink, Launch Data Bus and the functional level
requirements for the applications - Guidance Navigation and Control
(GN&C), Systems Management (SM), and Vehicle Utility (VU) as defined in
the following documents:

SS-P-0002-140 SS Downlist/Uplink Software Requirements

SS-P-0002-150 SS LDB Software Interface Requirements

SS-P-0002-170 SS System Level A Software Requirements

SS-P-0002-510 SS Functional Level Requirements, GN&C

SS-P-0002-550 SS Functional Level Requirements, Vehicle Utility

SS-P-0002-580 SS Functional Level Requirements, Systems Management

Each document contains the requirements in the Change Requests (CR's)
approved by the Shuttle Avionics Change Control Board (SASCB).

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE:]{.underline} Changes shall be incorporated as
required by PCN's or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.3 -x

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

5\. PAGE: 1/1

6\. TITLE: Engineering DCE Support for SASCB Change Reviews

7.  DESCRIPTION/USE: Defines the products delivered in support of
    Engineering review of Out of Family and New Development DCRs and
    I-Loads.

8\. DISTRIBUTION:

9\. INITIAL SUBMISSION: 30 days after contract start

10\. SUBMISSION FREQUENCY: Weekly in support of the Engineering Change
Review Board

11\. REMARKS:

12\. INTERRELATIONSHIP: SASCB Agenda and SASCB DCR and I-Loads DCR
Agendas

13\. DATA PREPARATION INFORMATION

13.1 [SCOPE]{.underline}: These products are required for the operation
of the Engineering DCE review process and Engineering Change Review
Board.

13.2 [APPLICABLE DOCUMENTS]{.underline}: Star and MAST Users Guides,
I-Loads Definition Handbook

13.3 [CONTENTS:]{.underline}

a.  DCR Analysis Reports - Definition and entry of Star and Mast DCR
    reports for vehicle data and transmittal to JSC those designated as
    requiring Engineering DCE review

b.  I-Loads Definitions/Review - Definition and entry of I-Loads DCRs
    into STAR as required for Engineering I-Load owners and transmittal
    to JSC of each I-Load DCR designated as requiring Engineering DCE
    review.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. DR[D
NO.]{.smallcaps}: 1.4.3.3-y

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Develop/Evaluate Flight Software (FSW) Change
Documents

7\. [DESCRIPTION/USE]{.smallcaps}: To request a change or document a
discrepancy in the Flight Software or associated software development
tools.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As required.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.3

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

13.1 [SCOPE]{.underline}: Flight Software change documents are used to
request a change to the Primary Avionics Software System (PASS), Backup
Flight System (BFS) Software, main engine controller software, Flight
Software development tools, or the Flight Software Initialization
I-loads. The Discrepancy Report is used to document discrepancies found
in delivered software or associated tools.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

SASCB Three-Year Plan

Program Requirements Control Board (PRCB) Directives

Mission manifests

Flight Production Schedules Working Group (FPSWG) directives

Software Change Requests (SCRs)

Shuttle Avionics Integration Laboratory (SAIL) Interim Discrepancy
Reports (IDRs)

Computer Program Development Specification (CPDS)

Functional Subsystem Software Requirements (FSSR)

BFS Program Requirements Document (PRD)

PASS/BFS Interface Control Document (ICD)

SCR 89050 SASCB Process Documentation Overview

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The following FSW change
documents are included:

a\. Flight Software Change Proposal (FCP)

b\. Software Change Request (SCR)

c\. Discrepancy Report/Requirements Issue Tracking (DR/RIT)

d\. I-Load Data Change Request (DCR)

e\. Software Authorization Notice (SAN)

f\. Requirement Change Notice (RCN)

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

[[13.5 MAINTENANCE]{.underline}]{.smallcaps}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.3-z

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

5\. PAGE: 1/1

6.  TITLE: Multifunction Electronic Display Subsystem (MEDS) System
    Segment Specification (SSS)

7\. DESCRIPTION/USE: To define the system architectural design,
performance, development-implementation, and test requirements for the
MEDS.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted in accordance
with the requirements and verification schedule, or as authorized by the
Contracting Officer's Technical Representative (COTR), or designated
representative. Planned submittals should be scheduled approximately 14
days prior to the SAR.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} This document defines the system architectural
design, performance, development-implementation, and test requirements
for the MEDS.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS:]{.underline} This document shall contain:

1.  Introduction

2.  Applicable Documents

3.  Requirements

4.  Quality Assurance Provisions

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

[13.5 MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.3-aa

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

5\. PAGE: 1/1

6.  TITLE: Multifunction Electronic Display Subsystem (MEDS) Principles
    Of Operation (POO)

7\. DESCRIPTION/USE: To define the principles of operation of the MEDS.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} This document defines the principles of
operation of the MEDS hardware and software.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS:]{.underline} This document shall contain:

1.  MEDS System Overview

2.  IDP Hardware Description

3.  IDP Software Description

4.  ADC Description

5.  MDU Hardware Description

6.  MDU Software Description

7.  MEDS Error Handling Description

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.4-d

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Reconfiguration
Deliverables

7\. [DESCRIPTION/USE]{.smallcaps}: The BFS Flight Software (FSW)
deliverables and supporting documentation are provided to the FSW
community in support of Shuttle missions.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As required to support
reconfiguration concurrent with delivery of each Software End Item
designed as a Configuration Item (CI).

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.4

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

13.1 [SCOPE]{.underline}: Deliverables include the BFS FSW datasets, FSW
tapes, optical disk or applicable device, and applicable documentation.

13.2 [APPLICABLE DOCUMENTS]{.underline}

JSC 08338 *Shuttle Avionics Mass Memory Unit Computer Program
Integration Plan (MIP)*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Release of BFS flight
software includes products specified in the Shuttle Avionics Mass Memory
Unit Computer Program Integration Plan (MIP), JSC 08338.

[13.4 [FORMAT]{.underline}]{.smallcaps}: Products will be generated in
the formats described in the MIP, JSC 08338. MIP contents are under
configuration control by the SASCB.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: In the event that changes
are required to the previously deliverable software items, the products
will be revised and redelivered with the appropriate documentation.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.5-a

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Software
Configuration Inspection Report/Briefing

7\. [DESCRIPTION/USE]{.smallcaps}: This report/briefing presents to NASA
the delivery of the Operational Increment (OI) software milestone. It
officially documents the completion of the development and verification
of the BFS software to assure the customer that the software was
developed per the requirements and is ready to support Shuttle missions.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative (COTR)
or designated representative, with planned submittal at Configuration
Inspection (CI) which is negotiated at the Shuttle Avionics Software
Control Board (SASCB).

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.5

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

13.1 [SCOPE]{.underline}: The Backup Flight System (BFS) Software
Configuration Inspection Report/Briefing describes the development
process, the verification process and results, and configuration control
performed in support of a new FSW OI.

13.2 [APPLICABLE DOCUMENTS]{.underline}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: This report/briefing shall
contain a summary of both Flight Software and Flight Software
Application Tools and status of all software changes, Discrepancy
Reports, waivers and user notes, verification testing and certification
related to a specific OI system. It will include a summary of processes
leading to CI and will identify any open work post CI. At a minimum the
report/briefing shall include:

> a\. An overview of the OI history and new major capabilities.
>
> b\. Identification of each CR/SSCR and DR/SSDR change applied to the
> OI.
>
> c\. Summary of all FSW and FSWAT Ops Notes, User Notes, and Waivers
> deleted and still applicable to this OI.
>
> d\. Summary of all verification and performance testing for this OI
> and test mapping to CR\'s and DR\'s.
>
> e\. Status of all open DR\'s applicable to this OI.
>
> f\. Summary of open items.
>
> g\. Summary and status of quality metrics historically and for this
> OI.
>
> h\. Briefing Package.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.5-b**

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

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

6\. **[TITLE]{.smallcaps}**: Backup Flight System (BFS) Software
Standards and Procedures Manual (SSPM)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document BFS tasks and duties,
including work procedures, checklists, and general information for all
functional areas of the BFS project.

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

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: The SSPM will be released
once a year in February. Procedure Change Notices (PCN\'s) will be
released on a monthly basis as deemed necessary. Full revisions as
required.

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

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

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

13.1 **[SCOPE]{.underline}**: The SSPM contains standards and procedures
used during the development of all Computer Software Configuration Items
(CSCI\'s) developed by the Software Engineering department.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The Software Standards
and Procedures Manual contains work procedures, checklists, forms, and
general information used to develop CSCI\'s for the following:

a\. Backup Flight System (BFS).

b\. General Purpose Computer Initial Program Load (GPCIPL).

c\. Backup System Loader (BSL).

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by PCN\'s or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.5-c**

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

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

6\. **[TITLE]{.smallcaps}**: Backup Flight System (BFS) Change Request
(CR) Risk Assessment Analysis/Report

7\. **[DESCRIPTION/USE]{.smallcaps}**: To assess the risk of changing
the existing code to implement the requested change.

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

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: As required to support
Software Change Requests (SCR\'s) for all code changes

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

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

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

13.1 **[SCOPE]{.underline}**: This report evaluates the risk of
implementing the change in terms of size, complexity, criticality, and
manpower utilized.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The report shall contain:

a\. Summary of benefits.

b\. Estimated size of change.

c\. Complexity.

d\. Criticality.

e\. Code paths.

f\. Failures.

g\. Operational phases.

h\. New or existing code.

i\. Area of code last changed.

j\. Manpower impact.

k\. Other comments.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.5-d**

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

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

6\. **[TITLE]{.smallcaps}**: Backup System Loader (BSL) Computer Program
Description Document

7\. **[DESCRIPTION/USE]{.smallcaps}**: To support software maintenance
of the BSL, under configuration control.

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

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

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

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

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

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

13.1 **[SCOPE]{.underline}**: This document defines the requirements and
functions of the BSL. This software is transferred from the Mass Memory
Unit (MMU) to the General Purpose Computer (GPC) \[by the GPC Initial
Program Load (GPCIPL) program\] when the Backup Flight System (BFS)
Program Load function is initiated by the crew during GPCIPL. The BSL
shall (1) manage the resources of the GPC communicating with the MMU;
(2) communicate with the Display Electronic Unit (DEU); (3) load the
BFS; (4) pass control to the BFS after BFS is loaded upon user request,
and (5) enunciate all detected errors.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The BSL Computer Program
Description Document shall contain:

a\. Scope: describes the usage and provides a functional summary of the
BSL computer program.

b\. Applicable documents: covers both Government and non-Government
documents.

c\. Requirements: defines computer program, interface requirements, part
numbers and labeling, and tape delivery format.

d\. Detailed functional requirements: covers real-time processor,
real-time control, GPC initialization, BSL interrupt handling/error
logging, DEU interface, DEU poll, DEU poll response, DEU update, mass
memory interface, GPCIPL interface, BFS interface, and BFS MMU build
system interface.

e\. Quality assurance: includes provisions for quality assurance
(verification and validation).

f\. Deliverables: covers provision for delivery (including deliverables
definition).

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.5-e**

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

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

6\. **[TITLE]{.smallcaps}**: General Purpose Computer Initial Program
Load (GPCIPL) Program Requirements Document

7\. **[DESCRIPTION/USE]{.smallcaps}**: To establish the requirements for
performance, design, and verification of the GPCIPL programs.

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

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

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

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

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

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

13.1 **[SCOPE]{.underline}**: This document establishes the requirements
for design and development of the GPCIPL program. The GPCIPL is used to
determine the operational readiness of the General Purpose Computer
(GPC), to initiate the loading of Flight System Software and to control
and monitor memory purge operations. The Flight System Software consists
of either the Primary Avionics Software System (PASS) or Backup Flight
System (BFS) software.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The GPCIPL Program
Requirements Document shall contain (as applicable):

a\. Architecture:

1\. Input/Output (I/O) interfaces.

2\. Data pools.

3\. Flow charts.

b\. Program:

1\. Functional overview.

2\. Program structure requirements.

3\. Initialization requirements.

4\. Tables of hardware elements and instructions.

5\. Functional diagrams.

c\. Engineering Orders (EO\'s)

13.4 FORMAT: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required in accordance with contractor\'s engineering
release and change control system.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.5-g

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Operational
Increment (OI) Deliverables

7\. [DESCRIPTION/USE]{.smallcaps}: The BFS OI products will be delivered
for use by the reconfiguration organization for production of training
and flight loads in support of Shuttle missions.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.5

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

13.1 [SCOPE]{.underline}: The BFS OI Deliverables consist of the FSW and
FSW Applications Tools software and products required for execution of
the flight to flight reconfiguration processes.

13.2 [APPLICABLE DOCUMENTS]{.underline}

JSC 22320 *Class 1 Integration Plan (CIP)*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Includes all deliverable
products specified in the FSW Class 1 Integration Plan (CIP), JSC 22320,
as deliverables for each OI.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Products will be generated in
Software Development Facility (SDF) datasets per the formats described
in the CIP. The CIP contents are under configuration control by the
SASCB.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: In the event that changes
to the previously delivered software items are required, the products
will be revised and redelivered with the appropriate documentation.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.5-h

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) High-order Assembly
Language/Shuttle (HAL/S) Compiler Audit Reports

7\. [DESCRIPTION/USE]{.smallcaps}: To provide analysis of audit results
on the BFS Flight Software for problems found in the HAL/S compiler.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.5

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

13.1 [SCOPE]{.underline}: The BFS HAL/S Compiler Audit Reports document
audit criteria (if applicable), audit results, and analysis of audit
results performed on the BFS Flight Software per Compiler Change
Requests and Compiler Discrepancy Reports.

13.2 [APPLICABLE DOCUMENTS]{.underline}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Compiler Audit Form shall
contain:

a\. Document number.

b\. Audit date.

c\. Compiler version.

d\. BFS Flight Software version and Operational Increment (OI) number.

e\. Document title.

f\. Audit criteria.

g\. Audit results/analysis.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.5-i

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

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

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Discrepancy Report
(DR) Analysis

7\. [DESCRIPTION/USE]{.smallcaps}: Detailed DR analysis and recommended
disposition for DR\'s written against the BFS Flight software are
documented on a BFS DR Analysis Form. A summary of the technical
analyses and recommended closure disposition with supporting rational is
documented on a FSW DR Management Form. Both of these are provided to
NASA for review and concurrence/approval.

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

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As required for each DR.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.5

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

13.1 [SCOPE]{.underline}: The BFS Discrepancy Report Analysis and DR
Management Form documents the evaluation of a problem or anomaly and
recommended disposition.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

SCR 89052 *Space Shuttle Flight Software Discrepancy Report Procedures*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Contents of the DR Management
Form are defined in SCR 89052, Space Shuttle Flight Software Discrepancy
Report Procedures. The DR Analysis Form shall contain:

a\. Title/DR number.

b\. Description of problem.

c\. How user sees effects.

d\. Requirement violated/inadequacy.

e\. Testing required.

f\. Rationale for disposition.

g\. Process Improvement.

h\. Analysis.

i\. Workaround/recovery procedure.

j\. Functional area.

k\. Implementation impact.

l\. Additional information.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.5-j**

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

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

6\. **[TITLE]{.smallcaps}**: Backup System Loader (BSL) Program
Requirements Document

7\. **[DESCRIPTION/USE]{.smallcaps}**: To establish the requirements for
performance, design, and verification of the BSL.

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

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

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

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

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

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

13.1 **[SCOPE]{.underline}**: The BSL Program Requirements Document
describes the functions and organization of the BSL program including
interrupt handling, executive, Display Electronic Unit (DEU) interface,
and Mass Memory Unit (MMU) interface.

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

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The document shall
contain the following, as applicable:

a\. Architecture:

1\. Input/Output (I/O) interfaces.

2\. Data pools.

3\. Flow charts.

b\. Program descriptions:

1\. Functional overview.

2\. Program structure.

3\. Initialization.

4\. Tables.

5\. Flow charts.

c\. Engineering Orders (EO\'s)

The following sections will be included in the document:

a\. Scope: covers identification and tape delivery format.

b\. Applicable documents: includes Government and non-Government
documents.

c\. Requirements: includes General Purpose Computer (GPC) architecture,
GPC interrupt structure, GPC I/O structures (the Ignition Over Pressure
(IOP)), BSL overview, overview summary, and IPL MENU selection and
usage.

d\. Functional description: describes real-time processor, interrupt
handlers, real-time executive, DEU interface, CIM 4 POLL, DEU POLL
response analysis (POLLPSP), CM 4 HEX, CIM4DEC, DEU update processing
(CIM4UPDT), IOP interface master sequence controller programs, data bus
control (CBCBTL), IOP Control (MSCINTF), mass memory (MM) I/O handlers,
backup system loader foreground processor (BSL2F), backup system loader
background processor (BSL2B), backup flight system control transfer
processor (MOVEPSA), GPC Initial Program Load (GPCIPL) interface, and
MMU build system interface.

e\. BSL error/advisory message.

**DRD Continuation Sheet**

**[TITLE]{.smallcaps}**: Backup System Loader (BSL) Program **[DRD
NO.]{.smallcaps}**: **1.4.3.5-j**

Requirements Document

**[DATA TYPE]{.smallcaps}**: 3 **[PAGE]{.smallcaps}**: 2/2

[13. **DATA PREPARATION INFORMATION (CONTINUED)**:]{.smallcaps}

13.4 **FORMAT**: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

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

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.5-k**

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

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

6\. **[TITLE]{.smallcaps}**: General Purpose Computer Initial Program
Load (GPCIPL) User\'s Guide

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide utilization
information relative to the GPCIPL operations and capabilities.

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

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

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

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.3.5

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The GPCIPL User\'s Guide provides an
overview of software capabilities including descriptions of the GPCIPL
services, operating system, and control operations. Also included is
information relative to the orbiter\'s cabin controls (switches, etc.)
as they affect operations of the GPCIPL.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The document shall
contain the following:

a\. GPCIPL overview.

b\. GPCIPL capabilities overview.

c\. Displays description including hardware/software interfaces.

d\. Switches description.

e\. Fault annunciation and messages description.

f\. Downlist description.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.5-l**

3\. **[DATA TYPE]{.smallcaps}**:3 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: General Purpose Computer Initial Program
Load (GPCIPL) Computer Program Description Document

7\. **[DESCRIPTION/USE]{.smallcaps}**: To support software maintenance
of the GPCIPL program under configuration control.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: As required

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.3.5

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The GPCIPL Computer Program Description
Document defines the requirements and functions of the GPCIPL. This
software is transferred from the Mass Memory Unit (MMU) to the General
Purpose Computer (GPC) by the Bootstrap Loader when IPL is initiated by
the crew during GPCIPL. The GPCIPL shall (1) manage the resources of the
GPC communicating with the MMU; (2) communicate with the Display
Electronic Unit (DEU); (3) load the Backup Flight System (BFS); (4) pass
control to the Back Focal Length (BFL) after the BFL is load at user
request; and (5) enunciate all detected errors.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The document shall
contain the following:

a\. Scope: describes the usage and provides a functional summary of the
GPCIPL computer program.

b\. Applicable documents: covers both Government and non-Government
documents.

c\. Requirements: defines computer program, interface requirements, part
numbers and labeling, and tape delivery format.

d\. Detailed functional requirements: covers real-time processor,
real-time control, GPC initialization, GPCIPL interrupt handling/error
logging, DEU interface, DEU poll, DEU poll response, DEU update, mass
memory interface, Backup System Loader (BSL) interface, Primary Flight
System (PFS) interface, and BFS MMU build system interface.

e\. Quality assurance: includes provisions for quality assurance
(verification and validation).

f\. Deliverables: covers provisions for delivery (including deliverables
definition).

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.5-m**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Backup Flight System (BFS) Program
Description Documents (PDD\'s)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To support software maintenance
of the Backup Flight System under configuration control.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: As required

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.3.5

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The BFS Program Description Documents
provide a description of the program structure and logic flow of the
program code which implements the specific requirements of the Backup
Flight System for each of the following major functional areas:

a\. Guidance, Navigation, and Control (GN&C).

b\. System Management/Special Processes (SM/SP) and Payloads.

c\. Sequencing (SEQ).

d\. Backup System Services (BSS).

e\. Displays and Control (D&C).

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The documents shall
contain the following, as applicable:

a\. Architecture:

1\. Input/Output (I/O) interfaces.

2\. Data pools.

3\. Flow charts.

b\. Program Descriptions:

1\. Functional overview.

2\. Program structure.

3\. Initialization.

4\. Tables.

5\. Flow charts.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.5-n**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Backup Flight System (BFS) Coding Standards
Document

7\. **[DESCRIPTION/USE]{.smallcaps}**: To identify software programming
standards utilized in the development and testing of the BFS.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: As required

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.3.5

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The BFS Coding Standards Document provides
a compilation of both BFS programming and supporting standards that
define the function, implementation, and compliance control of each
standard.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The documents shall
contain categorized standards consisting of the following:

a\. Coding standard identification number: The following categories,
under which the coding standards are placed during the compilation
process, are assigned an upper case letter as follows:

1\. A - standards pertaining to error detection, prevention, and
recovery.

2\. B - standards imposed by the programming language.

3\. C - standards that represent good programming practices.

4\. D - standards imposed by system requirements.

5\. E - standards pertaining to patches.

b\. Coding standard statement: describes the rationale for the
assignment of the coding standard.

c\. Applicable language.

d\. Implementation methods.

e\. Compliance control procedures, as applicable.

f\. Remarks applicable to the standard.

g\. Auditing classifications: assigned to the coding standards as
follows:

1\. Mandatory - must be followed.

2\. Guideline - desirable but not mandatory (improves visibility,
readability, etc.).

3\. Compiler or pilot imposed (e.g., will not compile if violated).

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.5-o**

3\. **[DATA TYPE]{.smallcaps}**:3 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/2

6\. **[TITLE]{.smallcaps}**: Backup Flight System (BFS) User\'s Guide

7\. **[DESCRIPTION/USE]{.smallcaps}**: To be used as a training and
testing aid providing information relative to the Backup Flight
System\'s operation and capabilities.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an ongoing
requirement; no break in existing

submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Products shall be submitted
as authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with the planned submittal prior
to the first flight of the Operational Increment (OI).

11\. **[REMARKS]{.smallcaps}**: Reference is made to contract
NAS9-19000/IRD SE-1616T9.

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.3.5

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The BFS User\'s Guide provides an overview
of software capabilities including descriptions of the backup system
services; backup operation system; guidance, navigation, and control
operations; and those operations classified as systems
management/special processes and sequencing. Also included is
information relative to payload support.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The document shall
contain the following:

a\. Backup Flight System Overview: includes the BFS purpose, PFS/BFS
hardware configuration overview, BFS capabilities, PFS/BFS interface and
interactions, BFS software structure, and BFS functional summary.

b\. Backup Flight System Capabilities Overview: includes the Operational
Sequences (OPS) and Major Modes (MM) description; BFS general
description; mass memory interface; system initialization; and BFS crew
functional and hardware interfaces.

c\. Displays Description including hardware/software interfaces: for
dedicated indicators and controls and Cathode Ray Tube (CRT) displays.

d\. Dedicated Displays Description: addresses the attitude director
indicator, alpha/mach indicator, altitude vertical velocity indicator,
horizontal situation indicator, and surface position indicator.

e\. Data Processing System: provides selected information concerning the
Shuttle Data Processing System (DPS). Emphasis is to be placed on the
various data buses and their operating characteristics.

f\. Caution, Warning, and Alert System Description: the BFS Fault
Detection and Annunciation (FDA) function will primarily support the
backup C&W and SM alert systems. The BFS FDA is to monitor specified
parameters from Guidance, Navigation and Control (GN&C), Backup System
Services (BSS), and System Management/Special Processes and Sequencing
(SM/SP&S).

**DRD Continuation Sheet**

**[TITLE]{.smallcaps}**: Backup Flight System (BFS) User\'s Guide **[DRD
NO.]{.smallcaps}**: **1.4.3.5-o**

**[DATA TYPE]{.smallcaps}**: 3 **[PAGE]{.smallcaps}**: 2/2

[13. **DATA PREPARATION INFORMATION (CONTINUED)**:]{.smallcaps}

g\. Backup Flight System Downlist: the downlist is to be the name of a
major communication link between the Space Shuttle Orbiter and the
ground support equipment. The purpose of the downlist description is to
identify precisely the usage of each 16-bit word in the downlist format.
This will be accomplished with the master measurement database, the
downlist matrices, and the BFS downlist word definitions.

h Payload Overview: includes payload support functions used on Orbiter
flight which require payload support. Consists of payload management,
FDA, scaling, display, and downlist processing.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.5-p

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/2

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Test Coordination
Team (TCT) Test Specifications and Performance Test Review (PTR) (Level
7)

7\. [DESCRIPTION/USE]{.smallcaps}: The BFS TCT test specifications
identify the performance test procedures that will be performed on a
particular Operational Increment (OI) and are used by the FSW technical
community to assure the accuracy of the BFS FSW performance verification
approach. The Level 7 PTR provides the FSW technical community with a
summary of the Level 7 performance testing, identifies variances to the
procedures, and any ongoing work/investigations.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with planned delivery of the TCT
Test Plan no later than four weeks prior to First Article Configuration
Inspection (FACI) in support of the TCT briefing which is held no later
than one week prior to FACI. The PTR briefing is conducted no later than
1.5 weeks prior to CI.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.5

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: The TCT test specifications identify the
performance test procedures and specifications to be exercised for the
OI. The PTR provides the FSW technical community with a summary of the
outcome of performance testing. Both of these are presented to the FSW
technical community in the form of a briefing.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

NSTS 08271 *Flight and Ground Software Verification and Validation
Requirements*

13.3 [[CONTENTS]{.underline}]{.smallcaps}:

a\. Level 7 performance testing is categorized into three areas:
Capability, Stress and Integrity testing. Each Level 7 Test
Specification shall include:

1\. Identification name for the test case.

2\. Title/Description of the test case.

3\. Principal functions tested.

4\. Major Mode being tested.

5\. Test Objectives.

6\. Testing Approach.

DRD CONTINUATION SHEET

[TITLE]{.smallcaps}: Backup Flight System (BFS) Test Coordination Team
[DRD NO.]{.smallcaps}: 1.4.3.5-p

(TCT) Test Specifications and Performance Test Review (PTR) (Level 7)

[DATA TYPE]{.smallcaps}: 3 [PAGE]{.smallcaps}: 2/2

[13. DATA PREPARATION INFORMATION (CONTINUED):]{.smallcaps}

13.3 [[CONTENTS (CONTINUED)]{.underline}:]{.smallcaps}

b\. The PTR shall contain:

1\. Software configuration.

2\. Software versions.

3\. Performance test plan.

4\. Software Change Requests (SCR\'s) tested.

5\. SCR test matrix.

6\. Software patch test configuration.

7\. Flight software anomalies.

8\. Miscellaneous anomalies.

9\. Open items.

10\. Performance test report summaries.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.5-q

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Functional Test
Reports (Level 6)

7\. [DESCRIPTION/USE]{.smallcaps}: Functional Test Reports document the
results of the Level 6 testing. These are provided to, and accepted by,
NASA as a certification that the delivered software conforms to NASA
approved requirements.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with planned delivery no later
than six weeks prior to Configuration Inspection (CI).

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.5

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: The report shall contain the approved changes
that were to be tested, the test procedure, test data, and a statement
by the tester on the success of the test.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

NSTS 08271 *Flight and Ground Software Verification and Validation
Requirements*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Each report shall contain:

a\. Test procedure.

b\. Software Modification Sheet (SMS), Change Request (CR), and/or
Discrepancy Report (DR).

c\. Test on-line output.

d\. Post-processed data.

e\. Test summary sheet.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.5-r

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Performance Test
Reports (Level 7)

7\. [DESCRIPTION/USE]{.smallcaps}: Level 7 test results are provided to,
and reviewed by, the FSW technical community to determine correct
performance of the software prior to CI software acceptance.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with planned delivery no later
than six weeks prior to Configuration Inspection (CI) for new OI
releases and no later than four weeks prior to launch for
flight-specific configured loads other than Complementary Loads, if
required.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.5

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: Each report contains the results of each
performance test as specified in the Test Coordination Team test
specifications (DRD 1.4.3.5-p).

13.2 [APPLICABLE DOCUMENTS]{.underline}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The report shall contain:

a\. Test specification and procedure.

b\. Miscellaneous anomalies.

c\. Test configuration.

d\. Patch summary description.

e\. Summary tables.

f\. Pass/fail performance summary.

g\. Appendices of plotted data.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None required

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.5-s

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Software First
Article Configuration Inspection (FACI) Report/Briefing

7\. [DESCRIPTION/USE]{.smallcaps}: This report/briefing presents to NASA
the status of the OI software development release in preparation for the
start of verification activities and officially reports the
contractor\'s OI development completion of baselined requirements.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule.

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Products shall be submitted as
authorized by the Contracting Officer\'s Technical Representative
(COTR), or designated representative, with planned submittal at FACI
which is negotiated at the Shuttle Avionics Software Control Board
(SASCB).

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.5

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: Covers the results of all Flight Software
development activities and the development testing performed prior to
the release of the OI software for verification.

13.2 [APPLICABLE DOCUMENTS]{.underline}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: This report/briefing shall
contain both Flight Software and Flight Software Application Tools
summary and status of all software changes, Discrepancy Reports, waivers
and user notes, major capability changes, and the Level 6 and 7
verification plans related to a specific OI system. It will include a
summary of processes leading to FACI and will identify any planned post
FACI development work. At a minimum the report shall include:

a\. Schedule.

b\. Baseline/build genesis.

c\. Identification of each CR, DR, SSCR, and SSDR change applied to the
OI system.

d\. Development and development test summary leading up to FACI.

e\. Summary and description of all FSW and FSWAT Waivers and Operations
Notes deleted by this OI and still applicable to this OI.

f\. Open Issues.

g\. Identification of all post FACI open work including opening DR\'s
potentially applicable to the OI.

h\. Summary and status of the quality metrics historically and for this
OI.

i\. Identification of the Level 6 and 7 Verification plans.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.5-u

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Biweekly
Development/Verification Report

7\. [DESCRIPTION/USE]{.smallcaps}: Provides a status of the BFS
development and verification activities for Operational Increments
(OI's) and Reconfiguration loads.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer's letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Report shall be submitted
biweekly, with submission deadline as negotiated with the Contracting
Officer\'s Technical Representative (COTR), or designated
representative, in support of the scheduled BFS Development/Verification
Status Meeting.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.5

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: This report shall include status of both BFS
and General Purpose Computer Initial Program Load/Backup System Loader
(GPCIPL/BSL) effort.

13.2 [APPLICABLE DOCUMENTS]{.underline}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Backup Flight system
(BFS) Biweekly Development/Verification Report shall include at a
minimum the following. Changes to the content can be negotiated with the
Contracting Officer\'s Technical Representative (COTR), or designated
representative.

a\. General Information

1\. HAL/S Compiler Issues

2\. General Operational Increment (OI) Planning

b\. Development/Verification Status for each OI Currently in Development
or Field Use

1\. OI schedule, including Change Request Baseline, build dates, First
Article Configuration Inspection, Level 6 and Level 7 Verification
Complete, Configuration Inspection, Level 7 Reviews, and other relevant
milestones

2\. Development Status, including build contents (CR's and DR's
incorporated) and issues

3\. Integration Testing Status, including schedules and issues

4\. Level 6 Testing Status, including schedules, issues, and a summary
which shows status of all test procedures and test cases

5\. Level 7 Testing Status, including schedules, issues, and a summary
which shows status of all performance test cases

c\. Status of reconfiguration loads

d\. BFS Issues and Concerns

e\. Special Topics

f\. Action Items

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor format is
acceptable.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: No maintenance
requirements.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.4.3.5-v

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Backup Flight System (BFS) Mass Memory
Universal Patch Format (UPF) Patch

7\. [DESCRIPTION/USE]{.smallcaps}: A BFS UPF Patch is used to modify the
BFS Mass Memory without altering the established memory maps.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer's letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Assumption of an ongoing
requirement; no break in existing submission schedule

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As required following approval
by the Shuttle Avionics Software Control Board (SASCB) of the
authorizing Change Request (CR) or Discrepancy Report (DR).

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.4.3.5

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: Provides a means of delivering modifications
to the BFS software to an end user. The development and delivery of the
patch requires a NASA approved Flight Software CR or DR.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

JSC 08338 *Shuttle Avionics Mass Memory Unit Computer Program
Integration Plan (MIP)*

[13.3 [CONTENTS]{.underline}]{.smallcaps}: BFS flight software UPF patch
contents and products are specified in the Shuttle Avionics Mass Memory
Unit Computer Program Integration Plan (MIP), JSC 08338.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Products will be generated in
the formats described in the MIP, JSC 08338. MIP contents are under
configuration control by the SASCB.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: None Required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.7 -a

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Progress Report

7\. DESCRIPTION/USE: To be used for monitoring of the progress,
significant accomplishments, major activities, problems, and corrective
actions.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Progress Report will be submitted monthly on
the 18^th^.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.7, 1.4.3.8, 1.4.3.9, 1.4.3.10, 1.4.3.12

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Covers all work accomplished during each month
of contract performance.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

3.  [CONTENTS]{.underline}: A progress report shall include but not be
    limited to the following.

A quantitative description of overall progress, including:

a.  Identification of current problems which can impede the scheduled
    progress or jeopardize the quality or any technical objectives and
    the proposed or implemented corrective action.

b.  Identification of all deliveries and significant activities for the
    last month including specific statement of the schedule performance
    for each deliverable.

c.  Updated program schedules. With a discussion of the work to be
    performed during the next monthly reporting period.

d.  Topical discussion of significant activities within the categories
    of Flights, Operational Increments, Facility Support, Flight
    Software, Flight Software Application Tools, and General.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.7 -b

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/2

6\. TITLE: Software Management Plan

7\. DESCRIPTION/USE: To describe the software contractor's approach to
managing the development of Orbiter software and to specify internal
procedures and interfacing NASA procedures.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: The Software Management Plan will be released
annually.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.7, 1.4.3.8, 1.4.3.9, 1.4.3.10, 1.4.3.12

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Defines the overall process expected of the
software contractor in support of Space Shuttle Orbiter avionics
software development from initiation through completion of each software
element delivery.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: a. Contractor's approach to accomplishing
the delivery of Shuttle software

in the following areas:

1.  Organization definition, responsibilities, and management controls

2.  Detailed software development process description for Shuttle
    onboard FSW and for ground FSWAT tools

3.  Configuration management description of control processes and
    automated tools

4.  Configuration accounting documents use and handling

5.  Delivery procedures for FSW and FSWAT end items

6.  Deliverable items definition

7.  Reconfiguration activities for flight-to-flight builds

```{=html}
<!-- -->
```
b.  Contractor's detailed verification plan, including specific methods
    to

> accomplish the following:

1.  Independent verification to assure that the software is
    mathematically and logically correct

2.  Show that valid software results exist throughout the expected
    performance range of the established requirements

3.  Plans for verification or reverification following software changes
    during code and test and during formal verification

4.  Traceability to test requirements and repeatability of verification
    test results

5.  Procedures and interfaces associated with ensuring software
    conformance to the appropriately authorized configuration management
    data base

6.  Interfaces with NASA

7.  Adherence to NSTS 08271 verification and validation requirements

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by PCN's or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.7 -c

2\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/2

6\. TITLE: Computer Resource Requirements and Utilization

7\. DESCRIPTION/USE: To provide a basis to plan for computer resources.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement

10\. SUBMISSION FREQUENCY: Products will be produced every 6 months.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.7

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Identifies the SRF & SDF mainframe and network
computer resources required by the contractor and provided by the
Government.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: A computer utilization forecast with
identification of estimated resource use

for the next 24 months and actual usage compared to projected for the
past 12 months.

The contractor shall collect and report to the one month granularity
both computer resource requirements and past actual usage. Each report
shall include a 12 month past history, a next 6 month projection and a
next 2 year projection of needs.

The reported resource needs shall include:

1.  Terminal connect session per week

2.  Short, Medium, and Long Batch jobs per week

3.  Tape mount jobs per week

4.  Short, Medium, and Long IMS jobs per week

5.  Local and Remote print support in thousands of lines per week

6.  DASD storage in megabytes average over the month

7.  Tape volumes in library during month

8.  FEID single, dual, and triple string jobs per week

9.  FEID connect hours per month

10. Other categories as defined by NASA

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:**]{.smallcaps} Rev. 1 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.7-d**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:
**01/10/00**

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **TITLE**: Software Development Plan

7\. **DESCRIPTION/USE**: To provide project and functional area
management with the level of detail into plans, schedules, and status
information necessary for proper control and direction of effort in all
areas of the project.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Assumption of an ongoing requirement; no
break in existing submission schedule.

10\. **SUBMISSION FREQUENCY**: Product shall be submitted monthly.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.7, 1.4.3.9, 1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: The development plan shall describe the
major managed deliverables and milestones for the overall performance
and status of work efforts assigned to each task order.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

13.3 **[CONTENTS]{.underline}**: Individual development plans from the
task order areas shall be combined into a project wide development plan
containing actions, issues, deliverables, and milestones to a level of
detail which provides NASA an accurate status of all products. The
development plan shall include but is not limited to:

a\. Shuttle flight schedule history and plan with an OI to flight
mapping

b\. Flight-to-flight release schedule for each mass memory load being
planned

c\. Action item assignments and due dates

d\. Detailed reconfiguration schedule for each flight

e\. Detailed schedule for all builds and milestone points in OI
development

f\. OI development issues and actions tracking

g\. OI Level 6 and 7 detailed status of testing

h\. Contractor actions to write CR's

i\. Compiler audit schedules and status

j\. Training development plans and schedules

13.4 **[FORMAT]{.underline}**: Contractor shall conform to delivery
media formats and electronic data formats per DRD 1.1.4.1-e, Data
Management Plan, or per Contracting Officer approval.

13.5 **[MAINTENANCE]{.underline}**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.7 -e

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Software Configuration Management Report (CMDB Report)

7\. DESCRIPTION/USE: Allows NASA to determine the current status and
disposition of any CR or DR control document.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Product shall be submitted weekly.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.7

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Records the configuration management
activities associated with each Flight Software Change Request and
Discrepancy Report and it's relation to software delivery end items.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: All CR's and DR's across the history of the
Shuttle FSW are maintained in a CMDB and reported by number along with
the following tracking data at a minimum:

1.  Title and date reported or submitted

2.  FSW release applicability

3.  Severity of problem (for DR's only)

4.  NASA board dispositions and date

5.  Contractor organization assigned corrective action

6.  FSW OI release incorporating code changes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

5.  [MAINTENANCE]{.underline}: None required

    **DATA REQUIREMENTS DESCRIPTION (DRD)**

    1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:**]{.smallcaps} Rev.
    1 2. **[DRD NO.]{.smallcaps}**: **1.4.3.7-f**

    3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE
    REVISED]{.smallcaps}**: **01/10/00**

    5\. **[PAGE]{.smallcaps}**: 1/1

    6\. **TITLE**: Software Quality Assurance Assessment Report

    7\. **DESCRIPTION/USE**: To provide management (contractor and NASA)
    with a summary of contractor's SQA assessment of FSW development and
    verification at CI.

    8\. **DISTRIBUTION**: Per Contracting Officer's Letter

    9\. **INITIAL SUBMISSION**: Assumption of an ongoing requirement; no
    break in existing submission schedule.

    10\. **SUBMISSION FREQUENCY**: Product shall be submitted at CI for
    each OI system.

    11\. **REMARKS**:

    12\. **INTERRELATIONSHIP**: 1.4.3.7

    13\. **DATA PREPARATION INFORMATION**:

    13.1 **[SCOPE]{.underline}**: SQA assessment of contractor's
    adherence to established design and development standards employed
    in the phases implementation of the FSW. The contractor SQA
    assessment will be in accordance with contractor SQA assessment
    activities defined in the Space Shuttle Orbiter Avionics software
    Quality Assurance Plan. (DRD 1.4.3.7-h)

    13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

    13.3 **[CONTENTS]{.underline}**:

    a\. Traceability between requirements, delivered software, and
    verification testing specification and results

    b\. Adherence to established design and programming standards and to
    applicable embedded verification and validation standards

    c\. Configuration management conformance to standards

    d\. Verification test conduct adherence to procedures and test
    requirements

    e\. Deliverables handling adherence to quality procedures and
    deliverables adherence to DRD requirements

    13.4 **[FORMAT]{.underline}**: Contractor shall conform to delivery
    media formats and electronic data formats per DRD 1.1.4.1-e, Data
    Management Plan, or per Contracting Officer approval.

13.5 **[MAINTENANCE]{.underline}**: None Required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.7 -g

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Quarterly Quality Report

7\. DESCRIPTION/USE: Describes the quality and reliability of the flight
software, and the quality of the flight software application tools.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Product shall be submitted on quarterly
review dates as specified by the COTR.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.7

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Describes the quality of the software as shown
by tracking of quality measurements including Early Detection Rate,
Process Error Rate, Product Error Rate, and Released Product Error Rate.
Also describes the reliability of the FSW through the appropriate
reliability measurements.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The Quarterly Quality Reports will include:

1.  Historical trends of quality measurements since OI release 1
    including process errors, product errors, early detection rates,
    verification effectiveness, and released product errors. Both charts
    and tabular history data will be presented

2.  Historical trends of reliability measurements and estimated time to
    the next problem will be computed using statistical and reliability
    engineering models

3.  Overview of quality improvement activities undertaken by the
    contractor and the results of their usage

4.  Selected metrics of the software process will be maintained and
    reported. All metrics defined under the contract will be reported
    and evaluated for trends

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.7 -h

2\. DATA TYPE: 3 4. DATE REVISED:

> 5\. PAGE: 1/2

6\. TITLE: Space Shuttle Orbiter Avionics Software Quality Assurance
(SQA) Plan

7\. DESCRIPTION/USE: To describe the SQA approach to assuring the
quality of the Onboard Shuttle (OBS) Software, and to specify procedures
used for internal and external SQA interface activities.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Product shall be submitted annually.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.7

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: SQA activity specified for SQA assessment and
involvement in all OBS plans, processes, and procedures relevant to
satisfy OBS contractual requirements.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}:

1.  Introduction

This paragraph shall summarize the purpose and contents of the plan
relative to the OBS flight software project activities.

1.  Reference Documents

This paragraph shall list, by document, number and title of all
documents listed in this plan.

1.  Software Quality Organization and Responsibilities

This section shall define the SQA organization responsibilities,
organizational structure and reporting requirements.

1.  SQA Training Certification

The contractor shall identify the SQA training program and the
procedures followed in certifying the SQA personnel.

1.  SQA Interfaces

The contractor shall define the SQA organization's interfaces with the
following:

-   Software Development Organization

-   Configuration Management

-   Documentation Management

1.  Subcontract Management

The contractor shall define that all applicable SQA requirements which
are flowdown to subcontractor(s). The contractor shall ensure that the
subcontractor(s) SQA implementation is in accordance with the SQA
contractual requirements.

1.  SQA Role in the Software Life Cycle

This section shall identify and define the SQA participation in the life
cycle milestones. This shall identify the life cycle in terms of the
following:

-   Requirements Definition

-   Design Phase

-   Code and Test Phase

-   Software Acceptance and Release

-   Post Turnover Support

1.  Software Quality Assurance Audits

The contractor shall conduct annual audits to verify compliance to
approved planned, procedures, processes, and standards. As a minimum,
these audits shall include:

-   Configuration Management

-   Software Development Library Controls

-   Software Testing

-   Documentation Management and Procedures

-   Software Development Processes

1.  Corrective Action

The corrective action monitoring and statusing procedures shall be
specified in this section.

1.  SQA Records Retention

This subparagraph shall describe the contractor's plans for preparing
and maintaining records of each quality evaluation/audit performed.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by PCN's or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.7 -i

2\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Software Quality Assurance Audit/Inspection

7\. DESCRIPTION/USE: To provide management with the findings and results
of audits, inspections, and product deliveries. A copy of each report
shall be retained in the contractor's SQA record retention files.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement

10\. SUBMISSION FREQUENCY: As required per the Quality Assurance Plan

11\. REMARKS:

12\. INTERRELATIONSHIP:1.4.3.7

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Software Quality Assurance findings resulting
from conducting audits and inspections, FSW and FSWAT development and
flight-to-flight maintenance activity.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}:

a.  Date Performed

b.  SQA Involvement

c.  Evaluation/Audit Criteria

d.  Findings, including detected problems, with reference to software
    problem report(s) as appropriate

e.  Recommended Corrective Action

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 3. DRD NO.: 1.4.3.7-j

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Flight Software Process Support Products & Services

7\. DESCRIPTION/USE: The products and services required to support the
flight software process and NASA Engineering Directorate control boards,
meetings, databases, records, documentation, agendas and reports.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Weekly for most products

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.7

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Describes the control board and meeting
coordination, the maintenance of databases and document and report
generation.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}:

13.3.1 [CONTROL BOARDS AND MEETINGS]{.underline}: This includes the
administration of formal boards and meetings including the
responsibility for agendas, scheduling, reporting of results and
maintaining records. The specific control boards and meetings include,
but are not limited to the following:

a.  Test and Operations Board

b.  Flight Software Discrepancy Review (DR) Control Board

c.  Support Software Boards (Change Request, DR, Compiler)

d.  Operational Increment (OI) Meetings

e.  Change Review Board

f.  Discrepancy Pre-Board Support

13.3.2 [DATABASE SUPPORT AND RECORDS FUNCTION]{.underline}: This
includes the maintenance and operation of various databases that contain
technical and administrative data pertaining to flight software
documents. A record of software change instruments Shuttle Program
Documents are also maintained. Continuous access to record contents is
provided. The following list describes the databases and records
maintained

a.  Support Software Databases (Change Request, DR, Compiler)

b.  Program Notes and Waivers

c.  Verification Test Procedures and Verification Test Report Data
    Coordination

d.  EV Library of Flight Software Requirements and Delivered Products

13.3.3 [DOCUMENTATION AND REPORT GENERATION]{.underline}: This includes
the scheduling, tracking and distribution of configuration control
meeting support documents for FSW Process and NASA Engineering
Directorate Support. This includes, but is not limited to, the
distribution of products as well as maintenance of copies and records of
the products. All documentation associated with the elements listed in
13.3.1 is included. Standard and specialized reports are to be produced
from the databases listed in 13.3.2 as required.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.8 -a

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: FSW Applications Tools Requirements Documents and Interface
Control Documents

7\. DESCRIPTION/USE: Defines the requirements, specifications, and
controlled interfaces for the FSW Applications Tools used to perform the
FSW and FSWAT processes.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal at CI for
each OI system and approved changes as required.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.8

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: The requirements documents, specifications,
and interface control documents for the FSW Applications Tools used for
the FSW and FSWAT development, build, reconfiguration, verification, and
configuration management processes.

13.2 [APPLICABLE DOCUMENTS]{.underline}: Support Software Change
Requests (SSCRs) authorizing changes to these requirements.

13.3 [CONTENTS]{.underline}: These documents specify detailed software,
data, and interface requirements and requirements design assumptions.

The individual Requirements Documents are defined in the Flight Software
Build and Reconfiguration Support Tools - JSC 20183 document ( DRD
1.4.3.8-c ).

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by PCN's or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.8 -b

2\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/2

6\. TITLE: FSW Applications Tools User's Guides

7\. DESCRIPTION/USE: A technical description of how to utilize the FSW
Applications Tools.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required, updated at CI

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.8

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: User information for the FSW Applications
Tools used for the FSW and FSWAT development, build, reconfiguration,
verification, and configuration management processes.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: These documents contain descriptions of how
to execute the FSW Applications Tools and how to interpret output
messages.

> The individual User's Guide documents are defined in the Flight
> Software Build and Reconfiguration Support Tools - JSC 20183 document
> ( DRD 1.4.3.8-c ).

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by PCN's or complete reissue

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.8-c

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Flight Software Build and Reconfiguration Support Tools - JSC
20183

7\. DESCRIPTION/USE: An inventory and brief description of the Flight
Software Application Tools (FSWAT) which are used to develop, verify and
reconfigure fight software.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Once per Operational Increment (OI) to be
published six weeks after CI.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.8

13\. DATA PREPARATION INFORMATION

13.1 [SCOPE]{.underline}: The Category A tools for the Primary Avionics
Software System (PASS) and Backup Flight System (BFS). The document also
contains sections describing the operating system level tools and the
High Order Assembly Language (HAL) Compilers.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENT]{.underline}: Each tool will be identified by functional
area and will include the following information: a brief description,
applicable computer system, language the tool is written in, number of
source lines of code (SLOCS), users of the tool, functional area, and
identification of reference documentation (requirements,design, users
guide).

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE:]{.underline} Changes shall be incorporated as
required by PCN's or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.8-d

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: HAL/S FC Compiler Test Plan

7\. DESCRIPTION/USE: For each release, the compiler test plan is
presented for review to assure testing of the compiler is adequate.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal 1 week
prior to compiler verification start for each compiler system

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.8

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Describes the tests planned for in use in
verifying all changes to the compiler.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The Compiler Test Plan presents the
methodology and procedures to be used to verify each of the changes
implemented in the compiler for the release and the integrity of the
integrated compiler itself:

This plan lists:

1.  All SSCR's/SSDR's implemented on the release

2.  Those SSCR's/SSDR's requiring compiler source code changes

3.  Those SSCR's/SSDR's causing object code changes

4.  Those SSCR's/SSDR's affecting error messages

5.  Those SSCR's/SSDR's having other unusual impacts

6.  External tools used in the compiler build

7.  Changes in compiler build procedures from the previous release

8.  External tools used in compiler testing

9.  Changes in test procedures from the previous release

10. Expected deviations from normal test results

11. Schedule for testing of the release

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.8-e

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: HAL/S FC Compiler Test Results Report

7\. DESCRIPTION/USE: For each release, the compiler test results report
is presented to assure that the testing of the compiler is complete and
correct.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal 1 week
prior to each compiler release.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.8

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Describes the results of the tests used to
verify all changes to the compiler.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The Compiler Test Results Report describes
the methodology and procedures that were used to verify each of the
changes implemented in the compiler for the release and the integrity of
the integrated compiler itself and the results of these tests.

This report lists:

1.  All SSCR's/SSDR's implemented on the release

2.  Changes in the baseline since the test plan review

3.  SSCR's/SSDR's that caused object code changes

4.  SSCR's/SSDR's that affected error messages

5.  SSCR's/SSDR's that had other unusual impacts

6.  Changes in compiler build procedures from those presented in the
    test plan

7.  Changes in test procedures from those presented in the test plan

8.  Actual deviations from expected results

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:**]{.smallcaps} Rev. 1 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.8-f**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:
**01/10/00**

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **TITLE**: Applications Tools SSDR Analyses and Waivers

7\. **DESCRIPTION/USE**: To document an analysis recommendation for
SSDR's written against the FSW Applications Tools.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Assumption of an ongoing requirement; no
break in existing submission schedule.

10\. **SUBMISSION FREQUENCY**: Product shall be submitted bi-weekly as
required

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: Provided for all SSDR's written against
the Applications Tools.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

13.3 **[CONTENTS]{.underline}**: For each SSDR to be dispositioned, an
analysis form containing the following shall be provided.

The DR analysis form shall include:

a\. DR number and title

b\. Releases to which the analysis applies

c\. Analysis start date, completion date, duration and DR priority

d\. Investigator

e\. How the problem was discovered

f\. Detailed technical description of the problem

g\. Fix resource estimates and suggested modification

h\. Other pertinent data

For those SSDRs that require a waiver, the waiver form shall include:

a\. DR number and title

b\. Releases to which the waiver applies

c\. Investigator

d\. DR disposition

e\. Detailed description of how the user sees the problem

f\. Code to produce the problem and workarounds

g\. Other pertinent data

13.4 **[FORMAT]{.underline}**: Contractor shall conform to delivery
media formats and electronic data formats per DRD 1.1.4.1-e, Data
Management Plan, or per Contracting Officer approval.

13.5 **[MAINTENANCE]{.underline}**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.8-g

2\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: GPC Emulator Simulation Documents

7\. DESCRIPTION/USE: Provides detailed descriptions of the math model
software, system requirements and procedures for running the Simulation,
and the operator interface software for the GPC Emulator Simulation.

8\. DISTRIBUTION:

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement

10\. SUBMISSION FREQUENCY: As required

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.8

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Covers all the documentation associated with
the GPC Emulator Simulation system.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: These documents include a general
description of how the math models interact with each other, identify
the RS/6000 system requirements, the components of the Simulation, and
the process and procedures for modifying, building, and executing the
Simulation, and include a general description of the operator interface
software.

> The documents are:
>
> GPC Emulator Simulation Math Model Software Detailed Description
> Document
>
> GPC Emulator Simulation Maintenance System User's Guide
>
> GPC Emulator Simulation Operator Interface Maintenance Manual

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:**]{.smallcaps} Rev. 1 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.8-h**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:
**01/10/00**

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **TITLE**: Support Software Change Control Board (SSCCB) Process
Products

7\. **DESCRIPTION/USE**: Products used in support of the SSCCB.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter.

9\. **INITIAL SUBMISSION**: Assumption of an ongoing requirement.

10\. **SUBMISSION FREQUENCY**: ref. 13.3 below. a - once per year, b -
once per OI with completion in time for CR approval by CI, c. -
quarterly, d - FACI and CI.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.8

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: These documents are required for the
operation of the Support Software Change Control Board.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

13.3 [**CONTENTS**:]{.underline}

a\. Support Software Change Control Board Procedures Document - Defines
the procedures for the operation of the SSCCB.

b\. Tool baseline CR's for both the PASS and the BFS - Flight software
CR's that define the tool baseline for the OI by listing the SSCR's and
SSDR's approved for the release.

c\. Changes to baseline CR's- CR mods that define the movers for the
PASS and BFS tools delivered after CI. The SSCR's and SSDR's are listed
as deltas to the baseline along with a brief description of the change
to the tool.

d\. Audit of SSCR/SSDR Oracle Database to ensure accuracy with the
CMDB - Differences are noted and investigated to determine if updates to
either database is required.

13.4 **[FORMAT]{.underline}**: Contractor shall conform to delivery
media formats and electronic data formats per DRD 1.1.4.1-e, Data
Management Plan, or per Contracting Officer approval.

13.5 **[MAINTENANCE]{.underline}**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.8-i

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: SPON System Interface and Integration

7\. DESCRIPTION/USE: To document the IMIC system integration,
application support, and user support needed for the NACC insight.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission

10\. SUBMISSION FREQUENCY: As required

11\. REMARKS: N/A

12\. INTERRELATIONSHIP: N/A

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: This requirement specification establishes the
SPON's system integration, application support, and user support.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document/task shall contain:

A.  Scope

B.  NACC Integration and Synchronization

C.  Application Computer Resource Management

D.  Change Management

E.  Problem Management and Help Desk Support

F.  Security administration and ID administration

G.  Independent Systems Assurance

H.  System Data Base Administration

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9 -a

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Orbiter Avionics Software Programming Standards Document

7\. DESCRIPTION/USE: The Programming Standards Document will define for
programmers the standards to be employed in the development of software
for the Space Shuttle Primary Avionics Flight Software.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Product shall be submitted annually

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Defines the programming standards to be used
for the development of FSW for the Space Shuttle Orbiter.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The standards document will contain
complete and explicit definitions, restrictions, and style guidelines
for the following aspects of software development.

a.  The definition of structured programming methods to be used

b.  A definition of naming conventions for all types of variables, data
    sets, segments, labels, procedures, functions, compools, and other
    data structures

c.  Special restrictions and guidelines in the use of HAL/S language
    features including data exchange, event variable, process priority,
    realtime features, I/O transactions, and interprocess variables

d.  The definition of a program, task, procedure, and function, and
    guidelines on when to use each

e.  Guidelines to be placed on the programmer in the use of diagnostic
    messages, data referencing, restricted HAL statements, and data
    initialization

f.  Standards to be applied to source code documentation including
    prologues, inline statement comments, and design specifications

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by PCN's or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9 -b

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: FSW Maintenance Specification Document

7\. DESCRIPTION/USE: This document provides a high level technical
description of the PASS FSW and the environment in which it operates.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal at CI for
each new OI release.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: The Maintenance Specification Document was
created to document the Flight Software (FSW) at a higher level than the
Detailed Design Specification (DDS) document. It is a unique user
document created to help current and future programmers and analysts
maintain the FSW. It contains functional overview of each principal
function or functional area and information to help people better
understand the FSW code.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The maintenance specification consists of
three parts as follows:

-   GN&C (contains Guidance, Navigation, Flight Control & Sequencing)

-   SSW (contains System Software)

-   VCS (contains SM/PL, Vehicle Utility and RMS)

> Each maintenance Specification Document will include the following:

1.  Text

```{=html}
<!-- -->
```
a.  Purpose/Usage

b.  Initiation/Termination Criteria

c.  Function Description

d.  Implementation Description

e.  Sequencing Description

f.  Design Considerations

g.  References

```{=html}
<!-- -->
```
2.  Flowcharts

```{=html}
<!-- -->
```
a.  Control and Flowcharts

b.  Data Flowcharts

c.  Sequencing Flowcharts

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by PCN's or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9 -c

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/2

6\. TITLE: Detail Design Specification (DDS)

7\. DESCRIPTION/USE: To define the detailed and data dependent design
for each program end item.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal at FACI
plus six weeks. Post FACI changes will be delivered at CI.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Presents the detailed design of all the source
code modules comprising the PASS software that runs in the on board
computers of the Space Shuttle.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The DDS is a document consisting of
detailed design descriptions for each of the code modules comprising the
software that runs in the onboard computers of the Space Shuttle.

The documentation for each module relates directly to the corresponding
module's source code, and specifies the following information:

1.  Module Name: The name of the module described in the section. Both
    an English and a HAL/S or Assembly name shall be provided

2.  Introductory Paragraph: A brief description of the functions
    performed by the module

3.  Control Interface: An identification of all the other modules that
    use or invoke this module, the form in which this module must be
    invoked, and the execution rate and priority at which this module is
    executed in each case

4.  Input Data: A list of all the parameters used as inputs by this
    module and their source.

5.  Process Description: A narrative that functionally describes the
    processing performed by the module as control flows through it. This
    description shall include algorithms and equations where necessary
    to explicitly define the design

6.  Output Data: A list of all the parameters computed by this module
    and their destinations

7.  Module References: A list of all the external modules referenced,
    invoked, activated or deactivated, by this module

8.  Module Type and Attributes for HAL/S modules: The HAL/S type of
    module (PROGRAMS, PROCEDURE, FUNCTION, COMPOOL, etc.) and attributes
    (EXCLUSIVE, REENTRANT, DEPENDENT, etc.) of the module

9.  Template References: A list of data templates and include segments
    referenced by the module

10. Error Handling: Descriptions of how the code in the module responds
    to specific, error conditions anticipated

11. Constraints and Assumptions: The processing limitation of the
    module, and the assumptions reflected in the design

12. Flow Diagrams: Graphical representations of the functional flow of
    control through the module

The DDS document is organized according to software functions as
follows:

-   System Services

```{=html}
<!-- -->
```
-   Part 1 - Flight Control Services (FCOS)

-   Part 2 - User Interface (UI)

-   Part 3 - System Control (SC)

```{=html}
<!-- -->
```
-   Applications

```{=html}
<!-- -->
```
-   Part 1 - Guidance, Navigation and Control (GN&C)

-   Part 2 - Systems Management (SM)

-   Part 3 - Vehicle Utility (VU)

For each book or published part, a list of CR numbers which have been
incorporated into the document and on which OI release shall be
included.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by PCN's or complete reissue

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9 -d

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Software First Article Configuration Inspection (FACI) Report

7\. DESCRIPTION/USE: This report presents to NASA the status of the OI
software development release for verification. This report officially
reports the contractor's OI development completion of baselined
requirements.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal at FACI
for each OI system

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.8, 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Covers the results of all Flight Software
development and development testing performed prior to release of the OI
software for verification.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This documentation shall present for both
Flight Software and Flight Software Application Tools a summary and
status of all software changes, DR's, waivers and user notes, major
capability changes, and the Level 6 and 7 verification plans related to
a specific OI system. It shall include a summary of processes leading to
FACI and shall identify any post FACI development work in line to CI. At
a minimum, the reporting shall include:

a.  Overview of the development process leading up to FACI

b.  Identification of each CR and DR change applied to the OI software

c.  A summary by major functional areas of new major capabilities
    provided with the new OI software

d.  Summary and description of all FSW and FSWAT waivers and Operations
    Notes deleted by this OI and still applicable to the OI.

e.  Definition of all post FACI open work including open DR's,
    potentially applicable to the OI.

f.  Summary and status of the quality metrics historically and for this
    OI

g.  A definition of the Level 6 and 7 verification plans

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9 -e

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Flight Software Capabilities Verification Plan (Level 6)

7\. DESCRIPTION/USE: Verification test plan is used to determine work
load over the life of the delivery and to allow NASA to plan and manage
the NASA review of testing.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal at FACI
for each OI system. Review copy shall be provided 4 weeks prior to FACI

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Describes the specific testing activity for
each FSW change request and projected dates of start and completion for
each detailed verification test as planned at that time.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The Test Plan consists of the following:

1.  Cover Sheet: Memo addressed to the FDSD OI Coordinator stating the
    start of the test planning cycle and containing a statement of the
    areas in FSW to be tested and any off nominal items for the upcoming
    test phase

2.  Overview: A breakdown of CR's/DR's and their individual testing
    requirements as well as graphical and/or table depiction's of FSW
    area (e.g., Guidance, Nav, etc.) workload balance

3.  Listing of CR's: A listing generated from the configuration database
    showing all CR's currently scheduled for the current FSW release
    under test

4.  Listing of DR's: A listing generated from the configuration database
    showing all DR's currently scheduled for the current FSW release
    under test

5.  Listing of Test Cases: A listing generated from the configuration
    database showing all planned Level 6 detailed verification test
    cases including the projected start and completion dates for each
    individual test case

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9 -f

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Flight Software Capabilities Verification Procedures (Level
6)

7\. DESCRIPTION/USE: Verification test procedures (VTP) are reviewed by
the contractor and NASA to assure accuracy of capabilities tests.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required for each OI system with planned
submittal prior to CI or by the SRR of the appropriate flight.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Describes the specific testing content and
methods to be used in verifying all new capabilities and error
corrections in the FSW. This product is required for all pre-CI and
post-CI approved changes to the FSW which are identified as requiring
testing.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The VTP consists of the following:

1.  The prologue: The prologue describes the testing environment, the
    related requirements documentation, the functional objective of the
    test, the change authorization which documents or describes the FSW
    change being tested, and the current testing objective

2.  The test log: The test log describes the test objective and the
    applicable steps in the test

3.  An initialization description: The initialization description
    describes the initial test conditions such as Shuttle systems
    states, avionics failures and flight phase conditions

4.  Test step descriptions: The test step descriptions list each step in
    the testcase. For each step, there will be a listing of the
    requirements referenced for that step, a detailed description of the
    step and what the expected results of that step are

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9 -g

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/2

6\. TITLE: Level 6 Test Cases - Capabilities Verification Phase

7\. DESCRIPTION/USE: Verification tests results allow acceptance of FSW
programs and approval of delivery for reconfiguration.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required for each OI system with planned
submittal prior to CI or by the SRR of the appropriate flight.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Verification Test Cases contain the materials
generated during the execution, analysis, and inspection of the flight
software end item tests.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}:

a.  JSTEP Expansion - A listing of the syntax checker which verifies the
    simulation control commands that were used to run the test

b.  FEID Online - Detailed listing of actual time stamped simulation
    events, both user induced and simulation induced, which serves as a
    simulation timeline record.

c.  Post Processor Output - This contains results of the interaction
    between the flight software and the testing scenario/environment.
    This output may include such things as:

-   Trace routines - Lists the flight software program execution path
    along with the execution times of each program step

-   DEU images - Relevant DEU images that assist in establishing what
    happened during the test and in determining whether the display
    programs are operating correctly

-   Parameter snaps - A time history listing of all significant
    parameters showing flight time versus parameter value tables

d.  Epilogue - Individual test case summary report which contains such
    information as:

-   Flight software authorization either partially or totally closed by
    this test case

-   Discrepancies discovered against flight software to support software
    which influence the outcome of the test case

-   Observations and results

-   Deviations from expected results

-   Conclusions

e.  Any additional material that further demonstrates the correctness of
    the test approach, i.e., bench program output, annotated code and
    output listings, resulting discrepancies, etc.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9 -h

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: FSW Performance Verification Plan (Level 7)

7\. DESCRIPTION/USE: Performance verification test plans are required by
NASA to assure accuracy of FSW performance verification approach.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal no later
than 5 weeks prior to FACI and at FACI.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Describes a set of tests for NASA community
review which prove the accuracy and performance of the FSW with respect
to expected results from requirements change effects across the major
software regions.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The test plan consists of the following
major regions:

1.  GN&C performance tests

2.  System Services performance tests

3.  VCS performance tests

Level 7 testing is at the performance level and is designed to assure
that the vehicle performance and flight software system performance is
not degraded as a result of FSW changes in nominal and off-nominal
situations.

The testing is divided into capability testing and System Integrity
tests. Capability test are designed to test new enhanced capabilities
resulting from FSW changes. System Integrity tests are designed to
provide mission phase coverage, assurance of satisfactory vehicle
performance and FSW system performance.

Level 7 test specifications will contain:

1.  Identification name for the test case

2.  Title/Description of the test case

3.  Principal functions tested

4.  Major mode being tested

5.  The testing objective

6.  The testing approach

7.  Special Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:**]{.smallcaps} Rev. 1 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.9-i**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:
**01/10/00**

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **TITLE**: FSW Test Reports - Performance Verification (Level 7)

7\. **DESCRIPTION/USE**: Level 7 test results reports are reviewed by
the technical community to determine correct performance of software
prior to CI software acceptance.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Assumption of an ongoing requirement; no
break in existing submission schedule.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal 8
weeks prior to CI, or as specified by the COTR.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.9

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: The results of each performance test as
specified in the FSW Performance Verification Plan (DRD-1.4.3.9-h).

13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

13.3 **[CONTENTS]{.underline}**: The performance test results consisting
of:

a\. The CR tested - specify the particular CR's that were tested by each
L7 test case

b\. The test specification - contains the identification name, title,
description of each test case, Ops and major modes tested, testing
objective, and testing approach

c\. Deviation from test specification - The deviations from the original
test specification (established at CI).

d\. General system description - The general system description defining
the flight software version, mission definition, mission data, simulator
base, computer configuration, simulator CR/DR patches required, and the
FSW CR/DR patches required

e\. CR description - each CR which will be tested is summarized

f\. Test procedure - A step-by-step instruction of all the steps used to
test the software

g\. Detailed test results - The detailed results of each test case will
be described sequentially for each major capability that is being
tested. Issues that are raised or uncovered by the testing will be noted

h\. Conclusions - Conclusions about the testing philosophy and results
will be noted. Specifically, whether the test was successful and whether
the vehicle and flight software performed satisfactorily will be stated

13.4 **[FORMAT]{.underline}**: Contractor shall conform to delivery
media formats and electronic data formats per DRD 1.1.4.1-e, Data
Management Plan, or per Contracting Officer approval

5.  13.5 **[MAINTENANCE]{.underline}**: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9 -j

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Software Configuration Inspection (CI) Report

7\. DESCRIPTION/USE: This report presents to NASA the delivery of an
Operational Increment (OI) software milestone. This report officially
documents the contractor's completion of OI development and
verification.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal at CI for
each OI system.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.8, 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Covers the results of all Flight Software
development, verification, documentation, and configuration control
performed in support of a new FSW Operational Increment (OI)

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This documentation shall present for both
Flight Software and Flight Software Application Tools a summary and
status of all software changes, DR's, waivers and user notes,
verification testing, certification, FSW memory sizing, and FSW CPU
loading estimates related to a specific OI system. It shall include a
summary of the processes leading to CI and shall identify any open work
post CI. At a minimum, the reporting shall include:

a.  An overview of the OI history and new major capabilities

b.  Identification of each CR and DR change applied to the OI software

c.  Summary of all verification and performance testing for this OI and
    test mapping to CR's and DR's

d.  Summary of all FSW and FSWAT waivers, Ops Notes and User Notes
    deleted and still applicable to the OI

e.  Definition of the memory space allocation and CPU performance status
    and margins with this OI

f.  Summary and status of the quality metrics historically and with this
    OI

g.  Status of all open DR's applicable to this OI software

h.  Flight Software Memory sizing and CPU Loading Estimates

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9 -k

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: FSW OI Deliverables

7\. DESCRIPTION/USE: FSW operational increment (OI) products will be
delivered for use by the reconfiguration organization for production of
training and flight loads.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal for each
OI system.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.8, 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: The FSW and FSW Applications Tools software
and products required for execution of the flight to flight
reconfiguration processes.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: Includes all deliverable products specified
in the FSW Class I Integration Plan (CIP), JSC 22320, as deliverables
for each OI.

13.4 [FORMAT]{.underline}: Products will be generated in Software
Development Facility (SDF) data sets in the formats described in the
CIP. The CIP contents are under configuration control by the SASCB.

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.:1.4.3.9-l

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/2

6\. TITLE: Flight Software Class 1 Integration Plan (CIP) - JSC-22320

7.  DESCRIPTION/USE: Defines the Primary Avionics Software System (PASS)
    and Backup Flight System (BFS) flight software products which
    comprise an Operational Increment (OI) system, and the flight
    software development tools which develop the flight to flight
    reconfiguration.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Once for each new Operational Increment of
flight software to be NASA approved by the Configuration Inspection for
that OI

11\. REMARKS:

12\. INTERRELATIONSHIP: Shuttle Avionics Mass Memory Unit Computer
Program Integration Plan (MIP), JSC-08338; Flight Software and Mission
Data Reconfiguration Tools Document, JSC-20183

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Describes the content and format of flight
software products and reconfiguration tools delivered to NASA by the
development contractors.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}:

a.  PASS flight software:

```{=html}
<!-- -->
```
1.  Details the OI products (format, media, method of delivery) to be
    delivered to NASA at CI, including: source code, flight software
    build documentation, products used for flight to flight
    reconfiguration.

2.  Describes the subset of OI products (format, media and method of
    delivery) to be delivered to other contractors and organizations.

3.  Describes the authorization, format and delivery of all flight
    software patches to be performed prior to, or post CI, on the OI
    base system, and on a recon system intended for flight.

4.  Lists the software tools delivered to support PASS/BFS development
    and

> PASS reconfiguration

b.  BFS flight software:

```{=html}
<!-- -->
```
1.  Details the OI products (format, media, and method of delivery) to
    be delivered to NASA at CI, including: source code, flight software
    build documentation, products used for flight to flight
    reconfiguration.

2.  Describes the subset of OI products (format, media and method of
    delivery) to be delivered to other contractors and organizations.

3.  Describes the authorization, format and delivery of all flight
    software patches to be performed prior to, or post CI, on the OI
    base system, and on a recon system intended for flight.

4.  Lists the software tools delivered to support BFS development and
    reconfiguration

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: Maintained by the contractor and
submitted for NASA approval via a Change Request (CR) to the Shuttle
Avionics Software Control Board (SASCB).

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9-m

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Payload Software Capabilities Overview - JSC 17086

7\. DESCRIPTION/USE: Provides a high level description of the payload
software capabilities provided on-orbit by the Systems Management
application of the PASS flight software. The payload customers may
choose to use these capabilities for the flight. The document is
intended for distribution to payload customers.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: When a capability changes.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.9

13\. DATA PREPARATION INFORMATION

13.1 [SCOPE]{.underline}: This document is limited to a description of
the payload software capabilities provided on-orbit by the Systems
Management application.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: A detailed description of the payload
software capabilities.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE:]{.underline} Changes shall be incorporated as
required by PCN's or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9-n

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/2

6\. TITLE: Change Request Risk Assessments

7\. DESCRIPTION/USE: To give NASA management an estimate of the cost
associated with implementing a CR, the risk associated with the CR, and
any impacts to other work.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required to support Software Change
Request (SCR) for all code changes.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: The risk assessment will define costs,
schedule impacts to existing work, and risks or implementation for all
CR's.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The VCS and SSW risk factors assessed are:

1.  Describe the current operation of the software system

2.  Describe code operation after implementation of change

3.  Define work-a-rounds or consequences if change is not implemented

4.  Recommendations for or against implementation

5.  Size of change in modules affected and lines of code or patch size

6.  Complexity of change whether low, medium, or high and the reason

7.  Criticality of Function being modified

8.  Fit into current design or special design required

9.  Frequency of execution of affected code paths

10. List the functional areas involved in the change

11. Identify recent change activity in the functional area

12. Define all flight phases affected

13. Identify the interactions or dependencies with other changes

14. Provide number of CR mods

15. Provide number of requirements issues

16. Provide number of requirements inspections

17. List DR's closed by the change

18. Define manpower impact in manweeks

19. Define the GPC memory space impacts in code and data space

20. Performance impacts to the Shuttle system

21. Define the verification costs in test cases and manweeks

22. Additional comments

> The GN&C and RMS risk factors assessed are:

1.  Provide a short summary of benefits of the change

2.  Estimated size of change

3.  Complexity of change whether low, medium, or high and the reason

4.  Criticality of areas affected

5.  Change affects abort or error paths vs. Nominal code paths

6.  Number of failures required to exercise this code

7.  Define the operational phases affected

8.  Indicate whether new or existing code is affect

9.  Describe recent change activity in the area of code

10. Describe other change activity in the area on the OI

11. Identify number of affected Principal Functions

12. Identify number of mods required for the CR

13. Describe requirements issues and their dispositions

14. Describe number of requirements inspections/reinspections (Author
    Involvement)

15. Define the development manpower impact in critical skills

16. Define the GPC memory space impacts in code and data space

17. Identify CPU performance impacts

18. Provide verification impacts (cost, risk)

19. Identify required tool modifications

20. Additional comments

> Any additional FSW Tool risks.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.9-o

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/2

6\. TITLE: Downlist Availability Configuration

7\. DESCRIPTION/USE: The FSW community uses this document to identify
what parameters are available for downlist.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal at CI for
each OI system.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.9

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: This document reports in a single source,
information specifying the actual availability of Primary Avionics
Software System (PASS) measurements for downlist on a given Operational
Increment (OI).

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This Downlist Availability Configuration
document contains two reports - a Requirements by MSID report (in which
all non-reconfigurable measurements that are available for downlist are
listed) and a Parent/Child Correlation report (in which all
non-reconfigurable Parent measurements are listed with their associated
child measurement). Each report is explained in more detail below.

The data in the requirements by MSID report is sorted by measurement
number (MSID). The 4^th^, 9^th^, and 10^th^ characters are ignored in
the sort. The following list describes each of the fields within the
report.

MSID - Measurement number of the parameter which is available for
downlist

Parent - Measurement number of the parent parameter associated with this
MSID

Parameter Nomenclature - The nomenclature of the parameter

Type - The data type od the measurement number

Units - The units of the parameter date

"0" 0 If the parameter is of type DISCRETE then the data in this field
indicates the meaning of the parameter when it has a value of binary 0

"1" - If the parameter is of type DISCRETE then the data in this field
indicates the meaning of the parameter when it has a value of binary 1

Format - D/L format and rate in which the parameter is downlisted

The data in the Parent/Child correlation report is sorted first by
parent measurement number (MSID) and then by child MSID. The 4^th^,
9^th^, and 10^th^ characters are ignored in the sort. The following list
describes each of the fields in the report.

Parent - Measurement number of the parent parameter which is available
for downlist

Child MSID - Measurement number of the child parameter associated with
the PARENT MSID

Parameter Nomenclature - The nomenclature of the parameter

"0" - The data in this field indicates the meaning of the child
parameter when it has a value of binary 0

"1" - The data in this field indicates the meaning of the child
parameter when it has a value of binary 1

Format - D/L format and rate in which the parameter is downlisted

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:**]{.smallcaps} Rev. 1 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.9-p**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:
**01/10/00**

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **TITLE**: Space Shuttle Programs PASS Parameter Data Tape Content

7\. **DESCRIPTION/USE**: Defines the requirements for the parameters to
be included in the PASS Parameter Data Tape (PDT).

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Assumption of an ongoing requirement; no
break in existing submission schedule.

10\. **SUBMISSION FREQUENCY**: As required with planned submittal at CI
for each OI system.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.9

**13. DATA** PREPARATION INFORMATION:

13.1 **[SCOPE]{.underline}**: Describes the PASS flight software HAL/S
parameters which are required to be included on the Parameter Data Tape
(PDT).

13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

13.3 **[CONTENTS]{.underline}**: Specifies only PASS parameters which
are on the PDT. The parameters may apply to the flight software areas of
Guidance, Navigation and Control; Systems Management; Vehicle Utilities;
and/or System Software (FCOS). It shall contain as a minimum:

a\. Purpose - The purpose of this document is to specify the PASS flight
software HAL/S parameters which are required to be included on the
Parameter Data Tape (PDT). Parameters are listed in a table in
alphabetical order by HAL/S name.

b\. Scope - This document specifies only PASS parameters which are on
the PDT; no other parameters are listed. The parameters may apply to the
flight software areas of Guidance, Navigation and Control; Systems
Management; Vehicle Utilities; and/or System Software (FCOS). Note that
only HAL/S name, FSSR name, MSID, and units fields are specified in this
document and that the FSSR name, MSID and units fields are optional for
all parameters but are included and verified when supplied in the
authorizing CR.

c\. Applicable Documents - The format of the PDT is defined in JSC 08338
(Memory Integration Plan), Appendix A.

d\. Table Format - This list is in alphabetical order by HAL/S name. The
lit is in tabular form and includes the following fields:

-   HAL -- the HAL/S name of the flight software parameter

-   FSSR Name -- the parameter name as defined by the source principal
    function

-   MSID -- the MSID of the parameter as defined by the Shuttle Data
    Integration Plan measurement and stimulus system

-   Units -- the units of the parameter

> e\. PDT Parameters - The actual formatted list of parameters contained
> on the Parameter Data Tape.

13.4 **[FORMAT]{.underline}**: Contractor shall conform to delivery
media formats and electronic data formats per DRD 1.1.4.1-e, Data
Management Plan, or per Contracting Officer approval

13.5 **[MAINTENANCE]{.underline}**: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.10 -a

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: MMU Reconfiguration Deliverables

7\. DESCRIPTION/USE: Shuttle MMU and PASS release deliverables and
supporting information to be sent to the various facilities.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.10

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: To provide Shuttle MMU and PASS release
deliverables and supporting information that is sent to the various
facilities.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: Includes products specified in the Shuttle
Avionics Mass Memory Unit Computer Program Integrated Plan (MIP), JSC
08338, as deliverables for each Flight or Special System.

13.4 [FORMAT]{.underline}: Products will be generated in the formats
described in the MIP. The MIP contents are under configuration control
by the Shuttle Avionics Software Control Board (SASCB).

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.10 -b

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Level 8 Products

7\. DESCRIPTION/USE: Level 8 test reports and products for review and
analysis use by technical community.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required for each Reconfiguration release

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.10

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Level 8 test reports and products for review
and analysis use by technical community.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: Includes products specified in the Flight
Software Reconfiguration Performance Test Plan (PTP), JSC 22530, as
deliverables for each Flight System.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.10 -c

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Monthly PASS Reconfiguration Status Report

7\. DESCRIPTION/USE: Describes the status and metrics of the PASS flight
software reconfiguration and the MMU reconfiguration deliverables.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted monthly with
planned submittal at status meetings.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.10

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Describes the status, schedule, quality, and
timeliness of the reconfiguration process.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}:

1.  Flight reconfiguration and issues status

2.  Reconfiguration schedules

3.  Process change status

4.  Reconfiguration product delivery summary information (actual and
    projected)

5.  Reconfiguration and level 8 metrics including quantity, timeliness,
    reconfiguration DR's and DR detection

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.:1.4.3.10-d

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: MMU Integration Plan (MIP) - JSC 08338

7.  DESCRIPTION/USE: Defines the Mass Memory Unit related products which
    are to be delivered for flight and field systems.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.10

13\. DATA PREPARATION INFORMATION:

1.  [SCOPE]{.underline}: Describes the content and format of flight
    software products for flight and field systems

> delivered by the FSW reconfiguration contractors.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

3.  [CONTENTS]{.underline}: Defines the requirements for inputs and
    outputs for processing and delivery of Mass

> Memory Unit contents for release to the field sites and use for
> flight. Defines the specific product formats and delivery mechanisms.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: Maintained by the contractor and
submitted for NASA approval via a Change

> Request (CR) to the Shuttle Avionics Software Control Board (SASCB).

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.10 -e

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Integrated Baseline Control Board (IBCB) Datapack

7\. DESCRIPTION/USE: Shows the detailed schedules for FSW
reconfiguration activities required to generate field and flight system
flight software loads.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Weekly

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.10

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Detailed planned and actual schedules for
flight software reconfiguration activities and other information related
to reconfigured systems and reconfiguration processes.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}:

1.  Detailed planned and actual schedules by flight system

2.  Flight system designators

3.  Flight system CR and DR implementation plans and matrix

4.  Historical summary of flights

5.  Reconfiguration process agreements

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.10 -f

2\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Level 8 Performance Test Plan Document

7\. DESCRIPTION/USE: Documents the test approach, products, and test
specifications for FSW reconfiguration verification (Level 8) to be
performed on flight system flight software loads.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement.

10\. SUBMISSION FREQUENCY: As required.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.10

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: The requirements and specifications for
testing conducted by the FSW reconfiguration contractors to verify
integrated FSW performance and assure product quality and integrity.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}:

1.  Philosophy, Approach, Quality Assurance and Process Control, and
    Applicable Documents

2.  Test Nomenclature, Description, Effectivity

3.  PASS GN&C Verification Test Specifications

4.  PASS /BFS Listen GN&C Verification Test Specifications

5.  BFS Engaged GN&C Verification Test Specifications

6.  PASS VCS Verification Test Specifications

7.  BFS VCS Verification Test Specifications

8.  MM Load Content Verification Specifications

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-e, Data Management
Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.11 -a

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: DPS Reports, Monthly Progress

7\. DESCRIPTION/USE: To summarize all work accomplished during each
month of contract performance in a comprehensive narrative report that
presents, for information or evaluation purposes, the Contractor's
overall program progress.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: The first initial report should cover a
minimum of 1 complete month with a cutoff date on the 30^th^/31^st^.
Thereafter, the report should cover 1 complete month with the cutoff
date on the 30^th^/31^st^. All reports are due to received by NASA on or
before the 10^th^ of the following month.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.11

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}:

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The Contractor's Monthly Progress Reports
shall be in a narrative form, brief, and informal in content.

The Monthly Progress Report shall include, but not limited to, the
following areas:

a.  A quantitative description of overall progress against the program
    schedule with reasons for significant differences

b.  Progress of individual major areas of the contract

c.  Progress of all major end items, description of the significant
    current discrepancies on problems, proposed corrective action and
    status

d.  A discussion of the work to be performed during the next monthly
    reporting period

e.  Configuration matrix of current hardware locations

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.11 -b

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: DPS Report, Engineering and Technical Data

7\. DESCRIPTION/USE: To provide technical information on the contractual
effort.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement

10\. SUBMISSION FREQUENCY: As required

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.11

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: The Contractor shall prepare technical reports
which describe the studies, analyses, and results of the specific
contractual efforts.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

3.  [CONTENTS]{.underline}: The individual report shall include, but not
    be limited to, such technical specialties as theoretical analyses,
    engineering verifications, current problems and proposed solutions,
    and conclusions and recommendations.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.11 -c

2\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: DPS Interface Control Document (ICD)

7\. DESCRIPTION/USE: Establish a means for defining and controlling
interface requirements.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement

10\. SUBMISSION FREQUENCY: As required with submittal due 30 days after
change or modification incorporated

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.11

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: This Data Requirements Description establishes
a requirement for preparation of ICD's which will define the physical
and functional interfaces between the SID and co-functioning equipment

13.2 [APPLICABLE DOCUMENTS]{.underline}:

3.  [CONTENTS]{.underline}: An ICD depicts physical and functional
    interface engineering requirements of a subsystem which affects the
    design control documents, delineating subsystems. These documents
    are used as design control documents, delineating subsystem
    interface engineering data coordination for purposes of:

```{=html}
<!-- -->
```
a.  establishing and maintaining compatibility between co-functioning
    subsystems

b.  controlling interface designs, thereby preventing changes to system
    requirements which could affect compatibility with co-functioning
    systems

c.  communicating design decisions and changes to participating
    activities

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by PCN's or complete reissue

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.11 -d

2\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: DPS Acceptance Data Packages

7\. DESCRIPTION/USE: To document original configuration of hardware and
track changes to configuration through repairs and modifications.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.11

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: The contractor shall maintain data packages
for all flight-like hardware (GPC's, DEU's, DU's)

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The data packages shall contain, as a
minimum:

As-Build Configuration documentation

Repair activity

Modification activity

Discrepancy Reports generated against the hardware

Acceptance test data

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by PCN's or complete reissue

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:**]{.smallcaps} Rev. 1 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.12-a**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:
**01/10/00**

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **TITLE**: Flight Software Test and Operations Plan - JSC-25392

7\. **DESCRIPTION/USE**: This document provides a single source
reference for information and procedures related to the Flight Software
Test and Operations Board and for providing T&O support at the various
support sites.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Assumption of an ongoing requirement

10\. **SUBMISSION FREQUENCY**: As required to incorporate changes in the
Test and Operation Board and support process.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.12

13\. **DATA PREPARATION INFORMATION**:

13.1 **[SCOPE]{.underline}**: This document defines how the Flight
Software Test and Operations (T&O) Board controls and how the software
contractor supports facility unique configuration changes of formally
released Orbiter avionics software used for vehicle checkout,
engineering evaluation, payload checkout, crew training, and flight
software verification testing.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**:

13.3 **[CONTENTS]{.underline}**: This document identifies a method for
accomplishing the T&O board and site support processes and also defines
the approval process for program notes and waivers. This document shall
include the following:

> a\. Purpose
>
> b\. Board authority and limitations
>
> c\. Configuration-control functions
>
> d\. Personnel support
>
> e\. Instructions for completing Software Approval Sheets, Maintenance
> Integration Plan change requests, program notes, and emergency
> facility patches.
>
> f\. General and facility unique T&O duties.

13.4 **[FORMAT]{.underline}**: Contractor shall conform to delivery
media formats and electronic data formats per DRD 1.1.4.1-e, Data
Management Plan, or per Contracting Officer approval

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated as
required by PCN's or complete reissue

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.12 -b

2\. DATA TYPE: Reserved 4. DATE REVISED:

5\. PAGE: 1/1

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.12 -c

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Mission Support Plan

7\. DESCRIPTION/USE: To describe the software contractor's approach to
providing mission operational support.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted annually

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.12

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Defines activities of the software contractor
in support of Space Shuttle operational missions, including preflight
preparation, flight support, and post-flight closeout of any questions
or anomalies.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The mission support plan will define the
procedures, communication protocol, personnel requirements, data
gathering, response time, facility requirements, console support,
contractor facility support and data processing capabilities used during
mission support.

The document will discuss in text and through flow charts the definitive
processes and capabilities provided by the contractor. The major areas
to be covered will include:

1.  Support team skills and functions in the Mission Evaluation Room
    (MER) and in the contractor's facility

2.  Coordination and communication procedures

3.  Data gathering requirements, capabilities and procedures

4.  Dump and other electronic data processing procedures

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by PCN's or complete reissue

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.12 -d

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Mission Operation Support Report

7\. DESCRIPTION/USE: To describe the contractor's participation,
achievement, and resources expended in real time support of each Shuttle
mission operations.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal within 10
working days of all Shuttle flight landings.

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.12

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Describes the contractor's participation,
achievement, and resources expended in support of mission operations, as
well as other applicable historical data. A single summary report will
be issued to cover all the mission operation support provided for each
mission.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: The Mission Operation Support Report shall
contain the periods of support for launch, the actual launch and landing
times, the Orbiter identifier and name, the mission objectives, major
mission milestones and a statement outlining the mission support team
activities during the mission. The report shall list in order all
subjects (i.e., CHITS, comments, etc.) that the mission support team was
involved with during the flight. A summary of the hardware and software
health will be provided at the end of the report.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.12 -e

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: DR Analysis and Status Reports

7\. DESCRIPTION/USE: To document an analysis recommendation for DR's
written against the Shuttle Primary Avionics Flight Software.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Product shall be submitted weekly as required

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.12

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}:

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: For each DR being dispositioned, a complete
analysis description containing:

1.  Technical details of the conditions and failures necessary to cause
    the problem

2.  Definition of the exact results and signature of the problem

3.  Detailed code analysis of the mechanism by which the software
    performs under the scenario conditions

4.  Description of all visible user effects

5.  Analysis of how the problem was missed in the inspection, review,
    development, and testing process

6.  Recommendations for closure of the DR and for process changes to
    avoid similar problems

> When requested, a listing of all open DR's by functional area. This
> listing shall include systems affected, probable severity and
> dispositions.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.:1.4.3.12-f

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Flight Software Program Notes and Waivers Document - JSC
19320

7\. DESCRIPTION/USE: This publication documents program anomalies to the
Primary Avionics Software System (PASS), the Backup Flight System (BFS),
the General Purpose Computer (GPC), the Self-Test Program (STP), and the
DEU Control Program (DCP) software.

8\. DISTRIBUTION: As specified in current Program Notes and Waivers
document -

JSC 19320

9\. INITIAL SUBMISSION: Two weeks prior to the first flight after
contract start

10\. SUBMISSION FREQUENCY: Updated for each Flight Software Operational
Increment and addenda published prior to each Shuttle Flight

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.12

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: This document specifically explains currently
known anomalies that have been approved by the Test and Operations (T&O)
Board and the Shuttle Avionics Software Control Board (SASCB).

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall consist (but is not all
inclusive) of currently known anomalies that have been approved by the
Test and Operations (T&O) Board and the Shuttle Avionics Software
Control Board (SASCB). The document shall include the following:

a.  Introduction

b.  Cross Reference Dictionary

c.  Program Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by PCN's or complete reissue

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.12 -g

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Program Notes and Waivers

7\. DESCRIPTION/USE: Used to update the PASS FSW Program Note and Waiver
document to describe software operations.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.12

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: There are three types of Program Notes:

Operations Note -- Describes an error discrepancy in a released version
of the FSW and provides user level descriptions of the visible affects.

User Note -- Describes the per requirements behavior of the FSW from a
user visibility perspective.

Waiver -- Documents a violation of FSW requirements. A waiver on the
requirement not met accompanies an Ops Note. A waiver may be issued
without a companion Ops Note.

13.2 [APPLICABLE DOCUMENTS]{.underline}: JSC 19320

13.3 [CONTENTS]{.underline}: Based on DR closure, the appropriate note
and/or waiver is produced, containing a description of the problem,
question, or idiosyncrasy along with an avoidance techniques or other
User information.

The Program Notes and Waivers are delivered to the T&O Board as
individual pages in the form approved by the T&O Board. They will be
published in a Program Notes and Waivers document after receiving Space
Shuttle community concurrence through the T&O Board.

13.4 [FORMAT]{.underline}: 8 ½ x 11 page size in electronic form using
the T&O board defined note templates.

13.5 [MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.12-h

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/2

6\. TITLE: PASS Flight Software User's Guide

7\. DESCRIPTION/USE: This document provides the information necessary to
operate and control the PASS FSW.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required with planned submittal at 2
months after CI for each OI system

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.12

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Describes how the flight software is loaded
into the flight computers, and how it is used. Provides the procedural
details of interfacing with the program inputs, display outputs, error
conditions and messages, and recovery options.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain a compilation
of information, procedures, and techniques necessary and useful for the
users to interface with the PASS FSW. Included shall be the following:

Introduction - This section will include general information about the
User's Guide (UG) such as the purpose, scope, applicable documents, and
Flight Software (FSW) deliverables.

System - This section of the UG will provide general information about
the Primary Avionics Software System (PASS). It will include a
description of the Mass Memory Unit, system initialization and overall
operation.

CRT Displays - This UG section will give a description of the
interactive user interface to the PASS. It will describe the hardware
used to provide this interface and explain the display interface
hierarchy and priorities. It will provide a description of the display
format and define the generic fields. The various type of displays and
their hierarchy will be discusses and a drawing and description of each
display available will be included.

Dedicated Displays - In this section of the UG, the definition of
dedicated displays will be provided. A description of the various
displays will be included with a drawing where appropriate. The meaning
of the information presented and when it is valid will be delineated.

Switches - This section of the UG will provide a list of all switch
functions which are required for the proper functioning of the PASS. The
list will be in tabular format and include information about the switch
such as the name, type, where located, when valid, frequency of sensing,
identifier, number of states and a definition.

Fault Annunciation and Messages - In this section of the UG, fault
detection will be discussed. The discussion will include types of faults
and their classification. A brief discussion of each class will be
included. A description of the format of each message that may be
annunciated will be provided.

Ground/GPC Interfaces - This section will describe the communications
between the vehicle and the ground control centers. Included will be
detailed discussions of the launch data bus interface, uplink
capabilities and downlist of selected data from the vehicle.

Data Analysis - This section will provide information on the data and
tools available to investigate and resolve issues that may arise while
working with the PASS.

Appendices - The UG will contain various appendices as deemed necessary
to support the main body of the document. This will include cross
reference listings, notes, information on tools and expanded message
explanations.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.1.4-a, Information
Management Plan, or per Contracting Officer approval

5.  [MAINTENANCE]{.underline}: Changes shall be incorporated as required
    by PCNs or complete reissue

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.12-i

2\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Mass Memory Patch

7\. DESCRIPTION/USE: The Mass Memory Patch is used to modify the Flight
Software without altering the AP101 memory maps.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required

11\. REMARKS:

12\. INTERRELATIONSHIP: 1.4.3.10, 1.4.3.12

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: Provides the means of delivering modifications
of the flight software to an end user. The development and delivery of
the patch requires a NASA approved Flight Software CR or DR.

13.2 [APPLICABLE DOCUMENTS]{.underline}: JSC 08338

13.3 [CONTENTS]{.underline}: The patch contents and format are defined
in the MMU Integration Plan (MIP)- JSC 08338 (DRD 1.4.3.10-d)

13.4 [FORMAT]{.underline}: The patch format is controlled through the
Memory Integration Plan (MIP), JSC document number JSC 08338. The patch
is delivered to NASA in an electronic dataset on the SDF or SPF.

[MAINTENANCE]{.underline}: None required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-a

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Software Development Plan (SDP) for the Multifunction
    Electronic Display Subsystem (MEDS)

```{=html}
<!-- -->
```
7.  DESCRIPTION/USE: To provide NASA with visibility into the software
    maintenance process.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: 90 days after contract start.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} This document describes the overall plan for
the maintenance of the MEDS software.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

1.  Scope

2.  Referenced Documents

3.  Software Development Plan

4.  Software Engineering

5.  Verification Testing

6.  Software Product Evaluations

7.  Software Configuration Management

8.  Other Software Development Functions

9.  Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-b

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: MEDS Software Quality Report

7\. DESCRIPTION/USE: To provide management and customer visibility into
the status of the software quality for the MEDS software program.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: As required.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative, with planned submittal semi-annually - no later than 21
days following close of reporting period.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} The Software Quality Report covers activities
occurring during a period of six months (January through June and July
through December).

13.2 [APPLICABLE DOCUMENTS]{.underline}: none

13.3 [CONTENTS:]{.underline} The report shall include:

> a\. Part 1 - Summary of Software Quality Assurance (SQA) activities
> during the reporting period
>
> These activities include:

1.  Software procedural and method enhancements

2.  Quality and configuration audits

3.  Product release verifications

4.  Program change control

5.  SQA quality metrics summary

> b\. Part 2 - Summary of quality metrics for the reporting period.
> These metrics trend analysis charts with information on early
> detection percentages and process and product error rates for software
> increments. Corrective actions to the software process are included
> for the post Test Readiness Review (TRR) and post Software Acceptance
> Review (SAR) product errors. Previous reported corrective actions are
> tracked until closure.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-c

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Software Readiness Review (SRR) Briefing

7\. DESCRIPTION/USE: To provide a description of the development and
verification of the MEDS software to assure the customer that the
software was developed per the requirements and is ready to support
Shuttle missions.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: As required.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative, with planned submittal approximately 1 month prior to
flight.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} The MEDS SRR briefing describes the MEDS
software activities since SAR and states that the software is ready to
support the Shuttle mission.

13.2 [APPLICABLE DOCUMENTS]{.underline}: none

13.3 [CONTENTS:]{.underline} This briefing package shall contain:

1.  Schedule

2.  Development activity

3.  Verification activity

4.  Notes and Waivers

5.  Open Items

6.  MEDS software tools

7.  Conclusion

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-d

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: MEDS Software Change Authorization

7\. DESCRIPTION/USE: Products used to propose detailed changes to the
MEDS Flight Software. Consists of:

-   MEDS Flight Software Change Proposal (FCP), used to obtain
    preliminary customer concurrence for development of software change
    requests

-   MEDS Software Change Request (SCR), used to propose changes to the
    MEDS flight software requirements

-   MEDS Change Request (CR) Risk Assessment Analysis Report, used to
    assess the risk of changing the existing code to implement the
    requested change

    8\. DISTRIBUTION: Per Contracting Officer's Letter

    9\. INITIAL SUBMISSION: As required.

    10\. SUBMISSION FREQUENCY: As required.

    11\. REMARKS:

    12\. INTERRELATIONSHIP:

    13\. DATA PREPARATION INFORMATION:

    13.1 [SCOPE:]{.underline} Includes products required to authorize
    MEDS software requirements changes approved by the customer.

    13.2 [APPLICABLE DOCUMENTS]{.underline}: none

    13.3 [CONTENTS:]{.underline} Products used to propose detailed
    changes to the MEDS Flight Software. Consists of:

-   MEDS Flight Software Change Proposal (FCP), used to obtain
    preliminary customer concurrence for development of software change
    requests

-   MEDS Software Change Request (SCR), used to propose changes to the
    MEDS flight software requirements

-   MEDS Change Request (CR) Risk Assessment Analysis Report, used to
    assess the risk of changing the existing code to implement the
    requested change

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-e

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Hardware Dependent Software Segment Specification (HDSSS) for
    the Multifunction Electronic Display Subsystem (MEDS)

7\. DESCRIPTION/USE: To provide the functional requirements for the
Hardware Dependent Software (HDS).

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative. Planned submittal should be scheduled approximately 14
days prior to the SAR.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} This document specifies functional
software/firmware requirements for the HDS. It also specifies the HDS
interface requirements with the MEDS application software.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS:]{.underline} This document shall contain:

1.  Scope

2.  Applicable Documents

3.  Segment Requirements

4.  Quality Assurance Provisions

5.  Preparation for Delivery

6.  Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-f

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: General Purpose Computer (GPC)/Integrated Display Processor
    (IDP) Interface Control Document (ICD)

```{=html}
<!-- -->
```
7.  DESCRIPTION/USE: To describe the MEDS interface to the Space Shuttle
    GPC and the appropriate Orbiter panel switches and keyboards with
    the IDP to perform the Man-Machine Crew Interface function of the
    Space Shuttle Orbiter.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: This document addresses the interface
requirements between the IDP and the GPC and delineated Orbiter panel
switches and the Orbiter keyboard.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

1.  Introduction

2.  Applicable Documents

3.  Requirements

4.  Acronyms and Abbreviations

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-j

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Test Readiness Review (TRR) Briefing

7\. DESCRIPTION/USE: To provide a description of the development
completeness and verification readiness of the MEDS software to assure
the customer that the software was developed per the requirements and is
ready for verification testing.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: As required.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative. Planned submittals should be scheduled approximately 1
day prior to the start of verification testing.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} The MEDS TRR briefing describes the
development work completed, the verification work to be performed, and
confirms that the software is ready for verification testing.

13.2 [APPLICABLE DOCUMENTS]{.underline}: none

13.3 [CONTENTS:]{.underline} This briefing package shall contain:

1.  Development activities

2.  Verification activities

3.  Open Items

4.  Conclusion

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-k

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Software Requirements Specifications (SRS) for the
    Multifunction Electronic Display Subsystem (MEDS)

```{=html}
<!-- -->
```
7.  DESCRIPTION/USE: To document the engineering requirements imposed on
    the software.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative. Planned submittals should be scheduled approximately 14
days prior to the SAR.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} These documents establish the requirements for
the MEDS software.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

a)  Scope

b)  Applicable Documents

c)  Engineering Requirements

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

5.  MTS

6.  Portable Loader Software

```{=html}
<!-- -->
```
d)  Verification Requirements

e)  Preparation of Delivery

f)  Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-l

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Interface Requirements/Design Document (IRDD) for the
    Multifunction Display Unit Function (MDUF) of the Multifunction
    Electronic Display Subsystem (MEDS)

```{=html}
<!-- -->
```
7.  DESCRIPTION/USE: To establish the interface requirements and design
    for the Multifunction Display Unit Function (MDUF) which includes
    the MDUF software and MDUF firmware.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative. Planned submittals should be scheduled approximately 14
days prior to the MDUF SAR.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: This document establishes the interface
requirements and design for the Multifunction Display Unit Function
(MDUF) which includes the MDUF software and MDUF firmware.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS:]{.underline} This document shall contain:

1.  Scope

2.  Referenced Documents

3.  Interface Design

4.  Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-m

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Interface Requirements Specification (IRS) for the
    Analog-to-Digital Converter (ADC) of the Multifunction Electronics
    Display Subsystem (MEDS)

7\. DESCRIPTION/USE: To define the interface requirements for the ADC
firmware.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative. Planned submittals should be scheduled approximately 14
days prior to the ADC Firmware SAR.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: This specification provides the interface
requirements for the ADC firmware.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

1.  Scope

2.  Applicable Documents

3.  Interface Specification

4.  Quality Assurance

5.  Preparation for Delivery

6.  Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting

Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-n

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Interface Design Document (IDD) for the Analog-to-Digital
    Converter (ADC) of the Multifunction Electronic Display Subsystem
    (MEDS).

7\. DESCRIPTION/USE: To describe the interface design for the ADC
firmware.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative. Planned submittals should be scheduled approximately 60
days after the ADC Firmware SAR.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: This document describes the interface design
of the ADC firmware.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

1.  Scope

2.  Applicable Documents

3.  Interface Design

4.  Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-o

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Software Design Documents (SDD) for the Multifunction
    Electronic Display Subsystem (MEDS)

7\. DESCRIPTION/USE: To establish the software design of the MEDS
software.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative. Planned submittals should be scheduled approximately 60
days after the SAR.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: These documents establish the software design
of the MEDS software.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

a)  Scope

b)  Referenced Documents

c)  Preliminary Design

d)  Detailed Design

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

5.  MTS

```{=html}
<!-- -->
```
e)  CSCI Data

f)  CSCI Data Files

g)  Requirements Traceability

h)  Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-p

3\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Software Programmers Manuals for the Multifunction Electronic
Display Subsystem (MEDS)

7\. DESCRIPTION/USE: To aid in the modifying and testing of the MEDS
software.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: As requested.

10\. SUBMISSION FREQUENCY: Products shall be submitted as requested by
the Contracting Officer's Technical Representative (COTR), or designated
representative.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: These documents describe the organization and
techniques used to modify and test changes to the MEDS software.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

a)  Scope

b)  Referenced Documents

c)  Software Programming Environment

d)  Programming Information

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

```{=html}
<!-- -->
```
e)  Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-q

3\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Software Development Files (SDF) for the Multifunction
Electronic Display Subsystem (MEDS).

7\. DESCRIPTION/USE:

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: As requested.

10\. SUBMISSION FREQUENCY: As requested.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}:

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

a.  Design considerations and constraints

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

5.  Portable Loader Software

```{=html}
<!-- -->
```
b)  Design documentation and data

c)  Schedule and status information

d)  Test requirements and responsibilities

e)  Test cases, procedures, and results

13.4 [FORMAT]{.underline}: Contractor format.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated informally
as applicable.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-r

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: MEDS Release Authorization Signature Sheet (RASS)

7\. DESCRIPTION/USE: The Release Authorization Signature Sheet (RASS)
provides authorization for the MEDS flight software to be released.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: As required.

10\. SUBMISSION FREQUENCY: As required for each MEDS flight software
increment.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} The Release Authorization Signature Sheet
(RASS) provides authorization for the MEDS flight software to be
released. This sheet must be approved by the chairman of the SASCB prior
to the software being released.

13.2 [APPLICABLE DOCUMENTS]{.underline}: none

13.3 [CONTENTS:]{.underline} The RASS shall contain:

a)  Product identification

b)  Purpose and description

c)  List of facilities authorized to use the software

d)  Any restrictions place on the release

e)  Description of the products contained in the release

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-s

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: Software Test Description (STD) for the Multifunction
    Electronic Display Subsystem (MEDS)

7\. DESCRIPTION/USE: To establish the test cases and procedures to be
used for verification of the MEDS software releases.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative, with baseline prior to the Test Readiness Review (TRR)
and delivery no later than 2 weeks prior to the SAR.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: These documents establish the test cases and
test procedures for the MEDS software which are necessary to perform
Verification tests.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

a)  Scope

b)  Referenced Documents

c)  Verification Test Preparations

d)  Verification Test Descriptions

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

```{=html}
<!-- -->
```
e.  Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-t

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Software Test Reports (STR) for the Multifunction Electronic
Display Subsystem (MEDS)

7.  DESCRIPTION/USE: To provide documentation of the test results of the
    verification tests performed on the MEDS software.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
    the Contracting Officer's Technical Representative (COTR), or
    designated representative, with planned delivery no latter than one
    week prior to the SAR.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: This document provides a record of the
verification tests performed on the MEDS software.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

a)  Scope

b)  Referenced Documents

c)  Overview of Test Results

d)  Detailed Test Results

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software/UDI

4.  ADCF

```{=html}
<!-- -->
```
e)  Test Log

f)  Notes

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-u

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: MEDS Software Version Increment Deliverables

7\. DESCRIPTION/USE: To provide MEDS Flight Software and support tools
utilized to fly and support Shuttle missions.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative, with planned delivery at the SAR.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} The MEDS Software Version Increment
deliverables consist of the files necessary for the MEDS flight software
and support tools as utilized to fly and support shuttle missions.

13.2 [APPLICABLE DOCUMENTS]{.underline}: none

13.3 [CONTENTS:]{.underline} The MEDS Software Version Increment
deliverables include:

a)  MEDS flight software files

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software

4.  MDU UDI

5.  ADCF

```{=html}
<!-- -->
```
b)  MEDS support software files

```{=html}
<!-- -->
```
1.  IDP Support Software

2.  MTS

3.  MTS Support Software

4.  MDUF FQT

5.  MOM

6.  AFTS

7.  Portable Loader Software

```{=html}
<!-- -->
```
c)  Flight software documentation

d)  Support Tools documentation

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-v

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/2

6.  TITLE: Version Description Documents for the Multifunction
    Electronic Display Subsystem (MEDS)

```{=html}
<!-- -->
```
7.  DESCRIPTION/USE: To provide the configuration data required to
    support software delivery to using sites.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative, with planned submittal with each MEDS software
deliverable.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: These documents describe the configuration
status accounting that identifies the as-built configuration of the
software.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

a)  Scope: identifies this document and its relationship to the system.

b)  Referenced Documents: identifies all documents referenced in this
    document.

c)  Version Description: describes the contents, revision, date,
    delivery instructions, media description, changes, and installation
    instructions.

```{=html}
<!-- -->
```
1.  IDP Software

2.  IDP-BSL

3.  MDUF Software

4.  MDU UDI

5.  ADCF

6.  MTS

7.  MTS Support Software

8.  IDP Support Software

9.  MDUF FQT

10. MOM

11. AFTS

12. Portable Loader Software

```{=html}
<!-- -->
```
d)  Notes: contains general information that aids in understanding this
    document, including a list of acronyms used within this document.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-w

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: Software Acceptance Review (SAR) Briefing

7\. DESCRIPTION/USE: To provide a description of the development and
verification of the MEDS software to assure the customer that the
software was developed per the requirements and is ready to support
Shuttle missions.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: As required.

10\. SUBMISSION FREQUENCY: Products shall be submitted as authorized by
the Contracting Officer's Technical Representative (COTR), or designated
representative, with planned submittal at the SAR.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} The MEDS SAR briefing describes the
development process, the verification process and results, and
verification that the software is ready to support Shuttle missions.

13.2 [APPLICABLE DOCUMENTS]{.underline}: none

13.3 [CONTENTS:]{.underline} This briefing package shall cover:

1.  Schedule

2.  Notes and Waivers

3.  Verification

4.  Open Items

5.  Performance Metrics

6.  Quality Metrics

7.  MEDS software tools

8.  Conclusion

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-x

3\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: User's Manual for the Hardware Dependent Executive (HDX)
Support Utilities of the Multifunction Electronic Display Subsystem
(MEDS)

7.  DESCRIPTION/USE: To describe the user interface and execution of the
    HDX Support Utilities (HSU).

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: As requested.

10\. SUBMISSION FREQUENCY: As requested.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: This document contains descriptions of the
user interface and execution of the HSU in terms of its function,
performance, and external interface capabilities.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain:

1.  Introduction

2.  General Description

3.  Utility Descriptions

4.  Notes

5.  Index

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-y

3\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: MDU Object Manipulator (MOM) User's Guide

7.  DESCRIPTION/USE: To describe the user interface and execution of the
    MOM.

8\. DISTRIBUTION: Per Contracting Officer's letter

9\. INITIAL SUBMISSION: As requested.

10\. SUBMISSION FREQUENCY: Products shall be submitted as requested by
the Contracting Officer's Technical Representative (COTR), or designated
representative.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE]{.underline}: This document contains descriptions of the
user interface, commands, and execution of the MOM in terms of its
function, performance, and external interface capabilities.

13.2 [APPLICABLE DOCUMENTS]{.underline}:

13.3 [CONTENTS]{.underline}: This document shall contain descriptions
of:

1.  Startup

2.  Keyboard Inputs

3.  Script Files

4.  Data Manipulation and Flow Control

5.  Graphics Commands

6.  General Notes on Graphics Templates

7.  MOM Editor

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan, or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.13-z

3\. DATA TYPE: 4 4. DATE REVISED:

5\. PAGE: 1/1

6.  TITLE: MEDS Software Standards and Procedures Manual (SSPM)

7\. DESCRIPTION/USE: To document MEDS tasks and duties, including
procedures, checklists, and general information for all areas of the
MEDS Project.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: As requested.

10\. SUBMISSION FREQUENCY: Products shall be submitted as requested by
the Contracting Officer's Technical Representative (COTR), or designated
representative.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} The SSPM contains standard and procedures used
during the development of all Computer Software Configuration Items
(CSCIs) developed.

13.2 [APPLICABLE DOCUMENTS]{.underline}: none

13.3 [CONTENTS:]{.underline} The SSPM contains procedures, checklists,
forms, and general information used to develop CSCIs for the MEDS.

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: Changes shall be incorporated as
required by complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.14-a

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: MEDS Software Discrepancy Resolution Authorization

7\. DESCRIPTION/USE: Consists of:

-   MEDS Software Discrepancy Report (DR), used to document MEDS
    software issues

-   MEDS Software Discrepancy Report (DR) Management Form, used to
    provide the rationale for selecting the appropriate disposition on a
    DR.

-   As required MEDS Waiver, used to describe anomalous behavior of the
    MEDS flight software that is in violation of the software
    requirements but will be flown anyway

-   As required MEDS Note, used to describe anomalous idiosyncrasies of
    the MEDS flight software observable by the crew, by the ground
    flight controllers, or from the analysis of data dumped during a
    flight.

    8\. DISTRIBUTION: Per Contracting Officer's Letter

    9\. INITIAL SUBMISSION: As required.

    10\. SUBMISSION FREQUENCY: As required.

    11\. REMARKS:

    12\. INTERRELATIONSHIP:

    13\. DATA PREPARATION INFORMATION:

    13.1 [SCOPE:]{.underline} Includes products used by the Shuttle
    Avionics Software Control Board (SASCB) to authorize discrepancy
    resolutions against the MEDS flight software and critical tools.

    13.2 [APPLICABLE DOCUMENTS]{.underline}: none.

    13.3 [CONTENTS:]{.underline}

-   MEDS Software Discrepancy Report (DR)

-   MEDS Software Discrepancy Report (DR) Management Form

-   MEDS Waiver

-   MEDS Note

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

13.5 [MAINTENANCE]{.underline}: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.14-b

3\. DATA TYPE: 3 4. DATE REVISED:

5\. PAGE: 1/1

6\. TITLE: MEDS Software Interim Release Deliverables

7\. DESCRIPTION/USE: To formally release MEDS software developed to
satisfy testing, training, and mission objectives in the laboratory
environment.

8\. DISTRIBUTION: Per Contracting Officer's Letter

9\. INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required.

11\. REMARKS:

12\. INTERRELATIONSHIP:

13\. DATA PREPARATION INFORMATION:

13.1 [SCOPE:]{.underline} The MEDS Software Interim Release deliverables
consist of the files necessary for the use of the interim release for
testing, training, and mission objectives in the laboratory environment.

13.2 [APPLICABLE DOCUMENTS]{.underline}: none

13.3 [CONTENTS:]{.underline} The MEDS Software Interim Release
deliverables include:

> a\) MEDS flight software files

1.  IDP Software

2.  MDUF Software

3.  Portable Loader Software

b\) Version Description Document

13.4 [FORMAT]{.underline}: Contractor shall conform to delivery media
formats and electronic data formats per DRD 1.1.4.1-a, Information
Management Plan or per Contracting Officer approval.

[MAINTENANCE]{.underline}: None required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. DPD NO.: 2. DRD NO.: 1.4.3.15-a

3\. DATA TYPE: 3 4. PAGE REVISED:

> 5\. PAGE: 1/2

6.  TITLE: PC-Decom Software Delivery Requirements

```{=html}
<!-- -->
```
7.  DESCRIPTION/USE: Describes the expected deliveries and schedules for
    PC-Decom software deliverables.

```{=html}
<!-- -->
```
8.  DISTRIBUTION: PER CONTRACTING OFFICER'S LETTER

```{=html}
<!-- -->
```
9.  INITIAL SUBMISSION: Assumption of an ongoing requirement; no break
    in existing submission schedule. Transfer of responsibility to take
    place 10/1/99.

```{=html}
<!-- -->
```
10. SUBMISSION FREQUENCY: Submission of products shall be divided into
    the following categories:

```{=html}
<!-- -->
```
A.  System Releases: Release schedules will be specified in and approved
    by the POCCB.

B.  Configurables: First use of PC-Decom software following release of
    FSW Operational Increment as well as required by changes in downlist
    specifications after the OI is released.

C.  Support Program Releases: Release schedules will be specified in and
    approved by the POCCB.

D.  Customer Support: As required.

```{=html}
<!-- -->
```
11. REMARKS: N/A

12. INTERRELATIONSHIP: N/A

13. DATA PREPARATION INFORMATION: N/A

```{=html}
<!-- -->
```
1.  [SCOPE]{.underline}: Covers all PC-Decom software development and
    maintenance

```{=html}
<!-- -->
```
2.  [APPLICABLE DOCUMENTS]{.underline}: Payload and General Support
    Computer

> (PGSC) Interface Definition Document
>
> Shuttle Data Integration Plan (DIP), JSC-18206,
>
> Vol. III

# 

# DRD Continuation Sheet

**TITLE**: PC-Decom Software Delivery Requirements **DRD NO.**:
1.4.3.15-a

**DATA TYPE**: 3 **PAGE:** 2/2

3.  [DATA/PROGRAM CONTENTS]{.underline}:

```{=html}
<!-- -->
```
A.  System Releases: New versions of PC-Decom software delivery contents
    and delivery dates shall be approved at the POCCB. Documentation
    delivered shall be consistent with expectations of Original
    Equipment Manufacturer (OEM) program deliveries.

B.  Configurables : Delivery contents and delivery dates shall coincide
    with requirements for use configurables on first PGSC training load.
    Contents for this delivery shall only consist of data (no program
    code).

C.  Support Program Releases: New or re-released support program
    contents and delivery dates shall be approved at the POCCB.
    Documentation delivered shall be consistent with expectations of
    Original Equipment Manufacturer (OEM) program deliveries.

D.  Customer Support: As required.

```{=html}
<!-- -->
```
4.  [FORMAT]{.underline}: Contractor shall conform to delivery media
    formats and electronic data formats per DRD 1.1.4.1-a, Information
    Management Plan, or per Contracting Officer approval.

```{=html}
<!-- -->
```
5.  [MAINTENANCE]{.underline}: As required to support discrepancies as
    documented by the POCCB. Changes shall be incorporated as required
    by PCNs, POCCB, or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.3.16-a**

3\. **[DATA TYPE]{.smallcaps}**: 2 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Data Reconfiguration Deliverables

7\. **[DESCRIPTION/USE]{.smallcaps}**: To reconfigure various Shuttle
facilities and flight software for each mission.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** N/A

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: As required for each flight

11\. **[REMARKS]{.smallcaps}**: Data content for the reconfiguration
database is controlled by Data Change Request (DCR\'s) approved by NASA.
Deliverable products are sent to external organizations for each
mission.

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.3.16

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[[SCOPE]{.underline}]{.smallcaps}**:

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**

NSTS-21000-A04 *Standard Integration Plan Annex 4, Command and Data
(C&D) Requirements*

NSTS-10784 *Space Shuttle Telemetered and Recorded Data Format
Requirements*

JSC-18206 *Shuttle Data Integration Plan* Volumes I and III

JSC-20201 *Operational Shuttle Data Reconfiguration*

JSC-22438 *STS Calibration Handling Handbook*

Vol I *Plans and Procedures*

Vol II *Space Transportation Automated Reconfiguration System (STARS)
Data Collection and Reconfiguration Procedures*

Vol III *Measurement and Stimuli (MAST) Data Collection and Integration
User\'s Guide*

Vol IV *Mission Control Center (MCC) Automated Reconfiguration System
(MARS) Data Collection and Integrated Procedures*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: Three categories to be
included:

a\. Payload requirements support (ref. NSTS-2100-A04) C&D annex and
related payload products, i.e., payload dataset.

b\. Telemetry descriptor products (ref. JSC-18206) used to reconfigure
ground telemetry equipment.

c\. Shuttle data products (ref. JSC-18206), Shuttle data tape, and
Master Measurements list and other related special reports needed to
reconfigure ground support and test facilities as well as postflight
data reduction facilities.

All deliverable products must be accompanied with appropriate
descriptions and release authorization as shown in the Operational
Shuttle Data Reconfiguration Plan, JSC-20201.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required, by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: [**ISSUE:** BASIC]{.smallcaps} 2. **[DRD
NO.]{.smallcaps}**: **1.4.3.16-b**

3\. **[DATA TYPE]{.smallcaps}**: 4 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **TITLE**: Reconfiguration Tools Requirements Documents

7\. **DESCRIPTION/USE**: Defines the requirements and specifications for
the Reconfiguration Tools used to perform the Shuttle Reconfiguration
processes.

8\. **DISTRIBUTION**: Per Contracting Officer's Letter

9\. **INITIAL SUBMISSION**: Assumption of an ongoing requirement; no
break in existing submission schedule.

10\. **SUBMISSION FREQUENCY**: As required with approved changes.

11\. **REMARKS**:

12\. **INTERRELATIONSHIP**: 1.4.3.16

13. **DATA PREPARATION INFORMATION**:

14. 

13.1 **[SCOPE]{.underline}**: The requirements documents and
specifications for the Reconfiguration Tools used for the Shuttle
Reconfiguration processes.

13.2 **[APPLICABLE DOCUMENTS]{.underline}**: Support Requests (SRs)
authorizing changes to these requirements.

3.  **[CONTENTS]{.underline}**: The following documents are included:

```{=html}
<!-- -->
```
a.  STSOC-RQ-601082 Software Production Facility Operation Planning
    Document Vol. VII Book 2

b.  STSOC-RQ-601101 MAST II Level B/C Requirements

c.  SFOC-FL2058 Level-C Table Generator Requirements

d.  SFOC-FL2056 Level C FSR Report Requirements

e.  STSOC-SP-601814 Detailed Requirement Document for Annex Table
    Generator

f.  SFOC-FL0311 Level B/C Requirements: Orbiter Interface Unit Converter
    ISSA/SSP Data Conversion Process Volume 2

g.  SFOC-FL0312 Level B/C Requirements: Orbiter Interface Unit Converter
    ISSA/SSP Data Conversion Process Volume 1

13.4 **[FORMAT]{.underline}**: Contractor shall conform to delivery
media formats and electronic data formats per DRD 1.1.4.1-e, Data
Management Plan, or per Contracting Officer approval.

13.5 **[MAINTENANCE]{.underline}**: Changes shall be incorporated as
required.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO:]{.smallcaps}** **1.4.3.17-a**

3\. **[DATA TYPE:]{.smallcaps}** 2/3/4 4. **[DATE
REVISED:]{.smallcaps}**

5\. **[PAGE:]{.smallcaps}** 1/2

6\. **[TITLE:]{.smallcaps}** SAIL Product Handbook and Product Glossary

7\. **[DESCRIPTION/USE:]{.smallcaps}** To define the content and
delivery requirements of each SAIL

test and documentation product.

8\. **[DISTRIBUTION:]{.smallcaps}** Per Contracting Officer's letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** 30 Days after Authority to
Proceed (ATP)

10\. **[SUBMISSION FREQUENCY:]{.smallcaps}** Annual review with NASA and
updates as agreed to

to keep documentation current with procedures, products, and customer
list.

Products and deliverables will be in consonance with the existing
schedules.

11\. **[REMARKS:]{.smallcaps}**

12\. **[INTERRELATIONSHIP:]{.smallcaps}** SOW 1.4.3.17

13\. **[DATA PREPARATION INFORMATION:]{.smallcaps}**

13.1 **[SCOPE:]{.smallcaps}** The SAIL Product Handbook product glossary
provides detailed product

definitions including use, types, government furnished data, and
delivery

requirements for each SAIL product and deliverable

13.2 **[APPLICABLE DOCUMENTS]{.smallcaps}**:

JSC 08663, Volume 1 SAIL Project Plan

JSC 08663, Volume 2 SAIL Configuration Management Plan

JSC 08663, Volume 3 SAIL Operations Management Plan

JSC 08663, Volume 4 SAIL Safety, Reliability and Quality Assurance
Support

Plan

JSC 0866D, Volume 5 SAIL Integrated Logistics Support Plan

SOC-PN-001120B SAIL Five Year Plan

RSOC86-0130 SAIL Flight Hardware/Software Mission Report

RSOC86-0123 SAIL MMES Configuration Definition Document

SAIL Flight System/Laboratory Upgrade Requirements & Schedules

SAIL Test Schedules

SAIL Test Requests

SAIL Process Flows

SAIL Technical and Metrics Review

SAIL Configuration Control Panel Minutes

SAIL Software/Math Model Requirements

SAIL Standard Operating Procedures

SAIL Technical Reports

SAIL Data Products

SAIL Accomplishments Data Base

SAIL Test Control Documentation

SAIL Test and Implementation Plans

SAIL Automated Information Systems Security Documents

DRD Continuation Sheet

**[TITLE]{.smallcaps}**: SAIL Product Handbook and Product Glossary
**[DRD NO.]{.smallcaps}**: **1.4.3.17-a**

**[DATA TYPE]{.smallcaps}**: 2/3/4 **[PAGE]{.smallcaps}**: 2/2

13.3 **[CONTENTS:]{.smallcaps}** The SAIL product handbook and glossary
shall include the

functional areas of SAIL flight system and laboratory, logistics at JSC
SAIL, other

NASA field centers, data/procedures/processes pertaining to
use/operation and

upkeep/maintenance of laboratory elements and flight system hardware and

software, safety, reliability, etc.

DATA TYPE 2 deliverables shall include the following :

a\. The 5 NASA SAIL Management volumes -

Volume 1 SAIL Project Plan

Volume 2 SAIL Configuration Management Plan

Volume 3 SAIL Operations Management Plan

Volume 4 SAIL Safety, Reliability and Quality Assurance Support Plan

Volume 5 SAIL Integrated Logistics Support Plan

b\. The SAIL Joint Test Schedule which identifies major milestones,
events, and schedules of the SAIL activities to support the Shuttle
program.

c\. The SAIL 5 Year Plan which defines the laboratory element upgrade
plan for replacement of worn/aged equipment replacements, new or
upgraded equipment or capability developments, etc.

d\. The SAIL Mission Support Plan and the SAIL Flight Hardware/Software
Mission Report.

e\. The SAIL Test Requests

f\. SAIL Test and Implementation Plans

g\. SAIL Laboratory/Flight System Upgrade Requirements & Schedules

h\. SAIL Automatic Information Systems Security Documents

DATA TYPE 3 deliverables shall include the following :

a\. SAIL Technical and Metric Reviews.

b\. SAIL Software and Math Model Requirements

c\. SAIL Standard Operating Procedures

d\. SAIL Detail and 72 hour test schedules.

e\. SAIL Accomplishments Data Base

DATA TYPE 4 deliverable shall include the following :

a\. SAIL Process Flows

b\. SAIL Technical Reports

c\. SAIL Data Products

d\. SAIL Configuration Control Panel Meeting Minutes

e\. SAIL Test Control Documentation such as Test Preparation Sheets,
Test and Checkout Procedures,

Interim Discrepancy Reports, Discrepancy Reports, Test Constraints
Reviews, etc.

13.4 **[FORMAT:]{.smallcaps}** Contractor format is acceptable

13.5 **[MAINTENANCE:]{.smallcaps}** Changes shall be incorporated by
page revision or total

resubmittal as applicable.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.9.1**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Extravehicular Mobility Unit (EMU) Flight
Data Book

7\. **[DESCRIPTION/USE]{.smallcaps}**: To present the results of EMU
testing used for mission support.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** First mission after contract
award

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Each mission

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**:

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The EMU Flight Data Book contains the
results of all preflight testing in support of each mission.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The EMU Flight Data Book
shall contain:

a\. Flight hardware list: includes as-built and as-designed
configuration and list of serial numbers for all components (to the
level of contract item number and/or reparable component serial number).

b\. PIA data for each PLSS: If reduced pre-installation acceptance
testing was performed, also include chamber run data.

c\. ETA chamber data (if not included above).

d\. V1103 data: This section may be delivered as a supplement no later
than Launch minus 2 days, if Launch minus 1 week time frame cannot be
met.

e\. CCC information: packing as well as consumable prediction rate based
on conversion percentage and use rate. Processing information: Delta P
and leak rate.

f\. Battery information: charging as well as consumable prediction rate
based on use rate.

g\. SOP servicing data: data on regulator performance as well as
transducer performance.

h\. SSA data inputs - For planned Extravehicular Activity (EVA) flights
only: brief sizing summary backup SEMU \[LTA and other sized Contract
End Items (CEI\'s) if flown\] describing which CM the item is sized for
and what is required to make it wearable by other EVA CM, where
applicable.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
[**DRD NO**.]{.smallcaps}: **1.4.9.1-a**

3\. **[DATA TYPE]{.smallcaps}**: 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/2

6\. **[TITLE]{.smallcaps}**: Drawings, Engineering and Associated Lists

7\. **[DESCRIPTION/USE]{.smallcaps}**: To establish the requirements for
the maintenance, revision, and/or preparation of all drawings and
associated lists by a contractor.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer's letter

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Ongoing requirement

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Assumption of an on-going
requirement; no break in existing submission schedule.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.9.1

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The contractor shall
maintain a complete set of engineering drawings in accordance with
MIL-D-1000 and MIL-STD-100, and as contractually required and specified
herein for the end item(s) covered by this contract. The Government
shall furnish to the contractor at the start of the contract a set of
drawings for all end items as they exist at that time. Subsequent
preparation, changes, and format shall be, as a minimum, as defined in
the following paragraphs.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**: MIL-STD-100,
MIL-D-1000

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**:

I.  [Drawing Revisions]{.underline}: When the contractor determines
    revisions are required, the contractor shall immediately prepare an
    engineering change request describing the changes required. Changes
    that effect form, fit, or function shall be forwarded to the
    procuring activity for approval. If needed, in order to fully
    describe the change, a marked-up, non-reproducible drawing or sketch
    shall also be forwarded. After approval, the contractor shall, when
    required, prepare any new or revised drawing that may be required or
    which results from engineering or manufacturing process changes.
    This also applies to those changes that are not covered by
    Engineering Change Proposal (ECP) action.

> [Note]{.underline}
>
> When revisions are not required, the contractor shall provide a
> certification that no deviations have been made from, or modifications
> made to, the engineering drawings furnished to the contractor. If
> illustrated parts breakdown, technical manuals, or technical
> directives are changed to reflect changes that affect engineering
> drawings, the above paragraph applies.

II. [Drawing Preparation]{.underline}: The contractor shall prepare
    original drawings as required to document minor design changes,
    replacement of obsolete parts, and/or additional flight and
    flight-type equipment which the contractor provides during the
    course of this contract.

```{=html}
<!-- -->
```
III. [Drawing Number Assignment]{.underline}: Each contractor drawing
     shall be assigned a number by the contractor or vendor. A number
     once assigned shall never be reused for another assignment, but
     shall be canceled when no longer required.

```{=html}
<!-- -->
```
IV. [Application Information]{.underline}: Application and next higher
    assembly information shall be specified on all drawings in an
    appropriate block near or adjacent to the title block. Such
    information may, however, be recorded in list form. When in list
    form, it shall be cross-referenced to the applicable drawing. Top
    assembly drawings shall indicate "AS ALLOCATED" in the "NEXT
    ASSEMBLY."

> V. The effectivity of drawings and associated lists for vehicle(s),
> stages, and other hardware shall be indicated as required.

VI. [Standard Commercial Parts]{.underline}: Parts not covered by
    Military Standards or Industrial Association Standards are used by
    the contractor exactly as procured from the supplier or
    manufacturer, drawings need not be prepared for these parts provided
    they are described on the assembly drawing in concise and sufficient
    detail to enable the Government to identify and procure from
    commercial sources. When the end item is not described in accordance
    with this criteria, reference shall be made tot he end item, the
    supplier or manufacturer's name, address, part number, and catalog
    number on the drawings, if the catalog defines the part in
    sufficient detail to enable the Government to identify and procure
    the end item. If suitable catalog data are not available, or the
    manufacturer's existent drawing does not comply with this
    requirement, a specification source control drawing shall be
    prepared for the end item.

```{=html}
<!-- -->
```
VII. [Interchangeability Marking]{.underline}: Engineering drawings
     required to be furnished for component parts shall be marked to
     indicate the approved interchangeability or replaceability status.
     The engineering drawings to be marked shall be those parts required
     by MIL-STD-100 to be listed in the interchangeability and
     replaceability working list (when contractually required). New part
     numbers shall be assigned to identify parts of replaceability, or
     from replaceable to interchangeable.

```{=html}
<!-- -->
```
VIII. [Original Drawings]{.underline}: For any drawings revised/created
      by the contractor, the originals shall be furnished at the
      termination of the contract.

> Packing the originals shall be Level "C" in accordance with
> specification MIL-D-1000.
>
> None of the original drawings shall be folded and shall be shipped
> flat or rolled.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
[**DRD NO**.]{.smallcaps}: **1.4.9.1-b**

3\. **[DATA TYPE]{.smallcaps}**: 1 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Food Contamination Control Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: To define the program to be
implemented for effective contamination control for the food production
facility.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer's letter

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an on-going
requirement; no break in existing submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Updated as required.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.9.1

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The contractor shall provide
a document describing the overall approach for implementation of an
effective contamination control program for the food and the food
production facility.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**: None

3.  **[[CONTENTS]{.underline}]{.smallcaps}**: The plan shall, as a
    minimum, specifically address control of contamination by micro
    organisms, dust, pests, rodents, chemicals, condensates, and other
    unsanitary sources as well as use of clean room facilities and clean
    work stations and cleanliness levels to be maintained.

> The contractor shall maintain the plan as necessary to assure that it
> accurately reflects his approach to contamination control in the food
> and the food production facility.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

**1. DPD NO.: 821 ISSUE: Rev. 1 2. DRD NO.: 1.4.9.1-c**

**3. DATA TYPE: 1 4. DATE REVISED: 12/99**

**5. Page 1 of 1**

6\. TITLE: Flight Food Certification Documentation

7\. DESCRIPTION/USE: To provide documentation supporting the

certification of flight food assemblies for each mission.

8\. DISTRIBUTION: Per Contracting Officer\'s letter

9\. INITIAL SUBMISSION: Assumption of an on-going requirement; no break

in existing submission schedule.

10\. SUBMISSION FREQUENCY: As required or upon NASA request

11\. REMARKS:

12\. INTERRELATIONSHIP: SOW 1.4.9.1

13\. DATA PREPARATION INFORMATION:

13.1 SCOPE: The contractor shall maintain an acceptance data package

which shall show adherence of the food processes, procedures, and
analyses

to required standards and specifications and provide the basis for

certification of the flight food assemblies for each mission. This data
shall be available to NASA upon request.

13.2 APPLICABLE DOCUMENTS: 528-48xxx. This is a flight unique drawing
which documents all food stowed for each mission. A copy of this drawing
shall be provided by the contractor to NASA as soon as it is available
prior to the launch of each Shuttle mission.

13.3 CONTENTS: This documentation shall include as a minimum: product

identification; lot number; food manufacturing specification; source;
date

of manufacture; microbiological certification; organoleptic and other
test

results required for specific foods; waivers, deviations and MRB
actions;

and the mission-specific Food Installation Drawing prepared in
accordance

with DRD 1.4.9.1-a.

13.4 FORMAT: Contractor format is acceptable.

13.5 MAINTENANCE: Changes shall be incorporated as required by change

page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** revision-a]{.smallcaps}
2. **[DRD NO.]{.smallcaps}**: **1.4.9.1-e**

3\. **[DATA TYPE]{.smallcaps}**: 2 4. **[DATE REVISED]{.smallcaps}**:
01/15/99

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Government Certification Approval Request
(GCAR)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide NASA JSC with
cognizance of the elements of the contractor's plan for hardware
certification and to report the results of the system certification
activity in order to assess the acceptability of the equipment design.

8\. **[DISTRIBUTION]{.smallcaps}**: NASA/JSC SR&QA. Also, see
instructions.

9\. **[INITIAL SUBMISSION]{.smallcaps}**: As required. Assumption of an
on-going requirement; no break in existing submission schedule

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Update as required.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.9.1

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The GCAR along with attached
documentation, provides the vehicle for NASA approval of hardware
certification. It also serves as the Certification Report or
Qualification Test Report when a formal certification report is not
submitted. The completed form, with attached documentation, is submitted
by the hardware/software provider to Safety Reliability and Quality
Assurance (SR&QA) for review and approval. All sections must be
addressed. All documents listed in the GCAR as verification of a
requirement or specification must be attached to the GCAR. The completed
GCAR, with supporting data, is also referred to as the certification
data package.

13..2 [**[APPLICABLE DOCUMENTS]{.underline}**:]{.smallcaps} See
instructions, NSTS 5300.4 (1D-2), NSTS 07700 Vol. V.

3.  **[[CONTENTS]{.underline}]{.smallcaps}**: Instructions on contents
    and use of the GCAR can be found electronically at
    http://wwwsrqa.jsc.nasa.gov/gcars/instructions.htm. Any questions or
    comments may be directed to the assigned NASA/JSC safety and mission
    assurance engineer.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: JSC Form 1296, latest
version. An electronic copy of the GCAR must be submitted with the hard
copy version.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Update as required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
[**DRD NO**.]{.smallcaps}: **1.4.9.1-f**

3\. **[DATA TYPE]{.smallcaps}**: 1 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Post Test Summary Report

7\. **[DESCRIPTION/USE]{.smallcaps}**: To fully report results of
testing and/or events of importance that involve the EMU, EVA support
equipment, and launch/entry suit equipment (flight and training) a post
test summary report shall be generated.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer's letter

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Assumption of an on-going
requirement; no break in existing submission schedule.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Updates as required

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.9.1

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**: None

[13.2 **[MAINTENANCE]{.underline}**]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

13.3 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** BASIC 2.
**[DRD NO.]{.smallcaps}**: **1.4.9.1-g**

3\. **[DATA TYPE]{.smallcaps}**: 1 4. **[DATE REVISED]{.smallcaps}**:
01/15/99

5\. **[PAGE]{.smallcaps}**: 1/3

6\. **[TITLE]{.smallcaps}**: Problem Reporting and Corrective Action
(PRACA)

7\. **[DESCRIPTION/USE]{.smallcaps}**: To fully report problems (as
described below) and describe their resolutions

8\. **[DISTRIBUTION]{.smallcaps}**:

Reports shall be sent to: JSC PRACA Center

NASA/JSC NT52/Bldg 45

Houston, Texas 77058

email (preferred): Send copy to both addresses:

terry.1.miller1@jsc.nasa.gov

k.s.ferguson1@jsc.nasa.gov

voice: Primary 281-244-1941

Secondary 281-244-1935

facsimile mail: Primary 281-244-2253

Secondary 281-244-1848

hours of operation: 8:00 a.m. - 4:30 p.m. Central, Monday thru Friday

9\. **MAINTENANCE**: Update as required.

10\. **[INITIAL SUBMISSION]{.smallcaps}**: As required. Assumption of an
on-going requirement; no break in existing submission schedule.

11\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Updates as required.

12\. **[REMARKS]{.smallcaps}**: Provide copies as requested.

13\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.4.9.1

14\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

14.1 **[SCOPE]{.underline}**: PRACA reportable problems are defined as
functional failures, overstress or potential overstress of hardware,
unsatisfactory conditions, and unexplained anomalies which occur on
flight products, flight-like products, or safety critical ground support
equipment (GSE) during qualification testing and during or subsequent to
acceptance testing. GSE reporting is limited to GSE problems which could
result in loss of personnel capability or loss of vehicle systems.

14.2 [**[APPLICABLE DOCUMENTS]{.underline}**:]{.smallcaps}

a\. JSC 28035, "JSC Government-Furnished Equipment (GFE) Problem
Reporting and Corrective Action (PRACA) Requirements" Latest Revision

[14.3 **[CONTENTS]{.underline}**]{.smallcaps}:

A.  Initial notification/report shall occur within 24 hours after
    isolation to the Line Replaceable Unit (LRU)/Orbital Replacement
    Unit (ORU) level or lower and shall include the following data:

```{=html}
<!-- -->
```
1.  A uniquely identifiable report number;

2.  The date the problem occurred if known, in unknown the date it was
    detected;

3.  The location at the time of occurrence/detection;

4.  The non-conforming LRU/ORU (top assembly) product identification:

```{=html}
<!-- -->
```
a.  part name;

b.  part number;

c.  serial number, logistical control number, lot number, or version
    number (if applicable);

d.  manufacturer;

e.  manufacturer cage code (if known).

```{=html}
<!-- -->
```
5.  The Shop Replacement Unit (SRU) (Subassembly) product identification
    (if known):

```{=html}
<!-- -->
```
a.  part name;

b.  part number;

c.  serial number, logistical control number, lot number, or version
    number (if applicable);

d.  manufacturer

e.  manufacture cage code (if known).

```{=html}
<!-- -->
```
6.  The Non-conforming article (NCA) (component, lowest traceable)
    product identification (if known):

```{=html}
<!-- -->
```
a.  part name;

b.  part number;

c.  serial number, logistical control number, lot number, or version
    number (if applicable);

d.  manufacturer

e.  manufacture cage code (if known).

7\. The test or operation (code)\* being performed at time of
occurrence;

8.  The prevalent condition (code)\* at time of occurrence;

9.  The failure mode (code)\* experienced;

10. Brief narrative description of nonconformance, including comparison
    of expected events with actual events (or results);

11. A brief title;

12. Technical point of contact name;

13. Technical point of contact phone number;

14. System/Subsystem(s) affected (if known);

15. Logistics Control Number (Station only);

16. Fracture Critical Indicator (Station only);

17. Detected During - The specific test/procedure being conducted, or
    use of the nonconforming hardware at the time of problem occurrence;

18. Material (code)\* which indicates the material that failed (in
    known).

```{=html}
<!-- -->
```
B.  The final resolution (close-out) shall include the following
    additional data:

```{=html}
<!-- -->
```
1.  Resolution narrative which includes

```{=html}
<!-- -->
```
a.  [Corrective actions]{.underline} **(Immediate, Interim, Remedial,
    Root Cause and Permanent)** that has been established including
    reference to released documentation establishing this corrective
    action, or

```{=html}
<!-- -->
```
a.  When not establishing corrective action to preclude recurrence of
    the problem provide a narrative explanation which documents the
    rationale. This narrative shall also include the following:

> (1.) Effects on mission, if nonconformance recurred, and recommended
> operational work around procedures;

2.  Methods of detecting the problem in-flight/on-orbit. Indicate how
    the crew will be made aware of the problem or what automatic system
    detects or corrects the problem;

3.  When last test of product, prior to mission, is performed;

4.  Assurance that explanations using redundancy and/or alternate modes
    of operation as one of the elements do not negate each other;

```{=html}
<!-- -->
```
2.  All end items and/or missions that may be affected by the problem;

3.  Previous history of nonconforming product;

4.  Problem report numbers related to the same problem;

5.  Clause (code)\* which indicates what action caused the failure;

6.  Defect (code)\* which indicates what defect caused the failure;

7.  Material (code)\* which indicates the material that failed (if not
    reported at initiation)

8.  Recurrence control (code)\* which indicates what action was taken as
    a result of the nonconformance;

9.  Indication as to whether or not the problem will cause a revision to
    a CIL;

10. Related document identification (waiver number, CCB directive,
    etc.);

11. Date of resolution.

12. The non-conforming Shop Replaceable Unit (subassembly) product
    identification:

```{=html}
<!-- -->
```
a.  part name;

b.  part number;

c.  serial number, logistical control number, lot number, or version
    number (if applicable);

d.  manufacturer

e.  manufacturer cage code.

```{=html}
<!-- -->
```
13. The non-conforming article (component, lowest traceable) product
    identification:

```{=html}
<!-- -->
```
a.  part name;

b.  part number;

c.  serial number, logistical control number, lot number, or version
    number (if applicable);

d.  manufacturer

e.  manufacturer cage code

\*Codes are per:

JSC 28035, Appendix B, PRACA Codes

14.4 **[[FORMAT]{.underline}]{.smallcaps}**: JSC Form 2174, Failure
Investigation Analysis Report, latest revision.

14.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Update as required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.4.9.2**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Equipment Inventory Report

7\. **[DESCRIPTION/USE]{.smallcaps}**: To provide inventory oversight.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}**

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Revisions as required

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**:

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The Equipment Inventory Report provides
visibility of the inventory of material, parts, subassemblies, and end
items.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The Equipment Inventory
Report shall contain the status of Government-furnished property (GFP)
to include the following:

a\. Flight status: quantity.

b\. Repair status: quantity from previous report (flight and training).

c\. Refurbish status: quantity from previous report (flight and
training).

d\. Quantity of material, parts, subassemblies, and end items:

1\. On-hand.

2\. On order and projected order for next reporting period.

3\. Projected required for the total NSTS mission model.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.5.1.2**

3\. **[DATA TYPE]{.smallcaps}**: 2 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Operations and Contamination Control Plan
for Integrated Processing at KSC

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document the approach to
Shuttle/Payload Integrated processing and contamination control at the
Orbiter Processing Facilities (OPF\'s) and Launch Pads.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an on-going
requirement; no break in existing submission frequency

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Annual revisions, as
required

11\. **[REMARKS]{.smallcaps}**: NAS10-10900, DRL items 040 and 041

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.5.1.2

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The Operations and Contamination Control
Plan for Integrated Processing at KSC develops and defines the
contractor\'s approach to payload element processing during integration
activities at the launch pad and the OPF, and to document contamination
control processes and responsibilities at these sites.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**

K-STSM-14.2.1 *KSC Cargo Facility Contamination Control Plan*

KVT-PL-0024 *PCR Payload Operations Plan*

KSC-PL-0025 *Shuttle Facility Contamination Control Implementation Plan*

NSTS 08242 *Space Shuttle Limitations for Non-Flight Materials and
Equipment Used In*

*and Around the SSV*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The contractor\'s
approach and plan shall be consistent with the scope and content of the
applicable documents. The contractor is encouraged to minimize like
documentation by consolidating like plans and documentation.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by change page or complete reissue (indicate revision level
and date).

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.5.2.1**

3\. **[DATA TYPE]{.smallcaps}**: 1 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: KSC Ground Launch Sequencer Configuration
Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: To define the Ground Launch
Sequencer configuration for Launch Countdowns at KSC.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an on-going
requirement; no break in existing submission schedule

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Per mission basis

11\. **[REMARKS]{.smallcaps}**: NAS10-10900, DRL item 32

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.5.2.1

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: This plan defines the approach for
implementing and monitoring the approved Ground Launch Sequencer
configuration.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**

NSTS 16007 *Launch Commit Criteria and Background*

KLO-82-0071 *GLS Configuration*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: This plan shall document
an approach for implementing and monitoring the approved Ground Launch
Sequencer configuration. The scope and content of this plan shall
contain as a minimum the KLO-82-0071/GLS Configuration plan.

13.4 FORMAT: Contractor shall conform to delivery media formats and
electronic data formats per DRD 1.1.4.1-e, Data Management Plan, or per
Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Update 14 days prior
to launch countdown Call-to-Station.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.5.2.3**

3\. **[DATA TYPE]{.smallcaps}**: 1 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: KSC Launch Team Certification Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document the training,
qualification and certification process for the KSC Launch Control Team.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** First complete mission flow by
contractor

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Annual revisions as
required.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.5.2.3

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The KSC Launch Team Certification Plan
documents, at a minimum, the launch team certification process for
Countdown Call-to-Stations through Launch or scrub turnaround safing.

13.2 [**[APPLICABLE DOCUMENTS]{.underline}**:]{.smallcaps} None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The plan shall document a
standardized approach for training the combined contractor/Government
launch team for conducting launch operations, providing flight crew pad
emergency egress training, and certifying that the contractor\'s
engineers and operations managers are fully qualified for conducting a
launch countdown. The plan shall encompass individual proficiency for
each respective discipline as well as in the launch process itself.
Training plans shall include as a minimum launch countdown simulations,
active participation in integrated testing activities, tanking
simulations, detailed training on the operation and maintenance of
flight hardware, software, and support equipment; and requirements,
procedures, and related requirements and processes.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format is
acceptable with NASA approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated by change pages or complete revision.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.5.4.1**

3\. **[DATA TYPE]{.smallcaps}**: 2 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Post Launch Operation Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document processes, products
and responsibilities for supporting landing and recovery operations at
secondary and contingency landing sites.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an on-going
requirement; no break in existing submission schedule

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: N/A

11\. **[REMARKS]{.smallcaps}**: NAS10-10900, DRL items 030 and 044

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.5.4.1

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The Post Launch Operation Plan defines
contractor\'s responsibilities and implementation procedures for
off-site landings, convoy operations, and Orbiter salvage operations.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**

SFOC-GO0021 KSC *Off-site Operations Plan*

SFOC-GO0014 *KSC NSTS Salvage Plan*

SFOC-GO0022 *Convoy Operations Plan*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The contractor shall
develop and maintain (update) a plan that covers support for an Orbiter
landing and recovery at secondary or contingency landing site, convoy
operations and KSC support for Orbiter salvage operations. These plans
shall encompass the scope and content of the applicable KSC documents in
13.2.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** [REVISION
3]{.smallcaps} 2. **[DRD NO.]{.smallcaps}**: **1.5.5.2**

3\. **[DATA TYPE]{.smallcaps}**: 2 4. **[DATE REVISED:
12/02]{.smallcaps}**

5\. **[PAGE]{.smallcaps}**: 1/3

6\. **[TITLE]{.smallcaps}**: Facility and Equipment Maintenance Plan and
Supporting Data

7\. **[DESCRIPTION/USE]{.smallcaps}**: To document the contractor\'s
method of integrating the proper mix of preventive, predictive,
programmed, and run-to-failure maintenance on facilities, systems and
equipment, and software associated with hardware maintenance actions. To
document the required identification, schedules, budgets, and
implementation methods for the above maintenance-related activities of
facilities, systems, and equipment assigned to the contractor. This DRD
has two parts, Facilities and Collateral Equipment Requirements (Part I)
and Non-Collateral Equipment (Part II). Part I is applicable for all
SFOC Facilities, facility systems and collateral equipment
responsibilities. Part II is applicable to only Launch & Landing/Ground
Ops. Non-collateral Equipment (Comm., GSE, LPS). The contractor shall
provide a subset of content applicable for each location for all
requirements in Part I (e.g., Ground Ops., SRB, Palmdale, Downey). The
contractor shall provide content applicable for only Ground Ops. for all
requirements in Part II.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter.

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Plan - 60 days after contract
award.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**:

> a\. Provide plan (updated or complete reissue) annually, each fiscal
> year; November 15.
>
> b\. Provide annual deliverables (Table 13-1) each fiscal year by
> November 15.
>
> c\. Provide trend analysis reports, 4 times a year; January 31, April
> 30, July 30 and November 15.
>
> d\. Provide Projected BMAR Estimates, NRC Maintenance and Repair
> Estimates and Unconstrained NRC Maintenance and Repair Estimates for
> the fiscal year beginning two years from the commencement date of the
> current fiscal year; November 15.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.5.5.2, 1.4, 1.1.6.1

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The Plan shall include the contractors\'
methodology of integrating and reporting condition assessments for
facilities, systems and equipment within their associated maintenance
programs, and their planning efforts in identifying and reducing the
Backlog of Maintenance and Repair (BMAR). The plan shall also address
their method in implementing a proactive corrosion control program to
insure facilities, systems, and equipment receive proper attention to
insure they achieve or exceed their design life.

13.2 [**[APPLICABLE DOCUMENTS]{.underline}**:]{.smallcaps}

NPG 8831.2 *NASA Facilities Maintenance and Energy Management Handbook*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**:

> Deliverables include metrics and reports listed in Table 13-1 below.

9.  

```{=html}
<!-- -->
```
1.  
2.  
3.  

DRD CONTINUATION SHEET

**[TITLE]{.smallcaps}**: Facility and Equipment Maintenance Plan and
**[DRD NO.]{.smallcaps}**: **1.5.5.2**

Supporting Data

**[DATA TYPE]{.smallcaps}**: 2 **[PAGE]{.smallcaps}**: 2/3

[13.]{.smallcaps} [**DATA PREPARATION INFORMATION
(CONTINUED)**:]{.smallcaps}

3.  [**[CONTENTS (CONTINUED)]{.underline}**:]{.smallcaps}

Table 13-1:

+----+------------------------------------------+-----------+---------+
|    | Deliverable                              | PART I    | PART II |
|    |                                          |           |         |
|    |                                          | (SFOC     | (Ground |
|    |                                          | Wide)     | Ops.    |
|    |                                          |           | only)   |
|    |                                          | F         |         |
|    |                                          | acilities | Non-col |
|    |                                          | &         | lateral |
|    |                                          | C         | Eq      |
|    |                                          | ollateral | uipment |
|    |                                          | Equip.    |         |
+----+------------------------------------------+-----------+---------+
| a  | AVAILABILITY: Reported as a percentage   | Quarterly | Qu      |
| \. | by system and facility. Applicability of |           | arterly |
|    | this metric to each system or piece of   |           |         |
|    | equipment shall be partnered with each   |           |         |
|    | site's applicable Government             |           |         |
|    | counterpart.                             |           |         |
+----+------------------------------------------+-----------+---------+
| b  | BMAR: Backlog of Maintenance and Repair  | Annual    | Annual  |
| \. | (BMAR) reported in dollars and broken    |           |         |
|    | into three categories: Facilities, GSE,  |           |         |
|    | and COMM/LPS.                            |           |         |
+----+------------------------------------------+-----------+---------+
| c  | AWP: Annual Work Plan (AWP) consisting   | Annual    | Annual  |
| \. | of a list of maintenance activity for    |           |         |
|    | each facility and system for the year.   |           |         |
+----+------------------------------------------+-----------+---------+
| d  | BUDGET: Maintenance funding planned for  | Annual    | Annual  |
| \. | the next fiscal year (Initial Operating  |           |         |
|    | Plan for M&R),,in accordance with        |           |         |
|    | approved WBS structure, with a breakdown |           |         |
|    | of Preventative Maintenance, Corrective  |           |         |
|    | Maintenance (including Trouble Calls),   |           |         |
|    | Programmed Maintenance and PT&I. (Ground |           |         |
|    | Ops. track Trouble Calls as a separate   |           |         |
|    | category.)                               |           |         |
+----+------------------------------------------+-----------+---------+
| e  | CONDITION ASSESSMENT: Aggregate          | Annual    | Annual  |
| \. | condition assessment code data: one      |           |         |
|    | chart depicting aggregate facility data, |           |         |
|    | and another presenting aggregate         |           |         |
|    | non-facility data. Applicability of      |           |         |
|    | condition assessment to individual       |           |         |
|    | pieces of equipment to be partnered with |           |         |
|    | the Government.                          |           |         |
+----+------------------------------------------+-----------+---------+
| f  | CONDITION ASSESSMENT BACKLOG: Aggregate  | Quarterly | Qu      |
| \. | proportion of Condition Assessments      |           | arterly |
|    | overdue.                                 |           |         |
+----+------------------------------------------+-----------+---------+
| g  | CORRECTIVE ACTIONS: A report identifying | Quarterly | Qu      |
| \. | corrective actions associated with any   |           | arterly |
|    | maintenance metric whose indicators are  |           |         |
|    | below expectations.                      |           |         |
+----+------------------------------------------+-----------+---------+
| h  | CORROSION CONTROL: A status report       | Annual    |         |
| \. | addressing corrosion issues by facility  |           |         |
|    | and equipment. Report indicates repair   |           |         |
|    | costs, activity, backlog, and scheduled  |           |         |
|    | corrective action dates. This            |           |         |
|    | requirement shall be partnered with each |           |         |
|    | site's applicable Government             |           |         |
|    | counterpart.                             |           |         |
+----+------------------------------------------+-----------+---------+
| i  | PM/CM RATIO: Ratio of PM cost to CM.     | Quarterly | Qu      |
| \. |                                          |           | arterly |
|    | CM/Total Maintenance: Ratio of CM to     | Quarterly |         |
| j  | Total Maintenance (Cost by               |           | Qu      |
| \. | facility/system for Ground Ops. only.)   |           | arterly |
+----+------------------------------------------+-----------+---------+
| k  | Annual M&R Funding w/o CoF: Operating    | Annual    |         |
| \. | Plan for current year.                   |           |         |
+----+------------------------------------------+-----------+---------+
| l  | UNCONSTRAINED M&R w/o CoF: Total         | Annual    |         |
| .. | requirement for current year.            |           |         |
+----+------------------------------------------+-----------+---------+
| m  | PM PERFORMANCE: Ratio of performed PM    | Monthly   | Monthly |
| \. | tasks to scheduled PM tasks.             |           | (p      |
|    |                                          | (provided | rovided |
|    |                                          | in PMS)   | in PMS) |
+----+------------------------------------------+-----------+---------+

  ----- ----------------------------------------- ------------ ------------
                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               
  ----- ----------------------------------------- ------------ ------------

DRD CONTINUATION SHEET

**[TITLE]{.smallcaps}**: Facility and Equipment Maintenance Plan and
**[DRD NO.]{.smallcaps}**: **1.5.5.2**

Supporting Data

**[DATA TYPE]{.smallcaps}**: 2 **[PAGE]{.smallcaps}**: 3/3

[13.]{.smallcaps} [**DATA PREPARATION INFORMATION
(CONTINUED)**:]{.smallcaps}

13.3 [**[CONTENTS (CONTINUED)]{.underline}**:]{.smallcaps}

**Table 13-1 (Continued[)]{.underline}**:

+----+------------------------------------------+-----------+---------+
|    | Deliverable                              | PART I    | PART II |
|    |                                          |           |         |
|    |                                          | (SFOC     | (Ground |
|    |                                          | Wide)     | Ops.    |
|    |                                          |           | only)   |
|    |                                          | F         |         |
|    |                                          | acilities | Non-col |
|    |                                          | &         | lateral |
|    |                                          | C         | Eq      |
|    |                                          | ollateral | uipment |
|    |                                          | Equip.    |         |
+----+------------------------------------------+-----------+---------+
| n  | PLAN vs. ACTUAL COSTS: Cost variance     | Annual    | Annual  |
| \. | (dollar and percentage) in accordance    |           |         |
|    | with approved WBS structure and          |           |         |
|    | maintenance type ( Preventative          |           |         |
|    | Maintenance, Corrective Maintenance      |           |         |
|    | (including Trouble Calls), Programmed    |           |         |
|    | Maintenance and PT&I.) (Ground Ops.      |           |         |
|    | track Trouble Calls as a separate        |           |         |
|    | category.)                               |           |         |
+----+------------------------------------------+-----------+---------+
| o  | COST TREND REPORT: Maintenance           | Annual    | Annual  |
| \. | expenditure trends report by in          |           |         |
|    | accordance with approved WBS structure   |           |         |
|    | and maintenance type (Preventative       |           |         |
|    | Maintenance, Corrective Maintenance,     |           |         |
|    | Programmed Maintenance and PT&I.)        |           |         |
+----+------------------------------------------+-----------+---------+
| p  | RCM PROGRESS: Percentage of systems      | Annual    |         |
| \. | analyzed using Reliability Centered      |           |         |
|    | Maintenance (RCM) methodology. Metric    |           |         |
|    | will be discontinued once all systems    |           |         |
|    | are analyzed.                            |           |         |
+----+------------------------------------------+-----------+---------+
| q  | RCM-INDUCED CHANGES: Percentage of       | Annual    |         |
| \. | maintenance tasks changed as a result of |           |         |
|    | RCM analysis. Metric will be             |           |         |
|    | discontinued once all systems are        |           |         |
|    | analyzed.                                |           |         |
+----+------------------------------------------+-----------+---------+
| r  | PT&I Finds                               | Annual    |         |
| \. |                                          |           |         |
+----+------------------------------------------+-----------+---------+
| s  | Cost of Scheduled Work: Cost of          | Annual    |         |
| \. | scheduled work consisting of PM, PT&I,   |           |         |
|    | PGM, ROI and PT&I finds repair costs.)   |           |         |
+----+------------------------------------------+-----------+---------+

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

  ----- ----------------------------------------- ------------ ------------
                                                               

                                                               

                                                               

                                                               
  ----- ----------------------------------------- ------------ ------------

4.  

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.5.5.3**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Notification of Modifications to KSC
Configured Systems and Equipment Report

7\. **[DESCRIPTION/USE]{.smallcaps}**: To notify the Government of
contractor planned and/or initiated modifications to KSC configured
systems, facilities, and equipment, including hardware, software, and
operating procedures.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Assumption of an on-going
requirement; no break in existing submission schedule

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Within 7 days of
project/change approval by the contractor, but in all cases prior to
implementation.

11\. **[REMARKS]{.smallcaps}**: NAS10-10900, DRL item 024

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.5.5.3

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: This report provides notification to the
Government of modifications to KSC configured systems, facilities, and
equipment.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**

KSC Drawing 79K09579, Rev. R, identifies the configured systems and
equipment.

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: This report shall
describe the modification of the hardware, software, and/or operating
procedures for the configured systems and equipment, and provide the
justification for making the change.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: As required

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.5.5.4.3-a**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Training/Certification Plan and Schedule
Report

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe the contractor\'s
method for training and certifying contractor and non-contractor
personnel, and the procedures for getting training.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION:** Assumption of an on-going requirement; no
break in existing submission schedule

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: MONTHLY

11\. **[REMARKS]{.smallcaps}**: NAS10-10900, DRL item 031

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.5.5.4.3; DRD 1.4-c

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: This plan and report shall apply only to
technical training related to flight hardware and associated GSE.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**

NHB 5300.4 (ID-2), *Safety, Reliability, Maintainability and Quality*

paragraph ID500.7 *Provisions for the Space Shuttle Program*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**:

> a\. The plan shall include:
>
> 1\. Description of the contractor certification program including a
> list of certifications.
>
> 2\. Training requirements to meet each of those certifications.
>
> 3\. Procedure that establishes the individual\'s certification.
>
> 4\. How certification records will be maintained.
>
> 5\. Procedures by which NASA and other contractor personnel may obtain
> training.
>
> b\. The contractor shall periodically publish a training schedule.
>
> c\. The contractor shall report on any ground or flight processing
> incidents that were due to lack of training or certification.
> Corrective action shall be reported.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.1.1

3\. [DATA TYPE]{.smallcaps}: 2 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Annex 7 (Training) - Payload Integration Plan

7\. [DESCRIPTION/USE]{.smallcaps}: Agreement with Space Shuttle Program
(SSP) Program Office and payload customer which includes training
responsibilities and requirements for flight controllers and flight
crew.

8\. [DISTRIBUTION]{.smallcaps}: Per Space Shuttle Program Office
procedures

9\. [INITIAL SUBMISSION:]{.smallcaps} First Cargo Integration Review
after Authority to Proceed (ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Submitted per payload, per
flight, to support the Cargo Integration Review if required by the
Payload Integration Plan (PIP) as negotiated between the payload
customer and the Annex 7 Book Manager.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.1.1, 1.6.1.2, 1.6.1.3

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: The Annex 7 (Training) - Payload Integration
Plan defines facility requirements and lesson responsibilities of
payload-specific training for SSP mission controllers and flight crew.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}

NSTS 07700, Vol. 4 *SSP Configuration Management Requirements and
Customer and Flight Integration Configuration Management Work
Instructions*

NSTS-2100-A07 *Training Annex Data Requirements Payload Integration Plan
(Blank Book)*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: In accordance with
NSTS-2100-A07, Annex 7 shall contain specifications and agreements of
Space Transportation System (STS) crew training requirements (skills,
training facilities, training duration and schedule), Integrated
Training Facility (ITF) model requirements, integrated Mission Control
Center (MCC)/Operations Support Center (OSC) training requirements,
integration simulation requirements, and schedules.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per Training Annex
Data Requirements Blank Book.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.1.1.1

3\. [DATA TYPE]{.smallcaps}: 4 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Flight Operations Training Records

7\. [DESCRIPTION/USE]{.smallcaps}: Records of as-performed training for
purposes of Flight Crew and flight controller certification.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Upon request

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As requested

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.1.1.1

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: Records required to demonstrate position
unique certification and certification of flight readiness for Flight
Crews, flight controllers, and any contractor supplied services that
require certification.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Contractor shall input
training records when lessons are complete and record all significant
student, lesson, integrated training objectives, and facility data.
Include student name, lesson, date, time, facility, time facility
unavailable for training, and whether or not lesson was successfully
accomplished.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Records and data
accessible within 10 days after completion of lesson.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.1.1.2-a

3\. [DATA TYPE]{.smallcaps}: 2 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Training Development and Support Plan (TDSP)
JSC 36049

7\. [DESCRIPTION/USE]{.smallcaps}: To document processes that are
utilized for curriculum and lesson development.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} 30 days after contract award

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Annually

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.1.1.2

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: The Training Development Support Plan (JSC
36049) defines curriculum (training flow) and lesson development
processes that will be used to develop Shuttle and Station lessons as
defined in crew training catalogs and flight controller/instructor
certification guides.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}

DT510 *Space Flight Training Division Document Standards*

DT511 *Technical Writing Training Manual*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Training Development and
Support Plan will document curriculum and lesson development processes.
Processes will be differentiated as a function of lesson delivery media.
The Training Development and Support Plan shall document lesson plan
formats.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.1.1.2-b

3\. [DATA TYPE]{.smallcaps}: 4 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Curriculum, Lesson, and Instructor Feedback

7\. [DESCRIPTION/USE]{.smallcaps}: To document quality of Space Shuttle
(SS) and International Space Station (ISS) flight operations curriculum
and lessons.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Upon request

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Be available to support all
Process Integrity Reviews

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.1.1.2

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: Curriculum and lesson feedback data shall
document appraisals of flight operations training as delivered for SS
and ISS flight crews and mission controllers.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Collect and maintain student
feedback data on lesson quality and performance.

> a\. Lesson data collected should appraise: lesson effectiveness,
> lesson efficiency, how lesson fits into curriculum.
>
> b\. Instructor performance data collected should appraise: lesson
> delivery, instructor readiness, technical competence.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Records and data
accessible within 10 days after completion of lesson. A process will be
set up by the contractor to sort and store these records that meets
contractor and NASA needs.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.1.1.4

3\. [DATA TYPE]{.smallcaps}: 2/3/4 4. [DATE REVISED:
09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Instructor Certification Guides and Training
Plan

7\. [DESCRIPTION/USE]{.smallcaps}: To define process to certify flight
operations instructors for Shuttle and Station.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Upon request

10\. [SUBMISSION FREQUENCY]{.smallcaps}:

Certification Guide for each instructor certifiable position: annually,
if required (Type 3 for CAF; Type 2 for GAF)

Instructor Training Plan and certification records: as requested (Type
4)

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.1.1.4

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: Instructor Certification and Training Plan
shall identify how the instructor will demonstrate qualification for all
formal flight operations training lessons.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}

JSC 36049 *Training Development and Support Plan*

DG6-90-14 *MOD Spaceflight Personnel Certification Plan (GAF personnel)*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Instructor Certification
Guides shall include a description of curriculum, lesson descriptions,
training objectives, and final certification criteria. The Training Plan
shall identify instructor assignments to training teams and one year
SMS, SCA, and SSTF team assignment plans. The contractor shall maintain
certification documentation for all instructors.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.1.2-a

3\. [DATA TYPE]{.smallcaps}: 2/3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Mission Controller Certification Guides

7\. [DESCRIPTION/USE]{.smallcaps}: Certification curriculum and
requirements for SSP and ISSP NASA Civil Service mission controller
certifiable positions and for contractor-provided certifiable positions.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} 30 days after Authority to Proceed
(ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Annually, or on a
flight-specific basis if special training requirements are identified

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.1.2

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: The document covers mission controller
certification and lesson as required by the MOD Resident Office.
Positions will be jointly agreed to by responsible MOD Resident Office
and SFOC Flight Operations organization. Government accountable
positions will be specified in the annual Government Accountable
Function Directive (GAFD). The contractor develops certification and
lessons based on NASA Flight Control task requirements. ISSP mission
controller certification and lesson requirements will be transitioned to
the contractor when they mature and stabilize.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}

JSC 36049 *Training Development and Support Plan*

STSOC-PN-001172A *Training Guide Development Operating Plan*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The contractor shall submit a
description of curriculum, lesson descriptions, and final certification
criteria. The document shall contain the following:

> a\. Reference to the required training material including manuals,
> workbooks, texts, videos, computer based training lessons, briefings,
> tours, and any other material required for certification.
>
> b\. Requirements for simulation support, and on-the-job training
> needed for certification.
>
> c\. Descriptions for tasks which must be demonstrated by trainees
> prior to certification.
>
> d\. Training flows including any prerequisite training certification.
>
> e\. Statement of certification forms.
>
> f\. Requirements for maintenance of training proficiency.

The Contractor shall document flight and mission controller training
objectives. The document shall contain Performance Objectives required
for Certification. The Objectives shall be categorized by discipline and
according to Integrated and Standalone Training.

NASA directed positions are Data Type 2; contractor provided positions
are Data Type 3.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.1.2-b

3\. [DATA TYPE]{.smallcaps}: 4 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Mission Controller Lessons and Scripts

7\. [DESCRIPTION/USE]{.smallcaps}: Lessons required for certification of
flight controllers and for preparations of flight control team.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Upon request

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Upon request

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.1.2; DRD 1.6.1.2-a,
*Mission Controller Certification Guides*

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: Lessons defined in blue books or certification
guides and integrated simulation scripts that are required to certify
flight controllers and prepare flight control teams for each mission.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}

JSC 36013 *Instructional Development Process*

JSC 36049 *Training Development and Support Plan*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Lessons shall be developed
based on Mission Controller Certification Guides (DRD 1.6.1.2-a)
requirements. Produce lessons in accordance with Training Development
and Support Plan Standards. Lessons must fulfill performance objectives
defined in lesson plan as identified in specified blue book or
certification guide.

Integrated simulation scripts shall be based on NASA flight-specific or
generic integrated simulation requirements and flight controller
objective requirements as provided in the Shuttle Mission Simulator
(SMS), Simulation Control Area (SCA), and Space Station Training
Facility environment.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.1.3-a

3\. [DATA TYPE]{.smallcaps}: 2 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Crew Training Catalogs \[Shuttle Crew Training
Catalog (SFOC-FL0258), Station Crew Training Catalog (JSC 36301)\]

7\. [DESCRIPTION/USE]{.smallcaps}: Curriculum and training requirements
for Space Shuttle (SS) and International Space Station (ISS) Flight
Crews.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} 30 days after Authority to Proceed
(ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Annually for the Shuttle Crew
Training Catalog; semi-annually for the Station Crew Training Catalog

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.1.3

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: The guide shall cover crew training curricula.
The contractor will work with SS and ISS Flight Crews to identify and
implement changes to curriculum or lessons based on Flight Crew
in-flight task requirements.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}

JSC 36049 *Training Development and Support Plan*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The contractor shall divide
the catalogs into sections covering training for systems, operations,
and integrated simulations. Each section shall include a course
introduction, a lesson sequence flow chart, a training requirements
table showing the hours and crew positions to be trained, a summary of
crew and facility hours, and a description of each individual lesson
(including duration, media, training objectives, prerequisites, etc.).
Content will be based on agreement with customer.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.1.3-b

3\. [DATA TYPE]{.smallcaps}: 3/4 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Crew Training Lessons and Scripts

7\. [DESCRIPTION/USE]{.smallcaps}: Lessons required training Space
Shuttle Program (SSP) and International Space Station (ISS) Flight
Crews.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Upon request

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As requested

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.1.3

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: This document covers lessons and other
documents that are required to train and prepare astronauts and
astronaut flight crews for each mission. Development of lessons will be
based on the Training Development and Support Plan and Crew Training
Catalog requirements.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}

SFOC-FL0258 *Shuttle Crew Training Catalog*

*JSC-36301 Station Crew Training Catalog*

JSC 36049 *Training Development and Support Plan*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The contractor shall produce
lessons in accordance with Training Development and Support Plan
Standards. Lessons must fulfill performance objectives defined in the
crew training catalog or certification guide. (Data Type 4)

The contractor shall maintain Shuttle Crew Operations Manual. INITIAL
SUBMISSION: contract ATP plus six months; submission frequency: once per
Flight Software Operational Increment. (Data Type 3)

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.1.3-c

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Flight or Increment Specific Crew Training Plan

7\. [DESCRIPTION/USE]{.smallcaps}: To define a plan to train Flight
Crews for each flight.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} N/A

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Once per flight at "DT
SCHEDULED START" minus 1 week

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.1.3

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: Contains all flight or increment specific crew
training requirements that will prepare Space Shuttle program (SSP) and
International Space Station (ISS) Flight Crews to accomplish required
in-flight tasks.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The document shall provide a
beginning-to-launch training plan that includes all lesson requirements,
broken into weekly requirements. This document shall identify the
flight-specific or increment-specific crew training plan. The plan will
be developed based on the Crew Training Catalog and NASA flight or
increment-specific requirements. The plan will include projected weekly
metrics of training hours for each crew member of: total training hours,
time in each facility (or facility group), and projected weekly average.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.6.1.3-d**

3\. **[DATA TYPE]{.smallcaps}**: 2 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Astronaut Candidate Training Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: Defines plan to train Astronaut
candidates.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** 30 days before first astronaut
class start after ATP.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: 30 days before each
astronaut class start.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.6.1.3

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: Contains all technical and other
identified training requirements that will prepare SSP and ISS
Astronauts for assignment to flight crews.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The document shall
provide a start-to-finish training plan that includes all lesson
requirements, broken into weekly requirements. This document shall
identify the Astronaut Candidate Training plan. The plan will be
developed based on the Crew Training Catalog and NASA flight or
increment-specific requirements. The plan will include weekly schedule
for the Astronaut Candidate class including : total training hours each
week and time in each facility (or facility group) for each week.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor format
acceptable with Astronaut Office concurrence.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.6.2.1.1**

3\. **[DATA TYPE]{.smallcaps}**: 2 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Flight Rules Publication

7\. **[DESCRIPTION/USE]{.smallcaps}**: Flight rules publication and
change processing to support flight preparation and flight execution.
Documentation for Flight Rules Control Board. Flight Technique Technical
Forums, Joint Operations Panels, Mission Management Team, and other
related technical flight rules forums.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Products and deliverables will
be in consonance with the existing schedules.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**:

a\. All-Flight Rules and Flight Specific Rules - Submit All-Flight Rules
per periodic update schedule. Submit Flight Specific Flight Rules per
flight specific schedules.

b\. Documentation for Flight Rules - Submit per Flight Rules Control
Board schedule.

c\. Documentation for Flight Techniques - Submit per Flight Techniques
Panel schedules.

d\. Documentation for JOP and other required forums - Submit per JOP
schedules.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.6.2.1.1

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**:

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**

*Flight Requirements Document*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: All Flight and Flight
Specific Flight Rules publication and change processing, documentation
for Flight Rules Control Board, Flight Technique Technical Forums, Joint
Operations Panels, Mission Management Team, and other related technical
flight rules forums.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: All-Flight Rules and
Flight Specific Rules: Changes should be incorporated as required by
page change or complete revision and/or electronically via the baseline
MOD operations electronic documentation system for distribution within
and external to the MCC.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.2.1.2

3\. [DATA TYPE]{.smallcaps}: 2 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Operations Documentation Product Handbook and
Product Glossary

7\. [DESCRIPTION/USE]{.smallcaps}: To define the content and delivery
requirements of each operations documentation product, provide
documented procedures required for each operations documentation
product, and provide consistent product standards.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} 30 days after Authority to Proceed
(ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Annual review with NASA and
updates as agreed to keep documentation current with procedures,
products, and delivery requirements.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.2.1.2

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: The Operations Documentation Product Handbook
provides the procedures, development process/product flows,
dependencies, and levels of quality assurance used in the development of
operations products. The associated Operations Documentation Product
Glossary provides detailed product definitions and delivery requirements
for each operations product.

13.2 [[APPLICABLE DOCUMENTS]{.underline}:]{.smallcaps} *Flight
Requirements Document*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Operations Documentation
Product Handbook and Product Glossary shall include the functional areas
of operations documentation (typical list described):

> a\. General - Flight Control Operations Handbook.
>
> b\. Flight Control Operations Documentation.
>
> 1\. Console Documentation.
>
> 2\. Standardized Console Procedures, Software Users Guides,
> Program-wide Shuttle System Schematics.
>
> c\. Flight Design Operations Documentation.
>
> 1\. Console Documentation.
>
> 2\. Console Handbook.
>
> d\. Flight operations technical library services support.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page to keep documentation current
with procedures, products and customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.6.2.1.3-a**

3\. **[DATA TYPE]{.smallcaps}**: 2 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Flight Data File (FDF)/Operations Data File
(ODF) Product Handbook and Glossary

7\. **[DESCRIPTION/USE]{.smallcaps}**: To define the content and
delivery requirements of each FDF/ODF, provide documented procedures
required for delivery of each product, and provide consistent product
standards.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** ATP plus 30 days.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Annual review with NASA and
updates as agreed to maintain documentation consistency with procedures,
products, and delivery requirements.

11\. **[REMARKS]{.smallcaps}**: Some terminology used in the DRD for ODF
and ODF associated data is being developed and is based on the FDF
counterpart to convey the nature of the data required.

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.6.2.1.3 and 1.6.2.1.3-c

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The FDF/ODF product handbook provides the
procedures, development process/product flows, dependencies, and quality
assurance requirements used in the development of FDF/ODF products. The
associated glossary provides detailed product definitions and delivery
requirements for each FDF/ODF product.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**

*Flight Requirements Document*

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The FDF/ODF Handbook and
product glossary shall include, but not be limited to, the functional
areas of FDF/ODF documentation as described below:

a\. FDF/ODF documentation - Procedures and related data for the
activities specified in the generic FDF/ODF Definition documents and the
flight-specific FDF/ODF Structure Sheets. The FDF contains primarily
crew procedures while the ODF includes both crew and ground executable
procedures where the latter effects onboard systems action.

b\. FDF/ODF Flight Set - Flight and flight-like sets will consist of
flight quality copies of the above procedures in book or electronic file
format as appropriate. Additionally, the flight set will contain
quantities and related FDF/ODF aids, e.g., cue cards, overlays,
flipbooks, maps, floppy disks, tethers, post-it-notes, cuff checklists,
etc., as specified in the flight/increment specific manifest.

c\. Associated documentation - Source data, rationale and as-flown
configuration information relating to the FDF/ODF, e.g., vehicle and
payload operations data, Flight Procedures Handbooks, PV/DSI records,
configuration records, etc.

d\. Specification standards and process documentation: Flight materials
and process configuration management plans, CPCB/SODF CB support plans,
and FDF/ODF configuration status for simulations and flight production
process plans.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes to paper
documents will be incorporated as required by complete revisions or page
change notices to keep documentation consistent with procedures,
products, and customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.6.2.1.3-c**

3\. **[DATA TYPE]{.smallcaps}**: 2/2 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Portable Onboard Computer (POC) Software
Loads Product Handbook and Glossary

7\. **[DESCRIPTION/USE]{.smallcaps}**: To define the content and
delivery requirements of each POC product, provide documented procedures
required for each POC product, and provide consistent product standards.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** 30 days after Authority to
Proceed (ATP)

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Annual review with NASA and
updates as agreed to keep documentation current with procedures,
products, and delivery requirements.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.6.2.1.3

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The POC Handbook provides the procedures,
development process/product flows, dependencies, and levels of quality
assurance used in the development of POC products. The associated POC
Product Glossary provides detailed product definitions and delivery
requirements for each POC product.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The POC Product Handbook
and Glossary shall include the functional areas of new POC applications
software, existing POC application maintenance and associated training.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page to keep documentation current
with procedures, products and customer lists.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.2.2.2-b

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Flight Design and Dynamics Training and
Certification Management Plan

7\. [DESCRIPTION/USE]{.smallcaps}: To provide insight into the flight
design training and certification process used for the flight design
team.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} 10 days after Authority to Proceed
(ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Updates as required to provide
consistency with DRD 1.6.2.2.2-c, *Flight Design Handbook and Product
Glossary*

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.2.2.2; DRD 1.6.2.2.2-c

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [[SCOPE]{.underline}]{.smallcaps}: This document shall specify the
curriculum and certification process at the flight design functional and
discipline level as described in SOW 1.6.2.2.2 (ascent, orbit, descent,
navigation, and flight integration).

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: To be defined by contractor
based upon the scope of this document.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue to provide
consistency with DRD 1.6.2.2.2-c.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.2.2.2-c

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Flight Design Handbook and Product Glossary

7\. [DESCRIPTION/USE]{.smallcaps}: To define the content of each flight
design product, provide documented procedures required for each flight
design product, and provide consistent product standards.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} 10 days after Authority to Proceed
(ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Updates as contractor requires
to keep documentation current with procedures, products and customer
lists

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.2.2.2

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: The Flight Design Handbook and Product
Glossary provide the procedures, detailed product definitions including
product development process flows, input data, procedural process,
output data, levels of quality assurance, and complete product customer
listings for each flight design product.

13.2 [[APPLICABLE DOCUMENTS]{.underline}: None]{.smallcaps}

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Flight Design Handbook
and Product Glossary shall include:

> a\. Procedures for all flight design processes.
>
> b\. Flight design product glossary.
>
> c\. Flight design product definition including requirements,
> input/output data, quality assurance levels and quality assurance
> process.
>
> d\. Process/product flows and dependencies.

Products shall include the functional areas of: ascent, orbit (including
rendezvous and proximity operations), descent, navigation (ground and
onboard), flight integration, and post-flight reconstruction.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Update by change page as
required to keep documentation current with procedures, products and
customer lists.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.2.2.3-a

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Standards for Flight Design and Dynamics
Software

7\. [DESCRIPTION/USE]{.smallcaps}: To define the maintenance and
development standards for all flight design software maintained by the
contractor.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} 10 days after Authority to Proceed
(ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As updates required to
standards

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.2.2.3

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: This document provides standards for all
flight design software maintained by the contractor. This includes
analysis, production, real time support and other application and
database software used in flight design, flight preparation, flight
execution, and post-flight reconstruction. Standards shall be provided
for new software development and modifications to existing software.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}

IRD-SE-1527T *Flight Design and Dynamics Software Management Plan*

JSC-27029 *Software Management Plan for Mission Control Center
Applications*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: Standards shall include
required documentation, software life cycle phases, user interfaces,
operations data policies, and other aspects of software development,
maintenance and programming standards.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.2.2.3-b

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Flight Design and Dynamics Software Management
Plan

7\. [DESCRIPTION/USE]{.smallcaps}: To define the contractor\'s policies,
procedures and management tools used to provide software sustaining
engineering activities and interfaces for flight design.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} 10 days after Authority to Proceed
(ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As required to maintain
currency with software management plans

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.2.2.3

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: This document shall define management
structures and responsibilities for all flight design software
sustaining engineering.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}

JSC-27029 *Software Management Plan for MCC Applications*

JSC-08211 *LSEAT Integration Support Plan*

JSC-23474 *MCC Critical Processor Certification Policy*

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The plan shall contain
management structures, and roles and responsibilities; procedures for
work planning and work tracking; software change processes; software
life cycle management; software configuration management; software
quality assurance; critical software certification process. Non-flight
critical software reporting is limited to applications used to generate
flight design products as defined in the Product Glossary.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.2.2.3-c

3\. [DATA TYPE]{.smallcaps}: 4 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Flight Design Software System Documentation

7\. [DESCRIPTION/USE]{.smallcaps}: The complete set of application
software life cycle documentation, including source and executable code,
for all FDD applications, under development or in production. This
includes test documents, test data, and test case libraries.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Upon Request

10\. [SUBMISSION FREQUENCY]{.smallcaps}: As required

11\. [REMARKS]{.smallcaps}: This request will be made via STF from NASA
for any documentation not available electronically on either the FADS or
SELS.

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.2.2.3, DRD 1.6.2.2.3-b

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: This document provides as requested either all
documentation for a specific application or a listing of the
documentation available for all flight design user applications
maintained under formal configuration management per the Flight Design
Software Management Plan (DRD 1.6.2.2.3-b) or discipline c.m. developed
under contract. This documentation is not required for previously
exempted applications unless specifically requested by the Government.

13.2 [[APPLICABLE DOCUMENTS]{.underline}:]{.smallcaps} None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: As required, a listing of
available documentation for all applications or specific software life
cycle documentation, as well as source code and executable code.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.2.2.3-d

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Flight Design and Dynamics Data Management
System Data Administration/Database Administration Plan

7\. [DESCRIPTION/USE]{.smallcaps}: To provide a plan for how FDD manages
data and databases owned by FDD, residing on the IPS and MCC computer
platform.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} 10 days after Authority to Proceed
(ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Upon request

11\. [REMARKS]{.smallcaps}: This plan is also used by NASA/DM to manage
GAF owned data.

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.2.2.3

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: This documents a plan for data administration
for all flight design computer hardware platforms used by FDD.

13.2 [[APPLICABLE DOCUMENTS]{.underline}:]{.smallcaps} None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Flight Design Data
Administration Plan for Platform Hardware shall include the following to
support the FDD and DM, ISS and Shuttle design, reconfiguration, and
operating processes:

> a\. Plans for using data archival and mass storage.
>
> b\. Data loss recovery plans.
>
> c\. Metrics that provide measures of user data management and mass
> storage resources.
>
> d\. Management organization and responsibility.
>
> e\. Operations data responsibilities.
>
> f\. Data ownership and control policy.
>
> g\. Data change process.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

**1. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.2.2.3-e**

**3. [DATA TYPE]{.smallcaps}: 2 4. [DATE REVISED:
09/01/98]{.smallcaps}**

**5. [PAGE]{.smallcaps}: 1/1**

**6. [TITLE]{.smallcaps}: Flight Design and Dynamics Operations Center
Software Engineering Strategic Plan**

**7. [DESCRIPTION/USE]{.smallcaps}: To provide an overall plan and
strategy for the upgrade of systems, tools, applications; to position
the Flight Design and Dynamics (FDD) software systems for responsiveness
to NASA programs; to provide the visions and paths for the evolution of
the FDD software systems; to be used by NASA and the contractor to make
decisions impacting FDD software long term goals and objectives.**

**8. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter**

**9. [INITIAL SUBMISSION:]{.smallcaps} Initial draft 10 days after
Authority to Proceed (ATP); final version approved at ATP plus 40 days**

**10. [SUBMISSION FREQUENCY]{.smallcaps}: Updates annually (no later
than April 1^st^) or as required by NASA**

**11. [REMARKS]{.smallcaps}:**

**12. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.2.2.3**

**13. [DATA PREPARATION INFORMATION]{.smallcaps}:**

**13.1 [SCOPE]{.underline}: The plan shall include goals and strategies
for FDD software addressing both short term (3-5 years) and long term
(5-10 years). This plan shall define the long-range plans for upgrading
FDD software to remain responsive to current and future NASA programs
that they must support.**

**13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**

**[NAS9-18000, IRD-SE-1526-T]{.smallcaps} *Flight Design and Dynamics
Software Strategic Plan***

**[STSOC PN -001264]{.smallcaps} *Flight Design and Dynamics Software
Strategic Plan***

**13.3 [[CONTENTS]{.underline}]{.smallcaps}: Domains that shall be
addressed by the strategic plan include management and engineering
processes, data management, technical upgrades, quality, information
management and communication, and growth, evolution, and
extensibility.**

**13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.**

**13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page or complete reissue.**

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.6.2.3-b**

3\. **[DATA TYPE]{.smallcaps}**: 2/2 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Flight Planning Product Handbook and
Product Glossary

7\. **[DESCRIPTION/USE]{.smallcaps}**: To define the content and
delivery requirements of each flight planning product, provide
documented procedures required for each flight planning product, and
provide consistent product standards.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** 30 days after Authority to
Proceed (ATP)

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Annual review with NASA and
updates as agreed to keep

documentation current with procedures, products, and delivery
requirements.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.6.2.3

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The Flight Planning Product Handbook
provides the procedures, development process/product flows,
dependencies, and levels of quality assurance used in the development of
flight planning products. The associated Flight Planning Product
Glossary provides detailed product definitions and delivery requirements
for each flight planning product.

13.2 [**[APPLICABLE DOCUMENTS]{.underline}**:]{.smallcaps} None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The Flight Planning
Product Handbook and Product Glossary shall include the functional areas
of:

a\. [Technical Assessments/Testing/Requirements]{.underline} to support
required flight-specific technical forums such as CIR, FPSR, IPT, POWG,
FOR, COWG, CoFR, and FRR.

\(1\) Attitude and Pointing Assessments and Reports.

\(2\) Documentation for Technical Forums.

\(3\) Requirements for Pointing Software Applications.

\(4\) Requirements for OTIS Software Applications.

b\. [Software Applications]{.underline} to support the flight planning
process. Documentation of the requirements for pointing and orbiter text
information system software applications. Development of additional
application software.

c\. [Flight-Specific Attitude and Pointing Products]{.underline} to
support the publication of the Basic and Final versions of the Flight
Data File and flight execution. These include the Attitude Timeline
(ATL), ATL databases, S-band and Ku-band communication data, blockage
diagrams, DAP configuration matrix, and other flight-specific attitudes.

d\. Planning Product: Pre-increment and tactical plans and process
definition.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Update by change page
as required to keep documentation current with procedures, products and
customer lists.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE:]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.2.3-d

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Systems Product Handbook and Product Glossary

7\. [DESCRIPTION/USE]{.smallcaps}: To define the content and delivery
requirements of each systems product, provide documented procedures
required for each systems product, and provide consistent product
standards.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} 30 days after Authority to Proceed
(ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Annual review with NASA and
updates as agreed to keep

documentation current with procedures, products, and customer lists.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.2.3

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [SCOPE]{.underline}: The Systems Product Handbook provides the
procedures, development process/product flows, dependencies, and levels
of quality assurance used in developing systems products. The associated
Systems Product Glossary provides detailed product definitions including
product input data, output data, delivery requirements, and complete
product customer listings for each systems product.

13.2 [[APPLICABLE DOCUMENTS]{.underline}: None]{.smallcaps}

13.3 [[CONTENTS]{.underline}:]{.smallcaps} Products shall include the
functional areas of electrical, environmental, propulsion, and thermal
systems analysis and consumables; sequential vehicle mass properties
analysis and management; robotics integration and analysis; photo/TV;
crew systems; in-flight maintenance; and station resource management.
Products are to be provided for design, analysis, flight planning and
integration, flight product development, vehicle consumables loading,
flight software reconfiguration, flight control systems technical
assessments, flight execution, and post-flight reconstruction.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Update by change page as
required to keep documentation current with procedures, products, and
customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. [**DPD NO**.]{.smallcaps}: 821 [**ISSUE**: REVISION 2]{.smallcaps}
2. [**DRD NO**.]{.smallcaps}: 1.6.2.4

3\. **[DATA TYPE]{.smallcaps}**: 2 4. [**DATE REVISED**:
08/02]{.smallcaps}

5\. **[PAGE]{.smallcaps}**: 1/2

6\. **[TITLE]{.smallcaps}**: Payload/Cargo Product/Services Handbook and
Glossary

7\. **[DESCRIPTION/USE]{.smallcaps}**: To define the content and
delivery requirements of each payload product or service, provide
documented procedures required for each payload/cargo product or
service, and provide consistent product or service standards.

8\. **DISTRIBUTION**: Per Contracting Officer\'s letter

9\. **INITIAL SUBMISSION**: 30 days after Authority to Proceed (ATP)

10\. **SUBMISSION FREQUENCY**: Annual review with NASA and updates as
agreed to keep documentation current with procedures, products, and
delivery requirements.

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.6.2.4

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[SCOPE]{.underline}**: The Payload/Cargo Product/Service Handbook
provides the procedures, development process/product flows,
dependencies, and levels of quality assurance used in developing
payload/cargo products and services. The glossary provides detailed
product definitions and delivery requirements for each payload product
or service.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The Payload/Cargo
Product/Service Handbook and Glossary shall include the functional areas
of:

> a\. Payload/Cargo Operations Documentation Cargo Systems Manuals,
> Payload Command Plan, Procedures Handbook, Operations Support
> Timelines, Joint Operations Interface Procedures, Operations Support
> Timelines, Preflight Notes of Interest, and the applicable
> documentation related to the ISS Assembly Operations.
>
> b\. Payload/Cargo Technical Reports/Inputs for typical forums such as
> CIR, FPSR, IPT, POWG, FOR, COWG, CoFR, and FRR.
>
> 1\. Payload/Cargo Assessments.
>
> 2\. Payload/Cargo Test Inputs and Reports.
>
> 3\. Review Packages for Payload/Cargo Technical Forums.
>
> 4\. PIP/MIP/Annex inputs.
>
> 5\. Payload/Cargo Operations Documentation Input.
>
> c\. Technical Forums Services required for Payload/Cargo Operations
>
> 1\. Forum Scheduling and logistics
>
> 2\. Meeting Documentation
>
> 3\. Data Package assembly and distribution
>
> d\. Operations Safety Documentation to provide payload safety
> compliance evaluation, ISS safety compliance evaluation, flight
> documentation safety evaluation (ISVR), 482 Flight Rule change request
> evaluation, and flight techniques/PRCB support, safety policy/process
> evaluation, S/MM Joint Safety Development/Compliance evaluation and
> safety activities status report.
>
> e\. Payload Facilities Definition and Implementation Data to provide
> for integration of payload customer requirements into Mission Control
> Center (MCC) facilities; and additional software computations,
> displays, and telemetry/command requirements that are required for
> flight preparation and flight execution using the MCC.

DRD CONTINUATION SHEET

**[TITLE]{.smallcaps}**: Payload/Cargo Product/Services Handbook and
Glossary [**DRD NO**.]{.smallcaps}: 1.6.2.4

**[DATA TYPE]{.smallcaps}**: 2 **[PAGE]{.smallcaps}**: 2/2

[13. **DATA PREPARATION INFORMATION (CONTINUED)**:]{.smallcaps}

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes should be
incorporated as required by page change to keep documentation current
with procedures, products, and customer lists.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.2.5-a

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/2

6\. [TITLE]{.smallcaps}: Flight Crew Operations Products Handbook and
Glossary

7\. [DESCRIPTION/USE]{.smallcaps}: To define the content and delivery
requirements of each flight crew product, provide documented procedures
required for each flight crew product, and provide product standards.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} 30 days after Authority to Proceed
(ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: Annual review with NASA and
updates as agreed to keep documentation current with procedures,
products, and delivery requirements.

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.2.5.1, 1.6.2.5.2,
1.6.2.5.4, 1.6.2.5.5.3, 1.6.2.5.5.6, 1.6.2.5.7

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [[SCOPE]{.underline}]{.smallcaps}: The Flight Crew Product Handbook
provides the procedures, development process/product flows, dependencies
and levels of quality assurance used in developing flight crew products.
The associated Flight Crew Product Glossary provides detailed product
definitions including product input data, output data, and delivery
requirements for each flight crew product.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The Flight Crew Product
Handbook and Flight Crew Product Glossary shall include the functional
areas of:

> a\. Operational impact assessments to develop positions on technical
> issues and provide operations planning assessments.
>
> b\. Technical evaluation of operational impacts and flight safety
> impacts of change requests (CRs).
>
> c\. PRCB and CCB action item technical evaluations.
>
> d\. Technical evaluation and impact assessment of proposed design or
> operational changes to flight software (FSW) user/operations notes.
>
> e\. Flight crew database management to include:
>
> 1\. Flight Software Database.
>
> 2\. Payload CR Database.
>
> 3\. Cargo Flight History Database.
>
> 4\. Flight Crew Equipment Database.
>
> f\. In-depth system status report to brief flight crew personnel on
> significant systems and/or operational modifications and proposed
> modifications.
>
> g\. CR/Engineering Change Request (ECR) development and presentation.
>
> h\. Assigned Flight Crew Equipment (FCE) Briefings.
>
> i\. Close-out Photographs.
>
> j\. New Crewmember Handbook
>
> k\. CAPCOM Handbook
>
> l\. Astronaut Support Personnel (ASP) Checklist (Generic and Flight
> Specific)
>
> m\. Ascent Switch List
>
> n\. Crew Equipment Interface Test (CEIT) Requirements

DRD CONTINUATION SHEET

[TITLE]{.smallcaps}: Flight Crew Products Handbook and Products Glossary
[DRD NO.]{.smallcaps}: 1.6.2.5-a

[DATA TYPE]{.smallcaps}: 3 [PAGE]{.smallcaps}: 2/2

[13. DATA PREPARATION INFORMATION (CONTINUED):]{.smallcaps}

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required by change page to keep documentation current
with procedures, products, and customer lists.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. [DPD NO.]{.smallcaps}: 821 [ISSUE: REVISION 1]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.6.2.5.4-a

3\. [DATA TYPE]{.smallcaps}: 3 4. [DATE REVISED: 09/01/98]{.smallcaps}

5\. [PAGE]{.smallcaps}: 1/1

6\. [TITLE]{.smallcaps}: Flight Crew Equipment (FCE) Management Plan

7\. [DESCRIPTION/USE]{.smallcaps}: To provide a management plan ensuring
that FCE items will be selected, procured, fit-checked, and any
discrepancies resolved prior to flight.

8\. [DISTRIBUTION]{.smallcaps}: Per Contracting Officer\'s letter

9\. [INITIAL SUBMISSION:]{.smallcaps} Three months after Authority to
Proceed (ATP)

10\. [SUBMISSION FREQUENCY]{.smallcaps}: One time and revisions as
required

11\. [REMARKS]{.smallcaps}:

12\. [INTERRELATIONSHIP]{.smallcaps}: SOW 1.6.2.5.4

13\. [DATA PREPARATION INFORMATION]{.smallcaps}:

13.1 [[SCOPE]{.underline}]{.smallcaps}: The Flight Crew Equipment (FCE)
Management Plan shall define all Space Shuttle Program (SSP) and
International Space Station Program (ISSP) FCE.

13.2 [[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}: None

13.3 [[CONTENTS]{.underline}]{.smallcaps}: The plan shall include the
following components:

> a\. Launch and entry suits and other crew-worn equipment delivery
> schedules; including schedules for delivery of crew clothing and other
> crew preference items.
>
> b\. All stowed and installed hardware fit checks.
>
> c\. Flight-specific stowage plans.
>
> d\. Major program schedule milestones such as Crew Equipment Interface
> Test (CEIT), Terminal Countdown Demonstration Test (TCDT), and Bench
> Reviews.

13.4 [[FORMAT]{.underline}]{.smallcaps}: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 [[MAINTENANCE]{.underline}]{.smallcaps}: Changes shall be
incorporated as required, by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: 821 [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: **1.6.4-a**

3\. **[DATA TYPE]{.smallcaps}**: 2 4. **[DATE REVISED]{.smallcaps}**:

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: Project Management Plan

7\. **[DESCRIPTION/USE]{.smallcaps}**: To describe significant new
capability development, capability upgrades, or other modifications to
existing contractor managed systems.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** As required

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: As required

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.6.4

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

13.1 **[[SCOPE]{.underline}]{.smallcaps}**: The Project Management Plan
shall describe the high level objectives, cost estimates, schedules, and
management plans/processes for significant enhancements or modifications
to contractor managed systems.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**: None

13.3 **[[CONTENTS]{.underline}]{.smallcaps}**: The Project Management
Plan shall consist of the following:

a\. Project objectives description.

b\. Project management team organization.

c\. Baseline control process description.

d\. Risk management plan.

e\. Project milestone definition.

f\. Project cost estimates.

g\. Project schedule estimates.

h\. Requirements verification and validation plan.

i\. Operations transition plan.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required, by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. **[DPD NO.]{.smallcaps}**: 821 **[ISSUE:]{.smallcaps}** REVISION 2
2. [**DRD NO**.]{.smallcaps}: **1.6.4.2-a**

3\. **[DATA TYPE]{.smallcaps}**: 3 4. **[DATE REVISED:
08/02]{.smallcaps}**

5\. **[PAGE]{.smallcaps}**: 1/1

6\. **TITLE:** Integrated Training Facility Simulation Systems
Operations Handbook

[7. **DESCRIPTION/USE**]{.smallcaps}: Defines the standard operating
procedures, processes, and guidelines for the operating positions,
maintenance coordination, and users of the Shuttle Mission Training
Facilities (SMTF) managed by the contractor

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer's letter

9\. **[INITIAL SUBMISSION]{.smallcaps}**: Before the end of FY98.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: Annually

11\. **[REMARKS]{.smallcaps}**:

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.6.4, 1.6.4.2

13\. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

[13.1 **[SCOPE]{.underline}**]{.smallcaps}: This document defines the
standard operating procedures, processes, and guidelines at the Shuttle
training facilities, including the Shuttle Mission Simulators (SMS),
Guidance & Navigation Simulator (GNS). An operation's appendix will be
provided for the trainers listed below when an operations interface is
established with existing SMTF resources. The trainers include Single
System Trainers (SST), Prototype Part-Task Trainer (P2T2), Flight
Controller Trainer (FCT), Playback Trainer (PBT), Payload Trainer (PLT),
Crew Software Trainer (CST), and other trainers developed to provide
Shuttle systems training.

13.2 **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**: None

3.  **[[CONTENTS]{.underline}]{.smallcaps}**: The following types of
    procedures shall be included: Administration/management, general,
    anomaly administration, software/hardware, power, safety/emergency,
    other operational support.

13.4 **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall conform to
delivery media formats and electronic data formats per DRD 1.1.4.1-e,
Data Management Plan, or per Contracting Officer approval. General
procedures shall be identified that apply to all trainers. Each trainer
shall have a section, which identifies unique procedures. Each procedure
shall define the purpose, participants, and procedure steps.

13.5 **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes shall be
incorporated as required by change page or complete reissue.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

1\. **[DPD NO.]{.smallcaps}**: **821** [**ISSUE:** BASIC]{.smallcaps} 2.
**[DRD NO.]{.smallcaps}**: 1.8.5**-a**

3\. **[DATA TYPE]{.smallcaps}**: 2 4. **[DATE REVISED]{.smallcaps}**:

5.  **[PAGE]{.smallcaps}**: 1/1

6\. **[TITLE]{.smallcaps}**: International Space Station Program (ISSP)
Meeting Support Process Definition

7\. **[DESCRIPTION/USE]{.smallcaps}**: To define processes for ISSP
meeting support.

8\. **[DISTRIBUTION]{.smallcaps}**: Per Contracting Officer\'s letter

9\. **[INITIAL SUBMISSION:]{.smallcaps}** Authority to Proceed plus 120
days.

10\. **[SUBMISSION FREQUENCY]{.smallcaps}**: One initial release and
updates as required (not to exceed every six months).

11\. **[REMARKS]{.smallcaps}**: N/A

12\. **[INTERRELATIONSHIP]{.smallcaps}**: SOW 1.8.5

13. **[DATA PREPARATION INFORMATION]{.smallcaps}**:

```{=html}
<!-- -->
```
1.  **[SCOPE]{.underline}**: Documented and baseline procedures used to
    provide meeting support to the ISSPO.

2.  [**[DEPENDENCIES:]{.underline}**]{.smallcaps} None.

3.  **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}**: N/A.

4.  **[[CONTENTS]{.underline}]{.smallcaps}**: Includes the following
    meeting support procedures:

> a\. Operations
>
> b\. Mission Integration
>
> i\) Stage Integration
>
> ii\) Launch Package Management and Increment Management
>
> c\. Payloads

5.  **[[FORMAT]{.underline}]{.smallcaps}**: Contractor shall deliver the
    document in electronic format.

6.  **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes to paper
    documents will be incorporated as required by complete revisions or
    page change notices to keep documentation consistent with
    procedures, products, and customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

**1. [DPD NO.]{.smallcaps}: 821 [ISSUE: BASIC]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.8.6-a**

**3. [DATA TYPE]{.smallcaps}: 2 4. [DATE REVISED]{.smallcaps}:**

5.  **[PAGE]{.smallcaps}: 1/1**

**6. [TITLE]{.smallcaps}** International Space Station (ISS) Logistics &
Maintenance (L&M) Technical Data & Documentation (TD&D)

**7. [DESCRIPTION/USE]{.smallcaps}: To** provide Illustrated Parts
Breakdowns (IPBs) and Source Data & Documentation (SD&D) for ISSP
on-orbit maintenance references for each flight.

**8. [DISTRIBUTION]{.smallcaps}:** Per Contracting Officer\'s letter

**9. [INITIAL SUBMISSION:]{.smallcaps}** Authority to Proceed per line
number 10.

**10. [SUBMISSION FREQUENCY]{.smallcaps}:** Scheduled for each U.S.
flight at L- 18 months, L-12 months, and L- 6 months**.**

**11. [REMARKS]{.smallcaps}:** N/A

**12. [INTERRELATIONSHIP]{.smallcaps}:** SOW 1.8.6

13. **[DATA PREPARATION INFORMATION]{.smallcaps}:**

```{=html}
<!-- -->
```
1.  **[SCOPE]{.underline}:** The TD&D will be provided as an initial
    product at L -18 months, an interim product at L-12 months and a
    final product at L-6 months. When source data is not available, the
    documents will contain the annotation "To Be Supplied (TBS)". The
    TD&D do not include IP and Boeing Prime developed hardware.

2.  **[[DEPENDENCIES:]{.underline}]{.smallcaps}** Product delivery
    schedule is dependent on the Shuttle ISS flight schedule. Source
    data to complete TD&D products are provided as GFD.

3.  **[[APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}:** Integrated
    Logistics Support Plan D684-10041-1, Volume 1 Books 1 and4;
    MIL-F-38807B (USAF), dated April 10, 1991; MIL-M-49502, dated
    November 6, 1990; MIL-STD 335; MIL-STD-1388-2A**.**

4.  **[[CONTENTS]{.underline}]{.smallcaps}:** The IPB shall include the
    documentation as described below:

> a**.** IPB Figures - Pictorial representations of Orbital Replaceable
> Units and in-situ maintenance hardware items and, at a minimum, must
> provide Isometric drawings. Still photography will be utilized when
> available.
>
> b\. Reference Tables - Contains pertinent information for parts
> identified for repair.

c.  Logistics Support Analysis Control Numbers (LCNs) - LCNs in
    alphanumerical sequence with a cross-reference to all figures
    containing that LCN.

```{=html}
<!-- -->
```
5.  **[[FORMAT]{.underline}]{.smallcaps}:** Contractor shall deliver
    media formats and electronic data formats required to support
    integration of the delivered product into the Prime Contractor's
    documents and into the NASA electronic database.

6.  **[[MAINTENANCE]{.underline}]{.smallcaps}**: Changes to paper
    documents will be incorporated during scheduled deliveries by
    complete revisions or page change notices to keep documentation
    consistent with procedures, products, and customer lists.

**DATA REQUIREMENTS DESCRIPTION (DRD)**

**1. [DPD NO.]{.smallcaps}: 821 [ISSUE: BASIC]{.smallcaps} 2. [DRD
NO.]{.smallcaps}: 1.8.6-c**

**3. [DATA TYPE]{.smallcaps}: 2 4. [DATE REVISED]{.smallcaps}:**

5.  **[PAGE]{.smallcaps}: 1 of 2**

**6. [TITLE]{.smallcaps}:** International Space Station Program (ISSP)
Logistics & Maintenance (L&M) Handbook and Product Glossary

**7. [DESCRIPTION/USE]{.smallcaps}:** To define the content and delivery
requirements of L&M products, provide documented procedures, and to
establish consistent standards.

**8. [DISTRIBUTION]{.smallcaps}:** Per Contracting Officer\'s letter

**9. [INITIAL SUBMISSION:]{.smallcaps} Authority** to Proceed plus 120
days.

**10. [SUBMISSION FREQUENCY]{.smallcaps}:** One initial release and
updates as required (not to exceed every six months).

**11. [REMARKS]{.smallcaps}:** N/A

**12. [INTERRELATIONSHIP]{.smallcaps}:** SOW 1.8.6

13. **[DATA PREPARATION INFORMATION]{.smallcaps}:**

```{=html}
<!-- -->
```
1.  **[SCOPE]{.underline}:** The L&M Handbook provides the procedures,
    development process/product flows and identifies dependencies, for
    development of L&M products. The associated L&M Product Glossary
    provides detailed product definitions and delivery requirements.

2.  **[[DEPENDENCIES:]{.underline}]{.smallcaps}** None.

**[13.3 [APPLICABLE DOCUMENTS]{.underline}]{.smallcaps}:** Integrated
Logistics Support Plan, D684-10041-1 Volume 1, Books 1 through 10; SPIPs
Vol. 1 through 10; plus those identified in each L&M sub-task.

**[13.4 [CONTENTS]{.underline}]{.smallcaps}:** The L&M Handbook and
product glossary shall include the functional areas of L&M as described
below:

> a\. Crew Provisioning (CP) documentation - Procedures and related
> activities for development of the associated products consisting of
> Integrated Crew Provisions requirements, Crew Provisioning Management
> Plan (CPMP) maintenance, Crew Provisioning Working Group (CPWG) plan
> maintenance, Joint Crew Provisioning Catalog (JCPC) maintenance, and
>
> Crew Provisioning Policy (CPC) updates.
>
> b**.** Government Furnished Equipment (GFE) - Quarterly LSAR data
> deliveries, review of Change requests, and Action Item assessments.

c.  Inventory Management System (IMS) - Space Station Interior/Exterior
    Operational Location Coding System, SSP 50375 maintenance; ISS
    Inventory Management System Label Specification, SSP 50007
    maintenance; revision/update SPIP Vols. 5, 8, and 9; IMS label
    production; IMS hardware flight certification documentation.

> d\. Maintenance & Resupply (M&R) - Incremental Definition Requirements
> Documents (IDRD), Annex 2; Tools documentation; L&M Operations &
> Support Plan (L&MOSP) development and maintenance; review of Change
> requests; Action Item assessments.

e\. Logistics Engineering Analysis (LEA) - FCA/PCA records, LSAR Comment
Database, TD&D

Comment Database, ORU list, review of Change requests, and Action Item
assessments.

f\. Partner Integration - SPIP Vol. 5 revisions and IDRD annex updates

g.  g\. Supply Support - Technical assessments of DD250s, LSAR H & H1
    data record reviews, and

FCA/PCA configuration audits.

**[13.5 [FORMAT]{.underline}]{.smallcaps}:** Contractor shall deliver
media formats and electronic data formats required to support
integration of the delivered products into the appropriate NASA records.

**[13.6 [MAINTENANCE]{.underline}]{.smallcaps}: Changes** to paper
documents will be incorporated by complete revisions or page change
notices to keep documentation consistent with procedures, products, and
customer lists.