### ATTACHMENT J-1-B

#### PERFORMANCE REQUIREMENTS SUMMARIES 

This summary is a cumulative listing of the revised Performance
Requirements contained in RFP Attachment J-1-A, the Space Flight
Operations Contract Statement of Work.

Initiatives during the NASA-USA pre-contract "partnering process"
resulted in the revision of the SOW Performance Requirements. These
initiatives are documented in "Decision Packages" developed and approved
by the TMRs and APMs for their respective WBS/SOW areas. Final
disposition of these Decision Packages was accomplished by the SFOC
Convergence Team. The results of this effort are reflected in the
contract SOW and this attachment.

This summary does not reflect the metrics for Phase II activity or the
method for documenting that performance. This information will be
provided with each contract/task addition to the SFOC.

1.1.1.1 RESERVED

1.1.1.4 Risk Management

Required Service: Reporting anomalies to the appropriate government
interface.

Standard: All of anomalies reported in accordance with applicable NSTS
08126 and SSP 30229 requirements.

MER: 2% of anomalies reported late but in no case greater than 5 days
beyond specified requirements, and no out-of-family anomalies reported
late.

Standard: All anomalies and nonconformance that occur during or
constrain launch countdown and flight operations reported as soon as
practical.

MER: 0%.

[Proposed Method of Documenting Performance]{.underline}: TBS

**1.1.6.1 FACILITY MANAGEMENT**

Required Service: Deliver specified end products on schedule and stay
within negotiated budget

Standard: All end products are delivered on schedule

Expectation: 85% of all end products delivered on schedule

MER: 70% of all end products delivered on schedule

[Proposed Method of Documenting Performance]{.underline}: TBS

Required Service: Maintain systems, software, firmware, facilities and
equipment.

Standard: Perform 100% of all planned maintenance tasks delineated in
the yearly maintenance plan (ref. DR 1.5.5.2).

Expectation: Perform 90% of all maintenance tasks delineated in the
yearly maintenance plan

MER: 15% of tasks not completed, 85% completed but in no case impact
safety, mission success or major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: TBS

**1.1.6.2 PROPERTY MANAGEMENT**

Required Service: Maintain approved property management systems and
satisfactory ratings for each category in accordance with NFS Tables
18-45-1 and -2B to subpart 18-45.72.

Standard: Meet criteria for satisfactory rating in all rating
categories.

Expectation: Satisfactory rating in 80% of all rating categories with
recovery of each unacceptable within 60 days.

MER: Satisfactory rating in 65% of all rating categories with recovery
of each unacceptable within 90 days.

[Proposed Method of Documenting Performance]{.underline}: TBS

**1.1.6.3 SECURITY MANAGEMENT**

Required Service: Provide physical access/egress, classified (CI)
information and violence/damage control.

Standard: No security violations, anomalies, unauthorized CI
disclosures, and preventable security incidents.

MER: No violations or incidents that result in compromises, disclosures,
serious personal injury or intentional physical damage.

[Proposed Method of Documenting Performance]{.underline}: TBS

1.1.7 Manifest and Schedules

Required Service: Meet major program schedule milestones as defined in
NSTS 07700, Vol.III, NSTS 08178, and SSP 50200-02, Vol. II.

Standard: Meet major program schedule milestones.

MER: No impacts to these dates due to contractor performance.

[Proposed Method of Documenting Performance]{.underline}: As required by
DRD's 1.1.1.3-a, b, c.

1.2.1.1 Post Flight Analysis

Required Service: Completion of all post flight analyses in all
technical areas.

Standard: All products 100% technically accurate.

MER: No errors that require rework of analyses.

Standard: All products delivered on or before due date.

MER: No major program schedule milestones missed.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.1.2-a and -c, Reference PDP MS4-002.

1.2.1.2 Ascent Margins Assessment

Required Service: Provide Ascent Margins Assessment.

Standard: All products 100% technically accurate.

MER: 0% errors leading to incorrect CoFR positions that affect safety,
mission success, or major program schedule milestones.

Standard: All products delivered on or before due date.

MER: No major program schedule milestones missed.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.1.2-a and -c, Reference PDP MS4-002.

**1.2.1.3 Cargo Integration Engineering Analysis**

Required Service: Provide all assessment and analysis necessary to
assure compatibility between Shuttle and cargo.

Standard: 100% complete by Orbiter rollout review.

MER: All compatibility completed prior to FRR and in no case impact
cargo mission objectives or major program milestones.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.1.3-b, Reference PDP MS2-001, 002, and MS3-002.

Required Service: Shuttle models provided to payload customer.

Standard: All models provided within 30 working days after request.

MER: Models delivered 5 working days late but in no case not support
payload customer design verification negotiated need date.

Standard: All models are 100% technically accurate.

MER: No errors will cause any impact to safety, mission success, or
major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.1.3-a, Reference PDP MS2-001, 002, and MS3-002.

Required Service: Engineering data to payload customer.

Standard: 100% of data delivered 5 months prior to launch.

MER: Data may be delivered 2 weeks late but in no case not support
payload customer negotiated need date to support major program schedule
milestones.

Standard: All engineering data is 100% technically accurate.

MER: No errors will cause any impact to safety, mission success, or
major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.1.3-b, Reference PDP MS2-001, 002, and MS3-002.

**1.2.1.5 Configuration Engineering**

Required Service: Shuttle systems-level drawings and reconfiguration
products complete for each shuttle flight.

Standard: 100% of all engineering products delivered in accordance with
mission schedule.

MER: 1% may be delivered late but in no case not support negotiated need
dates for compatibility with launch processing.

Standard: Engineering products contain no contractor induced technical
errors.

MER: The average error/flight shall be 6 or less. All technical errors
must be dispositioned by Orbiter Rollout for OPF processed payloads and
L-2 for pad installed payloads with no errors impacting safety, mission
success, or major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.1.5-a and b, Reference PDP MS3-001, 002, and MS8-001.

**1.2.1.6 LSEAT Configuration and Database Management**

Required Service: Provide LSEAT configuration and database maintenance
and mission support.

Standard: All products 100% technically correct.

MER: No errors that could result in incorrect launch recommendations.

Standard : All products delivered on or before due date in support of
major program schedule milestones.

MER: No missed major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.1.6-a and b, Reference PDP MS4-002.

**1.2.2.1 Integrated Mass Properties**

Required Service: Provide integrated mass property products.

Standard: All products are implemented and delivered in accordance with
program template milestones.

MER: 1% of the products are late but in no case impact safety, mission
success, or major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.2.1-a, Reference PDP MS4-002.

**1.2.2.2 Trajectory Design Data Packages (TDDP)**

Required Service: Provide TDDP publication.

Standard: All TDDP products are implemented and delivered in accordance
with program template milestones.

MER: 1% of products can be late but in no case impact safety, mission
success, or major program schedule milestones.

Standard: 100% of all TDDP products are technically accurate.

MER: 0% errors that affect safety, mission success, or major program
schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.2.2-a and b, Reference PDP MS4-002.

**1.2.2.4** **Engineering** **Integration Plan (PIP) Annexes**

Required Service: Develop and baseline Integration Plan (IP) Annexes 1
(Payload Data Package), and 6 (Crew Compartment Configuration).

Standard: 100% Annexes baselined in accordance with IP schedule.

MER: 10% of Annexes may be baselined late but not later than Flight
Planning and Stowage Review, and in no case impact major program
schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: By metrics
associated with inputs to SFOC for DRD 1.2.2.4a, b, and c.

**1.2.2.5 Element Interface Control Document (ICD)**

Required Service: Provide maintenance of baselined ICD's.

Standard: 100% of submitted changes have all needed contractor technical
concurrences.

MER: 1 change annually may not have all contractor technical
concurrences, but in no case impact flight schedules.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.2.5, Reference PDP MS3-002, MS8-003.

**1.2.2.6 Payload Unique ICD's**

Required Service: Develop and baseline ICD's and IRD's.

Standard: 100% ICD's and IRD's are baselined in accordance with flight
production schedule.

MER: 5% of ICDs/IRDs may be baselined later than the negotiated
schedules, but in no case impact major program schedule milestones.

Standard: ICD's and IRD's are 100% technically accurate.

MER: ICD's and IRD's contain no more than an average of 5 contractor
induced technical errors per ICD/IRD with all errors corrected by
Orbiter Rollout Review and in no case impact safety, mission success, or
major program schedule milestone.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.2.6, Reference PDP MS3-001.

**1.2.2.7 Payload OMRS Test Requirements**

Required Service: Develop and provide test requirements for OMRS
baselining.

Standard: 100% known OMRS requirements approved 10 working days prior to
LSRR program milestones.

MER: Requirements may be approved 5 working days late.

[Proposed Method of Documenting Performance]{.underline}: Per PDRD
P-1.2.2.7, Reference PDP MS3-002.

**1.2.2.8 Technical Integration Analysis**

Required Service: Integrated analysis of technical changes associated
with OMRS, LCC, etc.

Standard: 100% assessments provided prior to program review milestones.

MER: 0% of assessment may be provided at program review milestone.

[Proposed Method of Documenting Performance]{.underline}: By metrics
tracking inputs to SFOC for boards listed in SOW 1.2.2.8, Reference PDP
MS8-002, 003.

**1.2.2.9** **STOWAGE ENGINEERING, INTEGRATION, AND DOCUMENTATION**

Required Services: Prepare and distribute CCCD's to support Shuttle
program milestones for each Shuttle flight.

Standard: 100% accurate at time of physical integration of flight
equipment.

MER: 1% of drawings and Drawing Change Notices (DCNs) from each CCCD
release may contain contractor induced errors that could affect physical
integration. No contractor error shall cause modification of flight
equipment to accomplish physical integration.

Standard: CCCDs are distributed ten working days prior to program
stowage reviews.

MER 1% of drawings can be delivered late. However, all CCCDs must be
available at the program stowage reviews and in no case shall delivery
impact scheduled milestones.

1.3 Risk Assessment

Required Service: Contractor to accurately identify and provide
information on increased risk to the Government and present to the
Government for acceptance.

Standard: 95% of risk packages presented to the Government are accepted.

Expectation: 85% of risk packages presented to the Government are
accepted.

MER: 80% of risk packages presented to the Government are accepted.

[Proposed Method of Documenting Performance:]{.underline} Establish
process to collect data from the initial risk review that includes
Government participation (e.g. Level III Risk Review) - Quarterly.

Required Service: Contractor will correctly assess risk and may
disposition items which pose no additional risk to the Government.

Standard: 95% of items correctly assessed as no increased risk validated
through use, Government audit, or Government surveillance.

Expectation: 85% of items correctly assessed as no increased risk
validated through use, Government audit, or Government surveillance.

MER: 80% of items correctly assessed as no increased risk validated
through use, Government audit, or Government surveillance.

[Proposed Method of Documenting Performance]{.underline}: NASA collected
recall data from Government audits, Government surveillance or use -
Quarterly .

**1.3 Quality Assurance**

Required Service: Assure that all critical hardware meets inspection
requirements.

Standard: 98% of all mandatory Government inspections are accepted.

Expectation: 95% of all mandatory Government inspections are accepted.

MER: 92% of all mandatory Government inspections are accepted.

[Proposed Method of Documenting Performance:]{.underline} Establish
process for inspectors to annotate call sheets - Monthly.

Required Service: Assure that all hardware that have designated
inspection points meet requirements.

Standard: Success rate of SFOC work volume greater than 95% .

Expectation: Success rate of SFOC work volume greater than 90%.

MER: Success rate of work SFOC volume greater than 85%.

[Proposed Method of Documenting Performance:]{.underline} First time
quality data - Monthly .

**1.3 Safety Assurance**

Required Service: Contractor will assure that neither non-SFOC
contractor personnel are injured nor NASA property damaged by
accidents/incidents during processing.

Standard: 10 mishaps per year (updated quarterly)

Expectation: 15 mishaps per year (updated quarterly)

MER: 20 mishaps per year (updated quarterly)

[Proposed Method of Documenting Performance]{.underline}: Injury data:
KSC 6-2 forms, Property data: KSC PER forms, Equivalent forms at other
Centers. Establish process to collect work volume data for
normalization - Monthly .

**1.4 Flight Elements**

Required Service: Provide hazardous waste material weight reduction for
hazardous waste under the control of the contractor.

Standard: Reduce hazardous waste material weight no less than 10% over
each year.

Expectation: Reduce hazardous waste material weight no less than 5% over
each year.

MER: No reduction in hazardous waste material weight.

[Proposed Method of Documenting Performance]{.underline}: TBS

**1.4.1.1** **MISSION AND TURNAROUND**

Required Service: Obtain timely product deliveries from the Orbiter
Element Subcontractor.

Standard: A score of 105% or better for the product delivery metric.

Expectation: A score of 97% or better for the product delivery metric.

MER: A score of 90% or better for the product delivery metric.

[Method of Documenting Performance:]{.underline} The product delivery
metric is computed by initializing the metric at 100%, then adjusting as
follows:

Adding 1% for each product delivered 1-5 days early.

Adding 2% for each product delivered 6 or more days early.

Subtracting 2% for each product delivered 1-5 days late.

Subtracting 4% for each product delivered 6 or more days late.

Any product defined as a DRD in the subcontract is considered a product
for computing the metric. "As required" products are considered on time
when delivered.

**1.4.1.2 Orbiter Logistics**

Required Service: Provide reparable hardware required for Orbiter
processing and flight.

Standard: 97.0% of all reparable Orbiter hardware requirements satisfied
by the negotiated need date.

Expectation: 96.0% of all reparable Orbiter hardware requirements
satisfied by the negotiated need date.

MER: No less than 90.0% of all reparable Orbiter hardware requirements
satisfied by the negotiated need date.

[Proposed Method of Documenting Performance:]{.underline} Logistics
ATLAS (Analytical Trends of Logistics Availability and Supportability)
Report - Monthly.

Required Service: Provide nonreparable hardware required for Orbiter
processing and flight.

Standard: 98.7% of all nonreparable Orbiter hardware/consumable
requirements satisfied by the negotiated need date.

Expectation: 97.7% of all nonreparable Orbiter hardware/consumable
requirements satisfied by the negotiated need date.

MER: No less than 96.7% of all nonreparable Orbiter hardware/consumable
requirements satisfied by the negotiated need date.

[Proposed Method of Documenting Performance:]{.underline} Logistics
ATLAS Report - Monthly.

Required Service: The contractor shall identify to the Government any
LRUs with the potential for cannibalization within the next 6 month
period. Each cannibalization of hardware shall be reported to the
Government no more than 8 hours after occurrence.

Standard: Fewer than 0.075% of all Orbiter hardware requirements
satisfied by cannibalization.

Expectation: Fewer than 0.1% of all Orbiter hardware requirements
satisfied by cannibalization.

MER: No more than 0.2% of all Orbiter hardware requirements satisfied by
cannibalization.

[Proposed Method of Documenting Performance:]{.underline} Logistics
ATLAS Report - Monthly.

Required Service: The contractor shall provide hardware which is
suitable for use upon receipt at the Kennedy Space Center or other
locations where Shuttle processing/servicing is conducted.

Standard: 100.0% of received hardware passes physical and functional
interfaces.

Expectation: At least 99.7% of received hardware passes physical and
functional interfaces.

MER: No less than 99.5% of received hardware passes physical and
functional interfaces.

[Proposed Method of Documenting Performance]{.underline}: Manual
feedback from Quality with Briefing Charts -Monthly.

Required Service: Provide TPS hardware required for Orbiter processing
and flight.

Standard: 99.0% of all Orbiter TPS requirements satisfied by the
negotiated need date.

Expectation: 95.0% of all Orbiter TPS requirements satisfied by the
negotiated need date.

MER: 93.0% of all Orbiter TPS requirements satisfied by the negotiated
need date.

[Proposed Method of Documenting Performance:]{.underline} Manual
feedback from the TPSF with Briefing Charts - Monthly.

**1.4.1.3 ORBITER TURNAROUND PROCESSING**

Required Service: Verification of vehicle and systems performance
readiness.

Standard: All ground verification requirements completed or
dispositioned through appropriate NASA forums.

Expectation: No processing operations executed without properly
completed or dispositioned verification of pre-requisite requirements.

MER: No processing operations executed without properly completed or
dispositioned verification of pre-requisite requirements.

**1.4.1.5 ORBITER HARDWARE PRODUCTION**

**Required Service: Provide high quality Orbiter modification hardware,
OMDP, and ET umbilicals.**

**Standard: The absence of Inflight Anomalies (IFAs) of Orbiter
modification hardware, OMDP, and ET umbilicals attributed to the
Contractor's performance which preclude accomplishment of major mission
objectives.**

# MER: Successful accomplishment is evidenced by the absence of IFA's attributed to the

**Contractor's performance which preclude accomplishment** **of major
mission objectives.**

**1.4.1.5.2 HARDWARE, MODIFICATIONS, AND SUPPORT**

Required Service: Ensure vehicle modification product quality

Standard: Product assurance (inspection) verification of hardware
attributes during manufacturing as reported in the product quality
report (non- conformances per 1000 direct labor hours) shall be no more
than 3.0/KDLH.

Expectation: Product assurance (inspection) verification of hardware
attributes during manufacturing as reported in the product quality
report (non- conformances per 1000 direct labor hours) shall be no more
than 4.5/KDLH.

MER: Product assurance (inspection) verification of hardware attributes
during manufacturing as reported in the product quality report (non-
conformances per 1000 direct labor hours) shall be no more than
6.0/KDLH.

**1.4.1.5.3 ORBITER OMDP**

4.  **ORBITER/EXTERNAL TANK UMBILICALS**

Required Service: Provide ET umbilicals.

Standard: All ET umbilicals delivered by the negotiated delivery date.

Expectation: No more than 1 ET umbilical shipset delivered more than 15
days after the negotiated delivery date.

MER: No more than 1 ET umbilical shipset delivered more than 30 days
after the negotiated delivery date.

Required Service: ET umbilical product quality.

Standard: Product assurance (inspection) verification of hardware
attributes during manufacturing as reported in the product quality
report (non-conformances per 1000 direct labor hours) shall be no more
than 4.0/KDLH.

Expectation: Product assurance (inspection) verification of hardware
attributes during manufacturing as reported in the product quality
report (non-conformances per 1000 direct labor hours) shall be no more
than 5.5/KDLH.

MER: Product assurance (inspection) verification of hardware attributes
during manufacturing as reported in the product quality report
(non-conformances per 1000 direct labor hours) shall be no more than
7.0/KDLH.

1.4.3.1 Flight Software Processing

Required Service: Provide BFS Software Approval Sheet (SAS) and test
patches.

Standard: Released software patches are 100% technically accurate,
complete in content and delivered on the negotiated schedules.

Expectation: Slips or redelivery caused by BFS not meeting negotiated
schedules or due to a redelivery to correct an error are allowed if no
additional resource impact to outside organizations is incurred.

MER: No errors in released test patches caused by BFS for crew training
or testing which cause impacts to mission safety, mission success or
scheduled launch date. There may be errors caused by BFS in the released
test patches which impact areas other than mission safety, mission
success or scheduled launch date.

[Proposed Method of Documenting Performance]{.underline}: Artemis
schedules, DRD records, CRs, DRs, SASCB decisions/minutes.

Required Service: Provide Telemetry Format Load/Decommutation Format
Load/Fetch Pointer Load (TFL/DFL/FPL) Universal Patch Format (UPF)
patches.

Standard: Delivered 100% correct in content and accuracy for MMU memory
locations.

Expectation: No errors requiring redelivery of patch which impacts
verification and mass memory build schedules.

MER: No errors which require program waivers, or impact safety, mission
success or major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: Artemis
schedules, DRD records, SASCB decisions/ minutes.

1.4.3.3 Avionics and Software System Support

Required Service: Provide I-load Selection Report.

Standard: Delivered I-loads 100% accurate.

Expectation: No errors requiring redelivery which impacts I-load
development schedules.

MER: No errors requiring patches or waivers or impact safety, mission
success, or major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: Artemis
schedules, DRD records, CRs, DRs, SASCB decisions/minutes.

Required Service: Integrated DPS issues resolution and documentation
update.

Standard: Issue resolution and documentation updates are 100%
technically accurate, complete in content, and delivered on the
negotiated schedules.

Expectation: Issues resolution and documentation updates are delivered
per the negotiated schedules. If required, redelivery is made in time to
prevent impact to SSPO milestones.

MER: 5% of the products can be delivered late but in no case later than
the SASR Readiness Review. All issue resolution should meet and support
SSPO milestones.

[Proposed Method of Documenting Performance]{.underline}: Artemis
schedules, DRD records, SASCB decisions / minutes.

Required Service: Develop and baseline Integration Plan (IP) Annex 4
(Command and Data Requirements)

Standard: 100% Annex baselined in accordance with IP schedule.

MER: 10% of Annex may be baselined late but not later than Flight
Planning and Stowage Review, and in no case impact major program
schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: TBS

1.4.3.4 Flight Software Reconfiguration

Required Service: Provide BFS reconfiguration deliverables to support
flight manifest.

Standard: All products affecting the BFS flight software configuration
will be delivered 100% accurate.

Expectation: Slips or redelivery caused by BFS not meeting negotiated
schedules or due to a redelivery to correct an error are allowed if no
additional resource impact to outside organizations is incurred.

MER: No errors in the BFS flight software configuration caused by BFS
which impact flight safety, mission success, or the applicable scheduled
launch date. There may be errors in the BFS flight software
configuration caused by BFS which impact areas other than mission
safety, mission success or scheduled launch date.

[Proposed Method of Documenting Performance]{.underline}: Artemis
schedules, DRD records, CRs, DRs, SASCB decisions/minutes.

1.4.3.5 Flight Software Modifications

Required Service: BFS OI deliverables.

Standard: The BFS flight software code development process will maintain
an error rate of less than or equal to .5 per 1000 lines of code change
in an OI which affected at least 2000 lines. Errors will be calculated
from the first SRR of that OI and will count all Severity 1, 2 and 3 DRs
only. A 100% accuracy will be expected for the associated data files,
configuration control files, and supporting product reports which would
impact the BFS flight software quality or configuration.

Expectation: Slips or redelivery caused by BFS not meeting negotiated
schedules or due to a redelivery to correct an error are allowed if no
additional resource impact to outside organizations is incurred.

MER: No errors in the BFS OI deliverables caused by BFS which impact
flight safety, mission success, or scheduled launch date. There may be
errors in the BFS OI deliverables caused by BFS which impact areas other
than mission safety, mission success or scheduled launch date.

[Proposed Method of Documenting Performance]{.underline}: Artemis
schedules, DRD records, CRs, DRs, SASCB decisions/minutes, CI briefings.

Required Service: Provide Software Version Description Document (VDD).

Standard: 100% accuracy for definition of configuration and
identification of flight software products which reflect the flight
software quality or configuration.

Expectation: Slips or redelivery caused by not meeting negotiated
schedules or due to a redelivery to correct an error are allowed if no
additional resource impact to outside organizations is incurred.

MER: No errors in the BFS software VDD which impact flight safety,
mission success, or scheduled launch date. There may be errors in the
BFS software VDD which impact areas other than mission safety, mission
success or scheduled launch date.

[Proposed Method of Documenting Performance]{.underline}: Artemis
schedules, DRD records, SASCB decisions/ minutes.

**1.4.5.2 RSRM LOGISTICS**

Required services: Spare parts and consumable requests filled from
inventory

Standard: 100% spare parts/consumables delivered on time to support
schedule.

MER: 3% of total transactions late with no unfilled orders 5 days prior
to start of ET/SRB mate.

**1.4.5.5 RSRM MODIFICATIONS**

Required Service: Approved closeout verification from element contractor
for each modification/change.

Standard: 100% verification within 5 days of completion of modification.

MER: 5% late but no incomplete work at ET/SRB mate.

**1.4.6.1 SSME ELEMENT PROCESSING**

Required Service: Agreement from the element contractor that the
baseline configuration has been certified and is ready for launch.

Standard: 100% baseline configuration certified prior to integration.

MER: 5% late but no incomplete work at integration from baseline
configuration.

1.4.9.1 ELEMENT PROCESSING

Required Service: Processing and delivery of flight crew equipment.

Standard: All crew equipment listed in the CCCD and SSCCD for each
flight is provided on time to meet program flight crew training and
flight planning milestones.

MER: All crew equipment is provided within 2 working days of scheduled
facility need dates, but in no case impact safety, mission success, or
major program schedule milestones.

1.4.9.3 TRAINING HARDWARE PROCESSING

Required Service: Processing, delivery and maintenance of flight crew
equipment in support of crew training activities.

Standard: All training hardware is properly configured.

MER: 1% of the training hardware is improperly configured to support
training, but in no case impact safety, mission success or crew training
objectives.

Standard: All training hardware is provided by negotiated need date.

MER: All training hardware is provided within 2 working days of the
negotiated need date but in no case impact safety, mission success, or
crew training schedules.

1.4.9.4 SHUTTLE REMOTE MANIPULATOR SYSTEM (srms) PROCESSING

Required Service: Prepare SRMS for flight

Standard: SRMS processing tasks scheduled and completed on time in
accordance with program requirements.

MER: 1% of processing milestones missed with no incomplete work at FRR
for baseline configuration and no impact to safety, mission success, or
major program schedule milestones.

1.5 Integrated Launch and Landing Operations

Required Service: Ensure Category 1 OMID procedures are current and
available.

Standard: 100% of Category 1 procedures on shelf 10 days prior to test
start for new procedures, 7 days prior to start for revised procedures,
and 3 days prior to start for minor or dash changes to the procedure.

Expectation: 96% of Category 1 hazardous procedures on shelf 10 days
prior to test start for new procedures, 7 days prior to start for
revised procedures, and 3 days prior to start for minor or dash changes
to the procedure.

MER: 6% late, but in no case impact safety, mission success or major
program schedule milestone.

Proposed Method of Documenting Performance: Shelf Date Objective
Report - Monthly.

Required Service: Meet baselined integrated test schedules.

Standard: 100% of all integrated tests are conducted within baselined
schedule timelines.

Expectation: All integrated tests are conducted within 95% of baselined
scheduled timelines.

MER: An integrated test may vary 7% from the planned baseline, but in no
case impact major Program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: Automated
report to be developed from KICS system.

1.5.2.4 Launch Readiness

Required Service: All work items identified on the initial Launch
Countdown constraints list either completed, closed, or scheduled to be
worked.

Standard: 100% of all items on the initial Launch Countdown constraints
list completed and closed prior to Launch Countdown Call-to-Stations.
(Except work items that must be either performed during the countdown
due to technical constraints or are in the final documentation closure
process.)

Expectation: 97% of all items on the initial Launch Countdown
constraints list completed and closed prior to Launch Countdown
Call-to-Stations. (Except work items that must be either performed
during the countdown due to technical constraints or are in the final
documentation closure process).

MER: 3% of items open until start of ET tanking, but in no case any work
open that impacts the remainder of the Launch countdown or safety.

Proposed Method of Documenting Performance: Current manual constraints
system to be automated on Integrated Work Control System (IWCS).

1.5.5.1 Operations

Required Service: Provide operational services scheduled on Kennedy
Integrated Control Schedules, Payload Integrated Control Schedules or
system outages to NASA and other KSC users for contractor assigned
systems which interface with others.

Standard: 100% of user request met by due date negotiated between the
contractor and the requester.

Expectation: 95% of user request met by due date negotiated between the
contractor and the requester.

MER: 10% late, with all requests met within 30 days of due date, but in
no case impact major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: New report
format from KICS system.

1.5.5.2 Maintenance

Required Service: Maintain systems, software, firmware, facilities, and
equipment.

Standard: Perform 100% of all planned maintenance tasks delineated in
the yearly maintenance plan ( DR 1.5.5.2).

Expectation: 90% of all maintenance tasks delineated in the yearly
maintenance plan (DR 1.5.5.2) completed.

MER: 15% of tasks not completed (85% completed), but in no case impact
safety, mission success or major program schedule milestones.

Proposed Method of Documenting Performance: Facility Operations and
Support Preventive Maintenance Metric Report - Monthly.

1.5.5.3 Sustaining Engineering

Required Service: Document changes to configured facilities, systems and
equipment.

Standard: 100% of all contractor generated changes documented prior to
implementation need.

Expectation: 98% of all contractor generated changes to facilities,
systems and equipment documented prior to implementation need.

MER: 5 % backlog (of contractor generated changes) to facilities,
systems and equipment late, but in no case impact safety or delay
critical milestones.

[Proposed Method of Documenting Performance]{.underline}: Ground Systems
Design Engineering (GSDE) Work Control Database - Monthly.

Required Service: Document changes to CCMS systems/applications
software/firmware.

Standard: 100% of all contractor generated CCMS system/applications
software/firmware changes documented prior to software production.

Expectation: 98% of all pre-planned contractor-generated CCMS
system/applications software/firmware changes documented prior to
implementation need.

MER: 5 % backlog (of configured products which document generated
changes) to software/firmware, but in no case impact specific user need.

[Proposed Method of Documenting Performance]{.underline}: GSDE Work
Control Database - Monthly.

Required Service: Configuration engineering documentation for
facilities, systems and equipment is released complete and with minimal
errors.

Standard: 100% of contractor changes to facilities, systems and
equipment requires no documentation correction or production
re-releases.

Expectation: 95% of contractor changes to facilities, systems and
equipment requires no documentation correction or production
re-releases.

MER: No more than 10% of contractor changes to facilities, systems and
equipment requires correction to released documentation or production
re-releases.

Proposed Method of Documenting Performance: GSDE Work Control Database -
Monthly.

Required Service: Configuration engineering documentation and code for
CCMS system/ applications software is released complete and with minimal
errors.

Standard: 100% of contractor changes to CCMS system/applications
software requires no documentation correction or immediate production
code re-releases as a result of coding errors.

Expectation: 98% of CCMS system/applications software changes requires
no correction to released documentation or immediate production code
re-releases as a result of coding errors.

MER: 95% of CCMS system/applications software changes requires no
correction to released documentation or immediate production code
re-releases as a result of coding errors.

Proposed Method of Documenting Performance: GSDE Work Control Database -
Monthly.

1.5.5.4 Logistics

Required Service: Provide parts, hardware, and materials for processing
and launch systems, facilities, and equipment.

Standard: 98% of requirements satisfied on or before the negotiated need
date.

Expectation: 96% of requirements satisfied on or before the negotiated
need date.

MER: No less than 92% of requirements satisfied on or before the
negotiated need date.

Proposed Method of Documenting Performance: DR 1.4-c - Logistics Ground
Customer Support Group.

Required Service: Provide needed hardware, parts, and materials for
processing and launch systems, facilities, and equipment so that
cannibalization does not become necessary.

Standard: No more than 0.075% of hardware requirements satisfied by
cannibalization.

Expectation: No more than 0.1% of critical hardware requirements
satisfied by cannibalization.

MER: No more than 0.2% of hardware requirements satisfied by
cannibalization.

[Proposed Method of Documenting Performance]{.underline}: DR 1.4-c -
Shop Floor Data Collection (SFDC).

Required Service: The contractor shall provide processing or launch
systems, facilities, or equipment hardware which is suitable for use
upon delivery.

Standard: No less than 99% of hardware provided suitable for use.

Expectation: No less than 97% of hardware provided suitable for use.

MER: No less than 95% of hardware provided suitable for use.

[Proposed Method of Documenting Performance]{.underline}: DR 1.4-c -
Shop Floor Data Collection (SFDC).

1.5.5.4.2 Material Management

Required Service: Provide hazardous waste material weight reduction for
hazardous waste under the control of the contractor.

Standard: Reduce hazardous waste material weight no less than 10% over
each year.

Expectation: Reduce hazardous waste material weight no less than 5% over
each year.

MER: No reduction in hazardous waste material weight.

Proposed Method of Documenting Performance: Hazardous Waste Tracking
Database - Monthly.

1.6.1.1.2 Curriculum and Lesson Development

Required Service: Flight Operations curriculum and training flows.

Standard: Curriculum or training flow contains 100% of performance
objectives required for certification or flight readiness.

Expectation: 1.5% errors or omissions in performance objectives required
for certification or flight readiness and no error impacts safety,
mission success or major program schedule milestones.

MER: 2% errors or omissions in performance objectives required for
certification or flight readiness and no error impacts safety, mission
success or major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan.

Required Service: Flight operations lessons

Standard: Lesson execution accomplishes 100% of the required performance
objectives.

Expectation: 1% of lessons are repeated in order to accomplish
performance objectives and in no case impact safety, mission success or
major program schedule milestones.

MER: 2% of lessons are repeated in order to accomplish performance
objectives and in no case impact safety, mission success or major
program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan.

1.6.1.3 Flight Crew Training

Required Service: Management and implementation of the Astronaut
Candidate Training Program.

Standard: All Astronaut Candidates complete program before completion
date identified in DR. 1.6.1.3-d.

Expectation: 1 month late but in no case impact flight crew assignments.

MER: 2 months late but in no case impact flight crew assignments.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan.

Required Service: Management and implementation of the flight or
increment specific crew training program.

Standard: Flight specific Orbiter systems crew training accomplished
within 26 weeks of planned launch date.

Expectation: + 8 weeks and in no case impact safety, mission success or
major program schedule milestones.

MER: + 14 weeks and in no case impact safety, mission success or major
program schedule milestones.

Standard: Crew training accomplished within 16 hours/week average SMS
flight specific or SSTF increment specific facility time for any
individual crew person.

Expectation: +.75 hours/week average and in no case impact safety,
mission success, or major program schedule milestones.

MER: + 1 hours/week average and in no case impact safety, mission
success, or major program schedule milestones.

Standard: Crew training accomplished within 25 hours/week average formal
catalog training time for any individual crew person.

Expectation: + 2 hours/week average and in no case impact safety,
mission success or major program schedule milestones.

MER: + 3 hours/week average and in no case impact safety, mission
success or major program schedule milestones.

Standard: All required training accomplished at the time the crew
departs to KSC for launch and in no case impact safety, mission success
or major program schedule milestones.

Expectation: All required training accomplished at the time the crew
departs to KSC for launch and in no case impact, safety, mission success
or major program schedule milestones.

MER: All training critical to safety and mission success completed at
the time the crew departs to KSC for launch and in no case impact
safety, mission success or major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan.

1.6.2.1 Flight Rules/Operations Documentation/Flight Data File (FDF)

Required Service: Flight critical operations documentation/data

Standard: No significant errors detected real-time in critical flight
operations documentation or data.

Expectation: 1 significant documentation or data error for each flight,
but in no case impact safety, mission success or major program schedule
milestones.

MER: 2 significant documentation or data error for each flight, but in
no case impact safety, mission success or major program schedule
milestones.

Standard: On time delivery of all agreed upon operations documentation
for crew review.

Expectation: One document per flight delivered late based on the agreed
upon delivery content, but in no case impact safety, mission success or
major program schedule milestones.

MER: Two documents per flight delivered late based on the agreed upon
delivery content, but in no case impact safety, mission success or major
program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan.

1.6.2.2.2 Flight Design Products

Required Service: Provide Flight Design Products (DR 1.6.2.2.2-c).

Standard: No errors in the initial delivery of critical flight design
products.

Expectation: 2 % errors in initial delivery of critical flight design
products, and in no case impact safety, mission success or major program
schedule milestones.

MER: 4 % errors in initial delivery of critical flight design products,
and in no case impact safety, mission success or major program schedule
milestones.

Standard: On time delivery of critical flight design products.

Expectation: 3 % late delivery of critical flight design products, and
in no case impact safety, mission success, or major program schedule
milestones.

MER: 5 % late delivery of critical flight design products, and in no
case impact safety, mission success, or major program schedule
milestones.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan.

**1.6.2.7 Data Collection/Reconfiguration**

Required Service: Data Reconfiguration Deliverables

Standard: 100% of the data products are error free.

Expectation: 2.5 % of the data products delivered during the previous
year contain errors, with all errors dispositioned prior to the start of
flight specific simulations, and in no case impact safety, mission
success or major program schedule milestones.

MER: 5 % of the data products delivered during the previous year contain
errors, with all errors dispositioned prior to the start of flight
specific simulations, and in no case impact safety, mission success or
major program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan

1.6.4 Flight Operations Systems and Equipment

Required Service: Flight operations system availability.

Standard: 100% flight operations system availability for the MCC, SMS,
SSTF, IPS, SAIL, and SPF.

Expectation: 2 % flight operations system non-availability for MCC and
IPS with no impact to safety, mission success or major program schedule
milestones.

Expectation: 1.5 % flight operations system non-availability for the SPF
with no impact to safety, mission success or major program schedule
milestones.

Expectation: 3 % flight operations system non-availability for the SMS &
SSTF with no impact to safety, mission success or major program schedule
milestones.

Expectation: 5 % flight operations system non-availability for the SAIL
with no impact to safety, mission success or major program schedule
milestones.

MER: No Significant impact to safety, mission success or major program
schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan

Required Service: Provide sustaining engineering and maintenance and
operations support for flight operations system and equipment.

Standard: Complete and adequate Closure of Sustaining Requirements and
Discrepancy Reports within negotiated and agreed upon user need dates
and in no case impact safety, mission success or major program schedule
milestones.

Expectation: 5 % late, but in no case impact safety, mission success or
major program schedule milestones.

MER: No Significant impact to safety, mission success or major program
schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan

Required Service: Management of software critical discrepancies to
enable the system to support flight operations.

Standard: No critical discrepancies in mission support software after
the scheduled start of mission specific training.

Expectation: No critical discrepancies after the start of mission
specific training that impact safety, mission success or major program
schedule milestones.

MER: More than 1 critical discrepancy after the start of mission
specific training that impact(s) safety, mission success or major
program schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan

1.6.4.1 Mission Control Center (MCC)

Required Service: Operate and maintain critical functions to support
flight operations in the MCC.

Standard: 99.95 % reliability of critical functions, as defined in JSC
12804, MCC Level A Requirements.

Expectation: 99.5% reliability for 20 hours of critical functions as
defined in JSC 12804, MCC Level A Requirements, with a maximum time to
restore of 1 minute and in no case impact safety, mission success or
major program schedule milestones.

MER: No Significant impact to safety, mission success or major program
schedule milestones.

Standard: 100% availability of critical functions, as defined in JSC
12804, MCC Level A Requirements.

Expectation: 99.5% availability of critical functions as defined in JSC
12804, MCC Level A Requirements, and in no case impact safety, mission
success or major program schedule milestones.

MER: No Significant impact to safety, mission success or major program
schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan

1.6.4.3 Integrated Planning System (IPS)

Required Service: Operate and maintain critical functions to support
prelaunch processing in the IPS.

Standard: 99.95 % reliability of critical functions as defined in JSC
13565, IPS Level A requirements.

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

MER: No Significant impact to safety, mission success or major program
schedule milestones.

[Proposed Method of Documenting Performance]{.underline}: DR 1.6-b,
Flight Operations Process Integrity Plan