![](media/image1.wmf){width="1.8333333333333333in"
height="1.8208333333333333in"}

U.S. DEPARTMENT OF TRANSPORTATION

FEDERAL AVIATION ADMINISTRATION

STATEMENT OF WORK

[WIDE AREA AUGMENTATION SYSTEM (WAAS)]{.underline}

[FULL LPV PERFORMANCE]{.underline}

[VERSION 11]{.underline}

[DATED]{.underline}

[SEPTEMBER 17, 2004]{.underline}

**Table of Contents**

[1. Scope 1](#scope)

[1.1. Applicable Documents 2](#applicable-documents)

[1.2. FAA Specifications 2](#faa-specifications)

[1.3. Military Specifications 2](#military-specifications)

[1.4. FAA Standards 2](#faa-standards)

[1.5. Military Standards 3](#military-standards)

[1.6. Federal Standards 3](#federal-standards)

[1.7. Other FAA Documents 3](#other-faa-documents)

[1.8. Other Documents 4](#other-documents)

[2. Contract Execution 5](#contract-execution)

2.1 [Full LPV Performance Delivery 5](#full-lpv-performance-delivery)

[2.1.1. Architecture Upgrade 5](#architecture-upgrade)

2.1.2 [Full LPV Performance Delivery
5](#full-lpv-performance-delivery-1)

[3. Requirements 5](#requirements)

[3.1. Program Management 6](#program-management)

[3.1.1. Program Management 6](#program-management-1)

[3.1.2. Program Overview Meetings (POM)
9](#program-overview-meetings-pom)

[3.2. Systems Engineering Management
10](#systems-engineering-management)

[3.2.1. Interface Design 10](#interface-design)

[3.2.2. System Engineering Analyses 10](#system-engineering-analyses)

[3.2.3. System Engineering Working Group (SEWG)
11](#system-engineering-working-group-sewg)

[3.3. Hardware Engineering 11](#hardware-engineering)

[3.4. Software Engineering 11](#software-engineering)

[3.4.1. Operational Software Development
12](#operational-software-development)

[3.4.2. Software Standards 12](#software-standards)

[3.4.3. Software Development Plan 12](#software-development-plan)

[3.4.4. Reserved 13](#reserved-1)

[3.4.5. Interface Requirements Specification(s)
13](#interface-requirements-specifications)

[3.4.6. Software Requirements Specification(s)
13](#software-requirements-specifications)

[3.4.7. Interface Design Document(s) 13](#interface-design-documents)

[3.4.8. Software Design Document(s) 13](#software-design-documents)

[3.4.9. Software Product Specification(s)
13](#software-product-specifications)

[3.4.10. Version Description Document(s)
13](#version-description-documents)

[3.4.11. Software Test Plan(s) 14](#software-test-plans)

[3.4.12. Software Test Description(s) 14](#software-test-descriptions)

[3.4.13. Software Test Report(s) 14](#software-test-reports)

[3.4.14. Software Accomplishment Summary
14](#software-accomplishment-summary)

[3.5. Communications Engineering 14](#communications-engineering)

[3.5.1. Terrestrial Communications Subsystem
14](#terrestrial-communications-subsystem)

[3.5.2. WTMS Terrestrial Communications Network
15](#wtms-terrestrial-communications-network)

[3.5.3. WAAS Geostationary Communications Control Segment
15](#waas-geostationary-communications-control-segment)

[3.6. System Safety Program 15](#system-safety-program)

[3.6.1. System Safety Program Plan 16](#system-safety-program-plan)

[3.6.2. System Safety Manager 16](#system-safety-manager)

[3.6.3. System Safety Working Group 16](#system-safety-working-group)

[3.6.4. Hazard Tracking 17](#hazard-tracking)

[3.6.5. System Safety Program Progress Report
17](#system-safety-program-progress-report)

[3.6.6. Safety Analyses 18](#safety-analyses)

[3.6.7. Test and Evaluation Safety 18](#test-and-evaluation-safety)

[3.6.8. Safety Review of Engineering Change Proposals, Specification
Change Notices, Requests for Deviation/Waiver
19](#safety-review-of-engineering-change-proposals-specification-change-notices-requests-for-deviationwaiver)

[3.6.9. Safety Verification 19](#safety-verification)

[3.6.10. Software Program Safety Interface
19](#software-program-safety-interface)

[3.6.11. System Safety Architecture 19](#system-safety-architecture)

[3.7. Human Engineering 19](#human-engineering)

[3.7.1. HE Program Planning 20](#he-program-planning)

[3.7.2. HE Studies and Analyses 20](#he-studies-and-analyses)

[3.7.3. HE Design Support 20](#he-design-support)

[3.7.4. HE Test and Evaluation 21](#he-test-and-evaluation)

[3.7.5. WAAS HE Action Item List 21](#waas-he-action-item-list)

[3.7.6. Human Factors Working Group 21](#human-factors-working-group)

[3.7.7. WAAS Users Group 22](#waas-users-group)

[3.7.8. HE Reviews 22](#he-reviews)

[3.8. Reliability and Maintainability
23](#reliability-and-maintainability)

[3.8.1. Reliability and Maintainability Program
23](#reliability-and-maintainability-program)

[3.8.2. Reliability and Maintainability Reports
24](#reliability-and-maintainability-reports)

[3.9. Reserved 24](#reserved-2)

[3.10. System Test and Evaluation 24](#system-test-and-evaluation)

[3.10.1. Test and Evaluation Management
24](#test-and-evaluation-management)

[3.10.2. Master Integration and Test Plan
24](#master-integration-and-test-plan)

[3.10.3 Production Acceptance Test and Evaluation Plan
25](#production-acceptance-test-and-evaluation-plan)

[3.10.4 Test Procedures 25](#test-procedures)

[3.10.5 Test Reports 25](#test-reports)

[3.10.6 Test Conduct 26](#test-conduct)

[3.10.7 General Test Ground Rules 26](#general-test-ground-rules)

[3.11. Configuration Management 28](#configuration-management)

[3.11.1. Configuration Management Program
28](#configuration-management-program)

[3.11.2. Configuration Management Plan
28](#configuration-management-plan)

[3.11.3. Configuration Identification 28](#configuration-identification)

[3.11.4. Configuration Control 29](#configuration-control)

[3.11.5. Configuration Status Accounting
29](#configuration-status-accounting)

[3.11.6. Data Management 29](#data-management)

[3.11.7. Configuration Audits 29](#configuration-audits)

[3.11.8. Interface Requirements/Control
30](#interface-requirementscontrol)

[3.11.9. Retrofit Requirements 30](#retrofit-requirements)

[3.12. Quality Control 30](#quality-control)

[3.12.1. Quality System Plan 30](#quality-system-plan)

[4. National Airspace Integrated Logistics Support
30](#national-airspace-integrated-logistics-support)

[4.1. Contractor NAILS Program Management Responsibilities
30](#contractor-nails-program-management-responsibilities)

[4.1.1. Planned FULL LPV PERFORMANCE Improvements
31](#planned-full-lpv-performance-improvements)

[4.1.2. Contractor Control 31](#contractor-control)

[4.1.3. Maintenance Planning 34](#maintenance-planning)

[4.1.4. Interim Contractor Depot Logistics Support
34](#interim-contractor-depot-logistics-support)

[4.1.5. Support Equipment 39](#support-equipment-1)

[4.1.6. Training, Training Support, and Personnel Skills
40](#training-training-support-and-personnel-skills)

[4.1.7. Provisioning 41](#provisioning)

[4.1.8. Site Spares 42](#site-spares)

[4.1.9. Packaging, Handling, Storage And Transportation (PHS&T)
43](#packaging-handling-storage-and-transportation-phst)

[4.1.10. Technical Data 43](#technical-data)

[5. Site Implementation 44](#site-implementation)

[5.1. Site Surveys 45](#site-surveys)

[5.1.1. Reserved 45](#reserved-9)

[5.1.2. Materiel 45](#materiel)

[5.1.3. Power 46](#power)

[5.2. Implementation Planning 46](#implementation-planning)

[5.3. Site Preparation 47](#site-preparation)

[5.4. Equipment Installation 47](#equipment-installation)

[5.5. As-Built Drawings 47](#as-built-drawings)

[5.6. WAAS Disestablishment 47](#waas-disestablishment)

[6. Government-Furnished Equipment 47](#government-furnished-equipment)

[6.1. Communications System 47](#communications-system)

[6.2. Equipment and Support Space 48](#equipment-and-support-space)

[6.2.1. Equipment Space 48](#equipment-space)

[6.2.2. Support Space 48](#support-space)

[6.3. Environmental Control 48](#environmental-control)

[6.4. Electrical Power and Termination
48](#electrical-power-and-termination)

[6.5. Ground Termination 48](#ground-termination)

[6.6. Documents 48](#documents)

[6.7. Physical Security 49](#physical-security)

[6.7.1. Points-of-Contact 49](#points-of-contact)

[6.8. Telephones 49](#telephones)

[6.9. Ground Monuments 49](#ground-monuments)

[7. Second Level Engineering Support
49](#second-level-engineering-support)

[7.1. Field Support 50](#field-support)

[7.1.1. Reserved 50](#reserved-10)

[7.1.2. Contract Award to FULL LPV PERFORMANCE
50](#contract-award-to-full-lpv-performance)

[7.1.3. On-Call and Onsite Support 50](#on-call-and-onsite-support)

[7.2. Performance Monitoring 51](#performance-monitoring)

[7.2.1. Monitoring and Reporting 51](#monitoring-and-reporting)

[7.2.2. Monitored Performance Parameters
51](#monitored-performance-parameters)

[7.3. Anomaly Investigation 52](#anomaly-investigation)

[7.4. SLES Transition Support 52](#sles-transition-support)

[7.4.1. Contract Award to Full LPV Performance
52](#contract-award-to-full-lpv-performance-1)

[7.4.2. Asset Transfer to AOS 52](#asset-transfer-to-aos)

[8. Operational Baseline Management
53](#operational-baseline-management)

[8.1. Scope Analysis 53](#scope-analysis)

[8.1.1. Problem Re-Validation 53](#problem-re-validation)

[8.1.2. Impact Assessment 53](#impact-assessment)

[8.1.3. Risk Assessment 53](#risk-assessment)

[8.1.4. Alternatives/Options 54](#alternativesoptions)

[8.1.5. Initial Test Approach 54](#initial-test-approach)

[8.1.6. Implementation Estimate 54](#implementation-estimate)

[8.1.7. Scope Analysis Report 54](#scope-analysis-report)

[8.1.8. WCRB -- Initial Approval Support
54](#wcrb-initial-approval-support)

[8.2. Detailed Design 55](#detailed-design)

[8.3. Operational Baseline Change Delivery
56](#operational-baseline-change-delivery)

[8.4. Implementation Report 56](#implementation-report)

[9. Acronyms 58](#acronyms)

# Scope

This Statement of Work (SOW) defines the requirements for the program
management, engineering management, engineering development, production,
test and evaluation, cutover of Full Lateral Precision with Vertical
Guidance (LPV) Performance to the operational Wide Area Augmentation
System (WAAS). This SOW also includes provisions for the Contractor to
provide Second Level Engineering Support (SLES) for the existing WAAS
Initial Operational Capability (IOC) for the duration of the Full LPV
Performance contract.

The Contractor must provide Full LPV Performance modifications and
upgrades to the currently fielded and operational IOC WAAS as directed
by the FAA, which will increase the coverage, continuity and
availability of the WAAS over CONUS and Alaska. The Contractor must also
provide SLES and system problem resolution as directed by the FAA and
defined in this SOW during the period of Full LPV Performance capability
development and cutover to the operational WAAS. The Contractor must
ensure the WAAS meets the specific functional and performance
requirements of the WAAS Specification, FAA-E-2892Bch2 as modified by
the WAAS Procurement Specification Preplanned Product Improvements for
Full Operational Capability, FAA-E-2976, dated March 18, 2004.
FAA-E-2976 is a delta specification that specifically addresses the
requirements for the changes being implemented under the Full LPV
Performance program. For requirements that are unchanged by the Full LPV
Performance efforts, FAA-E-2892Bch2 will remain in effect. For the
remainder of this SOW the term "Full LPV Performance Specification\"
will be used to denote the combination of the FAA-E-2892Bch2 IOC and the
FAA-E-2976 specifications. Not all Full LPV Performance requirements
changes must be unilaterally applied to existing WAAS installations. The
need to retrofit the Full LPV Performance changes into existing
installations will be made by the FAA on a case-by-case basis. The
Contractor must provide the WAAS to the FAA in accordance with the
requirements cited in this SOW.

The Contractor must implement upgrades to the IOC WAAS that meet FAA
Full LPV Performance navigation requirements for domestic en route,
non-precision approach, and precision approach phases of flight. The
Contractor must utilize the National Airspace System (NAS)
Inter-facility Communications System (NICS) and other GFS communications
capabilities to provide ground-ground communications between the various
Contractor-provided Hardware Configurations Items.

The Contractor must provide, as a minimum, the following for the WAAS:

a.  System analysis and design using software, firmware, communications
    media, and Non-Developmental Item (NDI) hardware (referred to as
    equipment hereafter),

b.  Hardware and software as required to meet the requirements described
    in the WAAS Full LPV Performance Specification,

c.  Logistics support,

d.  System analysis and problem resolution of hardware, software and
    system issues and anomalies arising from the operation of WAAS,

e.  Technical and management support to the WAAS Change Review Board
    (WCRB).

The Contractor must provide equipment, personnel, and related services
in support of the WAAS in the following areas:

a.  Project management,

b.  Full LPV Performance System engineering and system design,

c.  Full LPV Performance Software development,

d.  System development and installation in compliance with applicable
    Federal Regulations, including site surveys, site preparation,
    equipment installation, quality assurance, testing, and cutover
    support,

e.  Configuration management,

f.  Technical services required to support SLES and Full LPV
    Performance,

g.  Software development and integration services for the integration of
    Ground Communication and Control (GCCS) services with WAAS,

h.  Logistics support,

i.  Support services including contingency planning and support,
    conference attendance, and technical assistance.

## Applicable Documents

All specifications and standards are as of the issue date of this
contract, unless mutually agreed otherwise. Documents are applicable to
the extent specified in Sections 2.0 through 8.0 of this Statement of
Work.

## FAA Specifications

  ------------------ ----------------------------------------------------
  FAA-E-2892Bch2     WAAS Functional and Performance Specification

  FAA-E-2976         Wide Area Augmentation System Procurement
                     Specification Preplanned Product Improvements for
                     Full Operational Capability

  FAA-G-1375C        Spare Parts‑Peculiar for Electronic, Electrical and
                     Mechanical Equipment

  FAA-G-2100G        Electronic Equipment, General Requirements
  ------------------ ----------------------------------------------------

## Military Specifications

  ------------------ ----------------------------------------------------
  MIL-DTL-31000B     Technical Data Packages, General Specification for

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

## FAA Standards

  ------------------ ----------------------------------------------------
  FAA-STD-005D       Preparation of Specification Documents

  FAA-STD-019B       Lightning Protection, Grounding, Bonding, and
                     Shielding Requirements for Facilities

  FAA-STD-020B       Transient Protection, Grounding, Bonding, and
                     Shielding Requirements for Equipment

  FAA-STD-021A       Configuration Management

  FAA-STD-025C       Preparation of Interface Control Documentation

  FAA-STD-026A       NAS Software Development, June 1, 2001

  FAAD-STD-1293C     Servicing Standards and Test Requirements for Ground
                     Electronic Equipment
  ------------------ ----------------------------------------------------

## Military Standards

  ------------------ ----------------------------------------------------
  MIL-STD-129L       Marking for Shipment and Storage

  MIL-STD-470B       Maintainability Program Requirements. (For Systems
                     and Equipment)

  MIL-STD-781D       Reliability, Design Qualification, and Production
                     Acceptance Tests

  MIL-STD-785B       Reliability Program for Systems and Equipment
                     Development and Production

  MIL-STD-881B       Work Breakdown Structures for Defense Material Items

  MIL-STD-882C       System Safety Program Requirements

  MIL-STD-973        Configuration Management

  MIL-STD-1390D      Level of Repair Analysis (LORA)

  MIL-STD-1629A      Procedures for Performing a Failure Mode, Effects
                     and Critically Analysis.

  MIL-STD-2073-1B    DoD Material Procedures for Development and
                     Application of Packaging Requirements

                     

  MIL-PRF-49506      Performance Specification: Logistics Management
                     Information

  MIL-HDBK-46855     Human Engineering Requirements for Military Systems,
                     Equipment and Facilities
  ------------------ ----------------------------------------------------

## Federal Standards

  ------------------ ----------------------------------------------------
  FED-STD-005D       Standard Guides for Preparation of Proposed Item
                     Logistics Data Records

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

## Other FAA Documents

  -------------------- ----------------------------------------------------
  FAA Order 1370.82    Information Systems Security Program June 9, 2000

  FAA Order 1800.58A   National Airspace Integrated Logistics Support
                       Policy

  FAA Order 4650.30    Vendor Shipments of Nationally Furnished Project
                       Material\
                       (In FAA Order 4650.30, reference made to DD Form 250
                       is changed to read FAA Form 256)

  FAA Order 6950.2C    Electrical Power Policy Implementation at National
                       Airspace System Facilities

  FAA Order 6950.15B   Air Route Traffic Control Complex (ARTCC) Critical
                       Load Circuits and Configuration

  FAA Order 6000.30C   Policy for Maintenance of the National Airspace
                       System

  FAA Order 6030.45    Facility Reference Data File (FRDF)

  FAA Order 6650.9     Requirements for Area Control Facility (ACF) Under
                       the Floor Cabling

  FAA AC 25.1309-1A    Subject: "System Design and Analysis"

  DI-AFZ500-2003-005   Asset Identification Contract Data Requirements List
                       and Data Item Description (CDRL/DID)

  DID-FAA-QA-003       Quality System Plan (QSP)

  DID-FAA-026-023      Software Quality Assurance Plan (SQAP)
  -------------------- ----------------------------------------------------

## Other Documents

+-----------------+----------------------------------------------------+
| MIL-HDBK-217    | Reliability Prediction of Electronic Equipment     |
+-----------------+----------------------------------------------------+
| MIL-HDBK-781    | Reliability Test Methods, Plans, and Environments  |
|                 | for Engineering Development, Qualifications and    |
|                 | Production                                         |
+-----------------+----------------------------------------------------+
| ANSI-           | C Programming Language                             |
| STD-X3.159-1989 |                                                    |
+-----------------+----------------------------------------------------+
| RTCA/DO-178B    | Software Considerations in Airborne Systems and    |
|                 | Equipment Certification                            |
+-----------------+----------------------------------------------------+
| DoD Manual      | DoD Provisioning and Other Preprocurement          |
| 4100.38M        | Screening Manual                                   |
+-----------------+----------------------------------------------------+
| Title 49,       | Code of Federal Regulations\                       |
| Section 172     | FAA Acquisition Management System dated April 1,   |
|                 | 1996                                               |
+-----------------+----------------------------------------------------+
| ARP 4754        | Aeronautical Recommended Practices (ARPs)          |
|                 |                                                    |
| ARP 4761        |                                                    |
+-----------------+----------------------------------------------------+
| ANSI/ISO/ASQ    | Quality Management System - Requirements, Dec. 13, |
| Q9001 2000      | 2000                                               |
+-----------------+----------------------------------------------------+

#   {#section .unnumbered}

# Contract Execution

## Full LPV Performance Delivery 

The WAAS System must have an architecture and performance upgrade which
must consist of multiple phases of hardware and software enhancements.
The phases ensure WAAS continuous service throughout the upgrade to Full
LPV Performance. The Contractor is encouraged to propose hardware,
software, and GFE communications system changes to integrate additional
functional capabilities as necessary to sustain continuous service
during the cutover. The Contractor must ensure that all changes to the
WAAS product baseline adhere to the processes described in SOW Section
8.0, Operational Baseline Management.

### Architecture Upgrade 

The Architecture Upgrade is intended to focus primarily on increasing
system capacity to support additional Wide-area Reference Stations
(WRSs), a Wide-area Master Station (WMS), integration of a third and
fourth GEO, and anticipated processing needs for software necessary to
achieve Full LPV Performance requirements defined in the Full LPV
Performance Specification. However, when appropriate, the Contractor
must propose hardware & software changes that also improve continuity,
availability, coverage, and supportability at the earliest opportunity
feasible. As a minimum, the Contractor must upgrade the existing WAAS
architecture to include the following:

-   System engineering, hardware, software, and GFE communications
    changes necessary to host additional WRSs and WMSs per the
    requirements of the Full LPV Performance specification.

-   System engineering, hardware, software, and GFE communications
    changes necessary to integrate up to 2 additional WAAS GEOs provided
    as part of the GCCS Contract DTFA01-03-C-00059.

-   System engineering, hardware, software, and GFE communications
    changes necessary to install and integrate the additional WRSs being
    added to the WAAS system as part of the Full LPV Performance effort.
    The Contractor must propose WRSs locations at FAA-approved locations
    based on maximum contribution to overall system performance.

### Full LPV Performance Delivery 

The Contractor must complete all system engineering, hardware, software,
and communications changes necessary to achieve all Full LPV Performance
requirements specified in the Full LPV Performance Specification.

# Requirements

The Contractor must perform the effort described in this SOW and must
comply with all the requirements set forth herein. The Contractor must
adhere to all plans developed in response to this SOW, when approved by
the FAA. The Contractor must deliver the data described in this SOW in
accordance with the schedule and other requirements specified in the
Contract Data Requirements List (CDRL). The applicable CDRLs have been
identified in parentheses at the end of the corresponding SOW paragraph
and are detailed in Attachment C.

Unless otherwise specified in the following sections, the agenda for
meetings (SEWG, WIPP, POM, NAILS, SLES, and ICDLS) must be provided to
the Government for approval no later than 15 days prior to the start of
the meeting and the minutes for meetings must be provided to the
Government for approval no later than 14 days after the completion of
the meeting. The Government will respond to the Contractor with comments
and/or approval for the submitted agenda within 5 days after receipt and
within 30 days for the delivered meeting minutes. The Contractor must
incorporate comments and resubmit no later than 3 days after receipt of
meeting agenda comments and no later than 15 days after receipt of
meeting minute comments. Contractor format for meeting agendas and
meeting minutes is acceptable.

All PNBs identified in this SOW must be delivered in Contractor format,
unless otherwise specified. For PNBs requiring Government approval, the
Contracting Officer will provide one consolidated set of comments to the
Contractor, via email, and post the comments on the shared file server
within 30 days of PNB receipt. The Contractor must incorporate comments
and resubmit no later than 15 days after receipt. The Contracting
Officer will respond, via email, within 15 days after receipt.

## Program Management

The Contractor must manage the effort described in this SOW. A single
Program Manager must be assigned the responsibility for control and
coordination of all work performed under the WAAS contract. The Program
Manager must have sufficient experience and authority to ensure
efficient and timely program execution and must be the single focal
point within the Contractor\'s activity for all required program tasks
performed under the contract.

### Program Management

#### Program Management Plan

The Contractor must update the existing Program Management Plan, as
required, to identify the Contractor's organization and procedures for
administering the WAAS program. These procedures must include (but not
be limited to) monitoring program performance (cost, schedule and
technical), contract administration, subcontract management, and
integrated product teams. (CDRL A001)

#### Contractor Work Breakdown Structure (CWBS)

The Contractor must establish and maintain a CWBS and dictionary in
compliance with MIL-STD-881. The summary CWBS must provide the basis for
any further extension by the Contractor to lower levels during the
performance of the contract. The dictionary must include references to
Contract Line Item Number (CLIN), Responsible Organization and
Performing Organization, including any subcontractors' performing work.
(CDRL A002)

#### Schedule Management

The Contractor must establish a single WAAS Master Integrated Network
Program Schedule based on a logical and efficient sequence of events
designed to accomplish the effort described in this contract. The
Contractor must develop and submit the Master Integrated Program
Schedule (MIPS) using Primavera Project Planner for Windows, Version 1.1
or later. The Contractor must comply with the following schedule
requirements:

-   Task IDs must be traceable to the CWBS. Tasks that represent CDRL
    deliveries must use the CDRL number as the task identifier.

-   Task names except Major Program Milestones must begin with a verb.
    Task names must be specific enough to stand-alone and be understood
    apart from their Work Breakdown Structure (WBS) number by
    non-technical personnel.

-   The MIPS file (CDRL A003) and subsequent Monthly Schedule Status
    Report (CDRL A004) must be electronically coded to enable the
    Contractor to provide Master, Intermediate, and Detail Level
    schedules.

-   The Master Level Schedule must depict all Contractor Major Program
    Milestones.

-   The Intermediate Level Schedule must depict work at the 4th level of
    the WBS.

-   The Detail Level Schedule must depict all activities in the Master
    Integrated Program Schedule (MIPS) file.

-   The Contractor must include an activity dictionary within the Log
    field for each activity in the MIPS and subsequent Monthly Updates.
    Task definitions in this Log field must fully define the work to be
    performed. In addition, the Contractor must include an acronym list
    with each delivery of the MIPS and Monthly Update.

-   Schedule tasks, which depict work such as Level of Effort (LOE)
    longer than 5 months, subcontractor deliverables \[i.e., Subcontract
    Data Requirements List (SDRL)\], or tasks used simply as
    "placeholders" for financial traceability must not be included in
    the MIPS submission or subsequent Monthly Schedule Status Report
    Updates (CDRL A004). Significant work performed by subcontractors
    must be included in the MIPS and Monthly Schedule Status Report
    Updates**.** Significant work is defined as any work other than work
    to develop or deliver SDRLs or perform LOE work as defined above.
    Subcontractor work must be logically integrated into prime
    Contractor work in all cases. (CDRL A003) (CDRL A004)

-   The Contractor must use a 5 working day calendar, unless otherwise
    specified, with both Contractor-specific holidays and government
    holidays as the only calendar for the MIPS. The Contractor must
    provide the Contractor specific holidays to the FAA with the first
    submission of CDRL A003. The FAA will recognize the standard
    published federal holidays.

-   The Contractor must base any schedule submitted as a part of any
    other CDRL, plan, or technical document on the Master Integrated
    Program Schedule (MIPS) and subsequent Monthly Schedule Status
    Report Updates. The Contractor's Program Manager or designee must
    sign all schedules submitted in such documents, whether formal or
    informally delivered. If a schedule submitted in a document as
    described above is at a more detailed level than is in the MIPS, the
    detailed activity must clearly track back (i.e., via a key) to its
    higher level MIPS activity ID. The Contractor must include "Best
    guess work-around plans" for activities identified in Risk Abatement
    Plans in the Monthly Schedule Status Report (MSSR). (CDRL A004).

#### Cost Management

The Contractor must establish, maintain and use internal cost management
control systems and provide the FAA with timely and auditable data on a
monthly basis that determine product-oriented contract status. (CDRL
A008)

#### Cost Management Reporting

The Contractor must use the Cost Performance Report (CPR). The monthly
reports of CPR data \-- Budgeted Cost of Work Scheduled, Budgeted Cost
of Work Performed, Actual Cost of Work Performed, Cost and Schedule
Variances, for the current and cumulative to date work periods -- must
be provided to at least WBS level 3 of the Contractor Work Breakdown
Structure (CWBS), or to a lower level if deemed appropriate. The FAA
reserves the right to require reporting to a lower level of detail, down
to the Work Package level. (CDRL A008)

#### Earned Value Management

The Contractor must perform continuous contract management and contract
performance assessment, in accordance with AMS clause 1.13-2, and the
Earned Value Management Implementation Guide (DCMA), latest revision.
The Contractor must be diligent in addressing cost and schedule
variances and provide specific information in their Cost Performance
Report (CPR) regarding the disposition, overall impact, and plans of
action (with projected dates of implementation) as part of the CPR. The
budgets agreed upon in the contract must reflect integration of schedule
and cost projections. For the determination of earned value, as much
work as possible must be defined in discrete Work Packages with
well-defined products and milestones. The Contractor's use of
Level-of-effort Work Packages must be minimized. Work Packages are
required to represent natural, logical subsets of the work described in
the CWBS.

#### Technical Program Management

The Contractor must establish a Technical Program Metric (TPM) Program
integrated with all other System Engineering and Risk Management
activities as called out in this SOW.

##### Technical Program Metrics Status Report

The Contractor must post the monthly Technical Program Metrics (TPM)
Status Report on the tenth of every month in PowerPoint format to the
shared file server and inform the FAA via email. The Contractor must
describe each parameter being tracked and summarize the performance
achievement along with current trends and discrepancies of actual versus
expected performance in the TPM Status Report. The Contractor must
prepare and submit the TPM Status Report in Contractor format for review
and approval.

##### Software Management Indicators

The Contractor must track and report on the following software
management indicators for all operational Computer Software
Configuration Items (CSCIs): software requirements stability, software
size, computer resource utilization, software manpower, incremental
software releases and software problem reports. The Contractor must also
track and report on management indicators for the test and support
software on the following topics: software problem reports, and software
size. The tracking and reporting of the software management indicators
must be performed via the Technical Program Metric (TPM) Status Report.

#### Risk Management

The Contractor must conduct risk management activities. The Contractor
must give full consideration to all factors, which could limit
technical, schedule, cost, or operational performance of the program.
Risk management activities must identify \"low,\" \"moderate,\" and
\"high\" risk items, track program performance on risk items, and
implement risk abatement procedures as needed. The risk assessment and
abatement program tracking, evaluation, and direction must be an
integral part of the Contractor \'s system engineering and engineering
management processes.

#### Contract Data Management

The Contractor must deliver all CDRLs, Correspondence, and other
documentation in softcopy in Microsoft Office 2000 format, or other
approved softcopy format, using agreed to communications media.

### Program Overview Meetings (POM)

The Contractor must conduct quarterly Program Overview Meetings (POMs)
at the Fullerton facility unless otherwise directed by the Contracting
Officer's Technical Representative (COTR), to provide status on all
program management activities. The COTR may require monthly POMs if
there are program (technical, schedule, or cost) issues that require
increased FAA attention. The Contractor must prepare and submit an
agenda and meeting minutes IAW Section 3 of this SOW.

## Systems Engineering Management

The Contractor must establish, implement, and maintain a Systems
Engineering Management Program. The Contractor must submit and update as
necessary a Systems Engineering Management Plan (SEMP) and a Metric
Plan, which describe the Contractor\'s systems engineering organization,
responsibilities, methodology and procedures for system engineering,
technical planning and control, and systems integration. The Contractor
must ensure the SEMP provides an overall discussion of how change impact
analysis will be accomplished for the WAAS and its constituent
components (e.g., hardware, and software). The Contractor must ensure
this change impact analysis considers, at a minimum: effects on safety
(including effects on integrity, availability, and continuity), effects
on procedures, effects on system resources (e.g., throughput), and
amount of reverification needed. (CDRL A013) The Metric Plan may be
prepared as a Program Notebook (PNB) and must be updated and delivered
concurrent with the SEMP.

### Interface Design

The Contractor must update existing interface control documents (ICDs)
as required for each change to the product baseline. (CDRL A052)

The Contractor must also develop and deliver an ICD that defines
functional and performance interface requirements between the Signal
Generation Subsystem (SGS) and the WMS and WRS. The ICD must be updated
and delivered, as required, to incorporate changes introduced by Full
LPV Performance development. (CDRL A144*)*

### System Engineering Analyses

The Contractor must perform and submit the analyses and trade studies to
determine the optimum allocation and apportionment of the requirements
contained in the Full LPV Performance Specification to individual
hardware and software configuration items (CIs). The Contractor must
perform the analysis, prototyping, modeling, etc. as required
substantiating the rationale for all hardware, software, and GFE
Subsystems selected for use in the system to meet the performance
requirements. (CDRL A014)

#### Service Volume Model (SVM)

The Contractor must update and maintain the existing SVM, as required,
to analyze and document availability and coverage performance for En
Route, LNAV, LNAV/VNAV, and Lateral Precision with Vertical guidance
(LPV) performance levels. The Contractor must document the SVM
algorithms and software requirements changes and present the results of
the SVM model at the WIPP/SEWG. The Contractor must present the results
of the SVM Model to the WIPP and SEWG.

#### Probabilistic Continuity Analysis

The Contractor must provide WAAS performance data in Contractor format
to the FAA on an as required basis for the purpose of verifying the
allocation values used by the FAA models of WAAS continuity performance.
The first set of WAAS performance data must be submitted the first of
the month following Full LPV Performance contract modification.

### System Engineering Working Group (SEWG)

The Contractor must continue the established System Engineering Working
Group (SEWG) to provide a forum for technical review and resolution of
all system development, improvement, and second level engineering
support activities. The SEWG will be co-chaired by the Contractor and a
FAA WAAS representative. The WAAS Integrity Performance Panel (WIPP) is
a subgroup of the SEWG used to resolve issues associated with integrity,
continuity, availability, safety, and performance. The Contractor must
prepare and submit an agenda and meeting minutes IAW Section 3 of this
SOW.

## Hardware Engineering

Only hardware, needed to satisfy the requirements for the Full LPV
Performance Specification must be procured. The Contractor must provide
hardware engineering to support the regression tests of the Common
Reference Receiver (CRR). Specifically, test and debug and changes
required during the Contractor integration and test of the receiver for
the Alaska WRS racks.

## Software Engineering

The Contractor must design and develop upgrades to the WAAS software in
accordance with FAA-STD-026A and RTCA/DO-178B, and meet the requirements
of the Full LPV Performance Specification. The Contractor must ensure
the software life-cycle process used is compliant with RTCA/DO-178B for
the software safety levels assigned to each CSCI.

The Contractor must provide support for software and test of the Common
Reference Receiver (CRR). The Contractor must provide support to
software and test efforts that arise from February to April 2004. Two
specific tasks required to support hardware updates:

1.  Updates must be required to the boot code and firmware load to
    support the new SDRAM

2.  The Multipath Estimation Delay Lock Loop (MEDLL) reference functions
    will need to be re-measured on the new hardware to ensure optimal
    performance with the new RF deck design.

In addition, the Contractor must correct two minor issues found with the
CRRs:

1)  Track all satellite ranges regardless of Almanac Health bit status

2)  Fix RX Commands log to indicate whether Binary or ASCII logs were
    requested by the user

### Operational Software Development

WAAS operational software and firmware must consist of all software,
firmware and commercial off the shelf/non-developmental software
(COTS/NDS) executed within the WAAS. The Contractor must code all WAAS
operational software developed under this contract in C. The Contractor
must obtain FAA approval for use of any language other than C. Existing
software used to monitor and control the GEO satellites is excluded
provided that WAAS performance requirements in the Full LPV Performance
Specification can be met and the hazard analysis shows there is no
unacceptable safety hazards associated with the software. The Contractor
must ensure that embedded or existing COTS/NDS software, including
complex logic devices (programmable logic arrays or equivalent), meet
the objectives of RTCA/DO-178B for the software safety levels assigned
to each CSCI. The Contractor must secure all rights, including licenses
and auditing of intellectual property, required for the Contractor and
the FAA to verify compliance with RTCA/DO-178B objectives for the
assigned software safety level for all COTS/NDS included in the WAAS.

### Software Standards

The Contractor must perform the planning, system requirements analysis,
system engineering analysis, system design, system safety assessment,
software safety assessment, requirements allocation, software design,
software coding, software test, software integration, system integration
and testing, configuration management, and documentation in accordance
with FAA-STD-026A as tailored by this SOW. The Contractor must comply
with ANSI-STD-X3.159-1989 for computer languages. The Contractor must
use best commercial practices for hardware firmware.

####  Reserved

### Software Development Plan

The Contractor must update the Software Development Plan (SDP) as
required. The Contractor must comply with the SDP as required in
FAA-STD-026A. This plan governs all software development, software
safety engineering, and human factors engineering activities necessary
to support all development, which includes but is not limited to:
micro-controller instructions, prototype software usage, COTS/NDS, and
test and support software. The Contractor must include processes to
support informal peer reviews of documentation, algorithm development
and prototyping activities by FAA personnel on an incremental basis in
the SDP. The Contractor must ensure the software safety level assigned
to each CSCI in the SDP meets the objectives of RTCA/DO-178B. The
Contractor must include a section in the SDP describing a Plan for
Software Aspects of Certification in accordance with RTCA/DO-178B,
paragraph 11.1. The Contractor must ensure the software configuration
management section of the SDP meets the requirements of RTCA/DO-178B
paragraph 11.4. (CDRL A017)

### Reserved

### Interface Requirements Specification(s)

The Contractor must update as required the Interface Requirements
Specification(s) (IRS) as prescribed in FAA-STD-026A for each change of
the product baseline. The Contractor must ensure IRS(s) meet the
objectives in RTCA/DO-178B for the software safety level assigned to
each CSCI. (CDRL A019)

### Software Requirements Specification(s)

The Contractor must update as required the Software Requirements
Specification(s) (SRS) as prescribed in FAA-STD-026A for each change of
the product baseline. The Contractor must ensure SRS(s) meet the
objectives in RTCA/DO-178B for the software safety level assigned to
each CSCI. (CDRL A043)

### Interface Design Document(s)

The Contractor must update as required the Interface Design Document(s)
(IDD) as prescribed in FAA-STD-026A for each change of the product
baseline. The Contractor must ensure IDD(s) meet the objectives in
RTCA/DO-178B for the software safety level assigned to each CSCI. (CDRL
A020)

### Software Design Document(s)

The Contractor must update, as required, the Software Design Document(s)
(SDD) as prescribed in FAA-STD-026A as an appendix to the Software
Product Specification (SPS) in accordance with the approved Plan for
Software Aspects for Certification (PSAC). The Contractor must ensure
SDD(s) meet the objectives in RTCA/DO-178B for the software safety level
assigned to each CSCI. (CDRL A022)

### Software Product Specification(s)

The Contractor must update the Software Product Specification(s) (SPS)
as prescribed in FAA-STD-026A for each change of the product software
baseline in accordance with the approved PSAC. (CDRL A022)

### Version Description Document(s)

The Contractor must update as required the Version Description
Document(s) (VDD) as prescribed in FAA-STD-026A and FAA-STD-021A,
Appendix XII for each change of the product baseline in accordance with
the approved PSAC. (CDRL A023)

### Software Test Plan(s)

The Contractor must include the software testing approach in the
Software Development Plan (A017). The Contractor must satisfy the
requirements for a Software Verification Plan in accordance with
RTCA/DO-178B for the software safety level assigned to each CSCI and
must be consistent with the Master Integrated Test Plan (MITP)(CDRL
A143).

### Software Test Description(s)

The Contractor must prepare or update software test descriptions as part
of the Implementation Report (A142) for each applicable change to the
product baseline. The Contractor must ensure the software test
descriptions satisfy the requirements for Software Verification Cases
and Procedures in accordance with RTCA/DO-178B for the software safety
level assigned to each CSCI. The Contractor must deliver test
descriptions to the FAA in accordance with Section 8.0 of this SOW.

### Software Test Report(s)

The Contractor must prepare software test reports as part of the
Implementation Report (A142) for each applicable change to the product
baseline. The software test reports must satisfy the requirements for
Software Verification Results in accordance with RTCA/DO-178B for the
software safety level assigned to each CSCI. The Contractor must deliver
test reports to the FAA in accordance with Section 8.0 of this SOW.

### Software Accomplishment Summary

The Contractor must prepare and submit a Software Accomplishment Summary
(SAS) as a PNB IAW the approved PSAC and Section 8.0 of this SOW. The
SAS will be evaluated and approved as part of the DO-178B audit process
for each proposed change to the operational baseline.

## Communications Engineering

The Contractor must ensure the WAAS and WTMS communications systems
support the transmission of data required to meet the Full LPV
Performance Specification requirements. The Contractor's requests for
GFE circuits must take into account the lead-time necessary to establish
the service.

### Terrestrial Communications Subsystem 

The Contractor must implement the WAAS Terrestrial Communications
Network using the NAS Interfacility Communication System (NICS), and
equivalent capabilities outside the United States (US), which will be
provided as GFE. The Contractor must design and integrate improvements
into the Terrestrial Communications Network while meeting the overall
system requirements specified in the Full LPV Performance Specification.
The Contractor must treat the Terrestrial Communications Network as a
subsystem of the WAAS even though the Contractor is provided
communication links as GFE. The Contractor must update the existing WAAS
Terrestrial Network Design Document. (CDRL A126)

### WTMS Terrestrial Communications Network

The WTMS Terrestrial Communications Network must include sufficient
network connections and equipment required to simulate the operation of
the WAAS as necessary to support training of WAAS operators and
maintainers.

### WAAS Geostationary Communications Control Segment 

All GEO satellites and associated subsystems will be provided to the
Contractor as GFE.

#### WAAS/GCCS Integration

When any GCCS is provided as GFE, the Contractor must integrate the GCCS
service into the WAAS while meeting the overall system requirements
specified in the Full LPV Performance Specification. Each GCCS is to be
treated as a subsystem of the WAAS even though the Contractor is
provided the subsystem as GFE.

## System Safety Program

The Contractor must maintain and update a System Safety Program (SSP)
that provides assurance that architectural, performance and maintenance
changes introduced into the WAAS do not result in a degradation in the
WAAS Safety performance achieved in the Lateral Navigation
(LNAV)/Vertical Navigation (VNAV) Phase. The Contractor must ensure the
activities defined in the SSP satisfy the requirements of this SOW and
the FAA-developed Safety Assurance Process Requirements (SAPR), as
specified in Attachment P of the contract. The SAPR, based on Society of
Automotive Engineering (SAE) Aeronautical Recommended Practices (ARPs)
4754 and 4761, together with hazard identification and analysis, risk
assessment and tracking based on MIL-STD-882C, provides an acceptable
approach to assuring the WAAS design. The Contractor must ensure the SSP
addresses hazards presented to the user as well as ground operations and
maintenance safety. Control of hazardous conditions is either
elimination of the hazard or reducing the safety risk to acceptable
levels as defined in the Contractor's System Safety Program Plan (SSPP).
The Contractor must ensure the SSP addresses identification of impacts
to the safety assurance (SA) baseline that were established during the
LNAV/VNAV Phase. The Contractor must ensure the SSP includes the
identification of all artifacts in the Safety Assurance Configuration
Item List (SACIL) (CDRL A014) that require an update based on WAAS
changes to the operational product baseline. The Contractor must notify
the FAA when artifact updates are available for review.

[]{.mark}

The Contractor must ensure the SSP complies with the safety requirements
specified in the Full LPV Performance Specification.

The Contractor must ensure the WAAS safety requirements and associated
analyses consider the combined effects of hazards associated with
hardware failures, software (including COTS/NDI) faults, algorithm
trips, integrated system faults and/or failures, operator and/or
maintainer procedures, and the WAAS operating environment.

The Contractor must identify an independent single point of contact in
the SSPP to serve as the primary safety interface with the FAA. The
Contractor must consider all contract activities and all safety
significant subcontracted efforts in the SSP.

### System Safety Program Plan

The Contractor must update the existing System Safety Program Plan. The
Contractor must include in the SSPP as a minimum:

-   A description of an integrated program covering the hardware,
    software, and firmware.

-   A description of the Contractor's proposed safety organization and
    its relationship to the overall systems engineering process,

-   A description of the hazard identification process proposed for both
    planned upgrades to the system and operation and test anomaly
    review,

-   A comprehensive approach for WAAS design safety assurance in
    accordance with the SAPR,

-   A description of the contents of the Safety CDRLs, and

-   A proposed Hazard Tracking System (HTS) capable of distinguishing
    hazards identified by program phase and build. The Contractor must
    maintain a HTS using Microsoft Access and contain the applicable
    existing LNAV/VNAV and Final Operating Capability ( Full LPV
    Performance) data. (CDRL A062)

### System Safety Manager 

The Contractor must task a single individual, the System Safety Manager
(SSM), with the responsibility for the WAAS System Safety Program. The
SSM must be independent of the WAAS Technical Director. This individual
must be delegated responsibility for meeting the SSP and technical
requirements. The SSM's responsibility must cover system and software
design and analysis, equipment acquisition, and subcontractor SSP
activities. The Contractor must ensure the SSPP identifies the SSM and
includes a summary of that individual's system safety credentials and
position in the WAAS Program and functional organization.

### System Safety Working Group

The Contractor must establish a System Safety Working Group (SSWG)
composed of, as a minimum, safety representatives from the Contractor,
appropriate subcontractors and the FAA. The SSWG's charter must address
all safety assurance related issues. This includes issues involving
hazards and those pertaining to safety analyses being conducted as part
of the WAAS safety assessment. The SSWG will meet, in conjunction with,
System Engineering Working Group (SEWG) meetings or as directed by the
FAA. In addition, discussions will take place as required to discuss the
disposition of hazards that the Contractor has recommended for closure.
The SSWG must be co-chaired by the SSM and a FAA WAAS representative.
Recommendations for system changes originated by the SSWG will be
accomplished in accordance with Section 8.0 of this SOW.

### Hazard Tracking

The Contractor must maintain a closed loop Hazard Tracking System (HTS)
for identification and control of hazards. The Contractor must maintain
the process definition in the SSPP for hazard submission, logging,
adjudication, mitigation/control, and closure of hazard records (HRs).
The HTS process definition must include hazard criticality categories,
Contractor management approval level authority necessary for each, and
procedure for closing out the hazard or assuming the risk. The FAA is
the final approval authority for the closing of hazards.

The Contractor must maintain a computerized hazard log containing all
identified safety hazards that exceed the criteria established in the
SSPP. The Contractor must use this log to document proposed hazards and
track hazards that exceed acceptable risk thresholds until they are
either eliminated, controlled to an acceptable level, or the risk is
assumed with FAA approval. The Contractor must include the information
in sufficient detail to permit WAAS system competent personnel to
understand the nature and status of all included hazards.

The Contractor must use the hazard log as a permanent record of hazard
control activity. The computerized hazard log must include all safety
hazard records identified for every delivery of the WAAS, including
historical deliveries. The computerized hazard log must provide the
capability to associate hazard records to individual WAAS deliveries to
support verification that hazards affecting the delivery have been
appropriately controlled and closed or the associated risk has been
assumed.

The Contractor must deliver the computerized hazard log to the FAA once
per month for the period of the contract. The delivered hazard log must
be a Microsoft Access 2000 developed database. Alternate formats
including .rtf report, Microsoft Access Viewer reports, and other
database exports are not acceptable. Delivery must be via posting on an
FAA-accessible server or mutually agreed upon method.

### System Safety Program Progress Report

The Contractor must provide a System Safety Program Progress Report
(SSPPR) in the format developed over the course of the WAAS LNAV/VNAV
Phase. The Contractor must ensure the SSPPR includes newly recognized
significant hazards and the source of those hazards (safety assessment
activities conducted for planned product upgrades or anomaly/problem
reporting of the current product baseline). The Contractor must ensure
the SSPPR identifies significant changes in the degree of control of the
risk of known hazards and significant cost and schedule changes that
impact the Program. The Contractor must include a Hazard Tracking Log
summary in this report. (CDRL A063)

### Safety Analyses

The Contractor must perform the analyses listed in this paragraph to
assess safety risk. The Contractor must account for the combined effects
of hazards associated with hardware failures, software (including
COTS/NDI) faults, algorithm trips, integrated system faults and/or
failures, operator and/or maintainer procedures, and the operating
environment in these analyses. Contribution of operator and/or
maintainer procedures to minor hazards such as loss of function (LOF)
may be addressed qualitatively. The Contractor must ensure the risk
assessment(s) address all phases of flight supported by WAAS, including
oceanic and domestic en route positioning and navigation, terminal,
non-precision approach, and precision approach operations.

The Contractor must include GCCS segment analyses generated by the GCCS
Contractor, as provided by the FAA, into all appropriate System Safety
Analyses

#### System Hazard Analysis

The Contractor must update the System Hazard Analysis (SHA), as required
for each update of the product baseline. The Contractor must ensure the
SHA updates account for equipment upgrades and technology refreshment.
The Contractor must ensure the SHA is comprehensive and considers the
sources of risk associated with both system integrity and continuity.
Results of those safety analyses conducted IAW the WAAS SAPR, including
Fault Tree Analysis (FTA), Failure Modes and Effects Analyses (FMEAs),
Failure Modes and Effects Summaries (FMESs), Common Cause Analysis
(CCA), Safety Directed Analyses (SDAs), Qualitative Analyses (QAs),
Safety Processor Input Analysis (SPIA), and Algorithm Probability of
Hazardously Misleading Information (PHMI) Analysis, must be captured in
the SHA. The Contractor must ensure the SHA considers all Subsystem
safety analyses (e.g., GCCS). (CDRL A067)

#### System Safety Assessment

The Contractor must maintain the baseline System Safety Assessment for
each change to the operational system baseline. The Contractor must
determine the need to update the safety assessment for all other changes
to be fielded through the conduct of a change impact analysis according
to Section 8.0 of this SOW. The Contractor must ensure the assessment
provides a comprehensive evaluation of the residual risk being assumed
prior to these major milestones. In accomplishing this task, the
Contractor must review all completed safety analyses and determine if
and where additional system safety verification is required. A final
comprehensive System Safety Assessment must be delivered formally at the
completion of the Contract. (CDRL A068)

### Test and Evaluation Safety

The Contractor must follow the requirements outlined in the SAPR for
component and system level testing that demonstrates the component,
series of integrated components or the system as a whole performs its
intended function. The Contractor must clearly flag safety critical
procedures, training, and tasks. The SSM must specify in the SSPP and
appropriate test documentation any safety related information needed to
be collected during the test program and provide support for analyzing
safety related test data and results.

### Safety Review of Engineering Change Proposals, Specification Change Notices, Requests for Deviation/Waiver

The Contractor's SSM must review all Engineering Change Proposals,
Specification Change Notices, Software Problem Reports, and Requests for
Deviation/Waiver for impact on safety. The SSM must approve all such
proposed changes prior to submission to the FAA.

### Safety Verification

The Contractor must perform safety verification in accordance with the
SAPR for all safety requirements.

### Software Program Safety Interface

The Contractor must ensure the SSP includes conduct of all safety
analysis, hazard identification, and mitigation and verification
activities required to support development of software according to the
objectives of RTCA/DO-178B. The Contractor must ensure software system
safety, as a major element of the WAAS SSP, is addressed in the SSPP and
the Software Development Plan.

### System Safety Architecture

The Contractor must review all changes authorized by the WAAS change
process, including but not limited to the Full LPV Performance
improvements, to determine all impacts to the WAAS Safety Architecture
and Design. The Contractor must update the WAAS Safety Architecture and
Design as needed, according to Section 8.0 of this SOW. The Contractor
must ensure such updates address any necessary changes to the Safety
Requirements Trace Matrix. The Contractor must ensure the description
identifies the allocation of System Safety Requirements to the system
implementation and provides complete and traceable evidence of the full
implementation of the System Safety Requirements and mitigation of
identified safety threats. The Contractor must ensure the description of
the Safety Architecture addresses the hazards identified as a result of
system hazard analyses and system development activities. Where system
safety is impacted, the Contractor must ensure the description of the
safety architecture provides evidence that the mitigations developed for
each threat operate as described and that the safety requirements have
been met. (CDRL A069)

## Human Engineering

The Contractor must implement a Human Engineering (HE) Program, in
accordance with the guidelines contained in Section 4 of MIL-HDBK-46855.
The Contractor must ensure the HE program consists of planning,
analysis, design support, and test and evaluation efforts to assure that
the WAAS Full LPV Performance design changes are consistent with the
capabilities and limitations of operators and maintainers in their
operational environments.

### HE Program Planning

The Contractor must update the HE Program Plan (HEPP) in accordance with
the guidelines contained in Section 4.1.2 of MIL-HDBK-46855, describing
the activities, tasks, schedule, organization, levels of effort, design
concepts, and test and evaluation. (CDRL A133)

### HE Studies and Analyses

The Contractor must develop and maintain task inventories for WAAS
Operators and Maintainers. The elements of those inventories must be
subjected to a Criticality Analysis. A critical task is defined as a
task: (1) which requires human performance which, if not accomplished in
accordance with system requirements, is likely to result in the
generation of Hazardously Misleading Information (HMI) or the Loss of
Signal-In-Space (SIS); or (2) where equipment design characteristics
demand human performance which approaches the limits of Operator or
Maintainer capabilities. The Contractor must further analyze tasks
identified as system critical tasks in a Critical Task Analysis (CTA) in
accordance with the guidelines contained in Section 4.2.1.3.2 of
MIL-HDBK-46855A. (CDRL A134)

The Contractor must solicit, analyze, and evaluate input from the WAAS
Users Group (WUG) (see Section 3.7.7 below) as appropriate in support of
studies and analytical efforts.

The Contractor must review the IOC design, evaluate and amalgamate data
and information from HE studies and analyses to establish and define
WAAS HE Critical Design Considerations (CDCs). A CDC is defined as an
aspect or element of the WAAS system (including hardware, software,
procedures, personnel, and environment), which will have a significant
impact on human performance (and hence system performance) if not
properly and adequately designed according to HE standards, guidance,
and best practices. Resulting CDCs will be analyzed and described in a
Critical Design Consideration Document PNB. The CDC PNB must be
delivered with each Scope Analysis Report (CDRL A140) for Government
approval. A formal Critical Design Consideration Document will be
delivered at the completion of the Contract. (CDRL A135)

### HE Design Support

The results of HE guidance (i.e., DOT/FAA/CT-96/01), studies, analyses,
test and evaluation, and WUG input must be applied to the Full LPV
Performance design of system equipment, software, human-computer
interfaces (HCI), and procedures. Mockup, rapid prototyping, and
simulation design evaluation must be employed as appropriate to assess
the impact of design details on human performance and user acceptance.
Alternate design evaluations to determine effectiveness, usability, and
user acceptance must be conducted as appropriate.

The Contractor must analyze, evaluate and prioritize action items
documented on the WAAS HE Action Items List (WHAIL) (see Section 3.7.5).
The Contractor must develop corrective actions for action items selected
by the Human Factors Working Group (HFWG) (see Section 3.7.6) and those
corrective actions, which are approved for implementation, must be
validated and implemented. The Contractor must revalidate and track the
implemented corrective actions for long-term effectiveness.

The Contractor must monitor, evaluate and provide recommendations on
Full LPV Performance proposed WAAS system design changes. The Contractor
must ensure that proposed changes do not negatively impact human
performance or negate/counter-act HE enhancements.

### HE Test and Evaluation

The Contractor must conduct a HE Test and Evaluation Program, which meet
the following objectives:

-   Demonstrates conformance of Full LPV Performance WAAS to the HE
    criteria established jointly between the Contractor and FAA; and

-   Determines whether undesirable (Legal questions use of this word.
    Can we replace with unintended or unsuitable, or something else???)
    hardware, software, or procedural features have been introduced.

### WAAS HE Action Item List 

Throughout Full LPV Performance, aspects of WAAS (including equipment,
software, CHI, and procedures) that may adversely impact human
performance (and subsequent system performance) must be identified by
the Contractor (as coordinated with the Government) as HE Action Items.
The Contractor must maintain and track the HE Action Items on a WAAS HE
Action Item List (WHAIL). Sources of HE Action Items must include (but
not be limited to): (1) study and analysis results, (2) recommendations
contained in *WAAS Human Factors Phase 1 Assessment*, dated 14 August
2000, (3) input from the WUG, and (4) other Human Factors Working Group
(HFWG) activities.

The Contractor must document and maintain the identified HE Action Items
in a tracking system. The Contractor must ensure the HE Action Item
documentation includes, as a minimum:

1.  A descriptive title;

```{=html}
<!-- -->
```
1.  A complete description of the issue;

2.  Potential impacts of the issue if unresolved;

3.  Planned resolution strategy(ies);

4.  Implemented resolution solution; and

5.  Effects of resolution solution.

Contractor format may be used for the tracking system. Upon Government
request, the Contractor must provide access to information maintained in
the tracking system.

### Human Factors Working Group 

The Contractor must participate in the joint Government-Contractor Human
Factors Working Group (HFWG). The Contractor Human Factors principal
must co-chair the group, along with the Government Human Factors
representative. The HFWG will consist of representatives from the
following: Government and Contractor Human Factors personnel, System
Engineering personnel, Safety and Training personnel, and, Operator and
Maintainer personnel. The HFWG is subordinate to the SEWG and will
coordinate, provide overall direction, and decision-making to the WAAS
HE effort. Recommendations for system changes originated by the HFWG are
presented to the WCRB for implementation in accordance with Section 8.0
of this SOW.

### WAAS Users Group 

The Contractor must host a WAAS Users Group (WUG) consisting of
Operators and Maintainers. The WUG is chaired by FAA Operators and
Maintainers representatives. The primary purpose of the WUG is to
provide a venue for soliciting input from WAAS users.

The WUG will participate, as a minimum, in the following activities:

1.  Task Inventory development,

```{=html}
<!-- -->
```
1.  Criticality analysis,

2.  Critical Task Analysis,

3.  Critical Design Consideration development,

4.  WHAIL item identification and corrective item development,

5.  WHAIL item evaluation and prioritization,

6.  Prototype and simulation evaluation,

7.  Alternative design evaluations,

8.  Usability evaluations,

9.  Proposed design change evaluation,

### HE Reviews

Contractor HE representatives must participate in all technical and
program reviews where human performance is a determinant of system
operational and maintenance effectiveness. In addition, the HE
representatives must address the following as a minimum during the HE
reviews:

1.  Principal Human Performance Requirements. Summarize system operation
    and maintenance requirements, which depend on human performance.
    Identify tasks critical to system effectiveness. Review critical
    tasks in terms of the impact of various operational and
    environmental conditions on their performance.

```{=html}
<!-- -->
```
1.  Human Engineering Design. Present the compliance of items having a
    human interface with human performance and DOT/FAA/CT-96/01
    requirements.

2.  HE Action Items. Present and discuss the current content of the
    WHAIL, along with the status of on-going and implemented design
    changes

> 4\. Manpower, Personnel, and Training (MPT) Implications. Describe MPT
> implications resulting from planned Full LPV Performance improvements.

## Reliability and Maintainability

### Reliability and Maintainability Program

The Contractor must maintain and update a reliability program in
accordance with MIL-STD-785B and a maintainability program in accordance
with MIL-STD-470B. The Contractor must generate a Reliability and
Maintainability (R&M) Program Plan by modifying, integrating, and
updating as required, the existing Reliability and Maintainability
program plans. The reliability and maintainability programs must be
planned, integrated, and executed to support the design, development,
and testing efforts of the two planned major system upgrades
(Architecture Upgrade and Full LPV Performance) to ensure that the
requirements of the Full LPV Performance Specification, and this SOW are
satisfied.

#### Reliability and Maintainability Program Plan

The Contractor must ensure the Reliability and Maintainability Program
Plan describes how the RMA tasks in this SOW are addressed for the
system changes accomplished under this SOW. The Contractor must include
the organizational structure to accomplish these tasks in the Plan.

#### RMA Team Meetings

The RMA Team is comprised of FAA and Contractor RMA representatives and
will meet quarterly as a sidebar in conjunction with System Engineering
Working Group meetings or as directed by the FAA. The RMA Team will
review all proposed designs changes, current status of Reliability and
Maintainability Modeling and Predictions for all proposed design changes
and FMEA development in support of the Safety Program. Wherever
possible, the Contractor must use historical MTBF values for the new
LRUs.

#### Failure Modes, Effects Analysis (FMEA)

The Contractor must document, in a PNB, the results of Failure Modes,
Effects Analysis (FMEA) for all proposed Full LPV Performance Upgrades
using MIL-STD-1629A as a guide. The Contractor must ensure the FMEA
covers hardware and firmware failures modes of the new and or modified
LRUs. The Contractor must tailor the FMEA with FMES to satisfy the
Safety Assurance Process Requirements, including support to Fault Tree
Analysis development.

#### Reliability and Maintainability Predictions

The Contractor must develop Reliability and Maintainability Predictions
for all Full LPV Performance upgrades. The Contractor must establish the
reliability and maintainability predictions based upon Vendor test
results, fielded data and through analysis, using MIL-HDBK-217 and
MIL-HDBK-781 as a guide. The Contractor must document LRU R&M
Predictions in PNB format.

#### Failure Reporting and Corrective Action System

The Contractor must ensure failure reporting tracks new and modified
LRUs, and provide a copy of all Vendor, i.e., prime and subcontractor,
failure analysis reports that allow traceability to the root cause. The
Contractor must ensure these reports must cover hardware and firmware
faults/failures.

### Reliability and Maintainability Reports

The Contractor must prepare and submit to the FAA a quarterly
Reliability and Maintainability Status Report to include failure summary
and analysis information. (CDRL A033)

## Reserved

## System Test and Evaluation 

The Contractor must establish a formal test program in accordance with
Section 4 of FAA-E-2976. The Contractor must be responsible for the
conduct of hardware, software, and system level testing that must apply
to the Full LPV Performance WAAS (Full LPV Performance Architecture
Upgrade and Performance Upgrades).

The Contractor may write the test documentation in Contractor format.
The Contractor must design the test program to verify the requirements
specified in Section 3 of the WAAS Specification.

### Test and Evaluation Management

The Contractor must assign a single Test Manager to interface with the
FAA Test Director to coordinate integration of prime Contractor and
subcontractor testing, and, support of FAA tests. The Contractor must
design the test program to minimize redundancy of effort or data. The
FAA Test Director may appoint a representative to observe formal and
informal tests. The FAA Test Director\'s or appointed representative's
authority is to ensure compliance with the approved test plans and
procedures.

### Master Integration and Test Plan 

The Contractor must develop a Master Integration and Test Plan (MITP)
that provides the strategy for the integration and test of reported
problems and enhancements to the LNAV/VNAV WAAS. The MITP provides the
groundwork for the detailed plans for each change due to a reported
problem or planned enhancement. The requirements for the detailed plans
are contained in the Section 8.0 of this SOW. The MITP may be prepared
in Contractor format. (CDRL A143)

The Contractor must include the following items in the MITP:

-   Relationship between the system engineering process and integration
    and test activities

-   General system integration strategy for each planned enhancement

-   Cutover approach. This includes the cutover approach for planned
    enhancements (algorithmic/software, new reference stations, new
    hardware, and changes to terrestrial communication design)

-   Software enhancement strategy to show compliance with the objectives
    of RTCA DO-178B

-   Strategy for requirements based testing for system, hardware, and
    software

-   Integration and testing of terrestrial communication enhancements

-   Regression test strategy

-   Software test strategy

-   Overall strategy for integration and test of reported problems with
    the operational WAAS

-   Verification Requirements Traceability Matrix (VRTM)

-   Factory Acceptance Test and Site Acceptance Test strategy

-   Integration and test resources

-   Integration and test management description

### 3.10.3 Production Acceptance Test and Evaluation Plan {#production-acceptance-test-and-evaluation-plan .unnumbered}

The Contractor must update the Production Acceptance Test and Evaluation
(PAT&E) Plan to include the new requirements identified in the Full LPV
Performance Specification. This Contractor must ensure the PAT&E Plan
addresses requirements pertaining to Factory Acceptance Testing (FAT),
for WAAS Program integrated Site Acceptance Testing (SAT) for new United
States, Canada, and Mexico sites and the 3^rd^ C&V. The Contractor must
support FAA SAT testing at each new WAAS site. The Contractor must
ensure the PAT&E Plan provides detail beyond that contained in the MITP
on the testing and integration of new hardware into the operational
system as well as detailed test descriptions for those requirements
allocated to PAT&E. The Contractor must ensure the PAT&E Plan includes
sections on PAT&E test management, schedule, test configuration
management, and a VRTM/ System Requirement Allocation Matrix (SRAM) for
those requirements allocated to PAT&E. The Contractor must ensure the
SAT section of the PAT&E Plan addresses the requirements for the
turnover of the data required to complete the Facility Reference Data
File (FRDF). The Contractor must ensure the content of the FRDF is in
accordance with FAA Order 6030.45. (CDRL A055)

### 3.10.4 Test Procedures {#test-procedures .unnumbered}

The Contractor must prepare and submit test procedures in Contractor
format to cover all requirements based testing. The Contractor must
ensure these procedures contain step-by-step instructions for test
conduct and the procedures clearly show which requirements are being
verified during the testing. The Contractor must not commence testing
until the procedures have been reviewed and approved by the FAA. (CDRL
A056) (CDRL A057)

### 3.10.5 Test Reports {#test-reports .unnumbered}

The Contractor must prepare and submit test reports documenting the
results of all formal testing conducted. Use of Contractor format is
authorized. The FAA will approve all formal test reports. (CDRL A058)
(CDRL A059)

### 3.10.6 Test Conduct {#test-conduct .unnumbered}

The Contractor must notify the Government, via contract letter, 15 days
in advance and receive formal approval to proceed to test prior to
performing any formal testing. The Contractor must perform all testing
in accordance with FAA approved test documentation. The Contractor must
maintain an official test log containing test identification,
description of the Unit-under-test, date and time of test, procedures,
test report(s), and any deviations or exceptions to the approved test
procedures. The Contractor must provide a list of any prior
discrepancies or retests to be picked up as part of the current test to
the FAA at least seven days prior to the start of testing. The
Contractor must not reallocate requirements from test to test without
prior formal notification and approval by the FAA.

### 3.10.7 General Test Ground Rules {#general-test-ground-rules .unnumbered}

The Contractor must comply with the following ground rules for all
testing conducted:

-   The Contractor must design tests such that the success or failure of
    each test event is determined by measuring the results of the test
    against the required or expected results of the approved test
    documentation. The FAA must make the determination of successful
    completion of test objectives and provide acceptance of test results
    in writing.

-   Notification of test conduct includes assurance that all facilities
    and other support are available, the test configuration identified
    and under configuration control, the test equipment properly
    calibrated, and any prior deficiencies have been corrected and
    verified in accordance with the Contractor\'s quality assurance
    procedures. Prior to the start of each formal test, the Contractor
    must brief the FAA representative(s), as a minimum, on the following
    topics:

```{=html}
<!-- -->
```
-   planned procedure and scenario changes that must be reflected in the
    procedure and scenario updates;

-   quality assurance baseline testbed audit report including the status
    of all hardware, software, and documentation to be used in the test;

-   test schedule;

-   walk-through of the test conduct.

-   The Contractor must make all changes to test procedures since the
    last submission to the FAA as \"Red-lined Items.\" If a work-around
    is required in one or more steps of the test procedures, the
    Contractor must explain the deviation and cause of this work-around.
    The Red-lined test procedures must be submitted to the FAA in the
    DT&E and the PAT&E Reports.

```{=html}
<!-- -->
```
-   The Contractor must not interrupt the WAAS nor cause its performance
    to degrade during normal monitoring, testing, and validation
    operations. The Contractor must obtain advance approval from the FAA
    to use any devices and procedures for monitoring, testing, trouble
    isolation, and related purposes. The Contractor must obtain FAA
    approval prior to interruption of the WAAS.

-   The Contractor must keep test logs to record all events that have
    occurred during the conduct of formal tests. The Contractor must
    document all failures that occur during formal testing. The
    Contractor and FAA will jointly conduct a scoring conference after
    the conclusion of each formal test and prior to the development of
    each formal test report.

-   The Contractor must maintain a database of failure reports occurring
    during formal testing, and track individual corrective actions. The
    FAA may choose to witness the closure of corrective actions and must
    be provided all updates to failure reports. The FAA reserves the
    right to approve or disapprove the closure of failure reports.

-   The Contractor must make test data and logs from formal tests
    available within two (2) working days after test completion upon FAA
    request and deliver a copy of FAA selected and requested data within
    five (5) working days. The Contractor must provide at least two (2)
    working days notice to the FAA prior to the start of each unique
    formal test dry run, on a test-by-test basis.

-   The Contractor must provide the FAA an opportunity to witness all
    Contractor conducted informal tests at the unit level and above.

-   The Contractor must conduct a post-test briefing not later than
    one (1) day after the conduct of each unique formal test. The
    Contractor must brief, at a minimum, the following topics:
    preliminary Contractor analysis of test responses and results;
    identification and preliminary analysis of anomalies discovered
    during test and post test analysis; planned and unplanned deviations
    and changes included in as-run test procedures; test procedures;
    test conduct log; and problem reports.

The Contractor must conduct retests when:

-   The analysis of test data and the assessment of test results against
    pass/fail criteria indicate the item under test has failed to meet
    its applicable requirements, or when the analysis and assessment are
    inconclusive, or

-   A review of changes to hardware, software, and firmware indicate
    that prior test results are invalid or that the impact on prior test
    results cannot be determined without repeating the test, or

-   The Contractor deviates from the approved test plans or procedures
    without the prior approval from the FAA.

## Configuration Management

### Configuration Management Program

The Contractor must update and maintain the existing Configuration
Management Program in accordance with FAA-STD-021A and MIL-STD-973 for
hardware, FAA-STD-026A, FAA-STD-021A and MIL-STD-973 for software and
Attachment P (Safety Assurance Process Requirements (SAPR) Document) for
System Safety. The Contractor must ensure the CM process for software
meets the objectives in paragraph 7.0 and Table A-8 of RTCA/DO-178B for
the software safety level assigned to each CSCI. The Contractor must
specify a single authority to serve as a focal point for all CM related
issues.

### Configuration Management Plan

The Contractor must update, as required, the existing WAAS Configuration
Management Plan (CMP), which describes the Contractor\'s Configuration
Management Program, including responsibilities, methodology and
procedures for baseline identification, configuration control, and audit
and status accounting of software, hardware, documentation, support
equipment, firmware, and data bases. In addition the Contractor must
ensure the CMP addresses the Contractor's interface to the WAAS Change
Control Process (Section 8.0). The Contractor must use MIL-STD-973 with
Notice 1, paragraph 5.2 and Appendix A and data item description
DI-CMAN-80858A when updating the CM plan. The Contractor must ensure the
CMP addresses software development tools; the developmental
configuration management process (MIL-STD-973, paragraph 5.3.3) required
hardware and software necessary to read, write, or modify existing
programs or data; requirements necessary to compile, assemble, link, and
load source code to produce executable programs and test and debug
program code. The Contractor must ensure the engineering release system
meets the requirements of Appendix C of MIL-STD-973. (CDRL A039)

### Configuration Identification

The Contractor must follow a configuration identification program
consistent with the LNAV/VNAV Phase of WAAS using MIL-STD-973 paragraph
5.3. The Contractor must select, identify, label, serialize, and mark
all Hardware Configuration Items (HWCI) and Computer Software
Configuration Items (CSCI) in accordance with MIL-STD-973 paragraph
5.3.6 and develop and maintain configuration baselines in accordance
with MIL-STD-973 paragraph 5.3.4.

#### System-Level Documentation

The Contractor must update the System Specification**,** consistent with
each WCRB approved change to the product baseline. (CDRL A121)

#### Configuration Item-Level Documentation

The Contractor must update the Configuration Item Development
Specification for each HWCI in accordance with MIL-STD-490A, Appendix
II, consistent with each WCRB approved change to the product baseline.
(CDRL A042)

#### System Configuration Load List

The Contractor must only maintain a load list for new Full LPV
Performance sites until the FAA assumes maintenance responsibility.
During Contractor maintenance, the Contractor must identify the location
of all configuration item serial numbers for each location of the new
Full LPV Performance sites. The Contractor must integrate the load list
with the hardware problem reporting systems and be available to the FAA,
via the WAAS Shared Server.

### Configuration Control

The Contractor must maintain a system described in the CM plan, of
configuration control in accordance MIL-STD-973 section 5.4. The
Contractor must establish an internal Configuration Control Board (CCB)
and establish and implement procedures to accomplish change control in
accordance with Section 8.0 of this SOW until the established baseline
is updated to include the respective change. The Contractor must submit
changes to established baselines to the FAA in accordance with Section
8.0 of this SOW. The Contractor must submit Requests for Deviations
(RFD) and Requests for Waivers (RFW) as detailed in paragraphs 5.4.3,
5.4.4, 5.4.8.3, and 5.4.8.4 of MIL-STD-973. The Contractor must prepare
and submit specification change notices in accordance with Section 5.4.6
of MIL-STD-973. (CDRL A048) (CDRL A049) (CDRL A122)

### Configuration Status Accounting

Configuration Status Accounting for the operational baseline (Reference
Product Level Configuration Index (PLCI)) is accomplished by AOS. The
Contractor must implement and maintain a Configuration Status Accounting
System in Contractor format, for activities covered by this SOW. The
Contractor must coordinate configuration status accounting with AOS as
changes are accomplished in accordance with Section 8.0 of this SOW. The
Contractor must ensure the system documents the configuration
identification for each serialized component and determines the status
of change requests, deviations, and waivers by an automated means with a
real-time capability whenever interrogated. The Contractor must provide
a Configuration Status Accounting Report(s) for each major operational
baseline update.

(CDRL A050)

### Data Management

The Contractor must comply with the requirements of FAA-STD-021A and
MIL-T-31000.

### Configuration Audits

A formal FCA/PCA will not be conducted for activities in support of this
SOW; however, the Contractor must support activities intended to ensure
all differences introduced to the operational baseline in each update
are documented. The Contractor must conduct an RTCA/DO-178B compliance
conformity review for each operational baseline update in accordance
with Section 8.3 of this SOW.

### Interface Requirements/Control

The Contractor must notify the FAA of impacts to GFE and NAS interfaces.
The Contractor must perform interface configuration management as stated
in section 5.3.7.1 of MIL-STD-973. The Contractor must prepare and
submit Interface Control Documents for each major release to the product
baseline in accordance with FAA-STD-025C. (CDRL A052)

### Retrofit Requirements

The Contractor must comply with retrofit reporting requirements of
paragraph 5.5.8 MIL-STD-973.

## Quality Control

The Contractor must maintain a Quality Assurance Program in accordance
with the requirements of ANSI//ISO/ASQ Q9001-2000, DID-FAA-QA-003,
FAA-STD-026A and DID-FAA-026-023. The Contractor must comply with
Software Quality Assurance objectives from Section 8.0 and A9 of
RTCA/DO-178B. The Contractor may utilize certified operators where
possible.

### Quality System Plan

The Contractor must maintain and update the Quality System Plan (QSP) as
necessary. The QSP describes the Contractor's quality control program
implemented in accordance with ANSI//ISO/ASQ Q9001-2000, DID-FAA-QA-003,
FAA-STD-026A and DID-FAA-026-023. (CDRL A030)

# National Airspace Integrated Logistics Support 

## Contractor NAILS Program Management Responsibilities

The maintenance support concept for WAAS is Interim Contractor Depot
Level Support (ICDLS). ICDLS will be provided by the Contractor prior to
transitioning to full FAA depot maintenance for the duration of the
contract. The Contractor must provide program management for the
requirements contained herein. The Contractor must designate a single
point of focus for the National Airspace Integrated Logistics Support
(NAILS) Program. The Contractor must execute a NAILS Program IAW the
requirements contained herein. The Contractor must ensure the NAILS
Program consists of the total set of tasks required to accomplish the
requirements stated in FAA Order 1800.58A, National Airspace Integrated
Logistics Support Policy. The NAILS Program must support the following
functions:

-   Planned Full LPV Performance improvements

-   ICDLS

-   Second Level Engineering Support (SLES)

### Planned Full LPV Performance Improvements

The Contractor must ensure NAILS activities continue to utilize the
practices and procedures established during the IOC portion of the WAAS
contract.

#### NAILS Program Planning

The Contractor must update the NAILS Integrated Support Plan (ISP) to
include planned Full LPV Performance updates. The ISP must contain
updated descriptions of the procedures, actions, events, and
organization the Contractor intends to employ in order to accomplish the
NAILS program. All updates of the NAILS ISP must be submitted for FAA
approval. (CDRL A070)

#### National Airspace Integrated Logistics Support Management Team (NAILSMT)

The Contractor must host all NAILSMT meetings, the first of which will
be held at the discretion of the FAA Associate Program Manager for
Logistics (APML) and the FAA Program Office. The APML will chair the
NAILSMT. The NAILSMT will monitor schedules and contract performance,
and, review the adequacy, timeliness, and compliance with contract
requirements. The NAILSMT will meet semi-annually throughout the
contract to review and assess the progress of the NAILS Program. The
NAILSMT meetings will be held at times and places mutually agreeable to
the APML and the Contractor. The Contractor must submit a proposed
agenda to the chairperson no later than 15 days prior to the start of
the meeting. The agenda will provide for status reporting and analysis
of problem areas. Contractor format is acceptable. The Contractor must
provide meeting minutes IAW with Section 3 of this SOW.

#### Contractor Support of Meetings and Conferences

The Contractor will assist the FAA in providing support for conferences
and

meetings, including facilities, office equipment, clerical personnel,
mock-ups,

technical data, and subcontractor participation (when requested by the
APML), in

accordance with the AMS policy. The Contractor must submit an agenda and
meeting minutes IAW Section 3 of this SOW.

### Contractor Control

#### Subcontractor/Vendor Control

The Contractor must maintain, and be held responsible for accomplishment
of subcontractor/vendor NAILS. The Contractor must incorporate this
requirement in all subcontracts exceeding \$100,000.

#### Similar Work Efforts

The Contractor must make maximum use of analysis and documentation being
procured under other or earlier provisions of this contract (i.e.,
subcontractor LSA data, Commercial-Off-The-Shelf (COTS) equipment data)
and as applicable and available, data from other Government contracts
and sources. The Contractor must ensure the task analysis and equipment
analysis do not duplicate the analysis, data collection, and
decision-making that went into compiling the data contained in these
other or earlier sources. The Contractor must ensure these similar work
efforts must be consolidated in such a way as to preclude duplication
and ensure consistency.

#### Logistic Management Information (LMI)

The Contractor must maintain an LMI (Logistic Management Information)
Program IAW the procedures MIL-PRF-49506 the Data Products in EXCEL
format. See **Attachment Q** LMI Data Produce Definitions for layout of
Excel spread sheet for the planned Full LPV Performance upgrades. The
Data Product must represent the physical system design configuration
including: system, subsystems, support and test equipment, components,
assemblies, subassemblies, and training equipment for the WAAS. The
Contractor must adhere to the DATA Definitions, Edits and Data Formats
as describe in CDRL A074.

As ordered by the Government, the Contractor must provide a top-down
hardware breakdown structure to the component level except
Commercial-Off-The-Shelf (COTS). Any COTS or Non-developmental Item
(NDI) item must only require LMI data to the Line Replaceable Unit (LRU)
level. Any modification to COTS item may disqualify it as COTS and may
require LMI data to the component level. The Government will determine
the level of LMI data required for COTS modification. The Contractor
must ensure the LMI identifies logistics resources for support of the
system at all levels of maintenance.

####  LMI Program Tasks

#####  Reserved

#####  Reserved

#####  Reserved

#####  Reserved

#####  LMI Provisioning Guidance Data

The Contractor must support and host the LMI/delta Provisioning Update
Meeting. The Contractor must provide as part of a NAILSMT meeting/WCRB
Provisioning/Supply Support data, in accordance with LMI
(Mil-PRF-49506). As determined by the FAA, the Contractor and
subcontractors, must attend, participate in and contribute expertise in
resolution of provisioning and supply support problems or issues. The
Contractor must document agreements reached in meeting minutes.

##### Reserved

#####  LMI Data Base

The Contractor must establish and maintain an automated LMI database for
equipment that is new to the WAAS baseline. The Contractor must ensure
the LMI software is a Logistics Support Activity (LOGSA) validated ADP
system. The Contractor must ensure the LMI is the central file of
logistics data for the system. The Contractor must prepare the LMI data
in accordance with MIL-PRF-49506. The Contractor must update LMI
documentation to reflect changes in support requirements resulting from:

-   Changes to equipment design, support or operational requirements as
    a result of logistic demonstrations, parts obsolescence, technical
    manual reviews, training results, and

-   Contractor or FAA testing.

-   Logistic support improvements or the correction of deficiencies
    discovered through analysis of test results or by Contractor's
    verification of LSAR documentation.

-   FAA reviews of LMI documentation and/or the result of provisioning
    data.

##### LMI Data Review

The Contractor must maintain internal procedures that provide for
verification of the adequacy and technical accuracy of LMI
documentation. The FAA will review Contractor-produced LMI data,
including LMI output summaries, drawings, mock-ups, specifications, and
photographic reproductions. The LMI review will be accomplished during
and by members of the NAILSMT. The Contractor must ensure availability
of support materials and personnel for LMI data reviews. Reviews will be
held at the Contractor\'s facility.

#####  LMI Delivery

The Contractor must prepare and submit for FAA approval, the required
LMI data for each hardware change identified in each WCRB Detailed
Design Report (A141). The Contractor must deliver the LMI data in
electronic media format IAW the format provided in MIL-PRF-49506. (CDRL
A074)

##### Delivery Information

The Contractor must furnish the following information with the delivery
of each electronic media:

-   Tables contained on the media and their sequence.

-   The approximate number of LCNs contained on the media.

-   Person to contact.

### Maintenance Planning 

#### Maintenance Concept

The Contractor must base the maintenance concept on FAA Order 6000.30C,
Policy For Maintenance of The National Airspace System (NAS). ICDLS will
be used initially with ultimate transition of depot level maintenance,
supply support, and second level engineering support to the FAA. FAA
Airway Facilities (AF) personnel will be responsible for WAAS site level
operations and maintenance.

#### System Design for Maintenance

The Contractor must design Full LPV Performance upgrades to enhance
system maintenance. System status will be continuously monitored from
the Operation and Maintenance (O & M) console. The Contractor must
upgrade the WAAS so that system level verification, validation, and
certification can continue to be accomplished at the O & M. The
Contractor must ensure WAAS upgrades incorporate modular design
techniques to support two levels of maintenance. On-site repair must be
limited to the removal and replacement of the LRU to restore service.
Depot level maintenance will consist of repairing or replacing faulty
LRUs.

#### Site Visits

The Contractor must ensure Full LPV Performance upgrades must support
periodic and corrective maintenance that can be accomplished with site
visits occurring no more frequently than in accordance with the Full LPV
Performance Specification and FAA Order 6000.30C.

### Interim Contractor Depot Logistics Support

#### ICDLS Management

The Contractor must maintain a depot logistics support management
program to effectively support the WAAS and to assist in the
accountability of services rendered through Full LPV Performance. The
Contractor must maintain, in the ISP, a summary of procedures that must
detail the Contractor\'s approach to depot maintenance. That portion of
the ISP may be in Contractor format, including the names and telephone
numbers for points of contact associated with the depot maintenance
effort.

The Contractor must provide bar code markings for deliverable WAAS Full
LPV Performance equipment for all LRUs returned for repair to the Depot
and Vendor. Markings are to comply with Asset Identification
Specification Version 2.4 dated November 18, 2003. (A073)

#### Operations and On-site Maintenance

##### Interim Contractor Depot Level Support (ICDLS) - Supply Support

The Contractor must furnish facilities, labor, equipment, material and
documentation necessary to provide for stocking, receipt, issue,
inventory/management control, and repair service IAW the provisions set
forth in this statement of work for all repairable/non-repairable LRUs
of the WAAS, with the exception of the NAVSYS Signal Generator.

The Contractor must provide for the repair of selected repairable items
to the extent not covered by the manufacturer\'s warranty. The
Contractor must include all labor, tools, test equipment, software,
facilities, materials, documentation, training, a level of serviceable
LRUs sufficient to maintain the level of service and any other technical
and administrative support necessary to repair and restore service to
the WAAS. The Contractor must provide to the Federal Aviation
Administration (FAA) field sites those items as requested by the
Government. This entails complete supply support, which includes issuing
expendable items and the issuing, receipting and repairing of exchange
and repair (E&R) of Line Replaceable Unit (LRU) for the WAAS for the
contract period of performance. The Contractor must ensure an E&R item
is repairable. The Contractor must ensure sufficient stock is maintained
to allow direct issue of the items listed for coverage under ICDLS and
those items covered by warranty are repaired or replaced at no cost to
the Government. The Contractor must repair, or replace as required, all
repairable E&R LRUs returned from FAA field sites and ensure the repair
cost does not exceed sixty-five per cent (65%) of the cost of a new
item, unless approved by the Contracting Officer or a designated
representative. The Contractor must furnish all labor, tools, test
equipment, parts, software, and any other technical or administrative
support necessary to provide the required depot level logistics support.

##### Reserved

##### E&R LRU Repair Procedure

The Contractor must repair E&R items to the extent necessary to restore
it to a condition in which the item is capable of meeting all
performance and functional requirements for which it was designed. If
the repaired item is part of a system, the Contractor must ensure it
functions in a manner, which will allow the complete system to meet all
operating tolerances. Minor cosmetic defects, which do not affect the
installation or operation of the item, do not require correction or
repair. The Contractor must clean, visually inspect, bench test, and
isolate faults. The Contractor must disassemble items to establish that
the item is serviceable. The Contractor must reassemble, calibrate,
functionally test, perform acceptance inspection, and prepare for
shipment of the item or component. All methods and procedures used by
the Contractor must be accomplished with the special tools and test
equipment developed for that purpose. The Contractor must ensure all
repaired items comply with FAAD-STD-1293C and all other applicable
specifications of the contract. The Contractor must make any
modification to items required by the contract and not previously
accomplished at the time of repair. Disposition of removed parts will be
at the direction of the FAA Logistics Center (FAALC) Manager. The
Contractor must conduct testing, inspection, and final acceptance of
repair items in accordance with the production, test, inspection, and
acceptance requirements of FAAD-STD-1293C and this SOW. The Contractor
must perform repairs using test equipment having traceability to the
National Institute of Standards Technology in accordance with
MIL-STD-45622, Calibration of System Requirements. The Government
reserves the right to inspect and verify all repairs in accordance with
the terms of this contract. Parts required to support the repair of E&R
items will remain the property of the Contractor until used to restore
failed items, at which time they become part of the LRU and Government
property. The Contractor may request additional inventory of parts from
the Contracting Officer based upon the repair experience or analysis of
this need. The Contractor must have available an inventory consisting of
a components/piece parts required for the supply support and repair of
all items. The Contractor must prepare for inventory an itemized list of
all items required for support. The Contractor must maintain an
inventory listing to include, but not necessarily limited to, the
following items:

-   Part number and manufacturer's cage code

-   Nomenclature or description

-   Quantity

-   Unit of issue or Unit Ordering Quantity (UOQ)

-   National Stock Number (if available)

-   Unit Price

-   Extended Price

The Contractor must maintain an Economic Ordering Quantity (EOQ) method
(the same as presently established under the Contractor's own ordering
system) for replenishment. Previously ordered spare parts peculiar by
the Government will be maintained at the Contractor's facility for use
in the rotatable pool and all parts will remain at the Contractor's
bonded storage facility. For all vendor items requiring repair by the
original equipment manufacturer (OEM), the Contractor must factor repair
times into the stock requirements to meet exchange requirements for the
LRUs.

###### Support Equipment

The Contractor must provide and maintain support equipment and test
equipment to support the WAAS depot activities during the ICDLS period.
The Contractor must certify that depot support and test equipment is
calibrated and operating within the required tolerances*.*

###### Maintenance Support Facility Requirements

The Contractor must provide the necessary office and work space to
effectively execute this contract during the period of performance. The
Contractor must be responsible for providing the necessary facilities
for maintenance of WAAS hardware, for shipping and receiving, and to
store system spares, piece parts, and support equipment required to
maintain the system.

##### Supply Support

###### Spare And Piece Parts Support

The Contractor must be responsible for procuring and providing all
required spares and piece parts, and replenishment thereof, for the
duration of the ICDLS period of performance. The Contractor must
initiate and maintain inventory control for spares and piece parts and
must maintain complete records of the inventory. The Contractor must
house the spares and piece parts in a Government Bonded Storeroom to
provide segregated storage of these spares. At the end of ICDLS (end of
Full LPV Performance Contract) the spares and any piece parts in the
bonded stock room will be transferred to the FAALC in two lots of
approximately 50% each. The first lot will be transferred 60 days prior
to the end of the ICDLS. The second lot will be transferred at the end
of ICDLS. Prior to the first shipment of parts from the Contractor, a
team from FAALC will accomplish a physical inventory of assets stored in
the bonded stockroom.

###### Consumption/Usage Report

The Contractor must maintain consumption usage reports on the WAAS
spares and piece parts used or consumed. Spares are the repairable and
non-repairable circuit cards, removable modules, and LRUs. Piece parts
are those items required to repair repairables. The Contractor must
submit consumption/usage reports to the FAA monthly no later than seven
days following the last day of each month. (CDRL A079) (CDRL A080)

###### Delivery Requirements 

####### Order Priority

The Contractor must provide a 24-hour point of contact. The Contractor
must provide the name and telephone number of the point of contact.
Requisitions/orders will be submitted to the Contractor via Web-base LIS
Interface Tool, or in some cases telephone or facsimile. Telephone
requisitions will be confirmed on Web-base LIS Interface Tool within 24
to 48 hours.

Web-base Requisition Interface Procedures

The Contractor must utilize the FAA Logistic Center Web-Based LIS
Interface Tool to receive and process requisitions forwarded by the FAA
Inventory Manager. The Contractor must complete all appropriate
Interface data fields; provide the required asset and asset return
information, as well as any associated shipping information on a daily
basis.

The Contractor must monitor the web-based tool for requisitions during
standard working hours, defined as 08:00 a.m. - 14:30 p.m. PST (10:00
a.m. - 16:30 p.m. CST), Monday - Friday, excluding federal and
Contractor holidays.

The Contractor will receive returned assemblies from WAAS sites and will
record information regarding the returned item in the web-based
requisition interface tool, to include originating site, LRU, and
shipping information.

For all requisitions, the Contractor must utilize the FAA priority codes
system: This identifies priority of requisition placed by the user;
indicates priority of Purchase Order on due-in; and priority of
requisition on due-out.

-   Priority 1- Requisition must be shipped within 24 hours of the
    Contractor having received the requisition request from the
    Government.

-   Priority 2- Requisition must be shipped within 48 hours of the
    Contractor having received the requisition request from the
    Government.

-   Priority 5- Requisition must be shipped within 7 business days of
    the Contractor having received the requisition request from the
    Government.

####### Shipment Of Items

######## Shipment of E&R Items

**From Contractor Facility to Government Facility**. Upon request by the
Government, the Contractor must ship a serviceable E&R item to the
designated Government field facility. The assigned FAALC manager will
furnish shipping instructions for those repaired items. The assigned
FAALC Manager will contact the Contractor\'s depot repair facility and
provide a tracking number for each shipment repair action. The
Contractor must use the assigned tracking number as the Return Material
Authorization (RMA) for transportation charges to bill as a separate
item on all invoices. If the item's shipping charges for any one
destination exceed \$100, the waybill must be marked as follows \"THESE
TRANSPORTATION CHARGES ARE TO BE PAID AS A SEPARATE AND DIRECT ITEM BY
THE U.S. GOVERNMENT; THEREFORE, ANY SPECIAL U.S. GOVERNMENT
TRANSPORTATION RATES MUST BE APPLIED.\" Method of shipment will be
commensurate with the designated priority of the requirements and may be
specifically designated by the assigned FAALC Inventory Manager (IM).

**From Government Facility to Contractor Facility.** Upon receipt of a
serviceable item at the Government facility, a repairable item will be
shipped using the prepaid return provided by the Contractor directly
from the field facility. The repairable item will be returned to the
Contractor by traceable means within ten (10) calendar days. All
shipments must be by traceable means.

######## Shipment of Expendable Consumable Items 

Upon request by the Government, the Contractor must ship the specified
quantity of the expendable consumable item to the designated Government
field facility. The assigned FAALC Manager will furnish shipping
instructions for the expendable consumable items. The Contractor must
bill transportation charges as a separate item on all invoices. If the
items shipping charges for any one destination exceed \$100, the
Contractor must mark the waybill \"THESE TRANSPORTATION CHARGES ARE TO
BE PAID AS A SEPARATE AND DIRECT ITEM BY THE U.S. GOVERNMENT; THEREFORE,
ANY SPECIAL U.S. GOVERNMENT TRANSPORTATION RATES MUST BE APPLIED.\"
Method of shipment will be commensurate with the designated priority of
the requirements and may be specifically designated by the assigned
FAALC Manager.

### Support Equipment

Support equipment has been provided to support the LNAV/VNAV WAAS. To
the extent possible, the Contractor must utilize LNAV/VNAV support
equipment to satisfy requirements associated with Full LPV Performance.

#### Support And Test Equipment Identification

The Contractor must identify support and test equipment for site
maintenance, depot maintenance, and depot software support. The
Contractor must justify requirements for special support and test
equipment. The Contractor must describe test equipment functions and
parameters measured in sufficient detail to enable the FAA to determine
the best method of satisfying the requirement. Whenever possible, the
Contractor must satisfy support and test equipment requirements with
items currently in the FAA inventory. The Contractor must identify the
depot test equipment, test plans and procedures and associated
documentation necessary for the FAA to conduct depot functions in the
transition plan. (CDRL A078)

#### Automated Test Equipment (ATE) Identification

The Contractor must select from the list of WAAS ATE hardware listed in
the transition plan. The Contractor must document any decision for not
selecting from the list of ATE; this rationale must be provided to the
FAA. The Contractor must require final approval by the FAA on ATE
selection to prevent unnecessary proliferation of types and quantities
of ATE in the FAA inventory. The Contractor must justify, document, and
describe requirements for ATE using the LSAR \"E\" data tables, Genrad
2272 (Bed of Nails, 1024 Pins), Factron 635 (Functional IC Tester), HP
3065 (Bed of Nails).

#### Development of ATE Software and Equipment

The Contractor must provide the Government all ATE software developed
for the WAAS program. This includes programs for both commercial ATE
hardware and/or "bench" test fixtures where Personal Computers (PC's)
control the testing of individual modules connected to separate
fixtures. The Contractor must provide a copy of the operating procedure
for the Test Program Set (TPS) software in sufficient detail that an
experienced ATE operator can run the program. (CDRL A105)

#### Development Of Test Program Sets (TPSs)

The Contractor must design all non-COTS/NDI LRUs in the WAAS to be
compatible with, and facilitate testing by the Contractor-designated
automatic test system. The Contractor must provide all software,
firmware, materials, instructions, and documented unit test programs
compatible with the designated automatic test system(s) for each
non‑COTS/NDI LRUs. If a particular unit under test (UUT) requires more
than one ATE device for conducting its required tests, the Contractor
must ensure the TPS for that UUT includes all hardware, software,
procedures for isolation and troubleshooting, etc., for each ATE device
which is involved in the test procedures. The Contractor must ensure the
test programs and the ATE are capable of isolating faults down to the
piece part level for each LRU provided as part of the system as follows:

-   Not less than 90% of all possible faults for each digital Printed
    Circuit Board (PCB)/LRU.

-   As a design goal, not less than 90% of all possible faults for each
    analog PCB/LRU.

-   The Contractor must provide updates/retrofits to the TPS, where the
    need for the change is generated by:

-   A result of failure to isolate the required percentage of the total
    number of possible faults during the TPS acceptance tests.

-   Hardware/firmware changes resulting from problems discovered in the
    repairable items and piece parts. (CDRL A106)

#### Automatic Test Equipment Requirements

The Contractor must deliver all software Test Program Sets and test
fixtures required to test/repair LRUs all on proposed Automatic Test
Equipment (ATE) hardware 6 months prior to the end of ICDLS. The
Contractor must install, debug, and demonstrate the capability of the
software and test fixtures to test all LRUs as outlined in the
transition plan.

### Training, Training Support, and Personnel Skills

#### Training

Training requirements associated with the procurement and deployment of
the WAAS is provided by the FAA.

#### Access to Contractor's Facilities and Data

The Contractor must permit FAA training personnel and/or their
designated representatives full access to the Contractor facility for
training development purposes, upon written or verbal notification from
the COTR with at least 30 calendar days advance notice of any visit. The
Contractor must grant access to any training development organization
under contract to the FAA to develop or assist in training program
development. The Contractor must provide FAA personnel or their
designated representatives access to any data that is to become FAA
property. This access includes data on system and/or equipment hardware,
software, and firmware.

#### Meetings/Conferences

The Contractor must provide facilities for meetings to support the FAA.
For estimating purposes, the Contractor must plan on six meetings at
their facility.

#### WTMS Spare Parts

The Contractor must assign WTMS spare parts delivered under the
LNAV/VNAV Phase to the WTMS to support FAA training activities. The
Contractor must provide ICDLS support for the WTMS in accordance with
SOW Section 4.1.4.2.1. The Contractor must make recommendations to the
FAA regarding the need to replenish the spare parts in to the depot that
have been assigned to the WTMS.

### Provisioning

Provisioning has been performed to support the LNAV/VNAV WAAS. To the
extent possible, the Contractor must utilize LNAV/VNAV provisioning to
satisfy requirements associated with Full LPV Performance. The
Contractor must provide provisioning recommendations to the WCRB.

For baseline changes to the WAAS, the Contractor must provide the
following data and service to the FAA (WCRB): The Contractor must
support and host Delta Provisioning Update Meeting(s) as required. The
Meeting must be held not later then 30 day after the configuration
audits performed in support of the detailed design review(s) and not
more then 45 days after approval of the first increment of LMI. The
Contractor must provide the following Data and Service:

-   The Contractor must have available for review one (1) complete set
    assembly and detail drawings for each item that appears on the
    Provisioning Part List (PPL) in PLISN with cross-reference list to
    part numbers in Technical Data Package (TDP).

-   The Contractor must have copies of the Government approved
    configuration audit documentation available for use as reference.

-   The Contractor must make available for the duration of the Meeting
    all equipment(s) on the contract.

-   The Contractor must furnish personnel and tools necessary to
    disassemble the equipment(s) to the extent required by the
    Government Provisioning Team.

-   The Contractor must ensure the participation of Contractor personnel
    with detailed knowledge of the subject mater they represent. E.g.
    provisioning documentation and technical documentation,
    hardware/software maintenance, engineering and system design, etc.

-   The Contractor must provide facilities, office space, conference
    room access to telephone/facsimile, etc for the Government
    provisioning team and the Contractor personnel participant in the
    Meeting will be provided to the Contractor prior to the conference.

At any time during the terms of this contract or any extension thereof
the Government reserves the right to order additional Delta Provisioning
Update Meeting(s) and updates to the LMI data that will be required to
support the provisioning process.

#### Spare Parts Peculiar

The Contractor must perform provisioning to identify, quantify, and
deliver all items defined as parts peculiar in accordance with
MIL-PRF-49506, Provisioning Requirements Statement. The Contractor must
document these items in the LMI database.

The Contractor must deliver additional spare parts peculiar as ordered
by the FAA. The Contractor must procure additional spare parts peculiar
as a result of WCRB direction. In the event that the FAA decides to
procure additional spare parts peculiar, fair and reasonable prices and
terms of delivery must be established by agreement between the
Contractor and the Contracting Officer. Such agreement will be set forth
in a modification to the WAAS contract.

The Contractor must provide bar code markings for deliverable WAAS Full
LPV Performance equipment for all spare LRUs. Markings are to comply
with Asset Identification Specification Version 2.4 dated November 18,
2003. (CDRL A073)

#### Prescreening

As ordered by the Government new equipment to the LNAV/VNAV baseline,
must be screen through the Defense Logistics Information Services (DLIS)
for National Stock Numbers (NSN) all information entered on the LMI data
Base (Item Identification). The Contractor's screening results must be
documented in the LMI Data Worksheet Data Table and must be no more than
60 days old when the LMI data is delivered. With Government approval,
the Contractor may use current PC based parts list/software program for
this requirement. After completing DLIS screening, the Contractor must
provide (contract option) data required by the Government for Item
Identification (FED-STD-5) for item not cataloged and complete design
change notices (DCNs) (A082).

Item identified as proprietary must be clearly marked and identified as
PROPRIETARY.

### Site Spares

####  Site Spares 

As ordered by the Government, the Contractor must prepare and deliver to
the Government a list of recommended site replaceable spares,
assemblies, and consumables for the WAAS Full LPV Performance
configuration at each site. The list must be in Contractor format and
must include each LRU noun nomenclature, NSN, part number,
manufacturer's CAGE code, and the unit price will that will charged to
the Government, Mean-Time-Between-Failure (MTBF) and recommended
quantity for each LRU. The Government reserves the right to order all,
more than, less, than, or none of the items and quantities recommended.
The Contractor must deliver the site spares ordered by Government with
each LNAV/VNAV WAAS.

### Packaging, Handling, Storage And Transportation (PHS&T)

#### Storage Requirements

It is anticipated no items will require storage at the FAALC during the
ICDLS period.

#### Hazardous Material Management Requirements

The atomic clock contains a small amount of cesium metal. The cesium
isotope used (cesium 133) is non-radioactive. However, because of its
reactive chemical properties, cesium is technically classified as a
hazardous material by the U.S. Department of Transportation (USDOT) and
the International Air Transport Association (IATA). During normal
handling, the atomic clock presents no danger since the cesium is
encased within a vacuum-sealed metal enclosure. However, the atomic
clock is subject to certain shipping regulations under Title 49 of the
Code of Federal Regulations (CFR), Section 172.101, which govern the
shipping case as well as its labeling. The Contractor must provide an
atomic clock with a tested and certified shipping case along with the
appropriate labels. During installation of the equipment, the Contractor
must be aware of the possibility of asbestos hazards in some of the FAA
buildings.

### Technical Data

Technical Data has been provided to support WAAS LNAV/VNAV. The
Contractor must provide additional technical data, to supplement
LNAV/VNAV data, to support WAAS Full LPV Performance requirements.

#### Support/Test Equipment Manuals

The Contractor must provide commercial manuals for the operation,
description, maintenance, and repair of the Contractor peculiar
furnished support/test equipment. In addition, the Contractor must
provide all original documentation delivered with the support/test
equipment,

#### Technical Data Package

##### Depot Level Repair Specifications

The Contractor must provide a copy of depot level limits and tolerances
for each individual LRU. These are criteria the Contractor uses to
validate the satisfactory operation of each individual LRU. (CDRL A107)

##### Technical Drawings and Associated Lists

The Contractor must provide commercial drawings and associated lists as
a part of the WAAS technical data package. (CDRL A108) (CDRL A109)

##### Technical Instruction Book

The FAA will update and maintain the Technical Instruction Book (TIB).
The maintenance instructions contained in the TIB will be of sufficient
detail to permit Government technicians to install, troubleshoot, and
repair the equipment. All tools, fixtures, and test equipment required
for installation and maintenance will be listed.

With each baseline approved by the FAA WCRB, the Contractor must provide
working data to support the FAA in updating the TIB after approval of
the scope analysis package and no later than 60 days prior to the
baseline cutover.

#### Contractor Support Transition Plan

The Contractor must prepare, submit for FAA review and approval, and
subsequently implement a Contractor Support Transition Plan (CSTP). The
CSTP establishes the procedures and means for the orderly transfer of
the system support activities from the Contractor to the FAA. (CDRL
A078). The Contractor must ensure the CSTP details the activities the
Contractor undertakes to assure a smooth transition from Contractor to
FAA operations, and the preparations, facilities, and personnel that the
FAA will require to assume responsibility for the conduct of all
services provided under ICDLS and SLES. The Contractor must ensure the
CSTP recommends the time required to ensure a smooth transition with
minimal interruption to repair activities. The CSTP may be submitted in
Contractor format. The Contractor must ensure the CSTP includes, but is
not limited to:

-   Any formal/OJT training/familiarization required to support the
    repair functions;

-   Activities, procedures and schedules for any necessary
    refurbishment, calibration, and acceptance of GFE/GFP/Contractor
    Acquired Property (CAP) prior to return to the FAA;

-   The detailed plan for shipment, installation, and checkout of any
    GFE/GFP/CAP at the designated FAA facility;

-   The duration and type of Contractor support required, if any, at the
    FAALC facilities during the depot repair startup;

-   The disposition and physical inventory of lay-in stock, to include
    all accounting records;

-   Operating methods to be employed to assure repair services during
    the transition period;

-   Method or procedure of transitioning management of the Vendor/OEM
    repair contracts to the FAA;

-   An estimated cost (based on the Contractor\'s prior experience) of
    managing vendor repair subcontracts for the life cycle of the
    system;

-   Post Production Support Analysis

-   Any recommendations for additional equipment, processes, and
    documentation which would be beneficial to the FAALC operation of
    the transitioned ICDLS;

-   Software support environment (SSE), system test facility (STF), and
    related documentation; and tools required to support and maintain
    the WAAS.

# Site Implementation

The Contractor must use the FAA designated Full LPV Performance sites
(as referenced in Section F of the contract) for the ground-based
equipment.

The Contractor must perform work according to the following table:

  --------------- ------------ ------------------ --------------- ----------------
  **EQUIPMENT**   **SITE       **SITE             **SITE          **EQUIPMENT
                  SURVEYS**    IMPLEMENTATION     PREPARATION**   INSTALLATION**
                               PLANS**                            

  Alaska WRS      FAA          FAA                FAA             FAA
  Sites                                                           

  Mexico WRS      Contractor   Contractor         FAA             FAA
  Sites                                                           

  Canada WRS      FAA          FAA                FAA             FAA
  Sites                                                           

  C&V (WMS)       Contractor   Contractor         Contractor      Contractor

  TCS             Contractor   Contractor         Contractor      Contractor
  --------------- ------------ ------------------ --------------- ----------------

The Contractor must supply the documentation, ground-based equipment,
equipment used to interface to the NICS or equivalent non-US
communications capabilities that will be provided as
Government-Furnished Service (GFS) for sites external to the US and
related resources to implement the Full LPV Performance WAAS. The
Contractor must provide, install, test, and support cutover of the new
equipment required for each operational update of the baseline of WAAS.
The Contractor must provide any tools and test equipment needed for
installing, testing, operating and maintaining the WAAS. The Contractor
must be responsible for compliance with applicable Federal Regulations
including but not limited to FCC Rules and Regulations and International
Rules and Regulations, concerning frequency coordination, licensing
actions, and related matters. All matters concerning coordination,
approval, and authorizations etc. with agencies external to the US will
be handled by the FAA.

## Site Surveys

Facility Site Surveys and FAA Surveys may be conducted at the same time
to facilitate communications and a common understanding of the
background environment. The results of the Site Survey must be submitted
as a PNB for approval IAW Section 3 of this SOW.

The Contractor must complete a facility Site Survey for each site as
directed in the table above, in order to acquire site-specific
information required for performance of the system implementation
activities.

###  Reserved

### Materiel

The Contractor must provide all materiel required for the installation
of all WAAS Full LPV Performance components. Such materiel must consist
of but not be limited to antennas (and mounts), racks, cabinets, circuit
conditioning, cables, and connectors. For facilities where the
Contractor will be installing equipment, the Contractor must also
furnish any equipment or electronics enclosures (including any
associated heating, ventilation, and air conditioning equipment)
required for any WAAS equipment that is to be installed outdoors
(outside of FAA facilities) and for any WAAS equipment that is to be
installed within FAA facilities that do not provide the environmental
conditions required by this WAAS equipment.

### Power

#### Cable and Connectors

The Contractor must determine, select, and provide cables and connectors
necessary to connect the WAAS equipment to the FAA-designated power
sources. For the equipment being installed by the Contractor, the
Contractor must install cables and connectors and ensure cable marking,
labeling, tracer indications and protection for unused power and radio
frequency (RF) outlets or receptacles is consistent with LNAV/VNAV
capability. The Contractor must ensure initial power installation is to
the building service power bus. Upon certification that the system meets
the AC power constraints in FAA-G-2100G, paragraph 3.1.1, the FAA will
switch the power connection to the critical power bus.

#### Standby Power

For equipment being installed by the Contractor, the Contractor must
provide standby power for the WAAS. The Contractor must provide WAAS
standby power for equipment, which includes but is not limited to units
such as uninterruptible power supplies, power conditioners, batteries,
and battery-backup power. The Contractor must ensure standby power is
available immediately (without interruption) upon failure of the primary
power source and must support operation for a period of at least four
hours.

#### Grounding

For equipment being installed by the Contractor, the Contractor must
ensure that all grounding is in accordance with FAA-STD-019B,
FAA-STD-020B, and the Full LPV Performance Specification. The Contractor
must ensure the ground wires utilize the same green wire tracer
indication for single and multipoint grounding as used in the LNAV/VNAV
Phase.

## Implementation Planning

The Contractor must prepare and submit a Site Implementation Plan (SIP)
for approval in PNB format for each new site, as described in the Table
included in Section 5, or any significant redesign of existing sites for
Full LPV Performance. The PNB must be delivered to the FAA, IAW Section
3 of this SOW, 60 days after approval of the Site Survey. For SIPs
produced external to the Contractor, the Contractor must review and
provide comments to the FAA no later than 14 days after receipt via
email to the Contracting Officer.

## Site Preparation

For new sites where the Contractor must perform site preparation work,
the work must be in accordance with the applicable FAA approved Site
Implementation Plans

## Equipment Installation

For equipment being installed by the Contractor, the Contractor must
install WAAS equipment in accordance with the approved Site
Implementation Plans. Upon completion of the Contractor installation
activities at each FAA site, the Contractor must be responsible for
clean-up and disposal at each applicable site of any shipping crates,
packing materials and related items not required for WAAS operation.

The Contractor must provide bar code marking for deliverable WAAS Full
LPV Performance equipment for all newly installed LRUs. Markings are to
comply with Asset Identification Specification Version 2.4 dated
November 18, 2003. (CDRL A073)

## As-Built Drawings

The Contractor must provide As-Built Drawings, for approval, 90 days
after SAT in PNB, IAW Section 3 of this SOW. For each new site added
where the Contractor performs the installation, the Contractor must
update the Government facility drawings to show the installed WAAS Full
LPV Performance configuration, including the Subsystems within all WAAS
sites. The Contractor must update the existing National Operations
Control Center (NOCC) as built documentation in WAAS PNB 107-1-3-2
including a review of the existing NOCC as built data, conduct a site
survey to gather data on current configuration, and update and release a
PNB updating the NOCC As-Built documentation.

## WAAS Disestablishment

If the WAAS contract is terminated without the election by the FAA to
purchase some or all of the WAAS equipment, the Contractor must be
responsible for the removal from FAA sites of any WAAS equipment and
related items not purchased by the FAA including but not limited to
receivers, processors, antennas, equipment enclosures, and Contractor
work-area furnishings.

# Government-Furnished Equipment 

The FAA will provide the Contractor the GFE in accordance with Section
H.4 of the contract.

## Communications System

Government furnished communications systems are listed in paragraph
3.5.1 of this SOW.

## Equipment and Support Space

### Equipment Space 

The FAA will provide up to fifty square feet for the installation of
WAAS equipment at WRS sites. The FAA will provide up to 150 square feet
for the installation of WAAS equipment at WMS sites. The FAA will
provide up to 100 square feet for the installation of the SGS equipment.
Internal facility space available for installation of WAAS equipment at
FAA facilities must be determined during Full LPV Performance facility
site surveys and will be subject to FAA coordination and approval via
NAS Change Proposals (NCPs)

### Support Space

At each facility at which WAAS equipment will be installed, the FAA will
provide up to sixty-five square feet of internal floor space for use in
on-site maintenance activities, storage of spare parts as well as
support and test equipment, and related purposes. Internal space
available for the Contractor\'s WAAS support activities will be
determined during facility site surveys and are subject to FAA
coordination and approval. The Contractor must be responsible for the
security of spare parts, support and test equipment, and related items
as long as the Contractor retains sole custody of said items. In cases,
if any, where physical security capabilities in excess of those normally
provided by the FAA are required, such as storage cabinets with locks,
the Contractor must provide these capabilities and furnishings.

## Environmental Control

Government facilities in which WAAS equipment may be installed will be
controlled to environmental condition I as specified in, FAA-G-2100G
paragraph 3.2.1.1.2 for outdoor equipment and paragraph 3.2.1.1.3 for
indoor equipment.

## Electrical Power and Termination

The FAA will provide normal alternating current (AC) electrical power.
Primary power will generally be available at FAA-provided power panels
in the form of 60 Hz three- phase 120/208V power or 60 Hz single-phase
120V power.

## Ground Termination

The FAA will provide access to the required facility power ground and
signal power ground buses for the Contractor-provided WAAS equipment.

## Documents

The FAA will provide available site documentation (e.g., site drawings
and building blueprints, geodetic survey information) to facilitate the
installation and operation of the WAAS upon written request from the
Contractor.

## Physical Security

The FAA will provide or coordinate security at Government sites and will
coordinate access to such through existing local security channels and
procedures (e.g., building passes). However, the FAA will not provide
physical security external to those sites (e.g., conduits or lines
routed from Government buildings to Commercially owned power or
telephone poles).

### Points-of-Contact

The FAA will identify a point-of-contact at each affected Government
facility for the coordination of activities related to the WAAS.

## Telephones

The FAA will provide access to existing Government telephones for use by
the Contractor personnel while on-site for the conduct of activities
related to the WAAS.

## Ground Monuments

The FAA will provide National Geodetic Survey (NGS) benchmarks or
suitable alternatives for each Full LPV Performance site.

# Second Level Engineering Support 

This section defines the Contractor\'s technical and management support
to the FAA in the Contractor\'s role of providing second level
engineering support (SLES) for the Wide Area Augmentation System (WAAS).
This includes engineering services to detect, investigate, verify, and
correct problems within the WAAS, and support the analysis, design, and
deployment of enhancements to the system as authorized or directed by
the FAA. The services described herein are provided to facilitate a
smooth transition of WAAS from development to Contractor-provided second
level engineering support to unassisted FAA support.

SLES *excludes* direct Contractor support to WAAS Operators and any
associated training unless associated with AOS coordinated Field
Support. Contractor depot repair, supply support, and coverage of NAILS
work scope are provided in Section 4.0 of the SOW and *are not part of
SLES*.

The Contractor\'s support to the FAA must include engineering services
to maintain the operational integrity of WAAS and provide an engineering
infrastructure to support the investigation and correction of problems,
and implementation of enhancements. The Contractor must provide
engineering services which include various layers of on-call and on-site
field support, detection and investigation of anomalous system behavior
or potential field problems, system performance monitoring, assessment,
and design, development, and test of modifications to repair or enhance
the system, and delivery of verified modifications consistent with the
processes described in Section 3.10 of the SOW.

The Contractor must ensure the engineering infrastructure includes
provision of the engineering and management expertise to assist the FAA
in maintaining and enhancing the WAAS, including the maintenance and
extension of laboratory assets, test environments, and associated
administrative services.

## Field Support

### Reserved

### Contract Award to Full LPV Performance 

The Contractor must ensure that complete and accurate contact
information for the second-level engineering support field personnel is
made available to the AOS for both on-call and administrative hours.

The Contractor must designate specific personnel to ensure that second
level engineering support is available to the AOS 24 hours a day, 7 days
a week.

The Contractor must provide engineering services when requested by the
AOS to support the SLES efforts at FAA field sites, the Contractor\'s
plant, or elsewhere, with skills in specific areas including, but not
limited to:

-   Anomaly Investigation / Analysis

-   Satellite navigation principles;

-   Telecommunications network applications~~,~~ engineering, and
    operation;

-   WAAS equipment (hardware, software, and firmware);

-   WAAS system operational, support modes, and procedures; and

-   Testing support.

### On-Call and Onsite Support

#### Administrative Support

The Contractor must provide engineering support during administrative
hours on a full time basis. Administrative hours are defined as
weekdays, 8:00 AM to 5:00PM PST, excluding Contractor published holiday
schedules.

#### On-call Support

The Contractor must respond to AOS within two (2) hours of the initial
request for engineering support.

The Contractor must render the necessary support to restore the system
to operation.

#### Onsite

The Contractor must provide onsite field assistance when requested by
AOS.

The Contractor must ensure that onsite assistance for high priority
problems is rendered within 24 hours. A problem categorized as high
priority typically will involve loss of Signal In Space (SIS) or a
significant loss or risk of loss of redundancy. Note: A longer response
time may be allowable, but must be coordinated with the FAA on a per
occurrence basis.

## Performance Monitoring

### Monitoring and Reporting

The Contractor must perform event and trend analysis of WAAS performance
parameters.

The Contractor must define other monitoring activities as needed to
fully characterize WAAS performance.

The Contractor must document, investigate, track, and disposition all
anomalies found in the course of monitoring WAAS performance.

The Contractor must report WAAS system performance including any anomaly
investigation activity weekly to the FAA (AOS). The format of this
report will be mutually agreed upon between the Contractor and the FAA
(AOS).

The Contractor must maintain the anomaly database and make the database
available to the FAA. The Contractor and the FAA will mutually agree on
the level of detail provided in the database for each anomaly.

The Contractor must define the performance monitoring during and
immediately following cutovers to new operational baselines including
new site installation, maintenance activities, and system upgrades.

The Contractor must make available all performance monitoring plans,
procedures, and devices to the FAA.

### Monitored Performance Parameters

The Contractor must monitor WAAS signal accuracy performance.

The Contractor must monitor WAAS integrity performance.

The Contractor must monitor WAAS availability performance.

The Contractor must monitor WAAS continuity performance.

The Contractor must monitor WAAS terrestrial communication circuit
performance.

##  Anomaly Investigation 

The Contractor must investigate the root cause of WAAS events, or
anomalies, that occur outside of expected system behavior or
performance, even if WAAS performance remains within specification
tolerances.

The Contractor must notify the FAA if an anomaly cannot be recreated. In
these cases, the Contractor may recommend closure of an anomaly report
due to lack of evidence. Such closures will be at the discretion of the
FAA.

The Contractor must report any anomalies to the FAA that are believed to
be a result of problems in GFE equipment (e.g. leased communication
lines, certain GUS components, etc.).

The Contractor must support the FAA in coordinating activities with
other GFE providers to resolve system anomalies.

## SLES Transition Support

### Contract Award to Full LPV Performance 

The Contractor must provide On-The-Job Training (OJT) for no more than
six FAA personnel at the Contractor's facility. This OJT must include,
but not be limited to: familiarization with WAAS procedures and
processes including activities involved with identification and
recognition of anomalous conditions, validation of anomalies, root cause
troubleshooting, corrective action tradeoffs/impact assessment,
interface to the WCRB, retesting, documentation updates, on-site
maintenance, configuration management practices, identification of items
requiring safety review and/or update, and performance monitoring.

The Contractor must provide a list of minimum WAAS job skill
qualifications for the start of OJT at the Contractor's facility.

The Contractor must ensure that OJT positions are available for AOS
personnel in key process areas to ensure the overall training needs of
AOS are satisfied.

The Contractor must also assist AOS in developing a recommended staffing
structure of engineering and administrative disciplines to perform and
manage these activities.

### Asset Transfer to AOS 

The Contractor must transfer FAA-owned assets (e.g., support and
maintenance environment) used by the Contractor to support SLES from the
Contractor\'s facility to AOS in Oklahoma City prior to Full LPV
Performance in accordance with Section 4.1.10.3 of this SOW.

# Operational Baseline Management 

The Contractor must adhere to the WAAS Change Control Process as
administered by the WCRB when modifying the WAAS operational baseline.

For modifications requiring equipment installations, the Contractor must
complete a facility survey of each WMS, WRS, and GUS location as
required in order to acquire site-specific information for system
implementation activities according to Section 5.0 of this SOW.

## Scope Analysis

The Contractor must perform a scope analysis, as directed by the FAA
(AOS), for each proposed change as initiated by contracts letter. (CDRL
A140)

### Problem Re-Validation

The Contractor must perform the activities to re-validate the reported
problem and that a need for change exists. The Contractor must notify
AOS if the reported problem and/or need for change cannot be
revalidated.

### Impact Assessment

The Contractor must perform a change impact analysis to determine what
elements within the system will be affected by the proposed change and
what supporting documentation will need to be updated. Such analysis
should identify the specific sections of system documentation that are
affected and provide a suggested approach for incorporating the changes.
Upon request, the Contractor must also provide written technical input
to support development of FAA Change Directives (e.g., System Support
Directives). Documents that may be affected include but are not limited
to those identified in the Product-Level Baseline. The Contractor must
identify the affected Computer Software Configuration Items (CSCIs),
Computer Software Components (CSCs), hardware components, and firmware
that require change and recommend how changes will be accomplished.

### Risk Assessment

The Contractor must assess the risk of implementing and fielding
modifications in the context of planned WAAS changes and the priority of
change implementation. If the change is part of an identified package of
changes, the Contractor must evaluate the implementation and fielding
risk given the other changes identified in the change package.

The Contractor must assess the potential for functional conflicts that
the change may introduce, examining each affected function or operation,
and adjust the implementation approach for risk avoidance or mitigation.
Where risks are unavoidable without excessive schedule or cost impact,
the risk factors must be clearly documented in the Scope Analysis for
consideration by the FAA.

The Contractor must rate the severity, likelihood, and overall risk of
each change package using criteria agreed upon by the Contractor and
FAA.

### Alternatives/Options

Where appropriate, the Contractor must develop solution alternatives or
options including an option for not implementing any solution. These
options must include all aspects of the Scope Analysis described herein.

The Contractor must also provide a recommendation that specifies a
preferred option and rationale for selecting it.

### Initial Test Approach

The Contractor must identify the initial approach to testing the change
prior to release according to the master integrated test plan (reference
Section 3.10 of this SOW). The test approach may be further refined or
modified during development and implementation. The approach must also
include identification of functionality that cannot be fully exercised
or tested within the Contractor\'s test facility. Risk associated with
not fully exercising functionality must be described in the Risk
Assessment portion of the analysis.

### Implementation Estimate

The Contractor must provide an estimate of the manpower, material, and
schedule to develop the change or enhancement.

The Contractor must identify any impacts to manpower, material, and
schedule - both positive and negative, associated with bundling a
particular change with other changes currently being considered.

The Contractor must provide a preliminary cost estimates and ESLOCs for
SLES changes by WPR and a mapping to WBS elements for Full LPV
Performance changes by WPR.

### Scope Analysis Report

The outputs of all scope analysis activities (Sections 8.1.1-8.1.6 of
this SOW) must be delivered to the FAA for consideration by the WCRB.
The specific format and details of this report must be delineated in the
CDRL. (CDRL A140)

### WCRB -- Initial Approval Support

The Contractor must present the findings of the scope analysis to the
WCRB.

## Detailed Design

For each change approved through the WCRB and as directed by the
Contracting officer, the Contractor must:

a)  Perform all change development activity utilizing the product-level
    baseline obtained from the FAA.

b)  Design changes for hardware and software for all changes approved by
    the WCRB. The Contractor must update product baseline documents for
    all changes approved by the WCRB.

c)  Provide engineering support and information associated with user
    document changes resulting from approved WCRB changes.

d)  Perform regression analysis and develop a verification/test approach
    for all changes including the development of modification acceptance
    criteria.

e)  Develop a cutover approach and identify risks for fielding. The
    Cutover approach must identify any and all special requirements for
    deploying the new baseline. When determining these requirements, the
    Contractor must take into account at least the following items: (a)
    upgrades must be accomplished with minimal risk to SIS
    interruption, (b) minimize the number of restarts of subsystems to
    reduce the risk of loss of SIS or availability, (c) avoid operator
    overload, and (d) minimize the impact on additional TCS bandwidth
    during the cutover transition. The Contractor must ensure the
    cutover approach has an appropriate and complete mechanism for
    rollback to an earlier baseline in the event of a problem.

f)  Verify/test where possible all hardware and software modifications
    and the associated cutover procedures. Where modifications and
    cutover procedures cannot be verified in the laboratory environment,
    the Contractor must identify residual risks for fielding.

g)  Conduct retests when a review of changes to hardware, software, and
    firmware indicate that prior test results are invalid or the impact
    on prior test results cannot be determined without repeating the
    test. The Contractor must conduct regression testing on those items
    and associated items that have previously been tested successfully
    and are subsequently modified.

h)  Provide documentation for each approved change to the product
    baseline according to Section 3.10.2 (Master Integrated Test Plan)
    of this SOW.

i)  Analyze and plan for the specific needs for implementing changes at
    each site affected by the change.

The Contractor, upon completion of the above change implementation
activities, must provide a completed WAAS Detailed Design Report to the
FAA for review and approval. This report must include, as a minimum, the
results of the change impact analyses; detailed information on the
changes made, and detailed information on the verification activities
associated with the changes. The specific format and details of this
report must be agreed upon jointly between the Contractor and the FAA.
(CDRL A141)

## Operational Baseline Change Delivery

The Contractor must conduct an RTCA/DO-178B compliance conformity review
for each update of the software product baseline.

The Contractor must support implementation of changes as requested by
the FAA. Support may include travel on-site to monitor or assist in
change installation.

The modified product baseline must be documented by the Contractor and
maintained in soft copy form on a shared file server for FAA access.
Updated baseline documentation must be made available to the FAA as
defined in the Contract Data Requirements List, and according to Major
or Minor upgrades as defined below:

Major Upgrade - Two major upgrades are defined for WAAS Full LPV
Performance: (a) the Architecture Upgrade, as described in paragraph
2.1.1, and (b) the Full LPV Performance Delivery, described in paragraph
2.1.2.

Minor Upgrade - Minor Upgrades provide for the deployment of field
problem corrections and enhancements, as approved by the WCRB and as
directed by the Contracting Officer, and serve as an incremental
approach to achieving higher levels of Full LPV Performance
functionality in support of Major Upgrades. The number and frequency of
minor upgrades must be mutually decided between the FAA and Contractor
during the course of Full LPV Performance. With the exception of
software deliverable media, all applicable documentation updates for
minor upgrades must be made available to the FAA in soft copy document,
format (PNB or other) to be agreed to by the FAA via a shared file
server to support timely review by the FAA. The Contractor must
incorporate FAA comments and post the updated document on the shared
file server. The Contractor must notify the FAA via email when the
documents are posted on the shared file server.

## Implementation Report

The Contractor must submit an Implementation Report to the FAA that
documents the first article, modified baseline (including all affected
product-level baseline documentation), reason for modifications,
required equipment, modification kit contents (if applicable),
installation instructions, and test after installation procedures as
delineated in the CDRL. (CDRL A142)

The Contractor must deliver the updated product baseline on a Compact
Disc that includes all products and artifacts for WCRB approved changes
concurrent with each delivery of A142.

#  Acronyms

AC Alternating Current

ACF Area Control Facility

AF Airway Facilities

AMS Acquisition Management System

AOR-W Atlantic Ocean Region -- West (INMARSAT)

AOS Operational Support Service

APML Associate Program Manager for Logistics

ARP Aeronautical Recommended Practice

ARTCC Air Route Traffic Control Complex

ATE Automated Test Equipment

C&V Corrections and Verification processor

CAP Contractor Acquired Property

CCA Common Cause Analysis

CCB Configuration Control Board

CDC Critical Design Considerations

CDRL Contract Data Requirements List

CFR Code of Federal Regulations

CI Configuration Item

CLIN Contract Line Item Number

CM Configuration Management

CMP Configuration Management Plan

COTS Commercial Off the Shelf

CRR Common Reference Receiver

CSC Computer Software Components

CSCI Computer Software Configuration Item

CPR Cost Performance Report

CSTP Contractor Support Transition Plan

CTA Critical Task Analysis

CWBS Contract Work Breakdown Structure

DID Data Item Description

DLIS Defense Logistics Information Services

DLSC Defense Logistics Services Center

DoD Department of Defense

DT&E Development Test and Evaluation

E&R Exchange and Repair

ECP Engineering Change Proposal

EOQ Economic Ordering Quantity

FAA Federal Aviation Administration

FAALC FAA Logistics Center

FAT Factory Acceptance Test

FCA Functional Configuration Audit

FCC Federal Communications Commission

FMEA Failure Modes and Effects Analysis

FMES Failure Modes and Effects Summary

FRDF Facility Reference Data File

FTA Fault Tree Analysis

GCCS Ground Communication and Control Segment

GEO Geostationary Earth Orbit

GFE Government Furnished Equipment

GFS Government Furnished Service

GPS Global Positioning System

GUS Geostationary Uplink Subsystem

HCI Human Computer Interface

HE Human Engineering

HEPP Human Engineering Program Plan

HFWG Human Factors Working Group

HMI Hazardously Misleading Information

HRs Hazard Records

HWCI Hardware Configuration Items

HTS Hazard Tracking System

IATA International Air Transport Association

IAW In Accordance With

ICD Interface Control Document

ICDLS Interim Contractor Depot Level Support

IDD Interface Design Documents

INMARSAT International Maritime Satellite

IOC Initial Operational Capability

IRS Interface Requirements Specification

ISP Integrated Support Plan

kbps Kilobits per second

L1 Radio Frequency Link 1 (GPS)

L2 Radio Frequency Link 2 (GPS)

L2C Radio Frequency Link 2 - Civilian (GPS)

L5 Radio Frequency Link 5 (GPS) LCN LSA Control Number

LNAV/VNAV Lateral Navigation/Vertical Navigation

LOF Loss of Function

LOGSA Logistics Support Activity

LORA Level of Repair Analysis

LPV Lateral Precision with Vertical Guidance

LRU Line Replaceable Unit

LSA Logistics Support Analysis

LSAR Logistics Support Analysis Record

MEDLL Multipath Estimation Delay Lock Loop

MIPS Master Integrated Program Schedule

MITP Master Integrated Test Plan

MOP Minimum Operating Procedure

MPT Manpower, Personnel, and Training

MSSR Monthly Schedule Status Report

MTBF Mean Time Between Failure

NAILS National Airspace Integrated Logistics Support

NAILSMT National Airspace Integrated Logistics Support Management Team

NAS National Airspace System

NCP NAS Change Proposal

NDI Non-Developmental Items

NDS Non-Developmental Software

NGS National Geodetic Survey

NICS NAS Interfacility Communications System

NSN National Stock Numbers

O&M Operations and Maintenance

OEM Original Equipment Manufacturer

OJT On-the-Job Training

PAT&E Production Acceptance Test and Evaluation

PC Personal Computer

PCA Physical Configuration Audit

PCB Printed Circuit Board

PHMI Probability of Hazardously Misleading Information

PHS&T Packaging, Handling, Storage And Transportation

PLCI Product Level Configuration Index

PM Periodic Maintenance

PMO Program Management Office

PNB Program Notebook

POM Program Overview Meeting

POR Pacific Ocean Region (INMARSAT)

PPL Provisioning Part List

PSAC Plan for Software Aspects of Certification

QA Quality Assurance

QA Qualitative Analysis

QSP Quality System Plan

R&M Reliability and Maintainability

RF Radio Frequency

RFD Request for Deviation

RFU Radio Frequency Uplink

RFW Request for Waiver

RMA Reliability, Maintainability and Availability

SAE Society of Automotive Engineering

SACIL Safety Assurance Configuration Item List

SAPR Safety Assurance Process Requirements

SAS Software Accomplishment Summary

SAT Site Acceptance Test

SCN Specification Change Notice

SDA Safety Directed Analysis

SDD Software Design Documents

SDP Software Development Plan

SDR System Design Review

SDRAM Synchronous Dynamic Random Access Memory

SDRL Subcontract Data Requirements List

SEMP System Engineering Master Plan

SEWG System Engineering Working Group

SGS Signal Generator Subsystem

SHA System Hazard Analysis

SIS Signal in Space

SLES Second-Level Engineering Support

SOW Statement of Work

SPIA Safety Process Input Analysis

SPR Software Problem Report

SPS Software Product Specification

SQAP Software Quality Assurance Plan

SPTD Supplementary Provisioning Technical Data

SRS Software Requirements Specification

SSE Software Support Environment

SSM System Safety Manager

SSP System Safety Program

SSPP System Safety Program Plan

SSPPR System Safety Program Progress Report

SSWG System Safety Working Group

STF Software Test Facility

STP Software Test Plan

TCN Terrestrial Communications Network

TIB Technical Instruction Book

T&E Test and Evaluation

TPM Technical Performance Measurement

TPS Test Program Set

TSO Technical Standard Order

UOQ Unit Ordering Quantity

U.S. United States

USDOT US Department of Transportation

UTC Universal Time Coordinated

UUT Unit Under Test

VDD Version Description Document

VRTM Verification Requirements Traceability Matrix

WAAS Wide Area Augmentation System

WBS Work Breakdown Structure

WCR WAAS Change Request

WCRB WAAS Change Review Board

WHAIL WAAS HE Action Items List

WIPP WAAS Integrity Performance Panel

WMS WAAS Master Station

WRS WAAS Reference Station

WTMS WAAS Training and Maintenance System

WUG WAAS Users Group