######### SECTION A

######### 

######### SOLICITATION/CONTRACT FORM

A.2 DETAILED TABLE OF CONTENTS

[PAGE]{.underline}

SECTION A -- SOLICITATION/CONTRACT FORM, SF33

A.1 STANDARD FORM 33 A-1

A.2 DETAILED TABLE OF CONTENTS A-2

SECTION B -- SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 ESTIMATED COST AND AWARD FEE B-1

B.2 CONTRACT FUNDING B-1

SECTION C -- DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

C.1 STATEMENT OF WORK C-1

SECTION D -- PACKAGING AND MARKING

D.1 PACKAGING, HANDLING, AND TRANSPORTATION D-1

SECTION E -- INSPECTION AND ACCEPTANCE

E.1 LISTING OF CLAUSES INCORPORATED BY REFERENCE E-1

E.2 HIGHER-LEVEL CONTRACT QUALITY REQUIREMENT E-1

E.3 MATERIAL INSPECTION AND RECEIVING REPORT E-1

E.4 INSPECTION AND ACCEPTANCE E-2

E.5 QUALITY ASSURANCE SURVEILLANCE PLAN E-2

SECTION F -- DELIVERIES OR PERFORMANCE

F.1 LISTING OF CLAUSES INCORPORATED BY REFERENCE F-1

F.2 BILLS OF LADING F-1

F.3 COMPLETION OF WORK F-2

F.4 OPTION TO EXTEND COMPLETION DATE F-2

F.5 SHIPPING INSTRUCTIONS F-4

F.6 FLIGHT ITEM F-5

SECTION G -- CONTRACT ADMINISTRATION DATA

G.1 LISTING OF CLAUSES INCORPORATED BY REFERENCE G-1

G.2 AWARD FEE FOR SERVICE CONTRACTS G-1

G.3 SUBMISSION OF VOUCHERS FOR PAYMENT G-2

G.4 DESIGNATION OF NEW TECHNOLOGY REPRESENTATIVE G-4

AND PATENT REPRESENTATIVE

G.5 TECHNICAL DIRECTION G-4

G.6 LIST OF GOVERNMENT-FURNISHED PROPERTY G-5

G.7 SECURITY/BADGING REQUIREMENTS FOR FOREIGN G-5

NATIONAL VISITORS AND EMPLOYEES/REPRESENTATIVES

OF FOREIGN CONTRACTORS

G.8 UNDERSTANDING WITH RESPECT TO COST VARIATIONS G-6

G.9 USE OF JSC CALIBRATION LABORATORY G-7

G.10 IDENTIFICATION OF EMPLOYEES G-7

G.11 REPAIR OF GOVERNMENT PROPERTY G-7

G.12 INSTALLATION-ACCOUNTABLE GOVERNMENT PROPERTY G-8

G.13 LIST OF INSTALLATION-ACCOUNTABLE PROPERTY AND G-10

SERVICES

SECTION H -- SPECIAL REQUIREMENTS

H.1 LISTING OF CLAUSES INCORPORATED BY REFERENCE H-1

H.2 KEY PERSONNEL AND FACILITIES H-1

H.3 REPRESENTATION, CERTIFICATION, AND OTHER STATEMENTS H-2

H.4 SMALL BUSINESS SUBCONTRACTING GOALS H-2

H.5 LIMITED RELEASE OF CONTRACTOR CONFIDENTIAL BUSINESS H-3

INFORMATION

H.6 LEVEL-OF-EFFORT H-3

H.7 SPECIAL PROVISION FOR CONTRACT CHANGE H-4

H.8 CONTRACT EXTENSION RESULTING FROM PROTESTS H-4

SECTION I -- CONTRACT CLAUSES

I.1 LISTING OF CLAUSES INCORPORATED BY REFERENCE I-1

I.2 APPROVAL OF CONTRACT I-4

I.3 PAYMENT FOR OVERTIME PREMIUMS I-4

I.4 DRUG-FREE WORKPLACE I-5

I.5 STATEMENT OF EQUIVALENT RATES FOR FEDERAL HIRES I-6

I.6 RIGHTS IN DATA-GENERAL I-7

I.7 TAXES-FOREIGN COST-REIMBURSEMENT CONTRACTS I-11

I.8 SUBCONTRACTS FOR COMMERCIAL ITEMS I-11

I.9 SUBMISSION OF COMMERCIAL TRANSPORTATION BILLS TO I-12

THE GENERAL SERVICES ADMINISTRATION FOR AUDIT

I.10 CLAUSES INCORPORATED BY REFERENCE I-13

I.11 SECURITY CLASSIFICATION REQUIREMENTS I-13

I.12 SECURITY REQUIREMENTS FOR UNCLASSIFIED I-13

INFORMATION TECHNOLOGY RESOURCES

I.13 OMBUDSMAN I-16

I.14 MINIMUM INSURANCE COVERAGE I-16

SECTION J -- LIST OF ATTACHMENTS

J.1 WAGE DETERMINATION J-1:1

J.2 AWARD FEE PLAN J-2:1

J.3 SMALL BUSINESS SUBCONTRACTING PLAN J-3:1

J.4 SAFETY AND HEALTH PLAN J-4:1

J.5 CONTRACT SECURITY CLASSIFICATION SPECIFICATION J-5:1

J.6 LIST OF GOVERNMENT-FURNISHED PROPERTY J-6:1

J.7 LIST OF INSTALLATION-ACCOUNTABLE PROPERTY J-7:1

J.8 DATA REQUIREMENTS DESCRIPTION LIST J-8:1

J.9 DATA REQUIREMENTS DESCRIPTION SHEETS J-9:1

J.10 PHASE-IN PLAN J-10:1

##  

## B. 1 ESTIMATED COST AND AWARD FEE (NASA 1852.216‑85) (SEP 1993)

\(a\) The estimated cost of this contract is \$223,796,618. The maximum
available award fee, excluding base fee, if any, is \$20,282,789**.**
The base fee is \$0. Total estimated cost, base fee, and maximum award
fee are \$244,056,437.

(b) The estimated cost and award fee for this contract is divided as
    follows. Award Fee is not applicable for the Phase-In period.

> Estimated Cost (excluding Phase-In Costs) \$223,645,391
>
> Phase-In Cost \$151,227
>
> Total Estimated Cost (including Phase-In Costs) \$223,796,618
>
> Maximum Available Award Fee \$20,282,789
>
> TOTAL CONTRACT VALUE \$244,079,407

(End of clause)

## B.2 CONTRACT FUNDING (NASA 1852.232‑81) (JUN 1990)

\(a\) For the purpose of cost, exclusive of fee, in accordance with the
Limitation of Funds clause, the total amount allotted by the Government
to this contract for all efforts is \$116,803,718.00. This allotment is
for all MSOC efforts and covers the following estimated period of
performance September 30, 2003 to July 8, 2005.

\(b\) An additional amount of \$10,679,537.27 is obligated under this
contract for all efforts for payment of fee.

(End of clause)

## C. 1 STATEMENT OF WORK 

The contractor shall, in a manner consistent with and subject to the
terms and conditions hereof, furnish all resources necessary to provide
Mission Support Operations in accordance with the following Statement of
Work. The Contractor shall perform phase-in activities in accordance
with the Phase-In Plan set forth in Section J, Attachment J-10.

(End of clause)

**Mission**

**Support Operations**

**Contract**

**Statement of Work**

1.  **Mission Support Operations Contract (MSOC)**

    1.  Program Management

    2.  Financial & Contract Performance

1.2.1 Financial Interface

1.2.1.1 Financial Reporting Form NF533

1.2.1.2 Integrated Financial Management Program (IFMP)

1.2.1.3 Assorted Financial Information

1.2.2 Technical Interfaces

1.2.2.1 Earned Value

1.2.2.2 Information Technology (I/T) Plan

3.  Administrative Services & Support

    1.  Administrative Services

        1.  Human Resources / Personnel Management

        2.  Contract Administration

        3.  Subcontract Administration

        4.  Procurement

    2.  Support Services

        1.  Security

        2.  Safety and Health Management

        3.  Environmental Management

        4.  Quality Assurance

4.  Data Requirements Descriptions (DRD's) and Applicable Documents

    1.  DRD's documenting contractors systems

    2.  Applicable Documents

5.  Technical Services & Support

    1.  Mission Services Function

1.5.1.1 Mission Control Center Houston (MCC-H), Houston Support Room
(HSR), and Backup Command and Control (BCC)

1.  Management

2.  Modification & Systems Engineering

3.  Maintenance & Sustaining Engineering

4.  Operations

5.  Facility Operations

6.  Performance Standards

7.  Test & Checkout

8.  Interface Support

9.  Certification and Training

10. Metrics/Data & Reports

11. Requirements Documentation & Facility DRD's

```{=html}
<!-- -->
```
1.  Integrated Planning System (IPS)

    1.  Management

    2.  Modification & Systems Engineering

    3.  Maintenance & Sustaining Engineering

    4.  Operations

    5.  Facility Operations

    6.  Performance Standards

    7.  Test & Checkout

    8.  Interface Support

    9.  Certification and Training

    10. Metrics/Data & Reports

    11. Requirements Documentation & Facility DRD's

```{=html}
<!-- -->
```
2.  Mission Support Services Function

    1.  Management

    2.  Modification & Systems Engineering

    3.  Maintenance & Sustaining Engineering

    4.  Operations

    5.  Facility Operations

    6.  Performance Standards

    7.  Test & Checkout.

    8.  Interface Support

    9.  Certification, Training & Travel

    10. Metrics & Reports

    11. Requirements Documentation & DRD's

    ```{=html}
    <!-- -->
    ```
    1.  Common Development Environment (CDE)

        1.  Management

        2.  Modification & Systems Engineering

        3.  Maintenance & Sustaining Engineering

        4.  Operations

        5.  Facility Operations

        6.  Reserved

        7.  Test & Checkout

        8.  Interface Support

        9.  Certification and Training

        10. Metrics & Reports

        11. Requirements Documentation & DRD's

    2.  Ground Systems Development Environment (GSDE)

        1.  Management

        2.  Modification & Systems Engineering

        3.  Maintenance & Sustaining Engineering

        4.  Operations

        5.  Facility Operations

        6.  Reserved

        7.  Test & Checkout

        8.  Interface Support

        9.  Certification and Training

        10. Reserved

        11. Requirements Documentation & DRD's

3.  Site Support Services

    1.  Emergency Operations Center (EOC)

        1.  Management

        2.  Modification & Systems Engineering

        3.  Maintenance & Sustaining Engineering

        4.  Operations

        5.  Facility Operations

        6.  Performance Standards

        7.  Test & Checkout

        8.  Interface Support

        9.  EOC IT Security Plan

        10. Reserved

        11. Reserved

4.  Program Support Services (Level-of-Effort)

    1.  GSCB

        1.  Reserved

1.5.4.1.2 Reserved

2.  Security Analysis and Response Team (SART)

    1.  Security Engineering Support

    2.  Documentation Support

    3.  Travel

3.  Network and Communications Analysis Integration Team (NACAIT)

    1.  Network Program Requirement Document (NPRD) Documentation
        Support

    2.  Travel

4.  Reserved

    1.  Reserved

    2.  Reserved

5.  Program Requirements Document (PRD)

    1.  PRD Documentation Support

    2.  Travel

6.  Human Space Flight (HSF) Network Operations Integration

    1.  Certification of Flight Readiness (COFR)

    2.  Project Management Documentation Support

    3.  Interface Control Document (ICD) Support

7.  Program Level Change Engineering Support & Integration

    1.  System Engineering

    2.  Reserved

1.5.4.8 Architectural and Engineering Support

1.5.4.8.1 Documentation

1.5.4.8.2 Travel

5.  Technical Administration Support

    1.  Resources

        1.  Property -- Government Furnished Equipment (GFE)

        2.  Property -- capital

        3.  Technical documentation

        4.  Equipment Replacement

    2.  Configuration Management

        1.  Change Authorization & Tracking

        2.  Anomaly Status & tracking

        3.  Technical documentation

    3.  Safety

        1.  Personnel

        2.  Physical

        3.  Safety, Reliability and Quality Assurance (SR&QA)

        4.  Environmental

    4.  Security

        1.  Reserved

        2.  Personnel

        3.  Information Technology (IT) Security

        4.  Communications Security (COMSEC) and Classified Data
            Computation

1.5.5.4.5 Physical

1.5.5.4.6 Reserved

List of Appendices

Appendix A Acronym List

Appendix B Glossary

1.0 Mission Support Operations Contract (MSOC)

The goals and expectations for this contract are as follows:

-   Provide excellent quality and reliable mission and support services
    at a minimum cost.

-   Define mission and data service responsibility and accountability.

-   Define and integrate process and facility improvements for the
    purposes of reducing costs without the reduction in SOW
    requirements.

1.1 Program Management

The contractor shall:

-   Perform all the necessary program management functions including
    technical and business management in order to plan, implement,
    track, report and deliver the required services described in this
    SOW.

-   Provide all personnel and other resources, except as otherwise
    specified in the contract, necessary to accomplish these functions.

-   Prepare and submit management reports and support program management
    reviews (DRD-MSOC-JSC-0012) in accordance with the Johnson Space
    Center (JSC) Contract Work Breakdown Structure (CWBS), (DRD
    MSOC-JSC-0001).

-   Submit a Management Plan (DRD MSOC-JSC-0002), Risk Management Plan
    (DRD MSOC-JSC-0003), Contract Configuration Management Plan (DRD
    MSOC-JSC-0004), and a Phase-in Plan (DRD MSOC-JSC-0005).

All program management systems and processes shall be operational on the
contract start date.

1.2 Financial and Contract Performance

The contractor shall provide and maintain a financial and contract
performance management system for the planning, tracking, accumulation,
monitoring, contract cost and contract performance to meet the
budgeting, cost reporting, billing and disclosure requirements of the
contract. All financial and contract performance monitoring systems
shall be fully operational at contract start. Financial and contract
performance management systems:

-   Shall provide financial and contract performance reporting 10
    working days after the close of the contractor's monthly accounting
    calendar.

-   Shall provide all information at a total government cost.

-   Shall provide all information consistent with the Contract Work
    Breakdown Structure (CWBS).

-   Shall be capable of providing information at assorted CWBS levels.

-   All systems shall be capable of separate tracking of financial
    adjustments for all external contracts using National Aeronautics
    and Space Administration (NASA) resources.

Financial, contract and administrative management systems shall be
integrated, with changes formally approved/authorized through defined
and documented procedures.

The contractor shall provide Financial Management Reports (DRD
MSOC-JSC-0020), Wage/Salary and Fringe Benefit Data (DRD MSOC-JSC-0021)
and Workforce Reports (DRD MSOC-JSC-0024).

1.2.1 Financial Interface

The contractor's financial system shall interface with the approved
governments systems, and be capable of cost allocation to customers
based on government approved allocations methodologies. Cost reporting
shall be compatible and capable of uploading cost accrual information
into NASA's Integrated Financial system and shall automatically map to
NASA's program coding structure.

1.2.1.1 Financial Reporting Form NF533

Reports shall fully comply with the most current version of NASA
Procedures and Guidelines (NPG) 9501.2C. Any supplemental cost data
shall be reconcilable back to the NF533 for the same accounting period.

1.2.1.2 Integrated Financial Management Program (IFMP)

The Contractor's financial system shall support NASA's full cost
accounting and enterprise funding. Customer Report DRD-0015 will provide
full cost information.

1.2.1.3 Assorted Financial Information

The contractor shall provide financial planning and historical
information along with the technical support information as required to
support the Human Space Flight (HSF) budget process (e.g. Program
Operating Plan (POP), monthly operating budget and performance call,
Construction of Facilities (CoF) budget calls) and support special
requests for budget impacts. The contractor shall provide a Fiscal Year
Operating Plan (DRD MSOC-JSC-0022), a Program Operating Plan (POP) (DRD
MSCO-JSC-0022) and Travel Plan (DRD MSOC-JSC-0023) in support of this
assorted financial information requirement. NASA shall specify the
format and content of the contractor's input and supporting rationale
guidelines.

1.2.2 Technical Interfaces

The contractor's technical system shall interface with the approved
Government systems.

1.2.2.1 Earned Value

The contractor shall provide Performance Measurement Plan and Reports
(DRD MSOC-JSC-0006). The contractor shall manage and report technical
performance measurement of the work using an integrated and time
correlated cost, schedule, content and quality performance management
system. This system shall:

-   Comply with the latest version of NASA Policy Directive 9501.3
    Performance Measurement System Criteria.

-   Develop, maintain and report technical performance metrics and data
    reports.

1.2.2.2 Information Technology (I/T) Plan

The contractor shall provide an Information Technology Plan and Reports
(DRD MSOC-JSC-0010).

The contractor shall provide a Government Property Management Plan (DRD
MSOC-JSC-0008) to describe the method of administering Government
property.

1.3 Administrative Services and Support

The contractor shall provide administrative support and services to
address the management; administration, operations and reporting
required in support of the contractor's personnel.

1.3.1 Administrative Services

The contractor shall provide the administrative services required to
support the contract's personnel and provide effective contract
administrative services.

1.3.1.1 Human Resources / Personnel Management

The contractor shall provide for the administration, management,
operations and documentation support of the contractor's personnel.

1.3.1.2 Contract Administration

The contractor shall provide contract administration to address the
management, operations and documentation requirements for the management
of this contract. Communications of these requirements, with NASA, shall
use the Transmittal/Information Request Form (TIRF), JSC Form JF994. The
TIRF will be used for general communications, submission of
documentation, and as a cover for all technical direction. The TIRF will
also be used as a receipt/acknowledgment of and response to direction.

1.3.1.3 Subcontract Administration

The contractor shall provide, document and implement a Small,
Small-Disadvantaged, and Small Women-Owned Business Subcontracting Plan
and Reports (DRD MSOC-JSC-0009).

The contractor shall include in the Management Plan (DRD MSOC-JSC-0002)
subcontract administration.

1.3.1.4 Procurement

The contractor shall provide procurement services to meet contract
administration and technical support requirements.

1.3.2 Support Services

The contractor shall provide the support services required to comply
with all city, state, Federal, international and NASA interface,
management and reporting requirements for the services required to
protect the safety, security, health and quality of the work environment
under this contract.

1.3.2.1 Security

The contractor shall provide:

-   A Contractor Security Management Plan (DRD MSOC-JSC-0080).

-   An Emergency Preparedness and Disaster Recovery Plan (DRD
    MSOC-JSC-0011) for all facilities and systems within the scope of
    this contract.

The contractor shall establish effective and comprehensive industrial,
physical, administrative, information, communications and Information
Technology (IT) security programs in accordance with the National
Industrial Security Program Operating Manual, NASA site-specific
regulations and DD Form 254.

In addition to any other requirements of this contract, all individuals
who perform tasks as a system administrator or have authority to perform
tasks normally performed by system administrator shall be required to
demonstrate knowledge appropriate to those tasks. This demonstration,
referred to as the NASA System Administrator Security Certification, is
a NASA funded two-tier assessment to verify that system administrators
are able to -

1\. Demonstrate knowledge in system administration for the operating
systems for which they have responsibility.

2\. Demonstrate knowledge in the understanding and application of
Network and Internet Security.

Certification is granted upon achieving a score above the certification
level on both an Operating System test and the Network and Internet
Security Test. The Certification earned under this process will be valid
for three years. The criteria for this skills assessment has been
established by the NASA Chief Information Officer. The objectives and
procedures for this certification can be obtained by contacting the IT
Security Awareness and Training Center at (216) 433-2063.

A system administrator is one who provides IT services, network
services, files storage, web services, etc. to someone else other than
themselves and takes or assumes the responsibility for the security and
administrative controls of that service or machine. A lead system
administrator has responsibility for information technology security
(ITS) for multiple computers or network devises represented within a
system; ensuring all devices assigned to them are kept in a secure
configuration (patched/mitigated); and ensuring that all other system
administrators under their lead understand and perform ITS duties. An
individual that has full access or arbitrative rights on a system or
machine that is only servicing themselves does not constitute a \"system
administrator\" since they are only providing or accepting
responsibility for their system. An individual that is only servicing
themselves is not required to obtain a System Administrator
Certification.

1.3.2.2 Safety and Health Management

To ensure compliance with pertinent NASA policies and requirements and
Federal, state and local regulations for safety health, and emergency
preparedness, the contractor shall develop, document and implement a
safety and health program.

The contractor shall:

-   Develop and implement an approach to ensure the protection of
    personnel, property, equipment, and the environment in contractor
    products and activities generated in support of institutional and
    space flight program objectives.

-   Submit for NASA approval their Safety and Health Plan (DRD
    MSOC-JSC-0030).

-   On a yearly basis provide a Safety and Health Program Self
    Evaluation (DRD MSOC-JSC-0031).

-   Provide Monthly Safety and Health Metrics (DRD MSOC-JSC-0032) for
    NASA review.

To ensure compliance with pertinent NASA policies and requirements and
federal, state, and local regulations for safety, health, environmental
protection, and fire protection, the contractor shall develop and
implement a safety and health program in accordance with a NASA-approved
safety and health plan.

The contractor shall:

-   Perform tasks to ensure the protection of personnel, property,
    equipment, and the environment in contractor products and activities
    generated in support of institutional and space flight program
    objectives.

-   Implement system safety engineering tasks for flight and
    institutional program activities and products in accordance with the
    schedule and applicable flight and institutional requirements as
    documented in the contractor's System Safety Program Plan (SSPP),
    (DRD MSOC-JSC-0033), which are approved by NASA.

-   Develop and implement risk management techniques (including risk
    assessment) to be applied to hazards derived from analyses of
    activities and products for the purpose of eliminating or
    controlling hazards as specified in NASA policies and requirements
    for hazard reduction. The JSC Safety and Health Handbook provides
    detailed requirements and instructions regarding safety and health
    procedures and policies at JSC and is incorporated by reference into
    all JSC contracts when performance is on site at a JSC facility.

-   Provide a Safety Lessons Learned (DRD MSOC-JSC-0046) for each
    reported safety incident.

1.3.2.3 Environmental Management

The contractor is responsible for complying with all applicable
international, Federal, state, and local environmental requirements, and
for submitting to the appropriate environmental regulatory agencies any
required official correspondence (e.g., permits/permit applications,
negotiated agreements, requests for information from/to regulatory
agencies).

1.3.2.4 Quality Assurance

The contractor shall establish a quality program that complies with
International Organization for Standardization document American Society
for Quality Control (ASQC) ISO-9000-2000 -- Model for Quality Assurance
in Design/Development, Production, Installation, and Servicing.

Third-party certification / registration is required.

The contractor shall:

-   Provide for their own hardware and software quality assurance
    (Quality Assurance, Quality Engineering, and Software Quality
    Assurance).

-   Develop a Quality Plan (DRD MSOC-JSC-0041) for on-site and off-site
    resources within this contract.

```{=html}
<!-- -->
```
-   Collect and compile information derived from contractor data (test
    results, analysis reports, inspection records, discrepancy data,
    nonconformance data, delivery logs, etc.) to demonstrate that the
    products and services delivered to the government are in compliance
    with the requirements and specifications as specified in this
    contract. The delivery of the compliance information will be at the
    request of the government, either specifically through this contract
    or on request of the appropriate government interface.

-   Comply with Non-conformance Record (DRD MSOC-JSC-0045) reporting.

-   Provide a Government Industry Database for Electronic Parts (GIDEP)
    and NASA Advisory Problem Data Sharing and Utilization Program
    Documentation and Reporting (DRD MSOC-JSC-0044).

The contractor shall submit procurement documents to the designated NASA
quality representative for determination of the need for Government
Source Inspection (GSI) prior to release of the procurement.

-   Procurements, which require GSI, shall include the following
    statements: "All work on this order is subject to inspection and
    test by the Government at any time and place. The Government quality
    representative who has been delegated quality assurance functions on
    this procurement shall be notified immediately upon receipt of this
    order. The Government representative shall also be notified 48 hours
    in advance of the time articles or materials are ready for
    inspection or test."

```{=html}
<!-- -->
```
-   Procurements, which do not require GSI, shall include the following
    statement: "The Government has the right to inspect any or all of
    the work included in this order at the supplier's plant."

At off-site facilities, the Government representative shall approve all
dispositions of nonconforming product except rework to specification.
On-site disposition is covered in NT-CWI-003.

The contractor may negotiate use of Receiving Inspection and Test
Facility (RITF) receiving inspection services for metallic and
nonmetallic material properties analysis, destructive physical analysis,
failure analysis of electronic components, and screen burn-in of
electrical and electronic parts and components. The contractor may
negotiate use of RITF training services for nondestructive evaluation,
hand soldering, and electrostatic discharge, and other special processes
for personnel certification.

The following standards shall be used in the design and manufacture and
maintenance of electrical/electronic equipment applications in this
contract:

-   [Soldering, Through-Hole Technology]{.underline} use
    NASA-STD-8739.3 - \"Soldered Electrical Connections\"

-   [Soldering, Surface Mount Technology]{.underline} use
    NASA-STD-8739.2 - \"Workmanship Standard for Surface Mount
    Technology\"

-   [Crimping, Cable and Harness]{.underline} use NASA-STD-8739.4 -
    \"Crimping, Interconnecting Cables, Harnesses and Wiring\"

-   [Conformal Coating and Staking]{.underline} use NASA-STD-8739.1-
    \"Workmanship Standard for Staking and Conformal Coating of Printed
    Wiring Boards and Electronic Assemblies\"

-   [Fiber Optics]{.underline} use NASA-STD-8739.5 - \"Fiber Optic
    Terminations, Cable Assemblies, and Installation\"

-   [Electrostatic Discharge Control (ESD]{.underline}) use ANSI/ESD
    S20.20-1999: Development of an Electrostatic Discharge Control
    Program for Protection of Electrical and Electronic Parts,
    Assemblies and Equipment (Excluding Electrically Initiated Explosive
    Devices).

-   [Rigid Printed Wiring Board (PWB) Design]{.underline} use IPC-2221-
    \"Generic Standard on Printed Board Design\" and IPC-2222-
    \"Sectional Design Standard for Rigid Organic Printed Boards\"

-   [Rigid Printed Wiring Board (PWB]{.underline}) use
    IPC-6011-\"Generic Performance Specification for Printed Boards\",
    IPC-6012- \"Qualification and Performance Specification for Printed
    Boards\" and S312-P-003B- \"GSFC, Procurement Specification for
    Rigid Printed Boards for Space Applications and Other High
    Reliability Users\"

Costs Related to Quality: - The contractor shall maintain and use
quality data cost data as a management element of the Quality Management
System. These data shall serve the purpose of identifying the cost of
prevention of non-conforming products (e.g., labor and material involved
in product defects caused by defective work, correction of defective
work and for quality assurance exercised by the contractor at the
subcontractor's or vendor's facility). The contractor shall determine
the specific quality cost data to be maintained and used. These data
shall, on request, be identified and made available to NASA.

Audits: - The contractor shall conduct internal audits to ensure
contract requirements are fully complied with. Additionally, the
contractor shall perform process audits upon request from the JSC
Contracting Officer. Process audits shall be performed to provide a
candid assessment of processes to identify generic system anomalies and
areas for improvement.

Calibration: - Inspection, Measuring, and Test Equipment (IM&TE), which
affect quality, shall be controlled in accordance with ISO 10012-1,
Quality Assurance Requirements for Measuring Equipment. If the JSC
Measurements Standards and Calibration Laboratory are used for
calibration services, JSC's System Level Procedure 4.11 Control of
Inspection, Measuring and Test Equipment shall be used.

Software Quality Assurance: - Software Quality Assurance requirements
are applicable to the following categories of software and firmware:

-   All mission ground support software and firmware, i.e., software and
    firmware that are an integral part of the operational mission
    (support of the program);

-   Software support tools that are used in development of flight and
    critical ground support software and firmware;

-   Manufacturing processes of mission critical hardware, and

-   Test and integration of mission critical hardware, software, and
    firmware.

The contractor shall develop and prepare a Software Quality Assurance
Plan and Reports (DRD MSOC-JSC-0042).

The contractor shall develop Acceptance Review Packages (DRD
MSOC-JSC-0071).

1.4 Data Requirements Description (DRD) and Applicable Documents

All referenced documents include the current version as of February
2003. The contractor is obligated to comply with updated versions.

1.4.1 DRD's documenting the contractors systems/processes.

DRD List:

  --------------------- -----------------------------------------------------
  [DRD                  [DRD Title]{.underline}
  Number]{.underline}   

  MSOC-JSC-0001         Contract Work Breakdown Structure and Dictionary

  MSOC-JSC-0002         Management Plan

  MSOC-JSC-0003         Risk Management Plan

  MSOC-JSC-0004         Contract Configuration Management Plan

  MSOC-JSC-0005         Phase-in Plan

  MSOC-JSC-0006         Performance Measurement Plan and Reports

  MSOC-JSC-0007         Metric and Status Reports

  MSOC-JSC-0008         Government Property Management Plan

  MSOC-JSC-0009         Small Business Subcontracting Plan and Reports

  MSOC-JSC-0010         Information Technology (IT) Plan and Reports

  MSOC-JSC-0011         Emergency Preparedness and Disaster Recovery Plan

  MSOC-JSC-0012         Reports/Reviews

  MSOC-JSC-0013         Reprocurement Data Package

  MSOC-JSC-0014         Property Financial Reporting

  MSOC-JSC-0015         Customer Reporting

  0016-0019 (Reserved)  

  MSOC-JSC-0020         Financial Management Reports

  MSOC-JSC-0021         Wage/Salary & Fringe Benefits

  MSOC-JSC-0022         Fiscal Year Operating Plan

  MSOC-JSC-0023         Travel Plan

  MSOC-JSC-0024         Workforce Reports

  0025-0029 (Reserved)  

                        

  MSOC-JSC-0030         Safety and Health Plan

  MSOC-JSC-0031         Safety and Health Program, Self-evaluation

  MSOC-JSC-0032         Safety Metrics (Monthly)

  MSOC-JSC-0033         System Safety Program Plan

  0034-0040 (Reserved)  

                        

  MSOC-JSC-0041         Quality Plan

  MSOC-JSC-0042         Software Quality Assurance Plan & Reports

  MSOC-JSC-0043         Reserved

  MSOC-JSC-0044         GIDEP and NASA advisory Problem data Sharing and
                        Utilization Program Documentation and Reporting

  MSOC-JSC-0045         Non-conformance Record

  MSOC-JSC-0046         Safety Lessons Learned

  0047-0049 (Reserved)  

                        

  MSOC-JSC-0050         Certificate of Flight Readiness Endorsement

  MSOC-JSC-0051         Integrated Planning System (IPS) Facility Operations
                        Procedures

  MSOC-JSC-0052         Deleted

  MSOC-JSC-0053         Training and Certification Plan

  0054-0059 (Reserved)  

                        

  MSOC-JSC-0060         Change Control Process Plan

  MSOC-JSC-0061         Configuration Management Plan

  MSOC-JSC-0062         Level A and B Requirements

  MSOC-JSC-0063         Interface Control Documents

  MSOC-JSC-0064         Reserved

  MSOC-JSC-0065         System Lifecycle Process

  MSOC-JSC-0066         Equipment Replacement Plan

  MSOC-JSC-0067         Integrated Planning System (IPS) Future Facility
                        Change Plan

  MSOC-JSC-0068         Test and Verification Plan

  MSOC-JSC-0069         Test and Verification Procedures

  MSOC-JSC-0070         Test and Verification Report

  MSOC-JSC-0071         Acceptance Review Package

  MSOC-JSC-0072         Design Review Package

  MSOC-JSC-0073         Design Specifications

  MSOC-JSC-0074         IPS Operations Concept

  0075-0079 (reserved)  

                        

  MSOC-JSC-0080         Contractor Security Management Plan

  MSOC-JSC-0081         Facility Security Plan

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

1.4.2 Applicable Documents

Applicable Documents List for SR&QA:

This list of documents form a part of the requirements, to the extent
specified within the Statement of Work and associated Data Requirements
Description. Unless otherwise specified the latest authorized version
shall be used.

  ------------------- ---------------------------------------------------
  ISO-9000-2000       Quality Systems, Aerospace Model for Quality
                      Assurance in Design, Development, Production,
                      Installation, and Servicing

  JPG 1700.1          JSC Safety & Total Health Handbook

  JSC 17773, as       Instruction for Preparation of Hazard Analysis for
  revised             JSC Ground Operations

  NASA-STD-8719.13A   NASA Software Safety Standard

  NASA-STD-2101-91    NASA Software Documentation Standard

  NASA-STD-2201-93    Software Assurance Standard

  NASA STD-8719.11    Safety for Fire Protection

  NASA-STD-8739.4\*   Crimping, Interconnecting Cables, Harnesses and
                      Wiring

  NASA-STD-8739.1\*   Workmanship Standard for Staking and Conformal
                      Coating of Printed Wiring Boards and Electronic
                      Assemblies

  NASA-STD-8739.2\*   Workmanship Standard for Surface Mount Technology

  NASA-STD-8739.5 \*  Fiber Optic Terminations, Cable Assemblies, and
                      Installation

  NPG 1700.1 (V1-B &  Guidelines for Mishap Investigation
  V2)\*               

  NSTS 5300.4 (1D-2)  Safety, Reliability, Maintainability and Quality
                      Provisions for the Space Shuttle Program

  NASA-STD-8739.3\*   Soldered Electrical Connections\"

  NPD 2820.1          NASA Software Policies

  NPD 8730.2          NASA Parts Policy

  NPG 7120.5          Program and Project Management Process and
                      Requirements

  NPG 8735.1          Procedure for Exchanging Parts, Materials, and
                      Safety Problem Data Utilizing the Government
                      Industry Data Exchange Program and NASA Advisories

  SO300-BT-PRO-010    GIDEP Operations Manual

  SO300-BT-GYD-010    GIDEP Requirements Guide

  SSP 30309, \*       Safety Analysis and Risk Assessment Requirements
                      Document

  SSP 30312           EEE Parts Management and Implementation Plan

  SSP 30695           Acceptance Data Package Requirements

  ANSI/ESD            Development of an Electrostatic Discharge Control
  S20.20-1999\*       Program for Protection of Electrical and Electronic
                      Parts, Assemblies and Equipment (Excluding
                      Electrically Initiated Explosive Devices)

  IPC-2221\*          Generic Standard on Printed Board Design\" and
                      IPC-2222- \"Sectional Design Standard for Rigid
                      Organic Printed Boards

  IPC-6011\*          Generic Performance Specification for Printed
                      Boards\", IPC-6012- \"Qualification and Performance
                      Specification for Printed Boards

  S312-P-003B \*      GSFC, Procurement Specification for Rigid Printed
                      Boards for Space Applications and Other High
                      Reliability Users 

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

\* Referenced in the SOW, all other listings are referenced in DRDs
MSOC-JSC-0041 through MSOC-JSC-0046.

1.5 Technical Services and Support

Technical Services and Support are those functions and services provided
to meet the Johnson Space Center (JSC) Human Space Flight (HSF) mission.
This includes assumption of on-going functions and services, including
all modification, systems engineering, sustaining engineering,
maintenance and operations activities, per the Phase-in Plan (DRD
MSOC-JSC-0005). Services are categorized as:

-   Mission Services

-   Mission Support Services

-   Site Support Services

-   Program Support Services

-   Technical Administration Support

-   Return-to-Flight (RTF)

    -   Mission Evaluation Room (MER) Phase I Expansion

1.5.1 Mission Services Function

The mission services function supports HSF programs by providing mission
operations and planning ground systems. Current major customers include
the Space Shuttle Program (SSP) and International Space Station (ISS)
Program. To accomplish this function, the Mission Control Center (MCC)
or as now designated MCC Houston (MCC-H) \[in order to distinguish from
multiple International Partner (IP) and supporting control centers for
Space Station operations---note that many documents still maintain only
the MCC designation\], Integrated Planning System (IPS), Houston Support
Room/Backup Command and Control Center (HSR/BCC) are currently used.

1.5.1.1 MCC-H, HSR and BCC

The MCC-H is an integrated spacecraft command and control facility that
is able to support multiple space flight programs. The MCC-H provides
command, telemetry, trajectory, real time mission re-planning, weather,
video, and voice communications to support mission operations. The MCC-H
is comprised of the following systems and subsystems: Command,
Telemetry, Trajectory, Voice, Timing, Configuration Management, Platform
Services, Data Display and Computation, External Data Distribution, Data
Archival, Video, Electronic Documentation, Communication Assets
Scheduling, and Orbital Communications Adapter (OCA) Ground System. The
Limited Station Operations System (LSOS) is a capability provided for
continuous operations of the ISS from the MCC-H in Houston, Texas, while
required maintenance is performed on the primary systems.

The majority of the MCC-H is physically located at the Johnson Space
Center in Building 30. Certain MCC-H equipment, provided for and
maintained via this contract, are in locations other than the Building
30 complex, as defined in the hardware equipment list.

The HSR and BCC are a combined facility, both located in Russia. The HSR
is an integrated ground facility that supports spacecraft planning,
analysis, telemetry monitoring and voice exchange for the ISS mission.
The HSR provides access to capabilities of the MCC-H for the United
States (US) ISS Flight Control Consultant group in Russia.

The BCC provides the backup command and control functions to support
NASA ISS Operations in case of an outage of the US command and control
capability.

Data Display and Computation system software (commonly referred to as
user applications) is not included in the scope of this contract, except
for the Operational Support Team (OST) and Ground Controller (GC)
applications which are included in the software lines of code count in
this contract. However, the interfaces to the data display and
computation system are included.

1.5.1.1.1 Management

In support of the MCC-H Mission services, the contractor shall:

> Maintain and provide upgrades to the MCC-H ground systems,

-   Ensure MCC-H functionality per the Level A and B requirements
    (section 1.5.1.1.11, table 1.5.1.1.11),

-   Provide operations support,

-   Provide security services, and

-   Provide program and technical services support.

-   Provide mission planning that includes meeting support, travel,
    interface negotiation and end-to-end ground systems integration

MCC-H Mission services consist of system engineering, modification,
maintenance, sustaining engineering, operations, facility operations,
facility resource scheduling, performance standards, test and checkout,
interface support, certification, training, travel, reports and
requirement documentation.

The contractor is responsible for configuration management and
documentation maintenance of the MCC-H architecture baseline, Level A,
and Level B system/subsystem requirements. NASA owns the MCC-H
architecture and the requirements (i.e., signature approvals) and is
responsible for approving any changes to the MCC-H architecture or the
requirements baseline. Where changes to the baseline introduce tradeoffs
between existing MCC-H requirements or between existing MCC-H
requirements and performance improvements, the NASA MCC-H project
management shall be the deciding official, including the authority to
change or waive the MCC-H requirement, through the CM process defined in
section 1.5.5.2.

The Contractor is responsible for MCC-H, HSR and BCC ground systems
integration and operations to ensure mission readiness of the ground
systems and supporting the space flight operations contractor in the
Certificate of Flight Readiness (COFR) process. Readiness Review data
requirements are established by the Flight Director Office. The
contractor shall provide a Certificate of Flight Readiness Endorsement
(DRD MSOC-JSC-0050).

1.5.1.1.2 Modification and Systems Engineering

For the MCC-H, BCC, and HSR the contractor shall provide systems
engineering, modification engineering and service integration for all
systems and subsystems as defined in the Level A and B requirements for
these facilities. These services shall include modification, upgrade or
replacement of the MCC-H hardware and software systems and interfaces.

The contractor shall provide supporting services that include technical
analyses, cost assessment, "make/buy" decisions, and other specific
activities necessary to accomplish the provisioning of services.

Typical systems engineering functions include:

-   Integrated service elements and spacecraft solutions

-   End-to-end Mission, Data and Center Unique service integration

-   Requirements management, analysis and requirements/design trade
    studies

-   Establishing systems engineering processes

-   Operations and development systems standards support, coordination,
    and control

-   Integrated architecture baseline configuration management and
    planning

-   Design analyses, architecture trade-off, and Make or Buy assessments

-   System-level functional designs development

-   Engineering strategies development

-   Service capacity, performance, and life cycle cost forecasting

-   External interface negotiation and design

-   Facilitate and coordinate designs across the contract, that are
    consistent with the NASA strategic architecture directions

-   Evaluating and testing commercial off-the-shelf (COTS) software and
    hardware products including development and engineering tools

-   Facility and Ops Support Team Operations concept development

-   Proactive end-to-end risk analysis management and abatement

-   Security engineering and analysis

The contractor shall:

-   Provide system-engineering support of all modification requests per
    the Change Process defined in section 1.5.5.2.

-   Receive NASA approval for all modifications that require a change to
    the MCC-H architecture or requirements.

-   Provide a Design Review (DRD MSOC-JSC-0072) for all approved
    modifications.

-   Document in the Design Specification (DRD MSOC-JSC-0073 all approved
    modifications and changes to the MCC-H Architecture).

Performance standards for the response to NASA driven modification
requests are defined in section 1.5.1.1.6

The contractor shall:

-   Perform hardware and software modifications to MCC-H systems and
    subsystems, including both custom and COTS hardware and software,
    per the change mechanism defined in section 1.5.5.2. The contractor
    is responsible for providing all hardware and software required to
    implement the modifications, unless otherwise specified through the
    change mechanism.

```{=html}
<!-- -->
```
-   Provide coordination of COTS software tools integration.

-   Provide integration and coordination with external organizations for
    interface changes due to modifications.

-   Provide sustaining engineering for all modifications to hardware and
    software.

-   Perform operational analysis and system engineering of all
    modifications.

-   Perform integration of all modifications with the current system and
    external organizations.

-   Perform verification testing of all modifications per section
    1.5.1.1.7 Test and Checkout.

The contractor shall:

-   Provide delivery of modifications as a base service. The contractor
    is responsible for 2 deliveries per year for each MCC-H
    system/subsystem, as defined in paragraph 1.5.1.1, for modifications
    that are a requirement or architecture change. These deliveries may
    bundle several systems/subsystems or maintain separate deliveries as
    is most efficient. All other modifications shall be released as an
    independent modification delivery to operations per the Systems
    Lifecycle Process upon successful test completion.

-   Provide modifications that are a requirement or architecture change
    in the delivery methodology per the Systems Lifecycle Process (DRD
    MSOC-JSC-0065).

-   Maintain a schedule for all modifications. The NASA project manager
    approves schedule content and delivery date.

-   Provide coordination of each delivery or independent modification
    delivery with external organizations and NASA.

-   Receive NASA acceptance of the delivery with the Acceptance Review
    Package (DRD MSOC-JSC-0071).

The contractor shall provide an annual Fiscal Year Operating Plan (DRD
MSOC-JSC-0022) that defines the modification content for the upcoming
Fiscal Year. The scope for the modification content is dependent upon
the NASA modification budget.

1.5.1.1.3 Maintenance and Sustaining Engineering

The contractor shall provide maintenance and sustaining engineering of
the facility and the associated systems and subsystems per the
configuration management process defined in Section 1.5.5.2. This
includes associated hardware and software, both COTS and custom.
Included shall be any transferred maintenance, operations and sustaining
from the previous contract (refer to the bidders library for a listing
of equipment and software). The performance expectation shall be to the
level of facility, system and subsystem availability and reliability as
specified by associated MCC-H System and Subsystem Level A and B
Requirements and in SOW section 1.5.1.1.6 Performance Standards.

The contractor shall provide system engineering support of all
sustaining engineering functions per the Change Process defined in
section 1.5.5.2.

The contractor shall maintain a Design Specification (DRD MSOC-JSC-0073)
for all sustaining engineering functions.

Performance of maintenance and sustaining engineering shall include the
provision of: spares and a spares depot as required, maintenance
agreements with hardware and software suppliers, software licenses,
resolution of anomaly reporting for the software and equipment and its
operations, calibration of test equipment, per JSC SLP4.11, Rev. B,
Quality Management System (QMS) requirements, installation equipment,
technical personnel to perform maintenance and repairs and sustaining
engineering. Included is installation of new equipment and interface
cabling, removal of obsolete equipment and cabling as agreed to by NASA,
and the Equipment replacement (reference section 1.5.5.1.4 Equipment
Replacement & Depreciation) for the facility. All processes used by the
Contractor shall be in compliance with NASA, Federal, and State
Standards as specified in the contract.

The Contractor shall provide integration and installation of Government
Furnished Equipment (GFE) and software.

NASA is responsible for providing building power and plant engineering
and operations in accordance with requirements documents, including the
Mission Operation Directorate (MOD)/Center Operation Directorate (COD)
Memorandum of Understanding (JSC-27049). The contractor shall be
responsible for technical power and coordination of plant engineering
and operations in accordance with requirements documents.

In performance of maintenance and sustaining engineering, the contractor
shall:

-   Provide coordination of Commercial-off-the-shelf (COTS) software
    tools integration.

-   Provide integration and coordination with external organizations for
    interface changes.

-   Perform operational analysis and system engineering of all updates.

-   Perform integration with the current system and external
    organizations.

-   Perform verification testing of all updates, including testing of IT
    security capabilities, per section 1.5.1.1.7 Test and Checkout.

-   Provide technical support of the Meteorological Interactive Data
    Distribution Subsystem (MIDDS) to the Marshall Space Flight Center
    (MSFC).

The contractor shall:

-   Provide releases of sustaining updates and changes as a base service
    per the Systems Lifecycle Process (DRD MSOC-JSC-0065). The
    contractor is responsible for up to 6 releases per year of each
    MCC-H system or subsystem. Sustaining changes that are independent
    from the release can be released to operations, per the Systems
    Lifecycle Process, upon successful test completion.

-   Maintain a schedule for all sustaining updates and changes. The NASA
    project manager approves schedule content and delivery date.

-   Provide coordination of each sustaining update and change with
    external organizations and NASA.

-   Document test results per section 1.5.1.1.7 Test and Checkout.

-   Report to NASA test completion success prior to release to
    operations.

-   Provide to NASA at any time a copy of the MCC-H, HSR and BCC
    software (source and executables, including scripts and
    configurables). NASA shall accept responsibility for any export
    control of the software.

The contractor shall provide an annual Fiscal Year Operating Plan (DRD
MSOC-JSC-0022) that defines the sustaining bases of estimate & content
for the upcoming Fiscal Year to meet the sustaining requirements.

1.5.1.1.4 Operations

The contractor shall provide mission control operations services that
include the capabilities to conduct mission operations. Services include
facilitating the command, control and monitoring for launch vehicle,
spacecraft, payloads, ground systems, subsystems and networks as
specified in section 1.5.1.1.11 for both real-time and non-real-time
operations. Additionally, support shall be provided to the Space Flight
Meteorology Group.

The contractor shall:

-   Provide a Training and Certification Plan (DRD MSOC-JSC-0053) to
    describe the contractor's plans for training and certification of
    operational support personnel for the MCC-H and IPS facilities.

-   Provide trained and certified personnel required to support the
    capabilities to operate, control, setup and change configurations
    and operational status for ground systems, subsystems, support
    systems, external interfaces and networks. This includes system and
    subsystem software and hardware configurations, allocation of
    equipment and system/subsystem status and control.

Supporting services shall be provided to the flight support teams,
headed by the Flight Director or designee, as required for operations
and the execution of the Mission Control functions.

Mission Services shall include support to the multi-lateral and
bi-lateral International Partner (IP) meetings \[e.g., Ground Segment
Control Board (GSCB), Security Analysis and Response Team (SART),
Network and Communications Analysis Team (NACAIT) Integration
Verification and Test (IV and T), Ground Segment Technical Interchange
Meetings (TIMs), Joint Operations Panels (JOPs), etc.\] to establish
technical and operational interfaces and procedures with both the NASA
and International Partner (IP) Mission Control Centers.

Supporting services shall also be provided to the NASA MOD IT Security
Management as required for operations and support, execution,
interpretation and analysis of the Mission Security Capabilities.

1.5.1.1.5 Facility Operations

The contractor shall provide MCC-H facility operation mission services
consistent with the following mission support operational requirements:

-   On Console, support up to 3-concurrent operations 456/hrs/week:

    -   1^st^ operations -- 24x7 = 168hrs

    -   2^nd^ operations -- 24x6 = 144 hrs (24x7 during Shuttle
        missions)

    -   3^rd^ operations -- 24x6 = 144 hrs

    -   This staffing level is to include any off console work

-   Security level - Mission Critical Security System Services

-   Operational MCC-H: During shuttle missions: the second operation is
    24x7 consistent with a shuttle flight rate of 4-7 flights per year
    (avg. flight = 10 days).

-   On-call and special request for support is to be provided as
    required to meet special peak or critical periods of activity

The contractor shall provide HSR/BCC facility operation:

-   Mission Critical Security Services

-   1 shift x 5 days. On call and special requests can be made 24x7

-   In the event of a MCC-H deactivation and BCC activation, after the
    additional staffing arrives on-site (72 hours, consistent with
    Flight Control Team plans), provide 24x7 Telecom/Controller support
    for up to 60 days.

1.5.1.1.6 Performance Standards

The contractor provides ground systems services for mission control in
accordance with requirements documents. The mission control ground
systems support from the MCC-H perform unique critical functions and
require a higher-level performance standard. Higher availability and
reliability performance standards are defined as:

Required Service: Provide ground systems services for mission control.

Std of Excellence: 100% availability of critical and non-critical
functions as defined in JSC-12804, MCC-H Level A Requirements.

Expectation: 99.5% availability of critical functions as defined in
JSC-12804, MCC-H Level A Requirements, and in no case impact safety,
mission success, or major program schedule milestones. There is to be
98% availability of non-critical functions, and in no case impact
safety, mission success, or major program schedule milestones.

Required Service: Provide ground systems services for mission control.

Std of Excellence: 99.95% reliability for 20 hours of critical functions
as defined in JSC-12804, MCC-H Level A Requirements, with a maximum
restore time of 1 minute.

Expectation: 99.5% reliability for 20 hours of critical functions as
defined in JSC-12804, MCC-H Level A Requirements, with a maximum restore
time of 1 minute

The contractor provides support for modification design and cost
definition per the change mechanism defined in section 1.5.5.2. The
response standards for a Type 1 Design Review (per DRD MSOC-JSC-0072)
are defined as:

Required Service: Provide SFDR and initial cost impact for NASA driven
modifications

STD of Excellence: Complete design and cost response in 8 weeks from SR
submittal for 95% of the yearly modifications

Expectation: Complete design and cost response in 10 weeks from SR
submittal for 95% of the yearly modifications. SR submittal is defined
as the time when the NASA Project manager or designee where applicable,
submits the SR to the CM process for tracking.

The contractor provides modification and implementation of maintenance
support for MCC-H software. Current MCC-H subsystems are assumed to be
mature software unless 50% or more is changed in one year. The
standards, for each MCC Subsystem, for Anomaly Report (AR) density in
Kilo (i.e. 1000) Lines of Source Code (KSLOC) are as follows:

Required Service: Maintain at or below the following "Open" anomaly
density (AR/KSLOC) for new and existing MCC-H software.

Std of Excellence: 1 Anomaly per 8 KSLOC for mature software (greater
than 2 years old) and 1 anomaly per 2 KSLOC for code less than 2 years
old.

Expectation: 1 Anomaly per 5 KSLOC for mature software (greater than 2
years old) and 1 anomaly per 1 KSLOC for code less than 2 years old.

The standards for the response to Support Request (SR) implementation of
hardware and software changes are defined as:

Required Service: Implementation of hardware and software changes
response. Implementation completion is defined as Return to Operations
(RTO) for hardware changes and the release or delivery of a software
change.

Expectation: Implementation of hardware or software reconfigurations or
modifications, that are priority 1 flight specific, shall be completed
by the negotiated Operational Need Date (OND) for the flight specified.

The standards for the response to Support Request (SR)
RTO/delivery/release of hardware and software changes are defined as:

Required Service: RTO/delivery/release of hardware and software changes
by the approved delivery/release date. Approved RTO/delivery/release
date is defined as the negotiated and NASA Project Manager approved date
that the contractor is expected to complete the SR implementation.

Std of Excellence: Delivery/release of hardware and software changes
shall be no longer than 14 days from the approved RTO/delivery/release
date (impacts due to flight window changes are excluded with NASA
project manager approval)

Expectation: Delivery/release of hardware and software changes shall be
no longer than 30 days from the approved RTO/delivery/release date
(impacts due to flight window changes are excluded with NASA project
manager approval)

1.5.1.1.7 Test and Checkout

The contractor shall:

-   Provide verification per the Test and Verification Plan and
    Procedures (DRD MSOC-JSC-0068 and DRD MSOC-JSC-0069) of all releases
    due to modification or maintenance changes, including IT Security
    capabilities.

-   Provide verification of the operational MCC-H environment.

-   Report test status and provide a Test and Verification Report (DRD
    MSOC-JSC-0070).

-   Receive NASA approval of completing verification.

-   Provide necessary test tools to complete verification.

-   Be responsible for scheduling all required test resources.

The contractor shall:

-   Perform performance testing on all major modification and sustaining
    releases per the Test and Verification Plan (DRD MSOC-JSC-0068),
    including IT security capabilities.

-   Continually collect performance data and perform performance
    analysis of the MCC-H systems and subsystems for trend analysis.

```{=html}
<!-- -->
```
-   The Contractor shall provide inputs to the International Ground
    System Specification (IGSS) verification compliance matrix.

The contractor is responsible for verification of all IP Interface
Control Documents, including IT security capabilities. This includes
joint testing with the IP facility.

1.5.1.1.8 Interface Support

The contractor is hereby authorized to utilize any excess capacity for
the purposes of entering into an agreement with The Canadian Space
Agency (CSA) on a non-interference and reimbursable basis. The
contractor shall obtain payment directly from CSA and shall reimburse
the Government via a credit to this contract on a revenue sharing basis
of 50/50. The contractor recognizes that the Government reserves the
right to exercise priority for use of its facility and property.

1.5.1.1.9 Certification and Training

The contractor shall establish their training and certification plan for
Maintenance and Operations personnel adhering to Occupational Safety and
Health Administration (OSHA) and JSC safety standards and guidelines.
The plan should generally follow the guidelines of the flight control
team certification requirements that are defined in the NASA Mission
Operations Directorate, Space Flight Personnel Certification Plan
(DA-WI-16).

1.5.1.1.10 Metrics/Data and Reports

The contractor shall provide metrics and reports per DRD MSOC-JSC-0007
Metrics and Status Reports.

The contractor shall provide metrics reports providing insight into the
facility operations:

-   Process Integrity metrics -- monthly and quarterly

-   Availability - monthly

The Contractor shall provide data reports providing insight into the
facility status:

-   Performance -- quarterly

The Contractor shall provide management reports and meeting support
providing insight into the overall facility:

-   Activity Report - weekly

-   Facility Status Report - daily

-   Progress Report - monthly

-   Project Integration Meeting - monthly

-   Delivery Schedules Report - monthly

-   Work Plan Report -- daily and monthly

-   DRD Status Report -- monthly

-   Project Status Reviews -- monthly

-   DV and Contractor tag-ups - biweekly

-   MCC-H Technical Control Panel (TCP)- biweekly

-   Process Integrity Metrics Review -- quarterly

-   MOD Flight Readiness Review (FRR) -- per flight and increment

-   MOD Flight Operations and Integration Group (FOIG) - weekly

-   MOD Facility Status Telecon --daily

-   MOD Product Integration Board (MPIB)- weekly

-   MOD Subsystem User and status meetings

-   Operational Readiness Test (ORT) working group meeting -- twice
    weekly

-   Test and Operations Board (T&O) -- weekly

-   MOD Integrated Scheduling meeting -- weekly

-   MOD Ops Cadre -- weekly

-   MOD MCC-H Recon Integration meeting - biweekly

The contractor shall provide support for agendas and minutes of Control
Board and Panel, Project Integration Meeting, and Project Status Review
meetings.

1.5.1.1.11 Requirements Documentation and Facility DRD's

The Contractor shall adhere to the latest revision of the following
requirements documents: (changes to the level of support will be
incorporated through the initiation and approval of SRs):

-   ISSP International Ground Segment Specifications, SSP-54500

-   ISSP Requirements Document, PRD/OR/PSP/OD 30000

-   Internal Partner Protocol Agreements

-   Requirements for Network, MCC-H Communications Systems, Ground
    Facilities, and Consulting Groups for Joint US/Russian Manned Space
    flight, WG-3/RSC E/NASA/005/3233

-   SSP 50200-01 Station Program Implementation Plan Vol. 1: Station
    Program Management Plan

-   SSP 50200-02 Station Program Implementation Plan Vol. 2: Program
    Planning and Manifesting

-   SSP 50110 Multi-Increment Manifest Document

-   Space Shuttle Program Requirements Document (Flight Operations Vol.
    I and II, Launch and Landing Vol. I and II), PRD/OR/PSP/OD 20000

-   Space Shuttle Program, NSTS-07700 Volumes 8 and 14

-   IPS Functional Requirements, JSC-13565

-   ISS Orbital Volume I and II PRD/OR/PSP/OD 30000

-   Software Management Plan USA000622

-   Critical Processor Certification Policy USA002295

-   Facility Management Policy USA002955

-   MCC-H and IPS Operational Change Control Procedures SFOC-FL2333

-   Flight Controllers Operations Handbook (FCOH)

The Contractor shall establish, maintain, adhere to, and publish the
following facility documents and DRD's:

-   All documents defined in Table 1.5.1.1.11 (adherence only for
    SFOC/SOC documents)

-   Level A and B requirements (DRD MSOC-JSC-0062)

-   Interface Control Documents (DRD MSOC-JSC-0063)

-   Systems Lifecycle Process

-   Test and Verification Plan

-   Test and Verification Procedures

-   Test Reports

-   Interface Control Documents

-   Design Notebook and Specifications

-   Non Maintainable Equipment Replacement Plan

-   Design Review

-   Fiscal Year Operating Plan and Program Operating Plan (POP)

-   Security Plan

-   COFR Endorsement

-   Acceptance Review

-   Change Control Process

+----------------------------+-----------------------------------------+
| Table 1.5.1.1.11           | MCC-H SYSTEMS LEVEL A/B/C REQUIREMENTS  |
|                            | and INTERFACE CONTROL DOCUMENTS (ICDs)  |
+============================+=========================================+
| MCC-H System               | Level A Requirements Documents          |
+----------------------------+-----------------------------------------+
| Mission Control Center     | JSC -- 12804                            |
| (MCC) Level A Requirements |                                         |
+----------------------------+-----------------------------------------+
|                            |                                         |
+----------------------------+-----------------------------------------+
| MCC-H System               | Level B/C Requirements Documents        |
+----------------------------+-----------------------------------------+
| Telemetry System           | LOR-TR1296 -- Consolidated              |
|                            | Communications Facility (CCF) System    |
|                            | Definition Document, Volume 1, System   |
|                            | Requirements                            |
|                            |                                         |
|                            | JSC-13499 -- Consolidated               |
|                            | Communications Facility (CCF) Front-End |
|                            | Processing Subsystem (FEPS) Subsystem   |
|                            | Requirements, Volumes I -- XII, XV      |
|                            |                                         |
|                            | JSC-13497 -- Consolidated               |
|                            | Communications Facility (CCF)           |
|                            | Consolidated Communications Interface   |
|                            | Subsystem (CCIS) Subsystem              |
|                            | Requirements, Volumes I - II            |
|                            |                                         |
|                            | JSC-13504 -- Consolidated               |
|                            | Communications Facility (CCF)           |
|                            | Consolidated Distribution Subsystem     |
|                            | (CDS) Subsystem Requirements, Volumes   |
|                            | I - IV                                  |
|                            |                                         |
|                            | JSC-13509 -- Consolidated               |
|                            | Communications Facility (CCF) Test and  |
|                            | Checkout Subsystem (TCS) Subsystem      |
|                            | Requirements                            |
|                            |                                         |
|                            | JSC-37504 -- Mission Control Center     |
|                            | Tracking and Data Relay Satellite       |
|                            | System Real-Time Manager Functional     |
|                            | Requirements                            |
|                            |                                         |
|                            | JSC-37567 -- Space Station Training     |
|                            | Facility (SSTF) Front End Processing    |
|                            | Subsystem (FEPS) ISS Ku-Band Simulated  |
|                            | Zone of Exclusion (ZOE) Downlink        |
|                            | Requirements                            |
+----------------------------+-----------------------------------------+
| Command System             | CSOC-JSC-RD-000536 -- Mission Control   |
|                            | Center Command Subsystem Requirements   |
+----------------------------+-----------------------------------------+
| Voice System               | JSC-11028 -- Digital Voice              |
|                            | Intercommunications Subsystem, Level    |
|                            | B/C Requirements                        |
|                            |                                         |
|                            | JSC-37503 -- Consolidated               |
|                            | Communications Facility (CCF) Voice     |
|                            | Subsystem Air/Ground Voice Equipment    |
|                            | Requirements, Volumes I - III           |
+----------------------------+-----------------------------------------+
| Video System               | JSC-13613 -- Mission Control Center     |
|                            | (MCC) Platform Services (PS) Video      |
|                            | Subsystem (VS) Requirements             |
+----------------------------+-----------------------------------------+
| Trajectory System          | SFOC-FL0864 -- Trajectory System        |
|                            | Upgrade Project System Requirements     |
|                            | Review                                  |
|                            |                                         |
|                            | USA-001662 -- Trajectory Server System  |
|                            | Requirements Specification              |
|                            |                                         |
|                            | SFOC-FL1493 -- MCC Trajectory Server    |
|                            | Application Requirements                |
|                            |                                         |
|                            | JSC-22396 -- MCC Upgrade Host Software  |
|                            | Level B Requirements                    |
|                            |                                         |
|                            | SOC-RQ-600283B - MCC Level B/C          |
|                            | Requirements for Shuttle System         |
|                            | Monitoring and Control                  |
|                            |                                         |
|                            | SOC-RQ-600287A - MCC Level B/C          |
|                            | Requirements for Shuttle Operations     |
|                            | Volume II - Trajectory Related          |
|                            | Information Processing Software         |
+----------------------------+-----------------------------------------+

+----------------------------+-----------------------------------------+
| Table 1.5.1.1.11           | MCC-H SYSTEMS LEVEL A/B/C REQUIREMENTS  |
| (continued)                | and INTERFACE CONTROL DOCUMENTS (ICDs)  |
+============================+=========================================+
| MCC-H System               | Level B/C Requirements Documents        |
+----------------------------+-----------------------------------------+
| Platform Services          | JSC-37512 - Mission Control Center      |
|                            | (MCC) Platform Services (PS) Subsystem  |
|                            | Requirements                            |
|                            |                                         |
|                            | JSC-13567, Volume I -- Mission Control  |
|                            | Center (MCC) Workstation and Server     |
|                            | Platform (WSP) Subsystem Requirements,  |
|                            | Workstation and Servers                 |
|                            |                                         |
|                            | JSC-13567, Volume II -- Control Center  |
|                            | Complex Workstation and Server Platform |
|                            | Subsystem Requirements, General Purpose |
|                            | (GP) Tools                              |
|                            |                                         |
|                            | JSC-13567, Volume III -- Control Center |
|                            | Complex Workstation and Server Platform |
|                            | Subsystem Requirements,                 |
|                            | MPSR/Institutional Rooms Console        |
|                            | Housings                                |
|                            |                                         |
|                            | CSOC-JSC-REQ-000809 -- Software         |
|                            | Requirements Specification 2D           |
|                            | Distributed Earth Model Orbiter         |
|                            | Simulation (2D DEMOS) Application       |
|                            | Software and Workstation Hardware       |
|                            |                                         |
|                            | JSC-13333 -- Mission Control Center     |
|                            | (MCC) Internal Data Distribution (IDD)  |
|                            | Subsystem Requirements                  |
|                            |                                         |
|                            | JSC-13562 -- Control Center Complex     |
|                            | Data Distribution and Workstation       |
|                            | Platform System Strip Chart Recorder    |
|                            | Subsystem Functional Requirements       |
+----------------------------+-----------------------------------------+
| Timing System              | JSC-13334 -- Mission Control Center     |
|                            | (MCC) Timing Subsystem (TSS) Subsystem  |
|                            | Functional Requirements                 |
+----------------------------+-----------------------------------------+
| Operations Configuration   | JSC-37507 -- Mission Control Center     |
| Management System          | Operational Configuration Management    |
|                            | Subsystem Requirements                  |
+----------------------------+-----------------------------------------+
| Status and Control System  | JSC-37557 -- Mission Control Center     |
|                            | (MCC) Health and Status (HS) Subsystem  |
|                            | Requirements                            |
+----------------------------+-----------------------------------------+
| Data Archive System        | CSOC-JSC-RD-002347 -- Level B           |
|                            | Operational Data Reduction Complex      |
|                            | (ODRC) System Requirements Document     |
+----------------------------+-----------------------------------------+

+----------------------------+-----------------------------------------+
| Table 1.5.1.1.11           | MCC-H SYSTEMS LEVEL A/B/C REQUIREMENTS  |
| (continued)                | and INTERFACE CONTROL DOCUMENTS (ICDs)  |
+============================+=========================================+
| MCC-H System               | Level B/C Requirements Documents        |
+----------------------------+-----------------------------------------+
| User Planning System (UPS) | SFOC-FL2192 -- Level B/C Requirements:  |
| / Electronic User (EU)     | User Planning System/Electronic User    |
| Application System         | (UPS/EU) Application System             |
|                            | Requirements for Control Center Complex |
|                            | (CCC)                                   |
+----------------------------+-----------------------------------------+
| Meteorological Interactive | SFOC-FL2189 -- MIDDS and WDS Software   |
| Data Display System        | Requirements Specification              |
| (MIDDS)                    |                                         |
|                            | CSOC-JSC-RD-2768 -- MIDDS Level B       |
|                            | Requirements Document (In-work)         |
+----------------------------+-----------------------------------------+
| Orbital Communication      | JSC-28862 -- Orbital Communications     |
| Adapter (OCA) Ground       | Adapter Ground System Level A           |
| System                     | Requirements                            |
|                            |                                         |
|                            | JSC-28865 -- Orbital Communications     |
|                            | Adapter Ground System Level B           |
|                            | Requirements                            |
+----------------------------+-----------------------------------------+
| Information Sharing        | CSOC-JSC-RD-002522 -- Information       |
| Protocol External          | Sharing Protocol External Interface     |
| Interface (ISPX)           | (ISPX) Level A Requirements             |
|                            |                                         |
|                            | CSOC-JSC-RD-002523 -- Information       |
|                            | Sharing Protocol External Interface     |
|                            | (ISPX) Level B Requirements             |
+----------------------------+-----------------------------------------+
| External Interface System  | CSOC-JSC-RD-002524 - Mission Control    |
| (EIS)                      | Center Platform Services System         |
|                            | External Interface Server (EIS)         |
|                            | Subsystem Requirements                  |
+----------------------------+-----------------------------------------+
| Electronic Documentation   | JSC-26447 -- Electronic Documentation   |
| Project (EDP)              | Project (EDP) Level A Requirements      |
|                            |                                         |
|                            | JSC-26679 - Electronic Documentation    |
|                            | Project (EDP) Level B Requirements      |
+----------------------------+-----------------------------------------+
| Security Services          | CSOC-JSC-RD-002684 -- Mission Control   |
|                            | Center (MCC) Security Data Processing   |
|                            | Services Requirements Document          |
|                            |                                         |
|                            | JSC-13341 -- Mission Control Center     |
|                            | (MCC) Operating Systems (OS) and        |
|                            | Security Services Subsystem             |
|                            | Requirements                            |
+----------------------------+-----------------------------------------+
| Houston Support Room (HSR) | JSC-37558 -- Backup Control Center      |
| Backup Control Center      | (BCC) Houston Support Room (HSR)        |
| (BCC)                      | Platform Services System (PSS)          |
|                            | Subsystem Requirements                  |
|                            |                                         |
|                            | JSC-37559 -- Backup Control Center      |
|                            | (BCC) Houston Support Room (HSR)        |
|                            | Telecommunications System (TS)          |
|                            | Subsystem Requirements, Volume I, Voice |
|                            | Intercom Equipment                      |
|                            |                                         |
|                            | JSC-37571 -- Telecommunications System  |
|                            | (TS) Backup Control Center (BCC)        |
|                            | Subsystem Requirements, Volumes I -- II |
+----------------------------+-----------------------------------------+

  ---------------------------- ------------------------------------------
  Table 1.5.1.1.11 (continued) MCC-H SYSTEMS LEVEL A/B/C REQUIREMENTS and
                               INTERFACE CONTROL DOCUMENTS (ICDs)

  MCC-H Interface              Interface Control Document

  Goddard Space Flight Center  JSC-11534, Volume I -- JSC/GSFC
  (GSFC)                       Operational Communications ICD for Mission
                               Control Center Systems, Volumes I - XIV

  George C. Marshall Space     External Interface Control Document --
  Flight Center (MSFC)         JSC/ITF/SLS-MSFC Operational
                               Communications ICD for Simulation of
                               Mission Control Center Systems

  Lewis Research Center (LeRC) SSP-45003 -- Space Station Control Center
                               (SSCC) to Lewis Research Center (LeRC)
                               Engineering Support Center (ESC) Interface
                               Control Document (ICD)

  Shuttle Mission Training     External Interface Control Document -- JSC
  Facility (SMTF)              Mission Control Center (MCC)/Integrated
                               Training Facility (ITF) Operational
                               Communications ICD for Simulation of
                               Mission Control Center Systems

  Integrated Planning System   JSC-13555 -- Integrated Planning System
  (IPS)                        (IPS) and Mission Control Center Interface
                               Control Document

  Station Verification         JSC-50026 -- Station Verification Facility
  Facility (SVF)               (SVF) to Space Station Control Center
                               (SSCC) and Electronic Systems Test
                               Laboratory (ESTL) External Interface
                               Control Document (ICD)

  ISS Mission Operations       JSC-37555 -- Integrated Planning System
  Directorate (MOD) Avionics   (IPS) International Space Station (ISS)
  Reconfiguration System       Mission Operations Directorate (MOD)
  (IMARS)                      Avionics Reconfiguration Subsystem (IMARS)
                               Data Products Interface Specification

  Electronic Systems Test      JSC-13241 -- Control Center Complex (CCC)
  Laboratory (ESTL)            to Electronic Systems Test Laboratory
                               (ESTL) Interface Control Document (ICD)

  Payload Operations Control   JSC-11534, Volume IV -- JSC Remote Payload
  Center (POCC)                Operations Control Center (POCC)
                               Operational Communications Interface
                               Control Document (ICD) for Mission Control
                               Center Systems

  Huntsville Operations        SSP-45001 -- SSCC to Huntsville Operations
  Support Center (HOSC)        Support Center (HOSC) Interface Control
                               Document (ICD), Part I

  Canadian Space Agency (CSA)  SSP-45004 -- Space Station Control Center
                               to Canadian Space Agency Interface Control
                               Document, Part I

  Russian Space Agency (RSA)   SSP-50057 -- Space Station Control Center
                               to Russian Space Agency Ground Segment
                               Interface Control Document, Part I

  European Space Agency (ESA)  SSP-45011 -- Space Station Control Center
                               to European Space Agency Ground Segment
                               Interface Control Document, Part I

  National Aeronautics/Space   SSP-45012 -- Space Station Control Center
  Development Agency (NASDA)   to National Space Development Agency of
  of Japan                     Japan (NASDA) Ground Segment, Part I

  Italian Space Agency (ASI)   SSP-50612 -- Space Station Control Center
                               / Space Station Processing Facility to
                               Italian Space Agency Ground Segment
                               Interface Control Document
  ---------------------------- ------------------------------------------

1.5.1.2 Integrated Planning System (IPS)

The IPS provides the planning and analysis tools required to support
long-range mission and vehicle assessments, trajectory design, mission
and increment planning, pre-mission contingency analysis, ISS avionics
reconfiguration, and direct mission support. The IPS is a distributed
system at NASA and is currently located, but not limited to JSC,
Buildings 30 (A, S), 4N, 5, 35, 585, 595 Gemini, 600 Gemini and the HSR
(Russia). The SCSC equipment in Russia is not part of the IPS, but shall
be maintained by the contractor. IPS also includes ISS Mission
Operations Directorate Automated Reconfiguration Software (IMARS)
equipment, as a subsystem or component of the IPS configuration.

Primary areas of functionality provided by IPS include Space Shuttle
Flight Design and Dynamics, ISS Avionics reconfiguration, ISS Resource
Utilization Planning and System Models, ISS Procedures Development and
Control, and functions common to both Space Shuttle and ISS including
Flight Dynamics Planning and Analysis, Consolidated Planning System,
Planning Information Management (PIM), and Robotics planning and
analysis.

IPS is allocated to two segments: the Application Segment and the
Platform Segment. The Application Segment is partitioned into Space
Shuttle Flight Design and Dynamics (FD&D), ISS flight planning and
analysis, ISS reconfiguration processing, and common software
applications that provide Multi-program tools for planning and analysis.
The Platform Segment provides the hardware, COTS, and non-COTS software
to support the Application Segment. The Platform Segment is defined to
include the subsystems designed to enforce system-wide policies. In
addition, the Platform Segment consolidates and integrates common
lower-level services needed by the Application Segment subsystems.

1.5.1.2.1 Management

In support of the IPS services, the contractor shall:

-   Maintain and provide upgrades to the IPS systems and subsystems,

-   Ensure IPS functionality per the Level A and B requirements (section
    1.5.1.2.11, table 1.5.1.2.11),

-   Provide operations support, and

-   Provide program and technical services support.

IPS services consist of system engineering, modification, maintenance,
sustaining engineering, operations, facility operations, performance
standards, test and checkout, interface support, certification,
training, travel, reports and requirement documentation.

The contractor is responsible for configuration management and
documentation maintenance of the IPS architecture baseline, Level A, and
Level B system/subsystem requirements. NASA owns the IPS architecture
and the requirements (i.e., signature approvals) and is responsible for
approving any changes to the IPS architecture or the requirements
baseline. Where changes to the baseline introduce tradeoffs between
existing IPS requirements or between existing IPS requirement and
performance improvements, the NASA IPS project management shall be the
deciding official, including the authority to change or waive the IPS
requirement, through the CM process defined in section 1.5.5.2.

The Contractor is responsible for IPS systems integration and operations
to ensure mission readiness of the systems and subsystems and supporting
the space flight operations contractor in the Certificate of Flight
Readiness (COFR) Endorsement (DRD MSOC-JSC-0050). The Flight Director
Office establishes the readiness review data requirements.

1.5.1.2.2 Modification and Systems Engineering

For the IPS the contractor shall provide systems engineering,
modification engineering and service integration for all systems and
subsystems, including all hardware and software, as defined in the Level
B requirements for these facilities, and per the change mechanism of
section 1.5.5.2. These services shall include modification, upgrade or
replacement of the IPS hardware and software systems and subsystems and
interfaces.

The contractor shall provide supporting services that include technical
analyses, cost assessment, "make/buy" decisions, and other specific
activities necessary to accomplish the provisioning of services.

The Contractor shall also provide operations analysis, systems
engineering, integration, testing, logistics, custom software/hardware
development and coordination of COTS tools for IPS.

Typical systems engineering functions include:

-   Integrated service elements and spacecraft solutions

-   End-to-end Mission, Data and Center Unique service integration

-   Requirements management, analysis and requirements/design trade
    studies

-   Establishing systems engineering processes

-   Operations and development systems standards support, coordination,
    and control

-   Integrated architecture baseline configuration management and
    planning

-   Design analyses, architecture trade-off, and Make or Buy assessments

-   System-level functional designs development

-   Engineering strategies development

-   Service capacity, performance, and life cycle cost forecasting

-   External interface negotiation and design

-   Evaluating and testing commercial off-the-shelf (COTS) software and
    hardware products including development and engineering tools

-   Operations concept development

-   Proactive end-to-end risk analysis management and abatement

-   Facilitate and coordinate designs across the contract, that are
    consistent with the NASA strategic architecture directions

-   Security engineering and analysis

The contractor shall:

-   Provide system-engineering support of all modification requests per
    the Change Process defined in section 1.5.5.2.

-   Receive NASA approval, per section 1.5.5.2, for all modifications
    that require a change to the IPS architecture or requirements.

-   Provide Design Review (DRD MSOC-JSC-0072) for all approved
    modifications.

-   Document in the Design Specification (DRD MSOC-JSC-0073) all
    approved modification changes to the IPS Architecture.

Performance standards for the response to NASA driven modification
requests are defined in section 1.5.1.2.6

The contractor shall:

-   Perform hardware and software modifications to IPS systems and
    subsystems, including both custom and COTS hardware and software,
    per the change mechanism defined in section 1.5.5.2. The contractor
    is responsible for providing all hardware and software required to
    implement the modifications, unless otherwise specified through the
    change process.

```{=html}
<!-- -->
```
-   Provide coordination of COTS software tools integration.

-   Provide integration and coordination with external organizations for
    interface changes due to modifications.

-   Provide sustaining engineering for all modifications to hardware and
    software.

-   Perform operational analysis and system engineering of all
    modifications.

-   Perform integration of all modifications with the current system and
    external organizations.

-   Perform verification testing of all modifications.

The contractor shall:

-   Provide delivery of modifications as a base service. The contractor
    is responsible for up to 2 modification deliveries per year of each
    IPS subsystem for modifications that are a requirement or
    architecture change. All other modifications shall be released as an
    independent modification delivery to operations per the Systems
    Lifecycle Process (DRD MSOC-JSC-0065) upon successful test
    completion.

-   Provide modifications that are a requirement or architecture change
    in the delivery methodology per the Systems Lifecycle Process (DRD
    MSOC-JSC-0065).

-   Maintain a schedule for all modifications. The NASA project manager
    approves schedule content and delivery date.

-   Provide coordination of each delivery or independent modification
    delivery with external organizations and NASA.

-   Receive NASA acceptance of the release per the Acceptance Review
    Package (DRD MSOC-JSC-0071).

The contractor shall provide an annual Fiscal Year Operating plan (DRD
MSOC-JSC-0022) that defines the modification content for the upcoming
Fiscal Year. The scope for the modification content is dependent upon
the NASA modification budget.

1.5.1.2.3 Maintenance and Sustaining Engineering

The contractor shall provide maintenance and sustaining engineering of
the facility and the associated systems and subsystems. For these
facilities, the contractor shall provide hardware and software support,
per the change mechanism of section 1.5.5.2. This includes associated
hardware and software (both COTS and custom) and Government Furnished
Equipment (GFE) provided systems. The performance expectation shall be
to the level of facility, system and subsystem availability and
reliability as specified by associated IPS Subsystem Level B
Requirements and in section 1.5.1.2.6.

The contractor shall provide system engineering support of all
sustaining engineering functions per the Change Process defined in
Section 1.5.5.2.

The contractor shall maintain and provide a Design Specification (DRD
MSOC-JSC-0073) and an Integrated Planning System (IPS) Future Facility
Change Plan (DRD MSOC-JSC-0067) for all sustaining engineering
functions.

Performance of maintenance and sustaining engineering shall include the
provision of spares and a spares depot, as required for the contractor
to meet the availability requirements, maintenance agreements with
hardware and software suppliers, software licenses, resolution of
anomaly reporting for the equipment and its operations, required test
equipment, installation equipment, technical personnel to perform
maintenance and repairs and sustaining engineering. Included is
installation of new equipment and interface cabling, as required by NASA
and Contractor approved processes, removal of obsolete equipment and
cabling per agreed to NASA and Contractor processes and the Equipment
replacement (reference section 1.5.5.1.4 Equipment Replacement &
Depreciation) for the facility.

The Contractor shall provide integration and installation of Government
Furnished Equipment (GFE) and software.

NASA is responsible for providing building power and plant engineering
and operations in accordance with requirements documents, including the
MOD/COD Memorandum of Understanding (JSC-27049). The Contractor shall be
responsible for technical power and coordination of plant engineering
and operations in accordance with requirements documents.

The contractor shall:

-   Provide coordination of COTS software tools integration.

-   Provide integration and coordination with external organizations for
    interface changes.

-   Perform operational analysis and system engineering of all updates.

-   Perform integration with the current system and external
    organizations.

-   Perform verification testing of all updates, including testing of IT
    security capabilities.

The contractor shall:

-   Provide releases of sustaining updates as a base service per the
    Systems Lifecycle Process (DRD MSOC-JSC-0065). The contractor is
    responsible for up to 6 releases per year of each IPS
    subsystem/system for sustaining updates and code corrections.
    Sustaining changes that are independent from the release can be
    released to operations, per the Systems Lifecycle Process, upon
    successful test completion.

-   Maintain a schedule for all sustaining updates and changes. The NASA
    project manager approves schedule content and delivery date.

-   Provide coordination of each release with external organizations and
    NASA.

-   Receive NASA acceptance of the release per the Acceptance Review
    Package (DRD MSOC-JSC-0071).

-   Provide to NASA at any time a copy of the IPS software (source and
    executables, including scripts and configurables). NASA shall accept
    responsibility for any export control of the software.

The contractor shall provide an annual Fiscal Year Operating plan (DRD
MSOC-JSC-0022) that defines the sustaining bases of estimate & content
for the upcoming Fiscal Year to meet the sustaining requirements.

1.5.1.2.4 Operations

The contractor shall provide IPS operations services that include the
capabilities to conduct mission planning and support.

The contractor shall:

-   Provide a Training and Certification Plan (DRD MSOC-JSC-0053) to
    describe the contractor's plans for training and certification of
    operational support personnel for the MCC-H and IPS facilities.

-   Provide trained and certified personnel to support the capabilities
    to operate, control, setup and change IPS configurations and
    operational status for: ground systems, subsystems, support systems,
    external interfaces and networks. This includes IPS system and
    subsystem software and hardware configurations, allocation of
    equipment and system/subsystem status and control.

Operation support services shall be provided in support of the Day of
Launch Initialization Load Update (DOLILU) requirement. The contractor
shall maintain Facility Operations Procedures (DRD MSOC-JSC-0051) for
IPS operations.

1.5.1.2.5 Facility Operations

The Contractor shall provide the following IPS facility operation:

-   Security Level - Mission Critical Security Services

```{=html}
<!-- -->
```
-   For DOLILU (flight critical system)

    -   DTS analyst on-site at L-16 until release after launch

    -   Sys Admin on-site at L-8 until release after launch

    -   2 hour on-call response time for contingency landing support

-   For IPS platform in general

    -   12x5 on-site support

    -   24-hour hardware repair time

```{=html}
<!-- -->
```
-   For the IPS PC Subnet

    -   8x5 on-site support

    ```{=html}
    <!-- -->
    ```
    -   2-hour return call for duty hours outside of the 8X5 normal
        support period. This support is required for up to 5 Shuttle-ISS
        Assembly flights per year, for Shuttle Launch -2 days through
        landing;

    -   24 hour restore to ops for the PC Subnet ISO Servers for up to 8
        times per year."

The Contractor shall provide Security Level- Mission Support System
Services for the IPS PC Subnet.The contractor shall maintain Facility
Operations Procedures (DRD MSOC-JSC-0051) for IPS facility operations.

1.5.1.2.6 Performance Standards

The contractor provides ground systems services for IPS in accordance
with requirements documents contained in the IPS Level A and Level B
Requirements.

For DOLILU:

Required Service: Provide ground systems services for Day-of-Launch
Initialization-Load Updates (DOLILU).

Std of Excellence: 99.95% reliability for 4 hours of critical functions
as defined in JSC-13565, IPS Level A Requirements.

Expectation: 99.5% reliability for 4 hours of critical functions as
defined in JSC-13565, IPS Level A Requirements, and in no case impact
safety, mission success, or major program schedule milestones.

For the IPS Platform in general:

Required Service: Provide ground system services for IPS platform

Std of Excellent: 100% availability, excluding scheduled downtime

Expectation: 98% availability of non-critical functions, for all
unscheduled outages and down times

> 95% availability of non-critical functions, for all scheduled and
> unscheduled outages and down times

The contractor provides support for modification design and cost per the
change mechanism defined in section 1.5.5.2. The response standards for
per Type 1 Design Review (DRD MSOC-JSC-0072) are defined as:

Required Service: Provide design and cost impact for NASA driven
modifications

STD of Excellence: Complete design and cost response in 8 weeks from SR
submittal for 95% of the yearly modifications. SR submittal is defined
as the time when the NASA Project manager or designee, where applicable,
submits the SR to the CM process for tracking.

Expectation: Complete design and cost response in 10 weeks from SR
submittal for 95% of the yearly modifications

The contractor provides modification and implementation of maintenance
support for IPS software. The standards for Anomaly Report (AR) density
are as follows:

Required Service: Maintain at or below the following "Open" anomaly
density (AR/KSLOC) for new and existing IPS software.

Std of Excellence: 1 Anomaly per 8 KSLOC for mature software (greater
than 2 years old) and 1 anomaly per 2 KSLOC for code less than 2 years
old.

Expectation: 1 Anomaly per 5 KSLOC for mature software (greater than 2
years old) and 1 anomaly per 1 KSLOC for code less than 2 years old.

The standards for the response to SR implementation of hardware and
software changes is defined as:

Required Service: Implementation of hardware and software changes
response.

Implementation completion is defined as Return to Operations (RTO) for
hardware changes and the release or delivery of a software change.

Expectation: Implementation of hardware or software reconfigurations or

> modifications, that are priority 1 flight specific, shall be completed
> by Operational Need Date (OND) for the flight specified.

The standards for the response to Support Request (SR)
RTO/delivery/release of hardware and software changes are defined as:

Required Service: RTO/delivery/release of hardware and software changes
by the approved delivery/release date. Approved RTO/delivery/release
date is defined as the negotiated and NASA Project Manager approved date
that the contractor is expected to complete the SR implementation.

Std of Excellence: Delivery/release of hardware and software changes
shall be no longer than 14 days from the approved RTO/delivery/release
date (impacts due to flight window changes are excluded with NASA
project manager approval)

Expectation: Delivery/release of hardware and software changes shall be
no longer than 30 days from the approved RTO/delivery/release date
(impacts due to flight window changes are excluded with NASA project
manager approval)

1.5.1.2.7 Test and Checkout

The contractor shall:

-   Provide verification of all releases per the Test and Verification
    Plan and Procedures (DRD MSOC-JSC-0068 and DRD MSOC-JSC-0069) due to
    modification or maintenance change.

-   Provide verification of the operational IPS environment.

-   Report test status.

-   Provide Test and Verification Reports (DRD MSOC-JSC-0070).

-   Receive NASA approval of system test procedures, system test plan,
    and system test completion.

-   Provide necessary test tools to complete verification.

-   Be responsible for scheduling all required test resources.

The contractor shall:

-   Perform performance testing on all major modification and sustaining
    releases per the Test and Verification Plan (DRD MSOC-JSC-0068),
    including IT security capabilities.

-   The Contractor shall provide inputs to the International Ground
    System Specification (IGSS) verification compliance matrix.

The contractor is responsible for verification of all Interface Control
Documents, including IT security capabilities. This includes support of
joint testing with the external facilities.

1.5.1.2.8 Interface Support

Management - The contractor shall provide support for documentation of
all IPS interfaces as defined in the IPS Level A requirements.

Technical - The contractor shall:

-   Provide support for the integration of all IPS interfaces as defined
    in the IPS Level A requirements.

```{=html}
<!-- -->
```
-   Install and maintain the external interfaces for the IPS external
    customers.

-   Provide installation and maintenance for the interfaces.

-   Provide system testing and integration support.

-   Provide all system interfaces.

-   Provide technical systems engineering and operational support to the
    Ground Segment Control Board (GSCB) and International Technical
    Interchange Meetings (TIMs).

1.5.1.2.9 Certification and Training

The contractor shall establish their training and certification plan for
Maintenance and Operations personnel adhering to OSHA and JSC safety
standards and guidelines. The plan should generally follow the
guidelines of the flight control team certification requirements that
are defined in the NASA Mission Operations Directorate, Space Flight
Personnel Certification Plan (DA-WI-16).

1.5.1.2.10 Metrics/Data and Reports

The Contractor shall provide metrics and reports per DRD MSOC-JSC-0007.

The Contractor shall provide metrics reports providing insight into the
facility operations:

-   Integrity metrics -- monthly and quarterly

-   Availability --monthly, and weekly (summed daily) electronic
    availability reports

The Contractor shall provide data reports providing insight into the
facility status:

-   Performance -- quarterly

The Contractor shall provide management reports providing insight into
the overall facility and support meetings:

-   Activity Report - weekly

-   Facility Status Report - daily

-   Project Integration Meeting (IPT) - monthly

-   Delivery Schedules Report - monthly

-   Work Plan Report (SR Work Plan) -- Weekly

-   DRD Status Report -- monthly

-   Project Status Reviews (PSR) -- monthly

-   Process Integrity Metrics Review (PIMR)-quarterly

-   IPS Staff Meeting -- weekly

-   MOD Flight Readiness Review (FRR) (in support of the Mission
    Management contractor for flight/increment readiness -- per flight
    and increment)

-   MOD Flight Operations and Integration Group (FOIG)- weekly

-   MOD Facility Status Telecon -- daily

-   IPS Platform Change Assessment Group (PCAG) -- Monthly

-   IPS Users' Meeting --bi-monthly

-   IPS User Scheduling Coordination Meeting --bi-monthly

```{=html}
<!-- -->
```
-   IPS Control Board -- Monthly

-   IPS Technical Control Panels (TCP) -- bi-monthly

-   Data Administrator Working Group (DAWG) -- Monthly

-   IPS/MCC-H Joint PCAG/TCP -- Monthly

##### Requirements Documentation and Facility DRD's

The Contractor shall adhere to the latest revision of the following
requirements documents:

-   ISSP International Ground Segment Specifications, SSP-54500

-   ISSP Requirements Document, PRD/OR/PSP/OD 30000

-   Internal Partner Protocol Agreements

-   Requirements for Network, MCC-H Communications Systems, Ground
    Facilities, and Consulting Groups for Joint USA/Russia Manned Space
    flight, WG-3/RSC E/NASA/005/3233

-   SSP 50200-01 Station Program Implementation Plan Vol. 1: Station
    Program Management Plan

-   SSP 50200-02 Station Program Implementation Plan Vol. 2: Program
    Planning and Manifesting

-   SSP 50110 Multi-Increment Manifest Document

-   Space Shuttle Program Requirements Document (Flight Operations Vol.
    I and II, Launch and Landing Vol. I and II), PRD/OR/PSP/OD 20000

-   Space Shuttle Program, NSTS-07700 Volumes 8 and 14

-   IPS Functional Requirements, JSC-13565

-   ISS Orbital Volume I and II PRD/OR/PSP/OD 30000

-   Software Management Plan USA000622

-   Critical Processor Certification Policy USA002295

-   Facility Management Policy USA002955

-   MCC-H and IPS Operational Change Control Procedures SFOC-FL2333

-   Flight Controllers Operations Handbook (FCOH)

The Contractor shall establish, maintain, adhere to, and publish the
following facility documents and DRD's:

-   All documents defined in Table 1.5.1.2.11

```{=html}
<!-- -->
```
-   Integrated Planning System (IPS) Facility Operations Procedures
    (MSOC-JSC-0051)

```{=html}
<!-- -->
```
-   Integrated Planning System (IPS) Future Facility Change Plan
    (MSOC-JSC-0067)

```{=html}
<!-- -->
```
-   Systems Lifecycle Process

-   Test and Verification Plan

-   Test and Verification Procedures

-   Test Reports

-   Interface Control Documents (DRD MSOC-JSC-0063)

-   Design Notebook and Specifications

-   Non Maintainable Equipment Replacement Plan

-   Design Review

-   Fiscal Year Operating Plan and Program Operating Plan (POP)

-   Security Plan

-   COFR Endorsement

-   Acceptance Review

-   Change Control Process

-   Level A and B requirements (DRD MSOC-JSC-0062)

-   IPS Operations Concept (DRD MSOC-JSC-0074)

+-----------------------------+----------------------------------------+
| Table 1.5.1.2.11            | IPS SYSTEMS LEVEL A/B REQUIREMENTS and |
|                             | INTERFACE CONTROL DOCUMENTS (ICDs)     |
+=============================+========================================+
| IPS System                  | Level A Requirements Document          |
+-----------------------------+----------------------------------------+
| Integrated Planning System  | JSC-13565, "IPS Level A Requirements." |
| (IPS) Level A Requirements  | Latest revision.                       |
+-----------------------------+----------------------------------------+
| IPS System                  | Level B/C Requirements Document        |
+-----------------------------+----------------------------------------+
|                             | JSC-37505, "IPS Platform Subsystem     |
|                             | Level B requirements," latest revision |
|                             |                                        |
|                             | JSC-13350, "IPS Consolidated Planning  |
|                             | System (CPS) Subsystem Functional      |
|                             | Requirements," latest revision         |
|                             |                                        |
|                             | JSC-13352, "IPS Resource Utilization   |
|                             | Planning and System Model (RUPSM)      |
|                             | Subsystem Functional Requirements,"    |
|                             | latest revision                        |
|                             |                                        |
|                             | JSC-13419, "IPS Flight Dynamics        |
|                             | Planning and Analysis (FDPA) Subsystem |
|                             | Functional Requirements," latest       |
|                             | revision                               |
|                             |                                        |
|                             | JSC-13325, "IPS Procedure Development  |
|                             | and Control (PDAC) Subsystem           |
|                             | Functional Requirements," latest       |
|                             | revision                               |
|                             |                                        |
|                             | JSC-12804, "Mission Control Center     |
|                             | (MCC) Level A requirements," latest    |
|                             | revision                               |
|                             |                                        |
|                             | JSC Letter DA9-02-02, "MCC PC Network  |
|                             | Hosting Policy," February 2002         |
|                             |                                        |
|                             | Implementation of modifications to the |
|                             | IPS should adhere to the standards and |
|                             | constraints specified in JSC-13565,    |
|                             | including Appendix C, unless           |
|                             | justification is provided and approved |
|                             | by the NASA IPS Project Manager.       |
|                             |                                        |
|                             | Implementation of external interfaces  |
|                             | to IPS shall be as specified in        |
|                             | JSC-13565 and the associated Interface |
|                             | Control Documents.                     |
+-----------------------------+----------------------------------------+
| **IPS Interface**           | Interface Control Document             |
+-----------------------------+----------------------------------------+
| See MCC ICD Table           | See MCC ICD Table 1.5.1.1.1            |
| 1.5.1.1.11                  |                                        |
+-----------------------------+----------------------------------------+
| Attitude and Pointing       | JSC-13640, IPS and Attitude and        |
| Flight Production Facility  | Pointing Flight Production Facility    |
| (APFPF)                     | (APFPF) Interface Control Document,    |
|                             | latest revision                        |
+-----------------------------+----------------------------------------+

1.5.2 Mission Support Services Function

The mission support services function provides communication and
software development support environments to streamline HSF mission
support.

1.5.2.1.1 Management

The contractor shall provide mission management services such as those
processes that accomplish the planning, interface testing and
verification, systems engineering, sustaining engineering, design,
development, logistics, operations, and analysis of missions and the
processing and storage of launch vehicle, spacecraft, payload,
instrument, ground system and network data. Mission services for this
facility are defined as those services provided by the ESTL to the
Programs and are provided in support of the ESTL. Mission services can
be either real-time or non real-time. Mission services shall include
support to Technical Interchange Meetings (TIMs) to establish technical
and operational interfaces and procedures with the Mission Control
Center or other entities.

The day-to-day schedule shall be at the direction of the NASA ESTL
Facility Manager or designee. Daily test conduct is the responsibility
of the Engineering, Analysis, and Test contractor and the MSOC
contractor shall provide area engineering support membership on the test
team for the supported areas.

Support provided by the MSOC contractor is limited to Area Engineering
for the following areas: a second Tracking Data Relay Satellite System
(TDRSS) Ground Terminal (STGT), Ground Spacecraft Tracking and Data
Network (GSTDN) ground station, and Command, Telemetry and Recording
Area (CTRA) and includes the non-spacecraft Antenna systems and MCC-H
ground hardware. It is essential that the ESTL TDRSS and GSTDN hardware
be exact duplicates of the STGT and GSTDN equipment, making the
identification and incorporation of TDRSS and GSTDN engineering changes
into the ESTL hardware critical.

The expertise to provide the configuration management, incorporate
engineering changes, and maintain and operate these systems resides with
the GSFC contractor responsible for the STGT and GSTDN sites. Therefore,
the contractor shall coordinate all ESTL functions, with the exception
of repair, upgrade, and replacement of MCC-H hardware systems, with the
GSFC contractor responsible for those functions at White Sands Complex
and at the GSTDN sites.

Mission Services consist of Ground Systems Services, which provide the
necessary capabilities (e.g., hardware, software, sustaining
engineering, facility and system documentation) and service operations
(e.g., data systems operators, maintainers and operations and
maintenance documentation) required to conduct Mission Operations, and
Mission Operations Services which are those required to execute missions
for users, defined as those services provided by the ESTL to the
Programs.

1.5.2.1.2 Modification and Systems Engineering

For the ESTL, the contractor shall:

-   Provide systems engineering, modification engineering and service
    integration for all systems and subsystems in the STGT, GSTDN, and
    CTRA areas, and non-spacecraft antennas. These services include
    modification, upgrade, or replacement to the STGT, GSTDN, CTRA
    areas, non-spacecraft antennas, MCC-H hardware and software systems
    and interfaces required for tests in the ESTL, and hardware and
    software systems required for support of aircraft customers.

-   Provide supporting services that include technical analyses, cost
    assessment, "make/buy" decisions, and other specific activities
    necessary to accomplish the provisioning of services.

Typical systems engineering functions include:

-   Integrated service elements and spacecraft solutions

-   End-to-end Mission, Data and Center Unique service integration
    required for ESTL testing

-   Requirements management, analysis and requirements/design trade
    studies

-   Establishing systems engineering processes

-   Integrated architecture baseline configuration management and
    planning

-   Design Analyses, architecture trade-off, and Make or Buy assessments

-   System-level functional design developments

-   Engineering strategies development

-   Service capacity, performance, and life cycle cost forecasting

-   Evaluating and testing commercial off-the-shelf (COTS) software and
    hardware products including development and coordination of COTS
    tools for the ESTL.

-   Security engineering and analysis

The contractor shall procure COTS hardware and software tools and
associated vendor maintenance contracts supporting user interfaces;
provide sustaining engineering, operations analysis, systems
engineering, integration, testing, logistics, custom software/hardware
development, and coordination of COTS tools for the ESTL; and provide
property management for the ESTL government and contractor property.

The contractor shall institute a procurement process to enable a rapid
response to test needs.

The contractor shall provide an annual Fiscal Year Operating plan (DRD
MSOC-JSC-0022) that defines the modification content for the upcoming
Fiscal Year. The scope for the modification content is dependent upon
the NASA modification budget.

1.5.2.1.3 Maintenance and Sustaining Engineering

The contractor shall:

-   Provide maintenance and operations of the ESTL STGT; GSTDN; CTRA
    areas; non-spacecraft antennas; and the ESTL Front-End Processor;

-   Provide modification and management of equipment in support of
    avionics customers. Equipment is contractor-maintained
    installation-provided government property.

The contractor shall provide systems engineering, maintenance and
sustaining engineering of the ESTL areas included in the previous
paragraph and the associated hardware and software components (both COTS
and custom).

-   Performance of maintenance and sustaining engineering includes the
    provision of spares, maintenance agreements with hardware and
    software suppliers, software licenses, resolution of anomaly
    reporting for the equipment and its operations, required test
    equipment installation, technical personnel to perform maintenance
    and repairs, and sustaining engineering support of these maintenance
    functions.

```{=html}
<!-- -->
```
-   Also Included is installation of new equipment and interface
    cabling, as required by NASA and Contractor approved processes,
    removal of obsolete equipment and cabling per agreed to NASA and
    Contractor processes and the Equipment Replacement Plan for the ESTL
    facility.

The contractor shall provide an annual Fiscal Year Operating plan (DRD
MSOC-JSC-0022) that defines the maintenance and sustaining engineering
content for the upcoming Fiscal Year.

1.5.2.1.4 Operations

The contractor shall support the ESTL in the provision of the following
facility operations services:

-   Support of the Shuttle Program Office and Station Program Office
    requested testing -- These tests are performed in the ESTL for
    customers outside the Avionic Systems Division (ASD) and for various
    Communications and Tracking subsystem managers from within the ASD.
    These tests include mission anomaly investigations, compatibility
    verification of payloads and modifications/upgrades to spacecraft
    communications and systems, and end-to-end system level engineering
    and verification testing of manned space flight communications
    systems, including ground elements, orbiting relay satellites and
    spacecraft hardware.

-   Support aircraft customers in the tracking of aircraft and recovery
    of experimenter data.

1.5.2.1.5 Facility Operations

Contractor shall provide the operation of ESTL STGT, GSTDN, CTRA, and
non-spacecraft antenna systems:

-   Security level- Mission Support System Services

-   Operations: 8x5

-   On call and special request support to be provided to meet critical
    activities

1.5.2.1.6 Performance Standards

The JSC ESTL shall have the following performance standards:

Required Service: JSC ESTL STGT, GSTDN, CTRA, and non-spacecraft antenna
systems availability.

Std of Excellence: 85% readiness of responsible areas.

Expectation: 80% readiness of responsible areas.

1.5.2.1.7 Test and Checkout.

Test and checkout shall be performed as necessary to ensure readiness of
systems and subsystems in all responsible areas to support the ESTL test
customers.

1.5.2.1.8 Interface Support

Management -- The contractor shall provide area configuration
documentation for all responsible areas, maintain property records in
accordance with JSC property procedures and maintain the master
configuration documentation for the facility.

Technical -- The contractor shall provide support for integration of
systems into the responsible areas and into the facility configuration
in cooperation with the Science, Engineering, Analysis and Test
(SEAT**)** contractor.

1.5.2.1.9 Certification, Training and Travel

Training should be provided in accordance with the ESTL required
training, as appropriate to maintain both maintenance and engineering
skills in support of maintenance, sustaining and system engineering
services for the ESTL, and shall include 2 years On the Job Training for
certification to perform area engineering duties.

Travel should be provided as necessary to support the ESTL test and
aircraft customers.

1.5.2.1.10 Metrics and Reports

Reporting shall be to the NASA ESTL Facility Manager or designee via
status and test planning meetings held according to the facility test
requirements, or at the Daily Coordination Meeting. Metrics shall be
based on area readiness to support the ESTL test schedule.

The Contractor shall not be required to provide any reports or
presentations, written or verbal on the status of testing, test results
or any analyses of tests performed in the Laboratory or on any general
aspect of Laboratory activity to outside entities.

As the contractor is providing only technical support to NASA as part of
a larger team effort, NASA JSC ESTL retains the sole right to produce,
release and distribute technical and status reports concerning
Laboratory activities.

11. Requirements Documentation and DRD's

ESTL General Operating Procedure, ESTL-SOP 001 (current revision).

1.5.2.2 Consolidated Development Environment (CDE)

CDE is located at JSC, Building 30s, Rm. 4302, 4318 and 4327, within the
MCC-H facility, and 600 Gemini, as a supporting facility to flight
operations development requirements.

1.5.2.2.1 Management

The contractor shall provide CDE management services such as those
processes that accomplish the planning, interface testing and
verification, systems engineering, sustaining engineering, design,
development, logistics, operations and analysis of systems for the
facility in support of the following MCC-H flight support development
and sustaining activities:

-   Software platform development, modification, delivery, test
    verification and deployment into the operational environment

-   User Application software development, modification, delivery, test
    verification and deployment into the operational environment.

-   Hardware systems development, modification, delivery, test
    verification and deployment into the operational environment.

-   Flight support reconfiguration products development, delivery,
    modification, test verification and deployment into the operational
    environment.

1.5.2.2.2 Modification and Systems Engineering

For the CDE, the contractor shall:

-   Provide systems engineering, modification engineering and service
    integration for all systems and subsystems as defined in the Level A
    and B requirements for these facilities. These services include
    modification, upgrade or to the MCC-H hardware and software systems
    and interfaces.

-   Provide supporting services that include technical analyses, cost
    assessment, "make/buy" decisions, and other specific activities
    necessary to accomplish the provisioning of services.

Typical systems engineering functions include:

-   Integrated service elements and spacecraft solutions

-   End-to-end Mission, Data and Center Unique service integration

-   Requirements management, analysis and requirements/design trade
    studies

-   Establishing systems engineering processes

-   Operations and development systems standards support, coordination,
    and control

-   Integrated architecture baseline configuration management and
    planning

-   Design analyses, architecture trade-off, and Make or Buy assessments

-   System-level functional designs development

-   Engineering strategies development

-   Service capacity, performance, and life cycle cost forecasting

-   External interface negotiation and design

-   Facilitate and coordinate services across the contract, consistent
    with the strategic architecture

-   Evaluating and testing commercial off-the-shelf (COTS) software and
    hardware products including development and engineering tools

-   Facility and Ops Support Team Operations concept development

-   Proactive end-to-end risk analysis management and abatement

-   Security engineering and analysis

The contractor shall receive NASA approval for all modifications that
require a change to the CDE architecture or requirements. Performance
standards for the response to NASA driven modification requests are
defined in section 1.5.2.2.6

The contractor shall:

-   Perform hardware and software modifications to CDE systems and
    subsystems per the change mechanism defined in section 1.5.5.2.

-   Perform modifications to contractor developed hardware and software
    as defined in this contract.

-   Perform modifications to COTS software and hardware as defined in
    this contract.

The contractor shall:

-   Provide coordination of COTS software tools integration.

-   Provide integration and coordination with external organizations for
    interface changes due to modifications.

-   Provide sustaining engineering for all modifications to hardware and
    software.

-   Perform operational analysis and system engineering of all
    modifications.

-   Perform integration of all modifications with the current system and
    external organizations.

-   Perform verification testing of all modifications.

```{=html}
<!-- -->
```
-   The contractor shall provide coordination of modifications with
    external organizations and NASA.

The contractor shall provide an annual Fiscal Year Operating plan (DRD
MSOC-JSC-0022) that defines the modification content for the upcoming
Fiscal Year. The scope for the modification content is dependent upon
the NASA modification budget.

1.5.2.2.3 Maintenance and Sustaining Engineering

The contractor shall provide systems engineering, maintenance, and
sustaining engineering of the CDE and the associated hardware and
software components.

-   This includes associated hardware and software (both COTS and
    custom). Performance of maintenance and sustaining engineering
    includes the provision of spares, maintenance agreements with
    hardware and software suppliers, software licenses, resolution of
    anomaly reporting for the equipment and its operations, required
    test equipment installation, equipment, technical personnel to
    perform maintenance and repairs and sustaining engineering support
    of these maintenance functions.

```{=html}
<!-- -->
```
-   Included shall be installation of new equipment and interface
    cabling, as required by NASA and Contractor approved processes,
    removal of obsolete equipment and cabling per agreed to NASA and
    Contractor processes and the Equipment Replacement plan for the CDE
    facility.

The contractor shall provide an annual Fiscal Year Operating plan (DRD
MSOC-JSC-0022) that defines the maintenance and sustaining engineering
content for the upcoming Fiscal Year.

1.5.2.2.4 Operations

The operations support to the CDE is to be provided per the Schedule of
MCC-H Activities process. The support would be defined as one of the
activities defined by section 1.5.1.1.5.

1.5.2.2.5 Facility Operations

1.  Security Level - Mission Critical System Services

2.  8 hrs. x 5 days (nominal)

-   24 hrs. x 7 days (as required)

-   8 hrs. x 5 days System Administration Support

1.5.2.2.6 Reserved

1.5.2.2.7 Test and Checkout

The contractor shall:

-   Test all changes to CDE hardware or software prior to releasing to
    CDE operations.

-   Provide Test and Verification Procedure (MSOC-JSC-0069) and Test and
    Verification Report (MSOC-JSC-0070) for CDE changes.

1.5.2.2.8 Interface Support

Management - The contractor shall:

-   Provide support for Interface Control Documentation (ICD) (DRD
    MSOC-JSC-0063) of all CDE interfaces.

-   Ensure continued services and compatibility for all external network
    interfaces.

User - The contractor shall:

-   Provide support for the Data Display and Computation system
    interfaces to user applications.

-   Provide support for performance analysis and testing of the
    interfaces.

-   Support troubleshooting of the interface

Technical - The contractor shall provide support for the maintenance,
operations, and integration of all CDE interfaces as defined in the MCC
Level A requirements.

1.5.2.2.9 Certification and Training

The contractor shall establish their certification and training plan for
Maintenance and Operations personnel adhering to OSHA and JSC safety
standards and guidelines

1.5.2.2.10 Metrics and Reports

The contractor shall provide Metric and Status Reports (MSOC-JSC-0007)
of the availability and utilization of CDE services.

1.5.2.2.11 Requirements Documentation and DRD's

Refer to section 1.5.1.1.11

1.5.2.3 Ground Systems Development Environment (GSDE)

The Ground Systems Development Environment (GSDE) is a NASA owned
facility used to develop ground systems for MCC-H, BCC-M, HSR-M and IPS.
Its focus is primarily hardware/infrastructure. Physical location is as
deemed necessary by both NASA and the contractor. This can be co-located
at the JSC facility or an off-site location at the contractor's
facility. Location should be determined as best expedites and provides
for the most cost effective means to provide the Ground Systems
Development support function. Typically, new systems shall be installed,
configured, tested and evaluated in the GSDE before deployment to the
CDE or I&T and then the Operational Control Center or IPS environment.

The GSDE is used to develop, test and certify platform services, user
applications, and other software prior to promotion into operations.

1.5.2.3.1 Management

The contractor shall provide GSDE management services such as those
processes that accomplish the planning, interface testing and
verification, systems engineering, sustaining engineering, design,
development, logistics, operations and analysis of systems for the
facility in support of the following MCC-H flight support development
and sustaining activities:

-   Software platform development, modification, delivery, test
    verification and deployment into the operational environment

-   Hardware systems development, modification, delivery, test
    verification and deployment into the operational environment.

1.5.2.3.2 Modification and Systems Engineering

For the GSDE, the contractor shall provide systems engineering,
modification engineering and service integration for all systems and
subsystems, including custom and COTS hardware and software, as defined
in the MCC-H and IPS Level A and B requirements for these facilities.
These services include modification, upgrade or replacement to the MCC-H
or IPS hardware and software systems and interfaces.

The contractor shall provide supporting services that include technical
analyses, cost assessment, "make/buy" decisions, and other specific
activities necessary to accomplish the provisioning of services.

Typical systems engineering functions, as appropriate, include:

-   Integrated service elements and spacecraft solutions

-   End-to-end Mission, Data and Site Support service integration

-   Requirements management, analysis and requirements/design trade
    studies

-   Establishing systems engineering processes

-   Operations and development systems standards support, coordination,
    and control

-   Integrated architecture baseline configuration management and
    planning

-   Design analyses, architecture trade-off, and Make or Buy assessments

-   System-level functional designs development

-   Engineering strategies development

-   Service capacity, performance, and life cycle cost forecasting

-   External interface negotiation and design

-   Facilitate and coordinate services across the contract, consistent
    with the strategic architecture

-   Evaluating and testing commercial off-the-shelf (COTS) software and
    hardware products including development and engineering tools

-   Facility and Ops Support Team Operations concept development

-   Proactive end-to-end risk analysis management and abatement

-   Security engineering and analysis

The contractor shall obtain NASA approval for all modifications that
require a change to the GSDE architecture or requirements. Performance
standards for the response to NASA driven modification requests are
defined in section 1.5.2.3.6

The contractor shall:

-   Perform hardware and software modifications to GSDE systems and
    subsystems per the change mechanism defined in section 1.5.5.2.

-   Perform modifications to contractor developed hardware and software
    as defined in this contract.

-   Perform modifications to COTS software and hardware as defined in
    this contract.

The contractor shall:

-   Provide coordination of COTS software tools integration.

-   Provide integration and coordination with external organizations for
    interface changes due to modifications.

-   Provide sustaining engineering for all modifications to hardware and
    software.

-   Perform operational analysis and system engineering of all
    modifications.

-   Perform integration of all modifications with the current system and
    external organizations.

-   Perform verification testing of all modifications.

The contractor shall provide an annual Fiscal Year Operating plan (DRD
MSOC-JSC-0022) that defines the modification content for the upcoming
Fiscal Year. The scope for the modification content is dependent upon
the NASA modification budget.

1.5.2.3.3 Maintenance and Sustaining Engineering

Performance of maintenance and sustaining engineering includes the
provision of spares, maintenance agreements with hardware and software
suppliers, software licenses, resolution of anomaly reporting for the
equipment and its operations, required test equipment installation,
equipment, technical personnel to perform maintenance and repairs and
sustaining engineering support of these maintenance functions.

Also included is installation of new equipment and interface cabling, as
required by NASA and Contractor approved processes, removal of obsolete
equipment and cabling per agreed to NASA and Contractor processes and
the Equipment replacement plan for the GSDE facility.

The contractor shall:

-   Provide sustaining as required.

-   Provide systems engineering, maintenance, and sustaining engineering
    of the GSDE and the associated hardware and software components.
    This includes associated hardware and software (both COTS and
    custom).

The contractor shall provide an annual Fiscal Year Operating plan (DRD
MSOC-JSC-0022) that defines the maintenance and sustaining engineering
content for the upcoming Fiscal Year

1.5.2.3.4 Operations

Operations support is primarily maintenance and sustaining engineering.

1.5.2.3.5 Facility Operations

The contractor shall provide:

-   Security Level - Mission Critical Support System Services

-   8x5 except for special support 24x7 as needed

-   8X5 of system administration support.

1.5.2.3.6 Reserved

1.5.2.3.7 Test and Checkout

The contractor shall test all changes to GSDE hardware or software prior
to releasing to GSDE operations. . The contractor shall provide Test and
Verification Procedure (MSOC-JSC-0069) and Test and Verification Report
(MSOC-JSC-0070) for GSDE changes.

1.5.2.3.8 Interface Support

Management -The contractor shall:

-   Provide support for Interface Control Documentation (ICD) (DRD
    MSOC-JSC-0063) of all GSDE interfaces. .

-   Ensure continued services and compatibility for all external network
    interfaces.

Technical - The contractor shall provide support for the maintenance,
operations, and integration of all GSDE interfaces.

1.5.2.3.9 Certification and Training

The contractor shall establish their certification and training plan for
Maintenance and Operations personnel adhering to OSHA and JSC safety
standards and guidelines

1.5.2.3.10 Reserved

1.5.2.3.11 Requirements Documentation and DRD's

Refer to Section 1.5.1.1.11

1.5.3 Site Support Services

Site support includes those facilities providing support to the
personnel housed at JSC, Ellington Field and the Sonny Carter Training
Facility.

1.5.3.1 Emergency Operations Center (EOC)

The Emergency Operations Center (EOC) provides site emergency management
response. This includes emergency event detection via phone, radio, or
remote sensing devices; emergency dispatch of Security, Fire and EMS
personnel; and the response coordination of emergency response
organizations. Operation of this facility, which is staffed
continuously, is the responsibility of another contractor.

The EOC is located at JSC, building 30. The Emergency Operations Center
(EOC) is the facility used to coordinate all security, fire protection
and medical field activities through receiving and transmitting
emergency communications. The EOC Dispatch Center (EDC) coordinates all
emergency response activities at the Johnson Space Center (JSC).

[The Security Access Control (SAC) system is subsystem to the EOC, which
provides access controls at various buildings at JSC, Ellington Field,
and SCTF and badging functions for JSC.]{.underline}

1.5.3.1.1 Management

The contractor shall provide EOC support services such as those
processes that accomplish the planning, interface testing and
verification, systems engineering, sustaining engineering, design,
development, logistics, operations, and analysis for the facility
dispatch console systems and its integration with other support systems.
[The contractor shall also provide systems engineering, sustaining
engineering, and maintenance for all elements of the SAC.]{.underline}

1.5.3.1.2 Modification and Systems Engineering

The contractor shall:

-   Provide systems engineering, modification engineering and service
    integration for all EOC designated systems and subsystems, including
    custom and COTS hardware and software, as defined in the Level A and
    B requirements for these facilities. These services include
    modification, upgrade or replacement to the EOC hardware and
    software systems and interfaces.

-   Provide supporting services that include technical analyses, cost
    assessment, "make/buy" decisions, and other specific activities
    necessary to accomplish the provisioning of services.

The contractor shall provide sustaining engineering and hardware and
software support for all EOC designated systems and subsystems per the
change mechanism of section 1.5.5.2.

The contractor shall also perform operations analysis, system
engineering, integration, testing, logistics, and also provide
coordination of COTS software tools integration.

Typical systems engineering functions include:

-   Integrated service elements

-   Center Unique service integration

-   Requirements management, analysis and requirements/design trade
    studies

-   Establishing systems engineering processes

-   Operations and development systems standards support, coordination,
    and control

-   Integrated architecture baseline configuration management and
    planning

-   Design analyses, architecture trade-off, and Make or Buy assessments

-   System-level functional designs development

-   Evaluating and testing commercial off-the-shelf (COTS) software and
    hardware products including development and engineering tools

-   Facility Operations concept development

-   Proactive end-to-end risk analysis management and abatement

-   System configuration control

Configuration Control includes all hardware, software, and integration
documentation. Integration documentation includes design analyses,
schematics, equipment description, software description, interface
drawings, maintenance requirements and spare parts list.

The contractor shall provide edits and changes to the systems
configuration control package to the Manager, Emergency Operations
Office within 30 days of change to the system.

The contractor shall provide sustaining and modification delivery
releases as a base service.

The contractor shall provide an annual Fiscal Year Operating plan (DRD
MSOC-JSC-0022) that defines the modification content for the upcoming
Fiscal Year. The scope for the modification content is dependent upon
the NASA modification budget.

1.5.3.1.3 Maintenance and Sustaining Engineering

Performance of maintenance and sustaining engineering includes the
provision of: spares, maintenance agreements with hardware and software
suppliers, software licenses, resolution of anomaly reporting for the
equipment and its operations, required test equipment installation,
equipment, technical personnel to perform maintenance and repairs, and
sustaining engineering support of these maintenance functions. Included
is installation of any new equipment and interface cabling, as required
by NASA in support of modification and engineering activities.

The contractor shall provide systems engineering, maintenance, and
sustaining engineering of the EOC and the associated level A and level B
hardware and software components. This includes associated hardware and
software (both COTS and custom).

For all equipment (hardware and associated firmware) identified below,
the contractor shall provide maintenance ([preventative and
reparative]{.underline})*,* system administration, data base
administration, CM, sustaining engineering, operations analysis, systems
engineering, training, testing, problem analysis and resolution,
security, documentation, logistics, scheduling, systems configuration
control and coordination.

1.  Audio System

2.  Speakers

3.  Monitors

4.  Electrical Tech-Power Panels

5.  Weather Station

6.  Console Housing and Equipment Cabinets

7.  Computer-Aided Dispatch (CAD) workstations and COTS software

8.  System Printer

9.  Un-interruptible Power Supply (UPS)

10. [CAD]{.underline} Interfaces: Fire Alarm, , ATM Alarm, , and
    Security Access Control Systems

11. EOC/INS Firewall/Router

12. Servers for Level A and Level B Systems

13. Integration, Verification and Test Equipment

14. [Security Access Control System, all elements, including field
    panels, badge readers, alarm controls, door hardware, badging
    workstations, servers, and COTS software.]{.underline}

[NASA EOC shall provide all required SAC engineering documentation in a
format usable by the contractor to sustain the SAC. The contractor is
not required to incorporate this documentation into the standard MSOC
Configuration Management toolset, but will use the construction drawings
supplied by NASA as the configuration control
documentation.]{.underline}

The contractor shall provide an annual Fiscal Year Operating plan (DRD
MSOC-JSC-0022) that defines the maintenance and sustaining engineering
content for the upcoming Fiscal Year.

1.5.3.1.4 Operations

The EOC operations [and badging operations]{.underline} are performed by
a different support contractor and are not applicable to this contract.

1.5.3.1.5 Facility Operations

The EOC is operational 24 hours a day, seven days each week. Dispatch
console and support systems shall be functional to meet facility
operations. Support services shall be sufficient to ensure that two of
the three Dispatch Consoles in the EDC are available and fully
operational at all times. The Security Level is defined as Mission
Support System Services.

[The SAC is operational 24 hours a day, seven days each week, in order
to provide security for mission essential infrastructure facilities. The
Security Level is defined as Mission Support System Services. Badging
workstations at Bldg. 110 are operational from 6 am to 10 pm 7 days a
week. The SCTF and Bldg. 30A badging workstations are operational 6:30am
to 4 pm, 5 days a week. The Bldg. 30A workstation is operational 24
hours per day during shuttle missions.]{.underline}

1.5.3.1.6 Performance Standards

The JSC EOC shall have the following performance standard:

Required Service: JSC EOC system availability.

Std of Excellence: 100% availability for the prime mission objective of
dispatching emergency equipment and personnel; 99% availability for the
secondary mission objective.

Expectation: 99% availability for the prime mission objective and 98%
availability for the secondary mission objective.

Availability figures are applicable to [the EOC's prime
mission]{.underline} of being capable of dispatching personnel to
emergencies as well as being able to monitor fire alarms, improper
access, or other security alarms. These availability requirements
pertain to the systems internal to the EOC and not to the external
interfaces, i.e., cameras, fire sensors, etc., which are the
responsibility of other contractors.

[For the security access control system, the following support is
required. Response to door hardware, badge reader, or field control
panel problems for mission essential infrastructure facilities shall be
within 2 hours of reporting. A minimum of two badging workstations shall
be available at JSC at all times. Response to SAC server problems will
be within 4 hours.]{.underline}

1.5.3.1.7 Test and Checkout

All hardware and software changes or new system capabilities shall be
tested, checked-out, and functionally verified. Testing, checkout and
verification shall be completed both on the EOC Test Lab System and at
Console 4, Integration, Verification and Test (IVT) Station before it is
up-loaded or changed out to the main EOC Dispatch Console systems. All
test and checkout reports shall be provided to the Manager, Emergency
Operations Office.

8.  Interface Support

Management - The contractor shall provide integration process
documentation for all level A systems and level B sub-systems supporting
the EOC dispatch center console functions. Some level B Sub-systems may
be provided by other contractors or the Government, but integration and
operation verification is required by the EOC functional support
contractor.

User - The contractor shall provide support for all EOC dispatch console
systems that are used by security contract personnel. The contractor
shall provide performance analysis and verification testing of all level
A systems and level B sub-systems.

Technical - The contractor shall provide support for integration of all
level A systems and level B sub-systems defined by EOC Level A and B
requirements.

Other -- Some level B sub-systems maybe provided by other contractors,
but integration and operation verification is required by the prime EOC
support contractor.

JSC Information Systems Directorate (ISD) is responsible for the
Information Network System (INS). Any INS network connectivity
requirements shall be coordinated through the Emergency Operations
Office (JA17).

Center Operations Directorate (COD) provides electrical power (refer to
MOU JSC-27049) to the lighting, receptacle, and tech-power panels within
the EOC.

1.5.3.1.9 [EOC IT Security Plan]{.underline}

[Per DRD MSOC--DRD-- 0010, the EOC IT security plan shall be maintained
and updated annually. The SAC system shall be included as part of the
EOC IT security plan.]{.underline}

1.5.3.1.10 Reserved

11. Reserved

1.5.4 Program Support Services (Level-of-Effort)

-   Program support services are those services provided directly in
    support of NASA. Personnel shall be familiar with all of the JSC
    Mission and Mission Support facilities to ensure proper technical
    interface support between MOD and the applicable NASA program or
    project. This section of the contract shall be initiated via Task
    Order using the Task Ordering Procedure clause contained in
    Section H. Travel plans for each PSS Task are per DRD MSOC-JSC-0023.

1.5.4.1 GSCB

The GSCB is a multilateral ISS Program level board that established a
baseline for and controls subsequent change to operations and mission
integration ground facilities related products. The GSCB also provides a
forum for the resolution of technical and schedule issues, including
joint operations and utilization issues.

Two Sub-Teams are chartered under the GSCB to work specific function
areas for ground systems interfaces and the contractor shall provide
support to these teams.

-   Security Analysis and Response Team (SART)

-   Network and Communications Analysis Integration Team (NACAIT)

1.5.4.1.1 Reserved

1.5.4.1.2 Reserved

1.5.4.2 Security Analysis and Response Team (SART)

The SART is chartered to integrate and coordinate ISS Program level
ground system security process. In support of SART, the contractor shall
provide a program level security risk analysis and risk mitigation
recommendations for the shared and networked ISS ground systems. The
contractor shall investigate ISS ground system security incidents, and
provide rapid response to security incidents.

The Security Analysis and Response Team (SART) provides for the
development of security agreements, security requirements, architecture
changes and security protective mechanisms applications for the IP
Interfaces with NASA. Service level of support shall be defined
annually. Average support is estimated at 3 FTE (estimate 1860 hrs/FTE)
annually.

1.5.4.2.1 Security Engineering Support

The contractor shall provide security-engineering support for:

-   Security Documentation review and evaluation for NASA and IP
    documentation

-   GSCB, MIOCB Document review and evaluation

-   Development of Program Process and Procedures regarding security

-   Security Incident support including, but not limited to, the
    development of operating procedures, event reporting, event response
    coordination, corrective action follow-up and final posture auditing

-   Security Protection Development support including, but not limited
    to, Security Risk Analysis, Security Requirements, Security Plans,
    Security Products and Implementation and Security Test support

-   Security projects scheduling

1.5.4.2.2 Documentation Support

The contractor shall provide for documentation generation, maintenance
and publication support for:

-   Program Process and Procedures

-   IP Agreement and Protocols

-   Interface Control Documents (ICD)

-   Security Plans

-   Technical Interface Meeting (TIM)

-   ISS Ground Segment schedules

-   Security Protection Documentation

1.5.4.2.3 Travel

As defined per the Travel Plan.

1.5.4.3 Network and Communications Analysis and Integration Team
(NACAIT)

The contractor shall provide support to the ISS Network and
Communications Analysis and Integration Team (NACAIT) by coordinating
and documenting Networks communications requirements. Additionally, the
contractor shall collect program requirements changes, work with various
program communities to validate the requirements, resolve any
discrepancies and document the final requirements in the program's
formal requirement document. Service level of support shall be defined
annually. Average support is estimated at 1 FTE (estimate 1860 hrs/FTE)
annually.

1.5.4.3.1 NPRD Documentation Support

The contractor shall provide for documentation generation, maintenance
and publication.

1.5.4.3.2 Travel

As defined per the Travel Plan.

1.5.4.4 Reserved

1.5.4.4.1 Reserved

1.5.4.4.2 Reserved

1.5.4.5 Program Requirements Document (PRD)

The contractor shall provide book management support of the Space
Shuttle and the International Space Station Program Requirements
Document into the Automated Support Requirements System (ASRS). The
contractor shall provide support to include identification, technical
analysis, coordination and documentation. Average support is estimated
at 2 FTE (estimate 1860 hrs/FTE) annually.

1.5.4.5.1 PRD Documentation Support

The contractor shall provide for documentation generation, maintenance
and publication.

1.5.4.5.2 Travel

As defined per the Travel Plan.

1.5.4.6 Human Space Flight (HSF) Network Operations Integration

The contractor shall provide technical integration support including
systems analysis and engineering support to the operations of the NASA
data services providers. These providers include the Wide Area Network,
the NASA Ground Networks, and the NASA Space Network support.
Additionally, the contractor shall assist in integrating the other NASA
centers and Department of Defense (DoD) support for HSF missions
including the use of tracking radars. The emphasis of this work shall be
in supporting certification that the space communications data services
are fully integrated and ready to support HSF missions.

This effort shall include, at a minimum, support in the preparation of
the:

-   Certificate of Flight Readiness (CoFR)

-   Associate Contractor Agreements (ACA)

-   Communications and Data Services Execution

-   Service Performance Metrics and Evaluation

-   Current and Pending Anomaly Resolution Reports

-   Space Improvement Recommendations

-   Periodic Roll-up reports on the status of the Space Communications
    Data Services Elements

Service level of support shall be defined annually. Average support is
estimated at 4 FTE (estimate 1860 hrs/FTE) annually.

1.5.4.6.1 Certificate of Flight Readiness (CoFR)

The contractor shall assist in the preparation of the CoFR
documentation. The contractor shall work with the NSG and NACAIT
organizations to plan the integrated implementation of space
communications data services required to support HSF missions. Also, the
contractor shall assist in the evaluation of required endorsement codes
within the CoFR implementation plan. This effort shall be documented in
a summary report on the results of providing space communications data
services for each mission in support of Progress, Automated Transfer
Vehicle (ATV), H-II Transfer Vehicle (HTV) and other scientific
laboratories.

1.5.4.6.2 Project Management Documentation Support

The contractor shall provide MSOC with project management documents
including service development and operations milestones and associated
schedules and cost and program evaluations that have sufficient depth to
identify problem areas in providing the services with options for
workarounds in the event of service interruption of any kind and for
whatever reason. Of particular attention, support shall be required to
provide an assessment and rollup of the ACAs necessary for successful
integrated service. Additionally, the contractor is expected to support
the MSOC at all HSF Readiness Reviews.

1.5.4.6.3 ICD Support

The integration effort shall require ICD's related to the Service
Providing Networks and the elements of the Mission support functions.
This effort shall include assurances that voice, video, and data shall
be available for mission services implementation. Particular attention
shall be given to the implementation plans at the hardware, software,
workforce, funding levels, and resource requirements. Supporting travel
shall be as defined per the Travel Plan.

1.5.4.7 Program Level Change Engineering Support and Integration

The contractor shall provide system engineering support services to the
government led effort of defining NASA's ongoing control center space
operations engineering projects.

1.5.4.7.1 System Engineering

The contractor shall provide system engineering support services to the
government lead effort of defining NASA's ongoing control center space
operations engineering projects. Engineering support shall include but
not be limited to systems engineering, spacecraft design and system
development skills to supplement government core competencies. The
support shall include, but not be limited to:

-   Providing studies, analyses, impact statements, end-to-end
    architecture tradeoff assessments, implementation plans and
    operations process reengineering for space operations change
    requests and proposed alternatives

Services levels of support shall be defined annually. Average support is
estimated at 3 FTE (estimate 1860 hrs/FTE) annually.

1.5.4.7.2 Reserved

1.5.4.8 Architectural and Engineering Support

The contractor shall provide system engineering and architectural design
support services to the NASA Architecture Panel and ongoing NASA control
center space operations engineering projects. All strategic engineering
activities shall be defined and scheduled by NASA. Engineering
activities shall be conducted at JSC, within an office and computer
laboratory environment. These NASA directed services shall include, but
are not limited to:

-   Studies and analysis of proposed operations modifications

-   Identifying and documenting alternative operations solutions

-   End-to-End architecture tradeoff assessment

-   Development of strategic and tactical plans

-   Implementation plans and strategies

-   Standards development

-   Investigating space operations process and reengineering

-   Evaluation of new NASA program requirements

-   Investigation of new technologies for possible operations
    modifications

Service level of support shall be defined annually. Average support is
estimated at 2 FTE (estimate 1860 hrs/FTE) annually.

The contractor's support of the NASA Architecture Panel in the
development, coordination, and refinement of the Mission Control Center
Systems (MCCS) strategic vision and tactical plans is reflected in the
estimates above.

1.5.4.8.1 Documentation

The contractor shall provide documentation generation and publication
support of the system engineering and architectural design results.

1.5.4.8.2 Travel

As defined per the Travel Plan.

1.5.5 Technical Administration Support

Technical support are those services that are applicable across all JSC
Mission, JSC Mission Support and the JSC Site facilities and services
identified in this SOW.

1.5.5.1 Resources

The contractor shall provide management, administration, documentation
and replacement monitoring over the physical hardware and software
resources that comprise the JSC HSF, JSC site and JSC Program support
facilities and services.

1.5.5.1.1 Property -- GFE

The contractor shall:

-   Have a property system in place, which is approved by a delegated
    property administrator.

-   Perform property management under the terms of the contract of all
    property owned, leased or acquired by the Government.

-   Provide, implement and maintain a Government Property Management
    Plan.

-   Perform maintenance and calibration on the Installation Provided
    Property for which the Government is accountable.

1.5.5.1.2 Property -- Capital

The contractor shall:

-   Have a property system in place, which is approved by a delegated
    property administrator.

-   Perform property management of all property owned, leased or
    acquired by the contractor under the terms of the contract.

-   Address capital property in the Contractor's Property Management
    Plan.

-   Perform maintenance and calibration on the capital property for
    which the contractor is accountable.

1.5.5.1.3 Technical documentation

The contractor shall provide technical documentation services that
accurately reflect, within 60 calendar days of Return to Operations
(RTO) for any hardware change and delivery of any software, the physical
and software configurations of the JSC Mission, JSC Mission Support and
the JSC site facilities, by facility.

1.5.5.1.4 Equipment Replacement

The integrated physical equipment and software that represent the JSC
Mission, JSC Mission Support and JSC site facilities defined in this SOW
are classified as Agency Peculiar and shall remain the responsibility of
the government to provide life cycle replacement and management.

The contractor shall:

-   Perform Non-Maintainable Equipment analysis and provide NASA with a
    recommended plan for all systems, subsystems and associated
    equipment (hardware and software), per DRD MSOC-JSC-0066.

-   Perform all equipment replacement per the change mechanism defined
    in section 1.5.5.2.

-   Provide a annual Fiscal Year Operating plan, per DRD MSOC-JSC-0022,
    that defines the equipment replacement content for the upcoming
    Fiscal Year. The scope for the equipment replacement content is
    dependent upon the NASA equipment replacement materials budget. All
    associated labor is considered in-scope for each Facility's
    Modification and Systems Engineering/Sustaining work content.

Equipment that enables the contractor to provide maintenance and
sustaining services remain the responsibility of the contractor to
provide and replace within their own equipment replacement plan and
shall remain the property of the contractor.

1.5.5.2 Configuration Management

The contractor shall:

-   Perform configuration management

-   Provide implementation, maintenance and documentation of a
    configuration management system that addresses identification,
    control, verification, and accounting for facilities, systems,
    interfaces, and mission reconfiguration products.

-   Provide configuration management products for the NASA change
    evaluation and control process.

Configuration management is part of the technical administration support
requirement, per DRD MSOC-JSC-0061, Configuration Management Plan. The
Contractor shall:

-   Perform configuration management,

-   Develop, provide, implement, and maintain a Configuration Management
    Plan for both hardware and software, in accordance with the above
    DRD. These Configuration Management Plans shall address
    identification and documentation of \'As-designed\' and \'As-built\'
    configurations, in addition to control, verification, and accounting
    of facilities, systems, interfaces, and mission reconfiguration
    products, to include training loads.

1.5.5.2.1 Change Authorization and Tracking

The contractor shall:

-   Track all modifications, systems engineering and sustaining
    engineering changes to the Mission services and Mission Support
    services and site services via a change or service request
    mechanism.

-   Provide a NASA approved process to manage change requests for the
    Mission Services, CDE, and GSDE facilities per DRD MSOC-JSC-0060,
    Change Control Process Plan. The process should include change
    submittal, NASA and contractor screening, impact assessment, NASA
    and contractor control board review and approval, authorization, and
    implementation status.

```{=html}
<!-- -->
```
-   Assume responsibility for the current Support Requirement (SR)
    database from the previous support contractors. The current database
    for MCC-H, BCC, HSR, EOC, ESTL, IPS, CDE, and GSDE is in
    (Configuration Management System (CMS) II format.

-   Provide a change authorization and tracking database that provides
    the following functionality:

```{=html}
<!-- -->
```
-   Provide electronic submittal and authorization of change requests

-   Provide electronic web access to change requests status from a
    centralized location. The contractor shall allow access to NASA and
    NASA contractors without additional ID/password controls.

-   Provide a user interface with search criteria fields and selection
    lists.

-   Provide electronic access control to change request cost impact
    information

-   Provide sorting on specified fields

-   Provide reports

The contractor shall provide facility specific metric and project status
reports on change request status as defined by NASA project manager.

NASA shall use the Transmittal/Information Request Form (TIRF) to
provide technical direction to the contractor and receive a status
response. The TIRF is used for general communications, submission of
documentation, and as a cover for all technical direction. The TIRF is
also used as a receipt/acknowledgment of and or response to direction.

1.5.5.2.2 Anomaly Status and tracking

The contractor shall:

-   Assume responsibility for the existing Anomaly Reports (ARs) from
    the previous support contractor in the current AR database.

-   Track all sustaining and maintenance anomalies of contractor
    responsible hardware and software via an AR.

-   Manage and track all ARs written on the contractor responsible
    hardware and software.

-   Utilize the current AR database that is the USA managed Discrepancy
    Reporting and Tracking System (DRTS).

-   Adhere to the policy and guidelines for AR prioritization as defined
    in USA002955 MCC Facility Management Policies and SFOC-FL2333 MCC-H
    and IPS Operational Change Control Procedures.

-   Respond to ARs based on priority provided by the initiator or NASA
    project management. AR performance standards for new and existing
    executable lines of code are defined in section 1.5.1.1.6 for MCC-H,
    BCC, and HSR and section 1.5.1.2.6 for IPS.

```{=html}
<!-- -->
```
-   Provide facility specific metric and project status reports on AR
    status as defined by NASA project manager.

-   Provide an Anomaly Report (AR) status and tracking systems such that
    the user community can obtain daily reports regarding the status of
    all ARs.

-   Provide users with information as to how to access this reporting
    system and its data.

The contractor shall:

-   Assume responsibility for all existing Operational Notes of the
    previous support contractor from the current Ops Note database.

-   Track all sustaining and maintenance temporary operational
    workarounds to ARs of contractor responsible hardware and software
    via the Ops Note.

-   Manage and track all Ops Notes written on the contractor responsible
    hardware and software.

-   Utilize the current Ops Note database, Manual Procedure Viewer
    (MPV).

1.5.5.2.3 Technical documentation

The contractor shall:

-   Provide configuration management of all contractor responsible
    documentation.

-   Keep the documentation up to date within the NASA agreed to update
    cycle for each document.

-   Provide a documentation change form and process for all Mission
    services Level A and B requirements.

-   Provide for NASA review prior to approval of required documentation.
    NASA approval of all data and documentation products, designated as
    Type 1, shall be required prior to contractor publication and work
    content implementation.

-   Provide and maintain a text based electronic documentation library,
    web accessible to all NASA and NASA support personnel. Documentation
    library will establish a documentation management plan and a
    document archive service.

1.5.5.3 Safety

The contractor shall provide facility safety and health support on a
daily basis to ensure the health and safety of all personnel occupying
the facilities, per JPG 1700.1(latest version).

1.5.5.3.1 Personnel

Personnel safety shall conform to JPG 1700.1 (latest version).

1.5.5.3.2 Physical

Physical requirements shall conform to JPG 1700.1 (latest version).

1.5.5.3.3 SR and QA

SR and QA shall conform to JPG 1700.1 (latest version).

1.5.5.3.4 Environmental

Environmental health requirements shall conform to JPG 1700.1 (latest
version).

1.5.5.4 Security

The contractor is responsible for management and documentation of the
MCC/IPS IT Security baseline (DRD MSOC-JSC-0081). NASA owns the MCC/IPS
architecture and the requirements as derived from Federal, NASA and MOD
unique mission policies, and is responsible for approving any changes to
the MCC/IPS Architecture and the associated risk accompanying that
change. Where changes to the baseline introduce IT security risks, the
NASA MCC/IPS Project Manager and the MCC/IPS IT Security manager shall
be the deciding officials, including the authority to change or waive
the MCC/IPS IT security requirement through the CM process section
1.5.5.2. The NASA MCC/IPS Project Manager and the MCC/IPS IT Security
manager jointly have the responsibility for formally obtaining risk
acceptance approvals from the MOD director.

The contractor shall:

-   Provide protection/safeguarding of personnel, facilities, assets,
    equipment and classified information and materials and unclassified
    sensitive, technological and International Partner data information
    as required.

-   Supports secure flight engineering and operations of secure
    facilities and systems through the implementation and adherence with
    NASA and DoD regulations governing National Security and National
    Resource Protection.

-   Provide security engineering, maintenance and operations for systems
    protecting classified information transmitted, processed or stored
    by electronic means. These functions require the application of
    physical, communications, and information and personnel security and
    configuration management.

1.5.5.4.1 Reserved

1.5.5.4.2 Personnel

The contractor shall provide personnel with secret clearances for those
tasks requiring access to classified information. Contractor shall
comply with all NASA and JSC Security requirements.

1.5.5.4.3 Information Technology (IT) Security

The contractor shall implement a proactive Information Technology
Security (ITS) program which meets at least the minimum requirements of
the NASA ITS program as specified in the NASA Policy Directive (NPD)
2810.1 (1998) Security of Information Technology or the latest revision.
The contractor shall:

-   Follow and participate in the JSC ITS program.

-   Meet the provisions of the JPG 2810.1 (2001) Security of Information
    Technology in accordance with I14 1852.204-76 or the latest
    revision.

-   Protect sensitive unclassified information including Privacy Act
    information, proprietary data, International Traffic in Arms
    Regulation data and technology embargoed from foreign dissemination
    and International Partner data transmitted, stored or processed in
    the MCC/IPS.

-   Protect information, which requires high standards of integrity and
    availability for use within NASA.

1.5.5.4.4 Communications Security (COMSEC) and Classified Data
Computation

The contractor shall:

-   Support program requirements for classified Communications Security
    (COMSEC) and unclassified security.

-   Maintain and administer a COMSEC custodial account through the
    SECRET level, and provide encryption key management services and
    classified documentation storage; provide encryption key management
    services and store sensitive documentation for teleconferencing and
    data circuits; operate and maintain an Automated Digital Network
    (AUTODIN) Secure Telephone Unit version III (STU-III) and a STU-III
    classified voice conference bridge.

-   Provide technicians certified to perform limited cryptographic
    maintenance and operations.

-   Provide maintenance for cryptographic equipment in the MCC, TOC/SCOR
    and Sonny Carter Training Facility (SCTF).

1.5.5.4.5 Physical

The contractor shall comply with JSC 1700.1. (Latest version).

1.5.5.4.6 Reserved

**Appendix A: Acronyms:**

ACA Associate Contractor Agreements

AR Anomaly Report

ASD Avionics System Division

ASQC American Society for Quality Control

ASRS Automated Support Requirements System

ATV Automated Transfer Vehicle

AUTODIN Automated Digital Network

BCC Backup Control Center

CAD Computer Aided Dispatch

CCC Control Center Complex

CCF Consolidated Communication Facility

CCIS Consolidated Communications Interface Subsystem

CDE Consolidated Development Environment

CDS Consolidated Distribution Subsystem

CMS Configuration Management System

CO Contracting Officer

COTR Contracting Officer's Technical Representative

COD Center Operations Directorate

CoF Construction of Facilities

COFR Certificate of Flight Readiness

COMSEC Communications Security

COTS Commercial-Off-the-Shelf

CPS Consolidated Planning System

CSA Canadian Space Agency

CTRA Command, Telemetry and Recording Area

CWBS Contract Work Breakdown Structure

DAWG Data Administration Working Group

DEMOS Distributed Earth Model Orbiter Simulation

DoD Department of Defense

DOLILU Day-of-Launch Initialization-Load Update DRD

DR Discrepancy Report

DRD Data Requirement Description

DRTS Discrepancy Reporting and Tracking System

EDP Electronic Document Project

EIS External Interface Server

EOC Emergency Operations Center

ESA European Space Agency

ESC Engineering Support Center

ESD Electrostatic Discharge Control

ESTL Electronic System Test Laboratory

FCOH Flight Console Operations Handbook

FD&D Flight Design and Dynamics

FDPA Flight Dynamics Planning and Analysis

FEPS Front End Processor Subsystem

FOIG Flight Operations Integration Group

FRR Flight Readiness Review

FTE Full Time Equivalent

GC Ground Controller

GFE Government Furnished Equipment

GIDEP Government Industry Database for Electronic Parts

GP General Purpose

GSCB Ground Segment Control Board

GSDE Ground System Development Environment

GSFC Goddard Space Flight Center

GSI Government Source Inspection

GSTDN Ground Spacecraft Tracking and Data Network

HOSC Huntsville Operations Support Center

HS Health and Status

HSF Human Space Flight

HSR Houston Support Room

HTV H-II Transfer Vehicle (Japanese)

ICD Interface Control Document

IDD Internal Data Distribution

IFMP Integrated Financial Management Program

IGSS International Ground System Specifications

IMARS ISS MOD Avionics Reconfiguration System

INS Integrated Network Service

IP International Partner

IPS Integrated Planning System

IPT Integrated Product Team

ISD Information System Directorate

ISPX Information Sharing Protocol External Interface

ISS International Space Station

I&T Integration and Test

I/T Information Technology

IT Information Technology

ITF Integrated Training Facility

ITS Information Technology Security

IV&T Integrated Verification and Test

IVT Integration, Verification and Test

JOP Joint Operations Panel

JSC Johnson Space Center

KSLOC Kilo (1000)-Source Lines of Code

LAN Local Area Network

LeRC Lewis Research Center

LSOS Limited Station Operations System

MAS MCC Automation System

MCC Mission Control Center

MCC-H Mission Control Center -- Houston

MIDDS Meteorological Interactive Data Distribution System

MOD Mission Operations Directorate

MPIB MOD Production Integration Board

MPSR Multi-purpose Support Room

MPV Manual Procedure Viewer

MSFC Marshall Space Flight Center

MSOC Mission Support Operations Contract

NACAIT Network and Communication Analysis Team

NASA National Aeronautics and Space Administration

NASDA National Space Development Agency of Japan

NISN NASA Integrated Services Network

NPD NASA Policy Directive

NPG NASA Procedures and Guidelines

NPRD Network Program Requirement Document

OCA Orbital Communications Adapter

ODIN Outsourcing Desktop Initiative for NASA

ODRC Orbital Data Reduction Complex

OND Operational Need Date

ORT Operational Readiness Test

OS Operating System

OSHA Occupational Safety and Health Administration

OST Operational Support Team

PC Personal Computer

PCAG Platform Change Assessment Group

PDAC Procedure Development and Control

PIMR Process Integrity Metrics Review

POCC Payload Operations Control Center

POP Program Operating Plan

PRD Program Requirement Document

PS Platform Services

PSR Project Status Reviews

PSS Platform System Service

PWB Printed Wiring Board

QMS Quality Management System

RF Radio Frequency

RITF Receiving Inspection and Test Facility

RUPSM Resource Utilization Planning and System Model

SART Security Analysis and Response Team

SCSC Spacecraft Computer Support Center

SCTF Sonny Carter Training Facility

SFOC Space Flight Operations Contract

SOW Statement of Work

SR Service Request

SR Support Request

SR&QA Safety Reliability & Quality Assurance

SSCC Space Station Control Center

SSP Space Shuttle Program

SSPP System Safety Program Plan

SSTF Space Station Training Facility

STGT Second TDRSS Ground Terminal

STU Secure Telephone Unit

SVF Station Verification Facility

TCP Technical Control Panels

TCS Test and Checkout Subsystem

TDRSS Tracking Data Relay Satellite System

TIM Technical Interchange Meeting

TIRF Transmittal Information Request Form

TM Task Manager

TOC Test Operations Center

TS Telecommunications Service

TSS Timing Subsystem

T&O Test and Operations Board

UPN Unique Project Number

UPS Un-Interruptible Power Supply

UPS/EU User Planning System/External Interface

US United States

USA United States of America

USA United Space Alliance

VS Video Subsystem

WSP Workstation and Server Platform

ZOE Zone of Exclusion

**Appendix B: GLOSSARY**

**Acceptance Testing** - the testing of a system, subsystem, assembly or
subassembly, in an operational environment, to ensure that the
performance of the aggregate is not compromised by the integration of
the newly developed or modified asset.

**Availability** - the percentage of a scheduled service delivered to
the user. Availability is measured as: 100 ∗ (amount of scheduled
service time in a reporting period − the amount of time the scheduled
service was not provided during a reporting period) / (total amount of
scheduled time in a reporting period). .

**Certification -** the process of determining and attesting to a
required level of value, performance and readiness.

**Compatibility testing -** A group of interface tests between the
spacecraft's transponder and the ground tracking RF equipment (i.e.,
receivers, transmitter & radio metric) for verifying RF
telecommunication links.

**Delivery** -- The scheduled content, design, implementation, and
testing of one or more modifications (hardware, software, or both) to
one or more missions services systems that involve a mission services
requirement or architecture change.

**End-to-End** - used to delineate the boundaries of a system. In the
context of this contract, end-to-end means the two-way path from the
spacecraft to the ground antenna through the ground systems, the
communications systems, to the user system, such as a control center or
payload processing facility.

**End-to-End testing -** the testing, in an operational environment, to
ensure that data flows from each one end to the other end of a defined
end-to-end system and meets documented performance and data flow and
data accuracy requirements and data interface agreements.

**Expectation** - The level of performance which would be considered to
fall in the "GOOD" range for performance evaluation purposes (Effective
performance; fully responsive to contract requirements. Reportable
deficiencies, but with little identifiable effect on overall
performance.)

**Facility -** the location where various mission services, data
services, and site services are performed.

**Ground System** - consists of the infrastructure (i.e., facilities and
tools) and the service operators required to operate the infrastructure
(i.e., network monitors, facility schedulers, tape operators, system
administrators, etc.).

**Ground System Operations** - This definition contains typical
functions required to accomplish the operations of the
telecommunications and computing assets used to deliver the services in
the statement of work. These functions include but are not limited to:

-   Modification and configuration management of operations processes
    and procedures in accordance with operations and service
    requirements, as well as capabilities and performance agreements.

-   Operations of equipment and services according to operations
    agreements, procedures, and negotiated schedules.

**Independent Modification Delivery --** Modifications to Mission
Services that do not involve a requirement or architecture change.

**Lost service time** - total time that customers requested and were
granted but for which the service was not available

**Mission Operations** - This definition contains typical functions
associated with mission operations for the services in the statement of
work. Mission operations encompass those activities required to plan,
conduct, and analyze ground operations associated with providing the
services encompassed by this contract. These functions include but are
not limited to:

-   Pre-mission analysis.

-   Mission operations support including participation in the Flight
    Control Team.

-   Post-mission analysis.

**Mission readiness certification** - the process of determining and
demonstrating performance according to mission support requirements.

**Mission Reconfiguration Products** - Hardware, firmware, software, and
data products used to configure service elements for usage with
spacecraft.

**Modification** -- any change to the configuration of the facility
resulting in the update to the current capabilities and services,
expansion of existing capabilities and services or the addition or
deletion of existing capabilities and services.

**Network interface** - the point of demarcation for outbound data
(e.g., command data) between a tracking complex and the NASA Integrated
Services Network (NISN). Also the point of demarcation for inbound data
(e.g., telemetry data) between the user and the NISN.

**Operations Analysis** - This definition contains typical functions
associated with the assessment of the current performance of the ground
systems and the impacts of additional loading to those services as
listed in the statement of work. These functions include but are not
limited to:

-   End-to-end system performance monitoring, recommending appropriate
    changes to eliminate potential system bottlenecks and overloads; and
    short-term and long-term trend analysis.

-   Risk analysis and management.

-   Assessment of technical, schedule, and cost factors involved with
    the operation of systems.

-   System operability and review of operation procedures, recommending
    or effecting changes to minimize data, voice, or video outages.

**Release** -- The scheduled content, implementation, and testing of one
or more hardware and software sustaining changes or updates to one or
more missions services systems or subsystems.

**Scheduling -** This definition contains typical functions associated
with the commitment of resources. These functions include but are not
limited to:

-   Scheduling of resources needed to provide a service.

-   Providing notification to customers of service availability and
    providing resolution of any conflicts.

-   Maintain schedule and resource utilization history databases.

**Standard of Excellence -** The level of performance, which would be
considered to fall in the "EXCELLENT" range for performance evaluation
purposes (Of exceptional merit; exemplary performance in a timely,
efficient and economical manner; very minor, if any, deficiencies with
no adverse effect on overall performance.)

**Subsystem -** A collection of hardware, software and procedures, which
perform an identifiable task in support of one or more systems.

**Sustaining Engineering** - the process whereby hardware and software
capability is introduced into a system to restore the system to its
as-built capabilities and performance. It includes but is not limited to
the functions of product design, product fabrication or programming,
product specification testing and acceptance, and product integration
and test.

**Sustaining Engineering Services**- This definition contains typical
functions associated with hardware, firmware, and software sustaining
engineering for the telecommunications and computing assets used to
deliver the services in the statement of work. Sustaining engineering
encompasses those activities required to restore systems to their
as-built capabilities and performance. These functions include but are
not limited to:

-   Plan, fabricate, develop, acquire, integrate, and modify hardware,
    software, or both, based on requirements changes, equipment
    obsolescence, and operational efficiency improvements.

-   Adherence to standards, architecture, functional designs, and
    engineering processes.

-   Configuration management of the system, including change
    requirements management and as built documentation (i.e.
    architecture baseline control).

**Systems Engineering** **Services**- This definition contains typical
functions associated with the system engineering of individual ground
systems within a mission, data, or center unique service. These
functions include but are not limited to:

-   Review customer requirements and augment existing ground system
    functional requirements.

-   Propose modifications, enhancements, or both, to existing ground
    systems.

-   Develop and maintain functional designs of systems and subsystems

-   Ensure all reviews, proposals, development, enhancements, and
    designs adhere to system, operational and data security requirements
    specified by US Federal requirements and as applicable,
    international standards. This includes IT security risk analysis and
    reporting to appropriate NASA line management

**Testing Services** - This definition contains typical functions
associated with hardware and software system and subsystem testing for
the assets used to deliver the services in the statement of work. These
functions include but are not limited to:

-   Diagnostic testing.

-   Verification and acceptance testing.

-   Compatibility testing.

-   Test planning, activities leading to the development of test plans,
    procedures, resource deployment, and execution of tests.

-   Support validation testing and mission readiness testing.

**Validation testing -** the testing of a newly developed or modified
asset (system, subsystem, assembly, subassembly or lowest replaceable
element), in an operational environment, to ensure that all requirements
of the specification have been met.

**Verification testing -** the testing of a newly developed or modified
asset (system, subsystem, assembly, subassembly or lowest replaceable
element), in a non-operational environment, to ensure that all
requirements of the specification have been met.

## D. 1 PACKAGING, HANDLING, AND TRANSPORTATION (NASA 1852.211-70) (JUN 2000) 

\(a\) The Contractor shall comply with NPG 6000.1E, \"Requirements for
Packaging, Handling, and Transportation for Aeronautical and Space
Systems, Equipment, and Associated Components\", dated April 26, 1999,
as may be supplemented by the statement of work or specifications of
this contract, for all items designated as Class I, II, or III.

\(b\) The Contractor\'s packaging, handling, and transportation
procedures may be used, in whole or in part, subject to the written
approval of the Contracting Officer, provided (1) the Contractor\'s
procedures are not in conflict with any requirements of this contract,
and (2) the requirements of this contract shall take precedence in the
event of any conflict with the Contractor\'s procedures.

\(c\) The Contractor must place the requirements of this clause in all
subcontracts for items that will become components of deliverable Class
I, II, or III items.

(End of clause)

## 

## E. 1 LISTING OF CLAUSES INCORPORATED BY REFERENCE 

## NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference: 

## FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1)

> CLAUSE
>
> NUMBER DATE TITLE
>
> 52.246-5 APR 1984 INSPECTION OF SERVICES-
>
> COST REIMBURSEMENT

## NASA FEDERAL ACQUISITION REGULATION SUPPLEMENT (48 CFR CHAPTER 18)

> CLAUSE
>
> NUMBER DATE TITLE
>
> 1852.246-73 MAR 1997 HUMAN SPACE FLIGHT ITEM

##  (End of By Reference Section)

## E.2 HIGHER-LEVEL CONTRACT QUALITY REQUIREMENT (FAR 52.246-11) (FEB 1999)

The Contractor shall comply with the higher-level quality standard
selected below.

The contractor shall establish a quality program that complies with
International Organization for Standardization document American Society
for Quality Control (ASQC) ISO-9000-2000 -- Model for Quality Assurance
in Design/Development, Production, Installation, and Servicing. Third
party registration is required.

(End of clause)

**E.3 MATERIAL INSPECTION AND RECEIVING REPORT (NASA 1852.246-72) (JUN
1995) (Does not apply to data deliverables; see Clause F.5)**

\(a\) At the time of each delivery to the Government under this
contract, the Contractor shall furnish a Material Inspection and
Receiving Report (DD Form 250 series) prepared in an original copy and
sufficient other copies to accomplish the following distribution:

(1) Via mail and marked "Advanced Copy", one copy each to the
    Contracting Officer, the Contracting Officer's Technical
    Representative (if designated in the contract), and to the cognizant
    Administrative Contracting Officer, if any.

(2) Via mail, the original and 1 copy (unfolded) to the shipment address
    (delivery point) specified in Section F of this contract. Mark the
    exterior of the envelope "CONTAINS DD FORM 250". This must arrive
    prior to the shipment.

(3) With shipment in a waterproof envelope (one copy) for the consignee.

\(b\) The Contractor shall prepare the DD Form 250 in accordance with
NASA FAR Supplement 1846.672-1. The Contractor shall enclose the copies
of the DD Form 250 in the package or seal them in a waterproof envelope,
which shall be securely attached to the exterior of the package in the
most protected location.

\(c\) When more than one package is involved in a shipment, the
Contractor shall list on the DD Form 250, as additional information, the
quantity of packages and the package numbers. The Contractor shall
forward the DD Form 250 with the lowest numbered package of the shipment
and print the words \"CONTAINS DD FORM 250\" on the package.

**(End of clause)**

## E.4 INSPECTION AND ACCEPTANCE (JSC 52.246-90) (JUN 1991)

Final inspection and acceptance shall be accomplished by the Contracting
Officer or his/her duly authorized representative at NASA Lyndon B.
Johnson Space Center.

(End of clause)

## 

E.5 QUALITY ASSURANCE SURVEILLANCE PLAN (JSC 52.246-93) (JUL 1996)

A Quality Assurance Surveillance Plan will be developed and implemented
by the Contracting Officer's Technical Representative as a part of the
contract administration and monitoring activities conducted to assure
that the Government receives products and services that conform to
contract requirements. The nature and extent of quality assurance
surveillance contemplated in this plan will be based, in part, on the
specific content of the contractor's quality Plan (Section J).

(End of Clause)

## F. 1 LISTING OF CLAUSES INCORPORATED BY REFERENCE 

## NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference: 

## FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1)

> CLAUSE DATE TITLE

NUMBER

52.242-15 AUG 1989 STOP-WORK ORDER (ALT I) (APR 1984)

I.  NASA FEDERAL ACQUISITION REGULATION SUPPLEMENT (48 CFR CHAPTER 18)

> There are no NASA by reference clauses in this section.

(End of By Reference Section)

**F.2 BILLS OF LADING (NASA 1852.247-73) (JUN 2002)**

The purpose of this clause is to define when a commercial bill of lading
or a government bill of lading is to be used when shipments of
deliverable items under this contract are f.o.b. origin.

\(a\) Commercial Bills of Lading. All domestic shipments shall be made
via commercial bills of lading (CBLs). The Contractor shall prepay
domestic transportation charges. The Government shall reimburse the
Contractor for these charges if they are added to the invoice as a
separate line item supported by the paid freight receipts. If paid
receipts in support of the invoice are not obtainable, a statement as
described below must be completed, signed by an authorized company
representative, and attached to the invoice.

\"I certify that the shipments identified below have been made,
transportation charges have been paid by (company name), and paid
freight or comparable receipts are not obtainable.

Contract or Order Number: [                    ]{.underline}

Destination:[               ]{.underline} \".

\(b\) Government Bills of Lading.

\(1\) International (export) and domestic overseas shipments of items
deliverable under this contract shall be ade by Government bills of
lading (GBLs). As used in this clause, "domestic overseas" means
non-continental United States, i.e. Hawaii, Commonwealth of Puerto Rico,
and possessions of the United States.

\(2\) At least 15 days before shipment, the Contractor shall request in
writing GBLs from:  Cynthia Ratliff, Transportation Management, Attn:
Mail Code JB9, 2101 NASA Parkway, Houston, TX 77058. If time is limited,
requests may be by telephone: 281-483-3208. Requests for GBLs shall
include the following information.

\(i\) Item identification/ description.

\(ii\) Origin and destination.

\(iii\) Individual and total weights.

\(iv\) Dimensional Weight.

\(v\) Dimensions and total cubic footage.

\(vi\) Total number of pieces.

\(vii\) Total dollar value.

\(viii\) Other pertinent data.

(End of clause)

**F.3** **COMPLETION OF WORK (JSC 52.211-95) (OCT 2001)**

All work required under this contract, including submission of all
reports, shall be completed on or before September 30, 2006.

(End of clause)

**F.4** **OPTION TO EXTEND COMPLETION DATE (JSC 52.217-90) (OCT 1996)**

OPTION 1

The Government may require the contractor to continue to perform
services under this contract. The Contracting Officer may exercise this
option by issuance of a unilateral contract modification 30 days or more
before the completion date set forth in Section F. Should the option be
exercised, the resultant contract will include all terms and conditions
of the basic contract as is it exists immediately prior to the exercise
of the option, except for the following changes:

A.  B.1 entitled "Estimated Cost and Award Fee" shall be modified to
    reflect the addition of \$18,399,332 to the estimated cost and
    \$1,701,938 to the maximum award fee.

B.  F.3, entitled "Completion of Work" shall be modified to extend the
    ending date of the contract to December 31, 2004.

C.  H.6 entitled "Level-of-Effort (Cost)," shall be modified by
    increasing the total direct labor man-hours (including overtime) by
    6,978.

OPTION 2

The Government may require the contractor to continue to perform
services under this contract. The Contracting Officer may exercise this
option by issuance of a unilateral contract modification 30 days or more
before the completion date set forth in Section F. Should the option be
exercised, the resultant contract will include all terms and conditions
of the basic contract as is it exists immediately prior to the exercise
of the option, except for the following changes:

A.  B.1 entitled "Estimated Cost and Award Fee" shall be modified to
    reflect the addition of \$17,960,687 to the estimated cost and
    \$1,616,462 to the maximum award fee.

B.  F.3, entitled "Completion of Work" shall be modified to extend the
    ending date of the contract to March 31, 2005.

C.  H.6 entitled "Level-of-Effort (Cost)," shall be modified by
    increasing the total direct labor man-hours (including overtime) by
    6,871.

OPTION 3

The Government may require the contractor to continue to perform
services under this contract. The Contracting Officer may exercise this
option by issuance of a unilateral contract modification 30 days or more
before the completion date set forth in Section F. Should the option be
exercised, the resultant contract will include all terms and conditions
of the basic contract as is it exists immediately prior to the exercise
of the option, except for the following changes:

A.  B.1 entitled "Estimated Cost and Award Fee" shall be modified to
    reflect the addition of \$163,800,517 to the estimated cost and
    \$14,742,047 to the maximum award fee.

B.  F.3, entitled "Completion of Work" shall be modified to extend the
    ending date of the contract to September 30, 2006.

C.  H.6 entitled "Level-of-Effort (Cost)," shall be modified by
    increasing the total direct labor man-hours (including overtime) by
    50,923.

D.  H.4 entitled "Small Business Subcontracting Goals" shall be deleted
    in its entirety and replaced with the following:

> **"H.4 SMALL BUSINESS SUBCONTRACTING GOALS (JSC 52.219-90) (JAN
> 2003)**
>
> For purposes of this clause, the terms, "HUBZone Small Business
> Concern," "Small Disadvantaged Business Concern," "Service-Disabled,
> Veteran-Owned Small Business Concern", "Veteran-Owned Small Business
> Concern," "Women-Owned Small Business Concern," and "Historically
> Black College or University (HBCU)" are defined in paragraph 2.101 of
> the Federal Acquisition Regulation.
>
> The total small business goal, expressed as a percent of total
> contract value, is 30.5 percent, including options. The small business
> percentage goal, (30.5 percent), includes the following goals
> expressed as a percent of total contract value:

Small Disadvantaged Business Concerns 10 percent

Woman-Owned Small Business Concerns 15 percent

> HUBZone Small Business Concerns (1/1/04 - 9/30/04) 1 percent

HUBZone Small Business Concerns (10/1/04 - 9/30/06) 3 percent

> Veteran-Owned Small Business Concerns 1 percent
>
> Service Disabled Veteran-Owned Small Business Concerns 1 percent

Historically Black Colleges or Universities/Minority Institutions 1
percent

> E. E.2 entitled "Higher-Level Contract Quality Requirement" is deleted
> in its entirety and replaced with the following:

## "E.2 HIGHER-LEVEL CONTRACT QUALITY REQUIREMENT (FAR 52.246-11) (FEB 1999)

The Contractor shall comply with the higher-level quality standard
selected below.

> The contractor shall establish a quality program that complies with
> International Organization for Standardization document American
> Society for Quality Control (ASQC) ISO-9000-2000 -- Model for Quality
> Assurance in Design/Development, Production, Installation, and
> Servicing. Third party registration is required."
>
> F. The first two paragraphs of Section 1.3.2.4, Quality Assurance, of
> the Statement Of Work contained in Section C, is deleted in its
> entirety and replaced with the following:

"1.3.2.4 Quality Assurance

> The contractor shall establish a quality program that complies with
> International Organization for Standardization document American
> Society for Quality Control (ASQC) ISO-9000-2000 -- Model for Quality
> Assurance in Design/Development, Production, Installation, and
> Servicing.
>
> Third-party certification / registration is required."

**F.5** **SHIPPING INSTRUCTIONS (JSC 52.247-94) (APR 1997)**

All documentation shall be shipped to the addresses cited in F.5.
Shipment of all other items shall be as follows:

Parcel Post Shipments and Freight Shipments

Ship to: Transportation Officer,

Building 421

NASA Johnson Space Center

2101 NASA Parkway

Houston, TX 77058-3696

Mark for: Accountable Property Officer

Mark with: Purchase Request No. 4200010497

Contract Number: NAS 9-03056

For reissue to: (Name) James Lowery

(Mail Code) DA30

(Bldg.) 17

(Rm.) 222D

(End of clause)

**F.6** **FLIGHT ITEM** **(JSC 52.247-95) (SEP 1989)**

Block 16 of each Department of Defense Form 250 prepared for hardware or
equipment to be shipped under this contract must be annotated as follows
in 1/4-inch letters or larger by hand printing or rubber stamp:

'THIS IS A FLIGHT ITEM: OR "THIS IS MISSION ESSENTIAL GROUND SUPPORT
EQUIPMENT," as applicable.

(End of clause)

## G. 1 LISTING OF CLAUSES INCORPORATED BY REFERENCE 

## NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference: 

## FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1)

> CLAUSE
>
> NUMBER DATE TITLE
>
> There are no FAR by reference clauses in this section.

## NASA FEDERAL ACQUISITION REGULATION SUPPLEMENT (48 CFR CHAPTER 18)

> CLAUSE

## NUMBER DATE TITLE

1852.227-70 MAY 2002 NEW TECHNOLOGY

1852.227-86 DEC 1987 COMMERCIAL COMPUTER

SOFTWARE-LICENSING

1852.242-73 JUL 2000 NASA CONTRACTOR FINANCIAL

MANAGEMENT REPORTING

1852.245-73 AUG 2001 FINANCIAL REPORTING OF NASA

PROPERTY IN THE CUSTODY OF

> CONTRACTORS (In Paragraph b, the NASA office for receipt of NF1018 is:
> The annual NASA Form 1018 shall be filed electronically through the
> NASA Form 1018 Electronic Submission System (NESS). The quarterly
> submission shall be filed electronically to
> <NASAContractorProperty@nasa.gov> and the JSC Delegated Property
> Administrator.)

##  (End of By Reference Section)

G.2 AWARD FEE FOR SERVICE CONTRACTS (NASA 1852.216-76) (JUNE 2000)

\(a\) The contractor can earn award fee from a minimum of zero dollars
to the maximum stated in NASA FAR Supplement clause 1852.216-85,
\"Estimated Cost and Award Fee\" in this contract.

\(b\) Beginning 9 months after the effective date of this contract, the
Government shall evaluate the Contractor\'s performance every 6 or 9
months (see Attachment J-2) determine the amount of award fee earned by
the contractor during the period. The Contractor may submit a
self-evaluation of performance for each evaluation period under
consideration. These self-evaluations will be considered by the
Government in its evaluation. The Government\'s Fee Determination
Official (FDO) will determine the award fee amounts based on the
Contractor\'s performance in accordance with Attachment J-2. The plan
may be revised unilaterally by the Government prior to the beginning of
any rating period to redirect emphasis.

\(c\) The Government will advise the Contractor in writing of the
evaluation results. The Accounts Payable Group will make payment based
on the unilateral modification.

\(d\) After 85 percent of the potential award fee has been paid, the
Contracting Officer may direct the withholding of further payment of
award fee until a reserve is set aside in an amount that the Contracting
Officer considers necessary to protect the Government\'s interest. This
reserve shall not exceed 15 percent of the total potential award fee.

\(e\) The amount of award fee, which can be awarded in each evaluation
period, is limited to the amounts set forth at Attachment J-2. Award fee
which is not earned in an evaluation period cannot be reallocated to
future evaluation periods.

\(f\) (1)Provisional award fee payments will be made under this contract
pending the determination of the amount of fee earned for an evaluation
period. If applicable, provisional award fee payments will be made to
the Contractor on a monthly basis. The total amount of award fee
available in an evaluation period that will be provisionally paid is the
lesser of 50% or the prior period\'s evaluation score.

\(2\) Provisional award fee payments will be superseded by the final
award fee evaluation for that period. If provisional payments exceed the
final evaluation score, the Contractor will either credit the next
payment voucher for the amount of such overpayment or refund the
difference to the Government, as directed by the Contracting Officer.

\(3\) If the Contracting Officer determines that the Contractor will not
achieve a level of performance commensurate with the provisional rate,
payment of provisional award fee will be discontinued or reduced in such
amounts as the Contracting Officer deems appropriate. The Contracting
Officer will notify the Contractor in writing if it is determined that
such discontinuance or reduction is appropriate.

\(4\) Provisional award fee payments will be made prior to the first
award fee determination by the Government.

\(g\) Award fee determinations are unilateral decisions made solely at
the discretion of the Government.

(End of clause)

## G. 3 SUBMISSION OF VOUCHERS FOR PAYMENT (NASA 1852.216‑87) (MAR 1998)

     (a) The designated billing office for cost vouchers for purposes of
the Prompt Payment clause of this contract is indicated below.  Public
vouchers for payment of costs shall include a reference to the number of
this contract.\
     (b) (1) If the contractor is authorized to submit interim cost
vouchers directly to the NASA paying office, the original voucher should
be submitted to:

NASA Lyndon B. Johnson Space Center

Attn: Mail Code LF231

2101 NASA Parkway

> Houston, TX 77058

            (2)  For any period that the Defense Contract Audit Agency
has authorized the Contractor to submit interim cost vouchers directly
to the Government paying office, interim vouchers are not required to be
sent to the Auditor, and are considered to be provisionally approved for
payment, subject to final audit.\
            (3) Copies of vouchers should be submitted as directed by
the Contracting Officer.\
     (c) If the contractor is not authorized to submit interim cost
vouchers directly to the paying office as described in paragraph (b),
the contractor shall prepare and submit vouchers as follows:\
            (1) One original Standard Form (SF) 1034, SF 1035, or
equivalent Contractor\'s attachment to:

#### Defense Contract Audit Agency 

Lockheed Martin Mt. Laurel Resident Office

Laurel Corporate Center

> Mt. Laurel, NJ 08054-1512

            (2) Five copies of SF 1034, SF 1035A, or equivalent
Contractor\'s attachment to the following offices by insertion in the
memorandum block of their names and addresses:\
                  (i)   Copy 1 NASA Contracting Officer\
                  (ii)  Copy 2 Auditor\
                  (iii) Copy 3 Contractor\
                  (iv) Copy 4 Contract administration office; and\
                  (v)  Copy 5 Project management office.\
            (3) The Contracting Officer may designate other recipients
as required.\
     (d) Public vouchers for payment of fee shall be prepared similarly
to the procedures in paragraphs (b) or (c) of this clause, whichever is
applicable, and be forwarded to:

> NASA Lyndon B. Johnson Space Center
>
> Attn: BH/Contract Specialist
>
> 2101 NASA Parkway
>
> Houston, TX 77058

     This is the designated billing office for fee vouchers for purposes
of the Prompt Payment clause of this contract.

     (e) In the event that amounts are withheld from payment in
accordance with provisions of this contract, a separate voucher for the
amount withheld will be required before payment for that amount may be
made.

(End of clause)

## G.4 DESIGNATION OF NEW TECHNOLOGY REPRESENTATIVE AND PATENT REPRESENTATIVE (NASA 1852.227‑72) (JUL 1997)

\(a\) For purposes of administration of the clause of this contract
entitled \"New Technology\" or \"Patent Rights ‑‑ Retention by the
Contractor (Short Form)\", whichever is included, the following named
representatives are hereby designated by the Contracting Officer to
administer such clause:

HA/Technology Transfer & Commercialization Office

NASA Lyndon B. Johnson Space Center

Houston, TX 77058

\(b\) Reports of reportable items, and disclosure of subject inventions,
interim reports, final reports, utilization reports, and other reports
required by the clause, as well as any correspondence with respect to
such matters, should be directed to the New Technology Representative
unless transmitted in response to correspondence or request from the
Patent Representative. Inquiries or requests regarding disposition of
rights, election of rights, or related matters should be directed to the
Patent Representative. This clause shall be included in any subcontract
hereunder requiring a \"New Technology\" clause or \"Patent
Rights‑‑Retention by the Contractor (Short Form)\" clause, unless
otherwise authorized or directed by the Contracting Officer. The
respective responsibilities and authorities of the above‑named
representatives are set forth in 1827.305‑370 of the NASA FAR
Supplement.

(End of clause)

**G.5 TECHNICAL DIRECTION (NASA 1852.242-70) (SEPT 1993)**

\(a\) Performance of the work under this contract is subject to the
written technical direction of the Contracting Officer Technical
Representative (COTR), who shall be specifically appointed by the
Contracting Officer in writing in accordance with NASA FAR Supplement
1842.270. \"Technical direction\" means a directive to the Contractor
that approves approaches, solutions, designs, or refinements; fills in
details or otherwise completes the general description of work or
documentation items; shifts emphasis among work areas or tasks; or
furnishes similar instruction to the Contractor. Technical direction
includes requiring studies and pursuit of certain lines of inquiry
regarding matters within the general tasks and requirements in Section C
of this contract.

\(b\) The COTR does not have the authority to, and shall not, issue any
instruction purporting to be technical direction that\--

\(1\) Constitutes an assignment of additional work outside the statement
of work;

\(2\) Constitutes a change as defined in the changes clause;

\(3\) Constitutes a basis for any increase or decrease in the total
estimated contract cost, the fixed fee (if

any), or the time required for contract performance.

(4) Changes any of the expressed terms, conditions, or specifications of
the contract; or

(5) Interferes with the contractor\'s rights to perform the terms and
conditions of the contract.

\(c\) All technical direction shall be issued in writing by the COTR.

\(d\) The Contractor shall proceed promptly with the performance of
technical direction duly issued by the COTR in the manner prescribed by
this clause and within the COTR\'s authority. If, in the Contractor\'s
opinion, any instruction or direction by the COTR falls within any of
the categories defined in paragraph (b) of this clause, the Contractor
shall not proceed but shall notify the Contracting Officer in writing
within 5 working days after receiving it and shall request the
Contracting Officer to take action as described in this clause. Upon
receiving this notification, the Contracting Officer shall either issue
an appropriate contract modification within a reasonable time or advise
the Contractor in writing within 30 days that the instruction or
direction is\--

\(1\) Rescinded in its entirety; or

\(2\) Within the requirements of the contract and does not constitute a
change under the changes clause of the contract, and that the Contractor
should proceed promptly with its performance.

\(e\) A failure of the contractor and contracting officer to agree that
the instruction or direction is both within the requirements of the
contract and does not constitute a change under the changes clause, or a
failure to agree upon the contract action to be taken with respect to
the instruction or direction, shall be subject to the Disputes clause of
this contract.

(f) Any action(s) taken by the contractor in response to any direction
    given by any person other than the Contracting Officer or the COTR
    shall be at the Contractor\'s risk.

(End of clause)

**G.6 LIST OF GOVERNMENT-FURNISHED PROPERTY (NASA 1852.245-76) (OCT
1988)**

For performance of work under this contract, the Government will make
available Government property in Attachment J-6 of this contract on a
no-charge-for-use basis. The Contractor shall use this property in the
performance of this contract at NASA Lyndon B. Johnson Space Center.
Under the FAR 52.245 Government property clause of this contract, the
Contractor is accountable for the identified property.

(End of clause)

**G.7 SECURITY/BADGING REQUIREMENTS FOR FOREIGN NATIONAL VISITORS AND
EMPLOYEES/REPRESENTATIVES OF FOREIGN CONTRACTORS (JSC 52.204-91) (MAR
2002)**

\(a\) An employee of a domestic Johnson Space Center (JSC) contractor or
its subcontractor who is not a U.S. citizen (foreign national) may not
be admitted to the JSC site for purposes of performing work without
special arrangements. In addition, all employees or representatives of a
foreign JSC contractor/subcontractor may not be admitted to the JSC site
without special arrangements. For employees as described above, advance
notice must be given to the Security Office of the host installation at
least three weeks prior to the scheduled need for access to the site so
that instructions on obtaining access may be provided.

\(b\) All visit/badge requests for persons described in (a) above must
be entered in the NASA Request for Request (RFR) and Foreign National
Management System (NFNMS) for acceptance, review, concurrence, and
approval purposes. When an authorized company official requests a JSC or
WSTF badge for site access, he/she is certifying that steps have been
taken to ensure that its contractor or subcontractor employees,
visitors, or representatives will not be given access to
export-controlled or classified information for which they are not
authorized. These individuals shall serve as the contractor's
representative(s) in certifying that all visit/badge request forms are
processed in accordance with JSC and WSTF security and export control
procedures. No foreign national, representative, or resident alien
contractor/subcontractor employee shall be granted access into JSC or
WSTF until a completed RFR has been approved and processed through the
NFNMS. Unescorted access will not be granted unless a favorable National
Agency Check (NAC) has been completed by the JSC Security Office.

\(c\) The contractor agrees that it will not employ for the performance
of work onsite at JSC or WSTF any individuals who are not legally
authorized to work in the United States. If the JSC or WSTF Industrial
Security Specialist or the contracting officer has reason to believe
that any employee of the contractor may not be legally authorized to
work in the United States and/or on the contract, the contractor may be
required to furnish copies of Form I-9 (Employment Eligibility
Verification), U.S. Department of Labor Application for Alien Employment
Certification, and any other type of employment authorization document.

The contractor agrees to provide the information requested by JSC or
WSTF Security Office in order to comply with NASA policy directives and
guidelines related to foreign visits to NASA facilities so that (1) the
visitor/employee/ representative may be allowed access to JSC or other
NASA centers for performance of this contract, (2) required
investigations can be conducted, and (3) required annual or revalidation
reports can be submitted to NASA Headquarters. All requested information
must be submitted in a timely manner in accordance with instructions
provided by JSC or any other center to be visited.

(End of clause)

**G.8 UNDERSTANDING WITH RESPECT TO COST VARIATIONS (JSC 52.232-93) (MAR
1989)**

The estimated cost of this contract is based on cost estimates for a
number of cost elements (e.g., direct labor, overhead, materials,
travel). One or more of these estimates was made by the Government and
provided to the contractor in the solicitation leading to this contract.
The parties recognize that the contractor\'s obligation to perform tasks
within the scope of the Statement of Work could result in actual
contractor expenditures which are greater or less than the Government\'s
estimates provided to the contractor for the related cost element.
Should such be the case, the parties agree that there will be no
adjustment to the fee provided for in this contract, nor to any other
terms and conditions hereof, except the contract estimated cost, should
that become necessary. Any such adjustment in estimated cost will be
subject to the terms of the \"Limitation of Cost\" or \"Limitation of
Funds\" clause hereof, whichever is applicable.

(End of clause)

**G.9 USE OF JSC CALIBRATION LABORATORY** **(JSC 52.204-92) (OCT 1997)**

The contractor shall utilize the services of the JSC Calibration
Laboratory to the maximum extent practicable for calibration of all
instruments (Government property or contractor property) utilized under
this contract, the total cost for maintenance of which would otherwise
be a direct charge to the Government. The procedures for obtaining
calibration of instruments are described in JSC Procedures and
Guidelines 5151.2 -- \"JSC Support Contractor Procedures and
Guidelines.\"

(End of clause)

**G.10 IDENTIFICATION OF EMPLOYEES (JSC 52.242-92) (MAR 2002)**

At all times while on Government property, the contractor,
subcontractors, their employees, and agents shall wear badges which will
be issued by the NASA Badging & Visitor Control Office, located in
Building 110 at the Johnson Space Center (JSC),or at the Main Gate at
the White Sands Test Facility (WSTF). JSC employee badges will be issued
only between the hours of 7:30 a.m. to 4 p.m., Monday through Thursday,
and 7:30 am to 12:00 pm on Friday. JSC visitor badges will be issued
between the hours of 6 a.m. to 10 p.m., 7 days a week. WSTF employee
badges will be issued only between the hours of 8 a.m. to 2 p.m., Monday
through Friday. WSTF visitor badges will be issued on a 7-day-a-week,
24-hour-a-day basis. Resident aliens and foreign
nationals/representatives shall be issued green foreign national badges.

Each individual who wears a badge shall be required to declare
citizenship and personally sign for the badge. The contractor shall be
held accountable for issued badges and all other related items and must
assure that they are returned to the NASA Badging & Visitor Control
Offices upon completion of work under the contract in accordance with
Security Management Directive (SMD) 500-15, \"Security Termination
Procedures.\" Failure to comply with the NASA contractor termination
procedures upon completion of the work (e.g., return of badges, decals,
keys, CAA cards, clearance terminations, JSC Public Key Infrastructure
(PKI)/special program deletions, etc.) may result in final payment being
delayed.

(End of clause)

**G.11 REPAIR OF GOVERNMENT PROPERTY (JSC 52.245-91) (JUN 1986)**

When removal of Government-owned property from its place of use for
repair is necessary, the Contractor must prepare a JSC Form 1318 prior
to removing the equipment. The form and instructions regarding its use
are available from the Property and Equipment Branch, Building 419, Room
162, phone number 281-483-6524. The repaired Government property is to
be returned to the location from which it was removed unless otherwise
directed by the Government.

(End of clause)

**G.12 INSTALLATION-ACCOUNTABLE GOVERNMENT PROPERTY** **(NASA
1852.245-71) (JUNE 1998) (JSC Version APR 2003)**

\(a\) The Government property described in the clause at 1852.245-77,
List of Installation-Accountable Property and Services, shall be made
available to the Contractor on a no-charge basis for use in performance
of this contract. This property shall be utilized only within the
physical confines of the NASA installation that provided the property.
Under this clause, the Government retains accountability for, and title
to, the property, and the Contractor assumes the following user
responsibilities:

# Property Custodian Responsibilities: Reference NPG 4200.2

**Chapter 2: Responsibilities**

Section 2.3. Property Custodians

Section 2.4 Full Time Property Custodians

Paragraphs 2.4.1 and 2.4.2 

**Chapter 4: Operational Procedures**

Section 4.2 Identification of Equipment

Paragraphs 4.2.8, 4.2.9, 4.2.10,

Section 4.3. Standard NEMS Reports for Property Custodians.

Paragraphs 4.3.1 through 4.3.4.5

Section 4.4. Inventory Procedures.

Paragraphs 4.4.1 through 4.4.5

**Chapter 5. (Entire Content)**

**User Responsibilities: Reference Document (NPG 4200.2)**

**Chapter 2.**

2.7. Responsibility of the Individual. The contractor shall ensure that
each of its employees are responsible for Government property as
follows: An employee has a duty to protect and conserve Government
property and shall not use such property, or allow its use, for other
than authorized purposes. Additional responsibilities include the
following:

2.7.1. Reporting any missing or un-tagged (meeting the criteria for
control) equipment, transfer, location change, or user change of
equipment to the property custodian immediately.

2.7.2. Notifying the property custodian, supervisor, and the Center
security officer immediately if theft of Government property is
suspected.

2.7.3. Ensuring that equipment is used only in pursuit of approved NASA
programs and projects.

2.7.4. Notifying the property custodian of equipment not actively being
used for determination of proper disposition.

2.7.5. Ensuring that equipment is returned through the property
custodian when no longer needed. Under no circumstances will an employee
throw away Government equipment.

2.7.6. Assigned users retain all responsibilities including notifying
property custodians of all activity associated with the user's assigned
equipment.

2.8. The contractor must ensure that all on-site contractor employees
notify the contracting officer, property custodian, and SEMO upon
termination of employment.

**Chapter 4.**

4.2.11. The user will assist the custodian in completing NF 1618 and
sign in the designated block.

The contractor shall establish and adhere to a system of written
procedures for compliance with these user responsibilities.

(b)(1) The official accountable record keeping, physical inventory,
financial control, and reporting of the property subject to this clause
shall be retained by the Government and accomplished by the installation
Supply and Equipment Management Officer (SEMO) and Financial Management
Officer. Center Administrative requirements are spelled out in JPG
5151.2, JSC Support Contractor Procedures & Guidelines. If this contract
provides for the contractor to acquire property, title to which will
vest in the Government, the following additional procedures apply:

\(i\) The contractor\'s purchase order shall require the vendor to
deliver the property to the installation central receiving area.

\(ii\) The contractor shall furnish a copy of each purchase order, prior
to delivery by the vendor, to the installation central receiving area.

\(iii\) The contractor shall establish a record of the property as
required by FAR 45.5 and 1845.5 and furnish to the Industrial Property
Officer a DD Form 1149 Requisition and Invoice/Shipping Document (or
installation equivalent) to transfer accountability to the Government
within 5 working days after receipt of the property by the contractor.
The contractor is accountable for all contractor-acquired property until
the property is transferred to the Government\'s accountability.

\(iv\) Contractor use of Government property at an off-site location and
off-site subcontractor use require advance approval of the contracting
officer and notification of the SEMO. The contractor shall assume
accountability and financial reporting responsibility for such property.
The contractor shall establish records and property control procedures
and maintain the property in accordance with the requirements of FAR
Part 45.5 until its return to the installation.

\(2\) After transfer of accountability to the Government, the contractor
shall continue to maintain such internal records as are necessary to
execute the user responsibilities identified in paragraph (a) and
document the acquisition, billing, and disposition of the property.
These records and supporting documentation shall be made available, upon
request, to the SEMO and any other authorized representatives of the
contracting officer.

(End of Clause)

**G.13 LIST OF INSTALLATION-ACCOUNTABLE PROPERTY AND SERVICES (NASA
1852.245-77) (JUL 1997) (JSC Version APR 2003)**

In accordance with the clause 1852.245-71, Installation - Accountable
Government Property the Contractor is authorized use of the types of
property and services listed below, to the extent they are available, in
the performance of this contract within the physical borders of the
installation which may include buildings and space owned or directly
leased by NASA in close proximity to the installation, if so designated
by the Contracting Officer.

\(a\) Office space, work area space, and utilities. Government
telephones are available for official purposes only; pay telephones are
available for contractor employees for unofficial calls.

\(b\) General - and special-purpose equipment, including office
furniture.

\(1\) Equipment to be made available is listed in Attachment J-7. The
Government retains accountability for this property under the clause at
1852.245-71, Installation-Accountable Government Property, regardless of
its authorized location.

\(2\) If the contractor acquires property, title to which vests in the
Government pursuant to other provisions of this contract, this property
also shall become accountable to the Government upon its entry into
Government records as required by the clause at 1852.245-71,
Installation-Accountable Government Property.

\(3\) The Contractor shall not bring to the installation for use under
this contract any property owned or leased by the Contractor, or other
property that the Contractor is accountable for under any other
Government contract, without the Contracting Officer's prior written
approval.

\(c\) Publications and blank forms stocked by the installation.

\(d\) Safety and fire protection for Contractor personnel and
facilities.

\(e\) Installation service facilities:

1\. [Audiovisual]{.underline}: Presentation services, sound services,
Release Print Film Library, Film Repository, and loan of audiovisual
equipment.

2\. [Automatic Data Processing (ADP) Services (onsite
only)]{.underline}: Generally, this includes access to large
general-purpose computer systems, workstations, and the accessing media;
i.e., terminals, printers, data communications, and consultation and
training in the use of said systems. Unless otherwise specified in the
contract, this does not include providing computer systems or ADP
services for the Contractor business management, accounting, and
administrative functions.

3\. [Transportation]{.underline}: Shuttle bus service for Contractor
employees within the parameters provided for Government employees.

4\. [Disposal Services]{.underline}: Disposal services for excess onsite
and offsite Contractor-held/Government-owned property.

5\. [Fabrication Services]{.underline}: Fabrication services such as
machining, sheet metal and welding, electronics, metal finishing, model
and plastics, and precision cleaning.

6\. [Photography, Processing, and Closed-Circuit
Television]{.underline}: For technical and scientific photography,
photographic processing, photographic sciences, and closed-circuit
television.

7\. [Pickup and Delivery of Official Mail]{.underline}: Within the
Center and to and from the Albert Thomas Post Office, provided the mail
is properly sealed and stamped. Such mail will be picked up or dropped
from only one point as designated by JSC or, if preferred, JSC will
provide a box in the central mailroom for the Contractor to pick up and
deposit its mail.

\(g\) Medical treatment of a first-aid nature for Contractor personnel
injuries or illnesses sustained during on-site duty.

\(h\) Cafeteria privileges for Contractor employees during normal
operating hours.

\(i\) Building maintenance for facilities occupied by Contractor
personnel.

\(j\) Moving and hauling for office moves, movement of large equipment,
and delivery of supplies. Moving services shall be provided on-site, as
approved by the Contracting Officer.

\(k\) The user responsibilities of the Contractor are defined in
paragraph (a) of the clause at 1852.245-71, Installation-Accountable
Government Property.

(End of Clause)

## H. 1 LISTING OF CLAUSES INCORPORATED BY REFERENCE 

## NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference: 

## FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1)

> CLAUSE
>
> NUMBER DATE TITLE
>
> There are no FAR by reference clauses in this section.

## NASA FEDERAL ACQUISITION REGULATION SUPPLEMENT (48 CFR CHAPTER 18)

> CLAUSE

## NUMBER DATE TITLE

> 1852.204-74 MAY 2002 CENTRAL CONTRACTOR REGISTRATION
>
> 1852.208-81 OCT 2001 RESTRICTIONS ON PRINTING AND DUPLICATING
>
> 1852.216-80 OCT 1996 TASK ORDERING PROCEDURE
>
> (Only applies to Section 1.5.4 of the SOW)
>
> 1852.223-70 APR 2002 SAFETY AND HEALTH
>
> 1852.223-75 FEB 2002 MAJOR BREACH OF SAFETY OR SECURITY
>
> 1852.223-76 JUL 2003 FEDERAL AUTOMOTIVE TOOL REPORTING
>
> 1852.225-70 FEB 2000 EXPORT LICENSES (ALT I) (FEB 2000)
>
> 1852.228-72 SEP 1993 CROSS WAIVER OF LIABILITY FOR SPACE
>
> SHUTTLE SERVICES
>
> 1852.228-76 DEC 1994 CROSS WAIVER OF LIABILITY FOR SPACE
>
> STATION ACTIVITIES
>
> 1852.242-72 AUG 1992 OBSERVANCE OF LEGAL HOLIDAYS (ALT II) (SEP 1989)
>
> 1852.246-70 MAR 1997 MISSION CRITICAL SPACE SYSTEMS PERSONNEL
> RELIABILITY PROGRAM

(End of By Reference Section)

**H.2 KEY PERSONNEL AND FACILITIES (NASA 1852.235-71) (MAR 1989)**

\(a\) The personnel and/or facilities listed below (or specified in the
contract Schedule) are considered essential to the work being performed
under this contract. Before removing, replacing, or diverting any of the
listed or specified personnel or facilities, the Contractor shall (1)
notify the Contracting Officer reasonably in advance and (2) submit
justification (including proposed substitutions) in sufficient detail to
permit evaluation of the impact on this contract.

\(b\) The Contractor shall make no diversion without the Contracting
Officer\'s written consent; [provided]{.underline}, that the Contracting
Officer may ratify in writing the proposed change, and that ratification
shall constitute the Contracting Officer\'s consent required by this
clause.

\(c\) The list of personnel and/or facilities (shown below or as
specified in the contract Schedule) may, with the consent of the
contracting parties, be amended from time to time during the course of
the contract to add or delete personnel and/or facilities.

(End of clause)

**H.3 REPRESENTATION, CERTIFICATION, AND OTHER STATEMENTS (JSC
52.209-90) (SEP 1988)**

This contract incorporates Section K, Representations, Certifications,
and Other Statements of Offerors, as set forth in the contractor\'s
proposal 6079A-03D dated July 21, 2003, by reference, with the same
force and effect as if it were given in full text.

## (End of clause)

**H.4 SMALL BUSINESS SUBCONTRACTING GOALS (JSC 52.219-90) (JAN 2003)**

For purposes of this clause, the terms, "HUBZone Small Business
Concern," "Small Disadvantaged Business Concern," "Service-Disabled,
Veteran-Owned Small Business Concern", "Veteran-Owned Small Business
Concern," "Women-Owned Small Business Concern," and "Historically Black
College or University (HBCU)" are defined in paragraph 2.101 of the
Federal Acquisition Regulation.

The total small business goal, expressed as a percent of total contract
value, is 30.5 percent, including options. The small business percentage
goal, (30.5 percent), includes the following goals expressed as a
percent of total contract value:

Small Disadvantaged Business Concerns 10 percent

Woman-Owned Small Business Concerns 15 percent

> HUBZone Small Business Concerns (1/1/04 -- 9/30/04) 1 percent
>
> HUBZone Small Business Concerns (10/1/04 -- 9/30/06) 3 percent
>
> Veteran-Owned Small Business Concerns 1 percent
>
> Service Disabled Veteran-Owned Small Business Concerns 1 percent

Historically Black Colleges or Universities/Minority Institutions 1
percent

## (End of clause)

**H.5 (LIMITED) RELEASE OF CONTRACTOR CONFIDENTIAL BUSINESS INFORMATION
(CBI) (JSC 52.227-91) (MAY 2002)**

\(a\) NASA may find it necessary to release information submitted by the
Contractor pursuant to the provisions of this contract, to individuals
not employed by NASA. Business information that would ordinarily be
entitled to confidential treatment may be included in the information
released to these individuals. Accordingly, by signature on this
contract, the Contractor hereby consents to a limited release of its
confidential business information (CBI).

\(b\) Possible circumstances where the Agency may release the
Contractor\'s CBI include the following:

\(1\) To other Agency contractors and subcontractors, and their
employees tasked with assisting the Agency in handling and processing
information and documents in the administration of Agency contracts,
such as providing post award audit support and specialized technical
support to NASA;

\(2\) To NASA contractors and subcontractors, and their employees
engaged in information systems analysis, development, operation, and
maintenance, including performing data processing and management
functions for the Agency.

\(c\) NASA recognizes its obligation to protect the contractor from
competitive harm that could result from the release of such information
to a competitor. Except where otherwise provided by law, NASA will
permit the limited release of CBI under subparagraphs (1) or (2) only
pursuant to non-disclosure agreements signed by the assisting contractor
or subcontractor, and their individual employees who may require access
to the CBI to perform the assisting contract.

\(d\) NASA's responsibilities under the Freedom of Information Act are
not affected by this clause.

\(e\) The Contractor agrees to include this clause, including this
paragraph (e), in all subcontracts at all levels awarded pursuant to
this contract that require the furnishing of confidential business
information by the subcontractor.

(End of clause)

**H.6 LEVEL-OF-EFFORT (COST) (applies only to Section 1.5.4 of the
SOW)**

\(a\) During the term of the contract, the Contractor is obligated to
provide not less than 95 percent nor more than 105 percent of 75,015
total direct labor hours in performance of the Statement of Work.

\(b\) "Direct labor hours" are those productive hours expended by
Contractor personnel performing work under this contract that are
charged as direct labor under the Contractor's established accounting
policy and procedures. The term does not include sick leave, vacation
leave, holiday leave, military leave, or any type of administrative
leave, but does include direct labor provided under level-of-effort
subcontracts.

\(c\) Once the maximum number of direct labor hours is reached or the
contract term has ended, the Contractor's obligations under the contract
are fulfilled, even though the specified work may not have been
completed. The Contractor is not authorized to exceed the maximum number
of direct labor hours specified in paragraph (a) of this clause. Any
estimated cost and fee adjustments for any additional direct labor hours
shall be based solely on the quantity of additional hours being added to
the maximum number of direct labor hours specified in this clause.

\(d\) The fee, if any, is based upon the furnishing of at least the
specified minimum number of direct labor hours, including subcontractor
hours. If the Contractor provides less than the specified number of
hours prior to expiration of the contract term, and the Government has
not invoked its rights under the Termination clause of this contract to
adjust the contract for such reduced effort, the Contracting Officer may
unilaterally make an equitable downward adjustment to the contract fee.
The downward adjustment in fee will be based on the difference between
the minimum direct labor hours specified under this clause and the
amount of direct labor hours provided by the Contractor. Prior to making
such an adjustment, the Contracting Officer will request the Contractor
provide a written discussion of any extenuating circumstances (e.g.,
productivity improvements or reductions in contract scope) that
contributed to the underrun. Any information provided by the Contractor
will be considered by the Contracting Officer in determining the amount
of downward adjustment in fee.

(End of clause)

**H.7 SPECIAL PROVISION FOR CONTRACT CHANGES**

The parties agree that, notwithstanding the provisions of the "Changes"
clause and the "Government Property" clause, no change made pursuant to
the "Changes" clause shall give rise to an equitable adjustment in the
estimated cost or fee or any other contract provision when said change
causes an increase or decrease of \$250,000 or less in the estimated
cost of this contract. Each change shall controlling in making this
determination, and such change shall not, for purposes of determining
the applicability of this clause, be added to any other changes (s). The
parties recognize that several changes may be grouped together in a
bilateral modification for definitization; however, the dollar value of
each individual change will be controlling in determining whether or not
an equitable adjustment is in order.

(End of clause)

**H.8 CONTRACT EXTENSION RESULTING FROM PROTESTS**

\(a\) If the award of a successor contract to perform the services being
performed under this contract is delayed because of a protest, the
Contracting Officer may extend the period of performance on this
contract to cover any delay caused by such a protest. The Contractor
shall be entitled to an equitable adjustment for such an extension,
subject to the limitations of paragraph (b).

\(b\) The final award fee evaluation period may be extended to include
the contract extension period provided for in paragraph (a). However, if
the Contractor is the protester or one of the protesters, no additional
fee shall be put in the award fee pool or otherwise made available to
the Contractor, unless the Contractor or another protester substantially
prevails in the protest.

(End of clause)

**H.9 LIMITATION OF FUTURE CONTRACTING (NASA 1852.209-71) (DEC 1988)**

\(a\) The Contracting Officer has determined that this acquisition may
give rise to a potential organizational conflict of interest.
Accordingly, the attention of prospective offerors is invited to FAR
Subpart 9.5\--Organizational Conflicts of Interest.

\(b\) The nature of this conflict is the MSOC contractor may be tasked
to provide systems engineering and technical direction for a system, but
does not have overall contractual responsibility for its development,
its integration, assembly, and checkout, or its production. The MSOC
contractor shall not (1) be awarded a contract to supply the system or
any of its major components or (2) be a subcontractor or consultant to a
supplier of the system or any of its major components.

Systems engineering includes a combination of all the following
activities: determining specifications, identifying and resolving
interface problems, developing test requirements, evaluating test data,
and supervising design. Technical direction includes a combination of
substantially all of the following activities: developing work
statement, determining parameters, directing other contractors'
operations, and resolving technical controversies. In performing these
activities, a contractor occupies a highly influential and responsible
position in determining a system's basic concepts and supervising their
execution by other contractors. Therefore, this contractor should not be
in a position to make decisions favoring its own products or
capabilities.

\(c\) The restrictions upon future contracting are as follows:

\(1\) If the Contractor, under the terms of this contract, or through
the performance of tasks pursuant to this contract, is required to
develop specifications or statements of work that are to be incorporated
into a solicitation, the Contractor shall be ineligible to perform the
work described in that solicitation as a prime or first-tier
subcontractor under an ensuing NASA contract. This restriction shall
remain in effect for a reasonable time, as agreed to by the Contracting
Officer and the Contractor, sufficient to avoid unfair competitive
advantage or potential bias (this time shall in no case be less than the
duration of the initial production contract). NASA shall not
unilaterally require the Contractor to prepare such specifications or
statements of work under this contract.

\(2\) To the extent that the work under this contract requires access to
proprietary, business confidential, or financial data of other
companies, and as long as these data remain proprietary or confidential,
the Contractor shall protect these data from unauthorized use and
disclosure and agrees not to use them to compete with those other
companies.

(End of clause)

**H.10 OPTION FOR THE INCREMENAL INCREASE OF EFFORT**

The Government may increase the number of direct labor hours required to
be furnished during the period of performance by an amount ranging from
1 to 2,700 hours. If the Government elects to exercise its option,
referred throughout this clause as a flex option, to increase the number
of direct labor hours to be furnished, the Contractor will be so
notified with a unilateral modification to the contract executed by the
Contracting Officer, which will make changes to affected contract terms
and conditions as authorized by this Clause.

The terms and conditions relating to the Government's rights as provided
herein are as follows:

a\. The options provided for herein may be exercised one or more times,
provided that the total number of optional direct labor hours shall not
exceed the maximum amount stated above.

b\. If the Government exercises one or more flex options pursuant to
this clause, the administration of such action(s) shall be as follows:

(i) The Government may increase the number of direct labor hours listed
    in Clause H.6 "Level-of-Effort (Cost)" during the base period,
    option 1, option 2, and option 3 by an amount ranging from 1 to
    2,700 hours. Flex option(s) can only be exercised in option 1,
    option 2, and option 3 if the applicable option(s) to extend
    contract period of performance are exercised.

(ii) The increase in estimated cost and maximum available award fee
     (applicable to Clause B.1 "Estimated Cost and Award Fee") due to
     the exercise of a flex option, or multiple flex options, will be
     based on when the flex option(s) is exercised. In Part iii below, a
     matrix specifies the increase in estimated cost and maximum
     available award fee for each additional direct labor hour ordered
     through the exercise of a flex option or multiple flex options.

(iii) The matrix below specifies the per hour increases that are
      applicable during the period the flex option is executed by the
      Contracting Officer.

+---------------------+---------+--------+--------+---------+---------+
| **Description**     | **Basic | **     | **     | *       | *       |
|                     | P       | Option | Option | *Option | *Option |
|                     | eriod** | 1**    | 2**    | 3**     | 3**     |
|                     |         |        |        |         |         |
|                     |         |        |        | **(GFY  | **(GFY  |
|                     |         |        |        | 05)**   | 06)**   |
+---------------------+---------+--------+--------+---------+---------+
| Increase in         | \$70.59 | \      | \      | \$76.18 | \$78.37 |
| estimated cost for  |         | $72.81 | $75.07 |         |         |
| each direct labor   |         |        |        |         |         |
| hour ordered by     |         |        |        |         |         |
| exercising flex     |         |        |        |         |         |
| option (s)          |         |        |        |         |         |
+---------------------+---------+--------+--------+---------+---------+
| Increase in maximum | \$6.53  | \$6.55 | \$6.76 | \$6.86  | \$7.05  |
| available award fee |         |        |        |         |         |
| for each direct     |         |        |        |         |         |
| labor hour ordered  |         |        |        |         |         |
| by exercising flex  |         |        |        |         |         |
| option (s)          |         |        |        |         |         |
+---------------------+---------+--------+--------+---------+---------+
| Amount of hours     | 1 to    |        |        |         |         |
| available for flex  | 2,700   |        |        |         |         |
| option(s)           | hours   |        |        |         |         |
|                     | are     |        |        |         |         |
|                     | av      |        |        |         |         |
|                     | ailable |        |        |         |         |
+---------------------+---------+--------+--------+---------+---------+

## I.1 LISTING OF CLAUSES INCORPORATED BY REFERENCE 

## NOTICE: The following contract clauses pertinent to this section are hereby incorporated by reference: 

## I. FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER 1) 

CLAUSE

[NUMBER]{.underline} [DATE]{.underline} [TITLE]{.underline}

> 52.202-1 DEC 2001 DEFINITIONS
>
> 52.203-3 APR 1984 GRATUITIES
>
> 52.203-5 APR 1984 COVENANT AGAINST CONTINGENT FEES
>
> 52.203-6 JUL 1995 RESTRICTIONS ON SUBCONTRACTOR SALES TO THE
>
> GOVERNMENT
>
> 52.203-7 JUL 1995 ANTI-KICKBACK PROCEDURES
>
> 52.203-8 JAN 1997 CANCELLATION, RESCISION, AND RECOVERY OF FUNDS
>
> FOR ILLEGAL OR IMPROPER ACTIVITY
>
> 52.203-10 JAN 1997 PRICE OR FEE ADJUSTMENT FOR ILLEGAL OR IMPROPER
>
> ACTIVITY
>
> 52.203-12 JUN 1997 LIMITATION ON PAYMENTS TO INFLUENCE CERTAIN
>
> FEDERAL TRANSACTIONS
>
> 52.204-2 AUG. 1996 SECURITY REQUIREMENTS
>
> 52.204-4 AUG 2000 PRINTING/COPYING DOUBLE SIDED ON RECYCLED
>
> PAPER
>
> 52.209-6 JUL 1995 PROTECTING THE GOVERNMENT\'S INTEREST WHEN
>
> SUBCONTRACTING WITH CONTRACTORS DEBARRED,
>
> SUSPENDED, OR PROPOSED FOR DEBARMENT
>
> 52.211-15 SEPT 1990 DEFENSE PRIORITY AND ALLOCATION REQUESTS
>
> 52.215-2 JUNE 1999 AUDIT AND RECORDS\--NEGOTIATION
>
> 52.215-8 OCT 1997 ORDER OF PRECEDENCE\--UNIFORM CONTRACT FORMAT
>
> 52.215-10 OCT 1997 PRICE REDUCTION FOR DEFECTIVE COST OR PRICING
>
> DATA
>
> 52.215-12 OCT 1997 SUBCONTRACTOR COST OR PRICING DATA
>
> 52.215-14 OCT 1997 INTEGRITY OF UNIT PRICES (ALT I) (OCT 1997)
>
> 52.215-15 DEC 1998 PENSION ADJUSTMENTS AND ASSET REVERSIONS
>
> 52.215-18 OCT 1997 REVERSION OR ADJUSTMENT OF PLANS FOR
>
> POSTRETIREMENT BENEFITS (PRB) OTHER THAN
>
> PENSIONS
>
> 52.215-19 OCT 1997 NOTIFICATION OF OWNERSHIP CHANGES
>
> 52.215-21 OCT 1997 REQUIREMENTS FOR COST OR PRICING DATA OR
>
> INFORMATION OTHER THAN COST OR PRICING DATA---
>
> MODIFICATIONS
>
> 52.216-7 DEC 2002 ALLOWABLE COST AND PAYMENT
>
> 52.219-8 OCT 2000 UTILIZATION OF SMALL BUSINESS CONCERNS
>
> 52.219-9 JAN 2002 SMALL BUSINESS SUBCONTRACTING PLAN (ALT II) (OCT
>
> 2001\)
>
> 52.219-16 JAN 1999 LIQUIDATED DAMAGES\--SUBCONTRACTING PLAN
>
> 52.222-1 FEB 1997 NOTICE TO THE GOVERNMENT OF LABOR DISPUTES
>
> 52.222-3 AUG 1996 CONVICT LABOR
>
> 52.222-4 SEPT 2000 CONTRACT WORK HOURS AND SAFETY STANDARDS ACT

52.222-21 FEB 1999 PROHIBITION OF SEGREGATED FACILITIES

> 52.222-26 FEB 2002 EQUAL OPPORTUNITY

52.222-35 DEC 2001 EQUAL OPPORTUNITY FOR SPECIAL DISABLED

VETERANS, VETERANS OF THE VIETNAM ERA, AND

OTHER ELIGIBLE VETERANS

> 52.222-36 JUN 1998 AFFIRMATIVE ACTION FOR WORKERS WITH
>
> DISABILITIES
>
> 52.222-37 DEC 2001 EMPLOYMENT REPORTS ON SPECIAL DISABLED
>
> VETERANS, VETERANS OF THE VIETNAM ERA, AND
>
> OTHER ELIGIBLE VETERANS

41. MAY 1989 SERVICE CONTRACT ACT OF 1965, AS AMENDED

52.223-3 JAN 1997 HAZARDOUS MATERIAL INDENTIFICATION AND

MATERIAL SAFETY DATA (ALT I) (JUL 1995) (Insert

"NONE" in paragraph b)

> 52.223-5 APR 1998 POLLUTION PREVENTION AND RIGHT-TO-KNOW
>
> INFORMATION
>
> 52.223-10 AUG 2000 WASTE REDUCTION PROGRAM
>
> 52.223-14 OCT 2000 TOXIC CHEMICAL RELEASE REPORTING

52.225-13 JUL 2000 RESTRICTIONS ON CERTAIN FOREIGN PURCHASES

> 52.227-1 JUL 1995 AUTHORIZATION AND CONSENT
>
> 52.227-2 AUG 1996 NOTICE AND ASSISTANCE REGARDING PATENT AND
>
> COPYRIGHT INFRINGEMENT
>
> 52.227-16 JUN 1987 ADDITIONAL DATA REQUIREMENTS

7.  MAR 1996 INSURANCE\--LIABILITY TO THIRD PERSONS

52.229-8 MAR 1990 TAXES-FOREIGN COST-REIMBURSEMENT CONTRACTS

> 52.230-2 APR 1998 COST ACCOUNTING STANDARDS
>
> 52.230-6 NOV 1999 ADMINISTRATION OF COST ACCOUNTING STANDARDS
>
> 52.232-9 APR 1984 LIMITATION ON WITHHOLDING PAYMENTS
>
> 52.232-17 JUN 1996 INTEREST
>
> 52.232-22 APR 1984 LIMITATION OF FUNDS
>
> 52.232-23 JAN 1986 ASSIGNMENT OF CLAIMS

52.232-25 FEB 2002 PROMPT PAYMENT (ALT I) (FEB 2002)

52.232-34 MAY 1999 PAYMENT BY ELECTRONIC FUNDS TRANSFER\--OTHER

> THAN CENTRAL CONTRACTOR REGISTRATION (Insert in
>
> paragraph (b)(1) no later than concurrent with the first request for
>
> payment.)
>
> 52.233-1 JULY 2002 DISPUTES (ALT I) (DEC 1991)
>
> 52.233-3 AUG 1996 PROTEST AFTER AWARD (ALT I) (JUN 1985)
>
> 52.237-2 APR 1984 PROTECTION OF GOVERNMENT BUILDINGS,
>
> EQUIPMENT, AND VEGETATION
>
> 52.237-3 JAN 1991 CONTINUITY OF SERVICES
>
> 52.242-1 APR 1984 NOTICE OF INTENT TO DISALLOW COSTS

52.242-3 MAY 2001 PENALTIES FOR UNALLOWABLE COSTS

> 52.242-4 JAN 1997 CERTIFICATION OF FINAL INDIRECT COSTS

52.242-13 JUL 1995 BANKRUPTCY

> 52.243-2 AUG 1987 CHANGES\--COST-REIMBURSEMENT (ALT II) (APR 1984)
>
> 52.243-6 APR 1984 CHANGE ORDER ACCOUNTING
>
> 52.244-2 AUG 1998 SUBCONTRACTS (ALT I) (AUG 1998) (Insert "NONE" in

Paragraphs (e) and (k))

5.  DEC 1996 COMPETITION IN SUBCONTRACTING

> 52.245-5 JAN 1986 GOVERNMENT PROPERTY (COST-REIMBURSEMENT,
>
> TIME-AND-MATERIAL, OR LABOR-HOUR CONTRACTS)
>
> (DEVIATION) (JUL 1995)\--(g)(5) of the clause shall read as
>
> follows: \"The contractor shall notify the contracting officer upon
>
> loss or destruction of, or damage to, Government property
>
> provided under this contract, with the exception of low value
>
> property for which loss, damage, or destruction is reported at
>
> contract termination, completion, or when needed for continued
>
> performance. The Contractor shall take all reasonable action to
>
> protect the Government property from further damage, separate the
>
> damaged and undamaged Government property, put all the affected
>
> Government property in the best possible order, and furnish to the
>
> Contracting Officer a statement of‑‑\". The balance of (g)(5) is
>
> unchanged.
>
> 52.245-18 FEB 1993 SPECIAL TEST EQUIPMENT
>
> 52.246-25 FEB 1997 LIMITATION OF LIABILITY\--SERVICES
>
> 52.247-1 APR 1984 COMMERCIAL BILL OF LADING NOTATIONS
>
> 52.247-63 JAN 1997 PREFERENCE FOR U.S.-FLAG AIR CARRIERS
>
> 52.247-64 APR 2003 PREFERENCE FOR PRIVATELY OWNED U.S. FLAG COMMERCIAL
> VESSELS

52.248-1 FEB 2000 VALUE ENGINEERING

> 52.249-6 SEP 1996 TERMINATION (COST-REIMBURSEMENT)
>
> 52.249-14 APR 1984 EXCUSABLE DELAYS

52.251-1 APR 1984 GOVERNMENT SUPPLY SOURCES

52.251-2 JAN 1991 INTERAGENCY FLEET MANAGEMENT SYSTEMS

> VEHICLES AND RELATED SERVICES
>
> 52.253-1 JAN 1991 COMPUTER GENERATED FORMS
>
> II\. NASA FAR SUPPLEMENT (48 CFR CHAPTER 18) PROVISIONS

CLAUSE

[NUMBER]{.underline} [DATE]{.underline} [TITLE]{.underline}

> 1852.203-70 JUN 2001 DISPLAY OF INSPECTOR GENERAL HOTLINE POSTERS

1852.216-89 JUL 1997 ASSIGNMENT AND RELEASE FORMS

1852.219-74 SEPT 1990 USE OF RURAL AREA SMALL BUSINESSES

1852.219-75 MAY 1999 SMALL BUSINESS SUBCONTRACTING REPORTING

1852.219-76 JUL 1997 NASA 8 PERCENT GOAL

> 1852.219-79 MAR 1999 MENTOR REQUIREMENTS AND EVALUATION

1852.223-74 MAR 1996 DRUG-AND ALCOHOL-FREE WORKFORCE

1852.237-70 DEC 1988 EMERGENCY EVACUATION PROCEDURES

1852.242-75 MAR 1999 EARNED VALUE MANAGEMENT SYSTEMS

> 1852.242-78 APR 2001 EMERGENCY MEDICAL SERVICES AND EVACUATION
>
> 1852.243-71 MAR 1997 SHARED SAVINGS

(End of By Reference Section)

## I. 2 APPROVAL OF CONTRACT (FAR 52.204‑1) (DEC 1989)

This contract is subject to the written approval of the JSC Procurement
Officer and shall not be binding until so approved.

(End of clause)

## I.3 PAYMENT FOR OVERTIME PREMIUMS (FAR 52.222-2) (JUL 1990)

\(a\) The use of overtime is authorized under this contract if the
overtime premium does not exceed \$0 or the overtime premium is paid for
work-

\(1\) Necessary to cope with emergencies such as those resulting from
accidents, natural disasters, breakdowns of production equipment, or
occasional production bottlenecks of a sporadic nature;

\(2\) By indirect-labor employees such as those performing duties in
connection with administration, protection, transportation, maintenance,
standby plant protection, operation of utilities, or accounting;

\(3\) To perform tests, industrial processes, laboratory procedures,
loading or unloading of transportation conveyances, and operations in
flight or afloat that are continuous in nature and cannot reasonably be
interrupted or completed otherwise; or

\(4\) That will result in lower overall costs to the Government.

\(b\) Any request for estimated overtime premiums that exceeds the
amount specified above shall include all estimated overtime for contract
completion and shall-

\(1\) Identify the work unit; *e.g*., department or section in which the
requested overtime will be used, together with present workload,
staffing, and other data of the affected unit sufficient to permit the
Contracting Officer to evaluate the necessity for the overtime;

\(2\) Demonstrate the effect that denial of the request will have on the
contract delivery or performance schedule;

\(3\) Identify the extent to which approval of overtime would affect the
performance or payments in connection with other Government contracts,
together with identification of each affected contract; and

\(4\) Provide reasons why the required work cannot be performed by using
multishift operations or by employing additional personnel.

(End of clause)

## I.4 DRUG-FREE WORKPLACE (FAR 52.223-6) (MAY 2001) 

\(a\) Definitions. As used in this clause-

\"Controlled substance\" means a controlled substance in schedules I
through V of section 202 of the Controlled Substances Act (21 U.S.C.
812) and as further defined in regulation at 21 CFR 1308.11 - 1308.15.

\"Conviction\" means a finding of guilt (including a plea of *nolo
contendere*) or imposition of sentence, or both, by any judicial body
charged with the responsibility to determine violations of the Federal
or State criminal drug statutes.

\"Criminal drug statute\" means a Federal or non-Federal criminal
statute involving the manufacture, distribution, dispensing, possession,
or use of any controlled substance.

\"Drug-free workplace\" means the site(s) for the performance of work
done by the Contractor in connection with a specific contract where
employees of the Contractor are prohibited from engaging in the unlawful
manufacture, distribution, dispensing, possession, or use of a
controlled substance.

\"Employee\" means an employee of a Contractor directly engaged in the
performance of work under a Government contract. \"Directly engaged\" is
defined to include all direct cost employees and any other Contractor
employee who has other than a minimal impact or involvement in contract
performance.

\"Individual\" means an offeror/contractor that has no more than one
employee including the offeror/contractor.

\(b\) The Contractor, if other than an individual, shall- within 30 days
after award (unless a longer period is agreed to in writing for
contracts of 30 days or more performance duration), or as soon as
possible for contracts of less than 30 days performance duration-

\(1\) Publish a statement notifying its employees that the unlawful
manufacture, distribution, dispensing, possession, or use of a
controlled substance is prohibited in the Contractor\'s workplace and
specifying the actions that will be taken against employees for
violations of such prohibition;

\(2\) Establish an ongoing drug-free awareness program to inform such
employees about-

> \(i\) The dangers of drug abuse in the workplace;
>
> \(ii\) The Contractor\'s policy of maintaining a drug-free workplace;
>
> \(iii\) Any available drug counseling, rehabilitation, and employee
> assistance programs; and
>
> \(iv\) The penalties that may be imposed upon employees for drug abuse
> violations occurring in the workplace;

\(3\) Provide all employees engaged in performance of the contract with
a copy of the statement required by paragraph (b)(1) of this clause;

\(4\) Notify such employees in writing in the statement required by
paragraph (b)(1) of this clause that, as a condition of continued
employment on this contract, the employee will-

> \(i\) Abide by the terms of the statement; and

\(ii\) Notify the employer in writing of the employee\'s conviction
under a criminal drug statute for a violation occurring in the workplace
no later than 5 days after such conviction;

\(5\) Notify the Contracting Officer in writing within 10 days after
receiving notice under subdivision (b)(4)(ii) of this clause, from an
employee or otherwise receiving actual notice of such conviction. The
notice shall include the position title of the employee;

\(6\) Within 30 days after receiving notice under subdivision (b)(4)(ii)
of this clause of a conviction, take one of the following actions with
respect to any employee who is convicted of a drug abuse violation
occurring in the workplace:

> \(i\) Taking appropriate personnel action against such employee, up to
> and including termination; or
>
> \(ii\) Require such employee to satisfactorily participate in a drug
> abuse assistance or rehabilitation program approved for such purposes
> by a Federal, State, or local health, law enforcement, or other
> appropriate agency; and

\(7\) Make a good faith effort to maintain a drug-free workplace through
implementation of paragraphs (b)(1) through (b)(6) of this clause.

\(c\) The Contractor, if an individual, agrees by award of the contract
or acceptance of a purchase order, not to engage in the unlawful
manufacture, distribution, dispensing, possession, or use of a
controlled substance while performing this contract.

\(d\) In addition to other remedies available to the Government, the
Contractor\'s failure to comply with the requirements of paragraph (b)
or (c) of this clause may, pursuant to FAR 23.506, render the Contractor
subject to suspension of contract payments, termination of the contract
or default, and suspension or debarment.

(End of clause)

## I. 5 STATEMENT OF EQUIVALENT RATES FOR FEDERAL HIRES (FAR 52.222‑42) (MAY 1989) 

In compliance with the Service Contract Act of 1965, as amended, and the
regulations of the Secretary of Labor (29 CFR Part 4), this clause
identifies the classes of service employees expected to be employed
under the contract and states the wages and fringe benefits payable to
each if they were employed by the contracting agency subject to the
provisions of 5 U.S.C. 5341 or 5332.

THIS STATEMENT IS FOR INFORMATION ONLY: IT

IS NOT A WAGE DETERMINATION

See Attachment J-1

(End of clause)

## I.6 RIGHTS IN DATA-GENERAL (FAR 52.227-14) (JUN 1987) as modified by NASA FAR Supplement 1852.227-14

\(a\) *Definitions*. \"Computer software,\" as used in this clause,
means computer programs, computer data bases, and documentation thereof.

\"Data,\" as used in this clause, means recorded information, regardless
of form or the media on which it may be recorded. The term includes
technical data and computer software. The term does not include
information incidental to contract administration, such as financial,
administrative, cost or pricing, or management information.

\"Form, fit, and function data,\" as used in this clause, means data
relating to items, components, or processes that are sufficient to
enable physical and functional interchangeability, as well as data
identifying source, size, configuration, mating, and attachment
characteristics, functional characteristics, and performance
requirements; except that for computer software it means data
identifying source, functional characteristics, and performance
requirements but specifically excludes the source code, algorithm,
process, formulae, and flow charts of the software.

\"Limited rights,\" as used in this clause, means the rights of the
Government in limited rights data as set forth in the Limited Rights
Notice of paragraph (g)(2) if included in this clause.

\"Limited rights data,\" as used in this clause, means data (other than
computer software) that embody trade secrets or are commercial or
financial and confidential or privileged, to the extent that such data
pertain to items, components, or processes developed at private expense,
including minor modifications thereof.

\"Restricted computer software,\" as used in this clause, means computer
software developed at private expense and that is a trade secret; is
commercial or financial and is confidential or privileged; or is
published copyrighted computer software, including minor modifications
of such computer software.

\"Restricted rights,\" as used in this clause, means the rights of the
Government in restricted computer software, as set forth in a Restricted
Rights Notice of paragraph (g)(3) if included in this clause, or as
otherwise may be provided in a collateral agreement incorporated in and
made part of this contract, including minor modifications of such
computer software.

\"Technical data,\" as used in this clause, means data (other than
computer software) which are of a scientific or technical nature.

\"Unlimited rights,\" as used in this clause, means the right of the
Government to use, disclose, reproduce, prepare derivative works,
distribute copies to the public, and perform publicly and display
publicly, in any manner and for any purpose, and to have or permit
others to do so.

\(b\) *Allocation of rights*.

\(1\) Except as provided in paragraph (c) of this clause regarding
copyright, the Government shall have unlimited rights in-

> \(i\) Data first produced in the performance of this contract;
>
> \(ii\) Form, fit, and function data delivered under this contract;
>
> \(iii\) Data delivered under this contract (except for restricted
> computer software) that constitute manuals or instructional and
> training material for installation, operation, or routine maintenance
> and repair of items, components, or processes delivered or furnished
> for use under this contract; and
>
> \(iv\) All other data delivered under this contract unless provided
> otherwise for limited rights data or restricted computer software in
> accordance with paragraph (g) of this clause.

\(2\) The Contractor shall have the right to-

> \(i\) Use, release to others, reproduce, distribute, or publish any
> data first produced or specifically used by the Contractor in the
> performance of this contract, unless provided otherwise in paragraph
> (d) of this clause;
>
> \(ii\) Protect from unauthorized disclosure and use those data which
> are limited rights data or restricted computer software to the extent
> provided in paragraph (g) of this clause;
>
> \(iii\) Substantiate use of, add or correct limited rights, restricted
> rights, or copyright notices and to take other appropriate action, in
> accordance with paragraphs (e) and (f) of this clause; and
>
> \(iv\) Establish claim to copyright subsisting in data first produced
> in the performance of this contract to the extent provided in
> paragraph (c)(1) of this clause.

\(c\) *Copyright*-

\(1\) *Data first produced in the performance of this contract.* Unless
provided otherwise in paragraph (d) of this clause, the Contractor may
establish, without prior approval of the Contracting Officer, claim to
copyright subsisting in scientific and technical articles based on or
containing data first produced in the performance of this contract and
published in academic, technical or professional journals, symposia
proceedings or similar works. The prior, express written permission of
the Contracting Officer is required to establish claim to copyright
subsisting in all other data first produced in the performance of this
contract. When claim to copyright is made, the Contractor shall affix
the applicable copyright notices of 17 U.S.C. 401 or 402 and
acknowledgment of Government sponsorship (including contract number) to
the data when such data are delivered to the Government, as well as when
the data are published or deposited for registration as a published work
in the U.S. Copyright Office. For data other than computer software the
Contractor grants to the Government, and others acting on its behalf, a
paid-up, nonexclusive, irrevocable worldwide license in such copyrighted
data to reproduce, prepare derivative works, distribute copies to the
public, and perform publicly and display publicly, by or on behalf of
the Government. For computer software, the Contractor grants to the
Government and others acting in its behalf, a paid-up nonexclusive,
irrevocable worldwide license in such copyrighted computer software to
reproduce, prepare derivative works, and perform publicly and display
publicly by or on behalf of the Government.

\(2\) *Data not first produced in the performance of this contract*. The
Contractor shall not, without prior written permission of the
Contracting Officer, incorporate in data delivered under this contract
any data not first produced in the performance of this contract and
which contains the copyright notice of 17 U.S.C. 401 or 402, unless the
Contractor identifies such data and grants to the Government, or
acquires on its behalf, a license of the same scope as set forth in
paragraph (c)(1) of this clause; *provided*, however, that if such data
are computer software the Government shall acquire a copyright license
as set forth in paragraph (g)(3) of this clause if included in this
contract or as otherwise may be provided in a collateral agreement
incorporated in or made part of this contract.

\(3\) *Removal of copyright notices*. The Government agrees not to
remove any copyright notices placed on data pursuant to this paragraph
(c), and to include such notices on all reproductions of the data.

\(d\) *Release, publication and use of data*.

\(1\) The Contractor shall have the right to use, release to others,
reproduce, distribute, or publish any data first produced or
specifically used by the Contractor in the performance of this contract,
except to the extent such data may be subject to the Federal export
control or national security laws or regulations, or unless otherwise
provided in this paragraph of this clause or expressly set forth in this
contract.

\(2\) The Contractor agrees that to the extent it receives or is given
access to data necessary for the performance of this contract which
contain restrictive markings, the Contractor shall treat the data in
accordance with such markings unless otherwise specifically authorized
in writing by the Contracting Officer.

(3)(i) The Contractor agrees not to estab­lish claim to copyright,
publish or release to others any computer soft­ware first pro­duced in the
performance of this contract without the Contracting Officer\'s prior
written permission.

\(ii\) If the Government desires to obtain copyright in computer
soft­ware first pro­duced in the performance of this con­tract and
permission has not been granted as set forth in paragraph (d)(3)(i) of
this clause, the Contracting Officer may direct the contractor to
assert, or authorize the asser­tion of, claim to copyright in such data
and to assign, or obtain the assignment of, such copyright to the
Government or its desig­nated assignee.

\(iii\) Whenever the word \"establish\" is used in this clause, with
reference to a claim to copyright, it shall be con­strued to mean
\"assert\".

\(e\) *Unauthorized marking of data*.

\(1\) Notwithstanding any other provisions of this contract concerning
inspection or acceptance, if any data delivered under this contract are
marked with the notices specified in paragraph (g)(2) or (g)(3) of this
clause and use of such is not authorized by this clause, or if such data
bears any other restrictive or limiting markings not authorized by this
contract, the Contracting Officer may at any time either return the data
to the Contractor, or cancel or ignore the markings. However, the
following procedures shall apply prior to canceling or ignoring the
markings.

> \(i\) The Contracting Officer shall make written inquiry to the
> Contractor affording the Contractor 30 days from receipt of the
> inquiry to provide written justification to substantiate the propriety
> of the markings;
>
> \(ii\) If the Contractor fails to respond or fails to provide written
> justification to substantiate the propriety of the markings within the
> 30-day period (or a longer time not exceeding 90 days approved in
> writing by the Contracting Officer for good cause shown), the
> Government shall have the right to cancel or ignore the markings at
> any time after said period and the data will no longer be made subject
> to any disclosure prohibitions.
>
> \(iii\) If the Contractor provides written justification to
> substantiate the propriety of the markings within the period set in
> subdivision (e)(1)(i) of this clause, the Contracting Officer shall
> consider such written justification and determine whether or not the
> markings are to be cancelled or ignored. If the Contracting Officer
> determines that the markings are authorized, the Contractor shall be
> so notified in writing. If the Contracting Officer determines, with
> concurrence of the head of the contracting activity, that the markings
> are not authorized, the Contracting Officer shall furnish the
> Contractor a written determination, which determination shall become
> the final agency decision regarding the appropriateness of the
> markings unless the Contractor files suit in a court of competent
> jurisdiction within 90 days of receipt of the Contracting Officer\'s
> decision. The Government shall continue to abide by the markings under
> this subdivision (e)(1)(iii) until final resolution of the matter
> either by the Contracting Officer\'s determination becoming final (in
> which instance the Government shall thereafter have the right to
> cancel or ignore the markings at any time and the data will no longer
> be made subject to any disclosure prohibitions), or by final
> disposition of the matter by court decision if suit is filed.

\(2\) The time limits in the procedures set forth in paragraph (e)(1) of
this clause may be modified in accordance with agency regulations
implementing the Freedom of Information Act (5 U.S.C. 552) if necessary
to respond to a request thereunder.

\(3\) This paragraph (e) does not apply if this contract is for a major
system or for support of a major system by a civilian agency other than
NASA and the U.S. Coast Guard agency subject to the provisions of Title
III of the Federal Property and Administrative Services Act of 1949.

\(4\) Except to the extent the Government\'s action occurs as the result
of final disposition of the matter by a court of competent jurisdiction,
the Contractor is not precluded by this paragraph (e) from bringing a
claim under the Contract Disputes Act, including pursuant to the
Disputes clause of this contract, as applicable, that may arise as the
result of the Government removing or ignoring authorized markings on
data delivered under this contract.

\(f\) *Omitted or incorrect markings*.

\(1\) Data delivered to the Government without either the limited rights
or restricted rights notice as authorized by paragraph (g) of this
clause, or the copyright notice required by paragraph (c) of this
clause, shall be deemed to have been furnished with unlimited rights,
and the Government assumes no liability for the disclosure, use, or
reproduction of such data. However, to the extent the data has not been
disclosed without restriction outside the Government, the Contractor may
request, within 6 months (or a longer time approved by the Contracting
Officer for good cause shown) after delivery of such data, permission to
have notices placed on qualifying data at the Contractor\'s expense, and
the Contracting Officer may agree to do so if the Contractor-

> \(i\) Identifies the data to which the omitted notice is to be
> applied;
>
> \(ii\) Demonstrates that the omission of the notice was inadvertent;
>
> \(iii\) Establishes that the use of the proposed notice is authorized;
> and
>
> \(iv\) Acknowledges that the Government has no liability with respect
> to the disclosure, use, or reproduction of any such data made prior to
> the addition of the notice or resulting from the omission of the
> notice.

\(2\) The Contracting Officer may also (i) permit correction at the
Contractor\'s expense of incorrect notices if the Contractor identifies
the data on which correction of the notice is to be made, and
demonstrates that the correct notice is authorized, or (ii) correct any
incorrect notices.

\(g\) *Protection of limited rights data and restricted computer
software*.

\(1\) When data other than that listed in subdivisions (b)(1)(i), (ii),
and (iii) of this clause are specified to be delivered under this
contract and qualify as either limited rights data or restricted
computer software, if the Contractor desires to continue protection of
such data, the Contractor shall withhold such data and not furnish them
to the Government under this contract. As a condition to this
withholding, the Contractor shall identify the data being withheld and
furnish form, fit, and function data in lieu thereof. Limited rights
data that are formatted as a computer data base for delivery to the
Government are to be treated as limited rights data and not restricted
computer software.

\(2\) \[Reserved\]

\(3\) \[Reserved\]

\(h\) *Subcontracting*. The Contractor has the responsibility to obtain
from its subcontractors all data and rights therein necessary to fulfill
the Contractor\'s obligations to the Government under this contract. If
a subcontractor refuses to accept terms affording the Government such
rights, the Contractor shall promptly bring such refusal to the
attention of the Contracting Officer and not proceed with subcontract
award without further authorization.

\(i\) *Relationship to patents*. Nothing contained in this clause shall
imply a license to the Government under any patent or be construed as
affecting the scope of any license or other right otherwise granted to
the Government.

(End of clause)

## I.7 TAXES-FOREIGN COST-REIMBURSEMENT CONTRACTS (FAR 52.229-8) (MAR 1990)

\(a\) Any tax or duty from which the United States Government is exempt
by agreement with the Government of any such country, or from which the
Contractor or any subcontractor under this contract is exempt under the
laws of any such country, shall not constitute an allowable cost under
this contract.

\(b\) If the Contractor or subcontractor under this contract obtains a
foreign tax credit that reduces its Federal income tax liability under
the United States Internal Revenue Code (Title 26, U.S. Code) because of
the payment of any tax or duty that was reimbursed under this contract,
the amount of the reduction shall be paid or credited at the time of
such offset to the Government of the United States as the Contracting
Officer directs.

## (End of clause)

## I. 8 SUBCONTRACTS FOR COMMERCIAL ITEMS (FAR 52.244-6) (MAY 2002)

\(a\) *Definitions.* As used in this clause-

\"Commercial item\" has the meaning contained in the clause at 52.202-1,
Definitions.

\"Subcontract\" includes a transfer of commercial items between
divisions, subsidiaries, or affiliates of the Contractor or
subcontractor at any tier.

\(b\) To the maximum extent practicable, the Contractor shall
incorporate, and require its subcontractors at all tiers to incorporate,
commercial items or nondevelopmental items as components of items to be
supplied under this contract.

\(c\) (1) The Contractor shall insert the following clauses in
subcontracts for commercial items:

> \(i\) 52.219-8, Utilization of Small Business Concerns (Oct 2000)
> (15 U.S.C. 637(d)(2) and (3)), in all subcontracts that offer further
> subcontracting opportunities. If the subcontract (except subcontracts
> to small business concerns) exceeds \$500,000 (\$1,000,000 for
> construction of any public facility), the subcontractor must include
> 52.219-8 in lower tier subcontracts that offer subcontracting
> opportunities.
>
> \(ii\) 52.222-26, Equal Opportunity (Apr 2002) (E.O. 11246).
>
> \(iii\) 52.222-35, Equal Opportunity for Special Disabled Veterans,
> Veterans of the Vietnam Era, and Other Eligible Veterans (Dec 2001)
> (38 U.S.C. 4212(a));
>
> \(iv\) 52.222-36, Affirmative Action for Workers with Disabilities
> (June 1998) (29 U.S.C. 793).
>
> \(v\) 52.247-64, Preference for Privately Owned U.S.-Flag Commercial
> Vessels (June 2000) (46 U.S.C. Appx 1241) (flowdown not required for
> subcontracts awarded beginning May 1, 1996).

\(2\) While not required, the Contractor may flow down to subcontracts
for commercial items a minimal number of additional clauses necessary to
satisfy its contractual obligations.

\(d\) The Contractor shall include the terms of this clause, including
this paragraph (d), in subcontracts awarded under this contract.

(End of clause)

**I.9 SUBMISSION OF COMMERCIAL TRANSPORTATION BILLS TO THE GENERAL
SERVICES ADMINISTRATION FOR AUDIT (FAR 52.247-67) (JUN 1997)**

(a)(1) In accordance with paragraph (a)(2) of this clause, the
Contractor shall submit to the General Services Administration (GSA) for
audit, legible copies of all paid freight bills/invoices, commercial
bills of lading (CBL\'s), passenger coupons, and other supporting
documents for transportation services on which the United States will
assume freight charges that were paid-

> \(i\) By the Contractor under a cost-reimbursement contract; and
>
> \(ii\) By a first-tier subcontractor under a cost-reimbursement
> subcontract thereunder.

\(2\) Cost-reimbursement Contractors shall only submit for audit those
CBL\'s with freight shipment charges exceeding \$50.00. Bills under
\$50.00 shall be retained on-site by the Contractor and made available
for GSA on-site audits. This exception only applies to freight shipment
bills and is not intended to apply to bills and invoices for any other
transportation services.

\(b\) The Contractor shall forward copies of paid freight
bills/invoices, CBL\'s, passenger coupons, and supporting documents as
soon as possible following the end of the month, in one package to the:

General Services Administration

Attn: FWA

1800 F. Street, NW

Washington, DC 20405

The Contractor shall include the paid freight bills/invoices, CBL\'s,
passenger coupons, and supporting documents for first-tier
subcontractors under a cost-reimbursement contract. If the inclusion of
the paid freight bills/invoices, CBL\'s, passenger coupons, and
supporting documents for any subcontractor in the shipment is not
practicable, the documents may be forwarded to GSA in a separate
package.

\(c\) Any original transportation bills or other documents requested by
GSA shall be forwarded promptly by the Contractor to GSA. The Contractor
shall ensure that the name of the contracting agency is stamped or
written on the face of the bill before sending it to GSA.

\(d\) A statement prepared in duplicate by the Contractor shall
accompany each shipment of transportation documents. GSA will
acknowledge receipt of the shipment by signing and returning the copy of
the statement. The statement shall show-

\(1\) The name and address of the Contractor;

\(2\) The contract number including any alpha-numeric prefix identifying
the contracting office;

\(3\) The name and address of the contracting office;

\(4\) The total number of bills submitted with the statement; and

\(5\) A listing of the respective amounts paid or, in lieu of such
listing, an adding machine tape of the amounts paid showing the
Contractor\'s voucher or check numbers.

(End of clause)

## I.10 CLAUSES INCORPORATED BY REFERENCE (FAR 52.252-2) (FEB 1998) 

This contract incorporates one or more clauses by reference, with the
same force and effect as if they were given in full text. Upon request,
the Contracting Officer will make their full text available. Also, the
full text of a clause may be accessed electronically at these addresses:

http://www.arnet.gov/far/

http://www.hq.nasa.gov/office/procurement/regs/nfstoc.htm

(End of clause)

**I. 11 SECURITY CLASSIFICATION REQUIREMENTS (NASA 1852.204-75) (SEPT
1989)**

Performance under this contract will involve access to and/or generation
of classified information, work in a security area, or both, up to the
level of **SECRET**. See Federal Acquisition Regulation clause 52.204-2
in this contract and DD Form 254, Contract Security Classification
Specification, Attachment J-5.

(End of clause)

## I.12 SECURITY REQUIREMENTS FOR UNCLASSIFIED INFORMATION TECHNOLOGY RESOURCES (NASA 1852.204-76) (JUL 2002)

a\) The Contractor shall be responsible for Information Technology
security for all systems connected to a NASA network or operated by the
Contractor for NASA, regardless of location. This clause is applicable
to all or any part of the contract that includes information technology
resources or services in which the Contractor must have physical or
electronic access to NASA\'s sensitive information contained in
unclassified systems that directly support the mission of the Agency.
This includes information technology, hardware, software, and the
management, operation, maintenance, programming, and system
administration of computer systems, networks, and telecommunications
systems. Examples of tasks that require security provisions include:

\(1\) Computer control of spacecraft, satellites, or aircraft or their
payloads;

\(2\) Acquisition, transmission or analysis of data owned by NASA with
significant replacement cost should the contractor\'s copy be corrupted;
and

\(3\) Access to NASA networks or computers at a level beyond that
granted the general public, e.g. bypassing a firewall.

 

\(b\) The Contractor shall provide, implement, and maintain an IT
Security Plan. This plan shall describe the processes and procedures
that will be followed to ensure appropriate security of IT resources
that are developed, processed, or used under this contract. The plan
shall describe those parts of the contract to which this clause applies.
The Contractor\'s IT Security Plan shall be compliant with Federal laws
that include, but are not limited to, the Computer Security Act of 1987
(40 U.S.C. 1441 et seq.) and the Government Information Security Reform
Act of 2000. The plan shall meet IT security requirements in accordance
with Federal and NASA policies and procedures that include, but are not
limited to:

\(1\) OMB Circular A-130, Management of Federal Information Resources,
Appendix III, Security of Federal Automated Information Resources;

\(2\) NASA Procedures and Guidelines (NPG) 2810.1, Security of
Information Technology; and

\(3\) Chapter 3 of NPG 1620.1, NASA Security Procedures and Guidelines.

 

\(c\) Within thirty (30) calendar days after contract award, the
contractor shall submit for NASA approval an IT Security Plan. This plan
must be consistent with and further detail the approach contained in the
offeror\'s proposal or sealed bid that resulted in the award of this
contract and in compliance with the requirements stated in this clause.
The plan, as approved by the Contracting Officer, shall be incorporated
into the contract as a compliance document.

 

(d)(1) Contractor personnel requiring privileged access or limited
privileged access to systems operated by the Contractor for NASA or
interconnected to a NASA network shall be screened at an appropriate
level in accordance with NPG 2810.1, Section 4.5; NPG 1620.1, Chapter 3;
and paragraph (d)(2) of this clause. Those Contractor personnel with
non-privileged access do not require personnel screening. NASA shall
provide screening using standard personnel screening National Agency
Check (NAC) forms listed in paragraph (d)(3) of this clause, unless
contractor screening in accordance with paragraph (d)(4) is approved.
The Contractor shall submit the required forms to the NASA Center Chief
of Security (CCS) within fourteen (14) days after contract award or
assignment of an individual to a position requiring screening. The forms
may be obtained from the CCS. At the option of the government, interim
access may be granted pending completion of the NAC.

\(2\) Guidance for selecting the appropriate level of screening is based
on the risk of adverse impact to NASA missions. NASA defines three
levels of risk for which screening is required (IT-1 has the highest
level of risk):

> \(i\) IT-1\--Individuals having privileged access or limited
> privileged access to systems whose misuse can cause very serious
> adverse impact to NASA missions. These systems include, for example,
> those that can transmit commands directly modifying the behavior of
> spacecraft, satellites or aircraft.
>
> \(ii\) IT-2\--Individuals having privileged access or limited
> privileged access to systems whose misuse can cause serious adverse
> impact to NASA missions. These systems include, for example, those
> that can transmit commands directly modifying the behavior of payloads
> on spacecraft, satellites or aircraft; and those that contain the
> primary copy of \"level 1\" data whose cost to replace exceeds one
> million dollars.
>
> \(iii\) IT-3\--Individuals having privileged access or limited
> privileged access to systems whose misuse can cause significant
> adverse impact to NASA missions. These systems include, for example,
> those that interconnect with a NASA network in a way that exceeds
> access by the general public, such as bypassing firewalls; and systems
> operated by the contractor for NASA whose function or data has
> substantial cost to replace, even if these systems are not
> interconnected with a NASA network.

\(3\) Screening for individuals shall employ forms appropriate for the
level of risk as follows:

> \(i\) IT-1: Fingerprint Card (FC) 258 and Standard Form (SF) 85P,
> Questionnaire for Public Trust Positions;
>
> \(ii\) IT-2: FC 258 and SF 85, Questionnaire for Non-Sensitive
> Positions; and
>
> \(iii\) IT-3: NASA Form 531, Name Check, and FC 258.

\(4\) The Contracting Officer may allow the Contractor to conduct its
own screening of individuals requiring privileged access or limited
privileged access provided the Contractor can demonstrate that the
procedures used by the Contractor are equivalent to NASA\'s personnel
screening procedures. As used here, equivalent includes a check for
criminal history, as would be conducted by NASA, and completion of a
questionnaire covering the same information as would be required by
NASA.

\(5\) Screening of contractor personnel may be waived by the Contracting
Officer for those individuals who have proof of\--

> \(i\) Current or recent national security clearances (within last

three years);

> \(ii\) Screening conducted by NASA within last three years; or
>
> \(iii\) Screening conducted by the Contractor, within last three
> years, that is equivalent to the NASA personnel screening procedures
> as approved by the Contracting Officer under paragraph (d)(4) of this
> clause.

 

\(e\) The Contractor shall ensure that its employees, in performance of
the contract, receive annual IT security training in NASA IT Security
policies, procedures, computer ethics, and best practices in accordance
with NPG 2810.1, Section 4.3 requirements. The contractor may use
web-based training available from NASA to meet this requirement.

 

\(f\) The Contractor shall afford NASA, including the Office of
Inspector General, access to the Contractor\'s and subcontractors\'
facilities, installations, operations, documentation, databases and
personnel used in performance of the contract. Access shall be provided
to the extent required to carry out a program of IT inspection,
investigation and audit to safeguard against threats and hazards to the
integrity, availability and confidentiality of NASA data or to the
function of computer systems operated on behalf of NASA, and to preserve
evidence of computer crime.

 

\(g\) The Contractor shall incorporate the substance of this clause in
all subcontracts that meet the conditions in paragraph (a) of this
clause.

(End of clause)

I.13 OMBUDSMAN (NASA 1852.215-84) (JUNE 2000)

\(a\) An ombudsman has been appointed to hear and facilitate the
resolution of concerns from offerors, potential offerors, and
contractors during the preaward and postaward phases of this
acquisition. When requested, the ombudsman will maintain strict
confidentiality as to the source of the concern. The existence of the
ombudsman is not to diminish the authority of the contracting officer,
the Source Evaluation Board, or the selection official. Further, the
ombudsman does not participate in the evaluation of proposals, the
source selection process, or the adjudication of formal contract
disputes. Therefore, before consulting with an ombudsman, interested
parties must first address their concerns, issues, disagreements, and/or
recommendations to the contracting officer for resolution.

\(b\) If resolution cannot be made by the contracting officer,
interested parties may contact the installation ombudsman, Debra L.
Johnson, Attn: Mail Code BA, Lyndon B. Johnson Space Center, 2101 NASA
Parkway, Houston, TX 77058, 281-483-4157, facsimile 281-483-5100, email:
debra.l.johnson@nasa.gov. Concerns, issues, disagreements, and
recommendations which cannot be resolved at the installation may be
referred to the NASA ombudsman, the Director of the Contract Management
Division, at 202-358-0422, facsimile 202-358-3083, e-mail
robert.s.thompson@nasa.gov. Please do not contact the ombudsman to
request copies of the solicitation, verify offer due date, or clarify
technical requirements. Such inquiries shall be directed to the
Contracting Officer or as specified elsewhere in this document.

(End of Clause)

## I.14 MINIMUM INSURANCE COVERAGE (NASA 1852.228‑75) (OCT 1988)

The Contractor shall obtain and maintain insurance coverage as follows
for the performance of this contract:

\(a\) Worker\'s compensation and employer\'s liability insurance as
required by applicable Federal and state workers\' compensation and
occupational disease statutes. If occupational diseases are not
compensable under those statutes, they shall be covered under the
employer\'s liability section of the insurance policy, except when
contract operations are so commingled with the Contractor\'s commercial
operations that it would not be practical. The employer\'s liability
coverage shall be at least \$100,000, except in States with exclusive or
monopolistic funds that do not permit workers\' compensation to be
written by private carriers.

\(b\) Comprehensive general (bodily injury) liability insurance of at
least \$500,000 per occurrence.

\(c\) Motor vehicle liability insurance written on the comprehensive
form of policy which provides for bodily injury and property damage
liability covering the operation of all motor vehicles used in
connection with performing the contract. Policies covering motor
vehicles operated in the United States shall provide coverage of at
least \$200,000 per person and \$500,000 per occurrence for bodily
injury liability and \$20,000 per occurrence for property damage. The
amount of liability coverage on other policies shall be commensurate
with any legal requirements of the locality and sufficient to meet
normal and customary claims.

\(d\) Comprehensive general and motor vehicle liability policies shall
contain a provision worded as follows:

\"The insurance company waives any right of subrogation against the
United States of America which may arise by reason of any payment under
the policy.\"

\(e\) When aircraft are used in connection with performing the contract,
aircraft public and passenger liability insurance of at least \$200,000
per person and \$500,000 per occurrence for bodily injury, other than
passenger liability, and \$200,000 per occurrence for property damage.
Coverage for passenger liability bodily injury shall be at least
\$200,000 multiplied by the number of seats or passengers, whichever is
greater.

(End of clause)

<table>
<colgroup>
<col style="width: 3%" />
<col style="width: 2%" />
<col style="width: 0%" />
<col style="width: 4%" />
<col style="width: 5%" />
<col style="width: 5%" />
<col style="width: 4%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 3%" />
<col style="width: 1%" />
<col style="width: 8%" />
<col style="width: 0%" />
<col style="width: 12%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 1%" />
<col style="width: 6%" />
<col style="width: 0%" />
<col style="width: 5%" />
<col style="width: 12%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="7"><h1 id="standard-form-98">STANDARD FORM 98</h1></td>
<td colspan="18"><strong>NOTICE OF INTENTION TO MAKE</strong></td>
<td colspan="3">1. NOTICE NO.</td>
</tr>
<tr class="even">
<td colspan="7">January 1996</td>
<td colspan="18"><strong>A SERVICE CONTRACT AND RESPONSE TO
NOTICE</strong></td>
<td colspan="3"></td>
</tr>
<tr class="odd">
<td colspan="7"><strong>U.S. DEPARTMENT OF LABOR</strong></td>
<td colspan="18"></td>
<td colspan="3"><h3 id="section-4">25366</h3>
<p>Memorandum</p></td>
</tr>
<tr class="even">
<td colspan="7">EMPLOYMENT STANDARDS</td>
<td colspan="18"><em>(See Instructions on Reverse)</em></td>
<td colspan="3"></td>
</tr>
<tr class="odd">
<td colspan="7">ADMINISTRATION</td>
<td colspan="18"></td>
<td colspan="3"></td>
</tr>
<tr class="even">
<td colspan="15"></td>
<td colspan="13">2. Estimated solicitation date <em>(use
numerals)</em></td>
</tr>
<tr class="odd">
<td colspan="15"><strong>MAIL TO:</strong></td>
<td colspan="13"></td>
</tr>
<tr class="even">
<td colspan="15"></td>
<td colspan="9">Month</td>
<td colspan="3">Day</td>
<td>Year</td>
</tr>
<tr class="odd">
<td colspan="15"><h4 id="administrator">Administrator</h4></td>
<td colspan="9"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="15"><p id="wage-and-hour-division" class="heading">Wage and
Hour Division</p></td>
<td colspan="13">3. Estimated date bids or proposals to be opened</td>
</tr>
<tr class="odd">
<td colspan="15"><p id="u.s.-department-of-labor" class="heading">U.S.
Department of Labor</p></td>
<td colspan="13">or negotiations begun <em>(use numerals)</em></td>
</tr>
<tr class="even">
<td colspan="15"><p id="washington-dc-20210" class="heading">Washington,
DC 20210</p></td>
<td colspan="9">Month</td>
<td colspan="3">Day</td>
<td>Year</td>
</tr>
<tr class="odd">
<td colspan="15"></td>
<td colspan="9"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="15"></td>
<td colspan="13">4. Date contract performance to begin <em>(use
numerals)</em></td>
</tr>
<tr class="odd">
<td colspan="15"></td>
<td colspan="13">Extension</td>
</tr>
<tr class="even">
<td colspan="15"></td>
<td colspan="9">Month</td>
<td colspan="3">Day</td>
<td>Year</td>
</tr>
<tr class="odd">
<td colspan="15"></td>
<td colspan="9">01</td>
<td colspan="3">01</td>
<td>05</td>
</tr>
<tr class="even">
<td colspan="13">5. PLACE(S) OF PERFORMANCE</td>
<td colspan="15">6. SERVICES TO BE PERFORMED <em>(describe)</em></td>
</tr>
<tr class="odd">
<td colspan="13"></td>
<td colspan="15"></td>
</tr>
<tr class="even">
<td colspan="13"><h2 id="harris-county-tx">Harris County, TX</h2></td>
<td colspan="15">IV: Mission Support Operations Contract</td>
</tr>
<tr class="odd">
<td colspan="13">El Paso County, TX</td>
<td colspan="15">WD Period 01/01/05 to 12/31/05</td>
</tr>
<tr class="even">
<td colspan="13"></td>
<td colspan="15">NAS 9-03056</td>
</tr>
<tr class="odd">
<td colspan="13"></td>
<td colspan="15"></td>
</tr>
<tr class="even">
<td colspan="28">7. INFORMATION ABOUT PERFORMANCE</td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td><strong>A.</strong></td>
<td colspan="2"><h6 id="x">X</h6></td>
<td colspan="6">Services now performed by a</td>
<td><strong>B.</strong></td>
<td></td>
<td colspan="7">Services now performed by Federal</td>
<td colspan="4"><strong>C.</strong></td>
<td></td>
<td colspan="5">Services not presently being</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="2"></td>
<td colspan="6">contractor</td>
<td></td>
<td></td>
<td colspan="7">employees</td>
<td colspan="4"></td>
<td></td>
<td colspan="5">performed</td>
</tr>
<tr class="even">
<td colspan="28">8. IF BOX A IN ITEM 7 IS MARKED, COMPLETE ITEM 8 AS
APPLICABLE</td>
</tr>
<tr class="odd">
<td colspan="14">a. Name and address of incumbent contractor</td>
<td colspan="14">b. Number(s) of any wage determination(s) in
incumbent’s contract</td>
</tr>
<tr class="even">
<td colspan="14">Lockheed Martin Space Operations</td>
<td colspan="14">WD 94-2516</td>
</tr>
<tr class="odd">
<td colspan="14">595 Gemini</td>
<td colspan="14"></td>
</tr>
<tr class="even">
<td colspan="14">Houston, TX 77058</td>
<td colspan="14"></td>
</tr>
<tr class="odd">
<td colspan="16">c. Name(s) of union(s) if services are being performed
under collective bargaining</td>
<td colspan="12"><strong>RESPONSE TO NOTICE</strong></td>
</tr>
<tr class="even">
<td colspan="16">agreement(s). <em><strong>Important:</strong></em>
Attach copies of current applicable collective</td>
<td colspan="12"><em>(by Department of Labor)</em></td>
</tr>
<tr class="odd">
<td colspan="16">bargaining agreements</td>
<td colspan="12"></td>
</tr>
<tr class="even">
<td colspan="16"></td>
<td><strong>A.</strong></td>
<td colspan="3">X</td>
<td colspan="8">The attached wage determination(s)</td>
</tr>
<tr class="odd">
<td colspan="16">None</td>
<td colspan="2"></td>
<td colspan="10">listed below apply to procurement.</td>
</tr>
<tr class="even">
<td colspan="16"></td>
<td colspan="12">WD 94-2516 Rev 24</td>
</tr>
<tr class="odd">
<td colspan="16"></td>
<td colspan="12">WD 94-2512 Rev 21</td>
</tr>
<tr class="even">
<td colspan="16">9. OFFICIAL SUBMITTING NOTICE</td>
<td colspan="12"></td>
</tr>
<tr class="odd">
<td colspan="12">SIGNED:</td>
<td colspan="4">DATE</td>
<td colspan="2"><strong>B.</strong></td>
<td colspan="3"></td>
<td colspan="7">As of this date, no wage determination</td>
</tr>
<tr class="even">
<td colspan="12"><mark>Original Signed by Connie R.
Pritchard</mark></td>
<td colspan="4"><mark>10/18/04</mark></td>
<td colspan="2"></td>
<td colspan="10">applicable to the specified locality and</td>
</tr>
<tr class="odd">
<td colspan="12"></td>
<td colspan="4"></td>
<td colspan="2"></td>
<td colspan="10">classes of employees is in effect.</td>
</tr>
<tr class="even">
<td colspan="12">TYPE OR PRINT NAME</td>
<td colspan="4">TELEPHONE NO.</td>
<td colspan="12"></td>
</tr>
<tr class="odd">
<td colspan="12">Connie R. Pritchard</td>
<td colspan="4">281-483-4121</td>
<td colspan="2"><strong>C.</strong></td>
<td colspan="2"></td>
<td colspan="8">From information supplied, the Service</td>
</tr>
<tr class="even">
<td colspan="12">Contract Labor Relations Officer</td>
<td colspan="4"></td>
<td colspan="2"></td>
<td colspan="10">Contract Act does not apply <em>(see attached</em></td>
</tr>
<tr class="odd">
<td colspan="16">10. TYPE OR PRINT NAME AND TITLE OF PERSON TO WHOM
RESPONSE IS TO BE SENT</td>
<td colspan="2"></td>
<td colspan="10"><em>explanation).</em></td>
</tr>
<tr class="even">
<td colspan="16">AND NAME AND ADDRESS OF DEPARTMENT OR AGENCY, BUREAU,
DIVISION, ETC.</td>
<td colspan="2"></td>
<td colspan="3"></td>
<td colspan="7"></td>
</tr>
<tr class="odd">
<td colspan="16"></td>
<td colspan="2"><strong>D.</strong></td>
<td colspan="3"></td>
<td colspan="7">Notice returned for additional information</td>
</tr>
<tr class="even">
<td colspan="16"></td>
<td colspan="2"></td>
<td colspan="10"><em>(see attached explanation)</em></td>
</tr>
<tr class="odd">
<td colspan="16"><h6 id="nasa-johnson-space-center">NASA Johnson Space
Center</h6></td>
<td colspan="2"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td colspan="16"><strong>Connie R. Pritchard, Mail Code
BA2</strong></td>
<td colspan="12">Signed:__________________________________</td>
</tr>
<tr class="odd">
<td colspan="16"><strong>2101 NASA Parkway</strong></td>
<td colspan="12"><em>(U.S. Department of Labor)</em></td>
</tr>
<tr class="even">
<td colspan="16"><strong>Houston, TX 77058</strong></td>
<td colspan="12"></td>
</tr>
<tr class="odd">
<td colspan="16"></td>
<td colspan="3"></td>
<td colspan="9">_______________________________________</td>
</tr>
<tr class="even">
<td colspan="16"></td>
<td colspan="12"><em>(Date)</em></td>
</tr>
<tr class="odd">
<td colspan="16">98-103</td>
<td colspan="10">COMPUTER-GENERATED</td>
<td colspan="2">1/96</td>
</tr>
</tbody>
</table>

+------------------+-----------------------+---------+----------------+
| STANDARD FORM    | NOTICE OF INTENTION   |         | 11\. Notice    |
| 98a              | TO MAKE               |         | No.            |
|                  |                       |         |                |
| February 1973    | A SERVICE CONTRACT    |         | NASA           |
|                  | AND RESPONSE TO       |         |                |
| U.S. DEPARTMENT  | NOTICE                |         | **25366** MOU  |
| OF LABOR         |                       |         |                |
|                  | (Attachment A)        |         |                |
| Employment       |                       |         |                |
| Standards        |                       |         |                |
| Administration   |                       |         |                |
+------------------+-----------------------+---------+----------------+
| 12\. CLASSES OF  |                       | 13\.    | 14\. HOURLY    |
| SERVICE          |                       | NUMBER  | WAGE RATE      |
| EMPLOYEES TO BE  |                       | OF      |                |
| EMPLOYED ON      |                       |         | THAT WOULD BE  |
| CONTRACT         |                       | EM      |                |
|                  |                       | PLOYEES | PAID IF        |
| Harris County,   |                       |         | FEDERALLY      |
| TX; 94-2516,     |                       | IN EACH |                |
| Occupations      |                       | CLASS   | EMPLOYED       |
| included in "SCA |                       |         |                |
| Directory of     |                       |         |                |
| Occupations"     |                       |         |                |
+------------------+-----------------------+---------+----------------+
|                  |                       |         |                |
+------------------+-----------------------+---------+----------------+
| Secretary, I     |                       | 2       | GS-4 \$12.70   |
+------------------+-----------------------+---------+----------------+
| Secretary, II    |                       | 3       | GS-5 \$14.21   |
+------------------+-----------------------+---------+----------------+
| Secretary, III   |                       | 2       | GS-6 \$15.83   |
+------------------+-----------------------+---------+----------------+
| Secretary, IV    |                       | 1       | GS-7 \$17.60   |
+------------------+-----------------------+---------+----------------+
| Accounting       |                       | 1       | GS-4 \$12.70   |
| Clerk, III       |                       |         |                |
+------------------+-----------------------+---------+----------------+
| General Clerk, I |                       | 21      | GS-1 \$9.22    |
+------------------+-----------------------+---------+----------------+
| Computer         |                       | 1       | GS-4 \$12.70   |
| Operator, I      |                       |         |                |
+------------------+-----------------------+---------+----------------+
| Computer         |                       | 5       | GS-5 \$14.21   |
| Operator, II     |                       |         |                |
+------------------+-----------------------+---------+----------------+
| Computer         |                       | 3       | GS-6 \$15.83   |
| Operator, III    |                       |         |                |
+------------------+-----------------------+---------+----------------+
| Computer         |                       | 1       | GS-7 \$17.60   |
| Programmer, II   |                       |         |                |
+------------------+-----------------------+---------+----------------+
| Word Processor,  |                       | 1       | GS-5 \$14.21   |
| III              |                       |         |                |
+------------------+-----------------------+---------+----------------+
| Shipping &       |                       | 4       | WG-4 \$13.71   |
| Receiving Clerk  |                       |         |                |
+------------------+-----------------------+---------+----------------+
| Store Worker, I  |                       | 1       | WG-1 \$9.67    |
+------------------+-----------------------+---------+----------------+
| Electrician      |                       | 5       | WG-10 \$21.21  |
| Maintenance      |                       |         |                |
+------------------+-----------------------+---------+----------------+
| Engineering      |                       | 1       | GS-7 \$17.60   |
| Technician, IV   |                       |         |                |
+------------------+-----------------------+---------+----------------+
| Electronic       |                       | 28      | WG-8 \$18.95   |
| Technician,      |                       |         |                |
| Maint. I         |                       |         |                |
+------------------+-----------------------+---------+----------------+
| Electronic       |                       | 15      | WG-9 \$20.18   |
| Technician,      |                       |         |                |
| Maint. II        |                       |         |                |
+------------------+-----------------------+---------+----------------+
| Electronic       |                       | 7       | WG-10 \$21.21  |
| Technician,      |                       |         |                |
| Maint. III       |                       |         |                |
+------------------+-----------------------+---------+----------------+
|                  |                       |         |                |
+------------------+-----------------------+---------+----------------+
|                  |                       |         |                |
+------------------+-----------------------+---------+----------------+
| El Paso County,  |                       |         |                |
| TX; 94-2512,     |                       |         |                |
| Occupations      |                       |         |                |
| included in "SCA |                       |         |                |
| Directory of     |                       |         |                |
| Occupations"     |                       |         |                |
+------------------+-----------------------+---------+----------------+
|                  |                       |         |                |
+------------------+-----------------------+---------+----------------+
| General Clerk, I |                       | 6       | GS-1 \$8.30    |
+------------------+-----------------------+---------+----------------+
| Computer         |                       | 1       | GS-6 \$14.26   |
| Operator, III    |                       |         |                |
+------------------+-----------------------+---------+----------------+
|                  |                       |         |                |
+------------------+-----------------------+---------+----------------+

REGISTER OF WAGE DETERMINATIONS UNDER U.S. DEPARTMENT OF LABOR

THE SERVICE CONTRACT ACT EMPLOYMENT STANDARDS

DIVISION

WAGE AND HOUR DIVISION

WASHINGTON D.C. 20210

By Direction of the Secretary of Labor

Wage Determination No.: 1994-2516

William W. Gross Division of Revision No.: 24

Director Wage Determinations Date Of Last Revision: 08/10/2004

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

State: Texas

Area: Texas Counties of Austin, Brazoria, Chambers, Colorado, Fort Bend,
Galveston,

Grimes, Harris, Houston, Jackson, Lavaca, Liberty, Madison, Matagorda,
Montgomery,

San Jacinto, Trinity, Walker, Waller, Washington, Wharton

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

\*\*Fringe Benefits Required Follow the Occupational Listing\*\*

# OCCUPATION CODE - TITLE MINIMUM WAGE RATE

**01000 - Administrative Support and Clerical Occupations**

01011 - Accounting Clerk I 11.45

01012 - Accounting Clerk II 12.35

01013 - Accounting Clerk III 13.86

01014 - Accounting Clerk IV 15.29

01030 - Court Reporter 17.73

01050 - Dispatcher, Motor Vehicle 14.00

01060 - Document Preparation Clerk 11.66

01070 - Messenger (Courier) 9.87

01090 - Duplicating Machine Operator 11.01

01110 - Film/Tape Librarian 11.50

01115 - General Clerk I 9.23

01116 - General Clerk II 10.01

01117 - General Clerk III 12.97

01118 - General Clerk IV 14.88

01120 - Housing Referral Assistant 19.36

01131 - Key Entry Operator I 10.76

01132 - Key Entry Operator II 13.76

01191 - Order Clerk I 12.51

01192 - Order Clerk II 14.27

01261 - Personnel Assistant (Employment) I 12.28

01262 - Personnel Assistant (Employment) II 13.79

01263 - Personnel Assistant (Employment) III 16.50

01264 - Personnel Assistant (Employment) IV 17.63

01270 - Production Control Clerk 18.50

01290 - Rental Clerk 14.34

01300 - Scheduler, Maintenance 14.67

01311 - Secretary I 14.67

01312 - Secretary II 17.73

01313 - Secretary III 19.36

01314 - Secretary IV 22.76

01315 - Secretary V 25.57

01320 - Service Order Dispatcher 13.30

01341 - Stenographer I 12.72

01342 - Stenographer II 15.12

01400 - Supply Technician 22.76

01420 - Survey Worker (Interviewer) 14.26

01460 - Switchboard Operator-Receptionist 10.88

01510 - Test Examiner 17.73

01520 - Test Proctor 17.73

01531 - Travel Clerk I 11.49

01532 - Travel Clerk II 12.39

01533 - Travel Clerk III 13.25

01611 - Word Processor I 11.45

01612 - Word Processor II 13.79

01613 - Word Processor III 16.27

**03000 - Automatic Data Processing Occupations**

03010 - Computer Data Librarian 13.18

03041 - Computer Operator I 13.26

03042 - Computer Operator II 14.61

03043 - Computer Operator III 16.59

03044 - Computer Operator IV 22.60

03045 - Computer Operator V 23.59

03071 - Computer Programmer I (1) 19.99

03072 - Computer Programmer II (1) 24.38

03073 - Computer Programmer III (1) 27.62

03074 - Computer Programmer IV (1) 27.62

03101 - Computer Systems Analyst I (1) 27.31

03102 - Computer Systems Analyst II (1) 27.62

03103 - Computer Systems Analyst III (1) 27.62

03160 - Peripheral Equipment Operator 12.36

**05000 - Automotive Service Occupations**

05005 - Automotive Body Repairer, Fiberglass 21.26

05010 - Automotive Glass Installer 19.86

05040 - Automotive Worker 19.15

05070 - Electrician, Automotive 20.76

05100 - Mobile Equipment Servicer 17.65

05130 - Motor Equipment Metal Mechanic 22.47

05160 - Motor Equipment Metal Worker 19.15

05190 - Motor Vehicle Mechanic 22.47

05220 - Motor Vehicle Mechanic Helper 16.93

05250 - Motor Vehicle Upholstery Worker 18.17

05280 - Motor Vehicle Wrecker 19.15

05310 - Painter, Automotive 20.76

05340 - Radiator Repair Specialist 20.96

05370 - Tire Repairer 14.40

05400 - Transmission Repair Specialist 23.06

**07000 - Food Preparation and Service Occupations**

(not set) - Food Service Worker 7.86

07010 - Baker 9.47

07041 - Cook I 8.52

07042 - Cook II 9.19

07070 - Dishwasher 7.74

07130 - Meat Cutter 12.19

07250 - Waiter/Waitress 7.51

**09000 - Furniture Maintenance and Repair Occupations**

09010 - Electrostatic Spray Painter 16.65

09040 - Furniture Handler 11.74

09070 - Furniture Refinisher 16.09

09100 - Furniture Refinisher Helper 13.74

09110 - Furniture Repairer, Minor 15.29

09130 - Upholsterer 16.65

**11030 - General Services and Support Occupations**

11030 - Cleaner, Vehicles 8.29

11060 - Elevator Operator 6.97

11090 - Gardener 11.04

11121 - House Keeping Aid I 6.86

11122 - House Keeping Aid II 6.97

11150 - Janitor 8.17

11210 - Laborer, Grounds Maintenance 8.86

11240 - Maid or Houseman 6.86

11270 - Pest Controller 11.80

11300 - Refuse Collector 8.29

11330 - Tractor Operator 10.40

11360 - Window Cleaner 8.92

**12000 - Health Occupations**

12020 - Dental Assistant 14.22

12040 - Emergency Medical Technician (EMT)/Paramedic

/Ambulance Driver 12.93

12071 - Licensed Practical Nurse I 13.52

12072 - Licensed Practical Nurse II 15.38

12073 - Licensed Practical Nurse III 16.71

12100 - Medical Assistant 11.91

12130 - Medical Laboratory Technician 13.63

12160 - Medical Record Clerk 12.72

12190 - Medical Record Technician 14.56

12221 - Nursing Assistant I 7.08

12222 - Nursing Assistant II 9.82

12223 - Nursing Assistant III 10.62

12224 - Nursing Assistant IV 12.40

12250 - Pharmacy Technician 13.10

12280 - Phlebotomist 13.30

12311 - Registered Nurse I 22.28

12312 - Registered Nurse II 27.45

12313 - Registered Nurse II, Specialist 29.16

12314 - Registered Nurse III 34.51

12315 - Registered Nurse III, Anesthetist 34.51

12316 - Registered Nurse IV 39.53

**13000 - Information and Arts Occupations**

13002 - Audiovisual Librarian 18.40

13011 - Exhibits Specialist I 19.30

13012 - Exhibits Specialist II 24.74

13013 - Exhibits Specialist III 28.94

13041 - Illustrator I 17.60

13042 - Illustrator II 22.56

13043 - Illustrator III 26.40

13047 - Librarian 21.17

13050 - Library Technician 12.96

13071 - Photographer I 13.93

13072 - Photographer II 17.60

13073 - Photographer III 22.56

13074 - Photographer IV 26.40

13075 - Photographer V 30.06

**15000 - Laundry, Dry Cleaning, Pressing and Related Occupations**

15010 - Assembler 7.93

15030 - Counter Attendant 7.93

15040 - Dry Cleaner 10.15

15070 - Finisher, Flatwork, Machine 7.93

15090 - Presser, Hand 7.93

15100 - Presser, Machine, Drycleaning 7.93

15130 - Presser, Machine, Shirts 7.93

15160 - Presser, Machine, Wearing Apparel, Laundry 7.93

15190 - Sewing Machine Operator 10.75

15220 - Tailor 11.56

15250 - Washer, Machine 8.67

**19000 - Machine Tool Operation and Repair Occupations**

19010 - Machine-Tool Operator (Toolroom) 16.65

19040 - Tool and Die Maker 19.20

**21000 - Material Handling and Packing Occupations**

21010 - Fuel Distribution System Operator 16.33

21020 - Material Coordinator 18.50

21030 - Material Expediter 18.50

21040 - Material Handling Laborer 12.26

21050 - Order Filler 10.53

21071 - Forklift Operator 12.84

21080 - Production Line Worker (Food Processing) 12.84

21100 - Shipping/Receiving Clerk 12.41

21130 - Shipping Packer 12.41

21140 - Store Worker I 9.51

21150 - Stock Clerk (Shelf Stocker; Store Worker II) 13.06

21210 - Tools and Parts Attendant 13.58

21400 - Warehouse Specialist 12.84

**23000 - Mechanics and Maintenance and Repair Occupations**

23010 - Aircraft Mechanic 21.09

23040 - Aircraft Mechanic Helper 16.43

23050 - Aircraft Quality Control Inspector 22.02

23060 - Aircraft Servicer 18.28

23070 - Aircraft Worker 19.26

23100 - Appliance Mechanic 16.65

23120 - Bicycle Repairer 13.91

23125 - Cable Splicer 19.51

23130 - Carpenter, Maintenance 17.01

23140 - Carpet Layer 15.92

23160 - Electrician, Maintenance 23.18

23181 - Electronics Technician, Maintenance I 14.70

23182 - Electronics Technician, Maintenance II 19.02

23183 - Electronics Technician, Maintenance III 22.33

23260 - Fabric Worker 15.00

23290 - Fire Alarm System Mechanic 17.43

23310 - Fire Extinguisher Repairer 14.40

23340 - Fuel Distribution System Mechanic 19.17

23370 - General Maintenance Worker 15.46

23400 - Heating, Refrigeration and Air Conditioning Mechanic 17.43

23430 - Heavy Equipment Mechanic 17.43

23440 - Heavy Equipment Operator 17.43

23460 - Instrument Mechanic 17.43

23470 - Laborer 9.70

23500 - Locksmith 16.65

23530 - Machinery Maintenance Mechanic 19.81

23550 - Machinist, Maintenance 20.16

23580 - Maintenance Trades Helper 13.58

23640 - Millwright 19.02

23700 - Office Appliance Repairer 16.65

23740 - Painter, Aircraft 18.32

23760 - Painter, Maintenance 16.65

23790 - Pipefitter, Maintenance 19.33

23800 - Plumber, Maintenance 17.15

23820 - Pneudraulic Systems Mechanic 17.43

23850 - Rigger 17.43

23870 - Scale Mechanic 15.92

23890 - Sheet-Metal Worker, Maintenance 17.43

23910 - Small Engine Mechanic 15.92

23930 - Telecommunication Mechanic I 20.53

23931 - Telecommunication Mechanic II 21.44

23950 - Telephone Lineman 19.17

23960 - Welder, Combination, Maintenance 17.43

23965 - Well Driller 17.43

23970 - Woodcraft Worker 17.43

23980 - Woodworker 9.64

**24000 - Personal Needs Occupations**

24570 - Child Care Attendant 9.68

24580 - Child Care Center Clerk 12.06

24600 - Chore Aid 6.28

24630 - Homemaker 15.41

**25000 - Plant and System Operation Occupations**

25010 - Boiler Tender 19.86

25040 - Sewage Plant Operator 17.00

25070 - Stationary Engineer 19.86

25190 - Ventilation Equipment Tender 14.33

25210 - Water Treatment Plant Operator 16.65

**27000 - Protective Service Occupations**

(not set) - Police Officer 20.86

27004 - Alarm Monitor 12.98

27006 - Corrections Officer 18.04

27010 - Court Security Officer 18.04

27040 - Detention Officer 18.04

27070 - Firefighter 17.70

27101 - Guard I 10.02

27102 - Guard II 17.90

**28000 - Stevedoring/Longshoremen Occupations**

28010 - Blocker and Bracer 15.62

28020 - Hatch Tender 15.62

28030 - Line Handler 15.62

28040 - Stevedore I 14.61

28050 - Stevedore II 16.63

**29000 - Technical Occupations**

21150 - Graphic Artist 23.11

29010 - Air Traffic Control Specialist, Center (2) 33.86

29011 - Air Traffic Control Specialist, Station (2) 23.35

29012 - Air Traffic Control Specialist, Terminal (2) 25.71

29023 - Archeological Technician I 19.34

29024 - Archeological Technician II 21.66

29025 - Archeological Technician III 26.79

29030 - Cartographic Technician 27.31

29035 - Computer Based Training (CBT) Specialist/ Instructor 25.70

29040 - Civil Engineering Technician 24.82

29061 - Drafter I 15.37

29062 - Drafter II 15.85

29063 - Drafter III 20.90

29064 - Drafter IV 26.79

29081 - Engineering Technician I 15.08

29082 - Engineering Technician II 18.74

29083 - Engineering Technician III 21.81

29084 - Engineering Technician IV 27.69

29085 - Engineering Technician V 36.15

29086 - Engineering Technician VI 41.10

29090 - Environmental Technician 24.76

29100 - Flight Simulator/Instructor (Pilot) 32.45

29160 - Instructor 23.47

29210 - Laboratory Technician 17.97

29240 - Mathematical Technician 28.04

29361 - Paralegal/Legal Assistant I 17.80

29362 - Paralegal/Legal Assistant II 21.38

29363 - Paralegal/Legal Assistant III 26.62

29364 - Paralegal/Legal Assistant IV 29.59

29390 - Photooptics Technician 26.79

29480 - Technical Writer 23.21

29491 - Unexploded Ordnance (UXO) Technician I 21.52

29492 - Unexploded Ordnance (UXO) Technician II 26.04

29493 - Unexploded Ordnance (UXO) Technician III 31.21

29494 - Unexploded (UXO) Safety Escort 21.52

29495 - Unexploded (UXO) Sweep Personnel 21.52

29620 - Weather Observer, Senior (3) 21.81

29621 - Weather Observer, Combined Upper Air and

Surface Programs (3) 17.99

29622 - Weather Observer, Upper Air 17.99

**31000 - Transportation/ Mobile Equipment Operation Occupations**

31030 - Bus Driver 14.48

31260 - Parking and Lot Attendant 7.68

31290 - Shuttle Bus Driver 11.52

31300 - Taxi Driver 8.81

31361 - Truckdriver, Light Truck 11.52

31362 - Truckdriver, Medium Truck 14.97

31363 - Truckdriver, Heavy Truck 16.00

31364 - Truckdriver, Tractor-Trailer 16.00

**99000 - Miscellaneous Occupations**

99020 - Animal Caretaker 8.21

99030 - Cashier 8.41

99041 - Carnival Equipment Operator 9.72

99042 - Carnival Equipment Repairer 10.22

99043 - Carnival Worker 7.50

99050 - Desk Clerk 10.65

99095 - Embalmer 19.59

99300 - Lifeguard 11.31

99310 - Mortician 23.71

99350 - Park Attendant (Aide) 14.21

99400 - Photofinishing Worker (Photo Lab Tech., Darkroom Tech) 9.48

99500 - Recreation Specialist 14.74

99510 - Recycling Worker 12.23

99610 - Sales Clerk 10.53

99620 - School Crossing Guard (Crosswalk Attendant) 8.29

99630 - Sport Official 10.43

99658 - Survey Party Chief (Chief of Party) 18.11

99659 - Surveying Technician (Instr. Person/Surveyor Asst./Instr.) 15.66

99660 - Surveying Aide 12.40

99690 - Swimming Pool Operator 13.10

99720 - Vending Machine Attendant 10.91

99730 - Vending Machine Repairer 13.10

99740 - Vending Machine Repairer Helper 11.19

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

ALL OCCUPATIONS LISTED ABOVE RECEIVE THE FOLLOWING BENEFITS:

HEALTH & WELFARE: Life, accident, and health insurance plans, sick
leave, pension plans, civic and personal leave, severance pay, and
savings and thrift plans. Minimum employer contributions costing an
average of \$2.59 per hour computed on the basis of all hours worked by
service employees employed on the contract.

VACATION: 2 weeks paid vacation after 1 year of service with a
contractor or successor; 3 weeks after 5 years, and 4 weeks after 15
years. Length of service includes the whole span of continuous service
with the present contractor or successor, wherever employed, and with
the predecessor contractors in the performance of similar work at the
same Federal facility. (Reg. 29 CFR 4.173)

HOLIDAYS: A minimum of ten paid holidays per year: New Year\'s Day,
Martin Luther King Jr.\'s Birthday, Washington\'s Birthday, Memorial
Day, Independence Day, Labor Day, Columbus Day, Veterans\' Day,
Thanksgiving Day, and Christmas Day. (A contractor may substitute for
any of the named holidays another day off with pay in accordance with a
plan communicated to the employees involved.) (See 29 CFR 4.174)

THE OCCUPATIONS WHICH HAVE PARENTHESES AFTER THEM RECEIVE THE FOLLOWING
BENEFITS (as numbered):

1\) Does not apply to employees employed in a bona fide executive,
administrative, or professional capacity as defined and delineated in 29
CFR 541. (See CFR 4.156)

2\) APPLICABLE TO AIR TRAFFIC CONTROLLERS ONLY - NIGHT DIFFERENTIAL: An
employee is entitled to pay for all work performed between the hours of
6:00 P.M. and 6:00 A.M. at the rate of basic pay plus a night pay
differential amounting to 10 percent of the rate of basic pay.

3\) WEATHER OBSERVERS - NIGHT PAY & SUNDAY PAY: If you work at night as
part of a regular tour of duty, you will earn a night differential and
receive an additional 10% of basic pay for any hours worked between 6pm
and 6am. If you are a full-time employed (40 hours a week) and Sunday is
part of your regularly scheduled workweek, you are paid at your rate of
basic pay plus a Sunday premium of 25% of your basic rate for each hour
of Sunday work which is not overtime (i.e. occasional work on Sunday
outside the normal tour of duty is considered overtime work).

HAZARDOUS PAY DIFFERENTIAL: An 8 percent differential is applicable to
employees employed in a position that represents a high degree of hazard
when working with or in close proximity to ordinance, explosives, and
incendiary materials. This includes work such as screening, blending,
dying, mixing, and pressing of sensitive ordance, explosives, and
pyrotechnic compositions such as lead azide, black powder and photoflash
powder. All dry-house activities involving propellants or explosives.
Demilitarization, modification, renovation, demolition, and maintenance
operations on sensitive ordnance, explosives and incendiary materials.
All operations involving regrading and cleaning of artillery ranges.

A 4 percent differential is applicable to employees employed in a
position that represents a low degree of hazard when working with, or in
close proximity to ordance, (or employees possibly adjacent to)
explosives and incendiary materials which involves potential injury such
as laceration of hands, face, or arms of the employee engaged in the
operation, irritation of the skin, minor burns and the like; minimal
damage to immediate or adjacent work area or equipment being used. All
operations involving, unloading, storage, and hauling of ordance,
explosive, and

incendiary ordnance material other than small arms ammunition. These
differentials are only applicable to work that has been specifically
designated by the agency for ordance, explosives, and incendiary
material differential pay.

\*\* UNIFORM ALLOWANCE \*\*

If employees are required to wear uniforms in the performance of this
contract (either by the terms of the Government contract, by the
employer, by the state or local law, etc.), the cost of furnishing such
uniforms and maintaining (by laundering or dry cleaning) such uniforms
is an expense that may not be borne by an employee where such cost
reduces the hourly rate below that required by the wage determination.
The Department of Labor will accept payment in accordance with the
following standards as compliance:

The contractor or subcontractor is required to furnish all employees
with an adequate number of uniforms without cost or to reimburse
employees for the actual cost of the uniforms. In addition, where
uniform cleaning and maintenance is made the responsibility of the
employee, all contractors and subcontractors subject to this wage
determination shall (in the absence of a bona fide collective bargaining
agreement providing for a different amount, or the furnishing of
contrary affirmative proof as to the actual cost), reimburse all
employees for such cleaning and maintenance at a rate of \$3.35 per week
(or \$.67 cents per day). However, in those instances where the uniforms
furnished are made of \"wash and wear\" materials, may be routinely
washed and dried with other personal garments, and do not require any
special treatment such as dry cleaning, daily washing, or commercial
laundering in order to meet the cleanliness or appearance standards set
by the terms of the Government contract, by the contractor, by law, or
by the nature of the work, there is no requirement that employees be
reimbursed for uniform maintenance costs.

\*\* NOTES APPLYING TO THIS WAGE DETERMINATION \*\*

Under the policy and guidance contained in All Agency Memorandum No.
159, the Wage and Hour Division does not recognize, for section 4(c)
purposes, prospective wage rates and fringe benefit provisions that are
effective only upon such contingencies as \"approval of Wage and Hour,
issuance of a wage determination, incorporation of the wage
determination in the contract, adjusting the contract price, etc.\" (The
relevant CBA section) in the collective bargaining agreement between
(the parties) contains contingency language that Wage and Hour does not
recognize as reflecting \"arm\'s length negotiation\" under section 4(c)
of the Act and 29 C.F.R. 5.11(a) of the regulations. This wage
determination therefore reflects the actual CBA wage rates and fringe
benefits paid under the predecessor contract.

Source of Occupational Title and Descriptions:

The duties of employees under job titles listed are those described in
the \"Service Contract Act Directory of Occupations,\" Fourth Edition,
January 1993, as amended by the Third Supplement, dated March 1997,
unless otherwise indicated. This publication may be obtained from the
Superintendent of Documents, at 202-783-3238, or by writing to the
Superintendent of Documents, U.S. Government Printing Office,
Washington, D.C. 20402. Copies of specific job descriptions may also be
obtained from the appropriate contracting officer.

REQUEST FOR AUTHORIZATION OF ADDITIONAL CLASSIFICATION AND WAGE RATE
{Standard Form 1444 (SF 1444)}

Conformance Process:

The contracting officer shall require that any class of service employee
which is not listed herein and which is to be employed under the
contract (i.e., the work to be performed is not performed by any
classification listed in the wage determination), be classified by the
contractor so as to provide a reasonable relationship (i.e., appropriate
level of skill comparison) between such unlisted classifications and the
classifications listed in the wage determination. Such conformed classes
of employees shall be paid the monetary wages and furnished the fringe
benefits as are determined. Such conforming process shall be initiated
by the contractor prior to the performance of contract work by such
unlisted class(es) of employees. The conformed classification, wage
rate, and/or fringe benefits shall be retroactive to the commencement
date of the contract. {See Section 4.6 (C)(vi)} When multiple wage
determinations are included in a contract, a separate SF 1444 should be
prepared for each wage determination to which a class(es) is to be
conformed.

The process for preparing a conformance request is as follows:

1\) When preparing the bid, the contractor identifies the need for a
conformed occupation) and computes a proposed rate).

2\) After contract award, the contractor prepares a written report
listing in order proposed classification title), a Federal grade
equivalency (FGE) for each proposed classification), job description),
and rationale for proposed wage rate), including information regarding
the agreement or disagreement of the authorized representative of the
employees involved, or where there is no authorized representative, the
employees themselves. This report should be submitted to the contracting
officer no later than 30 days after such unlisted class(es) of employees
performs any contract work.

3\) The contracting officer reviews the proposed action and promptly
submits a report of the action, together with the agency\'s
recommendations and pertinent information including the position of the
contractor and the employees, to the Wage and Hour Division, Employment
Standards Administration, U.S. Department of Labor, for review. (See
section 4.6(b)(2) of Regulations 29 CFR Part 4).

4\) Within 30 days of receipt, the Wage and Hour Division approves,
modifies, or disapproves the action via transmittal to the agency
contracting officer, or notifies the contracting officer that additional
time will be required to process the request.

5\) The contracting officer transmits the Wage and Hour decision to the
contractor.

6\) The contractor informs the affected employees.

Information required by the Regulations must be submitted on SF 1444 or
bond paper.

When preparing a conformance request, the \"Service Contract Act
Directory of

Occupations\" (the Directory) should be used to compare job definitions
to insure that duties requested are not performed by a classification
already listed in the wage determination. Remember, it is not the job
title, but the required tasks that determine whether a class is included
in an established wage determination. Conformances may not be used to
artificially split, combine, or subdivide classifications listed in the
wage determination.

REGISTER OF WAGE DETERMINATIONS UNDER U.S. DEPARTMENT OF LABOR

THE SERVICE CONTRACT ACT EMPLOYMENT STANDARDS

DIVISION

WAGE AND HOUR DIVISION

WASHINGTON D.C. 20210

By Direction of the Secretary of Labor

Wage Determination No.: 1994-2512

William W.Gross Division of Revision No.: 21

Director Wage Determinations Date Of Last Revision: 07/21/2004

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

States: New Mexico, Texas

Area: New Mexico Counties of Chaves, Dona Ana, Eddy, Grant, Hidalgo,
Lincoln, Luna,

Otero, Sierra

Texas Counties of Culberson, El Paso, Hudspeth

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

\*\*Fringe Benefits Required Follow the Occupational Listing\*\*

# OCCUPATION CODE - TITLE MINIMUM WAGE RATE

**01000 - Administrative Support and Clerical Occupations**

01011 - Accounting Clerk I 8.60

01012 - Accounting Clerk II 10.14

01013 - Accounting Clerk III 13.49

01014 - Accounting Clerk IV 15.70

01030 - Court Reporter 12.97

01050 - Dispatcher, Motor Vehicle 11.97

01060 - Document Preparation Clerk 10.58

01070 - Messenger (Courier) 7.78

01090 - Duplicating Machine Operator 10.58

01110 - Film/Tape Librarian 10.00

01115 - General Clerk I 7.60

01116 - General Clerk II 9.17

01117 - General Clerk III 10.18

01118 - General Clerk IV 10.97

01120 - Housing Referral Assistant 14.58

01131 - Key Entry Operator I 8.50

01132 - Key Entry Operator II 10.05

01191 - Order Clerk I 8.89

01192 - Order Clerk II 11.20

01261 - Personnel Assistant (Employment) I 9.82

01262 - Personnel Assistant (Employment) II 11.56

01263 - Personnel Assistant (Employment) III 13.33

01264 - Personnel Assistant (Employment) IV 13.56

01270 - Production Control Clerk 13.14

01290 - Rental Clerk 8.85

01300 - Scheduler, Maintenance 10.15

01311 - Secretary I 10.15

01312 - Secretary II 12.97

01313 - Secretary III 14.58

01314 - Secretary IV 17.23

01315 - Secretary V 18.34

01320 - Service Order Dispatcher 8.85

01341 - Stenographer I 10.86

01342 - Stenographer II 11.65

01400 - Supply Technician 17.23

01420 - Survey Worker (Interviewer) 12.88

01460 - Switchboard Operator-Receptionist 8.55

01510 - Test Examiner 12.97

01520 - Test Proctor 12.97

01531 - Travel Clerk I 9.66

01532 - Travel Clerk II 10.33

01533 - Travel Clerk III 11.00

01611 - Word Processor I 9.37

01612 - Word Processor II 10.50

01613 - Word Processor III 13.41

**03000 - Automatic Data Processing Occupations**

03010 - Computer Data Librarian 8.94

03041 - Computer Operator I 9.49

03042 - Computer Operator II 12.77

03043 - Computer Operator III 14.80

03044 - Computer Operator IV 16.43

03045 - Computer Operator V 18.24

03071 - Computer Programmer I (1) 16.45

03072 - Computer Programmer II (1) 22.06

03073 - Computer Programmer III (1) 25.16

03074 - Computer Programmer IV (1) 27.62

03101 - Computer Systems Analyst I (1) 21.50

03102 - Computer Systems Analyst II (1) 25.79

03103 - Computer Systems Analyst III (1) 27.62

03160 - Peripheral Equipment Operator 9.49

**05000 - Automotive Service Occupations**

05005 - Automotive Body Repairer, Fiberglass 15.63

05010 - Automotive Glass Installer 13.69

05040 - Automotive Worker 13.69

05070 - Electrician, Automotive 14.67

05100 - Mobile Equipment Servicer 11.73

05130 - Motor Equipment Metal Mechanic 15.63

05160 - Motor Equipment Metal Worker 13.69

05190 - Motor Vehicle Mechanic 16.49

05220 - Motor Vehicle Mechanic Helper 10.75

05250 - Motor Vehicle Upholstery Worker 12.70

05280 - Motor Vehicle Wrecker 13.69

05310 - Painter, Automotive 14.67

05340 - Radiator Repair Specialist 13.69

05370 - Tire Repairer 11.33

05400 - Transmission Repair Specialist 15.63

**07000 - Food Preparation and Service Occupations**

(not set) - Food Service Worker 6.96

07010 - Baker 10.41

07041 - Cook I 9.48

07042 - Cook II 11.06

07070 - Dishwasher 6.37

07130 - Meat Cutter 10.41

07250 - Waiter/Waitress 7.02

**09000 - Furniture Maintenance and Repair Occupations**

09010 - Electrostatic Spray Painter 14.67

09040 - Furniture Handler 8.80

09070 - Furniture Refinisher 14.67

09100 - Furniture Refinisher Helper 10.75

09110 - Furniture Repairer, Minor 11.95

09130 - Upholsterer 14.67

**11030 - General Services and Support Occupations**

11030 - Cleaner, Vehicles 6.66

11060 - Elevator Operator 7.06

11090 - Gardener 10.70

11121 - House Keeping Aid I 6.68

11122 - House Keeping Aid II 7.25

11150 - Janitor 7.42

11210 - Laborer, Grounds Maintenance 8.02

11240 - Maid or Houseman 6.60

11270 - Pest Controller 10.97

11300 - Refuse Collector 6.88

11330 - Tractor Operator 9.82

11360 - Window Cleaner 8.34

12000 - Health Occupations

12020 - Dental Assistant 11.25

12040 - Emergency Medical Technician (EMT)/Paramedic

/Ambulance Driver 12.30

12071 - Licensed Practical Nurse I 12.12

12072 - Licensed Practical Nurse II 13.60

12073 - Licensed Practical Nurse III 15.21

12100 - Medical Assistant 10.35

12130 - Medical Laboratory Technician 12.33

12160 - Medical Record Clerk 9.77

12190 - Medical Record Technician 13.54

12221 - Nursing Assistant I 7.46

12222 - Nursing Assistant II 8.39

12223 - Nursing Assistant III 9.16

12224 - Nursing Assistant IV 10.27

12250 - Pharmacy Technician 12.19

12280 - Phlebotomist 12.29

12311 - Registered Nurse I 17.92

12312 - Registered Nurse II 21.94

12313 - Registered Nurse II, Specialist 21.94

12314 - Registered Nurse III 26.54

12315 - Registered Nurse III, Anesthetist 26.54

12316 - Registered Nurse IV 31.79

**13000 - Information and Arts Occupations**

13002 - Audiovisual Librarian 19.93

13011 - Exhibits Specialist I 19.15

13012 - Exhibits Specialist II 23.08

13013 - Exhibits Specialist III 26.14

13041 - Illustrator I 19.15

13042 - Illustrator II 23.08

13043 - Illustrator III 26.14

13047 - Librarian 21.41

13050 - Library Technician 11.31

13071 - Photographer I 11.81

13072 - Photographer II 15.14

13073 - Photographer III 18.93

13074 - Photographer IV 22.50

13075 - Photographer V 25.66

**15000 - Laundry, Dry Cleaning, Pressing and Related Occupations**

15010 - Assembler 6.61

15030 - Counter Attendant 6.61

15040 - Dry Cleaner 8.05

15070 - Finisher, Flatwork, Machine 6.61

15090 - Presser, Hand 6.61

15100 - Presser, Machine, Drycleaning 6.61

15130 - Presser, Machine, Shirts 6.61

15160 - Presser, Machine, Wearing Apparel, Laundry 6.61

15190 - Sewing Machine Operator 8.52

15220 - Tailor 9.37

15250 - Washer, Machine 7.09

**19000 - Machine Tool Operation and Repair Occupations**

19010 - Machine-Tool Operator (Toolroom) 14.67

19040 - Tool and Die Maker 18.42

**21000 - Material Handling and Packing Occupations**

21010 - Fuel Distribution System Operator 12.90

21020 - Material Coordinator 12.20

21030 - Material Expediter 12.20

21040 - Material Handling Laborer 7.84

21050 - Order Filler 10.19

21071 - Forklift Operator 10.39

21080 - Production Line Worker (Food Processing) 10.86

21100 - Shipping/Receiving Clerk 9.87

21130 - Shipping Packer 9.87

21140 - Store Worker I 8.54

21150 - Stock Clerk (Shelf Stocker; Store Worker II) 11.04

21210 - Tools and Parts Attendant 10.86

21400 - Warehouse Specialist 10.86

**23000 - Mechanics and Maintenance and Repair Occupations**

23010 - Aircraft Mechanic 18.57

23040 - Aircraft Mechanic Helper 12.77

23050 - Aircraft Quality Control Inspector 19.75

23060 - Aircraft Servicer 15.09

23070 - Aircraft Worker 16.27

23100 - Appliance Mechanic 14.67

23120 - Bicycle Repairer 11.33

23125 - Cable Splicer 17.19

23130 - Carpenter, Maintenance 14.67

23140 - Carpet Layer 13.69

23160 - Electrician, Maintenance 16.97

23181 - Electronics Technician, Maintenance I 15.24

23182 - Electronics Technician, Maintenance II 18.72

23183 - Electronics Technician, Maintenance III 19.92

23260 - Fabric Worker 12.70

23290 - Fire Alarm System Mechanic 15.63

23310 - Fire Extinguisher Repairer 11.73

23340 - Fuel Distribution System Mechanic 17.19

23370 - General Maintenance Worker 13.69

23400 - Heating, Refrigeration and Air Conditioning Mechanic 15.63

23430 - Heavy Equipment Mechanic 17.19

23440 - Heavy Equipment Operator 15.63

23460 - Instrument Mechanic 15.63

23470 - Laborer 7.84

23500 - Locksmith 14.67

23530 - Machinery Maintenance Mechanic 16.14

23550 - Machinist, Maintenance 15.98

23580 - Maintenance Trades Helper 10.75

23640 - Millwright 17.19

23700 - Office Appliance Repairer 14.67

23740 - Painter, Aircraft 14.67

23760 - Painter, Maintenance 14.67

23790 - Pipefitter, Maintenance 15.75

23800 - Plumber, Maintenance 14.78

23820 - Pneudraulic Systems Mechanic 15.63

23850 - Rigger 15.63

23870 - Scale Mechanic 13.69

23890 - Sheet-Metal Worker, Maintenance 15.63

23910 - Small Engine Mechanic 13.76

23930 - Telecommunication Mechanic I 18.70

23931 - Telecommunication Mechanic II 19.89

23950 - Telephone Lineman 17.19

23960 - Welder, Combination, Maintenance 15.63

23965 - Well Driller 15.63

23970 - Woodcraft Worker 15.63

23980 - Woodworker 11.73

**24000 - Personal Needs Occupations**

24570 - Child Care Attendant 8.41

24580 - Child Care Center Clerk 10.49

24600 - Chore Aid 6.23

24630 - Homemaker 12.70

**25000 - Plant and System Operation Occupations**

25010 - Boiler Tender 15.63

25040 - Sewage Plant Operator 14.67

25070 - Stationary Engineer 15.63

25190 - Ventilation Equipment Tender 10.75

25210 - Water Treatment Plant Operator 14.67

**27000 - Protective Service Occupations**

(not set) - Police Officer 19.88

27004 - Alarm Monitor 12.33

27006 - Corrections Officer 17.48

27010 - Court Security Officer 17.48

27040 - Detention Officer 17.48

27070 - Firefighter 19.83

27101 - Guard I 6.60

27102 - Guard II 10.38

**28000 - Stevedoring/Longshoremen Occupations**

28010 - Blocker and Bracer 15.20

28020 - Hatch Tender 15.20

28030 - Line Handler 15.20

28040 - Stevedore I 14.81

28050 - Stevedore II 18.11

**29000 - Technical Occupations**

21150 - Graphic Artist 19.52

29010 - Air Traffic Control Specialist, Center (2) 30.50

29011 - Air Traffic Control Specialist, Station (2) 21.03

29012 - Air Traffic Control Specialist, Terminal (2) 23.16

29023 - Archeological Technician I 17.29

29024 - Archeological Technician II 19.33

29025 - Archeological Technician III 23.95

29030 - Cartographic Technician 22.84

29035 - Computer Based Training (CBT) Specialist/ Instructor 21.50

29040 - Civil Engineering Technician 18.93

29061 - Drafter I 13.16

29062 - Drafter II 15.41

29063 - Drafter III 19.99

29064 - Drafter IV 26.25

29081 - Engineering Technician I 11.29

29082 - Engineering Technician II 14.72

29083 - Engineering Technician III 18.43

29084 - Engineering Technician IV 22.69

29085 - Engineering Technician V 26.70

29086 - Engineering Technician VI 30.43

29090 - Environmental Technician 25.79

29160 - Instructor 20.38

29210 - Laboratory Technician 15.08

29240 - Mathematical Technician 24.90

29361 - Paralegal/Legal Assistant I 14.31

29362 - Paralegal/Legal Assistant II 19.00

29363 - Paralegal/Legal Assistant III 20.91

29364 - Paralegal/Legal Assistant IV 28.11

29390 - Photooptics Technician 20.82

29480 - Technical Writer 28.84

29491 - Unexploded Ordnance (UXO) Technician I 19.38

29492 - Unexploded Ordnance (UXO) Technician II 23.45

29493 - Unexploded Ordnance (UXO) Technician III 28.11

29494 - Unexploded (UXO) Safety Escort 19.38

29495 - Unexploded (UXO) Sweep Personnel 19.38

29620 - Weather Observer, Senior (3) 18.15

29621 - Weather Observer, Combined Upper Air and

Surface Programs (3) 16.08

29622 - Weather Observer, Upper Air (3) 16.08

**31000 - Transportation/ Mobile Equipment Operation Occupations**

31030 - Bus Driver 12.42

31260 - Parking and Lot Attendant 6.82

31290 - Shuttle Bus Driver 11.32

31300 - Taxi Driver 9.55

31361 - Truckdriver, Light Truck 11.32

31362 - Truckdriver, Medium Truck 12.96

31363 - Truckdriver, Heavy Truck 13.90

31364 - Truckdriver, Tractor-Trailer 13.90

**99000 - Miscellaneous Occupations**

99020 - Animal Caretaker 8.02

99030 - Cashier 6.89

99041 - Carnival Equipment Operator 9.30

99042 - Carnival Equipment Repairer 10.13

99043 - Carnival Worker 6.75

99050 - Desk Clerk 9.41

99095 - Embalmer 19.38

99300 - Lifeguard 10.19

99310 - Mortician 19.38

99350 - Park Attendant (Aide) 12.79

99400 - Photofinishing Worker (Photo Lab Tech., Darkroom Tech) 8.24

99500 - Recreation Specialist 11.65

99510 - Recycling Worker 9.47

99610 - Sales Clerk 8.91

99620 - School Crossing Guard (Crosswalk Attendant) 7.01

99630 - Sport Official 9.06

99658 - Survey Party Chief (Chief of Party) 14.34

99659 - Surveying Technician (Instr. Person/Surveyor Asst./Instr.) 11.72

99660 - Surveying Aide 9.93

99690 - Swimming Pool Operator 10.77

99720 - Vending Machine Attendant 8.47

99730 - Vending Machine Repairer 10.77

99740 - Vending Machine Repairer Helper 8.47

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

ALL OCCUPATIONS LISTED ABOVE RECEIVE THE FOLLOWING BENEFITS:

HEALTH & WELFARE: Life, accident, and health insurance plans, sick
leave, pension plans, civic and personal leave, severance pay, and
savings and thrift plans. Minimum employer contributions costing an
average of \$2.59 per hour computed on the basis of all hours worked by
service employees employed on the contract.

VACATION: 2 weeks paid vacation after 1 year of service with a
contractor or successor; 3 weeks after 5 years, and 4 weeks after 15
years. Length of service includes the whole span of continuous service
with the present contractor or successor, wherever employed, and with
the predecessor contractors in the performance of similar work at the
same Federal facility. (Reg. 29 CFR 4.173)

HOLIDAYS: A minimum of ten paid holidays per year: New Year\'s Day,
Martin Luther King Jr.\'s Birthday, Washington\'s Birthday, Memorial
Day, Independence Day, Labor Day, Columbus Day, Veterans\' Day,
Thanksgiving Day, and Christmas Day. (A contractor may substitute for
any of the named holidays another day off with pay in accordance with a
plan communicated to the employees involved.) (See 29 CFR 4.174)

THE OCCUPATIONS WHICH HAVE PARENTHESES AFTER THEM RECEIVE THE FOLLOWING
BENEFITS (as numbered):

1\) Does not apply to employees employed in a bona fide executive,
administrative, or professional capacity as defined and delineated in 29
CFR 541. (See CFR 4.156)

2\) APPLICABLE TO AIR TRAFFIC CONTROLLERS ONLY - NIGHT DIFFERENTIAL: An
employee is entitled to pay for all work performed between the hours of
6:00 P.M. and 6:00 A.M. at the rate of basic pay plus a night pay
differential amounting to 10 percent of the rate of basic pay.

3\) WEATHER OBSERVERS - NIGHT PAY & SUNDAY PAY: If you work at night as
part of a regular tour of duty, you will earn a night differential and
receive an additional 10% of basic pay for any hours worked between 6pm
and 6am. If you are a full-time employed (40 hours a week) and Sunday is
part of your regularly scheduled workweek, you are paid at your rate of
basic pay plus a Sunday premium of 25% of your basic rate for each hour
of Sunday work which is not overtime (i.e. occasional work on Sunday
outside the normal tour of duty is considered overtime work).

HAZARDOUS PAY DIFFERENTIAL: An 8 percent differential is applicable to
employees employed in a position that represents a high degree of hazard
when working with or in close proximity to ordinance, explosives, and
incendiary materials. This includes work such as screening, blending,
dying, mixing, and pressing of sensitive ordance, explosives, and
pyrotechnic compositions such as lead azide, black powder and photoflash
powder. All dry-house activities involving propellants or explosives.
Demilitarization, modification, renovation, demolition, and maintenance
operations on sensitive ordnance, explosives and incendiary materials.
All operations involving regrading and cleaning of artillery ranges.

A 4 percent differential is applicable to employees employed in a
position that represents a low degree of hazard when working with, or in
close proximity to ordance, (or employees possibly adjacent to)
explosives and incendiary materials which involves potential injury such
as laceration of hands, face, or arms of the employee engaged in the
operation, irritation of the skin, minor burns and the like; minimal
damage to immediate or adjacent work area or equipment being used. All
operations involving, unloading, storage, and hauling of ordance,
explosive, and incendiary ordnance material other than small arms
ammunition. These differentials are only applicable to work that has
been specifically designated by the agency for ordance, explosives, and
incendiary material differential pay.

\*\* UNIFORM ALLOWANCE \*\*

If employees are required to wear uniforms in the performance of this
contract (either by the terms of the Government contract, by the
employer, by the state or local law, etc.), the cost of furnishing such
uniforms and maintaining (by laundering or dry cleaning) such uniforms
is an expense that may not be borne by an employee where such cost
reduces the hourly rate below that required by the wage determination.
The Department of Labor will accept payment in accordance with the
following standards as compliance:

The contractor or subcontractor is required to furnish all employees
with an adequate number of uniforms without cost or to reimburse
employees for the actual cost of the uniforms. In addition, where
uniform cleaning and maintenance is made the responsibility of the
employee, all contractors and subcontractors subject to this wage
determination shall (in the absence of a bona fide collective bargaining
agreement providing for a different amount, or the furnishing of
contrary affirmative proof as to the actual cost), reimburse all
employees for such cleaning and maintenance at a rate of \$3.35 per week
(or \$.67 cents per day). However, in those instances where the uniforms
furnished are made of \"wash and wear\" materials, may be routinely
washed and dried with other personal garments, and do not require any
special treatment such as dry cleaning, daily washing, or commercial
laundering in order to meet the cleanliness or appearance standards set
by the terms of the Government contract, by the contractor, by law, or
by the nature of the work, there is no requirement that employees be
reimbursed for uniform maintenance costs.

\*\* NOTES APPLYING TO THIS WAGE DETERMINATION \*\*

All terms and conditions of this Collective Bargaining Agreement apply
EXCLUDING Section 41.02 of this agreement.

Source of Occupational Title and Descriptions:

The duties of employees under job titles listed are those described in
the \"Service Contract Act Directory of Occupations,\" Fourth Edition,
January 1993, as amended by the Third Supplement, dated March 1997,
unless otherwise indicated. This publication may be obtained from the
Superintendent of Documents, at 202-783-3238, or by writing to the
Superintendent of Documents, U.S. Government Printing Office,
Washington, D.C. 20402. Copies of specific job descriptions may also be
obtained from the appropriate contracting officer.

REQUEST FOR AUTHORIZATION OF ADDITIONAL CLASSIFICATION AND WAGE RATE
{Standard Form 1444 (SF 1444)}

Conformance Process:

The contracting officer shall require that any class of service employee
which is not listed herein and which is to be employed under the
contract (i.e., the work to be performed is not performed by any
classification listed in the wage determination), be classified by the
contractor so as to provide a reasonable relationship (i.e., appropriate
level of skill comparison) between such unlisted classifications and the
classifications listed in the wage determination. Such conformed classes
of employees shall be paid the monetary wages and furnished the fringe
benefits as are determined. Such conforming process shall be initiated
by the contractor prior to the performance of contract work by such
unlisted class(es) of employees. The conformed classification, wage
rate, and/or fringe benefits shall be retroactive to the commencement
date of the contract. {See Section 4.6 (C)(vi)} When multiple wage
determinations are included in a contract, a separate SF 1444 should be
prepared for each wage determination to which a class(es) is to be
conformed.

The process for preparing a conformance request is as follows:

1\) When preparing the bid, the contractor identifies the need for a
conformed occupation) and computes a proposed rate).

2\) After contract award, the contractor prepares a written report
listing in order proposed classification title), a Federal grade
equivalency (FGE) for each proposed classification), job description),
and rationale for proposed wage rate), including information regarding
the agreement or disagreement of the authorized representative of the
employees involved, or where there is no authorized representative, the
employees themselves. This report should be submitted to the contracting
officer no later than 30 days after such unlisted class(es) of employees
performs any contract work.

3\) The contracting officer reviews the proposed action and promptly
submits a report of the action, together with the agency\'s
recommendations and pertinent information including the position of the
contractor and the employees, to the Wage and Hour Division, Employment
Standards Administration, U.S. Department of Labor, for review. (See
section 4.6(b)(2) of Regulations 29 CFR Part 4).

4\) Within 30 days of receipt, the Wage and Hour Division approves,
modifies, or disapproves the action via transmittal to the agency
contracting officer, or notifies the contracting officer that additional
time will be required to process the request.

5\) The contracting officer transmits the Wage and Hour decision to the
contractor.

6\) The contractor informs the affected employees.

Information required by the Regulations must be submitted on SF 1444 or
bond paper.

When preparing a conformance request, the \"Service Contract Act
Directory of Occupations\" (the Directory) should be used to compare job
definitions to insure that duties requested are not performed by a
classification already listed in the wage determination. Remember, it is
not the job title, but the required tasks that determine whether a class
is included in an established wage determination. Conformances may not
be used to artificially split, combine, or subdivide classifications
listed in the wage determination.

I. INTRODUCTION

In accordance with the provisions of the Federal Acquisition Regulation,
NASA FAR Supplement and the NASA Award Fee Handbook, and JSC
Implementation, an award fee evaluation procedure is hereby established
for determination of award fees payable under this contract. The fee
arrangement outlined in this plan has been established to motivate the
contractor to strive for excellence in the quality and timeliness of
performance, subcontracting goals, safety, and cost. The payment of any
award fee is contingent upon compliance with contractual requirements
and performance to the degree specified in Appendix 1.

The Contractor's performance will be evaluated by the Government in
accordance with the procedures set forth below, at the expiration of
each period specified in Appendix 3. The evaluation to be performed by
the Government will be based on the Government's assessment of the
Contractor's accomplishment of the various areas of work covered by the
SOW, in accordance with the criteria, weightings, procedures, and other
provisions set forth below.

Performance determinations will be made at the end of each 6-month
evaluation period as shown in Appendix 3.

# II. ORGANIZATION STRUCTURE

A.  PEB (Performance Evaluation Board)

A PEB, comprised of selected NASA technical and administrative
personnel, will evaluate the Contractor's performance after each
evaluation period to determine whether and to what extent the
Contractor's performance during the evaluation period is deserving of
the payment of award fee. The Board, at the end of each evaluation
period, will prepare a summary of the evaluations for review by the Fee
Determination Official (FDO). This summary will include a recommendation
to the FDO as the adjective rating and numerical score to be assigned
for the Contractor's performance in the preceding evaluation period.

B.  FDO

The FDO, a senior NASA official, will determine the Contractor's
performance score in accordance with the procedures set forth below.
After considering available and pertinent information and
recommendations, the FDO will make a performance determination for each
period. The FDO is shall appoint the PEB Chairperson and members.

# III. EVALUATION PROCEDURES

A. No later than 45 calendar days prior to the start of each evaluation
period (for the first evaluation period, this shall be construed as 30
days prior to the end of the phase-in period), the Contractor may submit
to the CO recommended areas of emphasis and weightings for the ensuing
evaluation period that are within the general factors listed in Section
III of this plan. Consideration will be given to the Contractor's
recommendations; however it is the Government's responsibility to
establish the specific areas of emphasis for each evaluation period.

B. No later than 30 days prior to the start of each new six-month
evaluation period (for the first evaluation period, this shall be
construed as 20 days prior to the end of the phase-in period), the
Contractor will be notified by the CO of the selected areas of emphasis
and weightings for that period. Emphasis will be directed at particular
areas under the contract which appear to the Government to be deserving
of special attention and will be used in judging the Contractor's
performance. These areas of emphasis will not necessarily cover the
entire spectrum of performance that will be evaluated in determining
award fee dollars earned. Other pertinent factors included under the
contract and general factors bearing upon overall performance will be
considered as the facts and circumstances of each period may require.

C. The Contractor shall be apprised of a general assessment of
performance at the mid-point of the period, and at such other times as
may be deemed appropriate. The purpose of these meetings shall be to
discuss any specific areas where the Contractor has excelled, and where
future Contractor emphasis may be necessary.

D. Promptly after the end of each six-month evaluation period, the PEB
shall meet to consider all of the performance information it has
obtained. At the meeting, the PEB will summarize its preliminary
findings and recommendations in the Performance Evaluation Board Report
(PEBR).

E. At the PEB meeting, the contractor may provide a self-evaluation
presentation (a copy of which shall be provided to the PEB) not to
exceed 30 minutes in length.

F. The Contractor may furnish a separate self-evaluation report on or
before the fifth calendar day following the expiration of each
evaluation period. These self-evaluation reports shall not exceed 20
pages in length per each evaluation period. The PEB will not submit its
recommendation to the Fee Determination Official (FDO) until (1) the
Contractor's self-evaluation report has been received and considered, or
(2) the Contractor has provided written notification that a
self-evaluation report will not be submitted, or (3) the deadline for
its submission has expired.

G. The PEB Chair will prepare the PEBR for the period and present the
findings and recommendations to the FDO. The reports will include an
adjective rating and a recommended performance score with supporting
documentation.

H. The Contractor will be notified of the PEB evaluation and recommended
ratings and scores and will be provided copies of the PEBR. The
Contractor may provide additional information for consideration by the
FDO. Such information shall be delivered in writing to the Contracting
Officer within 5 calendar days of notification to the contractor of the
recommended rating and score. The PEB Chair will in turn provide this
additional information to the FDO

I. The FDO will consider the recommendations of the PEB, the PEBR,
information provided by the Contractor, if any, and any other pertinent
information in determining performance scores. The FDO's determination
of the scores will be stated in a written Award Fee Determination.

J. The FDO will not make a performance determination prior to the
expiration of the 5 calendar day period prescribed above for Contractor
submissions unless the Contractor has affirmatively indicated, in
writing, that no further Contractor submission will be made.

K. The Award Fee Determination will be provided to the Contractor by the
Contracting Officer.

SECTION IV. AWARD FEE EVALUATION CRITERIA AND WEIGHTING

A. In evaluating the performance of the Contractor, the Government will
evaluate major elements of Contractor performance including performance
and cost.

B. The criteria for evaluation of Contractor performance for
determination of award fee is defined below. The Government may
unilaterally modify the award fee performance evaluation factors and
performance evaluation areas applicable to the evaluation period. The CO
shall notify the Contractor in writing of any such changes prior to the
start of the relevant evaluation period.

**Evaluation Criteria Weight**

**1. Performance, Compliance with Safety and**

**Health Requirements and Subcontracting Goals. 70 Percent**

Performance criterion includes all aspects of quality and schedule based
on objective evidence demonstrating both technical and management
performance. For technical performance, emphasis will be placed on the
SOW performance standards.

Compliance with Safety and Health Requirements criterion includes all
aspects of safety and health and environmental compliance issues
primarily based on objective evidence demonstrating performance.

The Subcontracting Goals criterion includes evaluation of the
Contractor's success in achieving or surpassing the subcontracting goals
specified in the contract.

**2. Cost 30 Percent**

Cost criterion includes evaluation of actual cost performance relative
to negotiated contract values, including detailed variance analyses.

> C. Notwithstanding any of the above, a major breach of safety or
> security, as defined by clause 1852.223-75 of this contract, may
> result in an award fee score of zero for the affected evaluation
> period.
>
> D. In order to earn any award fee, the Contractor must receive a
> numerical score of 61 or greater. Appendix 1 provides the performance
> level definition adjective ratings and corresponding numerical scores
> that will be used in evaluating performance. The numerical grade
> ranges corresponding to these adjective ratings and their conversion
> to total award fee earned are set forth in Appendix 2. Appendix 3
> provides the distribution of the available maximum award fee for each
> evaluation period.

**APPENDIX 1 -- EVALUATION DEFINITIONS**

+------------+----+--------------------------------------+---+--------+
| ##  {#     | #  | ###  {#section-7}                    | # | #      |
| section-5} | ## |                                      | # |  GRADE |
|            |    | ### DEFINITION                       | # |  RANGE |
| ##         | {# |                                      |   |        |
|  ADJECTIVE | se |                                      |   |        |
|            | ct |                                      | { |        |
|            | io |                                      | # |        |
|            | n- |                                      | s |        |
|            | 6} |                                      | e |        |
|            |    |                                      | c |        |
|            |    |                                      | t |        |
|            |    |                                      | i |        |
|            |    |                                      | o |        |
|            |    |                                      | n |        |
|            |    |                                      | - |        |
|            |    |                                      | 8 |        |
|            |    |                                      | } |        |
+------------+----+--------------------------------------+---+--------+

Excellent Of exceptional merit exemplary performance 91-100

in a timely, efficient, and economical manner;

very minor (if any) deficiencies with no adverse

effect on overall performance.

Very Good Very effective performance, fully responsive 81-90

to contract requirements; reportable deficiencies

but with little identifiable effect on overall

performance.

Good Effective performance, fully responsive to contract 71-80

requirements, reportable deficiencies, but with

little identifiable effect on overall performance.

Satisfactory Meets or slightly exceeds minimum acceptable 61-70

standards; adequate results. Reportable

deficiencies with identifiable but not

substantial effects on overall performance.

Poor/

Unsatisfactory Does not meet minimum acceptable standards 60 and

in one or more areas; remedial action required below

in one or more areas; deficiencies in one or more

areas, which adversely effect overall performance.

#### APPENDIX 2 -- PERFORMANCE SCORE CONVERSION CHART

+------------------+-------------------------------+------------------+
| ## Weighed P     | ###  {#section-9}             | # P              |
| erformance Score |                               | ercentage of Ava |
|                  |                               | ilable Award Fee |
+------------------+-------------------------------+------------------+
| #                |                               | #  {#section-11} |
| #  {#section-10} |                               |                  |
+------------------+-------------------------------+------------------+
| ## 1             |                               | # **100%         |
| 00 {#section-12} |                               | ** {#section-13} |
+------------------+-------------------------------+------------------+
| ##               |                               | # **99           |
| 99 {#section-14} |                               | ** {#section-15} |
+------------------+-------------------------------+------------------+
| ##               |                               | # **98           |
| 98 {#section-16} |                               | ** {#section-17} |
+------------------+-------------------------------+------------------+
| ##               |                               | # **97           |
| 97 {#section-18} |                               | ** {#section-19} |
+------------------+-------------------------------+------------------+
| ##               | Excellent                     | # **96           |
| 96 {#section-20} |                               | ** {#section-21} |
+------------------+-------------------------------+------------------+
| ##               |                               | # **95           |
| 95 {#section-22} |                               | ** {#section-23} |
+------------------+-------------------------------+------------------+
| ##               |                               | # **94           |
| 94 {#section-24} |                               | ** {#section-25} |
+------------------+-------------------------------+------------------+
| ##               |                               | # **93           |
| 93 {#section-26} |                               | ** {#section-27} |
+------------------+-------------------------------+------------------+
| ##               |                               | # **92           |
| 92 {#section-28} |                               | ** {#section-29} |
+------------------+-------------------------------+------------------+
| ##               |                               | # **91           |
| 91 {#section-30} |                               | ** {#section-31} |
+------------------+-------------------------------+------------------+
| ##               |                               | # **90           |
| 90 {#section-32} |                               | ** {#section-33} |
+------------------+-------------------------------+------------------+
| 89               |                               | # **89           |
|                  |                               | ** {#section-34} |
+------------------+-------------------------------+------------------+
| 88               |                               | # **88           |
|                  |                               | ** {#section-35} |
+------------------+-------------------------------+------------------+
| 87               |                               | # **87           |
|                  |                               | ** {#section-36} |
+------------------+-------------------------------+------------------+
| 86               | Very Good                     | # **86           |
|                  |                               | ** {#section-37} |
+------------------+-------------------------------+------------------+
| 85               |                               | # **85           |
|                  |                               | ** {#section-38} |
+------------------+-------------------------------+------------------+
| 84               |                               | # **84           |
|                  |                               | ** {#section-39} |
+------------------+-------------------------------+------------------+
| 83               |                               | # **83           |
|                  |                               | ** {#section-40} |
+------------------+-------------------------------+------------------+
| 82               |                               | # **82           |
|                  |                               | ** {#section-41} |
+------------------+-------------------------------+------------------+
| 81               |                               | # **81           |
|                  |                               | ** {#section-42} |
+------------------+-------------------------------+------------------+
| 80               |                               | # **80           |
|                  |                               | ** {#section-43} |
+------------------+-------------------------------+------------------+
| 79               |                               | # **79           |
|                  |                               | ** {#section-44} |
+------------------+-------------------------------+------------------+
| 78               |                               | # **78           |
|                  |                               | ** {#section-45} |
+------------------+-------------------------------+------------------+
| 77               |                               | # **77           |
|                  |                               | ** {#section-46} |
+------------------+-------------------------------+------------------+
| 76               | Good                          | # **76           |
|                  |                               | ** {#section-47} |
+------------------+-------------------------------+------------------+
| 75               |                               | # **75           |
|                  |                               | ** {#section-48} |
+------------------+-------------------------------+------------------+
| 74               |                               | # **74           |
|                  |                               | ** {#section-49} |
+------------------+-------------------------------+------------------+
| 73               |                               | # **73           |
|                  |                               | ** {#section-50} |
+------------------+-------------------------------+------------------+
| 72               |                               | # **72           |
|                  |                               | ** {#section-51} |
+------------------+-------------------------------+------------------+
| 71               |                               | # **71           |
|                  |                               | ** {#section-52} |
+------------------+-------------------------------+------------------+
| 70               |                               | # **70           |
|                  |                               | ** {#section-53} |
+------------------+-------------------------------+------------------+
| 69               |                               | # **69           |
|                  |                               | ** {#section-54} |
+------------------+-------------------------------+------------------+
| 68               |                               | # **68           |
|                  |                               | ** {#section-55} |
+------------------+-------------------------------+------------------+
| 67               |                               | # **67           |
|                  |                               | ** {#section-56} |
+------------------+-------------------------------+------------------+
| 66               | Satisfactory                  | # **66           |
|                  |                               | ** {#section-57} |
+------------------+-------------------------------+------------------+
| 65               |                               | # **65           |
|                  |                               | ** {#section-58} |
+------------------+-------------------------------+------------------+
| 64               |                               | # **64           |
|                  |                               | ** {#section-59} |
+------------------+-------------------------------+------------------+
| 63               |                               | # **63           |
|                  |                               | ** {#section-60} |
+------------------+-------------------------------+------------------+
| 62               |                               | # **62           |
|                  |                               | ** {#section-61} |
+------------------+-------------------------------+------------------+
| 61               |                               | # **61           |
|                  |                               | ** {#section-62} |
+------------------+-------------------------------+------------------+
| 60 and below     |                               | # **0            |
|                  |                               | ** {#section-63} |
+------------------+-------------------------------+------------------+

**APPENDIX 3 -- AWARD FEE DISTRIBUTION**

+--------------------------------+-------------------+----------------+
| **Evaluation Period**          | **Estimated**     | **Earned**     |
|                                |                   |                |
|                                | **Award Fee       | **Award Fee**  |
|                                | Available**       |                |
+--------------------------------+-------------------+----------------+
|                                |                   |                |
+--------------------------------+-------------------+----------------+
| BASIC CONTRACT (If Options 1,  |                   |                |
| 2, and 3 are not exercised):   |                   |                |
+--------------------------------+-------------------+----------------+
|                                |                   |                |
+--------------------------------+-------------------+----------------+
| January 1, 2004 -- June 30,    | \$3,838,208       |                |
| 2004                           |                   |                |
+--------------------------------+-------------------+----------------+
| July 1, 2004 -- September 30,  | \$1,885,794       |                |
| 2004                           |                   |                |
+--------------------------------+-------------------+----------------+
|                                |                   |                |
+--------------------------------+-------------------+----------------+
| ### Total Available Awa        | # **\$5,724,00    | #              |
| rd Fee for Basic Contract Only | 2** {#section-64} |  {#section-65} |
+--------------------------------+-------------------+----------------+
| **Total Available Award Fee if | \$7,425,940       |                |
| Option 1 is exercised**        |                   |                |
+--------------------------------+-------------------+----------------+
|                                |                   |                |
+--------------------------------+-------------------+----------------+
|                                |                   |                |
+--------------------------------+-------------------+----------------+
| If OPTION 2 is exercised the   |                   |                |
| evaluation periods will be as  |                   |                |
| follows:                       |                   |                |
+--------------------------------+-------------------+----------------+
|                                |                   |                |
+--------------------------------+-------------------+----------------+
| January 1, 2004 -- June 30,    | \$3,703,418       |                |
| 2004                           |                   |                |
+--------------------------------+-------------------+----------------+
| July 1, 2004 -- March 31, 2005 | \$5,338,984       |                |
+--------------------------------+-------------------+----------------+
|                                |                   |                |
+--------------------------------+-------------------+----------------+
| **Total Available Award Fee if | \$9,042,402       |                |
| Option 2 is exercised**        |                   |                |
+--------------------------------+-------------------+----------------+
|                                |                   |                |
+--------------------------------+-------------------+----------------+
|                                |                   |                |
+--------------------------------+-------------------+----------------+
| **If OPTION 3 is exercised the |                   |                |
| evaluation periods will be as  |                   |                |
| follows:**                     |                   |                |
+--------------------------------+-------------------+----------------+
|                                |                   |                |
+--------------------------------+-------------------+----------------+
| January 1, 2004 -- June 30,    | \$3,860,125       | \$3,589,916.25 |
| 2004                           |                   |                |
+--------------------------------+-------------------+----------------+
| July 1, 2004 -- December 31,   | \$3,710,991       | \$3,525,441.45 |
| 2004                           |                   |                |
+--------------------------------+-------------------+----------------+
| January 1, 2005 -- June 30,    | \$3,633,150       |                |
| 2005                           |                   |                |
+--------------------------------+-------------------+----------------+
| July 1, 2005 -- December 31,   | \$3,633,149       |                |
| 2005                           |                   |                |
+--------------------------------+-------------------+----------------+
| January 1, 2006 -- September   | \$5,445,374       |                |
| 30, 2006                       |                   |                |
+--------------------------------+-------------------+----------------+
|                                |                   |                |
+--------------------------------+-------------------+----------------+
| **Total Available Award Fee if | \$20,282,789      |                |
| Option 3 is exercised**        |                   |                |
+--------------------------------+-------------------+----------------+

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

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

#   {#section-66}

# Table of Contents

[2.1 Mission Support Operations Contract (MSOC) Small Business Goals
DRD9-5](#mission-support-operations-contract-msoc-small-business-goals)

[2.2 Small Business Approach DRD9-5](#small-business-approach)

[3.1 Meet or Exceed Stated Small Business Goals in all Small Business\
Categories
DRD9-7](#meet-or-exceed-stated-small-business-goals-in-all-small-business-categories)

[3.2 Small Businesses Specifically Identified in Proposal
DRD9-7](#small-businesses-specifically-identified-in-proposal)

[3.4 Degree of Commitment from Proposed Small Businesses
DRD9-8](#degree-of-commitment-from-proposed-small-businesses)

[3.5 Complexity of Small Business Work
DRD9-9](#complexity-of-small-business-work)

[3.6 Risk Mitigation Associated with Small Business Performance
DRD9-9](#risk-mitigation-associated-with-small-business-performance)

[3.7 Applicability of Appropriate NAICS Codes to Work Allocated to
Small\
Businesses
DRD9-10](#applicability-of-appropriate-naics-codes-to-work-allocated-to-small-businesses)

[7.1 Master Small Business Subcontracting Plan
DRD9-15](#master-small-business-subcontracting-plan)

[7.2 Small Business Awards DRD9-15](#small-business-awards)

[7.3 Small Business Outreach Initiatives
DRD9-16](#small-business-outreach-initiatives)

[7.4 Small Business Training DRD9-16](#small-business-training)

[8.1 Small Business Subcontract Management Plan (SMP)
DRD9-17](#small-business-subcontract-management-plan-smp)

[8.2 Subcontractor Evaluation DRD9-17](#subcontractor-evaluation)

[8.3 Requirements Flowdown DRD9-18](#requirements-flowdown)

9.0 Small Business
Summary...............................................................DRD9-17

# List of Figures

Figure DRD9-1 LM Small Business Goals for MSOC DRD9-4

Figure DRD9-2 MSOC SOW Work Assignments DRD9-5

Figure DRD9-3 Teammate Selection Process DRD9-10

Figure DRD9-4 LMSO SB Participation Features and Benefits DRD9-16

**ADDENDUMS**

Addendum A Addendum A to Master Subcontracting
Plan..........................V-A-1

Addendum B Subcontractor Letters of
Commitment...................................V-B-1

Addendum C Pro-Net Firm
Profiles....................................................... V-C-1

# 1.0 Small Business Participation

It is Lockheed Martin's (LM) policy to provide maximum opportunities for
Small Business, Small Disadvantaged Business (SDB), Women-Owned Small
Business (WOSB), Historically Underutilized Business Zone (HUBZone)
Small Business, Veteran-Owned Small Business (VOSB), Service-Disabled
Veteran-Owned Small Business (SDVOB), and Historically Black Colleges
and Universities/Minority Institutions. Refer to July 1, 2003,
memorandum from Michael F. Camardo, Executive Vice President, Lockheed
Martin Technology Services (LMTS), LM Small Business Policy Statement.
To that end, our Mission Support Operations Contract (MSOC) proposal
exceeds the specified Small Business participation goal and the complex
and diverse needs of our customer with the careful selection of
subcontractors. We have identified small business subcontractors across
all socioeconomic categories.

The following paragraphs define our enhanced Small Business
Subcontracting Plan for the MSOC. This plan is supported by our formal
Master Small Business Subcontracting Plan and MSOC Addendums A through
C. The Master Plan is attached to this Subcontracting Plan.

# 2.0 Small Business Subcontracting Goals and Approach

## 2.1 Mission Support Operations Contract (MSOC) Small Business Goals

We commit to meet the Small Business participation goals and to meet
Johnson Space Center (JSC) expectations in all our Small Business
Program. We are committed to implementing a low-risk enhanced Small
Business Subcontracting Plan that embodies the spirit and intent of the
Small Business Administration (SBA) and Headquarters (HQ) National
Aeronautics and Space Administration (NASA) Small Business Programs. Our
commitment includes providing a series of Small Business initiatives to
provide support to the NASA Small Business Program.

We satisfy NASA MSOC requirements for utilization of Small Business
categories and commit to allocation of complex work to a variety of
Small Businesses.

To honor every aspect of our Small Business Subcontracting Plan, we
establish enforceable commitments as defined in Federal Acquisition
Regulation (FAR) 19.1202-3 with the customer in the form of contract
provisions and award fee requirements.

## 2.2 Small Business Approach

![](media/image2.jpeg){width="3.097916666666667in"
height="2.292361111111111in"}Small Business subcontracting represents a
significant and very important part of our MSOC proposal. We augment our
extensive system engineering and integration capabilities with those of
key Small Business subcontractors who possess demonstrated capabilities
and past performance in critical elements of the mission. Our team
includes

### 2.2.1 Concept of Operations

We propose to employ all of our MSOC subcontractors in a single
operations environment in which the Small Business employees are
integrated into the work force. MSOC subcontractors have been selected
to perform in their respective areas of expertise. They operate as part
of the integrated MSOC work force. Technical performance is directed,
monitored, and evaluated on a daily basis by the responsible
supervisor/lead. The Lockheed Martin Space Operations (LMSO) Subcontract
Administrator provides contractual direction.

We chose an integrated teaming approach over allocation of functional
work to Small Businesses for the following reasons.

Integrated operation strengthens our team and guarantees strong mission
performance

A "one team -- one badge" concept ensures close, daily contact with
Small Business teammate employees

Potential operational and cost surprises are eliminated, reducing
mission performance risk.

All teammates follow the common work center processes and procedures
that have proven successful on the CSOC Contract

Integrated operation promotes strong team identity

Integrated operation facilitates the use of our proven subcontract
management process

Smaller amounts of work are allocated to a greater number of teammates,
thereby distributing the workload

Small Business subcontractors benefit from the opportunity for technical
growth.

# 3.0 Small Business Subcontracting Plan

## 3.1 Meet or Exceed Stated Small Business Goals in all Small Business Categories

LMSO offers a Small Business Subcontracting Plan, developed in
accordance with FAR 52.219-9 and NASA Supplement 1852.219-73, that
provides Small Business participation to the maximum extent without
introducing risk. We attain the Small Business participation requirement
by selecting highly credible teammates and vendors who provide a
valuable contribution to MSOC. In every Small Business category, our
plan satisfies the Request for Proposal (RFP) requirements for
utilization of every Small Businesses category (refer to **Figure
G237152H**). Our program supports the spirit and intent of the SBA,
NASA, and JSC Small Business Programs and exceeds requirements for total
Small Business participation.

## 3.2 Small Businesses Specifically Identified in Proposal

We have signed letters of commitment and will have signed subcontracts
before contract start. The specific number of Small Businesses and
personnel skill mix is contained in the Cost Volume. **Figure G237153H**
shows the Small Business allocation by name, work assignments, North
American Industry Classification System (NAICS) code assigned, and NAICS
threshold. Percentage and dollars committed to each Small Business are
listed in the Master Small Business Subcontracting Plan, Addendum A. The
Cost Volume provides detailed information by position allocated to Small
Businesses. Our team is complete and may only change if the Government
includes new requirements.

An outstanding Small Business Program with a proven record for exceeding
Small Business performance goals

Enforceable Small Business commitments

Signed Small Business Letters of Commitment

Emphasis on SDB subcontracting

Commitment to NASA Special Emphasis Programs (of the subcontracted
dollars is allocated to SDB, WOSB, VOSB, SDVOB, HBCU/MI, and HUBZone
teammates)

of total contract value is committed to Small Business

Commitment to multiple outreach initiatives

Small Business growth opportunities during program execution.

## 3.4 Degree of Commitment from Proposed Small Businesses

We are highly confident that all of our Small Business subcontractors
are 100% committed to joining the LM Team. Our proposed team members
have clearly demonstrated their commitment by the following actions:

All four Small Business concerns have signed Letters of Commitment to
the team (see Addendum B to Master Subcontracting Plan)

Our teammates are involved in proposal development strategy sessions
with LM

Teammates have committed resources to support the proposal development
effort.

## 3.5 Complexity of Small Business Work

In keeping with our concept of an integrated work force, we have
allocated a variety of complex MSOC functions to our Small Business
subcontractors. To expose the Small Businesses to a wide range of MSOC
functions and facilitate their growth, we allocated Small Business
participation to support 33 separate CWBS paragraphs. Small Businesses
perform in all major areas of the SOW as previously shown in Figure
DRD9-2.

## 3.6 Risk Mitigation Associated with Small Business Performance

We have high confidence that our selected Small Business subcontractors
will perform their allocated work assignments in an excellent manner.
The following factors support our position:

**Demonstrated Past Performance**. We have selected Small Businesses
with solid past performance (or personnel qualifications) in every
performance area. We analyzed their past performance for relevancy and
quality of performance and selected highly qualified teammates. The
Small Businesses bring excellent past performance credentials and
therefore present low risk to mission and cost performance.

**Compatibility of Work Allocated**. In every case, we have allocated
work to the Small Businesses consistent with their past performance, and
with their core competencies. In no case did we "stretch" Small Business
subcontractors to perform in areas where they may be uncomfortable,
minimizing the risk that they might perform unsatisfactorily.

**Reasonable Amounts of Work**. We have been very sensitive to the size
and experience of our teammates when making workload allocations.

**Ability to Staff Allocated Positions**. In light of Small Business
teammate past performance citations and discussions, we are confident
that each Small Business has the experience and ability to fill 100% of
the MSOC allocated positions by contract start.

**Integrated Operations**. By integrating our subcontractor personnel
into work centers working along side LM technicians, engineers, and
supervisors, we will retain immediate visibility into subcontractor
performance. This arrangement also facilitates real-time communication
and heads off problems as they arise.

**Subcontractor Price Analysis**. We have verified, through price
analysis, that our teammates not only submitted realistic proposals
addressing required staffing and skill mixes, but also meet or exceed
existing wage determinations and are compliant with collective
bargaining agreements where applicable. We are confident that the
compensation plans proposed by the Small Businesses enable them to
successfully hire and retain personnel in Houston, TX.

## 3.7 Applicability of Appropriate NAICS Codes to Work Allocated to Small Businesses

In assigning NAICS codes to our Small Businesses, we first reviewed all
definitions of the applicable NAICS codes for the MSOC subcontracted
effort as defined in the NAICS U.S. Manual published by the Department
of Commerce. We then made a stringent and accurate review of the codes
for the specific work to be performed by each subcontractor. We have
determined NAICS Code 541710, Research and Development in the Physical,
Engineering, and Life Sciences is applicable to the majority of the work
to be performed by our subcontractors. In addition, NAICS Code 541330,
Engineering Services, is applicable to two of our subcontractors. Figure
DRD9-2 defines the Small Business subcontractors, CWBS work assignments
and the applicable NAICS code number, and threshold (either dollars or
number of employees).

# 4.0 Small Business Initiatives

As part of our Small Business Subcontracting Plan, we offer "above and
beyond" initiatives to support and reinforce the NASA Small Business
Program. LM believes it is essential that the MSOC prime contractor make
a *qualitative contribution* to the NASA Small Business program as well
as meet the *quantitative* Small Business participation value stipulated
in the RFP. Our initiatives include the following:

**Boost Small Business Participation in NASA Acquisitions**. LMSO
supports NASA's number one qualitative Small Business goal by committing
of the total acquisition value of the contract to Small Business. LMSO
has chosen to increase our Small Business percentages because it is a
cost-competitive approach for MSOC and it supports the NASA Small
Business participation goals.

-   Our allocation to Small Business subcontracting is accomplished with
    no additional impact to contract cost, performance risk, or program
    schedule. Further, our Small Business subcontractors enable us to be
    cost-competitive by providing competitive loaded labor rates.

**Expand Small Business Subcontracting Opportunities**. Our approach in
supporting MSOC is that having more Small Business subcontractors
participate is better than awarding larger dollar subcontracts to just a
single Small Business. This approach supports both the spirit and intent
of the Small Business Program. As such, we have included four Small
Business subcontractors on our MSOCTeam. We also have identified two
HBCU/MI entities. Additional subcontractors will be used should further
subcontracting opportunities develop.

**Grow Small Businesses**. LMSO is committed to expanding MSOC Small
Business subcontracting opportunities by giving Small Business concerns,
in the form of contract changes, primary consideration for new contract
work. Our objective is to substantially exceed the Small Business goals
of the approved Small Business Subcontracting Plan (reference Figure
DRD9-1).

**Promote Special Emphasis Programs (SDB, WOSB, SDVOB, HBCU/MI, VOSB and
HUBZone)**. In addition to exceeding the Small Business participation
goal, support of the special emphasis programs is a significant point of
our Small Business Program. of the subcontracted dollars is allocated to
SDB, VOSB, WOSB, SDVOB, HBCU/MI, and HUBZone concerns.

**Assume a Leadership Role to Broaden Responsive Small Business
Education Programs**. LMSO offers two initiatives to broaden Small
Business education and awareness:

-   We play an active role in promoting Small Businesses within our own
    program environment. To that end, we display MSOC Small Business
    statistics in our Program Office to monitor our participation and
    serve as a constant reminder of our commitment to the JSC Small
    Business Program.

-   We commit to educate our Small Business subcontractors by sharing
    process improvements and lessons learned. As teammates on MSOC, the
    Small Businesses participate in our LM21 initiatives and are given
    full and open access to process improvements and lessons learned as
    they occur in the course of the program. These data are presented to
    teammate management during our Subcontractor Program Reviews. These
    reviews have proven to be highly effective on other LM programs.

**Adapt Small Business Program to Changing Environment and Collaborate
at All Levels to Strengthen Small Business Programs**. We participate in
SBA regional meetings/symposia and support local councils by the
involvement of our corporate Technology Services Small Business Manager.
Through our MSOC Business Manager, we work closely with and support the
NASA Small Business Advocate outreach initiatives.

Our support of the Small Business qualitative goals and initiatives and
the NASA Small Business Program is what differentiates our Small
Business Program from the competition. These proposed initiatives offer
a significant benefit to our customer at no increase in cost or risk to
the contract.

# 5.0 Subcontractor Selection Process

LM enacted a rigorous selection process for our teammates and
subcontractors as shown in **Figure DRD9-3**. Our approach began with a
clear understanding of the MSOC program goals and objectives, and led
ultimately to selection of the best Small Business subcontractors
available. We ensured that potential teammates would present an *overall
low risk* to our team, including consideration of present financial
stability and strong past performance credentials.

![](media/image3.jpeg){width="6.497916666666667in"
height="3.872916666666667in"}

##  {#section-67}

# 6.0 Subcontractor Independent Assessment

The selection of MSOC teammates is governed by the Lockheed Martin
Acquisition Procedure (LMAP) 2310, Determining Noncompetitive
Acquisitions and LM Technology Services Supplement. These procedures
ensure that a consistent approach is applied in every LMSO acquisition.

In building our MSOC team, we conducted an independent assessment of
each potential Small Business to assess technical and managerial
capabilities, relevant past performance, experience with NASA work,
previous contractual performance with LM, financial stability, Small
Business status, NAICS code applicability and overall potential risk.
Subsequent to our "due diligence" assessment, we selected the following
subcontractors:

# 7.0 LMTS Small Business Program

## 7.1 Master Small Business Subcontracting Plan

The LMTS Master Small Business Subcontracting Plan was approved by the
Defense Logistics Agency (DLA) in September 2002 for a 3-year period.
This approval is based on the results of audits performed by the LMTS
oversight authority, the DLA Deputy for Small Business. In addition,
LMTS is subject to audit by the SBA. As part of LMTS, LMSO performs
within the guidelines of the LMTS Master Small Business Subcontracting
Plan. Each proposal submitted by LMSO complies with the Master Plan and
provides an Addendum with goals for the specific contract effort (see
Addendum A to Master Subcontracting Plan). Ms. Julie Paglione, LMTS
Small Business Programs Manager, is responsible for administering the
Master Small Business Subcontracting Plan and the MSOC Subcontracting
Program. Her duties and responsibilities, including outreach efforts,
records maintenance and requirements, and Small Business reporting
requirements, are defined in the Master Subcontracting Plan attached
hereto.

## 7.2 Small Business Awards

To accomplish our Small Business participation goals, we apply our
award-winning Small Business Management Processes to the MSOC. For many
years, our strong commitment to Small Businesses has been recognized by
government agencies. In recognition of superior Small Business
performance, we have received numerous, significant awards from Federal
agencies including the SBA, DLA, Defense Contract Management Command
(DMSOC), Department of Energy (DOE), and NASA.

**Dwight D. Eisenhower Award**. In 1998, and again in 2000, LMTS
received the Dwight D. Eisenhower Award for Excellence, the SBA's
highest award for Small Business excellence. In 1998 we received the
award for excellence in the Services Category, and in 2000 we received
the award at Sandia National Laboratories for the category of Research
and Development. This prestigious national award recognizes LMTS'
commitment to using Small Businesses as subcontractors and suppliers.

**SBA Award of Distinction**. On June 4, 2001, the SBA presented us with
the SBA's Award of Distinction. This award was initiated in 1995 to
recognize large Federal contractors (approximately 2,500 business
entities). Only those that have exceptional Small Business
Subcontracting Programs (less than 2% of SBA's portfolio of large
contractors) are active recipients of the award. Less that 1% receive it
twice, as LM did this year. This award is a prerequisite for winning the
Dwight D. Eisenhower Award for Excellence.

**DMSOC Recognition**. Most notably, our Small Business Subcontracting
Program has been rated "Outstanding" 8 years in a row by DMSOC and has
exceeded SDB and WOSB subcontracting goals every year since inception of
the company in 1987.

**Billion Dollar Roundtable**. In May 2003 LM was inducted into the
Billion Dollar Roundtable (BDR) which honors U.S. corporations that
grant more than \$1 billion in contracts annually to minority and
woman-owned businesses. Established in 2001, the mission of the BDR is
to research, educate, and promote best practices in supply-chain
diversity.

## 7.3 Small Business Outreach Initiatives

LMTS takes a very active role in participating in Small Business
outreach programs and initiatives. In 2002, our Corporate Small Business
Programs Manager personally participated in excess of 30 government/
industry conferences, National Minority Supplier councils, Small
Business trade shows, fairs, and education and training conferences.
Through this active participation, we gain access to many qualified
Small Businesses and assist them in getting involved with the Lockheed
Martin Small Business Programs.

On MSOC, our Business Manager will be the LM lead participant in local
outreach programs such as those mentioned above, and involve our LM
Small Business Liaison Officer in appropriate meetings and conferences.

## 7.4 Small Business Training

An important feature of our Small Business program is the continuing
education of LM personnel in the area of Small Business participation.
In light of continuing changes in Federal legislation concerning Small
Business programs, it is essential to refresh original "schoolhouse"
education with current laws and changes in the FAR and NASA FAR
Supplement. To this end, LMTS conducts an Annual Small Business Training
Seminar for up to 60 personnel, including buyers, subcontract
administrators, technical personnel, and proposal writers. Topics
include:

What the program is and why it exists

Existing laws and recent legislative changes

What responsibility passes to contractors

Master Small Business Subcontracting Plans and Addendum.

LMSO MSOC personnel participate at least every other year in the LMTS
Small Business Seminar to maintain proficiency in the Small Business
function. This training feature of our Small Business Program provides
the foundation and support for LMSO to exceed our Small Business
participation requirements.

# 8.0 Management of Small Businesses

Our Small Business management approach concentrates on ensuring
effective performance of teammates and subcontractors. We place strong
emphasis on early identification of problems and full and open
communication across company and functional lines. Our teammates are
integrated into our daily work center reviews to maximize efficiency and
technical performance. Continuous communication minimizes the
requirement for internal management oversight. Well-defined subcontract
SOW and a Subcontract Management Plan (SMP), accurate and timely
reporting and reviews, and complete customer visibility into all aspects
of subcontractor activities ensure a fully integrated,
performance-oriented MSOC Team. Additionally, LMSO prepares the Data
Requirements Description (DRD) MSOC-JSC-0009, Small Business
Subcontracting Plan and Reports, submitting them in accordance with FAR
52.219-9 and NFS 1852.219-75. SF 294 Subcontracting Report for
Individual Contracts will be submitted semi-annually and at contract
completion to the NASA/JSC Contracting Officer. SF 295 Summary
Subcontract Report will be submitted semi-annually to NASA Headquarters,
Code K. These reports provide our small business metrics including
actual expenditures for the preceding quarter and the current fiscal
year. The report also details our LM Team's actions taken and
descriptions of our efforts to enhance Small Business, SDB, HubZone, and
WOSB utilization.

## 8.1 Small Business Subcontract Management Plan (SMP)

The SMP is developed during the phase-in period and supports the
subcontract between LMSO and our Small Business subcontractors. The SMP
is the "how to" document that describes how we interface with our
subcontractors for the successful execution of the contract. The SMP
describes the following:

Integrated operational team concept

Small Business relationship to the prime and other teammates

Prime/subcontractor contractual relationships

Small Business overall responsibilities

Specific Small Business responsibilities including communication,
reporting requirements, progress\
reviews, functional lead responsibilities, quality assurance (QA), and
business management responsibilities.

## 8.2 Subcontractor Evaluation

Performance evaluation is a key component of MSOC Small Business
performance. Daily assessment and feedback obtained by interacting with
Small Business employees is the foundation of our structured evaluation
process. For MSOC we apply several *best practices* that have greatly
enhanced relationships between LMSO and the subcontractors on similar
subcontracts.

**Subcontractor Evaluation System**. Our Subcontractor Evaluation System
is a written, quarterly evaluation of a subcontractor's performance in
the following five areas: program staffing, technical competence,
product quality, business relations, and cost/rate performance. Each of
these areas is tied directly to a subcontractor performance in meeting
or exceeding the performance thresholds contained in the CWBS. LMSO
functional managers rate the Small Businesses supporting their work
center and provide ratings and written comments to the LMSO Subcontract
Administrator. Ratings in the categories listed above are
Unsatisfactory, Marginal, Satisfactory, and Outstanding. The Program
Manager assigns an overall rating after review, and a formal package is
released to each company executive responsible for the program. This
process ensures top-level corporate insight into program performance and
ensures open access to and communication with Small Business top
management.

**Benefits of Subcontractor Evaluation**. By committing to a formal,
written evaluation of the subcontractor's performance, LMSO communicates
its assessment of overall performance to the subcontractor's top
management. Our evaluation facilitates corrective action, when required,
and identifies excellent performance when applicable. These reports have
proven highly successful in focusing subcontractor attention to program
performance, and continue to enhance prime/subcontractor communication.

**Subcontractor Program Management Reviews**. Another best practice is
implemented in our proposal for MSOC. LMSO employs Subcontractor Program
Reviews at least semi-annually in which we provide a status of program
performance and issues, review customer award fee evaluations, discuss
issues applicable to all subcontractors, and respond to
comments/questions from our subcontractors' senior management.
Subcontractor senior management and program managers attend these
reviews and provide open and candid dialogue on overall program
performance. These reviews are used to inform and foster teamwork and
close relationships. This proven process is highly effective on many LM
programs.

## 8.3 Requirements Flowdown

We manage our Small Businesses by flowing down all applicable contract
clauses and provisions and by establishing tailored subcontract
reporting. All subcontractors submit monthly inputs to LMSO's staffing
and financial data requirement submissions. After contract award, LMSO
will review each Small Business's reporting systems to ensure that their
systems are properly implemented and that data can be readily integrated
into LMSO financial system.

# 9.0 Small Business Summary

Our LMSO MSOC Small Business Subcontracting Plan exceeds the MSOC Small
Business requirement by providing Small Business participation in the
program and by providing companies of every Small Business type (SDB,
WOSB, VOSB, SDVOB, HUBZone, & HBCU/MI) the opportunity to participate.
We structured a plan that meets the customer's Small Business
participation goals in every category and offers our Small Business
subcontractors an opportunity to grow by allocating to them a broad
range of complex work assignments in integrated work centers across the
program. We selected high quality Small Businesses with excellent past
performance records to perform the allocated work.

Our Small Business Plan also supports NASA Small Business Programs with
*meaningful* *initiatives* that bring credibility and positive support
to our customer.

**We bring to the customer an award-winning Small Business Program and a
DMSOC-approved Master Small Business Subcontracting Plan that are the
foundations of our MSOC Small Business Subcontracting Plan. Our Small
Business approach offers the customer the *lowest risk* approach to
successfully execute the MSOC program. Our MSOC Small Business
Subcontracting Plan offers key features and benefits outlined in**
Figure G237155H.

+---------------------------------+------------------------------------+
| *Figure DRD9-4. LMSO Small      |                                    |
| Business Participation Features |                                    |
| and Benefits*                   |                                    |
+---------------------------------+------------------------------------+
| Small Business Participation    |                                    |
| Summary                         |                                    |
+---------------------------------+------------------------------------+
| RFP Requirements                | Mission Support Contract (MSOC)    |
|                                 | Team Features and Benefits         |
+---------------------------------+------------------------------------+
| Maximize Small Business         | -   Signed agreements with SDB,    |
| Participation                   |     WOSB, VOSB, HUBZone, HBCU/MI,  |
|                                 |     and SDVOB concerns provides    |
|                                 |     extensive growth opportunities |
|                                 |     for SBs                        |
|                                 |                                    |
|                                 | -   Provide multiple SB            |
|                                 |     Initiatives to strengthen the  |
|                                 |     center program without         |
|                                 |     impacting mission success or   |
|                                 |     increasing contract cost       |
+---------------------------------+------------------------------------+
| Comply with FAR 52.219-9 & NASA | -   DCMC award winning             |
| FAR Supplement 1852.219-73      |     subcontracting plan approved   |
|                                 |     for a three year period with   |
|                                 |     addendum tailored to MSOC      |
+---------------------------------+------------------------------------+
| Small Business Firms            | -   SB Subcontractor commitments   |
| Specifically Identified in      |     for CWBS support               |
| Proposal                        |                                    |
+---------------------------------+------------------------------------+
| Prime Commitment to Use Small   | -   Enforceable commitments        |
| Business Firms                  |     reflected in award fee plan    |
|                                 |                                    |
|                                 | -   LMSO exceeds RFP requirement   |
|                                 |     with commitment to subcontract |
|                                 |     of total contract value to SBs |
+---------------------------------+------------------------------------+
| Applicability of Appropriate    | -   Conservative interpretation to |
| NAICS Codes                     |     NAICS code applicability for   |
|                                 |     SB assignments                 |
+---------------------------------+------------------------------------+
| Small Business Participation in | -   Achieves RFP goals for SB      |
| Various Categories as of Total  |     utilization improving MSOC SB  |
| Contract Value                  |     program                        |
|                                 |                                    |
|                                 | -   Exceeds RFP total contract     |
|                                 |     value requirement              |
+---------------------------------+------------------------------------+
| Commitment to Use SDB Firms for | -   SDB participation accounts for |
| Targeted NAICS Codes            |     of total contract value        |
+---------------------------------+------------------------------------+
| Our small business program      |                                    |
| supports all MSOC requirements  |                                    |
| and maintains low risk to       |                                    |
| mission performance.            |                                    |
+---------------------------------+------------------------------------+
| G237155H                        |                                    |
+---------------------------------+------------------------------------+

# ADDENDUM A TO MASTER SUBCONTRACTNG PLAN

**Subcontracting Plan in accordance with PL95-507**

1a. Solicitation Number RFP 9-BH5-JBQ-03-01P

1b. Proposal Number 6079A-03D

1c. Agency NASA, Lyndon B. Johnson Space Center

Houston, TX 77058

Point of Contact -- Contracting Officer Caroline Marrs Root

1d. Contract Term Base Period: January 1, 2004 through\
September 30, 2004

Option: October 1, 2004 through\
September 30, 2006

2\. Contractor Name Lockheed Martin Technology Services

3\. Person completing this Plan Julie E. Paglione

856/486-5977

4\. Total Value of Proposal 5a. Estimated Value of Materials/\
Subcontracts (including options)

5b. **Goals -- based on [Total contract value]{.underline}:**

**[Maximum Performance Period -- January 1, 2004 through September 30,
2006]{.underline}**

**Subcontracted Dollars:**

  ---------------------------------- ----------------------- --------------------
                                     [Dollars]{.underline}   Percentage of Total
                                                             [Subcontract
                                                             Value]{.underline}

  Small Business Concerns                                    

  Small Disadvantaged Business                               

  Woman-Owned Business                                       

  Veteran-Owned Business                                     

  HUBZone                                                    

  Service Disabled Veteran-Owned                             

  HBCU/MI                                                    

  Large Business Concerns                                    
  ---------------------------------- ----------------------- --------------------

> Indirect cost is not included in establishing the subcontracting goals

5c. **Goals -- based on [subcontracted value]{.underline}:**

> **[Maximum Performance Period -- January 1, 2004 through September 30,
> 2006]{.underline}**

  ---------------------------------- ----------------------- --------------------
                                     [Dollars]{.underline}   Percentage of Total
                                                             [Subcontract
                                                             Value]{.underline}

  Small Business Concerns                                    

  Small Disadvantaged Business                               

  Woman-Owned Business                                       

  Veteran-Owned Business                                     

  HUB-Zone                                                   

  Service Disabled Veteran-Owned                             

  HBCU/MI                                                    

  Large Business Concerns                                    
  ---------------------------------- ----------------------- --------------------

Although our team exceeds the NASA JSC desired Small Business
participation of of total contract value, our SDB participation
percentage is less than the desired. LM will endeavor to increase this
percentage during MSOC performance. The increased participation will be
achieved by a combination of assignment of new tasks and shift of
baseline tasks to SDBs to the greatest extent practicable.

**6. [METHOD OF DEVELOPMENT OF SUBCONTRACTING GOALS:]{.underline}**

Goals were established based on the review of the RFP requirements and
evaluations of potential subcontractors capable of performing various
tasks and adding strength to the LM Team.

Goals and percentages are submitted based on two formats in accordance
with the RFP and FAR:

Goals as a percentage of total contract / proposal value (Item 5b.
above)

Goals as a percentage of estimated subcontracted dollars (Item 5c.
above)

**7. [PRINCIPAL PRODUCT AND SERVICE AREAS:]{.underline}**

This proposal offers subcontract opportunities for development and
testing, operations & maintenance, software development, training, and
engineering services. Lockheed Martin will retain overall responsibility
for the Mission Support Operations Contract management and
administration activities. We have identified the small business
concerns in **Figure SBP-1** as available for participation.

The assignment of the CWBS paragraphs assigned to is consistent with
their managerial and technical capabilities, and also considers their
relevant past performance.

8\. Small Disadvantaged Business (SDB), HUB-Zone Small Business,
Veteran-Owned Small Business, Service Disabled Veteran-Owned, and Small
Woman-Owned Business concerns have been considered when arriving at the
subcontracting goals in this plan. See Addendum C for Small Business
Administration PRO-Net Firm Profiles for these concerns.

9\. Historically Black Colleges and Universities (HBCU) and Minority
Institutions (MIs) have been considered in arriving at the
subcontracting goals in the plan

10\. Lockheed Martin Technology Services is constantly striving to
identify potential sources for solici­tation purposes and to increase the
level of business participation by small, small disadvantaged and
women-owned small business concerns in furnishing Lockheed Martin
products and services. We shall continue to locate additional sources
through the use of vendor locating methods and through the local
Chambers of Commerce, the National Minority Supplier Development
Councils, and publications such as Try Us and the National Directory of
Minority and Women-Owned Business.

11\. In 1998, Technology Services received the U.S. Small Business
Administration's Dwight D. Eisenhower Award for Excellence in the
Services category, and in 2000, Sandia National Laboratories received
the Eisenhower Award in the Research & Development category. This
prestigious National Award (the highest given by the Small Business
Administration) recognizes our commitment to using small businesses as
subcontractors and suppliers.

12\. On June 4, 2001, the Small Business Administration (SBA) presented
Lockheed Martin Technology Services with the SBA's Award of Distinction.
This Award was initiated in 1985 to recognize large Federal contractors
(there are approximately 2,500 business entities in this category). Only
those that have exceptional Small Business Subcontracting Programs,
which is less than 2% of SBA's portfolio of large contractors, are
active recipients of this award. Less than 1% receives it twice, as
Lockheed Martin Technology Services did on June 4. This award is the
prerequisite for winning the Dwight D. Eisenhower Award for Excellence.
Lockheed Martin Technology Services has been recognized by the Defense
Logistics Agency for its OUTSTANDING Small Business Program and has
received the OUTSTANDING RATING eight years in a row.

13\. Method used to identify potential sources for solicitation
purposes:

Review and analysis of:

Procurement possibilities for commodities not listed as a mandatory
source.

Make-or-buy process, as applicable.

Cost Information Requests (CIRs).

Computerized compilation of material costs and identification by part
number, of vendors available to provide those commodities.

Develop and utilize alternatives to low-price contract awards in order
to increase HUB-Zone small, SDB, WOSB and HBCU/MI participation when
required.

**Duties of the Minority and Small Business Administrator:**

A. Inform and assist Buyers in locating and using appropriate Small,
Small Disadvantaged and Woman-Owned Small Business sources of supply.

B. Respond to inquiries from potential vendors and ensure they are
brought together with Buyers and other appropriate people who may be
able to use their products and services.

C. Review subcontract potential for Small, Small Disadvantaged and
Woman-Owned Small Business participation on specific contracts.

D. Participate in make-or-buy decisions and identify maximum practical
opportunities for these firms.

E. Participate in establishment of relevant subcontract goals and
monitor performance.

F. Collect data and report on achievements are required.

G. As LM representative, attend monthly Delaware Valley Minority
Business Resource Council (formerly Minority Purchasing Council)
meetings, participate as an active member of The Houston Minority
Business Council, attend trade fairs and seminars for Small, Small
Disadvantaged and Woman-Owned Small Business Concerns, attends a
National Minority Supplier Development Council (NMSDC) on a yearly
basis.

H. Assist in development of seminars that cover updating of Public Law
95-507 requirements (i.e., through participation in TRIAD Seminars and
in-house programs to assist Buyers in expanding contracts with Small,
Small Disadvantaged and Woman-Owned Small Business Concerns.) Report to
the Manager of Procurement for Lockheed Martin who fully supports
Lockheed Martin Minority Business Advisory Group.

I. Report to the Manager of Procurement for Lockheed Martin Services,
Inc. who fully supports Lockheed Martin Services Minority Business
Advisory Group.

3\. [EFFORTS TO ASSURE EQUITABLE OPPORTUNITIES]{.underline}

Lockheed Martin will take the following steps to assure that Small,
Small Disadvantaged and Woman-owned Small Business Concerns will have an
equitable opportunity to compete for Subcontracts:

a\) Issue and promulgate company-wide policy statements in support of
this effort, develop written procedures and work instructions, and
assign specific responsibilities regarding the requirements of this
clause.

b\) Demonstrate continuing management interest and involvement in
support of this effort through such actions as regular reviews of
progress and establishment of overall corporate and divisional goals and
objectives.

c\) Train and motivate Lockheed Martin Personnel regarding the support
of Small, Small Disadvantaged and Woman-Owned Small Business Concerns.

d\) Provide adequate and timely consideration of the potentialities of
Small, Small Disadvantaged and Woman-Owned Small Business Concerns in
all "make-or-buy" decisions.

e\) Counsel and discuss subcontracting opportunities with
representatives of Small, Small Disadvantaged and Woman-Owned Small
Business Concerns.

f\) Provide notice to subcontractors concerning penalties and remedies
for misrepresentation of business status as Small, Small Disadvantaged
and Woman-Owned Small Business for the purpose of obtaining a
subcontract that is to be included as part or all of a goal contained in
the Contractor's subcontracting plan.

g\) Maintain company source lists of potential vendors/subcontractors
who are qualified Small, Small Disadvantaged and Woman-Owned Small
Business concerns. Such lists will be compiled and updated from company
sources and the source identification system provided by the Small
Business Administration's Procurement Automated Source System.

h\) Utilize, where subcontracting opportunities exist, its Small, Small
Disadvantaged and Woman-Owned Small Business Concerns list to select and
solicit a minimum of three such qualified concerns to bid for such
business opportunities.

i\) Assist Small, Small disadvantaged and Woman-Owned Small Business
Concerns whenever possible by counseling them on how to do business with
Lockheed Martin by arranging solicitations, allowing sufficient time for
the preparation of bids, quantities, specifications, and delivery
schedules so as to facilitate the participation by such concerns. Where
the available lists of potential Small, Small Disadvantaged and
Woman-Owned Small Business subcontractors are excessively long,
reasonable effort shall be made to give all such small business concerns
an opportunity to compete over a period of time.

4\. [UTILIZATION OF SMALL, SMALL DISADVANTAGED AND WOMAN-OWNED SMALL
BUSINESS CONCERNS CLAUSE]{.underline}

Lockheed Martin assures that the clause as stated in the applicable
Federal Acquisition Regulations 52.219-8 and 52.219-9 statutory
requirements, entitled, "Utilization of Small, Small Disadvantaged and
Woman-Owned Small Business concerns," and, "Small, Small Disadvantaged
and Woman-Owned Small Business Subcontracting Plan," respectively, will
be included in all subcontracts which offer further subcontracting
opportunities and will require all subcontractors (except small business
concerns) who receive subcontracts in excess of \$500,000 or, in the
case of a contract for the construction of any public facility, \$1
million, to adopt and comply with a subcontracting plan as required by
this clause.

5\. [PERIODIC REPORTS AND COOPERATION IN SURVEYS]{.underline}

Lockheed Martin will submit such period reports and cooperate in studies
or surveys as may be required by the contracting agency or the Small
Business Administration in order to determine the extent of compliance
by Lockheed Martin with the Subcontracting Plan. Such reports will
include the Subcontracting Report for individual contracts, Standard
Form SF 294 (required semi-annually), and the Summary Subcontracting
Report, Standard Form SF 295 (required semi-annually) and ensure its
subcontractors agree to submit standard forms 294 and 295.

6\. [MAINTENANCE OF RECORDS]{.underline}

Lockheed Martin will maintain records which will demonstrate procedures
that have been adopted to comply with the requirements and goals set
forth in this plan. These records will include:

a\) Company source lists of potential vendors/subcontractors who are
qualified Small, Small Disadvantaged and Woman-Owned Small Business
concerns. Such lists will be compiled and updated from company sources
and the source identification system provided by the Small Business
Administrations Automated Source system, and input derived from the
customer.

b\) Publications, guides and other data identifying Small, Small
disadvantaged and Woman-Owned Small Business vendors.

c\) Lists of organizations contacted for Small, Small Disadvantaged and
Woman-Owned Small Business vendors.

d\) Provide information to Lockheed Martin Corporate Director of
Minority Programs relative to bestowing awards to Small, Small
Disadvantaged and Woman-Owned Small Business concerns.

e\) Maintain records to support internal activities to guide and
encourage buyers, such as:

1\) workshops, seminars, training programs, etc., and

2\) monitoring activities to evaluate compliance,

3\) contacts with Small, Small Disadvantaged and Woman-Owned Small
Business trade associations

4\) contacts with business development organizations; and

5\) attendance at Small, Small Disadvantaged and Woman-Owned Small
Business procurement conferences and trade fairs.

f\) Records on each subcontract solicitation resulting in an award of
more than \$100,000 indicating:

1\) whether small business concerns was solicited; and if not, why not;

2\) whether small disadvantaged business concerns was solicited, and if
not, why not;

3\) whether woman-owned small business concerns was solicited; and if
not why not; and

> 4\) reasons for the failure of solicited small, small disadvantaged
> and woman-owned small business to receive the subcontract award.

ADDENDUM B

TO

MASTER SUBCONTRACTNG PLAN

SUBCONTRACTOR

LETTERS OF COMMITMENT

ADDENDUM C

TO

MASTER SUBCONTRACTNG PLAN

Pro-Net Firm Profiles

##  {#section-68}

## Mentor/Protege Data

Interested in participating in a mentor/protege program?:

\[X\] Yes \[  \] No

This company is interested in participating in a mentor/protege program
in the following areas.

  ----------------------- -----------------------------------------------
  \[  \] Yes \[X\] No     Sales and Marketing

  \[  \] Yes \[X\] No     Production

  \[  \] Yes \[X\] No     Finance

  \[X\] Yes \[  \] No     Research and Development

  \[  \] Yes \[X\] No     Human Resources Development

  \[  \] Yes \[X\] No     General Management

  \[  \] Yes \[X\] No     Strategic Planning

  \[  \] Yes \[X\] No     International

  \[X\] Yes \[  \] No     Other: Software Development
  ----------------------- -----------------------------------------------

## Performance/History References

### Federal Agency or Prime Contractor

  ----------- ------------------------------------------------------------
  Name:       Department of Labor Employment Training Administration

  Contract:   

  Start:      09/01/1996

  End:        12/31/2000

  Value:      24,256,283

  Contact:    Linda Estep

  Phone:      202-219-8550
  ----------- ------------------------------------------------------------

### Other Major Customer Name

  ----------- ------------------------------------------------- -- -- -- ------
  Name:                                                                  

  Contract:   ISS                                                        

  Start:      10/01/2000                                                 

  End:        09/30/2004                                                 

  Value:      80,000,000                                                 

  Contact:    Joseph Derringer                                           

  Phone:      281-244-4197                                               

  Name:       Lockheed Martin Space Operations                           

  Contract:                                                              

  Start:      10/01/1998                                                 

  End:        09/30/2004                                                 

  Value:      106,781,307                                                

  Contact:    Doug Tighe                                                 

  Phone:      281-853-3030                                               

  Name:       Lockheed Martin                                            

  Contract:                                                              

  Start:      09/01/1994                                                 

  End:        12/31/2001                                                 

  Value:      10,309,565                                                 

  Contact:    Judy Wheaton                                               

  Phone:      228-688-2973                                               

  Name:       Lockheed Martin Information Technology (LMIT)              

  Contract:                                                              

  Start:      08/01/1999                                                 

  End:        12/31/2003                                                 

  Value:      3,967,874                                                  

  Contact:    Tanya Bouldware                                            

  Phone:      301-220-7159                                               

  Name:       Lockheed Martin Space Mission Systems & Services           

  Contract:                                                              

  Start:      08/01/1992                                                 

  End:        12/10/1999                                                 

  Value:      30,000,000                                                 

  Contact:    Steve Bloom                                                

  Phone:      281-335-6557                                               
  ----------- ------------------------------------------------- -- -- -- ------

The structure of this page was last updated 03/20/2003, as part of
PRO-Net 4.3.9.1.

# PRO-Net Firm Profile

[**Privacy
Statement**](http://pro-net.sba.gov/cgi-bin/closemesba.pl?TO=http://www.sba.gov/privacy.html)

## Identification Data

  ------------------------------------------------- ---------------------
  This profile was last updated:                    06/16/2003

  Name of Firm:                                     

  Trade Name:                                       

  Main office or branch office?:                    

  Address, line 1:                                  

  Address, line 2:                                  

  City:                                             

  State:                                            

  Zip:                                              

  Phone Number:                                     

  Fax Number:                                       

  E-mail Address:                                   

  WWW Page:                                         

  E-Mall (electronic mall\                           
  selling firm\'s products):                        

  Contact Person:                                   

  Contact Title:                                    

  County Code (3 digit):                            

  Congressional District:                           

  Metropolitan Statistical Area:                    

  DUNS Number:                                      

  CAGE Code:                                        

  Year Established:                                 

  Average Number of Employees:                      

  Average Annual Gross Revenue:                     

  Accepts Government Credit Card?:                  \[X\] Yes \[  \] No

  GSA Advantage Contract:                           
  ------------------------------------------------- ---------------------

## Organizational/Ownership Data

  ---------------------------------------------------------------------------------- ----------------------
  Legal Structure:                                                                   Corporation

  Minority Code:                                                                     Hispanic American

  Women-Owned?:                                                                      \[  \] Yes \[X\] No

  Veteran?:                                                                          \[X\] Yes \[  \] No

  Service Disabled Veteran?:                                                         \[X\] Yes \[  \] No

  Vietnam Veteran?:                                                                  \[X\] Yes \[  \] No

  Registered in DoD [Central Contractor                                              \[X\] Yes \[  \] No
  Registration](http://pro-net.sba.gov/cgi-bin/closeme.pl?TO=http://www.ccr.gov/)?   

                                                                                      

  **Current Principals:**                                                            (Name, Title)

                                                                                     Israel Galvan,
                                                                                     President

                                                                                      

  **Business Development Servicing Office** (for certifications):                    

  HOUSTON (SBA office code 0671)                                                     

                                                                                      

  **8(a) Certification:**                                                             

  SBA 8(a) Case Number:                                                              

  SBA 8(a) Entrance Date:                                                            

  SBA 8(a) Exit Date:                                                                

                                                                                      

  **Small Disadvantaged Business Certification:**                                    

  SDB Entrance Date:                                                                 

  SDB Exit Date:                                                                     

                                                                                      

  **HUB Zone Certified?:**                                                           \[  \] Yes \[X\] No

  **HUB Zone Certification Date:**                                                   N/A

                                                                                      

  **Non Federal Government Certifications:**                                          
  ---------------------------------------------------------------------------------- ----------------------

## Products & Services Data

### Capabilities Narrative:

Software Development, Safety, Reliability & Quality Assurance, Ground
Network Support, Networking, Desktop Support and ISP. Web-based Time
Management Software, HR Software, and Recruiting and Staffing Software.

### Special Equipment/materials:

### Business Types (Construction, Manufacturing, R&D and/or Service):

  --------------------------------------------------------------------------------------------------------- --------------------------------
  **Business Type Percentages:**                                                                            Research & Development (55.0 %)\
                                                                                                            Service (45.0 %)

                                                                                                             

  Construction Bonding Level (per contract)                                                                 00000000

  Construction Bonding Level (aggregate)                                                                    00000000

  Service Bonding Level (per contract)                                                                      00000000

  Service Bonding Level (aggregate)                                                                         00000000

                                                                                                             

  **Firm has had TECH-*Net* award(s), R&D-related:**                                                        

  [SYSTEMS                                                                                                  
  TECHNOLOGY](http://tech-net.sba.gov/sybase-bin/tech-net.cgi?FNC=firmlist_submit__Afirmlist_html___2145)   
  --------------------------------------------------------------------------------------------------------- --------------------------------

### Codes and Keywords:

  --------------------- -------------------------------------------------
  Primary NAICS Code:   541710

  Other NAICS Codes:    334611, 421430, 513330, 541511, 541512, 541513,
                        541519, 541720

  \"Buy Green\" NAICS   
  Codes:                

  Keywords:             Development, R&D, Research, Engineering, Software

  Quality Assurance     ISO-9000 Series
  Standards:            
  --------------------- -------------------------------------------------

##  {#section-69}

## Miscellaneous Data 

  -------------------------------------------------- --------------------
  Electronic Data Interchange capable?:              \[X\] Yes \[  \] No

  Exporter?:                                         Wants to Be
  -------------------------------------------------- --------------------

##  {#section-70}

## Mentor/Protege Data

Interested in participating in a mentor/protege program?:

\[X\] Yes \[  \] No

This company is interested in participating in a mentor/protege program
in the following areas.

  ----------------------- -----------------------------------------------
  \[X\] Yes \[  \] No     Sales and Marketing

  \[  \] Yes \[X\] No     Production

  \[  \] Yes \[X\] No     Finance

  \[X\] Yes \[  \] No     Research and Development

  \[X\] Yes \[  \] No     Human Resources Development

  \[  \] Yes \[X\] No     General Management

  \[X\] Yes \[  \] No     Strategic Planning

  \[  \] Yes \[X\] No     International

  \[  \] Yes \[X\] No     Other:
  ----------------------- -----------------------------------------------

## Performance/History References

### Federal Agency or Prime Contractor

### Other Major Customer Name

The structure of this page was last updated 03/20/2003, as part of
PRO-Net 4.3.9.1.

# PRO-Net Firm Profile

[**Privacy
Statement**](http://pro-net.sba.gov/cgi-bin/closemesba.pl?TO=http://www.sba.gov/privacy.html)

## Identification Data

  ------------------------------------------------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  This profile was last updated:                    12/17/2002

  Name of Firm:                                     

  Trade Name:                                       

  Main office or branch office?:                    

  Address, line 1:                                  

  Address, line 2:                                  

  City:                                             

  State:                                            

  Zip:                                              

  Phone Number:                                     

  Fax Number:                                       

  E-mail Address:                                   

  WWW Page:                                         

  E-Mall (electronic mall\                          
  selling firm\'s products):                        

  Contact Person:                                   

  Contact Title:                                    

  County Code (3 digit):                            

  Congressional District:                           

  Metropolitan Statistical Area:                    

  DUNS Number:                                      

  CAGE Code:                                        

  Year Established:                                 

  Average Number of Employees:                      

  Average Annual Gross Revenue:                     

  Accepts Government Credit Card?:                  \[  \] Yes \[X\] No

  GSA Advantage Contract:                           [GS-35F-0365J](http://pro-net.sba.gov/cgi-bin/closeme.pl?TO=http://www.gsaadvantage.gov/advgsa/main_pages/elibrary_zipcode.jsp%3Fquerytext%3DGS-35F-0365J%26source%3Dpronet)
  ------------------------------------------------- ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

## Organizational/Ownership Data

  ---------------------------------------------------------------------------------- ------------------------------
  Legal Structure:                                                                   Subchapter S Corporation

  Minority Code:                                                                     

  Women-Owned?:                                                                      \[  \] Yes \[X\] No

  Veteran?:                                                                          \[  \] Yes \[X\] No

  Service Disabled Veteran?:                                                         \[  \] Yes \[X\] No

  Vietnam Veteran?:                                                                  \[  \] Yes \[X\] No

  Registered in DoD [Central Contractor                                              \[X\] Yes \[  \] No
  Registration](http://pro-net.sba.gov/cgi-bin/closeme.pl?TO=http://www.ccr.gov/)?   

                                                                                      

  **Current Principals:**                                                            (Name, Title)

                                                                                     Brian K. Horn, Chief Financial
                                                                                     Officer

                                                                                     Bruce C. Larsen, President

                                                                                     Dr. Frederick J. Hawkins, CEO

                                                                                     George R. Sauble, Vice
                                                                                     President

                                                                                     Scott D. Miller, Vice
                                                                                     President

                                                                                      

  **Business Development Servicing Office** (for certifications):                    

  WASHINGTON, DC (SBA office code 0353)                                              

                                                                                      

  **8(a) Certification:**                                                             

  SBA 8(a) Case Number:                                                              

  SBA 8(a) Entrance Date:                                                            

  SBA 8(a) Exit Date:                                                                

                                                                                      

  **Small Disadvantaged Business Certification:**                                    

  SDB Entrance Date:                                                                 

  SDB Exit Date:                                                                     

                                                                                      

  **HUB Zone Certified?:**                                                           \[  \] Yes \[X\] No

  **HUB Zone Certification Date:**                                                   N/A

  **Non Federal Government Certifications:**                                          

                                                                                     ISO 9001 Team Member

                                                                                     MS Solutions -

                                                                                     Provider in process
  ---------------------------------------------------------------------------------- ------------------------------

##  {#section-71}

## Products & Services Data

### Capabilities Narrative:

IT SECURITY, SYSTEMS ENGINEERING, MISSION ANALYSIS AND OPERATIONS,
SPACECRAFT SYSTEMS, FLIGHT SOFTWARE, REALTIME SYSTEMS DEVELOPMENT,
SPECIALIZED HARDWARE DEVELOPMENT, ENGINEERING DISCIPLINE SUPPORT,
ARTIFICIAL INTELLIGENCE, ROBOTICS.

### Special Equipment/materials:

### Business Types (Construction, Manufacturing, R&D and/or Service):

  -------------------------------------- --------------------------------
  **Business Type Percentages:**         Research & Development (100.0 %)

                                          

  Construction Bonding Level (per        00000000
  contract)                              

  Construction Bonding Level (aggregate) 00000000

  Service Bonding Level (per contract)   00000000

  Service Bonding Level (aggregate)      00000000
  -------------------------------------- --------------------------------

###  {#section-72}

### Codes and Keywords:

  ------------ -----------------------------------------------------------
  Primary      541330
  NAICS Code:  

  Other NAICS  
  Codes:       

  \"Buy        
  Green\"      
  NAICS Codes: 

  Keywords:    Aerospace Eng., Architecture Design, Astrodynamics, Command
               and Control, Data Systems, Flight Software, Ground Systems,
               H/W Development, Info. Security, Information Tech.,
               Integration & Test, Launch Systems, Mission Operations,
               Network Security, Sensors, Orbital Analysis, Science Data
               Proc., Science Operations, Software Development, Systems
               Engineering, Systems Integration, Test Planning, Tradeoff
               Analysis, Training

  Quality      ISO-9000 Series
  Assurance    
  Standards:   
  ------------ -----------------------------------------------------------

##  {#section-73}

## Miscellaneous Data

  -------------------------------------------------- --------------------
  Electronic Data Interchange capable?:              \[  \] Yes \[X\] No

  Exporter?:                                         Yes
  -------------------------------------------------- --------------------

##  {#section-74}

## Mentor/Protege Data

Interested in participating in a mentor/protege program?:

\[  \] Yes \[X\] No

## Performance/History References

### Federal Agency or Prime Contractor

### Other Major Customer Name

The structure of this page was last updated 03/20/2003, as part of
PRO-Net 4.3.9.1.

# PRO-Net Firm Profile

[**Privacy
Statement**](http://pro-net.sba.gov/cgi-bin/closemesba.pl?TO=http://www.sba.gov/privacy.html)

## Identification Data

  ---------------------------------------------------- ------------------
  This profile was last updated:                       06/03/2003

  Name of Firm:                                        

  Trade Name:                                          

  Main office or branch office?:                       

  Address, line 1:                                     

  Address, line 2:                                     

  City:                                                

  State:                                               

  Zip:                                                 

  Phone Number:                                        

  Fax Number:                                          

  E-mail Address:                                      

  WWW Page:                                            

  E-Mall (electronic mall\                             
  selling firm\'s products):                           

  Contact Person:                                      

  Contact Title:                                       

  County Code (3 digit):                               

  Congressional District:                              

  Metropolitan Statistical Area:                       

  DUNS Number:                                         

  CAGE Code:                                           

  Year Established:                                    

  Average Number of Employees:                         

  Average Annual Gross Revenue:                        

  Accepts Government Credit Card?:                     

  GSA Advantage Contract:                              
  ---------------------------------------------------- ------------------

## Organizational/Ownership Data

  ---------------------------------------------------------------------------------- --------------------------
  Legal Structure:                                                                   Corporation

  Minority Code:                                                                     

  Women-Owned?:                                                                      \[X\] Yes \[  \] No

  Veteran?:                                                                          

  Service Disabled Veteran?:                                                         

  Vietnam Veteran?:                                                                  \[  \] Yes \[X\] No

  Registered in DoD [Central Contractor                                              \[X\] Yes \[  \] No
  Registration](http://pro-net.sba.gov/cgi-bin/closeme.pl?TO=http://www.ccr.gov/)?   

                                                                                      

  **Current Principals:**                                                            (Name, Title)

                                                                                     E.J. Cook,
                                                                                     Secretary/Treasurer

                                                                                     Linda A. Cook, President

                                                                                      

  **Business Development Servicing Office** (for certifications):                    

  HOUSTON (SBA office code 0671)                                                     

                                                                                      

  **8(a) Certification:**                                                             

  SBA 8(a) Case Number:                                                              

  SBA 8(a) Entrance Date:                                                            

  SBA 8(a) Exit Date:                                                                

                                                                                      

  **Small Disadvantaged Business Certification:**                                    

  SDB Entrance Date:                                                                 

  SDB Exit Date:                                                                     

                                                                                      

  **HUB Zone Certified?:**                                                           \[X\] Yes \[  \] No

  **HUB Zone Certification Date:**                                                   05/31/2002

                                                                                      

  **Non Federal Government Certifications:**                                          
  ---------------------------------------------------------------------------------- --------------------------

## Products & Services Data

### Capabilities Narrative:

. is a WOMAN OWNED SMALL HUBZONE CERTIFIED BUSINESS. PRINCIPLE has been
providing SUBCONTRACT LABOR HOUR contracting and placement services to
Houston AEROSPACE firms since 1986. has 20 years experience in
GOVERNMENT CONTRACTING.

### Special Equipment/materials:

Hi-Tech consultants and Contractors, Engineers fo all disciplines, SW
Specialists, System and SW Requirements analysts, SW Engineers, Database
Administrators, System & SW Testers, Oracle Programmers, Contract
Administators,Specialty Aerospace positions

### Business Types (Construction, Manufacturing, R&D and/or Service):

  ------------------------------------------------- ---------------------
  **Business Type Percentages:**                    Service (100.0 %)

                                                     

  Construction Bonding Level (per contract)         00000000

  Construction Bonding Level (aggregate)            00000000

  Service Bonding Level (per contract)              00000000

  Service Bonding Level (aggregate)                 00000000
  ------------------------------------------------- ---------------------

### Codes and Keywords:

  ----------------- -----------------------------------------------------
  Primary NAICS     541330
  Code:             

  Other NAICS       514210, 541219, 541511, 541519, 541710, 561310,
  Codes:            561320

  \"Buy Green\"     
  NAICS Codes:      

  Keywords:         Aerospace, Engineer, IT, Software, Development,
                    Computer, Project, Management, Payroll, HubZone

  Quality Assurance 
  Standards:        
  ----------------- -----------------------------------------------------

##   {#section-75}

##  {#section-76}

## Miscellaneous Data

  -------------------------------------------------- --------------------
  Electronic Data Interchange capable?:              \[  \] Yes \[X\] No

  Exporter?:                                         No
  -------------------------------------------------- --------------------

##  {#section-77}

## Mentor/Protege Data

Interested in participating in a mentor/protege program?:

\[X\] Yes \[  \] No

This company is interested in participating in a mentor/protege program
in the following areas.

  ----------------------- -----------------------------------------------
  \[  \] Yes \[X\] No     Sales and Marketing

  \[X\] Yes \[  \] No     Production

  \[  \] Yes \[X\] No     Finance

  \[X\] Yes \[  \] No     Research and Development

  \[X\] Yes \[  \] No     Human Resources Development

  \[  \] Yes \[X\] No     General Management

  \[  \] Yes \[X\] No     Strategic Planning

  \[X\] Yes \[  \] No     International

  \[  \] Yes \[X\] No     Other:
  ----------------------- -----------------------------------------------

## Performance/History References

### Federal Agency or Prime Contractor

### Other Major Customer Name

The structure of this page was last updated 03/20/2003, as part of
PRO-Net 4.3.9.1.

# PRO-Net Firm Profile

[**Privacy
Statement**](http://pro-net.sba.gov/cgi-bin/closemesba.pl?TO=http://www.sba.gov/privacy.html)

## Identification Data

  ---------------------------------------------------- ------------------
  This profile was last updated:                       12/19/2002

  Name of Firm:                                        

  Trade Name:                                          

  Main office or branch office?:                       

  Address, line 1:                                     

  Address, line 2:                                     

  City:                                                

  State:                                               

  Zip:                                                 

  Phone Number:                                        

  Fax Number:                                          

  E-mail Address:                                      

  WWW Page:                                            

  E-Mall (electronic mall\                             
  selling firm\'s products):                           

  Contact Person:                                      

  Contact Title:                                       

  County Code (3 digit):                               

  Congressional District:                              

  Metropolitan Statistical Area:                       

  DUNS Number:                                         

  CAGE Code:                                           

  Year Established:                                    

  Average Number of Employees:                         

  Average Annual Gross Revenue:                        

  Accepts Government Credit Card?:                     

  GSA Advantage Contract:                              
  ---------------------------------------------------- ------------------

## Organizational/Ownership Data

  ---------------------------------------------------------------------------------- ------------------------
  Legal Structure:                                                                   Corporation

  Minority Code:                                                                     Hispanic American

  Women-Owned?:                                                                      \[  \] Yes \[X\] No

  Veteran?:                                                                          \[  \] Yes \[X\] No

  Service Disabled Veteran?:                                                         \[  \] Yes \[X\] No

  Vietnam Veteran?:                                                                  \[  \] Yes \[X\] No

  Registered in DoD [Central Contractor                                              \[X\] Yes \[  \] No
  Registration](http://pro-net.sba.gov/cgi-bin/closeme.pl?TO=http://www.ccr.gov/)?   

                                                                                      

  **Current Principals:**                                                            (Name, Title)

                                                                                     Jorge Hernandez,
                                                                                     President

                                                                                      

  **Business Development Servicing Office** (for certifications):                    

  HOUSTON (SBA office code 0671)                                                     

                                                                                      

  **8(a) Certification:**                                                             

  SBA 8(a) Case Number:                                                              105569

  SBA 8(a) Entrance Date:                                                            01/12/2000

  SBA 8(a) Exit Date:                                                                01/12/2009

                                                                                      

  **Small Disadvantaged Business Certification:**                                    

  SDB Entrance Date:                                                                 01/12/2000

  SDB Exit Date:                                                                     01/12/2009

                                                                                      

  **HUB Zone Certified?:**                                                           \[  \] Yes \[X\] No

  **HUB Zone Certification Date:**                                                   N/A

  **Non Federal Government Certifications:**                                          
  ---------------------------------------------------------------------------------- ------------------------

## Products & Services Data

### Capabilities Narrative:

Analysis, Design, Configuration Management, CAD, Dynamics, Risk,
Programming, Software, Web design, Database Development, Thermal,
Stress, Unigraphics, NASTRAN

### Special Equipment/materials:

Unigraphics, CATIA, PRO/Engineer, ProE, NASTRAN

### Business Types (Construction, Manufacturing, R&D and/or Service):

  -------------------------------------- --------------------------------
  **Business Type Percentages:**         Research & Development (10.0 %)\
                                         Service (90.0 %)

                                          

  Construction Bonding Level (per        00000000
  contract)                              

  Construction Bonding Level (aggregate) 00000000

  Service Bonding Level (per contract)   00000000

  Service Bonding Level (aggregate)      00000000
  -------------------------------------- --------------------------------

### Codes and Keywords:

  ------------ ----------------------------------------------------------
  Primary      
  NAICS Code:  

  Other NAICS  514210, 541330, 541511, 541512, 541513, 541519, 541620,
  Codes:       541690, 541710, 541990, 561110, 561210, 611430

  \"Buy        
  Green\"      
  NAICS Codes: 

  Keywords:    3D Modeling, Analysis, Config. Management, CAD, Design,
               Dynamics, Facility, NASTRAN, Operations, Pro/Engineer,
               ProE, Quality, Risk, Safety, Software, Stress, Thermal,
               Training, Unigraphics, iman, CATIA

  Quality      ISO-9000 Series
  Assurance    
  Standards:   
  ------------ ----------------------------------------------------------

##   {#section-78}

##  {#section-79}

## Miscellaneous Data

  -------------------------------------------------- --------------------
  Electronic Data Interchange capable?:              \[X\] Yes \[  \] No

  Exporter?:                                         No
  -------------------------------------------------- --------------------

##  {#section-80}

## Mentor/Protege Data

Interested in participating in a mentor/protege program?:

\[X\] Yes \[  \] No

This company is interested in participating in a mentor/protege program
in the following areas.

  ----------------------- -----------------------------------------------
  \[  \] Yes \[X\] No     Sales and Marketing

  \[  \] Yes \[X\] No     Production

  \[  \] Yes \[X\] No     Finance

  \[X\] Yes \[  \] No     Research and Development

  \[  \] Yes \[X\] No     Human Resources Development

  \[  \] Yes \[X\] No     General Management

  \[  \] Yes \[X\] No     Strategic Planning

  \[  \] Yes \[X\] No     International

  \[  \] Yes \[X\] No     Other:
  ----------------------- -----------------------------------------------

## Performance/History References

### Federal Agency or Prime Contractor

### Other Major Customer Name

The structure of this page was last updated 03/20/2003, as part of
PRO-Net 4.3.9.1.

# PRO-Net Firm Profile

[**Privacy
Statement**](http://pro-net.sba.gov/cgi-bin/closemesba.pl?TO=http://www.sba.gov/privacy.html)

## Identification Data

  ---------------------------------------------------- ------------------
  This profile was last updated:                       04/24/2003

  Name of Firm:                                        

  Trade Name:                                          

  Main office or branch office?:                       

  Address, line 1:                                     

  Address, line 2:                                     

  City:                                                

  State:                                               

  Zip:                                                 

  Phone Number:                                        

  Fax Number:                                          

  E-mail Address:                                      

  WWW Page:                                            

  E-Mall (electronic mall\                             
  selling firm\'s products):                           

  Contact Person:                                      

  Contact Title:                                       

  County Code (3 digit):                               

  Congressional District:                              

  Metropolitan Statistical Area:                       

  DUNS Number:                                         

  CAGE Code:                                           

  Year Established:                                    

  Average Number of Employees:                         

  Average Annual Gross Revenue:                        

  Accepts Government Credit Card?:                     

  GSA Advantage Contract:                              
  ---------------------------------------------------- ------------------

## Organizational/Ownership Data

  ---------------------------------------------------------------------------------- -----------------------------
  Legal Structure:                                                                   Corporation

  Minority Code:                                                                     Hispanic American

  Women-Owned?:                                                                      \[  \] Yes \[X\] No

  Veteran?:                                                                          \[X\] Yes \[  \] No

  Service Disabled Veteran?:                                                         \[X\] Yes \[  \] No

  Vietnam Veteran?:                                                                  \[X\] Yes \[  \] No

  Registered in DoD [Central Contractor                                              \[X\] Yes \[  \] No
  Registration](http://pro-net.sba.gov/cgi-bin/closeme.pl?TO=http://www.ccr.gov/)?   

                                                                                      

  **Current Principals:**                                                            (Name, Title)

                                                                                     EDELMIRO MUNIZ, PRESIDENT

                                                                                      

  **Business Development Servicing Office** (for certifications):                    

  HOUSTON (SBA office code 0671)                                                     

                                                                                      

  **8(a) Certification:**                                                             

  SBA 8(a) Case Number:                                                              102384

  SBA 8(a) Entrance Date:                                                            06/27/1995

  SBA 8(a) Exit Date:                                                                06/30/2004

                                                                                      

  **Small Disadvantaged Business Certification:**                                    

  SDB Entrance Date:                                                                 08/24/1998

  SDB Exit Date:                                                                     06/30/2004

                                                                                      

  **HUB Zone Certified?:**                                                           \[  \] Yes \[X\] No

  **HUB Zone Certification Date:**                                                   N/A

  **Non Federal Government Certifications:**                                          
  ---------------------------------------------------------------------------------- -----------------------------

## Products & Services Data

### Capabilities Narrative:

Systems Engineering, Integration, Test & Evaluation; Payload Integration
and Operations; Information Technology; Training and Simulation Systems;
Safety, Product Assurance, and Risk Management; Configuration
Management; Program Planning

### Special Equipment/materials:

### Business Types (Construction, Manufacturing, R&D and/or Service):

  -------------------------------------------------------------------------------------------------------- --------------------------------
  **Business Type Percentages:**                                                                           Research & Development (25.0 %)\
                                                                                                           Service (75.0 %)

                                                                                                            

  Construction Bonding Level (per contract)                                                                00000000

  Construction Bonding Level (aggregate)                                                                   00000000

  Service Bonding Level (per contract)                                                                     00000000

  Service Bonding Level (aggregate)                                                                        00000000

                                                                                                            

  **Firm has had TECH-*Net* award(s), R&D-related:**                                                       

  [Use Of Laptop Computers For Future Spacecraft Crew Work                                                 
  Stations](http://tech-net.sba.gov/sybase-bin/tech-net.cgi?FNC=firmlist_submit__Afirmlist_html___31312)   
  -------------------------------------------------------------------------------------------------------- --------------------------------

### Codes and Keywords:

  -------------- --------------------------------------------------------
  Primary NAICS  541330
  Code:          

  Other NAICS    518210, 541512, 541519, 541710, 561210
  Codes:         

  \"Buy Green\"  
  NAICS Codes:   

  Keywords:      CONFIGURATION MGMNT., ENGINEERING SERVICES, TRAINING,
                 INFORMATION TECH., SAFETY, PRODUCT ASSURANCE

  Quality        ISO-9000 Series
  Assurance      
  Standards:     
  -------------- --------------------------------------------------------

##   {#section-81}

##  {#section-82}

## Miscellaneous Data

  -------------------------------------------------- --------------------
  Electronic Data Interchange capable?:              \[X\] Yes \[  \] No

  Exporter?:                                         No
  -------------------------------------------------- --------------------

##  {#section-83}

## Mentor/Protege Data

Interested in participating in a mentor/protege program?:

\[X\] Yes \[  \] No

This company is interested in participating in a mentor/protege program
in the following areas.

  ----------------------- -----------------------------------------------
  \[  \] Yes \[X\] No     Sales and Marketing

  \[  \] Yes \[X\] No     Production

  \[  \] Yes \[X\] No     Finance

  \[  \] Yes \[X\] No     Research and Development

  \[  \] Yes \[X\] No     Human Resources Development

  \[X\] Yes \[  \] No     General Management

  \[X\] Yes \[  \] No     Strategic Planning

  \[  \] Yes \[X\] No     International

  \[  \] Yes \[X\] No     Other:
  ----------------------- -----------------------------------------------

##  {#section-84}

## Performance/History References

### Federal Agency or Prime Contractor

  ------------------ ----------------------------------------------- -- -- -- --
  Name:                                                                       

  Contract:                                                                   

  Start:                                                                      

  End:                                                                        

  Value:                                                                      

  Contact:                                                                    

  Phone:                                                                      

  Name:                                                                       

  Contract:                                                                   

  Start:                                                                      

  End:               12/31/2003                                               

  Value:             \$15,700,472                                             

  Contact:           Marianne Ruiz                                            

  Phone:             281-483-8528                                             

  Name:              NASA - Johnson Space Center                              

  Contract:          NAS9-99107                                               

  Start:             10/01/1999                                               

  End:               09/30/2003                                               

  Value:             \$16,131,346                                             

  Contact:           Fran Mahan                                               

  Phone:             281-483-2338                                             

  Name:              NASA - Johnson Space Center                              

  Contract:          COMPLETE: NAS9-97125                                     

  Start:             06/05/1997                                               

  End:               06/06/2002                                               

  Value:             \$4,300,000                                              

  Contact:           Keith Hutto                                              

  Phone:             281-483-9953                                             

  Name:              NASA - Johnson Space Center                              

  Contract:          NAS9-99088                                               

  Start:             06/01/1999                                               

  End:               05/31/2004                                               

  Value:             \$2,700,000                                              

  Contact:           Alice Pursell                                            

  Phone:             281-483-9027                                             
  ------------------ ----------------------------------------------- -- -- -- --

### Other Major Customer Name

  -------------------------------------------------- ------- --- --- ----
  Name:                                                              

  Contract:                                                          

  Start:                                                             

  End:                                                               

  Value:                                                             

  Contact:                                                           

  Phone:                                                             

  Name:                                                              

  Contract:                                                          

  Start:                                                             

  End:                                                               

  Value:                                                             

  Contact:                                                           

  Phone:                                                             

  Name:                                                              

  Contract:                                                          

  Start:                                                             

  End:                                                               

  Value:                                                             

  Contact:                                                           

  Phone:                                                             

  Name:                                                              

  Contract:                                                          

  Start:                                                             

  End:                                                               

  Value:                                                             

  Contact:                                                           

  Phone:                                                             
  -------------------------------------------------- ------- --- --- ----

The structure of this page was last updated 03/20/2003, as part of
PRO-Net 4.3.9.1.

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

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

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

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

                                                               

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

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

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

                                                            

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

Change Information Page

  ----------------------- ----------- ------------ ---------- -------------- -------------
  **List of Effective                                                        
  Pages**                                                                    

                                                   **Nature                  
                                                   of                        
                                                   Change**                  

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

  **Document History**                                                       

  **Document Number**     **Version                           **Issue Date** **Effective
                          -- Change**                                        Date**

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

                                                                             

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

Contents

List of Figures

Preface

.

.

######## Abbreviations and Acronyms {#abbreviations-and-acronyms .unnumbered}

+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      | #  {#section-85}                              |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+
|                      |                                               |
+----------------------+-----------------------------------------------+

<table style="width:100%;">
<colgroup>
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 4%" />
<col style="width: 10%" />
<col style="width: 4%" />
<col style="width: 4%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 2%" />
<col style="width: 1%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 5%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 5%" />
<col style="width: 3%" />
<col style="width: 5%" />
<col style="width: 6%" />
<col style="width: 3%" />
<col style="width: 4%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 0%" />
<col style="width: 3%" />
<col style="width: 1%" />
<col style="width: 2%" />
<col style="width: 2%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="22"><strong>THIS DD FORM 254 IS SUBMITTED FOR A SOLE-SOURCE
SOLICITATION" PURPOSES ONLY"</strong></td>
<td colspan="12"><strong>1. CLEARANCE AND SAFEGUARDING</strong></td>
</tr>
<tr class="even">
<td colspan="22"><strong>DEPARTMENT OF DEFENSE</strong></td>
<td colspan="12">a. FACILITY CLEARANCE REQUIRED</td>
</tr>
<tr class="odd">
<td colspan="22"><strong>CONTRACT SECURITY CLASSIFICATION
SPECIFICATION</strong></td>
<td colspan="12">SECRET</td>
</tr>
<tr class="even">
<td colspan="22"><em>(The requirements of the DoD Industrial Security
Manual apply</em></td>
<td colspan="12">b. LEVEL OF SAFEGUARDING REQUIRED</td>
</tr>
<tr class="odd">
<td colspan="22"><em>to all security aspects of this effort.)</em></td>
<td colspan="12">SECRET</td>
</tr>
<tr class="even">
<td colspan="16"><strong>2. THIS SPECIFICATION IS FOR:</strong> <em>(X
and complete as applicable)</em></td>
<td colspan="18"><strong>3. THIS SPECIFICATION IS:</strong> <em>(X and
complete as applicable)</em></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="14">a. PRIME CONTRACT NUMBER</td>
<td colspan="2"></td>
<td colspan="10"></td>
<td colspan="6">Date <em>(YYMMDD)</em></td>
</tr>
<tr class="even">
<td colspan="2">X</td>
<td colspan="14">NAS 9-03056</td>
<td colspan="2">X</td>
<td colspan="10">a. <strong>ORIGINAL</strong> <em>(Complete date in all
cases)</em></td>
<td colspan="6">04/02/06</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="14">b. SUBCONTRACT NUMBER</td>
<td colspan="2"></td>
<td colspan="6">b. <strong>REVISED</strong> <em>(Supersedes</em></td>
<td colspan="4">Revision No.</td>
<td colspan="6">Date <em>(YYMMDD)</em></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="14"></td>
<td colspan="2">X</td>
<td colspan="6"><em>all previous specs)</em></td>
<td colspan="4">1</td>
<td colspan="6">04/08/19</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td colspan="8">c. SOLICITATION OR OTHER NUMBER</td>
<td colspan="6">Due Date <em>(YYMMDD)</em></td>
<td colspan="2"></td>
<td colspan="10"></td>
<td colspan="6">Date <em>(YYMMDD)</em></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td colspan="8"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="10">c. <strong>FINAL</strong> <em>(Complete Item 5 in all
cases)</em></td>
<td colspan="6"></td>
</tr>
<tr class="odd">
<td colspan="8"><strong>4. IS THIS A FOLLOW-ON CONTRACT?</strong></td>
<td colspan="3">X</td>
<td colspan="4">YES</td>
<td></td>
<td colspan="18">NO. If Yes, complete the following:</td>
</tr>
<tr class="even">
<td colspan="7">Classified material received/generated under</td>
<td colspan="14">NAS9-98100 as MSOC related data</td>
<td colspan="13"><em>(Preceding Contract Number)</em> are transferred to
this follow-on contract.</td>
</tr>
<tr class="odd">
<td colspan="8"></td>
<td colspan="3"></td>
<td colspan="23"></td>
</tr>
<tr class="even">
<td colspan="8"><strong>5. IS THIS A FINAL DD FORM 254?</strong></td>
<td colspan="3"></td>
<td colspan="4">YES</td>
<td>X</td>
<td colspan="18">NO. If Yes, complete the following:</td>
</tr>
<tr class="odd">
<td colspan="6">In response to contractor's request dated</td>
<td colspan="7">N/A</td>
<td colspan="12">, retention of the classified material is authorized
for the period</td>
<td colspan="8">N/A</td>
<td></td>
</tr>
<tr class="even">
<td colspan="8"></td>
<td colspan="3"></td>
<td colspan="23"></td>
</tr>
<tr class="odd">
<td colspan="34"><strong>6. CONTRACTOR</strong> <em>(Include Commercial
and Government Entity (CAGE) Code)</em></td>
</tr>
<tr class="even">
<td colspan="14">a. NAME, ADDRESS, AND ZIP CODE</td>
<td colspan="5">b. CAGE CODE</td>
<td colspan="15">c. COGNIZANT SECURITY OFFICE <em>(Name, Address, and
Zip Code)</em></td>
</tr>
<tr class="odd">
<td colspan="14"><p>Lockheed Martin Space Operations</p>
<p>Attn: Security Officer</p>
<p>595 Gemini Avenue</p>
<p>Houston, TX 77058</p></td>
<td colspan="5">IEOF9</td>
<td colspan="15"><p>DIS-Defense Investigative Service</p>
<p>Southwestern Region</p>
<p>106 Decker Court, Suite 200</p>
<p>Irving, TX 75062-2795</p></td>
</tr>
<tr class="even">
<td colspan="34"><strong>7. SUBCONTRACTOR</strong></td>
</tr>
<tr class="odd">
<td colspan="14">a. NAME, ADDRESS, AND ZIP CODE</td>
<td colspan="5">b. CAGE CODE</td>
<td colspan="15">c. COGNIZANT SECURITY OFFICE <em>(Name, Address, and
Zip Code)</em></td>
</tr>
<tr class="even">
<td colspan="14">N/A</td>
<td colspan="5">N/A</td>
<td colspan="15">N/A</td>
</tr>
<tr class="odd">
<td colspan="34"><strong>8. ACTUAL PERFORMANCE</strong></td>
</tr>
<tr class="even">
<td colspan="14">a. LOCATION</td>
<td colspan="5">b. CAGE CODE</td>
<td colspan="15">c. COGNIZANT SECURITY OFFICE <em>(Name, Address, and
Zip Code)</em></td>
</tr>
<tr class="odd">
<td colspan="14">NASA/Johnson Space Center</td>
<td colspan="5">N/A</td>
<td colspan="15">N/A</td>
</tr>
<tr class="even">
<td colspan="34"><strong>9. GENERAL IDENTIFICATION OF THIS
PROCUREMENT</strong></td>
</tr>
<tr class="odd">
<td colspan="34">Mission Support Operations Contract (MSOC)</td>
</tr>
<tr class="even">
<td colspan="10"><strong>10.CONTRACTOR WILL REQUIRE ACCESS
TO:</strong></td>
<td colspan="2">YES</td>
<td colspan="2">NO</td>
<td colspan="16"><strong>11. IN PERFORMING THIS CONTRACT, THE CONTRACTOR
WILL:</strong></td>
<td colspan="2">YES</td>
<td colspan="2">NO</td>
</tr>
<tr class="odd">
<td colspan="10">a. COMMUNICATIONS SECURITY (COMSEC) INFORMATION</td>
<td colspan="2">X</td>
<td colspan="2"></td>
<td colspan="16">a. HAVE ACCESS TO CLASSIFIED INFORMATION ONLY AT
ANOTHER CONTRACTOR'S FACILITY OR A GOVERNMENT ACTIVITY</td>
<td colspan="2"></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td colspan="10">b. RESTRICTED DATA</td>
<td colspan="2"></td>
<td colspan="2">X</td>
<td colspan="16">b. RECEIVE CLASSIFIED DOCUMENTS ONLY</td>
<td colspan="2"></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td colspan="10">c. CRITICAL NUCLEAR WEAPON DESIGN INFORMATION</td>
<td colspan="2"></td>
<td colspan="2">X</td>
<td colspan="16">c. RECEIVE AND GENERATE CLASSIFIED MATERIAL</td>
<td colspan="2">X</td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td colspan="10">d. FORMERLY RESTRICTED DATA</td>
<td colspan="2"></td>
<td colspan="2">X</td>
<td colspan="16">d. FABRICATE, MODIFY, OR STORE CLASSIFIED HARDWARE</td>
<td colspan="2">X</td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="10">e. INTELLIGENCE INFORMATION</td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="16">e. PERFORM SERVICES ONLY</td>
<td colspan="2"></td>
<td colspan="2">X</td>
</tr>
<tr class="even">
<td colspan="10">(1) Sensitive Compartmented Information (SCI)</td>
<td colspan="2"></td>
<td colspan="2">X</td>
<td colspan="16">f. HAVE ACCESS TO U.S. CLASSIFIED INFORMATION OUTSIDE
THE U.S., PUERTO RICO, U.S. POSSESSIONS AND TRUST TERRITORIES</td>
<td colspan="2"></td>
<td colspan="2">X</td>
</tr>
<tr class="odd">
<td colspan="10">(2) Non-SCI</td>
<td colspan="2">X</td>
<td colspan="2"></td>
<td colspan="16">g. BE AUTHORIZED TO USE THE SERVICES OF DEFENSE
TECHNICAL INFORMATION CENTER (DTIC) OR OTHER SECONDARY DISTRIBUTION
CENTER</td>
<td colspan="2">X</td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td colspan="10">f. SPECIAL ACCESS INFORMATION</td>
<td colspan="2"></td>
<td colspan="2">X</td>
<td colspan="16">h. REQUIRE A COMSEC ACCOUNT</td>
<td colspan="2">X</td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="10">g. NATO INFORMATION</td>
<td colspan="2"></td>
<td colspan="2">X</td>
<td colspan="16">i. HAVE TEMPEST REQUIREMENTS</td>
<td colspan="2">X</td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td colspan="10">h. FOREIGN GOVERNMENT INFORMATION</td>
<td colspan="2"></td>
<td colspan="2">X</td>
<td colspan="16">j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS</td>
<td colspan="2">X</td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="10">i. LIMITED DISSEMINATION INFORMATION</td>
<td colspan="2"></td>
<td colspan="2">X</td>
<td colspan="16">k. BE AUTHORIZED TO USE THE DEFENSE COURIER
SERVICE</td>
<td colspan="2">X</td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td colspan="10">j. FOR OFFICIAL USE ONLY INFORMATION</td>
<td colspan="2">X</td>
<td colspan="2"></td>
<td colspan="16">l. OTHER <em>(Specify)</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
</tr>
<tr class="odd">
<td colspan="10">k. OTHER <em>(Specify)</em></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="16">(See item #13)</td>
<td colspan="2"></td>
<td colspan="2"></td>
</tr>
<tr class="even">
<td colspan="34"><strong>12. PUBLIC RELEASE</strong> Any information
<em>(classified or unclassified)</em> pertaining to this contract shall
not be released for public dissemination except as provided by the
Industrial Security Manual unless it has been approved for public
release by appropriate U.S. Government authority. Proposed public
releases shall be submitted for approval prior to release</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="2">X</td>
<td>Direct</td>
<td></td>
<td colspan="29">Through <em>(Specify)</em></td>
</tr>
<tr class="even">
<td colspan="34">NASA/JOHNSON SPACE CENTER AP/PUBLIC AFFAIRS OFFICE
HOUSTON, TX 77058</td>
</tr>
<tr class="odd">
<td colspan="34">CC To the Public Affairs Division, NASA Headquarters,
Washington, D.C. 20546 for review.</td>
</tr>
<tr class="even">
<td colspan="34"><strong>13. SECURITY GUIDANCE.</strong> The security
classifiection guidance needed for this classified effort is identified
below. If any difficulty is encountered in applying this guidance or if
any other contributing factor indicates a need for changes in this
guidance, the contractor is authorized and encouraged to provide
recommended changes; to challenge the guidance or the classification
assigned to any information or material furnished or generated under
this contract; and to submit any questions for interpretation of this
guidance to the official identified below. Pending final decision, the
information involved shall be handled and protected at the highest level
of classification assigned or recommended. <em>(Fill in as appropriate
for the classified effort. Attach, or forward under separate
correspondence, any documents/guides/extracts referenced herein. Add
additional pages as needed to provide complete guidance.)</em></td>
</tr>
<tr class="odd">
<td colspan="34"><p>The following documents shall be applicable and
binding in the performance of this contract:</p>
<p>a. DOD Secure Shuttle Operations Security Classification Guide (DSSO
SCG), Headquarters Space Systems Division (AFSC)/USAF, Los Angeles, CA
dated February 22, 1991.</p>
<p>b. The STS Operations and Engineering Handbook is the official
document within NASA and NASA contractors for interpreting the STS
Security Classification Guide dated June 16, 1989. This document is to
be used by contractor personnel to assist them in determining what
information is to be classified.</p>
<p>c. Space Network Security Classification Guide dated March 2, 1992,
and document Change Notice #1 dated March 9, 1995.</p>
<p>d. Chapter 4 of the NASA Security Procedures &amp; Guidelines (NPG
1620.1A) applies to "CNSI" and "ACI" (formerly FOUO) information.</p>
<p>e. National Industrial Security Program Operating Manual (NISPOM),
DOD 5220.22-M, dated January 1995.</p>
<p>f. COMSEC Supplement to former Industrial Security Manual, DOD
5220.22-S, current edition.</p>
<p>g. NASA Communications Security Classification Guide dated January 8,
1987.</p>
<p>h. Security Handbooks, Manuals, Regulations, Instructions, and
Directives (current editions) for JSC, as well as other applicable
policies and procedures as identified by NASA.</p>
<p>Additional security, technical, and/or classification guidance will
be provided by NASA officials. Requests concerning clarification or
interpretation regarding security requirements under this contract will
be directed to the NASA/JSC Industrial Security Specialist. The place of
performance will be at the contractor cleared facilities, JSC, and other
locations where the requirement is covered by the obligations specified
in Section C of the basic contract document. The basic period of
performance is January 1, 2004 through September 30, 2004, with a
3-month transition period starting on October 1, 2003. There are two
option scenarios that are mutually exclusive. . The second scenario is a
single 2-year option with performance through September 30,
2006.</p></td>
</tr>
<tr class="even">
<td colspan="26"><strong>14. ADDITIONAL SECURITY REQUIREMENTS.</strong>
Requirements, in addition to ISM requirements, are established for
this</td>
<td>X</td>
<td colspan="2">Yes</td>
<td colspan="2"></td>
<td colspan="3">No</td>
</tr>
<tr class="odd">
<td colspan="26">contract. <em>(If Yes, identify the pertinent
contractual clauses in the contract document itself, or provide an
appropriate statement whch identifies the additional requirements.
Provide a copy of the requirements to the cognizant security office. Use
Item 13 if additional space is needed.)</em></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="3"></td>
</tr>
<tr class="even">
<td colspan="34">See attached page.</td>
</tr>
<tr class="odd">
<td colspan="26"><strong>15. INSPECTIONS.</strong> Elements of this
contract are outside the inspection responsibility of the cognizant
security office. <em>(If Yes, explain</em></td>
<td>X</td>
<td colspan="2">Yes</td>
<td colspan="2"></td>
<td colspan="3">No</td>
</tr>
<tr class="even">
<td colspan="26"><em>and identify specific areas or elements carved out
and the activity responsible for inspections. Use Item 13 if additional
space is needed.)</em></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="3"></td>
</tr>
<tr class="odd">
<td colspan="34">As a long-term visitor to NASA/JSC, the contractor will
comply with all applicable NASA/JSC security issuances, memorandums,
policies/procedures, and regulations as directed. Inspection authority
of contractor activities on NASA installations is the responsibility of
NASA security officials and will be coordinated by the JSC Industrial
Security Specialist.</td>
</tr>
<tr class="even">
<td colspan="34"><strong>16. CERTIFICATION AND SIGNATURE</strong>.
Security requirements stated herein are complete and adequate for
safeguarding the classified information to be released or generated
under this classified effort. All questions shall be referred to the
official named below.</td>
</tr>
<tr class="odd">
<td colspan="9">a. TYPED NAME OF CERTIFYING OFFICIAL</td>
<td colspan="14">b. TITLE</td>
<td colspan="11">c. TELEPHONE <em>(Include Area Code)</em></td>
</tr>
<tr class="even">
<td colspan="9">Judith Ann Elam</td>
<td colspan="14">Industrial Security Specialist</td>
<td colspan="11">(281) 483-4028</td>
</tr>
<tr class="odd">
<td colspan="17">d. ADDRESS <em>(Include Zip Code)</em></td>
<td colspan="17"><strong>17. REQUIRED DISTRIBUTION</strong></td>
</tr>
<tr class="even">
<td colspan="17">NASA/Johnson Space Center</td>
<td colspan="3">X</td>
<td colspan="14">a. CONTRACTOR</td>
</tr>
<tr class="odd">
<td colspan="17">JA14/Security Office</td>
<td colspan="3"></td>
<td colspan="14">b. SUBCONTRACTOR</td>
</tr>
<tr class="even">
<td colspan="17">Houston, TX 77058</td>
<td colspan="3">X</td>
<td colspan="14">c. COGNIZANT SECURITY OFFICE FOR PRIME AND
SUBCONTRACTOR</td>
</tr>
<tr class="odd">
<td colspan="17">e. SIGNATURE</td>
<td colspan="3"></td>
<td colspan="14">d. U.S. ACTIVITY RESPONSIBLE FOR OVERSEAS SECURITY
ADMINISTRATION</td>
</tr>
<tr class="even">
<td colspan="17">Original signed by Judith Ann Elam</td>
<td colspan="3">X</td>
<td colspan="14"><blockquote>
<p>e. ADMINISTRATIVE CONTRACTING OFFICER</p>
</blockquote></td>
</tr>
<tr class="odd">
<td colspan="17"></td>
<td colspan="3">X</td>
<td colspan="14">f. OTHERS AS NECESSARY: BH/Caroline Root DA/James
Lowery JLS/J.Hagan</td>
</tr>
</tbody>
</table>

DD Form 254 Page Two, Dec 90 (EG) (MS Word 4/96

Item #14. Additional Security Requirements and/or Guidance for MSOC

Performance of this contract will involve the receipt, generation, and
storage of classified material/information. Reports containing
classified extracts from other classified sources will contain security
markings, which correspond to those of the source documents. Those
employees requiring access to classified information must have
appropriate personnel security clearances. The contractor is authorized
to receive/generate classified material only at approved locations.
Classified Information Technology (IT) processing will be involved;
however, classified information will not be entered into any IT system
until the system has been accredited by the appropriate Designated
Approving Authority as meeting the required national standards and/or
guidelines. The contractor will be required to operate a COMSEC account
issued by the National Security Agency (NSA) for NASA. COMSEC
inspections and/or audits will be conducted as required by the NASA
Central Office of Records. The NSA, at their discretion, may also
conduct inspections for compliance with COMSEC standards and/or
guidelines. Only U.S. citizens granted a final personnel security
clearance (as appropriate) and who have been COMSEC-briefed and have
signed a Cryptographic Access Certification are eligible for access to
classified COMSEC information released or generated under this contract,
any other employees must have prior written approval from the
appropriate NASA official(s).

Security-related activities checked in item #11 also apply to personnel
requiring access to security-controlled and/or crypto areas, involved in
the generation and receipt of classified information. Due to the need to
operate cryptographic equipment and/or devices at the Center, it will
require the use of classified as well as unclassified but sensitive
cryptographic keying material. The need is thereby established for
access to documents such as NACSIs, NACSIMs, NTISSIs, and/or other
related national doctrine and/or guidelines.

A Defense Courier Service account is requested; designated contractor
employees are authorized to courier classified material up to and
including COMSEC/CRYPTO in accordance with the NISPOM.

TEMPEST requirements are to be met in accordance with NTISSI 7000 and/or
other related national doctrine and any cost pertaining to this
requirement must be approved though the appropriate NASA security
official(s). Additionally, the following regulations or directives
apply: (1) CSCM-1; (2) NACSI 4005; (3) NACSI 4008; (4) NACSI 4010

This information is included in the Space Program Integrated Contract
Environment (SPICE) system. The Contractor will submit a new listing to
the Contracting Officer within 30 days at the end of each Government
fiscal year, for annual updates into SPICE.

A. Johnson Space Center On-site Office Space -- 6,609.6 square feet

B. Publications and blank forms stocked by the installation (on-site and
off-site)

C. Copiers, fax machines (on-site only)

D. Additional plant equipment, which does not meet the criteria for
accountability under the NEMS system (under \$5,000; not on sensitive
list) will also be provided at contract award. The contractor shall
replace this plant equipment as necessary for use in the performance of
this contract.

E. ODIN Seats -- Quantity 50

<table>
<colgroup>
<col style="width: 11%" />
<col style="width: 7%" />
<col style="width: 1%" />
<col style="width: 21%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 9%" />
<col style="width: 9%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 0%" />
<col style="width: 6%" />
<col style="width: 9%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="11">a. Title of Contract, Project, SOW, etc.</th>
<th colspan="6">b. Contract/RFP No.</th>
<th colspan="3">c. DRL Date/Mod Date</th>
</tr>
<tr class="odd">
<th colspan="11">Mission Support Operations Contract</th>
<th colspan="6">NAS 9-03056</th>
<th colspan="3"></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0001</td>
<td colspan="7">Contract Work Breakdown Structure and Dictionary</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0002</td>
<td colspan="7">Management Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10">.</td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="8">2. DRD Title</td>
<td>3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0003</td>
<td colspan="8">Risk Management Plan</td>
<td>See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0004</td>
<td colspan="7">Contract Configuration Management Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0005</td>
<td colspan="7">Phase-In Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval (Plan)</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal (Reports)</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0006</td>
<td colspan="7">Performance Measurement Plan and Reports</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter.</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0007</td>
<td colspan="7">Metric and Status Reports</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter.</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0008</td>
<td colspan="7">Government Property Management Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>xX</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter.</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0009</td>
<td colspan="7">Small Business Subcontracting Plan and Reports</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0010</td>
<td colspan="7">Information Technology (IT) Plan and Reports</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0011</td>
<td colspan="7">Emergency Preparedness and Disaster Recovery Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0012</td>
<td colspan="7">Reports/Reviews</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0013</td>
<td colspan="7">Reprocurement Data Package</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0014</td>
<td colspan="7">Property Financial Reporting</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval (Plan)</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal (Reports)</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0015</td>
<td colspan="7">Customer Reporting</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0016</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0017</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0018</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td><ol type="1">
<li><p>Line item no.</p></li>
</ol></td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. Date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0019</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0020</td>
<td colspan="7">NF 533 M/Q Cost Reporting</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>X</td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0021</td>
<td colspan="7">Wage/Salary and Fringe Benefit Data</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0022</td>
<td colspan="7">FY Operating Plan (FY OP Plan) and Program Operating
Plan (POP)</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval (Tech Op Plan)</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal (POP)</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0023</td>
<td colspan="7">Travel Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0024</td>
<td colspan="7">Workforce Reports</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0025</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0026</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval (Plan)</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request (Report)</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0027</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0028</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0029</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval (Plan)</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal (Products)</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0030</td>
<td colspan="7">Safety and Health Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0031</td>
<td colspan="7">Safety and Health Program, Self Evaluation</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0032</td>
<td colspan="7">Monthly Safety and Health Metrics</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0033</td>
<td colspan="7">System Safety Program Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>XX</td>
<td>(1) Written approval.</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0034</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0035</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval (Plan)</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal (Metrics)</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0036</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0037</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0038</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0039</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0040</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0041</td>
<td colspan="7">Quality Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>X</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2">x</td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0042</td>
<td colspan="7">Software Quality Assurance Plan &amp; Reports</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>X</td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0043</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0044</td>
<td colspan="7">GIDEP and NASA Advisory Problem Data Sharing and
Utilization Program Documentation and Reporting</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
</tbody>
</table>

<table>
<colgroup>
<col style="width: 11%" />
<col style="width: 7%" />
<col style="width: 1%" />
<col style="width: 21%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 9%" />
<col style="width: 9%" />
<col style="width: 1%" />
<col style="width: 0%" />
<col style="width: 1%" />
<col style="width: 1%" />
<col style="width: 6%" />
<col style="width: 6%" />
<col style="width: 0%" />
<col style="width: 6%" />
<col style="width: 9%" />
</colgroup>
<thead>
<tr class="header">
<th colspan="11">a. Title of Contract, Project, SOW, etc.</th>
<th colspan="6">b. Contract/RFP No.</th>
<th colspan="3">c. DRL Date/Mod Date</th>
</tr>
<tr class="odd">
<th colspan="11">Mission Support Operations Contract</th>
<th colspan="6">NAS 9-03056</th>
<th colspan="3"></th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0045</td>
<td colspan="7">Non-conformance Record</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0046</td>
<td colspan="7">Safety Lessons Learned</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">xX</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10">.</td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="8">2. DRD Title</td>
<td>3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0047</td>
<td colspan="8">Reserved</td>
<td></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0048</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0049</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval (Plan)</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal (Reports)</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0050</td>
<td colspan="7">Certificate of Flight Readiness Endorsement</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter.</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0051</td>
<td colspan="7">Integrated Planning System (IPS) Facility Operations
Procedures</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter.</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0052</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As of Date</td>
<td colspan="5">5. 1<sup>st</sup> subm. Date</td>
<td colspan="2">6. Copies</td>
<td>a. Type</td>
<td>b. Number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0053</td>
<td colspan="7">Training and Certification Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"><em>8. Distribution (Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0054</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0055</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0056</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0057</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0058</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval (Plan)</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal (Reports)</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0059</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0060</td>
<td colspan="7">Change Control Process Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0061</td>
<td colspan="7">Configuration Management Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>X</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0062</td>
<td colspan="7">Level A and B Requirements</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td><ol start="2" type="1">
<li><p>Line item no.</p></li>
</ol></td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. Date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0063</td>
<td colspan="7">Interface Control Document</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0064</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0065</td>
<td colspan="7">Systems Lifecycle Process</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0066</td>
<td colspan="7">Equipment Replacement Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval (Plan &amp; SLAs)</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s Letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0067</td>
<td colspan="7">Integrated Planning System (IPS) Future Facility Change
Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0068</td>
<td colspan="7">Test and Verification Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>X</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0069</td>
<td colspan="7">Test and Verification Procedures</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2">X</td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0070</td>
<td colspan="7">Test and Verification Report</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval (Plan)</td>
<td colspan="2">x</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2">X</td>
<td colspan="6">(3) Submitted upon request (Report)</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0071</td>
<td colspan="7">Acceptance Review Package</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0072</td>
<td colspan="7">Design Review</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>X</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0073</td>
<td colspan="7">Design Specifications</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval (Plan)</td>
<td colspan="2">X</td>
<td colspan="6">(2) Mandatory Submittal (Products)</td>
<td colspan="2">X</td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0074</td>
<td colspan="7">Integrated Planning System Operations Concept</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2">X</td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0075</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0076</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0077</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval.</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0078</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0079</td>
<td colspan="7">Reserved</td>
<td colspan="2"></td>
<td></td>
<td colspan="5"></td>
<td colspan="3"></td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td></td>
<td>(1) Written approval (Plan)</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal (Metrics)</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9"></td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="odd">
<td>MSOC-JSC-0080</td>
<td colspan="7">Contractor Security Management Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="odd">
<td>1. Line item no.</td>
<td colspan="7">2. DRD Title</td>
<td colspan="2">3. Frequency</td>
<td>4. As-of-Date</td>
<td colspan="5">5. 1st subm. date</td>
<td colspan="2">6. Copies</td>
<td>a. type</td>
<td>b. number</td>
</tr>
<tr class="even">
<td>MSOC-JSC-0081</td>
<td colspan="7">Facility Security Plan</td>
<td colspan="2">See DRD</td>
<td></td>
<td colspan="5">See DRD</td>
<td colspan="3">Per Contracting Officer’s letter</td>
<td></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td colspan="2">7. Data type:</td>
<td>x</td>
<td>(1) Written approval</td>
<td colspan="2"></td>
<td colspan="6">(2) Mandatory Submittal</td>
<td colspan="2"></td>
<td colspan="6">(3) Submitted upon request</td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="even">
<td></td>
<td colspan="9">8. Distribution <em>(Continue on a blank sheet if
needed)</em></td>
<td colspan="10">9. Remarks</td>
</tr>
<tr class="odd">
<td></td>
<td colspan="9">Per Contracting Officer’s letter</td>
<td colspan="10"></td>
</tr>
<tr class="even">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
<tr class="odd">
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td colspan="2"></td>
<td colspan="6"></td>
<td colspan="2"></td>
<td colspan="5"></td>
</tr>
</tbody>
</table>

NASA Johnson Space Center

Mission Support Operations Contract (MSOC)

Data Requirements Description (DRD) Sheets

> DATA REQUIREMENTS DESCRIPTION (DRD)
>
> DRD No.: MSOC-JSC-0001
>
> DRD Title: Contract Work Breakdown Structure and Dictionary
>
> Data Type: 1
>
> Page: 1 / 1
>
> Description/Use - To organize the tasks to be accomplished in this
> contract in a service oriented structure. The CWBS and dictionary
> shall provide the framework for structuring the program implementation
> plans, establishing and tracking budgets, preparing schedules,
> developing work force and material estimates, preparing work
> authorization documents, and reporting contract performance.
>
> SOW Ref.: 1.1
>
> Submission:

Initial -- Due with proposal

Final -- Due contract start

Approval -- Due 90 days from contract start

Submission Frequency - Each CWBS update

> Applicable Documents: None
>
> Data Preparation Information:

Scope -- The CWBS shall encompass all the services required to achieve
all the requirements of this contract. The CWBS shall subdivide the work
to be accomplished into elements that serve as the basis for detailed
planning and control, and in addition, permit collection of cost and
schedule data for each element.

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

Format: The CWBS tree is to be in organization chart format and the
associated CWBS narrative (CWBS Dictionary) in text form and arranged as
depicted by the CWBS tree. The CWBS tree and dictionary shall be
provided in both electronic and hard copy form.

Distribution: distribution specified below plus additional distribution
per Contracting Officer's letter

Initial -- as specified in the Proposal instructions

Final -- Contracting Officer, COTR, Task Manager, each Facility Project
Manager

Update -- Contracting Officer, COTR, Task Manager, each Facility Project
Manager

> Maintenance - Revisions shall be incorporated by change page or
> complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0002
>
> DRD Title: Management Plan
>
> Data Type: 1
>
> Page: 1 / 1
>
> Description/Use - To describe the contractor\'s integrated management
> approach, organization, and systems.

SOW Ref: 1.1, 1.3.1.3

> Submission:

Initial -- Due with proposal

Final -- Due 90 days after contract award

Approval -- From start of contract + 180 days

Submission Frequency -- as required

> Applicable Documents: none
>
> Data Preparation Information:

Scope --The Integrated Management Plan shall describe the basis for the
contractor management approach, organization, and systems for
accomplishing and managing all services and functions described in the
SOW. It shall provide a comprehensive integration of all management
systems of the prime, subcontractors, and major vendors, including Small
and Small Disadvantaged business goals. The systems shall 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.

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

Format: Contractor's electronic format is acceptable

Distribution: distribution specified below plus additional distribution
per Contracting Officer's letter

Initial -- as specified in the Proposal instructions

Final -- Contracting Officer, COTR, Task Manager

Update -- Contracting Officer, COTR, Task Manager

> Maintenance - Revisions shall be incorporated by change page or
> complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0003
>
> DRD Title: Risk Management Plan
>
> Data Type: 1
>
> Page: 1 / 1
>
> Description/Use - To describe the contractor's implementation approach
> for performing and reporting risk management, in conformance with the
> processes that are defined by the Government provided guidelines NPG
> 7120.5.

SOW Ref: 1.1

> Submission:

Initial -- Start of contract + 15 days

Final -- Start of contract + 45 days

Approval -- From start of contract + 60 days

Submission Frequency -- as required

> Applicable Documents: none
>
> Data Preparation Information:

Scope -- The risk management plan defines the contractor's method to
accomplish proactive end-to-end risk analysis management and abatement,
throughout the contract duration. Risk management includes risk:
identification, analysis, handling, mitigation, tracking, controlling
and risk communication.

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

Format: Contractor's electronic format is acceptable.

Distribution: distribution specified below plus additional distribution
per Contracting Officer's letter

Initial -- as specified in the Proposal instructions

Final -- Contracting Officer, COTR, Task Manager

Update -- Contracting Officer, COTR, Task Manager

> Maintenance - Revisions shall be incorporated by change page or
> complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0004
>
> DRD Title: Contract Configuration Management Plan
>
> Data Type: 1
>
> Page: 1 / 1
>
> Description/Use - To describe the contractor\'s method for
> accomplishing the configuration management of the contract.

SOW Ref: 1.1

> Submission:

Initial -- Due with proposal

Final -- Due 90 days after contract award

Approval -- From contract award + 120 days

Submission Frequency -- as required

> Applicable Documents: none
>
> Data Preparation Information:

Scope -- The plan shall describe the contractor's management approach
and planned implementation methods for accomplishing the configuration
management of the contract.

Content -- The plan shall describe the contractor's CM organization,
policies, procedures, implementation approach, and control systems that
are to be used to ensure proper contract CM activities.

Format: Contractor's electronic format is acceptable.

Distribution: distribution specified below plus additional distribution
per Contracting Officer's letter

Initial -- as specified in the Proposal instructions

Final -- Contracting Officer, COTR

Update -- Contracting Officer, COTR, Task Manager

> Maintenance - Revisions shall be incorporated by change page or
> complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0005
>
> DRD Title: Phase-in Plan
>
> Data Type: 1
>
> Page: 1 / 1
>
> Description/Use - To provide an approach and rationale for transition
> of HSF Space Operations activities to the MSOC.
>
> SOW Ref: 1.1, and 1.5
>
> Submission:

Initial -- Due with proposal

Final -- Contract Award + 5 days

Approval -- Contract Award + 10 days

> Applicable Documents: none
>
> Data Preparation Information:

Scope -- The MSOC Transition Plan provides plans for the transfer of all
anticipated operations activities along with supporting logic and
rationale.

Content -- The Transition plan shall describe the overall plan for
transition. As a minimum, it shall address:

Schedule with key milestones

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

Metrics used to determine progress for contract transition

Property control transfer

Facilities responsibility transfer

Mission assurance considerations

Security considerations

Classified document control transfer

Risk mitigation strategy

Configuration management considerations.

Format: Contractor format is acceptable.

Distribution: distribution specified below plus additional distribution
per Contracting Officer's letter

Initial -- as specified in the Proposal instructions

Final -- Contracting Officer, COTR, Task Manager, each Facility Project
Manager

> Maintenance - change pages or complete reissue shall incorporate
> Changes.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0006
>
> DRD Title: Performance Measurement Plan and Reports
>
> Data Type: Plan: 1 Reports: 2
>
> Page: 1 / 2
>
> Description/Use - The Performance Measurement Plan shall measure and
> assess the contractor's effective management of all contract
> requirements and SOW elements in an integrated and time-correlated
> cost, schedule, content, and quality (technical metrics) system. This
> plan shall include a surveillance plan that defines technical metrics
> reporting for SOW Expectations and Standards for Excellence. This plan
> shall describe both the technical metrics (technical metrics reports)
> and the cost/schedule/content metrics (cost performance reports) and
> how these reports are integrated into a comprehensive management
> performance assessment process. This plan shall describe how the
> contractor uses these reports and the underlying data to effectively
> manage the work. These reports shall be used by the Government to
> assess the contractor's performance.
>
> SOW Ref: 1.2.2.1
>
> Submission:

Initial -- Due with proposal

Final -- 1/19/2004

Approval -- 1/26/2004

Submission Frequency -- Plan shall be updated as required. Reports shall
be due 10 days after period close and reflect the content of the period
closed.

> Applicable Documents: For the technical metrics use as a reference
> guides the following JSC documents:

JSC-26010 DA3 Software Sustaining Engineering Metrics

JSC-25519 DA3 Software Development Metrics

JSC-36112 DA3 Development Project Metrics

JSC-26458 DA3/SSO Sustaining and Operations Performance Management
Metrics

JSC-27450 Performance Measurement System Handbook

NASA Policy Document (NPD) 9501.3 and 9501

> Data Preparation Information:

Scope -- The Performance Measurement Plan shall describe the system,
processes, and reports that the contractor shall utilize to measure an
integrated and time-correlated cost, schedule, content, and quality
performance and shall utilize for accomplishing and managing all
services and functions described in the statement of work. This plan
shall provide a comprehensive integration of all metrics/measurement and
management systems of the prime, subcontractors, team arrangements, and
major vendors. The Performance Measurement Reports shall provide the
quality metrics, cost, and schedule information in accordance with the
Performance Measurement Plan. These reports shall be the same metrics
and cost/schedule information used by the contractor to effectively
measure performance and to manage the work of all services and elements
of the SOW. The level of detail in these reports to the government shall
normally be limited to the SOW WBS reporting level, as negotiated and
finalized in the plan, except for level of detail required to explain
variances exceeding reporting thresholds.

Content -- In accordance with JSC 27450, Performance Measurement System
Handbook Performance Measurement System Plan/System Description
Document - NPD 9501.3 and 9501.4, Earned Value Performance Management.

Performance Measurement System Plan/Performance Metrics and Surveillance
Reports shall use as a guide the metrics handbooks listed under the
"Remarks" section of this DRD. These documents shall include definition
of metrics and thresholds for variance analysis to identify cause,
impact, and corrective action for any out of limit conditions.

Format: In accordance with JSC 27450 Performance Measurement System
Handbook

> Cost Performance report - Reference DI-MGMT-81466 and ANSI ASC X.12
> Electronic Format
>
> Technical Performance Metrics and Surveillance Reports - Reference
> metrics handbooks listed under applicable documents as a guide.
>
> Information will be provided at the "Adjusted Total: Cost Plus Fee"
> level per report.

Distribution: distribution specified below plus additional distribution
per Contracting Officer's letter

Initial -- as specified in the Proposal instructions

Final -- Contracting Officer, COTR, Task Manager, each Facility Project
Manager, DCMA

Update -- Contracting Officer, COTR, Task Manager, each Facility Project
Manager, DCMA

> Maintenance - change pages or complete reissue shall incorporate
> Changes.

# **DATA REQUIREMENTS DESCRIPTION (DRD)**

DRD No.: MSOC-JSC-0007

DRD Title: Metric and Status Reports

Data Type: 2

Page: 1 / 1

Description/Use -- Metric and status Reports shall be provided to the
NASA Project Integration and Status meetings and as requested by NASA.
The reports are for the MCC, HSR/BCC, IPS, GSDE, and CDE systems.

SOW Ref.: 1.5.1.1.10, 1.5.1.2.10, 1.5.2.2.10, and 1.5.2.3.10

Submission:

Initial -- Due monthly after contract start

Final -- Due at contract completion

Approval -- N/A

Submission Frequency -- Metric reports - monthly, Status reports as
required

Applicable Documents: JSC-26010 DA Software Sustaining Engineering
Metrics, JSC-25510 DA3 Software Development Metrics, JSC-36112 DA3
Development Project Metrics, JSC-26458 DA3/SSO Sustaining and Operations
Performance Management Metrics.

Data Preparation Information:

Scope -- The report shall contain current and trend data on facility
system/subsystem availability, utilization and performance.

Content -- Metric and status reports shall be provided. Metric reports
shall include, but not be limited to the following: (1) change request
status (2) system/subsystem availability (3) system/subsystem
utilization (4) Anomaly report and ops note status (5) system/subsystem
performance

> Status reports shall include, but not be limited to: (1) Daily and
> Weekly activity reports (2) Facility Status Report (3) Progress Report
> (4) Project Integration meetings (5) Delivery Schedules (6) Work plan
> (7) DRD status reports (8) Project Status Reports (9) Security reports
> (10) QA reports

Format: Metric reports shall be in accordance with JSC-27450 Performance
Measurement System Handbook. Technical performance metrics and
Surveillance Reports -- reference metrics handbooks listed under
applicable documents as a guide. Status reports are as defined by NASA.

Distribution: per Contracting Officer's letter

Maintenance - N/A

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0008
>
> DRD Title: Government Property Management Plan
>
> Data Type: 1
>
> Page: 1 / 2
>
> Description/Use - To describe the method of administering Government
> personal property.
>
> SOW Ref: 1.5.5.1.1
>
> Submission:

Initial -- Due with proposal

Final -- Due 90 days after contract award

Approval -- From contract award + 180 days

Submission Frequency -- as required

> Applicable Documents:

Federal Acquisition Regulation (FAR) Part 45

NASA FAR Supplement (NFS) Part 1845

> Data Preparation Information:

Scope -- The Government Property Management plan defines the
contractor\'s use, maintenance, repair, protection, and preservation of
Government personal property. It shall describe the contractor's
approach to receiving, handling, stocking, maintaining, protecting, and
issuing Government property.

Content -- This plan shall consist of those procedures which constitute
the contractor\'s Property Management Manual and shall include at a
minimum the following categories:

Property Management

Acquisition

Receiving

Identification

Records

Movement

Storage

Physical Inventories

Reports

Consumption

Utilization

Maintenance

Subcontractor Control

Disposition

Reconcile Contractor Records with Financial Records

Center -- Unique Considerations

Contractor Closeout

Facility

Format: Contractor's electronic format is acceptable

Distribution: distribution specified below plus additional distribution
per Contracting Officer's letter

Initial -- as specified in the Proposal instructions

Final -- Contracting Officer, COTR, Task Manager, each Facility Project
Manager

Update -- Contracting Officer, COTR, Task Manager, each Facility Project
Manager

> Maintenance - Revisions shall be incorporated by change page or
> complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

DRD No.: MSOC-JSC-0009

DRD Title: Small Business Subcontracting Plan and Reports

Data Type: Plan: 1 Report: 2

Page: 1 / 2

Description/Use - To describe the contractor\'s planned approach to
Small Business Subcontracting and their reporting against this plan.

SOW Ref.: 1.3.1.3

Submission:

> **Subcontracting Plan:**
>
> Initial - Subcontracting plan shall be submitted with offeror's
> proposal.
>
> Approval -- Prior to Contract Award
>
> Submission Frequency -- Subcontracting Plan to be updated in
> accordance with FAR 19.702
>
> **Reports:**

All reports shall be submitted in accordance with FAR 52.219-9 and NFS
1852.219-75.

SF 294 Subcontracting Report for Individual Contracts shall be submitted
semi-annually and at contract completion to the NASA/JSC Contracting
Officer.

SF 295 Summary Subcontract Report shall be submitted semi-annually to
NASA Headquarters, Coke K.

Applicable Documents: FAR 52.219.8 and 52.219.9 and NASA FAR Supplement
(NFS) 1852.219-75, 1852.219-76 and 1852.219-79.

Data Preparation Information:

> a\. Scope -- The Small Business Subcontracting Plan shall be in
> compliance with FAR 52.219.9. The Small Business Subcontracting
> Reporting shall be in compliance with NFS 1852.219-75.
>
> b\. Content - The Subcontracting plan must include the approach that
> the Contractor intends to use in meeting the subcontracting goals.
> Subcontractors whose bid is part of this proposal should be
> identified. For each subcontractor, the percentage of the proposal and
> any small or small business subcategory classification should be
> identified. For areas of potential future subcontracting, the
> Contractor should identify the area of work, the percentage of
> contract that this is expected to encompass, potential subcontractors
> and their small business or small business subcategory classification.
> Describe the management approach to subcontracting with small, and
> small disadvantaged 8(a) and HubZoned companies.
>
> c\. Format: Contractor format is acceptable for the plan the;
> reporting shall be in compliance with NFS 1852.219-75.
>
> d\. Distribution: distribution specified below plus additional
> distribution per Contracting Officer Letter.

i\. Initial -- as specified in the Proposal instructions

> ii\. Final -- Contracting Officer, COTR, Task Manager
>
> iii\. Update -- Contracting Officer, COTR, Task Manager

Maintenance - Revisions shall be incorporated by change page or complete
reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0010
>
> DRD Title: Information Technology (IT) Plan and Reports
>
> Data Type: Plan: 1 Reports: 2
>
> Page: 1 / 1
>
> Description/Use - To document the contractor's compliance with Federal
> and NASA IT Planning and Reporting regulations and requirements.

SOW Ref: 1.2.2.2

> Submission:

Plan Initial -- Due with proposal

Plan Final -- Due 30 days after contract award

Plan Approval -- Start of contract + 30 days

Plan Submission Frequency -- as required by MOD I/T Planning, Procedures
and Guidelines

Report Frequency -- per HSF Task Manager letter

> Applicable Documents:

JSC 27201 JSC/MOD Standard Facilities Practices and Technologies
Handbook

IT Management Reform Act of 1996 (the Clinger-Cohen bill)

Current JSC Chief Information Officer (CIO) instructions/guidelines for
I/T plans (JSC CIO and CFO web sites)

Office of Management and Budget Circular A-130 and A-11

Computer Security Act of 1987

JPG 2810.1 (or current version) JSC's I/T Security Handbook

Executive Order 12845, Energy-efficient Microcomputers

Section 508 of the Rehabilitation Act

JSC Capital Planning and Investment Control (CPIC) Process

Mission Operations Directorate I/T Planning, Procedures and Guidelines

> Data Preparation Information:

Scope --The plan shall document the contractor's compliance with Federal
and NASA IT planning and reporting regulations and requirements.

Content -- The contractor's Information Technology plan defines the
contractor's method to accomplish meeting IT POP, FY IT Plans, IT
Capital Planning and Investment Control, and IT Standards. .

Format: Plan -- As outlined in the MOD I/T Planning, Procedures and
Guidelines document

> -- Per HSF Task Manager letter

Distribution: distribution specified below plus additional distribution
per Contracting Office's letter

Initial -- as specified in the Proposal instructions

Final -- Contracting Officer, COTR, Task Manager

Update -- Contracting Officer, COTR, Task Manager

Reports -- Contracting Officer, COTR, Task Manager, NASA Facility
Project Managers

MOD Chief Information Officer

> Maintenance - Revisions shall be incorporated by change page or
> complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0011
>
> DRD Title: Emergency Preparedness and Disaster Recovery Plan
>
> Data Type: 1
>
> Page: 1 / 1
>
> Description/Use - To describe the contractor\'s approach for emergency
> preparedness and disaster recovery.

SOW Ref: 1.3.2.1

> Submission:

Initial -- Start of contract + 15 days

Final -- Start of contract + 45 days

Approval -- Start of contract + 90 days

Submission Frequency -- annual

> Applicable Documents:

NMI 1040.3 Emergency Preparedness Program

QS-EPP-95-001 NASA Emergency Preparedness Plan

JSC-05900 JSC Emergency Preparedness Plan

JPG 2810 IT Security Handbook

> Data Preparation Information:

Scope -- The Emergency Preparedness and Disaster Recovery Plan describe
the contractor\'s approach for emergency preparedness and disaster
recovery.

Content -- Content shall include the following: a risk analysis of all
facilities/systems; identification of specific equipment/facilities that
require backup or alternate sites; identification of backup strategies;
emergency response plans; backup facility/alternate sites operating
plans.

Format: Contractor's electronic format is acceptable.

Distribution: distribution specified below plus additional distribution
per Contracting Officer's letter

Initial -- as specified in the Proposal instructions

Final -- Contracting Officer, COTR, Task Manager, each Facility Project
Manager

Update -- Contracting Officer, COTR, Task Manager, each Facility Project
Manager

> Maintenance - Revisions shall be incorporated by change page or
> complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0012
>
> DRD Title: Reports/Reviews
>
> Data Type: 2
>
> Page: 1 / 1
>
> Description/Use -- To provide information necessary for NASA's insight
> function.
>
> SOW Ref.: 1.1, 1.2.1.3, 1.5.1.1.10, 1.5.1.2.10, 1.5.2.2.10, 1.5.2.3.10
>
> 6\. Submission:
>
> Initial -- Due at the end of the first reporting period after contract
> award
>
> Final -- Due at the end of the final reporting period
>
> Approval -- N/A
>
> Submission Frequency -- As described in table below

  ----- ----------------------- ---------------------- ----------------------------
        **Title**               **Frequency**          **Comments**

        [REPORTS]{.underline}                          

  1\.   Activity Report         Daily/Weekly           See DRD MSOC-JSC-0007

  2\.   Facility Status         Weekly                 See DRD MSOC-JSC-0007

  3\.   Progress Report         Weekly                 See DRD MSOC-JSC-0007

  4\.   Availability Report     Weekly                 See DRD MSOC-JSC-0007

  5\.   Metrics Report          Daily/Weekly/Monthly   See DRDs MSOC-JSC-0006 and
                                                       0007

  6\.   Status of DRDs          Monthly                See DRD MSOC-JSC-0007

                                                       

        REVIEWS/MEETINGS                               

  7\.   Program Manager Status  Monthly                DRD MSOC-JSC-0012
        Review                                         

  8\.   Operating Plan Review   As Required            DRD MSOC-JSC-0022

  9\.   POP Review              As Required            DRD MSOC-JSC-0022

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

  ----- -------------------------------------------------------------------
        **Title/Description**

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

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

  3\.   Project Status Review -- This monthly review documents
        accomplishments; changes in plans; problems being worked and
        proposed solutions consistent with the requirements of DRD
        MSOC-JSC-0006. . The discussion of plans, progress and problems
        shall include variance analysis and reporting cause, impact and
        corrective action. Technical issues shall be covered in terms of
        performance goals (metrics), exit criteria, schedule progress.
  ----- -------------------------------------------------------------------

> 7\. Applicable Documents: None
>
> 8\. Data Preparation Information:
>
> a\. Scope -- This DRD establishes the activity reporting for the
> Contractor's progress and accomplishments as well as performance and
> utilization of facilities/systems.
>
> b\. Content -- The report shall include quantitative descriptions of
> overall technical and administrative progress, and status, of
> significant activities relating to the accomplishments of the
> contractual objectives. Risks to the accomplishment of contractual
> objectives shall also be identified. The report shall also include
> performance and utilization data for major facilities and systems.
> Activity Report items covered shall included significant
> accomplishments, problems encountered, quality assurance results,
> corrective actions. Metrics Report items shall be in accordance with
> DRD MSOC-JSC-0006 and 0007. All reports shall be of sufficient depth
> and clarity to permit understanding and evaluation of progress made.
> Supporting data in the form of charts, graphs, etc. may be included as
> appropriate.
>
> c\. Format: To be determined by mutual agreement with the COTR and TM.
>
> d\. Distribution: distribution specified below plus additional
> distribution per Contracting Officer's letter
>
> i\. Initial -- as specified in the Proposal instructions
>
> ii\. Final -- Contracting Officer, COTR, Task Manager, each Facility
> Project Manager
>
> iii\. Update -- Contracting Officer, COTR, Task Manager, each Facility
> Project Manager
>
> 9\. Maintenance - Revisions shall be incorporated by change page or
> complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0013
>
> DRD Title: Reprocurement Data Package
>
> Data Type: 2
>
> Page: 1 / 2
>
> Description/Use - Provide content and format requirements for delivery
> to NASA of all analytical models, tools, supporting documentation,
> equipment, data items and resource/cost information used to perform
> future reprocurement activities. **Data contained in Paragraph 7.e.i,
> "Labor Resources", Paragraph 7.e.ii, "Non-labor Resources", and
> Paragraph 7.e.iii may be marked "Lockheed Martin Proprietary Data" and
> "Competition Sensitive". Data contained in Paragraph 7.e.iv,
> "Technical and Process Information" may be disclosed to competing
> offerors in the future.**
>
> SOW Ref.: N/A

Submission:

Initial/Final -- One deliverable at the CO's direction

Approval -- N/A

Submission Frequency - No periodic submissions required per this DR
(this does not relieve the requirement for periodic or incremental
deliveries per other DRs).

Applicable Documents: None

Data Preparation Information:

Scope -- Analytical models, unique tools, supporting documentation,
equipment and resource/cost information shall be submitted in accordance
with this Data Requirement (DR).

Content -- Data package containing the following:

Labor resources:

List of all direct labor skills by labor category, segregated by current
work breakdown structure (WBS)

An estimate of the number of indirect labor skills such as business or
computer support normally charged through an indirect expense pool or
through a service center expense

Current annual average wage rates for each labor category and when these
wages were last adjusted for escalation. Also indicate whether any
adjustments are projected to be made prior to contract expiration

The number of FTEs (Full Time Equivalents) and the estimated number of
productive hours for each labor category currently on contract,
segregated by current WBS.

Seniority level of all skills on the current contract

Non-labor resources:

List of all materials, equipment, travel, supplies, etc., and the
incurred annual cost by WBS. Only include significant items that are
used to perform the technical requirements of this contract.

Provide a discussion associated with the major items identified above,
such as the materials estimate includes a prompt payment discount of
TBD% due to large volume discounts you have negotiated with your
vendors.

The projected liability cost associated with unused accrued paid leave
associated with non-exempt personnel. Provide a copy of any Collective
Bargaining Agreements in place and a current status of any upcoming
negotiations with a union.

Technical and Process Information:

> [Data Requirement Descriptions (DRDs):]{.underline}
>
> MSOC-JSC-0002, Management Plan
>
> MSOC-JSC-0007, Metric and Status Reports
>
> MSOC-JSC-0008, Government Property Management Plan
>
> MSOC-JSC-0010, Information Technology Plan and Reports
>
> MSOC-JSC-0012, Reports/Reviews (excluding Program Manager Status
> Review charts)
>
> MSOC-JSC-0061, Configuration Management Plan
>
> MSOC-JSC-0062, Level A and B Requirements
>
> MSOC-JSC-0063, Interface Control Document

MSOC-JSC-0073, Design Specifications

Format: Electronic format of all submissions shall be compatible with
ODIN desktop standard applications or other ISS standard tools.
Organizational format of the supporting documentation shall be the
contractor's format

Distribution: Distribution per Contracting Officer's letter

> 8\. Maintenance - All models/tools and data items shall be maintained
> electronically. All documentation developed to support the use of each
> model/tool and data items shall also be maintained electronically.
> Both the models and the supporting documentation shall be updated as
> necessary to perform the assessments for which they were developed.

DATA REQUIREMENTS DESCRIPTION (DRD)

DRD No.: MSOC-JSC-0014

DRD Title: Contractor-Held Property Reporting

Data Type: 2

Page: 1 / 2

Description/Use - To report NASA Property in the custody of Contractors.

> SOW Ref.: N/A

6\. Submission:

The due date for the final Property Financial Reporting quarterly
submission is July 21, 2004 for the quarter ending June 30, 2004. After
this, quarterly Property Financial reporting requirements will be
changed to monthly reporting.

The data required for the monthly submission is due the 21^st^ day after
the close of the month, beginning August 21, 2004. The first monthly
submission will be for the month of July 2004. Example due dates for the
monthly submission are as follows:

August 21 for the month ending July 31

September 21 for the month ending August 31

October 21 for the month ending September 30

The due date for the Financial Property annual submission (NASA Form
1018) is November 30.

All reports shall be submitted electronically.

7\. Applicable Documents: Procurement Information Circulars (PIC) 03-14
and 04-12 and NASA FAR Supplement Subpart 1845.7101.

8\. Data Preparation Information:

> Quarterly Property Financial Report, due July 21, 2004, is required to
> be submitted using the spreadsheet located at the URL referenced in
> PIC 03-14.
>
> Monthly Property Financial Reports are required to be submitted using
> the format located at the URL referenced in paragraph below. Monthly
> Financial Report will be submitted in accordance with PIC 04-12.
>
> Annual Property NF 1018 reports shall be submitted using the NF 1018
> Electronic Submission System (NESS).
>
> The NF1018 shall be completed in accordance with NASA FAR Supplement
> Subpart 1845.7101 and any supplemental guidance provided by the
> Contracting Officer.

9\. Content

Monthly Report General Instructions:

> a\. Monthly property financial reports are required with item level
> supporting data. This data shall be submitted for all items with an
> acquisition cost of \$100,000 or more, in the contractor's and its
> subcontractors' possession, in the following classifications: real
> property, equipment, special test equipment, special tooling, and
> agency peculiar property. Monthly reporting is not required for
> property in the above classifications with an acquisition cost under
> \$100,000. Monthly data shall also be submitted for items of any
> acquisition cost in the classifications of materials and contract
> work-in-process (WIP). Itemized monthly data is required for materials
> and WIP line items of \$100,000 and over. Summary monthly data is
> required for materials and WIP line items under \$100,000. The monthly
> reports shall be electronically submitted using the Contractor-Held
> Asset Tracking System (CHATS) (http://nasachats.gsfc.nasa.gov/) using
> the format described in the CHATS user\'s manual.
>
> b\. Acquisition costs shall be developed using actual costs to the
> greatest extent possible, especially costs directly related to
> fabrication such as labor and materials. Supporting documentation
> shall be maintained and available for all amounts reported, including
> any amounts developed using estimating techniques.
>
> All Adjustments shall be thoroughly explained and directly related to
> a specific fiscal year. If the fiscal year cannot be determined, the
> default shall be the previous fiscal year.
>
> Work Breakdown Structures (WBS) shall be provided for all Contractor
> acquired property (CAP), WIP, and any new materials acquired. The
> format shall be a five digit numerical level. (i.e. 803-10). If the
> WBS is not identifiable, contact the NASA CFO Property Branch for
> further guidance, as outlined below.

10\. NF 1018 Reports

> a\. Contractors shall report all NASA-owned property in US dollars,
> regardless of location.
>
> Negative reports are required.
>
> This reporting shall be completed in accordance with the NASA FAR
> Supplement (NFS) Subpart 1845.7101 and any supplemental guidance
> provided by the Contracting Officer.

11\. Distribution

> a\. The monthly reports shall be electronically submitted using the
> Contractor-Held Asset Tracking System (CHATS)
> (http://nasachats.gsfc.nasa.gov/) using the format described in the
> CHATS user\'s manual.
>
> b\. NASA Form (NF) 1018 reports shall be submitted using the NF 1018
> Electronic Submission System (NESS) (<http://ness.gsfc.nasa.gov/>).

12\. Maintenance

a\. Revisions shall be incorporated by change page or complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

DRD No.: MSOC-JSC-0015

DRD Title: Customer Reporting

Data Type: Initial Baseline Report: 1 Monthly Report: 2

Page: 1/ 2

Description/Use - The Customer report provides insight into the fully
loaded cost per Human Space Flight and Space Communications CWBS Element
enabling it for use in the JSC IFMP system.

Submission:

Baseline Report:

Initial: 30 days from contract start

Approval: Initial contract -12/15/03 Subsequent -- GFY minus 30 days

Submission Frequency: GFY minus 60 days

Monthly Report:

Initial -- Synchronized with NASA 533 report.

Final -- Synchronized with NASA 533 report

Approval -- Due 90 days from contract start

Submission Frequency --

> Monthly - Due not later than 10 days following the close of the
> contractor\'s monthly accounting period.
>
> The due dates reflect the date the Customer reports are received by
> personnel on the distribution list, not the date the reports are
> generated or mailed by the contractor. It is critical that the
> Customer reports are submitted in a timely manner to ensure adequate
> time for NASA to analyze and record the cost into the NASA accounting
> system.

Applicable Documents: none

Data Preparation Information:

Format -- Baseline Report -- Establishes and Documents the load
allocation agreement per CWBS.

Format -- Monthly Report

Monitory information will be reported thru " Adjusted Total: Cost Plus
Fee"

Header Information required include the following information with
title:

Accounting Calendar Period (i.e. July 2003)

Accounting Calendar Period start and end dates (i.e. 06/23/03 --
07/20/03)

CWBS number

Data required -- Columns

Current Month: Actual Hours, Actual Dollars

GFY Cum-to-Date: Actual Dollars

Next Month Estimate: Hours, Dollars

Contract Cum-to-Date: Dollars

Data required - Rows

Cost

Allocated line items

Total Adjusted Cost

Distribution:

Copies/Distribution:

> MOD Resources Office -- MSOC: 1 hard copy and 1 copy electronically
>
> Financial Management Division -- MSOC: 1 hard copy and 1 copy
> electronically
>
> Contracting Officer - 1 hard copy
>
> COTR - 1 hard copy
>
> Technical Manager - 3 hard copy

Maintenance - change pages or complete reissue shall incorporate
Changes.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. DRD No.: MSOC-JSC-0020

2\. DRD Title: NF533 M/Q Cost Reporting

3\. Data Type: Initial Baseline Reports: 1 NASA Forms 533 M/Q: 2

4\. Page: 1/ 4

5\. Description/Use - The NASA Form 533 (NF533) reports provide data
necessary for the following:

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

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

Planning, monitoring, and controlling project and program resources.

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

SOW Ref: 1.2.

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

6\. Submission: The due dates for the NF533M and NF533Q reports are
outlined in Chapter 3 of NPG 9501.2D. The following is a summary of the
NF533 due date requirements.

> a\. Initial -- NASA Form 533Q - Within 30 days after authorization to
> proceed.

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

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

> b\. Final -- n/a (see item 6. i.)

c\. Approval -- Due 90 days from contract start

d\. Submission Frequency --

> 533M - Due not later than 10 days following the close of the
> contractor\'s monthly accounting period.
>
> 533Q - Due not later than the 15th day of the month preceding the
> quarter being reported.
>
> The due dates reflect the date the NF533 reports are received by
> personnel on the distribution list, not the date the reports are
> generated or mailed by the contractor. It is critical that the NF533
> reports are submitted in a timely manner to ensure adequate time for
> NASA to analyze and record the cost into the NASA accounting system.

7\. Applicable Documents:

a\. NFS 1852.242-73 NASA Contractor Financial Management Reporting

> b\. NMI 9501.1 NASA Contractor Financial Management Reporting Systems

c\. NPG 9501.2C NASA Contractor Financial Management Reporting.

8\. Data Preparation Information:

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. Examples of accrual accounting for
common cost elements reported on the NF533 follow:

[Cost Elements:]{.underline}

*Labor:* Reported to NASA as hours are incurred.

*Equipment & Materials* (commercial off the shelf) Generally reported to
NASA when received and accepted by the contractor.

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

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

*Travel:* Reported to NASA as costs are incurred.

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

*Unfilled Orders:* Reported as the difference between the cumulative
cost incurred to date and amounts obligated to suppliers and
subcontractors.

*Fee:* Should be accrued as earned using a consistent and auditable
method to determine the amount. For example: an acceptable method would
be to use historical data to determine the amount to accrue each month.
Fee should be reported on the NF533 following the \"Total Cost\" line.
Award fee must be reported by the following categories: Base Fee, Fee
Earned, Interim Fee, Provisional Fee, Potential Additional Fee, and
Total Fee. If any of the above fee categories do not pertain, they
should not be included in the NF533.

*Prompt Payment Discounts:* Cumulative cost reported to NASA should be
the full-incurred cost. The prompt payment discount amount taken should
be reported as a separate line item on the NF533 below the cumulative
cost amounts for the contract.

The NF533 reports are the official cost documents used at NASA for cost
type, price determination, and fixed price incentive contracts. The data
contained in the reports must be auditable using Generally Accepted
Accounting Principles. Supplemental cost reports submitted in addition
to the NF533 must be reconcilable to the NF533.

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

For contracts, which have multiple schedules, a summary NF533 is
required to provide a cumulative from inception cost for the contract,
regardless of schedule.

An initial NF533 report is required in the NF533Q format to be used as a
baseline for the life of the contract. The initial (baseline) NF533Q
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 30 days after the incurrence of cost.

Column 7b (planned cost incurred/hours worked for the month) and 7d
(cumulative planned cost incurred/ hours worked) of the NF533M represent
the negotiated baseline plan for the contract. There may not be a
relationship between the estimates provided in columns 8 of the NF533M
to columns 7b and 7d. 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 cost adjustments should be reported in column 7a and 7c of
NF533M and column 7a of the NF533Q with a footnote discussing the
reasons for and amounts of the adjustments.

Monthly NF533 reporting is no longer required once the contract is
physically complete, provided the final cost report includes actual cost
only (no estimates or forecasts). The contractor must continue to submit
monthly NF533 reports as long as estimates for the following period are
included. If the final cost of a contract changes after the submission
of the \"final\" contractor cost report, the contractor must submit a
revised NF533 report in the month the cost change is recognized.

Format: (See attached) The reports shall be prepared in accordance with
NPG 9501.2C or its most current revision, NMI 9501.1, and NFS
1852.242-73 and as defined in the statement of work and by contracting
officer's letter. All reports shall be provided electronically and in
hard copy form. The contractor shall report cost and hours via
electronic submission or diskette and shall be compatible with Microsoft
Excel. A hardcopy of the data shall accompany either method and shall be
signed by the same person who signs the hard copy NF533. The totals of
the submitted data shall agree with the NF533 totals.

Format Adjustments:

Information on all 533M & Q pages are reported thru "Adjusted Total:
Cost Plus Fee".

Addition of Government Fiscal Year (GFY) information:

GFY Cum-to-Date

GFY EAC

Balance of GFY (keep)

533 reports header section will contain the following information with
title:

Accounting Calendar Period (i.e. July 2003)

Accounting Calendar Period start and end dates (i.e. 06/23/03 --
07/30/03)

Operating Days and Effective Hours (i.e. 19 days / 133 hrs)

Distribution:

Initial -- as specified per Contracting Officer's letter

Final -- Formatting and electronic distribution per Contracting
Officer's letter

Update \-- Formatting and electronic distribution per Contracting
Officer's letter

Copies/Distribution:

LM4/MOD Resources Office - 1 hard copy and 1 copy electronically

> LF6/Financial Management Division - 1 hard copy and 1 copy
> electronically

BH/Contracting Officer - 1 hard copy

DA3/COTR - 1 hard copy

DV/Technical Manager - 3 hard copy

9\. Maintenance - change pages or complete reissue shall incorporate
Changes.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0021
>
> DRD Title: Wage/Salary and Fringe Benefit Data
>
> Data Type: 2
>
> Page: 1 / 6
>
> Description/Use - The Wage/Salary and Fringe Benefit Data shall be
> used by the NASA Contracting Officer and the Contract 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.
>
> SOW Ref: 1.2
>
> Submission:

Initial -- February 1, 2004

> Submission Frequency - Annually, 90 days prior to the anniversary date
> of the contract.
>
> Applicable Documents: FAR 52.222-41
>
> Data Preparation Information:

Scope -- The Wage/Salary and Fringe Benefit Data shall 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.

Content The Wage/Salary and Fringe Benefit Data shall contain the data
included in the enclosed DRD forms, titled "Wage/Salary Rate
Information", "Fringe Benefit for Service Employees", and Fringe
Benefits per Collective Bargaining Agreement". The Wage/Salary Rate
Information shall contain a listing of all exempt and nonexempt labor
classifications on the contract. Separate forms shall be utilized for
classifications in different geographic areas and for each
subcontractor. Wage determination numbers, appropriate labor
organization names, and subcontractor names, shall be reflected. All
nonexempt labor classifications shall 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
shall reflect the actual lowest and highest paid employees, along with a
computed average rate. State the number of employees in each labor
category. Separate Fringe Benefit forms shall be completed for
non-represented classifications and for each separate Collective
Bargaining Agreement (CBA). A separate form shall be completed for the
prime and each subcontractor. Three copies of each Collective Bargaining
Agreements are required.

Format: The Wage/Salary and Fringe Benefit Data shall be in a format
substantially the same as enclosed with this DRD. (Forms 2, 3, and 3A
enclosed).

Distribution: Per Contracting Officer's Letter

> Maintenance - Changes shall be incorporated as required by change page
> or complete reissue.

+--------------+--------------+----------+---------+-------+----------+
| FORM 2       |              |          |         |       |          |
|              |              |          |         |       |          |
| WORK SHEET   |              |          |         |       |          |
| FOR SF-98    |              |          |         |       |          |
| DATA         |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
| WAGE RATE    |              |          |         |       |          |
| INFORMATION  |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
| CONTRACTORS  | WAGE         | EXEMPT   | UNION   | CU    | MYE NO   |
| LABOR        | D            | OR       | OR      | RRENT | OF       |
|              | ETERMINATION |          |         | H     |          |
|              |              |          |         | OURLY |          |
+--------------+--------------+----------+---------+-------+----------+
| [CLA         | [CLA         | [NONEXE  | [       | [RA   | [EMPLOY  |
| SSIFICATION] | SSIFICATION] | MPT]{.un | NONUNIO | TE]{. | EES]{.un |
| {.underline} | {.underline} | derline} | N]{.und | under | derline} |
|              |              |          | erline} | line} |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
| Illustration |              |          |         |       |          |
| of required  |              |          |         |       |          |
| data:        |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
| Project      | Not Required | E        | N       | \$    | 1        |
| Manager      |              |          |         | 25.00 |          |
+--------------+--------------+----------+---------+-------+----------+
| Supervisor   | Not Required | E        | N       | \$    | 1        |
|              |              |          |         | 20.00 |          |
+--------------+--------------+----------+---------+-------+----------+
| Electrical   | Not Required | E        | N       | \$16  | 3        |
| Engineer     |              |          |         | .50 - |          |
|              |              |          |         | \$    |          |
|              |              |          |         | 20.00 |          |
+--------------+--------------+----------+---------+-------+----------+
| Technician,  | Elect Tech   | N        | U       | \$12  | 12       |
| Jr           | Main 1       |          |         | .78 - |          |
|              |              |          |         | \$    |          |
|              |              |          |         | 15.50 |          |
+--------------+--------------+----------+---------+-------+----------+
| Technician,  | Elect Tech   | N        | U       | \$18  | 4        |
| Sr           | Main II      |          |         | .20 - |          |
|              |              |          |         | \$    |          |
|              |              |          |         | 20.00 |          |
+--------------+--------------+----------+---------+-------+----------+
| Secretary    | Secretary I  | N        | N       | \$11  | 2        |
|              |              |          |         | .11 - |          |
|              |              |          |         | \$    |          |
|              |              |          |         | 12.50 |          |
+--------------+--------------+----------+---------+-------+----------+
| File Clerk   | General      | N        | N       | \     | 1        |
|              | Clerk II     |          |         | $8.29 |          |
+--------------+--------------+----------+---------+-------+----------+
| Clerical     | Word         | N        | N       | \$9   | 3        |
| Data Entry   | Processor I  |          |         | .25 - |          |
|              |              |          |         | \$    |          |
|              |              |          |         | 10.90 |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
| Submit data  |              |          |         |       |          |
| in the       |              |          |         |       |          |
| above        |              |          |         |       |          |
| -illustrated |              |          |         |       |          |
| format for   |              |          |         |       |          |
| all labor    |              |          |         |       |          |
| cla          |              |          |         |       |          |
| ssifications |              |          |         |       |          |
| used, or     |              |          |         |       |          |
| planned to   |              |          |         |       |          |
| be used, on  |              |          |         |       |          |
| this         |              |          |         |       |          |
| contract.    |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
| All          |              |          |         |       |          |
| contractor   |              |          |         |       |          |
| labor        |              |          |         |       |          |
| cla          |              |          |         |       |          |
| ssifications |              |          |         |       |          |
| shall be     |              |          |         |       |          |
| matched to   |              |          |         |       |          |
| wage         |              |          |         |       |          |
| d            |              |          |         |       |          |
| etermination |              |          |         |       |          |
| classes      |              |          |         |       |          |
| listed in    |              |          |         |       |          |
| CBA\'s       |              |          |         |       |          |
| represented  |              |          |         |       |          |
| classes or   |              |          |         |       |          |
| classes      |              |          |         |       |          |
| shown in WD  |              |          |         |       |          |
| 94-2516 for  |              |          |         |       |          |
| no           |              |          |         |       |          |
| nrepresented |              |          |         |       |          |
| classes.     |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
| CONTRACTORS  | WAGE         | EXEMPT   | UNION   | CU    | MYE NO   |
| LABOR        | D            | OF       | OR      | RRENT | OF       |
|              | ETERMINATION |          |         | H     |          |
|              |              |          |         | OURLY |          |
+--------------+--------------+----------+---------+-------+----------+
| [CLA         | [CLA         | [NONEXE  | [       | [RA   | [EMPLOY  |
| SSIFICATION] | SSIFICATION] | MPT]{.un | NONUNIO | TE]{. | EES]{.un |
| {.underline} | {.underline} | derline} | N]{.und | under | derline} |
|              |              |          | erline} | line} |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+
|              |              |          |         |       |          |
+--------------+--------------+----------+---------+-------+----------+

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)

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)

DRD No.: MSOC-JSC-0022

DRD Title: FY Operating Plan (FY Op Plan) and Program Operating Plan
(POP)

Data Type: Op Plan: 1 / POP: 2

Page: 1 / 1

Description/Use -- The contractor shall provide a separate annual FY
Operating Plan and POP for each of the Technical services under this
contract.

> SOW Ref.: 1.2.1.3,
>
> 1.5.1.1.2, 1.5.1.1.3, 1.5.1.2.2, 1.5.1.2.3, 1.5.2.1.2, 1.5.2.1.3,
> 1.5.2.2.2, 1.5.2.2.3, 1.5.2.3.2, 1.5.2.3.3, 1.5.3.1.2, 1.5.3.1.3,
> 1.5.4.1.2, 1.5.4.2.3, 1.5.4.6.3, 1.5.4.8.2, and 1.5.5.1.4.

Submission:

Initial -- FY Op Plan - Jan 15 of each year, POP -- As Required

Final -- FY Op Plan - July 15 of each year, POP -- As Required

Approval -- FY Op Plan - Aug 15 of each year, POP -- As Required

Submission Frequency -- FY Op Plan, every six months, POP -- As Required

> For the first delivery Final 12/1/03 and Approval 12/15/03.

Applicable Documents: N/A

Data Preparation Information:

Scope -- The FY Operating Plan and POP will include a detailed analysis
of the content and cost for the future Government Fiscal Year. The POP
will contain a minimum of a 5-year forecast.

Content. The FY Operating Plan and POP shall include the plans
associated with modification, sustaining, Program support, and
Architecture and engineering support.

Format: electronic copy and hardcopy

Distribution: per Contracting Officer's letter

Maintenance - N/A

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0023
>
> DRD Title: Travel Plan
>
> Data Type: 2
>
> Page: 1 / 1
>
> Description/Use - To describe the contractor\'s projected travel
> requirements in support of HSF objectives per fiscal year.

SOW Ref: 1.2.1.3, 1.4.1, and 1.5.4

> Submission:

Initial -- Start of contract + 30 days

Final -- Start of contract + 45 days

Approval -- Start of contract + 60 days

Submission Frequency -- annually 2 months prior to FY start August
1^st^.

> Applicable Documents: none
>
> Data Preparation Information:

Scope --The Travel Plan shall describe the travel plans and purpose
required to meet the HSF objectives per fiscal year.

Content -- The Travel Plan shall address the contractor\'s plans by SOW
item. Identifying purpose, dates and duration for travel.

Format: Contractor's electronic format is acceptable

Distribution: distribution as specified below plus additions per
Contracting Officer's letter

Initial -- as specified in the Proposal instructions

Final -- Contracting Officer, COTR, Task Manager, Facility PM

Update -- Contracting Officer, COTR, Task Manager, Facility PM

> Maintenance - Revisions shall be incorporated by change page or
> complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0024
>
> DRD Title: Workforce Reports
>
> Data Type: 2
>
> Page: 1

Description/Use - To provide workforce information by geographic
location.

SOW Ref: 1.2.

> Submission:

Initial -- 10 Workdays after initial month end

Final -- n/a

Approval -- Due 90 days from contract start

Submission Frequency --

> Monthly Workforce Report - Monthly, no later than the 10th day
> following the close of the accounting period.
>
> As Requested Workforce Report - As directed.
>
> Data Preparation Information:

Scope -- The reports provide workforce data by geographic location.
There are two types of reports:

Monthly Workforce Report by location

As Requested Workforce Report

Content -- The monthly workforce report should provide Equivalent
Personnel (EPs) by location, specifically on or near site (JSC), and by
State for workforce outside of the Clear Lake area. The data should be
reconcilable to other financial deliverables. The content of the As
Requested Workforce Report will vary based on specific direction
provided by NASA Headquarters to support congressional inquiries. Its
most common form is an annual request to provide workforce by Zip Code.

Format: Specific formatting to be tailored by DV/Contractor.

Distribution:

Initial -- as specified per Contracting Officer's letter

Final -- Formatting and electronic distribution per Contracting
Officer's letter

Update -- Formatting and electronic distribution per Contracting
Officer's letter

Maintenance - Changes shall be incorporated by change page or complete
reissue.

Distribution:

Contracting Officer: 1 copy

LM4/Resources Analyst: 1 copy

COTR: 1 copy

DATA REQUIREMENTS DESCRIPTION (DRD)

DRD No.: MSOC-JSC-0030

DRD Title: Safety and Health Plan

Data Type: 1

Page: 1 / 10

Description/Use - Establishes Safety, Health, and Environmental
Compliance Plan for contractors providing support to JSC organizations.
\*\*\*The Office of Primary Responsibility for this DRD is the JSC
Safety, Reliability, and Quality Assurance Office. [NOTE: UPON NASA
APPROVAL, THE CONTRACTOR'S SAFETY, HEALTH, and ENVIRONMENTAL COMPLIANCE
PLAN (\"The Plan\") BECOMES A CONTRACTUAL REQUIREMENT.]{.underline}

> SOW Ref.: 1.3.2.2 Submission:

Initial -- Due with proposal

Final -- Due 60 days after contract award

Approval -- Start of contract

Submission Frequency -- as required

Applicable Documents: NPG 8715.3 (as revised); JPG 1700.1 (as revised)

Data Preparation Information:

Scope --

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

> [Management Leadership and Employee Participation.]{.smallcaps}

Policy. Provide the contractor's safety, health, and environmental
compliance policy statement with the plan. Compare the contractor's
policy statement with those of NASA and OSHA and discuss any
differences.

Goals and Objectives.

Describe specific safety and health goals and objectives to be met.
Discuss status of safety program using the "Performance Evaluation
Profile" as safety performance criteria. Describe the contractor's
approach to continuous improvement (including milestone schedule) using
level 5 of the Performance Evaluation Profile as a guideline.

Describe Environmental Goals & Objectives to be met for the following:

Pollution Prevention and Source Reduction of:

Hazardous and Industrial Solid Wastes

Solid Wastes (trash, refuse)

Wastewater Discharges (sanitary sewerage)

Air Emissions

Medical & Radiological Discharges

Affirmative Procurement (Purchase of Environmentally Preferable
Materials IAW Executive Order)

Hazardous Materials Handling/Purchasing/Reduction/Replacement

> Elimination from Specifications and Standards requirements for the use
> of
>
> Hazardous/Toxic Substances & Materials

Use of an Environmental Planning Checklist to review & document Impacts
of New and Modified Programs, Projects, Activities and Operations.

Life cycle analysis and costing

Incorporating Environmental Requirements in Subcontracts

Participation in JSC Recycling

Outreach programs

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

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

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

Safety Representative - identify by title the individual who shall be
trained and certified in accordance with JPG 1700.1 to be responsive to
Center-wide safety, health, environmental, and fire protection concerns
and goals, and who shall participate in meetings and other activities
related to the JSC Safety and Health program.

Company Physician/Occupational Injury/illness case manager - identify a
point of contact who is responsible for the transfer or receipt of
company medical data and who shall be the primary contact for the
company in the event any employee suffers a work related injury or
illness (such as the company physician) by name, address, and telephone
number to the JSC Clinic, mail code SD22. This shall facilitate
communication of medical data to contractor management. Prompt
notification to the JSC Occupational Health/ Clinic shall be given of
any changes that occur in the identity of the point of contact. A letter
to the JSC Occupational Health Office can accomplish initial
identification of point of contact and subsequent updates with a copy
sent to the Contracting Officer. The initial letter is to be received by
the Government prior to contract start.

Building Fire Wardens - provide a roster of fire wardens (their names,
phone numbers and pagers, and mail codes). Contractor fire wardens are
needed to facilitate the JSC fire safety program, including coordination
of related issues with NASA facility managers and emergency planning and
response officials and their representatives. Fire wardens shall be
trained in accordance with JPG 1700.1. The roster shall be maintained by
letter to JSC Occupational Safety, mail code NS2, with copies to the
Contracting Officer and COTR. The initial letter shall be received by
the Government not later than 15 days after contract start.

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

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

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

Program Evaluation. The program evaluation consists of:

Participation in a Performance Evaluation Profile (PEP) survey at the
request of the Government. The PEP survey normally shall be scheduled
and administered at the discretion of the Government. If the Government
chooses not to do the PEP in a given year, the contractor may at its
option initiate its own PEP by contacting JSC Occupational Safety, code
NS2, for assistance. The contractor shall not be required to take two or
more PEP surveys in any contract year.

\[Reserved.\]

A written self-evaluation report to be delivered by Sept 30 of each
year. The self-evaluation shall follow the VPP program evaluation report
format found in OSHA TED 8.1, Revised Voluntary Protection Programs
(VPP) Policies and Procedures Manual, Appendix H, \"Format for Program
Evaluation Report\", as mandated by the cognizant OSHA regional office.
Contractors who have submitted a written self-evaluation as a VPP site
may submit their original report to OSHA in lieu of writing a new self
-evaluation provided that all action plans and status are updated. The
self-evaluation shall as a minimum cover the elements of the approved
safety and health plan.

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

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

Date of report, contractor identity and contract number.

For each person listed, provide name, social security number, and date
of termination.

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

[Material Safety Data.]{.underline} The contractor shall prepare and/or
deliver Material Safety Data for hazardous materials brought onto
Government property or included in products delivered to the Government.
This data is required by the Occupational Safety and Health
Administration (OSHA) regulation, 29 CFR 1910.1200, "Hazard
Communication", EPA "Emergency Planning and Community Right-to-Know
(EPCRA, ref. 40 CFR 302, 311, 312); and the Texas Department of Health
(TDH, ref. Chapters 505-507 of the Health and Safety Code), and Federal
Standard 313 (or FED-STD-313), "Material Safety Data, Transportation
Data and Disposal Data for Hazardous Materials Furnished to Government
Activities", as revised. 1 copy of each MSDS shall be sent upon receipt
of the material for use on NASA property to the JSC Central Repository,
Occupational Health and Test Support, Mail Code SD13, along with
information on new or changed locations and/or quantities normally
stored or used. If the MSDS arrives with the material and is needed for
immediate use, the MSDS shall be delivered to the Central Repository by
close of business of the next day after it enters the site.

[Hazardous Materials Inventory]{.underline}. The contractor shall
compile an inventory report of all hazardous materials it has located on
Government property not less than annually, and which is within the
scope of 29 CFR 1910.1200, "Hazard Communication"; and Federal Standard
313 (or FED-STD-313), "Material Safety Data, Transportation Data and
Disposal Data for Hazardous Materials Furnished to Government
Activities", as revised. The call for this annual inventory and
instructions for delivery shall be issued by the JSC Occupational Health
and Test Support Office, mail code SD13. This information shall use the
format used by JSC for chemical inventory compilation to provide the
following:

the identity of the material;

the location of the material by building and room;

the quantity of each material normally kept at each location

peak quantity stored

actual or estimated rate of annual usage of each chemical

Government Access to Safety and Health Program Documentation. The
contractor shall recognize in its plan that it shall be expected to make
all safety, health, and environmental documentation (including relevant
personnel records) available for inspection or audit at the Government's
request. Electronic access by the Government to this data is preferred
as long as Privacy Act requirements are met and Government safety and
health professionals and their representatives have full and unimpeded
access for review and audit purposes. For contractor activities
conducted on NASA property, the contractor shall identify what records
it shall make available to the Government in accordance with the
Voluntary Protection Program criteria of OSHA as implemented in JPG
1700.1, "JSC Safety and Health Handbook", as revised. For the purpose of
this plan, safety, health, and environmental compliance documentation
includes but is not limited to logs, records, minutes, procedures,
checklists, statistics, reports, analyses, notes, or other written or
electronic document which contains in whole or in part any subject
matter pertinent to safety, health, environmental protection, or
emergency preparedness.

The contractor may be requested to participate in the review and
modification of safety requirements that are to be implemented by the
Government including any referenced documents therein. This review
activity shall be implemented at the direction of the NASA COTR in
accordance with established NASA directives and procedures.

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

Certified Professional Resources. Discuss your access to certified
professional resources for safety, health, and environmental protection.
Discuss their roles in motivation/awareness, worksite analysis, hazard
prevention and control, and training.

> [Worksite Analysis.]{.smallcaps} Hazards shall be systematically
> identified through a combination of surveys, analyses, and inspections
> of the workplace, investigations of mishaps and close calls, and the
> collection and trend analysis of safety and health data such as:
> records of occupational injuries and illnesses; findings and
> observations from preventive maintenance activities; reports on
> hazardous substance spills and inadvertent releases to the
> environment; facilities related incidents related to partial or full
> loss of systems functions; etc. Hazards identified by any of the
> techniques identified below shall be ranked and processed in
> accordance with JPG 1700.1. All hazards on NASA property, which are
> immediately dangerous to life or health, shall be reported immediately
> to the Occupational Safety Office. All safety engineering products
> that address operations, equipment, etc., on NASA property shall be
> subject to JSC SR&QA review and concurrence unless otherwise waived by
> the JSC Occupational Safety Office.

Industrial Hygiene. Describe your industrial hygiene program and how it
shall be coordinated with the JSC government provided resources for
industrial hygiene. In the event corporate resources are used to
determine workplace exposures, copies of all monitoring data shall be
provided to JSC Occupational Health within 15 days of receipt of
results.

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

Comprehensive Survey -- A "wall to wall" engineering assessment of the
work site including facilities, equipment, processes, and materials
(including wastes -- (TNRCC/EPA solid & hazardous, radioactive,
explosives, medical-infectious-biological). )). The comprehensive survey
shall establish a baseline of hazards that may put contract assets at
risk as early as is feasible, preferably at contract start.

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

Hazard Analysis -- may address facilities, systems/subsystems,
operations, processes, materials (including waste), and specific tasks
or jobs. Analyses and report formats shall be in accordance with JSC
17773, \"Preparing of Hazard Analyses for JSC Ground Operations.\"

Inspections.

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

Discrepancies between observed conditions and current requirements, and

New (not previously identified) or modified hazards.

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

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

Accident and Record Analysis[.]{.smallcaps}

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

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

> Accident/Incident Summary Report. The contractor shall prepare and
> deliver Accident/Incident Summary Reports as specified on JSC Form
> 288, "Accident / Incident Statistics" (attached), as revised. All new
> and open mishaps, including vehicle accidents, incidents, injuries,
> fires, and close calls shall be described in summary form along with
> current status. Negative reports are also required monthly. Report
> frequency is monthly; Date due is the 10^th^ day of the month
> following each month reported. Report to be delivered to the JSC
> Safety, Reliability, and Quality Assurance Office through the
> Occupational Safety Office, mail code NS2, by fax to 281-244-0426 or
> by attaching to an e-mail and transmitting to
> mishaps@ems.jsc.nasa.gov.
>
> Log of Occupational Injuries and Illnesses. For each establishment on
> and off NASA property that performs work on this Contract, the
> Contractor shall deliver to the Government a copy of its annual
> summary of occupational injuries and illnesses (or equivalent) as
> described in Title 29, Code of Federal Regulations, Subpart 1904.5.
> Copy of all summaries as required above under Contractor's cover
> letter. If contractor is exempt by regulation from maintaining and
> publishing such logs, equivalent data in contractor's format is
> acceptable (such as loss runs from insurance carrier) which contains
> the data required by JSC Form 288. Data shall be compiled and reported
> by calendar year and provided to the Government within 45 days after
> the end of the year to be reported (e.g. not later than February 15 of
> the year following.)
>
> [Hazard Prevention and Control.]{.smallcaps} Identified hazards shall
> be eliminated or controlled. In the multiple employer environment of
> the center, it is required that hazards including discrepancies and
> corrective actions be collected in a center wide information system
> (Hazard Abatement Tracking System (HATS) for risk management purposes.
> Describe your approach to implementing this requirement.

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

Hazardous Operations and Processes. Establish methods for notification
of personnel when hazardous operations and processes are to be performed
in their facilities or when hazardous conditions are found to exist
during the course of this contract. JPG 1700.1 shall serve as a guide
for defining, classifying, and prioritizing hazardous operations; 29 CFR
1910.119 shall be the guide for hazardous processes. Develop and
maintain a list of hazardous operations and processes to be performed
during the life of this contract. The list of hazardous operations and
processes shall be provided to JSC as part of the plan for review and
approval. JSC and the Contractor shall decide jointly which operations
and processes are to be considered hazardous, with JSC as the final
authority. Before hazardous operations or processes commence, the
Contractor shall develop a schedule to develop written procedures with
particular emphasis on identifying the job safety steps required. NASA
shall have access on request to any contractor data necessary to verify
implementation. For all identified operations or processes that may have
safety or health implications outside contract operations, the
contractor shall identify such circumstances to the JSC Occupational
Safety Branch and Occupational Health and Test Support Office who shall
provide additional instructions for further NASA management review and
approval.

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

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

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

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

Environmental Operations & Activities

Operations Involving Hazardous Waste. Identify procedures used to manage
hazardous waste from point of generation through disposal. Clearly
identify divisions of responsibility between contractor and NASA for
hazardous waste generated throughout the life of the contract.
Operations that occur on site at JSC, SCTF, or Ellington Field shall be
evaluated by the JSC Environmental Services Office and shall be properly
controlled as advised by same. JSC Environmental Services Office shall
be notified prior to initiation of any new or modified operations,
equipment, systems, or activities generating new hazardous wastes or
where the chemicals change or there are volume increases of 25% or more
on site at JSC, SCTF, or Ellington Field.

Operations Involving New or Modified Emissions/Discharges to the
Environment. Set forth methods for identifying new or modified
emissions/discharges and coordinating results with the Environmental
Services Office, mail code JA131. Set forth a plan of procedures to
conduct pollution prevention, waste minimization or source
reduction/elimination of environmental pollution. Address management and
continuous improvement for the reduction of hazardous materials;
substitution of non-hazardous or less hazardous materials for hazardous
materials; proper segregation of hazardous wastes from non-hazardous
wastes; and other methods described by NASA, EPA, GSA, and Executive
Order recycled content / affirmative procurement purchases. The
JA131/Environmental Office is the single point of contact for
coordinating all JSC environmental permits Emphasis shall be placed on
providing for sufficient lead-time for processing permits through the
appropriate state agency and/or the Environmental Protection Agency.

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

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

Medical (Occupational Healthcare) Program. Discuss your medical
surveillance program and injury /illness case management to evaluate
personnel and workplace conditions to identify specific health issues
and prevent degradation of personnel health as a result of occupational
exposures. Discuss approach to Cardiopulmonary Resuscitation (CPR),
first aid, and, return to work policies and the use of government
provided medical and emergency facilities for the initial treatment of
occupational injuries/illnesses.

Hazard Correction and Tracking. Discuss your system for correcting and
tracking safety, health, and environmental hazards with particular
emphasis on integration with JSC\'s Hazard Abatement Process (found
online at [http://wwwsrqa.jsc.nasa.gov/HATS]{.underline}/). (The scope
is restricted to establishments at JSC, Sonny Carter Training Facility,
and Ellington Field.) This includes the following:

Personnel awareness of hazards. Discuss your approach to communicate
unsafe conditions and approved countermeasures to your employees.
Discuss your approach to communicating such conditions to the Government
and other contractors whose personnel may be exposed to such unsafe
conditions. Discuss communications with facility managers. Discuss use
of the NASA Lessons Learned Information System for both obtaining
lessons from other sources and as a repository for lessons learned
during performance of the contract.

Interim and Final Abatement Plans. Describe how you shall approach
interim and final abatement of hazards. Describe how you shall provide
data to the JSC Hazard Abatement Tracking System for all hazards that
are not finally abated (all interim and final abatement actions
completed) within 30 days of discovery. Discuss your approach to posting
such plans using JSC Form 1240, \"JSC Notice of Safety or Health Hazard
and Action Plan\", or equivalent. Discuss compatibility of your system
with JSC\'s the role of facility managers in abatement planning,
implementation, and verification.

Disciplinary System. Describe your system for ensuring safety and health
discipline in your personnel (including subcontractors). Describe your
approach to modifying personnel behaviors when personnel are exhibiting
discrepant safety and health performance.

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

> [Safety and Health Training.]{.smallcaps} Describe the contractor\'s
> training program including identification of responsibility for
> training employees to assure understanding of safe work practices,
> hazard recognition, and appropriate responses for protective and/or
> emergency countermeasures, including training to meet federal, state,
> and local regulatory requirements. In doing so, the contractor shall
> factor parallel requirements found in other mandates such as
> environmental protection \[example: 29 CFR 1910.38 for emergency
> action plans and fire prevention plans versus EPA Resource
> Conservation & Recovery Act (RCRA) for Emergency Planning and
> Community Right-to-know (EPCRA).\] Describe approach to identifying
> training needs including trace ability to exercises such as job safety
> analyses, performance evaluation profiles, hazard analyses, mishap
> investigations, trend analyses, etc. Describe approach to training
> personnel in the proper use and care of protective equipment (PPE).
> Discuss tailoring of training towards specific audiences (management,
> supervisors, and employees) and topics (safety orientation for new
> hires, specific training for certain tasks or operations). Discuss
> approach to ensure that training is retained and practiced. Discuss
> personnel certification programs. Certifications shall include
> documentation that training requirements and physical conditions have
> been satisfied (examples include physical examination, testing, and
> on-the-job performance). Address utilization of JSC safety and health
> training resources (such as asbestos worker training/certification,
> hazard communication, confined space entry, lockout/tag out, etc.) as
> appropriate with particular emphasis on programs designed for the
> multiple employer work environment on NASA property. All training
> materials and training records shall be provided to NASA, and other
> federal, State, and local agencies for their review upon request. If
> the contractor wishes to train their personnel in any regulatory
> mandated training, an agreement shall be secured with JSC Occupational
> Safety Branch and Occupational Health and Test Support office prior to
> beginning training. The agreement shall ensure that safety and health
> training resources available from NASA are utilized where appropriate
> and to ensure that contractor-supplied training is in agreement with
> JSC safety and health processes.

Format:

> Cover page - to include as a minimum the signatures of Contractor\'s
> project manager and designated safety official (if different); NASA
> COTR; JSC Occupational Safety Branch; and the NASA Contracting
> Officer. Other signatures may be required at the discretion of the
> Government.

Table of Contents. See content above

> Body of plan - as required. Contractor's format is acceptable but
> shall be traceable to the elements of the content below.
>
> When preparing its plan, the offeror/contractor is expected to review
> all the items above and tailor its plan accordingly. Certain
> requirements set forth in this DR may be specific for contractor
> operations performed at JSC, Ellington Field, or Sonny Carter Training
> Facility in the Clear Lake, Texas, area; tailoring of the plan to the
> requirements of specific establishments is acceptable**.** The plan
> shall clearly identify those resources to be provided by the
> contractor and provided by the Government. This review and supporting
> rationale is to be made available to the Government as part of this
> plan. It can be documented as a checklist or outline, inserted
> directly in the body of the plan, or in any format developed by the
> contractor that clearly conveys the results of this review including
> the basis for any underlying assumptions.
>
> Authority: FAR 52.223-1 through -5, -10; NFS 18-23.70, 18-52.223-70,
> 18-52.223-73.

Distribution: After NASA approves the plan, the Contracting Officer
shall retain the plan in the contract file. The contractor shall send
additional copies to each of the following: NS/Safety and Test
Operations Division (2 copies); SD13/Occupational Health Officer (1
copy); JA131 / Environmental Services (1 copy); COTR (1 copy)

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

DATA REQUIREMENTS DESCRIPTION (DRD)

DRD No.: MSOC-JSC-0031

DRD Title: Safety and Health Program Self Evaluation

Data Type: 2

Page: 1 / 2

Description/Use - Self evaluation of Contractor\'s safety and health
program performance

SOW Ref.: 1.3.2.2

Submission:

Initial -- NA

Final -- Sept 30 of each year

Approval -- NA

Submission Frequency - annual

Applicable Documents: JPG 1700.1 (as revised)

Data Preparation Information:

Scope -- The Contractor shall conduct an annual self-evaluation of its
safety and health program as required by its safety and health plan.

Content --

The internal assessment of safety and health program effectiveness
during the report period (i.e., the previous year) indicating the status
of goals or objectives previously established and areas of strength and
weakness in Contractor safety program performance.

Safety and health concerns and resolutions relating to JSC operations,
which may have been identified during the report period.

Unresolved safety and health concerns relating to JSC operations which
the Contractor feels merit attention of JSC safety and health
management.

The goals and objectives of the Contractor safety and health program for
the next report period.

An analysis of the contractor\'s performance, at JSC-administered
establishments, in each of the 32 Voluntary Protection Program
sub-elements as found in the Federal Register of July 24, 2000
(available at the following link):
<http://www.osha-slc.gov/FedReg_osha_data/FED20000724A.html>

Action plans shall be attached for identified problem areas. Action
plans shall include schedule for periodic progress reports to the
Government. Frequency of status reports shall to be agreed to by the
Government and the Contractor for each problem area.

Format: as specified in OSHA TED 8.1, \"Revised Voluntary Protection
Programs (VPP) Policies and Procedures Manual\", Appendix H (Program
Evaluation Report), Attachment 2 (VPP Onsite Evaluation Format for
Safety and Health Programs) for a STAR work site which is found at the
following link:
<http://www.osha-slc.gov/OshDoc/Directive_data/TED_8_1A.html>. Also, as
mandated by the cognizant OSHA regional office. Contractors who have
submitted a written self-evaluation as a VPP site may submit their
original report to OSHA in lieu of writing a new self -evaluation
provided that all action plans and status are updated.

Distribution: per Contracting Officer's letter

Maintenance - NA

DATA REQUIREMENTS DESCRIPTION (DRD)

DRD No.: MSOC-JSC-0032

DRD Title: Monthly Safety and Health Metrics

Data Type: 2

Page: 1 / 2

Description/Use - Establishes selected Safety and Health Program
metrics. The Office of Primary Responsibility for this DRD is the JSC
Safety, Reliability, and Quality Assurance Office

SOW Ref.: 1.3.2.2

Submission:

Initial -- a month after contract start

Final -- at contract end

Approval -- N/A

Submission Frequency - Monthly by 10^th^ of month following month being
reported.

Applicable Documents:

DRD MSOC-JSC-0030

Refer to JPG 1700.1 and OSHA requirements for definitions of terms
below.

Data Preparation Information:

Scope -- The scope of the information required is limited to the
JSC-administered establishments of Houston Texas at NASA Road One; Sonny
Carter Training Facility; and Ellington Field.

Content --

I. Management Commitment and Employee Involvement.

<table style="width:100%;">
<colgroup>
<col style="width: 9%" />
<col style="width: 9%" />
<col style="width: 9%" />
<col style="width: 9%" />
<col style="width: 9%" />
<col style="width: 0%" />
<col style="width: 9%" />
<col style="width: 9%" />
<col style="width: 0%" />
<col style="width: 9%" />
<col style="width: 9%" />
<col style="width: 10%" />
</colgroup>
<tbody>
<tr class="odd">
<td colspan="2"><p>Date of Management</p>
<p>Safety Committee Meeting</p></td>
<td colspan="2">Type/Title of Meeting</td>
<td colspan="3">No. of Managers attending</td>
<td colspan="3">No. of supervisors attending</td>
<td colspan="2">No. of non-supervisory attending</td>
</tr>
<tr class="even">
<td>This month</td>
<td>Year to date</td>
<td></td>
<td></td>
<td colspan="2">This month</td>
<td>Year to date</td>
<td colspan="2">This month</td>
<td>Year to date</td>
<td>This month</td>
<td>Year to date</td>
</tr>
<tr class="odd">
<td></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td colspan="2"></td>
<td></td>
<td></td>
</tr>
</tbody>
</table>

Include electronic copies of minutes or representative information

  ---------- -------- ------------ -------- ----------- -------- ---------------------- --------
  No. of              Type/Title            No. of               No. of                 
  Employee            of Meeting            Employees            managers/supervisors   
  Safety                                    attending            attending              
  Meeting                                                                               

  This month Year to                        This month  Year to  This month             Year to
             date                                       date                            date

                                                                                        

                                                                                        

                                                                                        

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

Include electronic copies of minutes or representative information

II\. Worksite Analysis. Refer to JPG 1700.1 for definitions of terms.

  ---------- ---------- ------ ----------- ------ ---------- ------ ----------- ------ ------------- ------ ----------- ------
  Division   No. of                               No. of Job                           No. of                           
             Hazard                               Safety                               Routine                          
             Analyses                             Analyses                             Inspections                      

             Required          Performed          Required          Performed          Required             Performed   

             This month Year   This month  Year   This month Year   This month  Year   This month    Year   This month  Year
                        to                 to                to                 to                   to                 to
                        Date               Date              Date               Date                 Date               Date

                                                                                                                         

                                                                                                                         

   Total                                                                                                                 
  ---------- ---------- ------ ----------- ------ ---------- ------ ----------- ------ ------------- ------ ----------- ------

> III\. Hazard Prevention and Control - hazards below were found during
> routine and special inspections, close calls, mishap investigations,
> etc., and require correction.

  --------- ------- ------ --------- ------- ------ --------- --------- ------- ------ --------- ------- ------ ---------
  No. of                   No. of                   No. of    No. of                   No. of                   No. of
  Hazards                  Hazards                  Hazards   Hazards                  Hazards                  JF1240s
  found                    closed                   open \<30 open \>30                closed                   in place
                           \<30 days                days      days                     \>30 days                

  Prior to  This    Year   Prior to  This    Year             Prior to  This    Year   Prior to  This    Year    
  month     month   to     month     month   to               month     month   to     month     month   to     
                    date                     date                               date                     date   

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

> Attach copies (electronic ok if sent by e-mail) of JF 1240\'s (or
> equivalent) including monthly updates. Mark JF 1240\'s where abatement
> has been completed as closed.
>
> IV\. Safety and Health Training - List courses specific to loss
> control initiatives (such as slips/trips falls, material handling;
> etc.) Report other training as \"Generic safety training not otherwise
> specified\" (examples include Hazard Communication, Confined Space
> entry, HAZWOPER, system safety, job safety analysis, etc.) Do not
> include job proficiency course work where safety is an issue (such as
> radiography, welding, painting, etc.)

  ---------------------------------------- ----------- --------- ----------
  Course Title                             No. to be   No.       On
                                           Trained     Trained   Schedule

                                                                 

                                                                 

                                                                 

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

Format: Electronic to NT2, SD26; hard copy to COTR. Send as Excel
spreadsheet or in tables compatible with MS Word.

Distribution: NT2/Occupational Safety Branch (2 copies).
SD26/Occupational Health Officer (1 copy). COTR (1 copy) plus additional
specified in CO letter

Maintenance - NA

> DATA REQUIREMENTS DESCRIPTION (DRD)

DRD No.: MSOC-JSC-0033

DRD Title: System Safety Program Plan

Data Type: 1

Page: 1 / 4

Description/Use - Establishes system safety tasks and activities to
identify, evaluate, and eliminate or control hazards associated with
space flight hardware and related operations.

> SOW Ref.: 1.3.2.2

Submission:

Initial -Due with proposal

Final -- Due 60 days after contract award

Approval -- Start of contract

Submission Frequency -- as required

Applicable Documents:

NPG 8715.3 \"Safety Manual\"

JPG 1700.1, as revised, "JSC Safety and Health Handbook."

MIL-STD-882, as revised, \"System Safety Program for Systems and
Associated Subsystems and Equipment, General Requirements for\"

NSTS 5300.4, 1D-2, as revised, \"Safety, Reliability, Maintainability,
and Quality Provisions for the Space Shuttle Program.\" (Note: also used
by the Space Station program.)

JSC 17773, as revised, \"Instruction for Preparation of Hazard Analyses
for JSC Ground Operations.\"

NSTS 1700.7, as revised, \"Safety Policy and Requirements for Payloads
Using the Space Transportation System.\"

45 SPW HB S-100/KHB 1700.7, "Space Transportation System Payload Ground
Safety Handbook."

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

JESA 30000, Section 9, as revised, \"Product Assurance Requirements.\"

SSP 30309, as revised, \"Safety Analysis and Risk Assessment
Requirements Document.\"

Data Preparation Information:

Scope -- Detailed System Safety requirements differ according to
different flight programs. The elements of a System Safety Program Plan
as outlined below are generic; refer to the appropriate applicable
references listed above for specific program requirements. System Safety
Program Plans are to be tailored for individual safety engineering
projects as integral parts of a formal, disciplined system safety
program plan implemented by the contractor.

Content -- System Safety Program Plan Requirements:

> 1\. Source Documents. The initial issue of the documents cited herein
> (including those of any applicable amendments and revisions) shall be
> as reflected in the contract schedule.
>
> 2\. General. The System Safety Program Plan shall be documented in
> narrative format and shall:
>
> 2.a Describe the scope of the project for which the safety engineering
> activity is to be tailored.
>
> 2.b Describe any interrelationships to other contract requirements,
> tasks and functional elements including appropriate cross references
> to minimize duplication.
>
> 2.c List the contractor and NASA documents, which shall be applied
> either as directives or as guidance in the conduct of the SSPP and
> related system safety tasks.
>
> 2.d Identify the system safety engineering requirements, tasks, and
> responsibilities on an item-by-item basis in accordance with the
> schedule.
>
> 3\. Content.
>
> 3.1 System Safety Engineering Organization. The SSPP shall describe:
>
> 3.1.a The system safety organization or function within the
> organization of the contract including charts to show the
> organizational and functional relationships and lines of
> communication.
>
> 3.1.b The responsibility, authority, and accountability of system
> safety personnel and other contractor organizational elements
> (including subcontractors) involved in the system safety effort.
> Identify each organizational unit responsible for executing each task.
> Identify the authority in regard to resolution of all identified
> hazards. Include the title, address, and telephone number of the
> System Safety Program Manager.
>
> 3.1.c The staffing of the system safety organization for the duration
> of the project including manpower loading and qualifications of
> assigned key personnel.
>
> 3.1.d The procedures by which the contractor shall integrate and
> coordinate the system safety efforts. Include methods of dissemination
> of system safety requirements to action organizations and
> subcontractors; coordination of subcontractors\' system safety
> programs; integration of hazard analyses; management and engineering
> reviews; program status reporting; and the identities and charters of
> any system safety groups.
>
> 3.1.e. The process through which contractor management decisions shall
> be made to include notification and subsequent actions for the
> following: critical and catastrophic hazards; corrective actions
> taken; mishaps or malfunctions; waivers to safety requirements; and
> program deviations.
>
> 3.1.f. The interfaces between the system safety organization and all
> other applicable disciplines such as Engineering, Occupational Safety
> and Health, Reliability, Quality Assurance, Medical Support, etc., at
> all levels of the project (NASA, contractor, and subcontractor.)
>
> 3.2 System Safety Project Milestones. The SSPP shall:
>
> 3.2.a Identify safety milestones required accomplishing evaluations of
> the effectiveness of the system safety effort at critical safety
> checkpoints (such as design reviews, self-evaluations, operational
> readiness reviews, audits, etc.)
>
> 3.2.b Provide a contract schedule of safety tasks showing start and
> completion dates, reports, review, and man loading, in relationship to
> other contract milestones.
>
> 3.2.c To preclude duplication identify integrated system activities
> (i.e., design analyses, test, demonstrations, etc.) applicable to the
> system safety program but specified within other engineering tasks.
> Include as part of this section the estimated system safety manpower
> loading required to accomplish these integrated tasks.
>
> 3.3 System Safety Requirements. The SSPP shall:
>
> 3.3.a Describe or reference the methods that shall be used to identify
> and apply hazard control requirements and criteria for the design and
> operation of equipment, software, and facilities, and for procedures
> covering all phases of acquisition specified in the schedule. List the
> safety standards and system specifications, which are the sources of
> safety requirements with which the contractor either is required to
> comply or intends to adopt as a requirement.
>
> 3.3.b Describe the risk assessment procedures including the hazard
> severity categories, hazard probability (or frequency) levels, and the
> precedence to be followed in satisfying safety requirements. State any
> qualitative or quantitative measures of system safety, which the
> contractor is required to meet, including a description of the
> acceptable risk levels. Include system safety definitions, which are
> in addition to those in JSC documents or are unique to the project
> covered by the SSPP.
>
> 3.3.c Describe the management controls that shall be used to ensure
> compliance or justify waivers and deviations with general design and
> operational safety criteria and the closed loop procedures to ensure
> hazard resolution and control.
>
> 3.4 Hazard Analyses. The SSPP shall describe:
>
> 3.4.a The analysis techniques and format that shall be used in
> qualitative and quantitative analysis to identify hazards, their
> causes and effects, and recommended corrective actions.
>
> 3.4.b The depth to which each analysis technique shall be used within
> the system, operation, or scenario being analyzed. This description
> shall include identification of hazards associated with the system,
> subsystem, components, personnel, support equipment, government
> furnished equipment, facilities, and their interrelationships in the
> logistics support, training, maintenance, transportability,
> operational environments, and phase out or disposal.
>
> 3.4.c The integration of subcontractor hazard analyses and techniques
> within the overall project including contractor hazard analyses.
>
> 3.4.d The techniques to be used to establish a single closed loop
> tracking system.
>
> 3.5 System Safety Data. The SSPP shall:
>
> 3.5.a Describe the approach for researching, disseminating, and
> analyzing pertinent historical hazard or mishap data.
>
> 3.5.b Identify deliverable data and the level of approval required for
> customer acceptance. Attach a copy of the appropriate sheets from the
> data requirements list (DRL) of the schedule.
>
> 3.5.c Identify safety related non-deliverable data and describe the
> procedures for accessibility by NASA and the retention of data.
>
> 3.6 Safety Verification and Audits. The plan shall describe:
>
> 3.6.a The verification and audit requirements and procedures for
> ensuring that the objectives and requirements of the system safety
> program have been adequately demonstrated and implemented.
>
> 3.6.b The procedures for ensuring feedback of safety-pertinent
> information for management and engineering review and analysis.
>
> 3.6.c The review procedures established by the contractor\'s system
> safety organization to ensure safe conduct of hazardous tests with
> particular emphasis on those involving human test subjects.
>
> 3.7 Training. Describe techniques and procedures to be used by the
> contractor to ensure that the objectives and requirements of the
> system safety program are implemented in training for engineers, test
> subjects, technicians, operators, and support (including maintenance)
> personnel.
>
> Authority. NFS 18-52.223-70, 18-52.223-73, 18-52.223-73 (Alt 1); JPI
> 52.223-92

Format: Contractor's electronic format is acceptable.

Distribution: per Contracting Officer's letter

Maintenance - Revisions shall be incorporated by change page or complete
reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0041
>
> DRD Title: Quality Plan
>
> Data Type: 1
>
> Page: 1 / 2
>
> Description/Use - The Quality Plan is used to document the specific
> details of the contractor's Quality Management System (QMS) related to
> a specific product or process

SOW Ref.: 1.3.2.4

> Submission:

Initial -- Due with Proposal

Final -- Start of contract + 30 days

Approval -- Start of contract + 90 days

Submission Frequency -- As required

> Applicable Documents: ANSI/ISO/ASQ Q 9001-2000
>
> Data Preparation Information:

Scope -- A contract specific Quality Plan shall be prepared which
identifies activities performed both on-site and off-site of JSC to
ensure the quality products and services. The Quality Plan is to be
submitted with the Contractor's proposal. The plan shall be approved by
the Contracting Officer concurrent with Contract award

Content -- The quality plan shall address each element of ANSI/ISO/ASQ Q
9001-2000 and the additional requirements identified below:

Identify the methods, procedures, and controls that shall be used to
ensure the quality, quantity, and timeliness of the required contract
requirements.

Explain how training shall be provided to personnel responsible for
quality assurance, quality engineering and software quality assurance
on-site at JSC, including JSC processes for Discrepancy Reporting and
Tracking, Work Authorization Documents (Task Performance Sheets) and
Flight Equipment Pre-Shipment Readiness Review.

Explain in detail how in-line quality assurance (Quality Assurance,
Quality Engineering, and Software Quality Assurance) shall be performed
on-site at JSC. Include discussion of specific allocation of
responsibilities, authority and resources.

Describe how controlled work instructions shall be provided to all
applicable employees, on and off-site JSC.

Explain how timely review of technical documents that affect quality and
changes thereto shall be performed.

Describe participation including responsibilities/activities in design
reviews.

Explain how quality aspects are ensured, and fully included in all
designs and are continuously maintained in the fabricated articles and
during operations.

Explain and ensure how quality requirements are implemented and
satisfied throughout all phases of contract performance, including
preliminary and engineering design, development, subcontracting,
fabrication, processing, assembly, inspection, test, checkout,
packaging, shipping, storage, maintenance, field use, flight
preparations, flight operations, and post-flight analysis, as
applicable, on and off-site JSC.

Explain how to ensure, monitor, measure, and control the quality of
products produced by the contractor and subcontractors. Explain how you
shall ensure that products, which do not conform to product
requirements, are identified and controlled to prevent their unintended
use or delivery.

Describe the methodology for inspection and test planning (economical
and effective use of personnel, facilities and equipment) for both off
and on-site.

Describe the methodology/criteria for assigning itinerate or resident
quality assurance personnel at subcontractor or supplier facilities.

Explain how the monitoring and measuring, and cross-utilization of
personnel will be performed to assure that contract products and
services shall not be negatively affected.

Describe your techniques, procedures, and mechanisms to ensure quality
output despite schedule and/or priority pressures.

Provide and explain the schedule, including milestones, outlining your
plan on accomplishing ANSI/ISO/ASQ Q 9001-2000 compliance within one
year of the contract award date.

Explain how inspection or other activities necessary for ensuring that
purchased product meets specified purchase requirements shall be
established.

Explain how to verify that all personnel performing work affecting
product quality are competent as a result of appropriate education,
training, skills, and experience. In addition explain the system that
shall be used to monitor and maintain this level of personnel competency
required during the duration of the contract.

Describe the responsibilities and requirements for planning and
conducting audits (internal and external), and for reporting results and
maintaining records.

Explain the process of involvement in waivers and deviations when
quality assurance is affected.

Explain the methods for measuring the achievement of your quality
objectives.

Format: - The Quality Plan format shall match the elements of the
ANSI/ISO/ASQ Q 9001-2000.

Distribution: distribution as specified below plus additions per
Contracting Officer's letter

Initial -- As specified in Proposal Instructions

Final -- Contracting Officer, COTR, Task Manager, NASA Quality Assurance

Update -- Contracting Officer, COTR, Task Manager, NASA Quality
Assurance

> Maintenance - Revisions shall be incorporated by change page or
> complete reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0042
>
> DRD Title: Software Quality Assurance Plan & Reports
>
> Data Type: Plan =1 Reports = 2
>
> Page: 1 / 2
>
> Description/Use - Software assurance planning is used to document the
> software assurance activities to be performed during the life cycle
> phases. Reports document the status of the activities.

SOW Ref.: 1.3.2.4

> Submission:

Initial -- Start of contract + 15 days

Final -- Start of contract + 45 days

Approval -- Start of contract + 90 days

Submission Frequency - Review as required, annually at a minimum.
Reports due Monthly.

> Applicable Documents:

Certification Data Package (CDP);

Problem Reporting and Corrective Action (PRACA)

NASA-STD-2201-93, Software Assurance Standard

NPD 2820.1, NASA Software Policies

NASA-STD-2100-91, NASA Software Document Standard

ANSI/ISO/ASQ Q9001-2000 - Quality Systems --Aerospace- Model for Quality
Assurance in Design, Development, Production, Installation, and Serving.

Other approved vendor/contractor, international, U.S., or Military
Standards

Project planning documents per the SOW (Statement of Work)

JSC 27291, GFE Software Design, Development, Test and Evaluation Work
Instruction

> Data Preparation Information:

Scope -- Software Assurance includes Quality Assurance, Quality
Engineering, Verification and Validation, Nonconformance Reporting and
Corrective Action, Safety Assurance, Software Reliability and Security
Assurance. Software Assurance activities are conducted during the
software development life cycle. The phases of the software development
life cycle are:

Concept and Initiation Phase

Requirements Phase

Design Phase

Implementation Phase

Integration and Test Phase

Acceptance and Delivery Phase

Operations/Maintenance Phase

> Software Quality Assurance applies to all software developed for NASA,
> including:

deliverable software,

software included as part of deliverable hardware (including firmware),

non-deliverable software (Commercially available or user-developed) used
for development, fabrication, manufacturing process control, testing, or
acceptance of deliverable software or hardware (test and acceptance
software; software design, test, and analysis tools; compilers, etc.)

Commercially available (COTS), reused, or government-furnished software
(GFS)

Content -- Contractor shall provide a Software Assurance Plan in
accordance with M400 as contained in NASA-STD-2100-91. The Software
Assurance Plan shall identify the software assurance approval authority
responsible for the establishment and composition of all software
baselines and any changes to the baseline. (Per NASA-STD-2201-93 section
3.2.6.). Contractor shall provide software assurance activity reports in
accordance with R008 as contained in NASA-STD-2100-91.

Format: - Contractor's format.

Distribution: distribution as specified below plus additions per
Contracting Officer's letter

Initial -- As specified in proposal instructions

Final -- Contracting Officer, COTR, Task Manager, NASA Quality Assurance

Update -- Contracting Officer, COTR, Task Manager, NASA Quality
Assurance

> Maintenance - Revisions shall be incorporated by change page or
> complete reissue.

DATA REQUIREMENT DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0044
>
> DRD Title: Government Industry Database for Electronic Parts (GIDEP)
> and NASA Advisory Problem Data Sharing and Utilization Program
> Documentation and Reporting
>
> Data Type: 2
>
> Page: 1 / 3
>
> Description/Use - This DRD provides the minimum information to be
> incorporated into the contractor\'s and sub tier contractor
> implementation procedures and contractual data reporting requirements
> to comply with the requirement to participate in GIDEP and NASA
> Advisory Problem Data Sharing and Utilization Program. Data types
> include:

Contractor and sub tier implementation procedures.

Preparation and submittal of GIDEP documents.

Preparation and submittal of NASA Advisories.

Task management, control, and tracking status.

Milestone/mission support (assessment/impact status reports).

Cost data on special problems (involving criminal investigations).

SOW Ref.: 1.3.2.4

> Submission:

Initial --

Contractor and sub tier implementation procedures (60 days after
contract award).

Release of GIDEP documents (in compliance with GIDEP Operations Manual
and Policy).

Release of NASA Advisories (in accordance with NASA policy).

Problem data assessments (30 days after receipt of the problem data).

Milestone/mission support (as required to support the milestone or
mission events).

Cost data (as required for special problems involving criminal
investigations).

Final -- NA

Approval -- NA

Submission Frequency - As required

> Applicable Documents:

SO300-BT-PRO-010 GIDEP Operations Manual and Policy.

SO300-BU-GYD-010 GIDEP Requirements Guide

NPG 8735.1 NASA Procedure and Guidelines, \"Procedure for Exchanging
Parts, Materials, and Safety Problem Data Utilizing the
Government-Industry Data Exchange Program and NASA Advisories.\"

Non-Conforming Parts and Materials Reports

> Data Preparation Information:

Scope -- Incidents involving non-conforming products or materials are to
be reported through the GIDEP Reporting System to comply with Government
Policy as defined by Office of Federal Procurement Policy, Policy Letter
No. 91-3 (Appendix D of GIDEP Operation Manual, SO300-BT-PRO-010).
Generic problems reported by GIDEP or NASA Advisory distribution
networks shall be assessed to determine if there is a real or potential
impact on the program or program assets. Generic problems experienced by
the program or by program assets shall be reported in the GIDEP or NASA
Advisory network, as appropriate. Management documentation shall be
adequate to ensure that (1) the subject problem data are received,
properly distributed, and thoroughly assessed for potential impact; (2)
identified impact issues are resolved or corrected with NASA program
management concurrence; (3) cost data for special problem issues are
accumulated and reported; and (4) all this information is captured and
retained in a database. Special controls shall be implemented to comply
with the confidentiality of the problem reports involving criminal
investigations. The implementation procedures shall address this special
need for the control of information with the restricted distribution as
well as the need to track and report the cost of the problem
investigation and resolution.

Content --

The contractor and sub tier Implementation procedures shall provide
details that shall ensure that the contractor understands and shall
implement these procedures, which cover the scope; task importance;
management responsibilities; technical expertise to identify and resolve
any impacts; \"special problem\" information sensitivity; and
documentation necessary to comply with GIDEP and NASA policies.

GIDEP documents are to comply with the GIDEP Operations Manual and
Policy requirements for the appropriate document being prepared and
released.

NASA Advisories are to comply with contents as required to complete the
JSC NASA Advisory Form, JSC Form 1159 (JF1159), and to accurately report
the problem and conditions.

Implementation documentation shall include an index of problem reports
received and assessed for impact; hardware/systems/subcontractors
subject to the assessments; status of the impact assessments by problem
report by hardware/system/subcontractor; and corrective actions for
problems with identified impacts, including (1) NASA program management
involvement and concurrence, (2) required supporting documentation for
all problems experienced on the program/project that meet the criteria
for release of a GIDEP report or NASA Advisory and the released GIDEP
reports and NASA Advisories, and (3) any other data required to comply
with the applicable GIDEP and NASA documents.

Details of the required milestone/mission support efforts and reports
with the associated roles and responsibilities shall be provided.

Financial data to justify and substantiate any reported \"cost impacts\"
are to be included.

Format: - Electronic submittal is the preferred medium for providing
access to or submittal of information and data under this DRD. Format
guidelines are as follows:

The contractor\'s format is acceptable for their internal implementation
procedures.

GIDEP documents are to be prepared on the appropriate GIDEP form found
in the GIDEP Operations Manual.

NASA Advisories are to be prepared on the JSC NASA Advisory Form,
JF1159.

The contractor\'s format is acceptable for providing the \"Task
Management, Control, and Tracking Status,\" as long as it includes all
the necessary information. An electronic database with access permission
to appropriate NASA personnel is preferred.

Formats for these reports are to comply with the applicable
milestone/mission event.

f\. Cost data are to be provided as required by the financial management
reporting system and as necessary to substantiate the data being
submitted in support of criminal investigations.

Distribution: Distribution per Contracting Officer's letter (must
include the JSC GIDEP/NASA Advisory Coordinator as a minimum).

> Maintenance - Data shall be maintained as required to:

Document the current implementation procedures and GIDEP and NASA
Advisory policies.

Ensure that the released GIDEP information is complete, factual,
accurate, and up to date.

Ensure that the released NASA Advisory information is complete, factual,
accurate, and up to date.

Tracking status provided periodically to demonstrate complete
accomplishment of the task.

Stay current and accurate or as requested to support management
activities.

Substantiate submitted costs or to include additional costs as they are
identified.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0045
>
> DRD Title: Nonconformance Record
>
> Data Type: 1
>
> Page: 1 / 2
>
> Description/Use - To provide that all nonconformance are documented in
> consistent manner and to assure that all the necessary data is
> included and available

SOW Ref.: 1.3.2.4

> Submission:

Initial -- Due with Proposal

Final -- Due 90 days after contract award

Approval -- Due 180 days after contract award

Submission Frequency -- As required

> Applicable Documents: Problem Reporting and Corrective Action (PRACA)
> for Johnson Space Center (JSC) Government Furnished Equipment (GFE),
> ANSI/ISO/ASQ Q 9001-2000
>
> Data Preparation Information:

Scope -- This DRD establishes the minimum data elements necessary to
provide records of the closed loop system for the control of
nonconforming products. Nonconformance shall commence with initial
receipt of materials or articles for the procurement and continue
through all subsequent phases of the program. A nonconformance is
defined as when an item fails to meet a specified requirement.

Content -- The record shall contain the following data elements:

A unique and traceable number

Identification of the nonconforming article or material;

Nomenclature

Part identification number

Serial no./Lot no./Version

Manufacturer\'s name or the Manufacturer\'s Contractor and Government
Entity (CAGE) code (preferable)

The date the nonconformance was discovered

The name of the initiator of the nonconformance record

A description of the nonconformance including a description of the
required characteristics or specification

The type of activity being conducted (e.g., fabrication, assembly,
qualification test, system test, pre-delivery or pre-installation test,
etc.,). Reference shall be made to applicable procedure numbers

When appropriate, identification of the next higher assembly

Nomenclature

Part identification number

Manufacturer\'s name or the Manufacturer\'s CAGE code (preferable)

Disposition of the nonconforming article or material;

The signatures of the personnel authorized to provide disposition;

Verification that the prescribed disposition was acceptably completed;
and

When applicable, a cross-reference to an associated PRACA reports.

Format: - Contractor's format.

Distribution: as specified below with additions per Contracting Officer
letter

Initial -- As specified in Proposal instructions

Final -- Contracting Officer, COTR, Task Manager, NASA Quality Assurance

Update -- Update as required

Maintenance - Revisions shall be incorporated by change page or complete
reissue.

DATA REQUIREMENTS DESCRIPTION (DRD)

DRD No.: MSOC-JSC-0046

DRD Title: Safety Lessons Learned

Data Type: 2

Page: 1 / 1

Description/Use - Obtains Lessons learned from Contractor for possible
publication in NASA Lessons Learned Information System (LLIS)

> SOW Ref.: 1.3.2.2

Submission:

Initial -- N/A

Final -- N/A

Approval -- N/A

Submission Frequency - 30 days after triggering event or 30 days after
mishap investigation or hazard analysis / evaluation is completed.

Applicable Documents:

DRD MSOC-JSC-0030

Data Preparation Information:

Scope -- Criteria for Selecting Lessons Learned. Uncommon insight
arising from any event or observation that shall benefit from sharing
with a larger community of interested parties. Lessons learned are
intended to prevent recurrence of undesirable events and to allow NASA
and its team members to capitalized to the greatest extent practical on
unique successes.

Content --

Subject - one line subject of the lesson.

Lesson Learned - usually one sentence that describes insight gained

Description of Event - narrative of what happened.

Recommendations - may be an action plan, suggestion, etc., that was
adopted at event source.

Supporting documentation - as needed to give clear picture of lesson
(photographs, illustrations, drawings, etc.)

Contact name and e-mail address (for follow up by Government prior to
publication of lesson)

Definitions. Refer to NASA LLIS at http://llis.gsfc.nasa.gov/ for
definitions of terms used.

Format:

Distribution: NT2/Occupational Safety Branch (1 electronic copy
including photographs, drawings, etc., in web-ready format such as HTML
or JPG). COTR (1 copy) plus additional per Contracting Officer's letter.

Maintenance - NA

## DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0050
>
> DRD Title: Certificate of Flight Readiness Endorsement
>
> Data Type: 2
>
> Page: 1 / 1
>
> Description/Use -- To certify the completion of disposition of all
> contractor tasks and planned work required preparing the ground
> systems (i.e., ground hardware and software; support facilities and
> equipment; operational procedures; certified personnel; and service
> operators) to safely support a specific mission in accordance with
> NSTS 08117 and SSP 50108.

SOW Ref.: 1.5.1.1.1 and 1.5.1.2.1

> Submission:

Initial -- First Flight Readiness Review (FRR) after contract award

Final -- N/A

Approval -- NA

Submission Frequency -- Each Flight Readiness Review per MOD schedules

> Applicable Documents:

NSTS 08117 Certification of Flight Readiness Requirements

SSP 50108 Certification of Flight Readiness for Space Station

> Data Preparation Information:

Scope -- The COFR defines the contractor's responsibilities as well as
product and process status for certifying readiness for launch, mission
and landing operations.

Content -- Data shall include integrity metrics for all processes and
products specified in the applicable documents, as well as necessary
supporting data, required to satisfy the contractor's responsibilities
and readiness to support the launch, mission and landing operations as
defined in applicable documents, and other data per direction of the
Flight Director Office.

Format: In accordance with NSTS 08117 (Certificate of Flight Readiness
Requirements) and SSP 50108 (Certification of Flight Readiness for Space
Station).

Distribution: per Contracting Officer's letter.

> Maintenance -- N/A

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. DRD No.: MSOC-JSC-0051

2\. DRD Title: Integrated Planning System (IPS) Facility Operations
Procedures

3\. Data Type: 2

4\. Page: 1/ 2

Description/Use - This document provides the procedures by which the IPS
contractor manages, operates, and maintains the on-site and off-site IPS
platform and its standalone systems and subsystems to support the
development, production, and direction of mission support activities. It
also provides guidelines to the IPS users on IPS usage.

> SOW Ref: 1.5.1.2.4, 1.5.1.2.5, and 1.5.1.2.11

Submission:

Initial -- Start of contract + 60 days

Final -- Start of contract + 90 days

Approval -- NA

Submission Frequency -- Semi-annually

7\. Applicable Documents:

> Integrated Planning System (IPS) Facility Operations Procedures,
> CSOC-JSC-PRO-002237 (latest revision)
>
> Integrated Planning System Future Facility Change Plan,
> CSOC-JSC-PRO-002237 (latest revision)
>
> Disaster Recovery Plan, CSOC-JSC.PO60.000084 (latest revision)
>
> IPS Master External Interface Control Document (ICD), SFOC-FL0493
>
> JSC Hardware Engineering Change Workflow Process, CSOC-JSC-EM11
>
> JSC Sustaining Engineering Procedures -- JSC Reliability Engineering
> and Analysis, CSOC-JSC-LOP-002378
>
> CSOC Standard Operating Procedure for Support Requirement (SR) and SR
> Evaluation Process, CSOC-JSC-SOP-000250
>
> CSOC-JSC-SOP-000252, CSOC Standard Operating Procedure for Software
> Engineering Process
>
> JSC IT Security Handbook, JPG-2810.1
>
> IPS General Purpose External Interface Software User\'s Handbook
> LOR-TR1803
>
> IPS Facility Operations Configuration Management Plan, SOC-PN-001476B
>
> IPS DOL Element MPSR OPS Concept, SOC-PR-002007
>
> USA Houston Operations Disaster Recovery and Continuity of Operations
> Plan (DRCOP), USA000018
>
> MCC and IPS Operational Change Control Procedures, USA001235
>
> Flight Operations Reliability Engineering Operating Procedure Anomaly
> Reporting, Basic USA002304
>
> IPS Multi-Purpose Support Room (MPSR) Configuration Management Plan,
> USA003377

8\. Data Preparation Information:

> Scope:
>
> To identify and document the type and level of operations support
> provided for the IPS platform. This document includes the procedures
> used to manage, operate, and maintain an efficient platform for all
> IPS users and developers.
>
> Content -- This document shall provide the information the IPS
> contractor uses to manage, operate, and maintain the on-site and
> off-site IPS platform and its standalone systems and subsystems to
> support the development, production, and direction of mission support
> activities. It also provides the guidelines for the IPS users on how
> to use the IPS.
>
> Format: - Contractor provided format is acceptable
>
> Distribution: - Shall be via both hardcopy and electronic as directed
> by the IPS Project Manager, or his designee, and shall be made
> available electronically via a web page, or like means, for user
> access.

9\. Maintenance -- The Integrated Planning System (IPS) Facility
Operations Procedures shall be reviewed and updated on a semi-annual
basis, as appropriate, but revised, annually, at a minimum.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0053
>
> DRD Title: Training and Certification Plan
>
> Data Type: 2
>
> Page: 1/1
>
> Description/Use -- To describe the contractor's plans for training and
> certification of operational support personnel for the MCC (including
> BCC/HSR) and IPS facilities.

SOW Ref.: 1.5.1.1.4 and 1.5.1.2.4

> Submission:

Initial -- Start of contract + 15 days

Final -- Start of contract + 45 days

Approval -- N/A

Submission Frequency -- As required

> Applicable Documents: DA-WI-16 (MOD Training and Certification Work
> Instruction)
>
> Data Preparation Information:

Scope -- The certification and training plans shall delineate the
specific training requirements required by personnel to become certified
in operations support.

Content -- The training and certification plan shall generally follow
the guidelines of DA-WI-16.

Format: Contractor's format

Distribution: distribution per the Contracting Officer's letter

> Maintenance -- The training and certification plan shall be updated to
> reflect any contract changes and revisions shall be incorporated by
> change page or complete reissue.

#  **DATA REQUIREMENTS DESCRIPTION (DRD)**

DRD No.: MSOC-JSC-0060

DRD Title: Change Control Process and Plan

Data Type: 1

Page: 1 / 1

Description/Use - This process plan describes the change control process
for modifications and sustaining changes to all the facilities and
systems covered by this contract.

SOW Ref.: 1.5.5.2.1

Submission:

Initial -- with proposal

Final -- Award + 60 days

Approval -- at contract start

Submission Frequency -- as required due to organizational restructures
or process improvement activities.

Applicable Documents:

Data Preparation Information:

Scope -- The Change Control Process plan shall address all of the
facilities, systems and subsystems covered by this contract. It shall
include contractor, NASA, and other organizations roles and
responsibilities. The plan shall address deliverables such as change
control database and metric reports.

Content -- The process shall include submittal, NASA and contractor
screening, impact assessment, NASA and contractor control board review
and approval, authorization, and implementation status. Also included
shall be quality assurance, security engineering and security
assessment. Products of this plan would be the change control database
and metric reports.

Format: hardcopy and electronic format, JSC web domain accessible

Distribution: per Contracting Officer's letter.

Maintenance - as required due to organizational restructures or process
improvement activities.

# **DATA REQUIREMENTS DESCRIPTION (DRD)**

> DRD No.: MSOC-JSC-0061
>
> DRD Title: Configuration Management Plan
>
> Data Type: 1
>
> Page: 1 / 2
>
> Description/Use -- The Configuration Management Plan shall prescribe
> the configuration management processes for hardware, software, and
> documentation to be implemented, methods to be utilized for
> configuration identification, interface control, documentation, and
> accounting.

SOW Ref.: 1.5.5.2

> Submission:

Initial -- due with proposal

Final -- Award + 60 days

Approval -- At contract start

Submission Frequency -- as required

> Applicable Documents: ISO 10007
>
> Data Preparation Information:

Scope -- A program specific Configuration Management Plan shall be
prepared which defines the requirements, and identifies the activities
to be carried out in order to achieve them.

Content -- The Configuration Management Plan shall contain those
subjects listed in the Configuration Management paragraph of this SOW
and the following as a minimum:

The steps in the processes that constitute the operating practice of the
organization (a flowchart or similar diagram can be used to demonstrate
the elements of the process);

The specific allocation of responsibilities, authority, and resources
during the different phases of the project;

The applicable documented procedures and instructions to be applied for
the purpose of coordinating, defining, testing, monitoring, and
controlling such things as floor plans, equipment lists, workstation
configuration configurations, software loads and all technical
interfaces.

Suitable testing, inspection, examination, and audit programs at
appropriate stages (e.g., design and development) for maintaining
integrity of hardware and software throughout their respective life
cycle(s).

A documented procedure for changes and modifications in the
Configuration Management Plan as projects proceed;

Method for measuring the achievement of the objectives;

Other actions necessary to meet the objectives.

Provisions for complying with the Quality Assurance supplements required
in the Statement of Work.

Format: - Contractor format is acceptable

> d\. Distribution: per Contracting Officer's letter
>
> Maintenance - Update as required due to configuration management
> process or procedure changes. Revisions shall be incorporated by
> change page or complete resubmit.

#  **DATA REQUIREMENTS DESCRIPTION (DRD)** {#data-requirements-description-drd-4 .unnumbered}

DRD No.: MSOC-JSC-0062

DRD Title: Level A and B Requirements

Data Type: 1

Page: 1 / 1

Description/Use -- The current Level A and B requirements for IPS, MCC,
BCC and HSR shall be maintained. The requirements establish the
functional and detailed requirements for each system and subsystem.

SOW Ref.: 1.5.1.1.11, 1.5.1.2.11

Submission:

Initial -- August following contract award

Final -- September following contract award

Approval -- October following contract award

Submission Frequency - updated yearly on the above schedule if changes
have occurred during the year.

Applicable Documents:

Data Preparation Information:

Scope -- The requirements packages shall be divided into system (Level
A) and subsystem (Level B) functional requirements. System functional
(Level A) requirements shall be provided separately for MCC, HSR/BCC and
IPS. Subsystem functional (Level B) requirements shall be provided for
each subsystem identified in the Level A requirements.

Content -- System functional (Level A) requirements shall identify the
functions to be performed by major system and shall include a general
description of the functional capabilities required; the relationship
with other functions, the user interface requirements, including input
and output characteristics, and planned functional uses. These
requirements will be traceable to parent requirement. Subsystem
functional (Level B) requirements shall include a complete description
and allocation of the capabilities required of each subsystem. It shall
identify subsystem interface requirements, including input and output
data requirements, and performance. The subsystem Level B requirements
shall describe the test and verification methodology and are traceable
to the Level As. Detailed design specifications should not be included
in the Level A requirements, but in the Design Specification.

Format: Shall include, but not be limited to, the following sections:
Introduction, Related Documentation, Assumptions and Constraints,
Interface Requirements, Functional requirements, Performance, Human
Factors, Security, Testing Methodology, Reliability, Maintainability,
Availability, Trace ability, Acronyms, and a glossary.

Distribution: -- per contracting officer's letter

Maintenance - The requirements are updated once a year, if required
based upon system/subsystem changes.

# **DATA REQUIREMENTS DESCRIPTION (DRD)**

> DRD No.: MSOC-JSC-0063
>
> DRD Title: Interface Control Document
>
> Data Type: internal -- 2, external -- 2 (relative to facility and it's
> systems/subsystems)
>
> Page: 1 / 1
>
> Description/Use -- The ICD is to define the technical and data
> interface between systems and/or subsystems internal or external to
> the IPS, MCC, HSR, BCC, CDE and GSDE systems. All the external and
> internal interfaces as defined in the MCC and IPS Level A and B
> requirements

SOW Ref.: 1.5.1.1.11, 1.5.1.2.11, 1.5.2.2.8, 1.5.1.1.8, and 1.5.2.3.8

> Submission:

Initial -- as required for each interface

Final -- within 60 days of initial submission

Approval -- within 90 days of initial submission

Submission Frequency -- as required due to changes.

> Applicable Documents:
>
> Data Preparation Information:

Scope -- Separate ICDs shall be provided for each system and/or
subsystem interfaces defined in the MCC and IPS Level A and Level B
requirements.

Content -- The ICD shall define the data exchange requirements (input
and output) between the specified systems and/or subsystems. This shall
include data rates, volumes, frequencies, response times, performance
expectations, sizing, and data format.

Format: The ICD shall contain, but not be limited to, the following
sections: Introduction, Applicable documents, Reference documents,
Interface description and requirements, Security, Availability,
Maintainability, and Reliability, Verification, Trace ability, Acronyms,
and Glossary.

Distribution: per Contracting Officer's letter

Maintenance - The ICDs as required, based upon system/subsystem changes.

#   {#section-86}

#  **DATA REQUIREMENTS DESCRIPTION (DRD)**

> DRD No.: MSOC-JSC-0065
>
> DRD Title: Systems Lifecycle Process
>
> Data Type: 2
>
> Page: 1 / 1
>
> Description/Use - This process shall be prepared and approved for each
> of the Mission services functions and shall cover all hardware,
> software, and integration efforts being performed by the contractor.
> The process shall indicate the contractor's planned approach to
> managing the full end-to-end lifecycle of Mission services projects.

SOW Ref.: 1.5.1.1.2, 1.5.1.1.3, 1.5.1.2.2 and 1.5.1.2.3.

> Submission:

Initial -- due with proposal

Final -- Start of contract + 30 days

Approval -- Start of contract + 45 days

Submission Frequency -- as required

> Applicable Documents: NPG 71XX.X NASA System Engineering Guidelines,
> SE JPD 8090 JSC System Engineering Guidelines
>
> Data Preparation Information:

Scope -- The process shall be prepared separately for the MCC (including
BCC/HSR) and IPS mission services. It shall outline the contractor's
methodology for project and system modification and sustaining. It shall
define the full lifecycle of Mission services projects.

Content -- The process shall include, but not be limited to, the
following tasks: requirement generation, design reviews, approval,
decision points, contractor, NASA, and external organization roles and
responsibilities, verification, acceptance, sustaining, operations, and
replacement.

Format: The process shall define the tasks listed above and provide a
flow from generation to operations.

Distribution: per Contracting Officer's letter.

> Maintenance - This document shall be a working document and shall be
> maintained to reflect current management data and policies.

#  **DATA REQUIREMENTS DESCRIPTION (DRD)**

DRD No.: MSOC-JSC-0066

DRD Title: Equipment Replacement Plan

Data Type: 2

Page: 1 / 1

Description/Use - The Equipment Replacement Plan is a two-part document.
This document is required for strategic planning of equipment and system
replacement due to non-maintainability. Part 1 is a 15-year forecast of
equipment support and maintainability. Part II is a replacement proposal
for specific equipment and/or systems identified in Part I. An NME Plan
Part II is provided for each system that is identified in the NME Plan
Part I.

SOW Ref.: 1.5.5.1.4 Equipment Replacement

Submission:

Initial -- Part I is after contract start + 30 days. Part II is 36
months prior to end of life of equipment identified in Part I.

Final -- Part I is after contract start + 60 days.

Approval -- NA

Submission Frequency -- Part I is submitted yearly, by August first.
Part II is submitted as required.

Applicable Documents:

Data Preparation Information:

Scope -- The Equipment Replacement Plan Part I includes all the
equipment in all the facilities under this contract. Equipment
Replacement Plan Part II addresses only the specific equipment or system
that is within 36 months of non-maintainability. Equipment or systems
that total replacement costs (not per unit cost) is under \$100,000 per
government fiscal year is excluded from the Equipment Replacement Plan
Part II requirement, with NASA Project Management approval.

Content --Equipment Replacement Plan Part I is a list of all equipment
maintained under this contract that is non maintainable in the next 15
years. It is based upon failure trend analysis, performance analysis,
spares availability, required vendor support, availability of COTS
software and/or licensing agreements. It contains a projection of
equipment end of life and an estimate per government fiscal year as to
the replacement cost. Equipment Replacement Plan Part II is a detailed
system engineering study and replacement proposal to NASA. . It
addresses current requirements, performance enhancements, and the
strategic architecture team vision/tactical plan. It shall provide
analysis and comparison of current technology availability and trends.
The Part II plan would also address security, RMA, integration, and
provide schedule. It also contains an estimate per government fiscal
year of the lifecycle costs of the proposed replacement system.

Format: deliverable document for both Part I and II. A summary of Part
II will be provided as a presentation to NASA upon delivery of Part II
documented study.

Distribution: per Contracting Officer's letter

Maintenance - updates as required.

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. DRD No.: MSOC-JSC-0067

2\. DRD Title: Integrated Planning System (IPS) Future Facility Change
Plan

3\. Data Type: 2

4\. Page: 1/ 2

Description/Use -- Defines and documents the Integrated Planning System
(IPS) platform contents. This document provides the planned system
upgrades and deletions for a five-year period. The document contains
appendices identifying the hardware, current and projected; current
version COTS software and where it is used; network equipment with port
assignments; and external interface connectivity indicating approved
sessions.

> SOW Ref: 1.5.1.2.3 and 1.5.1.2.11

Submission:

Initial From start of contract + 60 days

Final -- From start of contract + 90 days

Approval -- N/A

Submission Frequency -- Semi-annually

7\. Applicable Documents:

> Integrated Planning System Future Facility Change Plan,
> CSOC-JSC-PRO-002237 (latest revision)
>
> Integrated Planning System (IPS) Facility Operations Procedures,
> CSOC-JSC-PRO-002237 (latest revision)
>
> Disaster Recovery Plan, CSOC-JSC.PO60.000084
>
> IPS Master External Interface Control Document (ICD), SFOC-FL0493

8\. Data Preparation Information:

> Scope -- This document identifies and separates the major elements of
> the IPS platform into the following appendices:
>
> Appendix A -- Future Facility Change Plan (identifies platform changes
> by projects)
>
> Appendix B - Hardware Elements
>
> Appendix C - Software Elements
>
> Appendix D - Router (and router connectivity) Definitions
>
> Appendix E - IPS General Purpose External Interface/JIN
> Connectivity's.
>
> Appendix F - Equipment Replacement Phase
>
> Each of these Appendices provides information regarding the current
> platform elements and the planned changes to these elements, both on a
> short term and long-term basis. While this document does not serve as
> the official configuration of the platform, it will provide
> configuration information, which can be used for planning purposes.
>
> This document also identifies the policies for setting priority,
> captures the generic work plan priority assignments and discusses how
> conflicts are resolved.
>
> Content -- This document defines and documents the Integrated Planning
> System (IPS) platform contents. This document provides the planned
> system upgrades and deletions for a five-year period. The document
> contains appendices identifying the hardware, current and projected;
> current version COTS software and where it is used; network equipment
> with port assignments; and external interface connectivity indicating
> approved sessions.
>
> Format: Contractor defined format is acceptable
>
> Distribution: -

Initial -- Shall be via both hardcopy and electronic as directed by the
IPS Project Manager, or his designee, and shall be made available
electronically via a web page, or like means.

> Final -- Shall be via both hardcopy and electronic as directed by the
> IPS Project Manager, or his designee, and shall be made available
> electronically via a web page, or like means
>
> Update -- Shall be via both hardcopy and electronic as directed by the
> IPS Project Manager, or his designee, and shall be made available
> electronically via a web page, or like means

9\. Maintenance -- The Integrated Planning System (IPS) Future Facility
Plan shall be reviewed and updated quarterly.

#  **DATA REQUIREMENTS DESCRIPTION (DRD)**

> DRD No.: MSOC-JSC-0068
>
> DRD Title: Test and Verification Plan
>
> Data Type: 1
>
> Page: 1/ 1
>
> Description/Use -- Separate Test and Verification Plans shall be
> prepared and submitted for approval for the following mission
> services: 1) IPS, 2) MCC (including BCC/ HSR). The plans shall supply
> a level of detail, which shall support test management, tool
> development, dependency identification, and resource planning. The
> plans shall indicate the overall test methodology for modification and
> sustaining releases/deliveries and independent releases/deliveries.

SOW Ref.: 1.5.1.1.7 and 1.5.1.2.7

> Submission:

Initial -- with contract proposal

Final -- Start of contract + 30 days

Approval -- Start of contract + 60 days

Submission Frequency -- review yearly for updates due to organizational
or process changes.

> Applicable Documents:
>
> Data Preparation Information:

Scope -- The contractor shall describe the overall test philosophy for
all releases/deliveries. It shall contain a high level description of
the test types and objectives.

Content -- The plan shall contain the following, but not limited to:
Identification of systems covered, organizational responsibilities, test
descriptions, success criteria, test tools required, documentation
requirements, test milestones, objectives, test support requirements,
test environment, anomaly tracking, and test reporting.

Format: hardcopy and electronic document, JSC web assessable.

Distribution: per Contracting Officer's letter

> Maintenance - reviewed yearly for updates due to organizational or
> process changes

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0069
>
> DRD Title: Test and Verification Procedures
>
> Data Type: System Level: 2/ Subsystem level: 3
>
> Page: 1 / 1
>
> Description/Use -- Test procedures are to specify formal testing of
> hardware and software systems for the following mission services: 1)
> IPS, 2) MCC and BCC/HSR 3) GSDE 4) CDE. The test procedures shall be
> developed prior to test execution. The test procedures shall include
> requirement verification matrices for all changes. Test procedures
> shall be created for subsystem and system level testing. Subsystem
> test procedures shall not be provided unless requested by NASA. System
> test procedures shall be provided prior to test execution.
>
> SOW Ref.: 1.5.1.1.7, 1.5.1.2.7, 1.5.2.2.7, and 1.5.2.3.7
>
> Submission:

Initial -- draft, 5 working days prior to start of Dry Run

Final -- 5 working days prior to start of Formal Test

Approval -- NA

Submission Frequency -- as required for every release/delivery test
activity

> Applicable Documents:
>
> Data Preparation Information:

Scope -- Test procedures shall be created for subsystem and system
testing for the MCC (including BCC/HSR), IPS, GSDE, and CDE services.
The test procedures shall contain detailed procedures to be followed,
acceptance criteria, and requirements trace ability.

Content -- The subsystem and system test procedures shall contain the
following information, but not be limited to:

Identification of system or subsystem to be tested

Test objectives

Resource requirements (including personnel, test equipment, test
environment, configuration, external requirements)

Step-by-step procedures (including performance)

Pass/Fail criteria

Requirement trace ability

Format: Contractor discretion

Distribution: per Contracting Officer's letter

> Maintenance -- no updates required.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0070

DRD Title: Test and Verification Report

Data Type: System Level: 2/ Subsystem level: 3

Page: 1 / 1

Description/Use -- Test reports are to specify the formal testing
results of hardware and software systems for the following mission
services: 1) IPS, 2) MCC and BCC/HSR 3) GSDE 4) CDE. The test results
shall be developed posttest execution. The test reports shall include
requirement verification matrices for all changes. Test reports shall be
created for subsystem and system level testing. Subsystem test reports
shall not be provided unless requested by NASA. System test reports
shall be provided prior to test execution.

> SOW Ref.: 1.5.1.1.7, 1.5.1.2.7, 1.5.2.2.7, and 1.5.2.3.7
>
> Submission:

Initial -- NA

Final -- System: 30 days after test completion

Approval -- NA

Submission Frequency -- as required for every release/delivery test
activity

Applicable Documents:

> Data Preparation Information:

Scope -- Test reports shall be created for subsystem and system testing
for the MCC (including BCC/HSR), IPS, GSDE, and CDE services. The test
reports shall contain detailed results of the test and verification
activities

Content -- The subsystem and system test reports shall contain the
following information, but not be limited to:

Identification of system or subsystem tested

Test objectives results

Resource actuals (including personnel, test equipment, test environment,
configuration, external requirements)

Procedure verification results (including performance)

Pass/Fail results

Requirement trace ability

Format: Contractor discretion

Distribution: per Contracting Officer's letter

> Maintenance -- no updates required.

#  **DATA REQUIREMENTS DESCRIPTION (DRD)**

> DRD No.: MSOC-JSC-0071
>
> DRD Title: Acceptance Review Package
>
> Data Type: 1
>
> Page: 1 / 1
>
> Description/Use -- The Acceptance Review package is to be provided to
> NASA for approval of each modification deliveries for the following
> mission services: 1) IPS, 2) MCC (including BCC/HSR).
>
> SOW Ref.: 1.3.24, 1.5.1.1.2, 1.5.1.2.2, and 1.5.1.2.3
>
> Submission:

Initial -- NA

Final -- within 4 weeks of system test completion

Approval -- within 8 weeks of system test completion

Submission Frequency -- required for each modification delivery or
independent delivery

> Applicable Documents:
>
> Data Preparation Information:

Scope -- The Acceptance Review package is a summary of the modification
delivery content, test status, and delivery readiness to operations.

Content -- The package shall include, but not be limited to, the
following specific to the changes: content overview, overview of
subsystem and system test plan/procedures, test report status, AR
status, documentation status, performance review, security review, QA,
issues, operations procedure status, open items

Format: presentation format

Distribution: per Contracting Officer's letter

> Maintenance - none required.

DATA REQUIREMENTS DESCRIPTION (DRD)

DRD No.: MSOC-JSC-0072

DRD Title: Design Review

Data Type: 1

Page: 1 / 2

Description/Use - The contractor shall provide a design review for each
delivery to the IPS, MCC, BCC and HSR systems/subsystems. The Design
Review shall provide NASA insight into the contractor proposed design to
meet the NASA approved changes. The Design Review shall be provided
prior to implementation to allow for changes to design. NASA shall
approve the Design Review, prior to commencing implementation. There are
two types of Design Review packages: (1) System/Subsystem Functional
Design Review (SFDR) and (2) System/Subsystem Detailed Design Review
(SDDR).

SOW Ref.: 1.5.1.1.2, 1.5.1.2.2, 1.5.1.1.6, and 1.5.1.2.6

Submission:

Initial -- SFDR -- NA, SDDR -1 week prior to final

Final -- SFDR -- per Performance Standards for modification design and
cost response, SSDR - 30 days prior to implementation start

Approval -- SFDR -- within 30 days of final SFDR submission, SSDR - at
implementation start

Submission Frequency -- required for all modification changes

Applicable Documents:

Data Preparation Information:

Scope -- The Design Review packages, SFDR and SSDR, shall contain a
system engineering analysis and design based on the requirement(s) of
the proposed modification.

Content --

The System/Subsystem Functional Design Review package shall contain, but
not limited to, the following: requirement description, assumptions and
constraints, design proposal, feasibility and tradeoff studies, impact
assessment (including performance, QA, Safety, RMA, and security), cost
estimates, schedule estimates, interface definition, resource
requirements, operational concepts, and verification philosophy.

The System/Subsystem Detailed Design Review package shall contain, but
not be limited to, the following: detailed system/subsystem requirement,
assumptions and constraints, detailed design proposal and engineering
assessment, impact assessment (including performance, QA, Safety, RMA,
and security), documentation identification, revised cost estimates,
schedule, interface definition, resource requirements, operational
concepts, and verification matrix. The contractor shall also provide at
the SSDR the Design Specification (DRD MSOC-JSC-0073) for the
system/subsystem modification.

Format: presentation

Distribution: per Contracting Officer's letter

Maintenance - change pages only due to action item responses.

DATA REQUIREMENTS DESCRIPTION (DRD)

> DRD No.: MSOC-JSC-0073
>
> DRD Title: Design Specifications
>
> Data Type: System Design Spec: 2 / Subsystem Design Spec: 3
>
> Page: 1 / 1
>
> Description/Use -- A separate system design specification for the MCC
> (including BCC/HSR) and IPS systems shall be provided that defines the
> current architecture baseline. In addition, design specifications
> shall be provided for each IPS, MCC, BCC, and HSR subsystems, both
> hardware and software.
>
> SOW Ref.: 1.5.1.1.3, 1.5.1.2.3, 1.5.1.1., and 1.5.1.22
>
> Submission:

Initial -- NA

Final -- System Design specification shall be provided annually at the
end of the government fiscal year.

Approval -- NA

Submission Frequency - annual

> Applicable Documents:
>
> Data Preparation Information:

Scope -- The System Design Specification shall contain the overview of
the hardware and software content, data flows, functional system
diagrams, and system engineering points of contact. The subsystem design
specifications shall contain

Content -- Block diagrams with associated descriptions of each function
to be performed shall be included. The specifications shall include at
least information flow, capacity requirements/limits, design
constraints, performance parameters, interface description, environment
information, RMS, operability, requirements trace ability, standards,
and drawings.

Format: technical document in Contractor's format

Distribution: per Contracting Officer's letter

> Maintenance - as changes occur

DATA REQUIREMENTS DESCRIPTION (DRD)

1\. DRD No.: MSOC-JSC-0074

2\. DRD Title: Integrated Planning System (IPS) Operations Concept

3\. Data Type: 2

4\. Page: 1/ 2

5\. Description/Use - This document defines the operational concept for
the satisfaction of the system requirements, describes the way in which
the system will appear to its users, and the ways in which the users
will interact with the system.

SOW Ref.: 1.5.1.2.11

6\. Submission:

Initial -- From start of contract + 90 days

Final -- NA

Approval -- Due 30 days after submittal.

Submission Frequency -- As Required

7\. Applicable Documents:

> Integrated Planning System (IPS) Level A Requirements, JSC-13565
>
> Integrated Planning System (IPS) Operations Concept, JSC-13601

8\. Data Preparation Information:

> Scope:
>
> To identify and document the operations concept used to satisfy system
> requirements and describe user interface/interaction.
>
> Content -- This document shall contain, as a minimum:
>
> A definition of each user group and scenarios that are applied to
> operate, maintain, or support the software in an operational
> environment.
>
> A summary of the user needs for the system in terms of the primary
> use, secondary use, and the environment in which the user operates.
>
> A description of the system operational capability in terms of system
> functions, functional relationships, and operations table (user
> actions and responses to system functions for each operations mode).
>
> A set of scenarios depicting operational flow from a functional
> perspective.
>
> A set of scenarios depicting operational flow from a data/information
> flow perspective.
>
> Where appropriate, high-level scenarios will be supported by more
> detailed scenarios addressing processing/data flow at a lower level.
>
> Format: - Contractor provided format is acceptable
>
> Distribution: - per Contracting Officer's letter

Initial -- Shall be via both hardcopy and electronic as directed by the
IPS Project Manager, or his designee, and shall be made available
electronically via a web page, or like means, for user access.

Final -- Shall be via both hardcopy and electronic as directed by the
IPS Project Manager, or his designee, and shall be made available
electronically via a web page, or like means, for user access.

Update -- Shall be via both hardcopy and electronic as directed by the
IPS Project Manager, or his designee, and shall be made available
electronically via a web page, or like means, for user access.

9\. Maintenance -- The Integrated Planning System (IPS) Operations
Concept shall be reviewed on an annual basis, as appropriate, and
revised as necessary.

DATA REQUIREMENTS DESCRIPTION (DRD)

DRD No.: MSOC-JSC-0080

DRD Title: Contractor Security Management Plan

Data Type: 1

Page: 1 / 2

Description/Use: The plan shall be used to define the contractor
security management task and shall include separate annexes/appendices
for COMSEC procedures and Secure Operations Procedures and
Sensitive/Protected Operations Procedures

SOW Ref.: 1.3.2.1

Submission

Initial: due with proposal

Final: Award of contract + 60 days

Approved: Start of contract

Submission frequency: annual

Applicable documents (note: some documents may fall into more than one
category and are grouped for reference only)

Federal Documents:

OMB circular A-130, App. III, Security of Federal Automated Information
Resources

NIST Special Publication 800-18 "Guide for Developing Security Plans

FAR 52.204-2

National Security Decision Memorandum (NSDM) 119

Space Network Security Classification Guide

Export Administration Regulations (EAR)

Arms Export Control Act (AECA)

Space Network Security Classification Guide

NISPOM National Industrial Security Program Operating Manual

Internal Program Security Requirements Handbook

NASA Agency and JSC Center documents

NPG 2810.1 Security of Information Technology

JSC JPG 2810.1B JSC IT Security Handbook

NASA Security handbook 1620.3, ch. 46

JSC-29234 "MOD IT Security and Contingency Planning Process"

National Security documents

Executive Order 12958: National Security Information

COMSEC Security Procedures (CSOC-JSC-PRO-001548)

TEMPEST Countermeasures for Facilities (NTISSI 7000)

JSC COMSEC Maintenance Support Plan

COMSEC Logistics Control Guide

STS COMSEC Key Control Agreement

NASA COMSEC Manual NHB 1600

NASA Security handbook 1620.3, ch. 46

International Standards documents

SSP 50525 "SART Security Management Processes" Section 6

Data Preparation Information

Scope: The Security Management Plan shall describe the Contractor's
approach for meeting and maintaining the security integrity of the
security baseline. The plan shall address the security requirements for
facilities, systems, equipment, personnel, information, classified
automated information systems, communications, sensitive IT security
procedures, COMSEC, and Secure Operations Procedures. This plan
establishes the security procedures, Government/contractor relationships
and assigns responsibilities for all physical, personnel, and IT
security required for the activity specified in the SOW. It is
applicable to all contractor and subcontractor personnel, operations and
procedures. This plan includes the MCC Mission Critical Systems, the
IPS, the MCC development and integration systems (GSDE & CDE), and the
MCC COMSEC.

Content: The management structure, processes and reporting requirements,
techniques and formats shall be established, defined and documented to
ensure adequate visibility and insight for Government personnel. The
Security Management Plan shall include, as a minimum, the following:

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

Methodology used to ensure separation of duties of IT security and
operational elements.

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

Description of the security baseline configuration management program.

The methodology for obtaining certifications and re-certifications
including as a minimum

Security Plan approval

Authorization to Process, mission critical systems

Authorization to Process, non-mission critical systems.

Process for developing security implementation plans for approved
systems in development including to identification, documentation,
development and protection of new systems under this contract

Approach to development and approval of COMSEC procedures

Approach to development of procedures for protection of sensitive
information.

Process for identification, reporting and resolution of IT security
incidents, with MOD

Format: Format shall be in the form specified by NIST computer security
guidelines.

Distribution: per Contracting Officer's letter

Maintenance: Document shall be updated and approved annually.

DATA REQUIREMENTS DESCRIPTION (DRD)

DRD No.: MSOC-JSC-0081

DRD Title: Facility Security Plan

Data Type: 1

Page: 1 / 2

Description/Use:

The facility security plan is used to document the security requirements
of the facility and describe the controls in place or planned for
meeting those requirements. Controls include system capabilities,
processes and procedures.

The facility security plan is used to document the results of the risk
analysis, identify the unmitigated security risks, and identify
potential impact of those risks.

The facility plan is used to delineate responsibilities and expected
behavior of all individuals who access the system.

The facility security plan includes by definition the facility
contingency plan identified as the Emergency Preparedness and Disaster
Recovery Plan (DRD No. SMSDSC -- JSC 0011)

> SOW Ref.: Section 1.5.5.4

Submission

Initial: Jan 31^st^ of each year

Final: March 1^st^ of each year

Approved: March 30^th^ of each year

Submission frequency: annual for Mission Critical Systems, all others as
required

Applicable documents:

Federal Documents:

OMB circular A-130, App. III, Security of Federal Automated Information
Resources

NIST Special Publication 800-18 "Guide for Developing Security Plans

FAR 52.204-2

National Security Decision Memorandum (NSDM) 119

Space Network Security Classification Guide

Export Administration Regulations (EAR)

Arms Export Control Act (AECA)

Space Network Security Classification Guide

NISPOM National Industrial Security Program Operating Manual

Internal Program Security Requirements Handbook

NASA Agency and JSC Center documents

NPG 2810.1 Security of Information Technology

JSC JPG 2810.1B JSC IT Security Handbook

NASA Security handbook 1620.3, ch. 46

JSC-29234 "MOD IT Security and Contingency Planning Process"

National Security documents

Executive Order 12958: National Security Information

COMSEC Security Procedures (CSOC-JSC-PRO-001548)

TEMPEST Countermeasures for Facilities (NTISSI 7000)

JSC COMSEC Maintenance Support Plan

COMSEC Logistics Control Guide

STS COMSEC Key Control Agreement

NASA COMSEC Manual NHB 1600

NASA Security handbook 1620.3, ch. 46

International Standards documents

SSP 50525 "SART Security Management Processes" Section 6

Data Preparation Information

Scope: A separate Facility Security Plan shall be provided for each
facility covered by this contract. The Plan shall describe the facility
security capabilities, processes and procedures implemented to maintain
the security integrity for the facility. The plan shall address the
security requirements for facilities, systems, equipment, personnel,
information, classified automated information systems, communications,
sensitive IT security procedures, COMSEC, and Secure Operations
Procedures. Each security plan shall be specifically generated to
address the type of facility and information processed in the facility
as defined JPG 2810.1 (latest version). It is applicable to all
facilities identified in this Statement of Work.

Content: The processes for data collection and risk analysis shall be
established, defined and documented to ensure adequate visibility and
insight for Government personnel.

The content described in JPG 2810.1B (latest) Section 5.11 "IT Security
Plan Content" shall be adhered to.

Additional content shall address and include MCC/IPS Mission critical
requirements not necessarily included in JPG system security guidelines.

Format: as defined by Mission Operations, Engineering and Center
Operations Directorates Computer Security Officer Security Plan
Templates

Distribution: per Contracting Officer letter.

Maintenance:

Changes to each facility security plan shall be documented per the
NASA/JSC Facility Computer Security Officer guidelines for addendums to
security plans. Contents of addendums shall be incorporated into the
next release of the security plan.

Security plans for General Support Systems and Mission Support systems
shall be updated as a minimum every three years, as significant
architecture or functional changes are incorporated, or as required by
NASA.

Security plans for Mission Critical Systems and/or JSC Major Information
Systems (JSC JPG 2810.1 B Appendix A) shall be updated as a minimum
every 12 months, as significant architecture or functional changes are
incorporated, or as required.

Click on the following link to access the Phase-In Plan.