TECHNICAL SUPPORT SERVICES CONTRACT (TSSC-II)

MANAGEMENT/ADMINISTRATION HANDBOOK

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

June 11, 1998

**DEPARTMENT OF TRANSPORTATION**

**FEDERAL AVIATION ADMINISTRATION**

FOREWORD

The Federal Aviation Administration (FAA) has entered into a Technical
Support Services Contract (TSSC-II) with Raytheon Support Services
Company (RSSC), hereinafter referred to as the Contractor, to provide
supplemental technical support to Airway Facilities and Equipment
resources in their efforts towards implementation of the National
Airspace System (NAS).

The Contractor shall provide support in Site Selection analysis and
recommendation; Site Preparation; Environmental Remediation; and
Installation and Test. Work shall be performed at any location within
the 50 United States; including its possessions and territories, the
District of Columbia, and Puerto Rico as designated by the Government in
a Work Release.

Robert D. Long

Program Director for

NAS Transition and Integration

TABLE OF CONTENTS

CHAPTER 1. GENERAL INFORMATION [1-1](#general-information)

1-1. PURPOSE. [1-1](#purpose.)

1-2. DISTRIBUTION. [1-1](#distribution.)

1-3. BACKGROUND. [1-1](#background.)

1-4. ACRONYMS. [1-2](#acronyms.)

1-5. TERMINOLOGY. [1-2](#terminology.)

1-6. DOCUMENT REVISIONS. [1-2](#document-revisions.)

CHAPTER 2. SCOPE AND ADMINISTRATION [2-1](#scope-and-administration)

2-1. GENERAL. [2-1](#general.)

2-2. CONTRACT MANAGEMENT OVERVIEW. [2-2](#contract-management-overview.)

2-3. TYPES OF WORK. [2-4](#types-of-work.)

2-4. WORK RELEASE CATEGORIES. [2-6](#work-release-categories.)

2-5. CONTRACT TYPE SUPPORT SERVICES.
[2-9](#contract-type-support-services.)

2-6. SERVICES AVAILABLE. [2-10](#services-available.)

2-7. DAVIS‑BACON ACT WORK ACTIVITIES.
[2-10](#davisbacon-act-work-activities.)

2-8. CREW/TEAM CONCEPT. [2-11](#crewteam-concept.)

2-9. WORK ACTIVITIES EXCLUDED FROM TSSC-II.
[2-11](#work-activities-excluded-from-tssc-ii.)

2-10. CONTRACTOR FURNISHED MATERIEL (CFM), EQUIPMENT, AND SERVICES.
[2-12](#contractor-furnished-materiel-cfm-equipment-and-services.)

2-11. FAA MANAGEMENT OFFICIALS − DESIGNATION  AND  RESPONSIBILITIES.
[2-12](#faa-management-officials-designation-and-responsibilities.)

2-12. CONTRACT PERFORMANCE EVALUATION.
[2-19](#contract-performance-evaluation.)

2-13. CUSTOMER SATISFACTION SURVEYS.
[2-21](#customer-satisfaction-surveys.)

CHAPTER 3. FISCAL PROCEDURES [3-1](#fiscal-procedures)

3-1. GENERAL. [3-1](#general.-1)

3-2. TSSC-II PROGRAM MANAGEMENT FUNDING.
[3-1](#tssc-ii-program-management-funding.)

3-3. TSSC-II PROJECT FUNDING. [3-2](#tssc-ii-project-funding.)

3-4. IDENTIFYING TSSC-II PROJECTS. [3-2](#identifying-tssc-ii-projects.)

3-5. TSSC-II AUTHORIZED EEP DESCRIPTIONS AND NUMBERS.
[3-5](#tssc-ii-authorized-eep-descriptions-and-numbers.)

3-6. PREPARATION OF ESTABLISHMENT ENGINEERING PLAN DATA SHEETS.
[3-8](#preparation-of-establishment-engineering-plan-data-sheets.)

3-7. PROCUREMENT REQUEST. [3-10](#procurement-request.)

3-8. NATIONAL (TSSC) PROGRAM OFFICE PROCESSING.
[3-12](#national-tssc-program-office-processing.)

3-9. CONTRACT MODIFICATION DISTRIBUTION.
[3-12](#contract-modification-distribution.)

3-10. MODIFICATION SCHEDULE. [3-13](#modification-schedule.)

CHAPTER 4. WORK RELEASE PROCESS [4-1](#work-release-process)

4-1. GENERAL. [4-1](#general.-2)

4-2. OBJECTIVE OF WORK RELEASES. [4-1](#objective-of-work-releases.)

4-3. TYPES OF WORK RELEASES. [4-1](#types-of-work-releases.)

4-4. PRELIMINARY WORK RELEASE (PWR).
[4-3](#preliminary-work-release-pwr.)

4-5. CREATING A NEW WR - PWR. [4-4](#creating-a-new-wr---pwr.)

4-6. PREPARATION OF WR SECTION A COVER SHEET.
[4-8](#preparation-of-wr-section-a-cover-sheet.)

4-7. WORK RELEASE PLAN. [4-20](#work-release-plan.)

4-8. EVALUATION OF THE CONTRACTOR\'S WORK RELEASE PLAN.
[4-22](#evaluation-of-the-contractors-work-release-plan.)

4-9. ISSUING THE FWR. [4-23](#issuing-the-fwr.)

4-10. PROCESSING REVISIONS TO A WR.
[4-24](#processing-revisions-to-a-wr.)

4-11. WR CHANGE ACTION PROCESS. [4-25](#wr-change-action-process.)

4-12. SCHEDULING. [4-33](#scheduling.)

4-13. PRODUCT/WORK ACCEPTANCE. [4-33](#productwork-acceptance.)

4-14. WR CLOSE-OUT AND RECORDKEEPING.
[4-34](#wr-close-out-and-recordkeeping.)

4-15. F&E PROJECT CLOSE-OUT (widely called Capitalization).
[4-37](#fe-project-close-out-widely-called-capitalization.)

CHAPTER 5. CONTRACTOR RESPONSIBILITIES
[5-1](#contractor-responsibilities)

5-1. SCOPE. [5-1](#scope.)

5-2. RSSC'S OVERALL MANAGEMENT RESPONSIBILITIES.
[5-1](#rsscs-overall-management-responsibilities.)

5-3. TSSC PERSONNEL/STAFFING. [5-1](#tssc-personnelstaffing.)

5-4. TSSC OFFICE LOCATIONS. [5-2](#tssc-office-locations.)

5-5. QUALITY CONTROL. [5-2](#quality-control.)

5-6. STANDARDS OF CONDUCT. [5-2](#standards-of-conduct.)

5-7. SECURITY REQUIREMENTS. [5-3](#security-requirements.)

5-8. TSSC EMPLOYEE IDENTIFICATION. [5-5](#tssc-employee-identification.)

5-9. SAFETY. [5-5](#safety.)

5-10. PROGRAM STATUS REVIEW (PSR) MEETINGS.
[5-6](#program-status-review-psr-meetings.)

5-11. WRITTEN ALERTS. [5-6](#written-alerts.)

CHAPTER 6. SPECIAL REQUIREMENTS/SERVICES
[6-1](#special-requirementsservices)

6-1. RECRUITMENT AND ORGANIZATIONAL ACTIVITIES.
[6-1](#recruitment-and-organizational-activities.)

6-2. ORGANIZATIONAL CONFLICTS OF INTEREST.
[6-1](#organizational-conflicts-of-interest.)

6-3. SUBCONTRACTING REQUIREMENTS. [6-2](#subcontracting-requirements.)

6-4. SUBCONTRACTORS/CONSULTANTS/INTERDIVISIONAL TRANSFERS.
[6-2](#subcontractorsconsultantsinterdivisional-transfers.)

6-5. SUBCONTRACTING GOALS FOR SMALL BUSINESSES (SB), SMALL DISADVANTAGED
BUSINESSES (SDB), AND WOMEN-OWNED BUSINESSES (WOB).
[6-3](#subcontracting-goals-for-small-businesses-sb-small-disadvantaged-businesses-sdb-and-women-owned-businesses-wob.)

6-6. BONDING AND INSURANCE. [6-3](#bonding-and-insurance.)

CHAPTER 7. INVOICE PAYMENTS [7-1](#invoice-payments)

7-1. INVOICE PREPARATION, BILLING CYCLE, AND SUBMISSION.
[7-1](#invoice-preparation-billing-cycle-and-submission.)

7-2. INVOICE CERTIFICATION AND PAYMENT.
[7-1](#invoice-certification-and-payment.)

CHAPTER 8. TSSC FIELD INTERFACES [8-1](#tssc-field-interfaces)

8-1. GENERAL. [8-1](#general.-3)

8-2. COORDINATION WITH THE AF ORGANIZATION.
[8-1](#coordination-with-the-af-organization.)

8-3. SYSTEM MANAGEMENT OFFICES (SMO) AND OR SMO MANAGEMENT FIELD OFFICE
INTERFACE.
[8-3](#system-management-offices-smo-and-or-smo-management-field-office-interface.)

8-4. FACILITY RESPONSIBILITY. [8-4](#facility-responsibility.)

8-5. NOTICE TO AIRMAN (NOTAM) ISSUANCES.
[8-6](#notice-to-airman-notam-issuances.)

8-6. CONTRACTOR ACCEPTANCE INSPECTION (CAI).
[8-8](#contractor-acceptance-inspection-cai.)

8-7. FACILITY COMMISSIONING/DECOMMISSIONING.
[8-9](#facility-commissioningdecommissioning.)

8-8. LIAISON ACTIVITIES. [8-9](#liaison-activities.)

CHAPTER 9. TSSC EXTERNAL RELATIONSHIPS
[9-1](#tssc-external-relationships)

9-1. GENERAL. [9-1](#general.-4)

9-2. AIRPORT SPONSORS/AUTHORITIES. [9-1](#airport-sponsorsauthorities.)

9-3. FACILITY SITE PROPERTY OWNERS.
[9-2](#facility-site-property-owners.)

9-4. UTILITY COMPANIES. [9-2](#utility-companies.)

9-5 OTHER GOVERNMENT CONTRACTS, CONTRACTORS & ORGANIZATIONS.
[9-2](#other-government-contracts-contractors-organizations.)

9-6. OTHER. [9-2](#other.)

CHAPTER 10.LOGISTICS [10-1](#logistics)

10-1. GENERAL. [10-1](#general.-5)

10-2. GOVERNMENT PROVIDED SERVICES.
[10-1](#government-provided-services.)

10-3. USE OF GOVERNMENT FACILITIES AND EQUIPMENT.
[10-2](#use-of-government-facilities-and-equipment.)

10-4. SMO LEVEL SUPPORT AND CONDITIONS.
[10-5](#smo-level-support-and-conditions.)

10-5 MATERIEL MANAGEMENT. [10-6](#materiel-management.)

CHAPTER 11.FAA TECHNICAL SUPPORT TO TSSC
[11-1](#faa-technical-support-to-tssc)

11-1. GENERAL. [11-1](#general.-6)

11-2. FAA INTERVENTION. [11-1](#faa-intervention.)

11-3. SMO SUPPORT. [11-2](#smo-support.)

11-4. REGIONAL OFFICE TECHNICAL SUPPORT.
[11-3](#regional-office-technical-support.)

11-5. FAA LOGISTICS CENTER SUPPORT.
[11-3](#faa-logistics-center-support.)

11-6. FAA HEADQUARTERS TECHNICAL ASSISTANCE.
[11-3](#faa-headquarters-technical-assistance.)

11-7. TRAINING SUPPORT. [11-4](#training-support.)

**APPENDIX 1. LIST OF ACRONYMS**

**APPENDIX 2. TSSC OFFICE LOCATIONS**

**APPENDIX 3. ATTACHMENT J.002, LIST OF CANDIDATE PROJECTS**

**FOR WORK RELEASES**

# GENERAL INFORMATION

## 1-1. PURPOSE. {#purpose. .unnumbered}

This Technical Support Services Contract (TSSC-II)
Management/Administration Handbook serves as a resource for the
**Technical Support Services Contract, DTFA01-95-C-00015, awarded to
Raytheon Support Services Company (RSSC), on June 22, 1995.** The
Contract is referred to as the **TSSC-II**, and is a cost-plus-fixed-fee
(CPFF) contract with a maximum period of performance of seven years: a
three-year base period with two, two-year options, if exercised.

The purpose of the TSSC-II Management/Administration Handbook (Handbook)
is to serve as a resource for personnel involved in the management and
administration of the TSSC-II. The **Contract is the governing document
in all situations**; the Handbook is to be used as a supplement to the
Contract. Questions regarding the contents of the Handbook should be
directed to the TSSC Program Office for clarification.

## 1-2. DISTRIBUTION. {#distribution. .unnumbered}

This order is distributed to the division level in Airway Facilities,
and Office of Acquisition in Washington ; to the division level in the
FAA Logistics Center at the Aeronautical Center; to the division level
in the Logistics division and Facilities Management division at the
Technical Center; to the branch level in the regional Airway Facilities
divisions; and to all Airway Facilities field offices with a standard
distribution.

## 1-3. BACKGROUND. {#background. .unnumbered}

The Federal Aviation Administration (FAA) has entered into a Technical
Support Services Contract (TSSC) with Raytheon Support Services Company
(RSSC), hereinafter referred to as the Contractor, to provide
supplemental technical support to Airway Facilities and Equipment
resources in their efforts towards implementation of the National
Airspace System (NAS).

The Contractor shall provide support in Site Selection analysis and
recommendation; Site Preparation; Environmental Remediation; and
Installation and Test. Work may be performed at any location within the
50 United States; including its possessions and territories, the
District of Columbia, and Puerto Rico as designated by the Government in
a Work Release. Work may also be performed at locations worldwide under
agreements pertaining to air transportation system facilities and
equipment in foreign countries.

## 1-4. ACRONYMS.  {#acronyms. .unnumbered}

Appendix 1 of this Handbook provides the list of the acronyms and
definitions used throughout this document.

## 1-5. TERMINOLOGY. {#terminology. .unnumbered}

Throughout this document, the term "regions" refers to the nine FAA
regions (including ANI Service Implementation Centers located in each
region), the Mike Monroney Aeronautical Center and the FAA Technical
Center. The term \"head- quarters\" refers to the FAA National
headquarters located in Washington, DC.

In addition, use of the phrase CO/ACO shall mean "the Contracting
Officer and/or the Administrative Contracting Officer." Similarly, the
term TO/ATO shall mean \"the Technical Officer and/or the Associate
Technical Officer*.*\"

## 1-6. DOCUMENT REVISIONS. {#document-revisions. .unnumbered}

The Management/Administration Handbook will be updated as required. Any
errors or ambiguities detected by the users should be brought to the
attention of the TSSC Program Office so that corrections can be
incorporated in subsequent revisions. Comments and suggestions are
invited and would be appreciated.

# SCOPE AND ADMINISTRATION

## 2-1. GENERAL. {#general. .unnumbered}

a.  The FAA has entered into a Technical Support Services Contract
    (TSSC-II) to support implementation of the Federal Aviation
    Administration\'s (FAA) Facilities and Equipment (F&E) programs in
    the Aviation System Capital Investment Plan.

b.  The Government will initiate and authorize work under the Contract
    by issuing Work Releases (WRs).

c.  Under the Contract terms, RSSC shall furnish and make available all
    professional, technical, and support labor; management; services;
    supplies; materiel; data; and facilities required to accomplish all
    efforts ordered through the issuance of WRs.

d.  RSSC is guaranteed a minimum of 100,000 direct labor hours of effort
    during the first Contract year of the base performance period.

e.  This is not a requirements Contract and the Government may, at its
    own discretion, utilize in‑house capabilities or other contractual
    vehicles to perform any work identified as a requirement within the
    Contract.

f.  RSSC is required to use the most current version, as well as future
    publications of FAA standards, Orders, notices, and standard
    drawings and specifications.

g.  Work efforts will cover the following work areas: (See paragraph 2-3
    of this chapter.)

```{=html}
<!-- -->
```
(1) Facility site selection analysis and recommendations.

(2) Site preparation.

(3) Environmental remediation.

(4) Installation and test related to CIP programs.

```{=html}
<!-- -->
```
h.  Work may be performed under the TSSC-II at any location within the
    50 United States; including its possessions and territories, the
    District of Columbia, and Puerto Rico as designated by the
    Government in a Work Release. Work may also be performed at
    locations worldwide under agreements pertaining to air
    transportation system facilities and equipment in foreign countries.

i.  WRs will be prepared by the Government in accordance with procedures
    described in chapter 4 of this Handbook.

j.  No costs shall be incurred in the performance of the Contract that:

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

```{=html}
<!-- -->
```
(1) Are not in accordance with the Federal Acquisition Regulations (FAR)
    Part 31.

(2) Have not been authorized in accordance with properly issued and
    executed WRs.

```{=html}
<!-- -->
```
k.  Only those activities directly related to and/or in support of the
    NAS may be the subject of WRs issued under this Contract.

l.  List of Candidate Projects for Work Releases, Section J, Attachment
    J.002 of the Contract, contains a list of projects from which the
    Government will select efforts that RSSC shall accomplish. (See
    Appendix 3 for Attachment J.002.)

m.  Section J, Attachment J.002 (Appendix 3) shall not be considered to
    be all-inclusive of project work that may be accomplished under the
    Contract and shall be subject to change by the Government to reflect
    additions and/or deletions to the list of projects made during the
    annual updates to the CIP.

n.  The general types of work stipulated in paragraph 2-3 of this
    chapter shall not change.

o.  Selection of projects shall be at the sole discretion of the
    Government.

```{=html}
<!-- -->
```
k.  RSSC is not authorized to perform any work outside the scope of the
    Statement of Work (SOW). In the event RSSC has concerns about tasks
    that may be outside the scope of work of the Contract, RSSC should
    notify the Contracting Officer/Administrative Contracting Officer
    (CO/ACO) for resolution.

```{=html}
<!-- -->
```
p.  While technical direction from the FAA may be necessary from time to
    time, the Contractor will ensure adherence to guidance concerning
    technical direction contained within the Contract.

## 2-2. CONTRACT MANAGEMENT OVERVIEW. {#contract-management-overview. .unnumbered}

The following sections provide an overview of the pertinent
administration items to assist in the management of the Contract.

a.  Management of the TSSC-II includes, among other functions:

```{=html}
<!-- -->
```
(1) Responsibility for the planning, funding, fiscal and technical
    control.

(2) Development and issuance of WRs.

(3) Scheduling and monitoring of project status.

(4) Certification of work accomplished.

(5) Evaluation of project and/or overall Contract performance.

```{=html}
<!-- -->
```
b.  FAA management of the TSSC-II will be a coordinated effort, with
    designated officials having specific management responsibilities as
    described in paragraph 2-11 of this chapter.

```{=html}
<!-- -->
```
b.  Since TSSC-II is a cost‑plus‑fixed‑fee (CPFF) Contract, RSSC is
    entitled to reimbursement for costs incurred that are allowable,
    allocable, and reasonable in accomplishing authorized work or
    providing authorized equipment, materiel, or services.

c.  Consistent interaction and cooperation among FAA and RSSC personnel
    are essential.

d.  All actions to be taken by the FAA or RSSC shall be in the
    Government\'s best interest, costs and other factors considered.

e.  RSSC is entitled to be paid a fee, the basis and amount of which was
    established during Contract negotiations.

f.  Contractor Labor and Travel (CL&T) vs. Davis-Bacon Act Construction
    Subcontracting (Davis-Bacon). CL&T and Davis-Bacon fees will be
    separately identified on the invoices submitted by RSSC.

```{=html}
<!-- -->
```
(1) CL&T

The fee earned by RSSC is determined by the number of fee credit hours
worked. The percentage used to calculate fee will vary for the base
Contract period and the two option periods. For the purposes of TSSC-II,
the term "fee credit hours\" means the following:

(a) Direct labor hours of RSSC\'s personnel for which RSSC is entitled
    to reimbursement as a direct cost under the Contract.

(b) Direct labor hours of the personnel of any first‑tier subcontractor
    (other than a subcontractor performing Davis‑Bacon work as that term
    is defined in the Contract, provided that:

```{=html}
<!-- -->
```
1.  The costs for such subcontract labor hours are chargeable to RSSC as
    a direct cost under a cost-reimbursement or a fixed‑rate labor hour
    sub­contract and are allowable costs under the Contract (examples
    would be contract service personnel and purchased labor).

2.  RSSC has obtained the written approval of the CO/ACO for such
    subcontract prior to award of the subcontract.

```{=html}
<!-- -->
```
(2) DAVIS-BACON

The fee earned by RSSC is determined by the dollar value of Davis-Bacon
subcontractor effort performed. The percentage used to calculate fee
will not vary for the base contract period and the two option periods.

## 2-3. TYPES OF WORK. {#types-of-work. .unnumbered}

Work under this Contract shall include efforts of the types indicated
below:

a\. **Site Selection.**

(1) Provide analysis and recommendations, including the application of
    various technical criteria, regulatory criteria,

(2) cost benefit considerations, to help determine optimum specific
    facility sites within an FAA-designated area.

(3) Assist FAA personnel in the selection of geographical sites required
    for FAA NAS implementation.

```{=html}
<!-- -->
```
(a) While RSSC assistance and recommendations will be sought, ultimate
    site selection decisions rest solely with FAA personnel.

(b) Various design, procurement, management, and coordination efforts
    needed to plan, accomplish, and monitor tasks of this nature shall
    be required.

b\. **Site Preparation.**

(1) Provide resources required for the development or adaptation of
    site-specific or standard designs to conduct construction activities
    that will include but are not limited to the following:

```{=html}
<!-- -->
```
(a) Installation of concrete footings, piers, slabs or pads.

(b) Excavation and trenching.

(c) Access road, parking area, and walkway construction and paving.

(d) Building construction repair, modification, and/or modernization,
    including electrical and mechanical systems and architectural
    finishes.

(e) Tower erection, i.e., microwave link, radar, and towers.

(f) Cable system installation related to antenna, control, fiber optic,
    power, and signal functions.

(g) Facility security system installation.

(h) Utility and power distribution system installation.

(i) Site restoration or demolition.

(j) Removal and preparation for disposition of systems and equipment.

\(2\) Various other design, procurement, management, and coordination
efforts needed to plan, accomplish, and monitor tasks of this nature may
also be required and will be delineated within individual WRs.

c\. **Environmental Remediation.**

(1) Provide resources for the performance of environmental/hazardous
    material remediation for programs/projects to ensure environmental
    compliance. Remediation efforts may include, but are not limited to
    the following:

```{=html}
<!-- -->
```
(a) Fuel tank spills/fuel tank removal.

(b) Asbestos, lead-based paint, and PCB removal.

(c) Contaminated material cleanup.

(d) Proper disposal/documentation of contaminants.

\(2\) Work will typically include site surveys by qualified/certified
personnel, who:

(a) Are knowledgeable of all applicable federal, state, and local
    regulations.

(b) Will locate, identify, and/or quantify material, chemicals, or other
    compounds.

(c) Will obtain all required permits and certifications for remediation.

(d) Will develop and implement all engineering packages required to
    accomplish the efforts.

(e) Will prepare all required environmental documentation, such as
    assessments and impact statements.

\(3\) Remediation may include actual disposal of hazardous material or
the independent oversight of environmental remediation activities as
performed by other contractors.

\(4\) In addition, various other design, procurement, management, and
coordination efforts may be needed to plan, accomplish, and monitor
tasks of this nature.

d\. **Installation and Test.**

(1) Provide resources for:

```{=html}
<!-- -->
```
(a) The development of site-specific designs, or adaptation of standard
    designs.

(b) The conduct of electronic installation activities, which may
    include, but not be limited to, the following:

```{=html}
<!-- -->
```
1.  Development of equipment installation designs.

2.  Purchase/assembly/rehabilitation of equipment/materiel in support of
    installation work.

3.  Relocation/modification of operational electronic systems and
    equipment.

4.  Placement of equipment.

5.  Electronic cable system installation related to antenna, control,
    fiber optics, power, and signal functions.

6.  Adjustment of equipment to specified operating parameters.

7.  Documentation of equipment parameters.

8.  Initial testing of equipment.

9.  Troubleshooting/performance resolution and coordination.

10. Preparation for flight inspection/certification.

11. Facility cleanup.

12. Removal of obsolete electronic cables and equipment.

13. Revision of engineering drawings (\"redline\" and \"as built\").

\(2\) In addition, various other design, procurement, management and
coordination efforts needed to plan, accomplish, and monitor tasks of
this nature may be required.

## 2-4. WORK RELEASE CATEGORIES. {#work-release-categories. .unnumbered}

a\. **General.**

All work to be accomplished under the TSSC-II will be authorized by a
national or regional Work Release (WR). Regional WRs are further defined
as regional specific and regional general. Procedures for WR preparation
are presented in chapter 4 of this Handbook.

b\. **National Category.**

(1) Work to be accomplished in this category includes projects that are
    national in scope and/or cut across regional boundaries.

(2) TSSC program management for headquarters and the regions is issued
    under a National WR. See Work Assignments below for an example of a
    National WR.

c\. **Regional Categories.**

Regionally issued WRs will typically be used when the work to be
accomplished consists of a project or series of projects to be performed
within a single region. These WRs will normally fall into one of two
basic types: regional specific or regional general.

(1) **Regional Specific.**

Regional specific WRs will cover work related to the implementation of
specific systems or equipment to be utilized in the NAS. Work in this
category will culminate in the installation and/or commissioning of a
facility or facilities, or in the completed preparation of a site or
facility to enable installation of equipment by FAA or turnkey
contractor personnel.

\(2\) **Regional General.**

(a) Regional general WRs will typically represent a requirement for:

```{=html}
<!-- -->
```
1.  A limited project deliverable; or

2.  A quantity of facilities and equipment (F&E) effort in specific work
    disciplines.

\(b\) The nature of regional general work is such that RSSC shall be
required to perform an identifiable task, or series of tasks, and
produce an identifiable product. Work in this category would normally
consist not of a total effort, but rather of accomplishing one or more
tasks in the overall process of facility implementation. This work would
not normally culminate in the final installation of equipment or
commissioning of a facility.

\(c\) WRs issued for this type of effort will specify the nature of the
work to be accomplished, the type and length of effort, and the specific
F&E disciplines required.

\(d\) See Work Assignments below for examples of regional general WRs.

d\. **Work Assignments.**

Work Efforts will encompass a wide variety of support functions.
Detailed specifications for work efforts will be provided by the
Government to RSSC via Preliminary WRs (PWRs). PWRs will enable RSSC to
develop technical proposals in the form of WR Plans, as well as cost
estimates.

\(1\) **National and Regional Specific WRs.** The work efforts will
usually fall into any one or all of the activities described below:

(a) Providing for site selection analysis and recommendations, site
    design adaptation and preparation, modernization, relocation, and/or
    upgrading of all types of F&E encompassed by the NAS (ultimate work
    to be accomplished by RSSC, FAA F&E in-house personnel, or other
    subcontractors).

(b) Performing site selection and site preparation studies and cost
    estimates required for alteration, relocation, installation, and/or
    inspection of F&E. Performing site preparation work when so
    directed.

(c) Providing technical support services required for the establishment,
    installation, tune‑up, test, relocation, modernization,
    refurbishment, improvement, and modification of F&E. Participating
    in Joint Acceptance Inspections (JAI) and/or flight inspections as
    required.

(d) Providing technical assistance in meeting environmental compliance
    for existing facilities. Participating in identification of
    materials, chemicals, and other compounds that are considered
    hazardous in nature. Assisting in remediation of these items to
    include oversight of disposal as appropriate.

(e) Providing technical services to prototype, test, document, and/or
    install modifications to NAS facilities for service improvement,
    maintainability, and/or supportability. Services include
    use/development of Automated Test Equipment (ATE), Test Program Sets
    (TPS), and related interface hardware for facility/Lowest
    Replaceable Unit (LRU) diagnostics.

\(2\) **Regional General WRs.** Work efforts in this category will
usually fall into any one or all of the categories described below:

(a) Providing technical personnel to support specified test activities.

(b) Performing field construction or installation surveillance (site
    construction supervisor or Resident Engineer \[RE\]).

(c) Providing field evaluations (such as environmental assessments
    and/or surveys).

(d) Providing electronic installation and construction support.

(e) Providing as-built drawings (drafting clean-ups).

(f) Providing support for rehabilitation of equipment.

e\. **Examples of WRs.**

\(1\) The Leapfrog project is a good candidate for a National WR. The
project involves replacing airport surveillance radar (ASR) 4/5/6s with
7/8/9s. The Leapfrog project involves equipment located in more than one
region, nationwide, and some equipment transfer from region to region.
RSSC crews, after becoming familiar with and obtaining knowledge of the
task required, would not have to "re-learn" the task, saving time and
cost to the Government. Their crews would also acquire an expertise of
the task that increases the quality of the project. The National Program
Manager would manage the project by planning and coordinating the entire
project for standardization, providing interregional coordination, and
conveying lessons learned from one site to another. The National Program
Manager does the paperwork and provides funding, yet the task is
accomplished in the field.

\(2\) Another candidate project for an National WR would be a one-time
project, such as the installation of a limited number of airport surface
detection equipment (ASDE-3) project. The project required the
installation of a limited number of ASDEs, only one or two in some
regions, four or five in others. The task needed to be completed once
(is not likely to be done again) but involved many locations throughout
all regions. However, the task was done by issuing Regional WRs. Instead
of having one crew acquire the knowledge and use that knowledge on
subsequent design and installations, thus decreasing the learning curve,
each region used crews with no previous ASDE experience. This created
cost overruns and schedule delays.

\(3\) The fuel tank removal and replacement projects are good candidates
for a Regional Work Release. Each project is site-specific with a number
of projects to be completed within each region.

## 2-5. CONTRACT TYPE SUPPORT SERVICES.  {#contract-type-support-services. .unnumbered}

a\. **TSSC-II is a support services Contract. No personal services shall
be performed under this Contract. While Government employees may, and
should, oversee contract task performance, employer‑employee or
supervisor‑subordinate relationships between Government and RSSC
personnel are prohibited.** To avoid situations that may lead to a
personal services relationship, Government employees are to follow the
guidelines listed below:

(1) **Do not** provide direct, daily supervision of RSSC employees.
    RSSC's representative (the RSSC supervisor) will receive work from
    the FAA and will supervise the RSSC employees. Deal with RSSC's
    supervisor in any matters affecting direction or supervision of RSSC
    employees.

(2) **Do not** provide any written or oral evaluation of RSSC employees'
    performance. Comments regarding any individual RSSC employee's
    performance should be forwarded to the RSSC supervisor.

(3) **Do not** assign work to RSSC on a daily basis. Work assignments
    should be as long-planned as possible.

(4) **Do not** permit a FAA supervisor to maintain close, daily contact
    with RSSC employees as they perform their assignments. Such a
    relationship can be perceived as supervision, unlike a more distant
    and general oversight of RSSC operations.

(5) **Do not** permit the RSSC employees to present themselves as
    Government employees or use FAA routing symbols.

(6) **Do not** permit RSSC employees to state orally or in writing that
    they are acting on behalf of the Government.

(7) **Do not** involve the FAA in the selection of RSSC personnel.

(8) **Do not** use RSSC employees to fill any FAA vacancies. RSSC
    personnel cannot substitute as replacements in vacant positions and
    cannot assume any FAA decision-making functions.

(9) **Do** have RSSC employees identify themselves as RSSC employees,
    and have them specify the name of the company for which they work
    when communicating with a third party in connection with this
    Contract.

b\. The CO or ACO should be notified for issues of clarification when
any situation arises that appears to create a personal services
relationship between the Government and any RSSC employee.

## 2-6. SERVICES AVAILABLE. {#services-available. .unnumbered}

TSSC-II will provide a wide range of services that may include
installation planning (only after a specific site is identified by the
FAA), equipment installation, tune‑up and testing, minor construction,
resident engineering work, site selection analysis and recommendation,
adaptation of site specific survey and design data, and engineering
studies below the level of typical architecture and engineering (A&E)
activity. For example, regional or national stan­dard designs would be
considered as outside the scope of the TSSC-II. Adaptation of standard
designs for site-unique requirements or one-of-a-kind design would
normally fall within the scope of the TSSC. Work to be accomplished by
RSSC will be determined through a planning process described in chapter
4 of this document.

## 2-7. DAVIS‑BACON ACT WORK ACTIVITIES.  {#davisbacon-act-work-activities. .unnumbered}

a\. For the purposes of the TSSC-II, the term \"Davis‑Bacon Act work\"
means any effort for construction, alteration, or repair work (including
painting and decorating) that is authorized by a WR and is performed by
laborers or other crafts personnel employed by RSSC or subcontractor to
RSSC, regardless of the dollar amount of such work. All Davis‑Bacon Act
work shall be performed in accordance with the provisions of the
Davis‑Bacon Act (40 U.S.C. 276a et. seq.) including the payment of at
least the minimum wages required by the Act. RSSC is required to
accomplish all Davis-Bacon Act work utilizing competitively awarded
firm-fixed-price subcontracts, except that contracts with a single
source may be awarded when it is determined to be in the best of the FAA
and the rational basis is documented. RSSC may perform Davis-Bacon Act
work with its own employees when:

(1) The cost of such work to the Government is not in excess of \$25,000
    per individual project; AND

(2) RSSC has demonstrated to the Government that it is more cost
    effective than awarding a firm-fixed-price subcontract; AND

(3) Permission to use the RSSC\'s employees to perform Davis-Bacon Act
    work is authorized in the Final WR.

**Note: All three of the above conditions** must be met before RSSC may
perform Davis-Bacon Act work with its own employees.

b\. RSSC shall not award a subcontract for a Davis-Bacon Act effort to
any of its affiliates, subsidiaries, divisions, stockholders, or
partners. This prohibition shall also apply to a company or companies
with which RSSC may form a team arrangement.

c\. RSSC is responsible for obtaining all applicable minimum wage
determinations from the Department of Labor (DOL), recommending the
appropriate wage determination for each site to the ACO and
incorporating these DOL rates in each subcontract involving Davis‑Bacon
Act work.

## 2-8. CREW/TEAM CONCEPT. {#crewteam-concept. .unnumbered}

There may be occasions when a single WR or a number of separate WRs may
be issued authorizing the accom­plishment of work that is repetitive in
nature; e.g., ARSR‑3 reinstallations from donor sites to receiving
sites, often referred to as leapfrogging. RSSC will analyze all work
programs, particularly those crossing regional boundaries, and where
practical use a crew concept to achieve potential efficiencies.
Periodically, the FAA and RSSC should meet to discuss future potential
work that may be candidates for the crew concept. Such meetings should
include planned national WR efforts.

## 2-9. WORK ACTIVITIES EXCLUDED FROM TSSC-II. {#work-activities-excluded-from-tssc-ii. .unnumbered}

The following activities are excluded from the Contract:

a.  The TSSC-II is **not to be used** to accomplish any activity not
    directly related to the NAS.

b.  The TSSC-II is **not to be used** to accomplish major construction
    or design efforts, even though F&E-funded and NAS-related.

c.  The TSSC-II is **not to be used** to develop installation planning
    (may be used only after a specific site is identified by the FAA)
    other than that planning required to accomplish work assigned under
    WRs.

d.  The TSSC-II is **not to be used** to perform activities covered by
    restrictions in the Federal Information Resources Management
    Regulations (FIRMR) unless authorized to do so by a Delegation of
    Procurement Authority (DPA) obtained in advance by the TSSC Program
    Office.

e.  The TSSC-II is **not to be used** as a vehicle to avoid procurement
    regulations such as sole source requirements.

When there is a question of applicability of the TSSC-II to a specific
project, consultation with the Technical Officer (TO) is advised.

## 2-10. CONTRACTOR FURNISHED MATERIEL (CFM), EQUIPMENT, AND SERVICES. {#contractor-furnished-materiel-cfm-equipment-and-services. .unnumbered}

a\. RSSC will furnish all materiel, equipment, and services necessary to
complete all required work related to the installation and/or
modification of NAS systems and equipment as described in the WRs. In
most instances, equipment components to be installed and major materiel
shall be furnished by the Government.

(1) Equipment as used in this sense does not mean material like lumber,
    concrete, fuses, wire, required to install F&E systems or
    subsystems.

(2) Equipment refers to those items normally budgeted for by Washington
    or the region, and acquired through regional contracts/orders.

b\. In all cases, Government Furnished Equipment (GFE) and Government
Furnished Materiel (GFM) will be identified and listed in WRs and
transferred to RSSC using the appropriate Govern­ment forms.

c\. TSSC-II procurement of this equipment is not normally within the
Contract scope. It was not intended to fill in the gap when FAA supply
contracts fail to provide the required equipment. Other FAA logistics
alternatives that should be explored for those circumstances include
borrowing, or \"leapfrogging\" available equip­ment from lower priority
sites to meet time constraints for high priority sites.

## 2-11. FAA MANAGEMENT OFFICIALS − DESIGNATION  AND  RESPONSIBILITIES. {#faa-management-officials-designation-and-responsibilities. .unnumbered}

a\. **Functions.**
Management of the TSSC-II consists of, among other functions:

(1) Responsibility for planning, funding, fiscal, and technical control.

(2) Scheduling, development, and issuance of WRs or Contract
    modifications.

(3) Monitoring of project and program status.

(4) Certification of work accomplished.

(5) Evaluation of project and/or overall contract performance.

b\. **FAA Management.** Management of the TSSC-II is a TEAM EFFORT, with
each team member having specific management responsibilities and
authority to interact with RSSC within the specified scope and limits of
the Contract. The team is comprised of the following:

(1) **TSSC Program Manager (TSSC PM).** The TSSC PM is responsible for
    overall FAA management of the TSSC-II. The TSSC PM is designated by
    the NAS Transition and Implementation Office, NAS Planning and
    Support Division. The TSSC PM\'s principal interface in RSSC's
    organization will be the National Contracts and Program Managers.
    Some of the TSSC Program Manager's responsibilities are:

```{=html}
<!-- -->
```
(a) Developing overall TSSC program policy.

(b) Serving as TSSC program spokesperson for FAA and OST, other
    government and public organizations.

(c) Defining clearly overall program and Contract requirements by fiscal
    year with an acceptable plan and criteria and an appropriate
    management and technical approach.

(d) Defining issues and monitoring regional requirements and resource
    utilization. Reviewing and assessing regional use of the Contract.

(e) Making any adjustments to individual regional shares of contract
    resources that become necessary due to workload fluctuation.

(f) Developing, issuing, and managing the Program Management WR.

(g) Nominating a Technical Officer (TO).

(h) Assessing RSSC performance and taking corrective action where
    appropriate.

(i) Evaluating regional use and management of the Contract.

\(2\) **Contracting Officer (CO).**

(a) The CO is responsible for overall contract administration of the
    TSSC-II. The Office of Acquisitions (ASU) designates the Contracting
    Officer. The CO\'s principal interface in RSSC's organization will
    be the National Contract and Program Managers. **Only the CO** has
    authority to:

```{=html}
<!-- -->
```
1.  Direct or negotiate any changes in the Contract.

2.  Modify or extend the Contract period.

3.  Otherwise change any terms and conditions of this Contract.

\(b\) Some of the Contracting Officer's responsibilities are:

1.  Overseeing the administration of the Contract.

2.  Developing and implementing Contract modifications.

3.  Issuing policy guidelines to the regional Administrative Contracting
    Officers (ACOs).

4.  Providing formal consent to any national subcontracts issued by RSSC
    subject to the Subcontracts clause of the Contract.

5.  Approving property transfers which are national in scope,
    administering and documenting the Government property clause of the
    Contract.

6.  Resolving any disputes which arise within the terms of the Disputes
    clause of the Contract.

7.  Auditing WRs, Contract modifications, resources utilized, and actual
    costs against FAA estimates and actual costs of other similar
    pro­jects.

8.  Approving key personnel changes.

9.  Managing Davis‑Bacon Act review.

10. Appointing the FAA Technical Officer (TO) and regional Associate
    Technical Officers (ATOs).

11. Reviewing and certifying national WR invoices to the payment office.

12. Obtaining available cost data for cognizant auditing organiza­tion.

13. Administering national WRs.

\(3\) **Technical Officer (TO).** The TO provides technical management
of the TSSC-II and assists the TSSC PM and CO in the overall management
and administration of the Contract. The TO is nominated by the TSSC PM
and appointed by the CO. The TO\'s principal interfaces in RSSC's
organization will be the National Contract and Program Managers. The TO
performs contractual respon­sibilities under a delegation of authority
issued by the CO. The delegated responsibilities are defined in the
letter of delegation. Some of these responsibilities are:

(a) Issuing and managing technical WRs and Establishment Engineering
    Plans (EEPs) and all revisions at the national level that include
    inter‑regional requirements.

(b) Ensuring that WRs issued are within the scope of the Contract and
    pertinent EEPs and do not exceed maximum dollar limits.

(c) Ensuring that the documents identifying regional requirements and
    funds to support each region's share of TSSC activity are forwarded
    to the CO for Contract modification.

(d) Reviewing billing breakdowns, accomplishing provisional review, and
    forwarding invoices for national WRs to the CO.

(e) Reviewing and evaluating, on an overall basis, RSSC technical and
    administrative performance and compliance, including conformance
    with price and schedule provisions of WRs.

(f) Assisting the CO in post‑audit review of WRs and revisions issued by
    the regions.

(g) Assisting the CO in comparing WRs, revision requirements, resources
    utilized and actual costs as paid by the regions with FAA estimates
    and actual costs of similar projects accomplished by TSSC in other
    regions, by other contractors, or by FAA in-house work force.

(h) Supporting the CO in resolving technical and operational problems
    between RSSC and regional users as required.

(i) Reviewing RSSC's overall personnel assignments to the TSSC-II for
    qualification at the labor category and skill level indicated.

(j) Notifying the CO regarding delinquent or noncomplying Contract
    performance.

(k) Monitoring WRs and revisions at the national and regional levels for
    compliance and consistency with national programs.

\(4\) **Administrative Contracting Officer (ACO).** The ACO acts for the
CO within their region. The ACO is nominated by the regional logistics
organization and appointed by the CO. The ACO\'s princi­pal interface in
RSSC's organization is the TSSC Regional Program Manager (TSSC RPM). For
purposes of this Handbook, the ACOs for the Aeronautical and Technical
Centers will be referred to as Regional ACOs. Their delegated
responsibilities are described in the letter of delegation. Some of the
ACO's responsibilities are:

(a) Administering the Contract for all WRs in their respective region
    for regional specific and regional general category work.

(b) Reviewing all final WRs prior to issuance to ensure compliance with
    Contract scope and substance.

(c) Providing formal consent to regional TSSC subcontracts requiring
    consent under the Subcontracts clause of the Contract.

(d) Administering the Government Property clause of the Contract,
    including the proper documentation of all accountable property
    transfers involving their region.

(e) Enforcing Davis‑Bacon Act wage determinations. This will include
    interviewing RSSC or subcontractors to RSSC employees as appropriate
    (and document­ing these interviews) in order to ensure that they are
    being paid properly.

(f) Reviewing WRs, resources utilized and actual costs against FAA
    estimates and actual costs of other similar projects.

(g) Reviewing, authorizing for payment, and forwarding invoices for
    regional WRs to the payment office.

(h) Maintaining the official file of regional WRs until transferred to
    the CO upon completion.

(i) Assisting the CO, or their designated representative, in post audit
    reviews of WRs and revisions issued by the regions.

\(5\) **Associate Technical Officer (ATO).** The ATO is the principal
official responsible for the technical management of the TSSC at the
regional level. The ATO is nominated by the regional AF division and is
appointed by the CO (different nominating procedure at the Aeronautical
and Technical Centers). The ATO\'s principal interface in RSSC's
organization is the Regional Program Manager (TSSC RPM). The ATO's
delegated responsibilities are described in the letter of delegation.
Some of their responsibilities include, but are not limited to, the
following:

(a) Developing, issuing, and managing EEPs, WRs, and revisions at the
    regional level. Ensuring that WRs issued are within the scope of the
    Contract and the pertinent EEP.

(b) Reviewing itemized invoices, accomplishing provisional certification
    and forwarding invoices for regional WRs to the ACO.

(c) Reviewing and evaluating RSSC's technical and administrative
    performance and compliance, including conformance with price and
    schedule provi­sions of WRs.

(d) Assisting the TO in reviews of WRs and revisions issued by the
    regions.

(e) Assisting the TO in comparing WRs, revision requirements, resources
    utilized and actual costs as paid by the region with FAA estimates
    and with actual costs of similar projects performed by FAA in-house
    work force or by other contractors.

(f) Reviewing key RSSC personnel assignments to regional WRs for
    qualification at the labor category and skill level indicated.

(g) Notifying the ACO regarding delinquent or noncomplying RSSC
    performance.

(h) Monitoring WRs and revisions at the regional level for compliance
    and consistency with regional and national programs.

\(6\) **Funds Certification Official (FCO).** The FCO is the official
responsible for the fiscal management of the TSSC. FCOs are located at
FAA headquarters and in the regions. The TSSC Business Manager is
designated as the FCO by the TSSC Program Manager at the national level.
At the national level, the Business Manager's primary RSSC interface is
with RSSC\'s Business Manager. The Business Manager/FCO's
responsibilities include, but are not limited to, the following:

(a) Coordinating with the TO/ATO relative to providing funding for TSSC
    Establishment Engineering Plan (EEP) updates.

\(b\) Certifying funds at the Procurement Request level. The Contract
cannot be modified for the obligation or deobligation of funds without
Business Manager/FCO certification**.**

\(c\) Coordinating with TO/ATO relative to availability of funds for
individual WRs.

\(d\) Certifying availability of funds prior to issuance of final WRs.

\(e\) Ensuring that funds are used for their designated purpose; e.g.,
in accordance with the description that appears on the Project
Authorization (PA) and appropriation law. For example, funds
appropriated for radar should not be used to replace fuel storage tanks.

\(f\) Maintaining cognizance over TSSC-II funds available versus funds
required to complete the WR.

\(g\) Verifying that obligations and deobligations created by each
TSSC-II Contract modification are appropriately recorded by the
applicable accounting office (regional or headquarters) in DAFIS. Also,
verifying that each TSSC-II invoice expenditure is appropriately
recorded in DAFIS. This could also be done by designated persons in the
regions.

\(7\) **FAA National Program Manager (NPM).** NPMs are assigned a
National WR issued by Headquarters. The NPM is responsible for the
development, production, acceptance testing, and overall coordination
for the implementation of a system or subsystem. The NPM is responsible
for TSSC-II accomplishment in their area of responsibility as follows:

(a) Developing the Statement of Work (SOW).

(b) Determining if TSSC-II is an appropriate and desirable vehicle for
    accomplishment of the NPM\'s program.

(c) Reviewing RSSC WR Plans to verify that appropriate skills and labor
    categories are planned for the WRs; that the cost is reasonable;
    that the schedule is satisfactory; and determining that the WR Plans
    address the intent of the FAA.

(d) Ensuring that the requirements, specifications, and schedules
    contained in WRs relevant to the NPM\'s program are adequate and
    will enable RSSC to estimate and perform the effort properly.

(e) Developing an independent government cost estimate (IGCE) for WRs
    prior to issuance of a PWR.

(f) Participating in WR Plan discussions with RSSC.

(g) Conducting a Quantitative and Qualitative (Q&Q) Analysis.

(h) Monitoring overall RSSC work performance for reasonableness of labor
    charges and adequacy of the service.

(i) Overseeing Regional Project Managers/Engineers' (RPM/RPE) inspection
    and acceptance of completed work with regard to the NPM\'s specific
    program.

(j) Informing the TO of problems within the scope of WRs.

(k) Providing overall technical monitoring of the work being performed
    under WRs, first-hand or via the RPM/RPE.

(l) Reviewing RSSC invoices for WRs and advising the TO of any problems
    or discrepancies. Approving correct invoices.

\(8\) **Regional Project Manager/Engineer (RPM/RPE).** The RPM/RPEs are
the F&E personnel responsible for accomplishing a project. As such they
are the "Requirements Contact" to be named upon the regional WR they
cause to be issued. These persons may or may not be involved with
coordination or other efforts on a National WR. They may have
responsibility for more than one regional WR. Their responsibilities
are:

(a) Developing a SOW for Preliminary WRs (PWR) for regional specific and
    regional general category work, ensuring that requirements,
    specifications, and lists of GFE are included as appropriate. When
    the WR directs sole source procurement, the RPM/RPE will provide the
    pre-approved FAA Justification for Other Than Full and Open
    Competition (JOTFOC), which will be provided with the SOW and become
    a part of the WR.

(b) Developing an independent cost/work hour estimate for each WR and/or
    revision prior to issuing a PWR or Final WR (FWR) Revision.

(c) Assisting in WR Plan discussions with RSSC prior to FWR issuance.

(d) Reviewing RSSC WR Plans to verify that appropriate skills and labor
    categories are planned for the WRs; that the cost is reasonable;
    that the schedule is satisfactory; and determining that the WR Plans
    address the intent of the FAA.

(e) Conducting a Qualitative and Quantitative (Q&Q) analysis.

(f) Monitoring RSSC\'s performance on assigned WRs.

(g) Conducting inspections and acceptance of WR projects in progress and
    those completed. Verifying RSSC\'s work performed for compliance
    with WR requirements.

(h) As requested by the ATO, reviewing RSSC's WR invoices for
    reasonableness of costs and hours indicated.

(i) Informing the ATO of any problems that arise during accomplishment
    of a WR.

## 2-12. CONTRACT PERFORMANCE EVALUATION. {#contract-performance-evaluation. .unnumbered}

The TO and TSSC Program Manager are responsible for overall evaluation
of the contractor's performance, while NPMs, ATOs and RPMs/RPEs are
responsible for evaluating performance of RSSC as it relates to each WR.
Contract performance evaluation shall involve the following.

a.  Overall evaluation of contract performance will include, among other
    factors:

```{=html}
<!-- -->
```
(1) The quality of WR deliverables.

(2) RSSC's compliance with the approved WR Plan.

(3) Timeliness of work start and completion.

(4) Actual versus planned costs.

(5) Exception clearance.

(6) Client (e.g., AT, AF) satisfaction.

```{=html}
<!-- -->
```
b.  Cost Performance is one of the key parameters that needs to be
    monitored periodically to effectively manage WRs. The tools made
    available to assist in this task are:

```{=html}
<!-- -->
```
(1) RSSC will prepare a monthly Cost Performance Report (CPR) which
    contains all WRs listing budgeted cost, actual cost, Estimate To
    Complete (ETC) cost, Latest Revised Estimate (LRE), funded amount,
    projected variance at completion, and percent completion of the WR
    for both hours and dollars. There are two reports, one separates
    costs by type, labor-related, and material/other and includes
    monthly cost/budget for the WR. The second report is broken down by
    task elements.

(2) Monthly RSSC co-hosts a Program Status Review (PSR) in each region
    and nationally. As part of this review, the cost status of each WR
    will be presented. For those WRs where projected costs exceed 15% of
    the budgeted cost, variance reports will be prepared with the cause
    of the variance and when appropriate, what steps are being taken to
    bring the cost into compliance.

```{=html}
<!-- -->
```
c.  Schedule Performance reporting is dependent upon the " Schedule
    Priority" line set in the WR Cover Sheet. RSSC will report schedule
    variances of as little as one day for high-priority WRs, with no
    report required for low-priority WRs. See chapter 4 for detailed
    discussion on Schedule Priorities.

d.  Program Reviews. In addition to the evaluation of individual WRs,
    the TSSC PM or TO will periodically direct an overall evaluation of
    the contractor's performance. Generally, these evaluations will be
    part of the monthly national Program Status Reviews and the regional
    Program Reviews attended by the TSSC PM, TO, or their
    representative. Areas that are evaluated, but not limited to,
    include:

```{=html}
<!-- -->
```
(1) Identifying trends that reflect overall performance of the
    contractor, such as cost and schedule variances.

(2) Measuring customer satisfaction through meetings with the customer.

(3) Evaluating the organization, technical, and administrative processes
    employed by both RSSC and the FAA.

(4) Review for assurances that there is no shifting or evolution of
    TSSC-II from a support services contract to a personal services
    contract.

## 2-13. CUSTOMER SATISFACTION SURVEYS. {#customer-satisfaction-surveys. .unnumbered}

Customer Satisfaction Survey forms have been developed to measure the
FAA customer satisfaction, which allows the regional users to provide
recommendations for improvement. There are three types of FAA customer
satisfaction surveys.

a.  The first Customer Satisfaction Survey is for the SMOs. SMOs are
    requested to evaluate RSSC's performance at the conclusion of work
    at a site, or multiple sites on the same WR. Each SMO should
    complete the form and return it to the ATO. The forms will be used
    by the ATO and RSSC to incorporate regional improvements and will be
    forwarded to the national headquarters. See Figure 2-2, Customer
    Satisfaction Survey: SMO.

b.  The second survey is for the FAA F&E project engineers. Evaluation
    feedback of RSSC's performance on each WR will be conducted upon
    completion of the WR, using Figure 2-1, Satisfaction Survey/Project
    Evaluation Form: Project Engineer.

For the 6 month review, the form serves as the project engineer's
customer service feedback to FAA and the TSSC contractor and is used in
evaluating the contractor's WR performance. The form is completed and
signed by only the FAA project engineer. It is then forwarded to the ATO
for his information. The ATO forwards it to the regional RSSC office for
feedback and any corrective procedural action. Summary data of all
Project Engineer survey forms will be provided by regional RSSC to the
ATO and headquarters RSSC and FAA on a 6 month cycle.

For the end-of-Work Release evaluation, the same form (TSSC Customer
Satisfaction Survey - Project Engineer) serves an additional function:
that of the official FAA evaluation for the contractor's performance of
the WR and FAA acceptance of the WR work effort. The ATO's signature is
added at the end of the form to certify that the engineer's "End of WR"
Evaluation has been accomplished correctly and that the ATO agrees with
the engineer's overall findings. After both signatures, the
[original]{.underline} evaluation form shall be filed in the official
regional (ACO) WR file. Information copies of the evaluation form will
be provided by the ATO to the regional RSSC. As before, summary data
will be provided by regional RSSC to the ATO and headquarters RSSC and
FAA on a 6 month cycle, as above.

c.  The final survey is for the ATO and ACO. The ATOs and ACOs are
    requested to evaluate the RSSC's performance on a six (6) month
    interval. The ATO and ACO should each complete one overall
    evaluation for all the WRs covered by the six (6) month period.
    These surveys should be completed and returned to the Washington
    Office (FAA or Raytheon) at the end of January and July of each
    year. See Figure2-3, Customer Satisfaction Survey: ATO/ACO.

**TSSC Customer Satisfaction Survey/Project Evaluation Form: Project
Engineer**

**Customer Satisfaction Survey Date:
[\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_]{.underline}**

**The following information is required per FAA Order 4450.12 to
identify the overall performance of the TSSC Contractor (Raytheon
Support Services Company -- RSSC). Please fill out this survey for each
work release at 6 month intervals (when a work release exceeds 6 months
in duration) and at work release completion ("X" revision) in order to
satisfy TSSC requirements. Feel free to add any comments to assist in
evaluating the Contractor's overall performance. For end-of-WR
evaluations, this original evaluation form shall be filed in the
official regional (ACO) WR file.**

**Please return this evaluation to the address below, by:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Federal Aviation Administration**

**Regional Office Address Line 1**

**Regional Office Address Line 2**

**ATTN: TSSC ATO**

**Work Release Number & Title:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Site Location(s):
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Regional Office:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**FAA PE Name:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Date:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**FAA PE Signature:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_Please
check (v) as appropriate:  WR Completion  6 Month**

***1. During the [work planning phase]{.underline}*** for this work
release, how effectively did TSSC address the following?

  ---------------------------------------------------------------------------------------------------------
                                 **Not    **Excellent**   **Very   **Satisfactory**   **Fair**   **Poor**
                                 App.**                   Good**                                 
  ------------------------------ -------- --------------- -------- ------------------ ---------- ----------
  Project Scope                                                                                  

  Project Schedule                                                                               

  Project Estimate                                                                               

  Project Coordination                                                                           

  Long Lead Items                                                                                

  GFM & GFE                                                                                      

  Special Site Access                                                                            
  Requirements                                                                                   

  Special Security Requirements                                                                  

  HAZMAT Handling                                                                                

  Environmental Impact                                                                           

  Training Requirements                                                                          
  ---------------------------------------------------------------------------------------------------------

Comments/Recommendations:

2.  ***During the [engineering phase]{.underline}*** for this work
    release , how effectively did TSSC address the following?

  ----------------------------- ------- -- --------------- -- -------- -- ------------------ -- ---------- ----------
                                **Not      **Excellent**      **Very      **Satisfactory**      **Fair**   **Poor**
                                App**                         Good**                                       

  Project Scope                                                                                            

  Project Schedule                                                                                         

  Project Budget                                                                                           

  Project Funding                                                                                          

  Timely Coordination                                                                                      

  Realistic Cost Estimates                                                                                 

  Site Survey                                                                                              

  Timely Response to Changes                                                                               

  Long Lead Items                                                                                          

  GFM & GFE                                                                                                

  Special Site Access                                                                                      
  Requirements                                                                                             

  Special Security Requirements                                                                            

  HAZMAT Handling                                                                                          

  Environmental Impact                                                                                     

  Training Requirements                                                                                    
  ----------------------------- ------- -- --------------- -- -------- -- ------------------ -- ---------- ----------

Comments/Recommendations

Figure 2-1. Example of TSSC Customer Satisfaction Survey/Project
Evaluation Form: Project Engineer

3.  ***During the [project implementation phase]{.underline}*** for this
    work release, how effectively did TSSC adhere to the following?

  -------------------------------------------------------------------------------------------------------
                               **Not    **Excellent**   **Very   **Satisfactory**   **Fair**   **Poor**
                               App.**                   Good**                                 
  ---------------------------- -------- --------------- -------- ------------------ ---------- ----------
  Project Scope                                                                                

  Project Schedule                                                                             

  Project Budget                                                                               

  Project Funding                                                                              

  Project Coordination                                                                         

  Project Change Notifications                                                                 

  HAZMAT Handling                                                                              

  Environmental Considerations                                                                 
  -------------------------------------------------------------------------------------------------------

Comments/Recommendations:

4.  ***At [project completion]{.underline}*** for this work release, how
    effectively did TSSC address the following?

  -------------------------------------------------------------------------------------------------------
                               **Not    **Excellent**   **Very   **Satisfactory**   **Fair**   **Poor**
                               App.**                   Good**                                 
  ---------------------------- -------- --------------- -------- ------------------ ---------- ----------
  CAI Coordination                                                                             

  CAI Item Close-out                                                                           

  As-Builts                                                                                    

  Schedule Performance                                                                         

  Cost Performance                                                                             

  Project Close-out                                                                            
  Coordination                                                                                 
  -------------------------------------------------------------------------------------------------------

**Comments/Recommendations:**

5.  ***Rate how well TSSC [manage]{.underline}d the Subcontractor(s) for
    this work release.***

    Not Applicable\_\_\_\_\_\_\_\_\_ Excellent\_\_\_\_\_\_\_\_\_ Very
    Good\_\_\_\_\_\_\_\_\_ Satisfactory\_\_\_\_\_\_\_\_
    Fair\_\_\_\_\_\_\_\_ Poor\_\_\_\_\_\_\_

    **Comments/Recommendations:**

6.  ***Rate the work accomplished in terms of overall
    [quality/workmanship]{.underline} for this work release.***

**Excellent\_\_\_\_\_\_\_\_\_ Very Good\_\_\_\_\_\_\_\_\_
Satisfactory\_\_\_\_\_\_\_\_ Fair\_\_\_\_\_\_\_\_ Poor\_\_\_\_\_\_\_**

**Comments/Recommendations:**

7.  ***Rate your overall [experience]{.underline} with TSSC for this
    work release in terms of:***

  -----------------------------------------------------------------------------------------------
                                **Excellent**   **Very   **Satisfactory**   **Fair**   **Poor**
                                                Good**                                 
  ----------------------------- --------------- -------- ------------------ ---------- ----------
  Professionalism                                                                      

  Initiative                                                                           

  Sensitivities To Regional                                                            
  Priorities                                                                           

  Your Expectations Being Met                                                          
  -----------------------------------------------------------------------------------------------

**Comments/Recommendations:**

*8. Please comment on your overall satisfaction with the TSSC for this
work release and on how the Contract can best meet your needs. Attach a
separate sheet if required.*

**Comments/Recommendations:**

For the six-month Work Release (WR) review, this evaluation form serves
as the project engineer's customer service feedback to FAA and the TSSC
Contractor and is used in evaluating the Contractor's overall
performance. This evaluation form is completed and signed only by the
FAA Project Engineer. Summary data of all Project Engineer evaluation
forms will be provided by regional RSSC to the ATO and headquarters RSSC
and FAA on a 6 month cycle.

For the end-of-WR evaluation, this same evaluation form serves as
additional functions; that of the official FAA evaluation for the
Contractor's performance of the WR and FAA acceptance of the WR work
effort. The ATO's signature is added at the end of the evaluation form
to certify that the engineer's "End of WR" Evaluation has been
accomplished correctly and that the ATO has reviewed the engineer's
overall findings. After both signatures, the original evaluation form
shall be filed in the official regional (ACO) WR file. Information
copies of the evaluation form will be provided by the ATO to the
regional RSSC. Summary data will be provided by regional RSSC to the ATO
and headquarters RSSC and FAA on a 6 month cycle, as above.

ATO Signature:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Date: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Figure 2-1. Example of TSSC Customer Satisfaction Survey/Project
Evaluation Form: Project Engineer (CONTINUED)

**[TSSC Customer Satisfaction Survey]{.underline}**

**[SMO]{.underline}**

**Customer Satisfaction Survey Date:
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

The following information is requested to identify the overall
performance of the TSSC contractor. Please fill out on a per site basis
unless there were multiple sites on the same work release completed. If
the TSSC Contractor performed work at multiple SMO sites, you may
generate one survey form provided the work was minor in nature. If major
work was accomplished, we request a separate survey form for each site
completed. Feel free to add any comments to assist in evaluating the
Contractor's overall performance. The TSSC Contractor will provide a
copy of this survey to the ATO for review.

**Please return this evaluation to the address below,
by\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Federal Aviation Administration**

**Regional Office Address Line 1**

**Regional Office Address Line 2**

**ATTN: TSSC ATO**

**Work Release Number &
Title:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Site
Location:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**SMO Office
Location:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Evaluator's
Name:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Signature:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Evaluator's
Title:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Date:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

1.  ***How effectively did TSSC [coordinate]{.underline} the following
    site specifics with your office***?

  ------------------- ---------- --------------- ---------- ------------------ ---------- ----------
                      **Not      **Excellent**   **Very     **Satisfactory**   **Fair**   **Poor**
                      App.**                     Good**                                   

  Project Start                                                                           

  Site Access                                                                             

  Security                                                                                

  Working Hours                                                                           

  SMO Personnel                                                                           
  Support                                                                                 

  Project Work                                                                            
  Scheduled                                                                               

  Scheduled Outages                                                                       

  Impact to Airport                                                                       
  Operations                                                                              
  ------------------- ---------- --------------- ---------- ------------------ ---------- ----------

Comments/Recommendations:

Figure 2-2. Example of TSSC Customer Satisfaction Survey/Project
Evaluation Form: SMO

2.  ***How effectively did TSSC follow [procedures]{.underline}*** in
    the following site specific areas?

  -------------------- ---------- --------------- -------- ------------------ ---------- ----------
                       **Not      **Excellent**   **Very   **Satisfactory**   **Fair**   **Poor**
                       App.**                     Good**                                 

  Site Access                                                                            

  Security                                                                               

  Working Hours                                                                          

  SMO Personnel                                                                          
  Support                                                                                

  Scheduled Outages                                                                      

  Impact to Airport                                                                      
  Operations                                                                             
  -------------------- ---------- --------------- -------- ------------------ ---------- ----------

Comments/Recommendations:

3.  ***Rate how well TSSC [managed]{.underline} the Subcontractor at the
    site.***

Not Applicable\_\_\_\_\_\_\_ Excellent\_\_\_\_\_\_\_\_ Very
Good\_\_\_\_\_\_\_\_\_ Satisfactory\_\_\_\_\_\_\_ Fair\_\_\_\_\_\_
Poor\_\_\_\_\_\_\_\_

Comments/Recommendations:

4.  ***Rate the work accomplished at the site in terms of overall
    [quality/workmanship]{.underline}.***

Excellent\_\_\_\_\_\_\_ Very Good\_\_\_\_\_\_\_\_ Satisfactory
\_\_\_\_\_\_\_ Fair\_\_\_\_\_\_\_ Poor\_\_\_\_\_\_\_

Comments/Recommendations:

5.  ***Rate your overall [experience]{.underline}*** with TSSC at the
    site in terms of:

  --------------------- --------------- ---------- ------------------ ---------- ----------
                        **Excellent**   **Very     **Satisfactory**   **Fair**   **Poor**
                                        Good**                                   

  Professionalism                                                                

  Initiative                                                                     

  Sensitivities To SMO                                                           
  Priorities                                                                     

  Your Expectations                                                              
  Being Met                                                                      
  --------------------- --------------- ---------- ------------------ ---------- ----------

Comments/Recommendations:

6.  ***Please comment on your [overall satisfaction]{.underline} with
    the TSSC for this specific site and on how the Contract can best
    meet your needs. Attach a separate sheet if required.***

Comments/Recommendations:

Figure 2-2. Example of TSSC Customer Satisfaction Survey/Project
Evaluation Form: SMO (CONTINUED)

**[TSSC Customer Satisfaction Survey]{.underline}**

**[ATO/ACO]{.underline}**

Customer Satisfaction Survey Date:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Evaluation Period:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

The following information is requested to identify the overall
performance of the TSSC Contractor. Please base your evaluation on the
last six months of performance. Feel free to add any comments to assist
in evaluating the Contractor's overall performance. A copy of this
survey will be sent too the TO and CO.

Please return this evaluation to the address below, by
\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**Raytheon Support Services Company**

**600 Maryland Avenue SW Suite 895**

**Washington, DC 20024**

**ATTN: National Quality Manager**

**Regional
Office:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Evaluator's
Name:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Signature:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

**Evaluator's
Title\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
Date:\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_**

1.  ***Rate how well TSSC managed Subcontractors and related subcontract
    activities over the last six (6) months.***

Excellent\_\_\_\_\_\_\_\_\_ Very Good \_\_\_\_\_\_\_\_ Satisfactory
\_\_\_\_\_\_\_Fair\_\_\_\_\_ Poor\_\_\_\_\_\_

Comments/Recommendations:

2.  ***Rate how well TSSC responded to [Contract
    requirements]{.underline} over the last six (6) months (i.e. 75%
    letters, work plan deliveries, invoice submittals, and timely
    funding requests*).**

> Excellent\_\_\_\_\_\_\_\_ Very Good\_\_\_\_\_\_\_\_\_
> Satisfactory\_\_\_\_\_\_\_ Fair\_\_\_\_\_ Poor\_\_\_\_\_\_\_

Comments/Recommendations:

3.  ***Rate how well TSSC responded to [FAA inquiries]{.underline} over
    the last six (6) months.***

Excellent\_\_\_\_\_\_\_\_ Very Good\_\_\_\_\_\_\_\_
Satisfactory\_\_\_\_\_\_\_ Fair\_\_\_\_\_\_ Poor\_\_\_\_\_\_\_

Comments/Recommendations:

Figure 2-3. Example of TSSC Customer Satisfaction Survey/Project
Evaluation Form: ATO/ACO

4.  ***Rate how effectively TSSC performed in the following areas at
    [project completion(s)]{.underline}*** over the last six (6) months?

  ----------------------- --------------- ----------- ------------------ ---------- ----------
                          **Excellent**   **Very      **Satisfactory**   **Fair**   **Poor**
                                          Good**                                    

  Schedule                                                                          

  Cost                                                                              

  Project Close-out                                                                 
  Coordination                                                                      
  ----------------------- --------------- ----------- ------------------ ---------- ----------

> Comments/Recommendations:

5.  ***Rate the work accomplished in terms of TSSC-FAA coordination and
    administration of documentation over the last six (6) months. What
    enhancement can be made to improve the overall process?***

Excellent\_\_\_\_\_\_\_\_\_\_ Very Good\_\_\_\_\_\_\_\_
Satisfactory\_\_\_\_\_\_\_\_ Fair\_\_\_\_\_\_ Poor\_\_\_\_\_\_

Comments/Recommendations:

6.  ***Rate your overall [experience ]{.underline}***with TSSC over the
    last six (6) months in terms of:

  -------------------------- --------------- ---------- ------------------ ---------- ----------
                             **Excellent**   **Very     **Satisfactory**   **Fair**   **Poor**
                                             Good**                                   

  Professionalism                                                                     

  Initiative                                                                          

  Sensitivities To FAA                                                                
  Priorities                                                                          

  Your Expectations Being                                                             
  Met                                                                                 
  -------------------------- --------------- ---------- ------------------ ---------- ----------

Comments/Recommendations:

7.  ***Please comment on your [overall satisfaction]{.underline} with
    TSSC over the last six (6) months and on how the Contract can best
    meet your needs. Attach a separate sheet if required.***

**Figure 2-3. Example of TSSC Customer Satisfaction Survey/Project
Evaluation Form: ATO/ACO (CONTINUED)**

# FISCAL PROCEDURES

## 3-1. GENERAL. {#general.-1 .unnumbered}

This chapter describes the unique procedures through which funds for the
TSSC are committed, obligated, and controlled and how the Contract is
modified by the CO.

## 3-2. TSSC-II PROGRAM MANAGEMENT FUNDING. {#tssc-ii-program-management-funding. .unnumbered}

A National Program Management Work Release (NPM WR) will be issued or
revised annually. The TSSC Program Office will develop an IGCE for the
annual funding required for program management cost and program
management-related fee and issue a PWR to RSSC. RSSC responds with a WR
Plan that is reviewed and discussed to resolve any issues. After review
and approval by the Program Office, an FWR revision is issued. The
amount required for program management will be subtracted from the
available TSSC funding before the regional distribution is made. The
TSSC Business Manager/FCO will prepare a Procurement Request (PR) for
program management costs and related fees. This PR will be certified by
the TSSC Business Manager and forwarded to the CO.

a.  **Functions of the NPM WR.**

```{=html}
<!-- -->
```
(1) Provides a contract structure and resources to implement the TSSC.

(2) Ensures that proper resources are provided responsively in support
    of FAA requirements.

b\. **Services Funded by the NPM WR.**

They include but are not limited to:

(1) Direct labor, travel, overtime, and related costs for all RSSC
    personnel assigned to the NPM WR, except for costs allocable to
    individual WRs.

(2) Facility lease costs, and associated utilities (fuel, water,
    electricity, etc.).

(3) Facility furniture, equipment, and supplies.

(4) Telephone, facsimile, and communication services.

(5) Office automation equipment (i.e., computer aided engineering
    graphics \[CAEG\]/engineering drawing workstations) for base amount
    proposed and costed under the NPM WR (additional equipment costed
    against technical WRs, if needed).

(6) Transportation of materiel (such as delivery of supplies or
    computers).

(7) Computer hardware/software maintenance.

(8) Preliminary Work Release review/Work Plan development.

(9) Quality control/safety inspections on randomly selected WRs, and
    safety and quality control training (instructors and periodic
    training for engineers/technicians when costs cannot be allocated to
    a WR).

## 3-3. TSSC-II PROJECT FUNDING. {#tssc-ii-project-funding. .unnumbered}

a.  **Contract Modification.** Prior to assigning projects to the
    TSSC-II, funds need to be obligated. Obligating funds is
    accomplished by Contract modification. An increase or decrease in
    the funding, or a change in the scope of an already approved
    project, also requires a Contract modification. The CO is the only
    person authorized to modify the Contract; that is, to issue a
    Contract Modification.

b.  **Fund Allotment**. It is contemplated that the Government will
    allot funds incrementally up to the full estimated costs of issued
    WRs. RSSC shall notify the appropriate CO/ACO in writing when the
    costs incurred against any WR exceed 75 percent of the funds
    allotted to the WR.

c.  **Establishment Engineering Plan (EEP) Data Sheet Assignments.**

```{=html}
<!-- -->
```
(1) To begin the process of obligating funds for a project, thereby
    adding a project to the Contract via a Contract modification, an EEP
    Data Sheet needs to be generated. The EEP Data Sheet is the vehicle
    used to add a project to the Contract, or to change the scope of the
    cumulative EEP description already in the Contract. The EEP Data
    Sheets become part of the Contract modification once executed.

(2) Standard EEPs have been established to categorize the types of work
    anticipated under the TSSC-II. The EEPs provide a common means of
    assigning work and are intended to simplify the obligation of funds
    onto the Contract. See paragraph 3-5 for authorized EEP descriptions
    and numbers.

(3) The EEP is established and maintained in the FAA TSSC-II Unitrack
    System. Refer to the TSSC-II Unitrack System User's Handbook for
    complete details, and step-by-step instructions, on how to create,
    view, edit, delete, and print EEP Data Sheets. Each of the EEP
    package components will be explained later in this chapter.

## 3-4. IDENTIFYING TSSC-II PROJECTS. {#identifying-tssc-ii-projects. .unnumbered}

a.  The first step is to identify projects that can be accomplished
    using the TSSC-II. Using the TSSC-II does not change the requirement
    to fund the project, nor does it change the technical requirements
    of the project. However, it does provide an alter­native to using FAA
    resources or other contractors to implement a project.

b.  The FAA NPM/RPM/RPE who is responsible for implementing a project,
    usually will make the determination as to the best method for
    accomplishing the assigned project using the resources of the FAA,
    TSSC-II, or other contractors.

c.  See chapter 2 of this Handbook and Appendix 3 for the List of
    Candidate Projects for Work Releases, of the Contract for examples
    of types of work suitable for the TSSC-II.

d.  There are certain types of tasks that are excluded from
    accomplishment through the TSSC. Chapter 2 of this Handbook lists
    those type of projects that **are not** to be accomplished using the
    TSSC.

e.  The TO/ATO should be consulted by the NPM/RPM/RPE to determine if
    the project being considered is within the scope of the Contract.
    The CO/ACO may also be consulted on matters of Contract scope and
    special clearances required. Once the project has been identified
    for TSSC accomplishment, an EEP is generated in the Unitrack System.

The following Figures 3-1 and 3-2, note the authorized users and the EEP
process, respectively:

+--------------+----------+--------+--------+-------+--------+--------+
| **User       |          |        |        |       |        |        |
| Group**      |          |        |        |       |        |        |
+--------------+----------+--------+--------+-------+--------+--------+
|              | *        | *      | *      | **    | **     | **     |
|              | *ADMIN** | *ACO** | *ATO** | FCO** | ENG/** | GUEST/ |
|              |          |        |        |       |        | OTHE   |
|              |          |        |        |       |        | RS\*** |
+--------------+----------+--------+--------+-------+--------+--------+
| **EEP**      |          |        |        |       |        |        |
+--------------+----------+--------+--------+-------+--------+--------+
| -   Create   | ---      | Yes    | Yes    | Yes   | Yes    | \*     |
|     EEP      |          |        |        |       |        |        |
+--------------+----------+--------+--------+-------+--------+--------+
| -   View EEP | ---      | Yes    | Yes    | Yes   | Yes    | \*     |
+--------------+----------+--------+--------+-------+--------+--------+
| -   Edit EEP | ---      | Yes    | Yes    | Yes   | Yes    | \*     |
+--------------+----------+--------+--------+-------+--------+--------+
| -   Delete   | ---      | Yes    | Yes    | Yes   | Yes    | \*     |
|     EEP      |          |        |        |       |        |        |
+--------------+----------+--------+--------+-------+--------+--------+

Figure 3-1. EEP Module Authorization

\* Guests/Others can view only on any/all actions.

![](media/image2.wmf){width="6.479861111111111in"
height="7.564583333333333in"}

Figure 3-2. Establishment Engineering Plan (EEP) Process

## 3-5. TSSC-II AUTHORIZED EEP DESCRIPTIONS AND NUMBERS. {#tssc-ii-authorized-eep-descriptions-and-numbers. .unnumbered}

**01 - Contractor Labor and Travel (CL&T)**

> Funds for CL&T-related expenses, to provide program management
> functions, project engineering, technical, installation, and
> construction-related labor services, and other labor tasks associated
> with providing support to approved F&E projects under this and the
> other EEP Items below.

**02 - Cable Loops**

> Provide technical and engineering support to perform site survey and
> investigation and Environmental Due Diligence Audit/Environmental
> Assessment (EDDA/EA); CSER; plans and specifications; site
> preparation; construction; construction contract oversight; CAI/JAI;
> and project documentation to install; replace; test; tune; optimize;
> clear CAI/JAI exceptions; and or restore NAS cable loop systems within
> various NAS, test, and training facilities.

**03 - Weather Systems**

> Provide technical and engineering support to perform site survey and
> selection analysis and evaluation; EDDA/EA; CSER; plans and
> specifications; site preparation; construction; construction contract
> oversight; CAI/JAI and project documentation to install; relocate;
> restore; test; tune; optimize; clear CAI/JAI exceptions; and or
> modernize various weather systems including but not limited to LLWAS,
> AWOS, ASOS, DUATS, MWP, RWP within various NAS, test, and training
> facilities.

**04 - Resident Engineering (RE)**

> In accordance with the requirements of the specific Work Release;
> provide RE services for construction and or installation oversight at
> various NAS, test, and training facilities for FAA logistics
> administered contracts.

**05 - Remote Maintenance Monitoring System (RMMS)**

> Provide RMMS engineering support to perform site survey and
> evaluations (including HAZMAT); CSER; plans and specifications; site
> preparation; installation; test; tune; optimize; clear CAI/JAI
> exceptions; and or provide contractor oversight; system integration;
> CAI/JAI at various NAS, training, and test facilities.

**06 - Spectrum Engineering**

> Provide engineering support to perform analysis and studies in the
> spectrum engineering field including but not limited to frequency
> management and RF interference studies; site evaluation; signal
> propagation; equipment installation; tune; relocation; integration;
> test; clear CAI/JAI exceptions; and perform optimization at various
> NAS, test, and training facilities.

**07 - Air Route Traffic Control Center (ARTCC)**

> Provide technical and engineering support to perform site survey and
> selection analysis and evaluation; EDDA/EA; CSER; plans and
> specifications; site preparation; construction; construction contract
> oversight; CAI/JAI and project documentation to install; relocate;
> restore; tune; test; optimize; clear CAI/JAI exceptions; and or
> modernize various ARTCC facilities; systems; and tie-in facilities or
> systems, including but not limited to, LINCS, EARTS, TMS, ODAPS,
> NADIN, MWP, DMN, AAS/VSCS, RCAG, AMCC, NEXRAD, BUEC, and CERAP at NAS,
> test, and training facilities.

**08 - Airport Traffic Control/Terminal Approach Control/Medium Control
Facility (ATCT/TRACON/MCF)**

> Provide technical and engineering support to perform site survey and
> selection analysis and evaluation; EDDA/EA; CSER; plans and
> specifications; site preparation; construction; construction contract
> oversight; CAI/JAI and project documentation to install; relocate;
> restore; test; tune; optimize; clear CAI/JAI exceptions; and or
> modernize various ATCT/TRACON/MCF structures and systems, including
> but not limited to ATIS, AAS/VSCS, TMS, airport field lighting, STCS,
> LLWAS, and RTR.

**09 - Satellite Systems**

> Provide technical and engineering support to perform site survey and
> selection analysis and evaluation; EDDA/EA; CSER; plans and
> specifications; site preparation; construction; construction contract
> oversight; CAI/JAI and project documentation to install; relocate;
> restore; test; tune; optimize; clear CAI/JAI exceptions; and or
> modernize various GPS, FAASAT, and ANICS facilities and systems at
> NAS, test, and training facilities.

**10 - Installation Support**

> Provide technical and engineering support to perform CSER; plans and
> specifications; site preparation; construction; CAI/JAI and project
> documentation to install; relocate; restore; test; tune; optimize;
> clear CAI/JAI exceptions; and or modernize various NAS equipment at
> NAS, test, and training facilities.

**11 - Communication Systems**

> Provide technical and engineering support to perform site survey; site
> selection analysis; site investigation & EDDA/EA; site preparation;
> construction; site adaptation; CSER; equipment overhaul; installation;
> clear CAI/JAI exceptions; test; tune-up; modernization and or
> optimization; facility restoration/ modernization; establishment; and
> relocation; for various communications facilities and systems,
> including but not limited to RCE, RCL, RCAT, RCAG, RCO, RCF, BUEC, and
> LINCS.

**12 - Environment and Regulatory Compliance**

> Provide technical and engineering support to perform site survey and
> site selection analysis and evaluation; EDDA/EA; CSER; plans and
> specifications; site preparation; construction; construction contract
> oversight; clear CAI/JAI exceptions; provide CAI/JAI and project
> documentation to assist FAA NAS, test, and training facilities comply
> with various environmental activities, regulations, laws, and
> requirements.

**13 - Plant Work**

> Provide technical and engineering support to perform site survey;
> CSER; plans and specifications; site preparation; construction;
> construction contract oversight; CAI/JAI and project documentation to
> install; relocate; restore; clear CAI/JAI exceptions; and or modernize
> various NAS components; test; and training facility structures and
> systems such as electrical power and environmental systems; mechanical
> systems; and system/facility bonding; grounding; and lightning
> protection.

**14 - NAVAIDS/VISAIDS**

> Provide technical and engineering support to perform site survey and
> selection analysis and evaluation; EDDA/EA; CSER; plans and
> specifications; site preparation; clear CAI/JAI exceptions;
> construction oversight; CAI/JAI and project documentation to install;
> relocate; restore; modernize various navigational and or visual aids,
> including but not limited to VASI, PAPI, VOR, VORTAC, ILS, Glide
> Slope, Localizer, LDA, NDB, Beacons, and Markers at NAS, test, and
> training facilities.

**15 - FSS/AFSS**

> Provide technical and engineering support to perform: site survey and
> selection analysis and evaluation; EDDA/EA; CSER; plans and
> specifications; site establishment or decommissioning or
> consolidation; site preparation; construction; construction contract
> oversight; equipment installation; equipment removal; CAI/JAI and
> project documentation to install; relocate; restore; clear CAI/JAI
> exceptions; modernize various new or existing FSS/AFSS facilities in
> the NAS, or at various test or training facilities.

**16 - Drafting**

> Provide drafting technical and engineering support for NAS, test, and
> training facilities F&E projects; including as-built drawings; new
> project drawings; site studies; line-of-sight studies; archive
> existing drawing files on FAA CAEG system and/or other
> electronic/digital media; clear CAI/JAI exceptions; conversion of
> \"hard copy\" drawings to electronic software/digital format; and
> conversion between various software/digital formats.

**17 - Radar**

> Provide technical and engineering support to perform site selection;
> site investigation; EDDA/EA; site preparation; construction; site
> adaptation; equipment overhaul; installation; testing; tune-up
> optimization; facility modernization; CAI/JAI participation and
> provide project documentation; clear CAI/JAI exceptions; and or
> perform facility relocation; for all Radar systems, including but not
> limited to ASR, ARSR, and ASDE.

**18 - Fuel Storage Tanks**

> Provide technical and engineering support to perform site survey; site
> selection analysis and evaluation; EDDA/EA; provide CSER; plans and
> specifications; perform site preparation; construction; construction
> contract oversight; provide CAI/JAI and project documentation to
> accomplish fuel storage tank installation; relocation; restoration;
> modernization; clear CAI/JAI exceptions; perform site clean up; tank
> removal; provide for conversion of stand-by power systems to
> alternative fuels; accomplish Fuel Storage Tank removal or
> replacement; and fuel tank testing at various existing or new sites.

## 3-6. PREPARATION OF ESTABLISHMENT ENGINEERING PLAN DATA SHEETS. {#preparation-of-establishment-engineering-plan-data-sheets. .unnumbered}

The NPM/RPM/RPE responsible for the project would normally be
responsible for completing the EEP Data Sheet. The TO/ATO is available
for assistance as required. Figure 3-3 shows an example of a blank EEP
Data Sheet.

**TSSC II EEP Data Sheet**

02-Aug-96

a\. Contact Name: Routing : Phone :

b\. EEP Item #: CIP \# New CIP#

EEP Title :

c\. Description of Project Work

Type of Change

Work Scope : PR #:

Funding Scope : Funding Amount :

WR Type : d. Target WR Start Date :

e\. Accounting Data

  --------- --------- ---------- --------- -------- -------- -------- --------- --------- --------------------
  **Loc**   **Reg**   **Appr**   **Lim**   **C      **P      **Ob     **CAF**   **JON**   **Obligated Amount**
                                           Cntr**   Elem**   Clss**                       

                                                                                          

                                                                                          

                                                                                          

                                                                                          

                                                                                          

                                                                                          

                                                                                          

                                                                                          

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

Total Obligated :

Figure 3-3. Example of a Blank EEP Data Sheet

Description of Blocks "a" through "e" of the EEP Data Sheet:

a.  **Block "a" Contact Name: Routing: Phone:** Provide name, routing
    symbol, and phone number of National/Regional Program
    Manager/Project Engineer responsible for project (WR).

b.  **Block "b" EEP Item #:** Select an EEP from the standardized list
    provided by Unitrack; **CIP #:** Select the CIP project (from the
    pre-1995 CIP #s) that best describes the work to be done.

**NEW CIP #:** Select the CIP project (from the newly created CIP #s)
that best describes the work to be done.

c.  **Block "c" Description of Project Work**: Provide specific
    description of work to be performed. Tell what it is you want the
    contractor to do when the FWR is issued. Be complete enough to
    enable the TO/ATO to determine if the work is within the scope of
    the Contract.

**Type of Change:** Indicate whether this will be to **increase or
decrease** the funding.

> **Work Scope:** Indicates the increase or decrease in the scope of the
> work.
>
> **Funding Scope:** Indicates the increase or decrease of the funding.

**WR Type:** Will be either "New" or "On-going." "New" will indicate
adding funds. If "on-going" WR is entered, user is prompted to select
the existing WR that will be affected by the increase or decrease of
funding or scope of work.

**Funding Amount:** This is the **actual amount** that will be increased
or decreased.

d.  **Block "d" Target WR Start Date:** If this is a PWR, enter the date
    you anticipate the project should be started. If an FWR or RWR,
    enter the actual date work should begin.

```{=html}
<!-- -->
```
d.  **Block "e" Accounting Data:** Data is found on Project Assignment
    Sheet given to Project Engineer.

## 3-7. PROCUREMENT REQUEST. {#procurement-request. .unnumbered}

a.  The PR establishes the obligation/deobligation in the FAA's System
    for Acquisition Management (SAM) program for transfer into the
    TSSC-II Unitrack System. When the PR is processed in SAM, an
    interface takes place between SAM and the FAA's Departmental
    Accounting and Financial Information System (DAFIS). A PR is used to
    add or reduce funding for a project under the Contract.

b.  After EEP Data Sheets are prepared and forwarded to the ATO via
    Unitrack, the ATO will prepare a Procurement Request (PR). If there
    are several EEP data sheets, the ATO will "batch" the EEP Data
    Sheets in Unitrack and prepare one PR for the "batch." A number will
    be assigned to the PR and referred to as the PR number.

c.  It is important that the following information be provided on the
    PR.

```{=html}
<!-- -->
```
(1) The funding total on the PR should be correct. The arithmetic should
    be verified and cross-checked to ensure that the final value on the
    PR matches the sum of the values tied to the appropriation codes.

(2) Block 3, Originating Office Data  enter "ANI-XXX."

(3) Block 10, Add EEP Number and Location Code.

NOTE: Under the new Acquisition Management System (AMS), the 4th quarter
certification of PR's is no longer required.

d\. Before a PR and the EEP data sheets (as a package) are forwarded to
the Program Office for processing, the regional FCO will verify that the
fiscal data on the PR is accurate and that the funds are available, and
sign the PR as FCO. The ACO's signature is also required on the PR. When
the ATO and FCO sign a PR, advance copies will be delivered to the CO,
but the original document, and completed package, must be processed
through to the TO and CO before any action can be taken in a contract
modification. The PR is forwarded with the EEP data sheet(s) to the TSSC
Program Office. The Program Office then forwards the package to the CO
to complete the contract modification process.

e\. After the PR is awarded in SAM by the CO and a contract modification
is executed, the accounting office runs the SAM/DAFIS interface routine
to process the PR in DAFIS. The TSSC Business Manager, or designated
persons in the regions, will check the DAFIS file to see that the new
obligations (created by the submission of the PR) have been put into the
system. If so, the TSSC Business Manager, or designated persons in the
regions, will download the ODF-8 data from DAFIS, with the updated data,
and import it into the Unitrack System. See the Unitrack System User's
Handbook for detailed information on how to import the ODF-8 file. While
Unitrack is importing the ODF-8 file(s) it checks the accounting codes
and dollar amounts to ensure that the EEP data sheets are in agreement
with the DAFIS data, and to detect any discrepancies between the EEP
data sheets and DAFIS. If discrepancies are discovered, they should be
resolved at the regional level. If DAFIS is in error, the region should
check with its accounting offices to resolve the errors promptly.

f\. If imported data is in agreement, you will get a message on Unitrack
stating that data was imported successfully. Unitrack will automatically
track the region's EEP funds availability versus Work Releases issued.

## 3-8. NATIONAL (TSSC) PROGRAM OFFICE PROCESSING. {#national-tssc-program-office-processing. .unnumbered}

a\. The process includes:

(1) Acknowledging receipt of the PRs and EEPs.

(2) Reviewing the regional submissions to ensure that the proposed
    pro­jects are within the scope of the TSSC.

(3) Reviewing and verifying a modification of an existing EEP to ensure
    that the EEP being used for the project is correct.

(4) Notifying the ATO when their original PR is received by the Program
    Office.

(5) Preparing the EEP updates that will appear in the Contract
    modification.

(6) Reviewing the EEP data sheets submitted by the NPMs to develop the
    EEP summary for the national projects.

b\. If problems are detected in packages submitted by the regions, the
TSSC Program Office will coordi­nate corrective actions as expeditiously
as possible, thus ensuring timely Contract modifications. PR packages
with errors that cannot be resolved without adversely impacting the
processing schedule may be returned to the regions or held until a later
modification to accomplish the necessary corrections.

## 3-9. CONTRACT MODIFICATION DISTRIBUTION. {#contract-modification-distribution. .unnumbered}

The executed Contract modification will be distributed as follows:

a.  By the CO to the TSSC Program Office's TO and Business Manager/FCO.
    ASU has internal requirements for distribution to ABA-220 and RSSC.

b.  By the CO to the regional ATOs/ACOs. Distribution will include
    copies of each region\'s/center\'s PR with the modification.

c.  By the CO to the regional FCOs and the respective regional/center
    accounting office. The regional FCO, or designated person, is
    responsible for ensuring their accounting office has received and
    recorded the obligation into the FAA accounting records.

## 3-10. MODIFICATION SCHEDULE. {#modification-schedule. .unnumbered}

a\. **Regional Submission**. Regions should send in their completed PR
pack­age (that includes the EEP data sheets) as soon as completed to be
included in the next Contract modification.

To serve regional needs and in consideration of other funding and
planning dates, and changing regional priorities, the Contract
modification process requires that **PRs are received at Headquarters by
the *4th Thursday* of each month** (the 4th Thurs- day of the month is
not necessarily the last Thursday of the month).

b\. **TSSC Program Office**. The TSSC Program Office's goal is to
complete the modification (PRs received at headquarters, the Contract
modification completed and signed) within 25 working days**.**

c\. **Accounting Office Notification**. The regional FCO is to ensure
that a copy of each Contract modification is received by the appropriate
accounting office. A copy of the PR shall be provided with each Contract
modification so that the accounting office can record the obligation.

d\. **Overall Process.** Figure 3-4 describes the overall
funding/modification process utilized for the TSSC.

+---------------------+----------------+---------------+-------------+
| **[Acti             | *              | **C           | **Copies**  |
| vity]{.underline}** | *Responsible** | oordination** |             |
|                     |                |               | **[To]{.u   |
|                     | **[Office]     | **[With]{     | nderline}** |
|                     | {.underline}** | .underline}** |             |
+=====================+================+===============+=============+
| FUNDING             |                |               |             |
+---------------------+----------------+---------------+-------------+
| Receiving F&E       | Headquarters   | AFZ           |             |
| Appropriation and   | Budget Office  |               |             |
| Issuing PAs         |                |               |             |
+---------------------+----------------+---------------+-------------+
| Identifying         | R              | AFZ, ASD,     | ANS-103     |
| Manpower Estimate   | egions/ANS-103 | TSSC Business |             |
| for Annual F&E      | & Appropriate  | Manager       |             |
| Budget Submission   | Program        |               |             |
|                     | Managers       |               |             |
+---------------------+----------------+---------------+-------------+
| MODIFICATION        |                |               |             |
+---------------------+----------------+---------------+-------------+
| EEP Preparation     | Regional AF    | TO/ATO        | ANS-103     |
|                     | Divisions      |               |             |
|                     |                |               |             |
|                     | HQS Prog.      |               |             |
|                     | Mgrs.          |               |             |
+---------------------+----------------+---------------+-------------+
| EEP Review          | ANS-103        | Regions       |             |
+---------------------+----------------+---------------+-------------+
| Preparing EEP PR    | ANS-103        | Appropriate   | CO          |
| for TSSC funding    |                | ATO           |             |
|                     | Regional AF    | FCOs/Program  |             |
|                     | Divisions      | Managers & CO |             |
+---------------------+----------------+---------------+-------------+
| Contract            | CO             | ANS-103       | HQ Acctg.   |
| Modification        |                |               | (AAA);      |
|                     |                |               |             |
|                     |                |               | Reg. Acct., |
|                     |                |               |             |
|                     |                |               | ANS-103,    |
|                     |                |               | ACO, ATO, & |
|                     |                |               | FCO         |
+---------------------+----------------+---------------+-------------+
| Obligation          | ANS-103        | Appropriate   | CO          |
| Recording           |                | Accounting    |             |
|                     | ASU-340        | Office        |             |
|                     |                |               |             |
|                     | Regional AF    |               |             |
|                     | Divisions      |               |             |
+---------------------+----------------+---------------+-------------+

Figure 3-4. TSSC Funding/Modification Process

![](media/image3.wmf)

Figure 3-5. National WR Funding Process

![](media/image4.wmf)

\(1\) Regional ATO Does Not Develop Regional EEP

\(2\) Individual Regions May Assign Differently

\(3\) "Delegation of Contracting Authority"

**Figure 3-6. Regional WR Funding Process**

# WORK RELEASE PROCESS

## 4-1. GENERAL. {#general.-2 .unnumbered}

a.  RSSC shall incur costs under the Contract only in the performance of
    WRs and revisions to WRs (including WR Change Actions \[WRCA\])
    issued in accordance with procedures defined in paragraph 4-11 of
    this chapter. **No other costs are authorized without the
    [written]{.underline} consent of the CO or the ACO**.

b.  As the Contract is not a requirements-type contract, the FAA shall
    bear no obligation nor responsibility to issue a WR for which it has
    identified and incorporated into the Contract as an EEP item. RSSC
    **may not perform work that is not issued on a WR**. RSSC **may not
    incur costs in the performance of any WR for which an EEP has not
    been incorporated** into the Contract.

c.  During the performance of the Contract, all WRs will be issued in
    writing by the CO or ACO.

d.  For national WRs, a properly executed WR will, at a minimum, contain
    the signatures of the TSSC Program Manager, TO, CO, and the TSSC
    Business Manager. For regional WRs, a properly executed WR will, at
    a minimum, contain the signatures of the RPM/RPE, ATO, ACO, and FCO.

## 4-2. OBJECTIVE OF WORK RELEASES. {#objective-of-work-releases. .unnumbered}

a.  A WR specifies and provides technical direction for work to be
    accomplished under the TSSC. WRs will be of three types: Preliminary
    Work Releases (PWR), Final Work Releases (FWR), and Revised Work
    Releases (RWR).

b.  The objective of a WR, when properly executed, is to give written
    Government authorization to RSSC to allow it to incur costs against
    the Contract to prepare a Work Release Plan (WR Plan), revise a WR
    Plan, or perform the effort identified in the specifications.

## 4-3. TYPES OF WORK RELEASES. {#types-of-work-releases. .unnumbered}

a.  **Preliminary Work Release (PWR)**. The objective of the PWR is to
    identify the work that the FAA intends to assign to RSSC and to
    solicit a WR Plan from RSSC as to how it would accomplish the work.
    The PWR authorizes RSSC to incur only that cost which is reasonable,
    allowable, and allocable in the development of the WR Plan. The cost
    of this PWR is charged to the Program Management WR. Internal FAA
    review of the PWR is also used to determine the appropriateness of
    assigning the work to RSSC. The level of invoicing, either at the
    job order level (JON) or WR level, will be identified in the PWR.

b.  **Final Work Release (FWR).** The objective of the FWR is to assign
    work to RSSC. The work assigned is that identified in the
    specifications submitted by RSSC. The issuance of the FWR may not,
    in itself, be authorization for RSSC to start work on the WR. The
    start of RSSC's work is predicated on whether or not the requirement
    for a Notice to Proceed has been stipulated (see paragraph 4-9 of
    this chapter for additional information regarding Notice to Proceed
    requirements).

c.  **Revised WR (RWR)**. The objective of the RWR is to authorize
    changes that are necessary to some aspect of the FWR after it has
    been issued. A change in scope, cost or schedule (except priority
    6 - see paragraph 4-6 bulleted heading, "Block 'C' Schedule
    Priority") requires that an RWR be issued. It is important that an
    RWR clearly identifies the reason and justification for the change.
    Changes must be approved by the CO/ACO as appropriate.

```{=html}
<!-- -->
```
(1) **Work Release Change Action (WRCA)** is a type of RWR. See
    paragraph 4-10, WR Change Actions Process, for its definition and
    how to process a WRCA.

(2) **Close-Out Work Release Revisions**. The objective of the Close-Out
    WR revision is to terminate the WR. It indicates that all effort
    authorized under an FWR, plus any subsequent revisions to the FWR,
    has been canceled or completed. There are three types of Close-Out
    WR revisions, the "C," \"X,\" and the \"Z.\"

```{=html}
<!-- -->
```
(a) The **"C" Cancellation WR Revision**. The objective of the \"C\" WR
    revision is to cancel a PWR that has been issued, or a FWR that has
    been issued but the Notice to Proceed (NTP) has not been issued. If
    the FAA decides to cancel a WR after a NTP has been issued, and RSSC
    has made obligations against the WR, the procedure would be to
    follow the close-out procedure of issuing an "X" revision to stop
    the work and a "Z" to fiscally close it out.

(b) The **\"X\" Close-Out WR Revision**. The objective of the \"X\"
    revision is to alert all concerned that the WR is in close-out
    status and that **no additional obligations are authorized against
    the WR**. Once the "X" is issued, no new costs may be accrued, no
    new work can be added; the WR **cannot be revised** to a "F" WR. If
    it is determined that additional work is required, a new WR needs to
    be prepared. The \"X\" revision will be initiated on receipt of
    notification from RSSC that the project is physically complete or
    when the FAA determines that it wants work to cease on the WR for
    whatever reason. Multiple "X" revisions may be issued . For example,
    allocated funding may have to be changed depending on the latest
    work release cost information available from TSSC. These changes may
    also be made at the time the "Z" revision is issued.

(c) The **\"Z\" Close-Out WR Revision**. The objective of the \"Z\"
    revision is to close out the WR. When RSSC determines that a WR is
    fiscally complete a final invoice will be issued with other
    close-out documentation. Upon receipt of the final invoice, FAA will
    initiate the \"Z\" revision. The \"Z\" revision indicates that the
    project is now both physically and fiscally complete.

\(3\) **"P" Revision.** The "P," in this case, means
[Preliminary]{.underline} Revision, as opposed to a Final Revision. It
is used on the WR cover sheet as follows:
2-HQS-96-0006-R-002-[P]{.underline}; meaning a Preliminary revision of
the second revision of a WR. 2-HQS-96-0006-R-002-[F]{.underline}, means
a Final Revision of the second revision of a WR. See paragraph 4-6,
Preparation of WR Section A Cover Sheet. The "P" revision is prepared to
solicit a WR Plan from RSSC for a change to the scope, the funding, the
schedule, or the number of hours, to the original FWR or to subsequent
Revised WRs.

## 4-4. PRELIMINARY WORK RELEASE (PWR).  {#preliminary-work-release-pwr. .unnumbered}

a\. **PWR Preparation.** The PWR will usually be prepared by the FAA
RPM/RPE responsible for completion of the project. (The PWR cover sheet
will be prepared in the Unitrack system, see paragraph 4-6.) Once the
FAA has identified effort that is being considered for accomplishment
under the Contract, an **SOW and IGCE** must be developed. Coordination
with the TO/ATO may be helpful at this point to obtain all needed data
to prepare the PWR. Coordination is **required** when the WR involves
certain activities such as those listed below:

(1) WRs containing ADPE (Automated Data Processing Equipment) and ADPE
    support services, coordinate with ANS-103.

(2) All telecommunications work, coordinate with AOP-600.

(3) Work involving alterations, modifications, or new construction of
    any FAA facility on or in leased property shall be cleared through
    the regional real estate branch (national WRs are cleared with
    ASU-140) to ensure that the FAA has the authority to make changes to
    building(s) or land. A realty specialist will contact the property
    owner and obtain such rights required for the project.

(4) Installation of navigational facilities should also be coordinated
    with the real estate branch prior to the release of the PWR. No work
    shall commence at any airport or other real property site until the
    necessary real property rights have been officially documented by
    the real estate branch.

b\. **Initial PWR Discussion.** The FAA and RSSC will have an initial
PWR discussion, **prior to the issuance of the PWR**, to discuss the
scope and the FAA's expectations of the potential WR. The SOW is
delivered to RSSC prior to the initial PWR discussion so that RSSC will
be able to participate in the discussion in a meaningful way. As a
result of the initial PWR discussion, a final SOW will be prepared for
delivery with the PWR. This discussion is intended to clarify the
requirements of the WR and to address any items and/or issues that could
impact cost and/or schedule. The benefits of these discussions include
assurances that RSSC has a complete understanding of what the FAA
expects to accomplish.

(1) RSSC has a "PWR Checklist" they complete during the discussion. The
    Checklist consists of standardized questions that RSSC developed and
    must ask of the FAA that will help ensure RSSC's understanding of
    the potential work. RSSC completes in detail a PWR Checklist for
    every PWR. The questions cover areas that include, for example:
    Scope of Project; Points of Contact, including SMO Personnel and
    City/Permitting Official; Special Zoning Requirements; Project
    Phases required, site survey, CSER, Installation; Environmental
    Surveys required; has an FAA HAZMAT investigation been conducted,
    what are the findings; Who (FAA or RSSC) will locate or obtain
    Drawings, Site Access, Service Outages, Underground Utilities; is
    GFM/GFE to be provided; ODC requirements; Environmental
    requirements; what are the deliverables; Real Estate Exhibits, Red
    Line Drawings, CAI/JAI; Electrical requirements; are Licenses or
    Permits required; who will identify requirements; who will obtain
    the license or permit; is special training required; are there
    overtime requirements; what is the priority. The PWR Checklist
    includes many other pertinent questions relating to the task
    requirements. It will assist in further ensuring RSSC's
    understanding of FAA's requirements. RSSC's understanding will
    result in a more complete and accurate requirements submission by
    them and should reduce the time necessary for RSSC to complete the
    plan. An advanced copy of the checklist can be obtained from the
    local RSSC office to enable the PEs to be prepared with some
    answers.

(2) After an initial PWR discussion has been held with RSSC, a PWR will
    be issued to RSSC. The TO/ATO is responsible for reviewing the PWR
    for conformance with Contract scope, completeness, and format and
    will issue the PWR to the Contractor. The FAA review should take
    less time as well since the requirements will reflect only those
    tasks identified in the PWR, to the extent clarified at the meeting.
    Copies of the PWR will be provided to other organizations as
    appropriate.

c\. **Distribution.** After the PWR has been signed by the ATO, the ACO,
and RSSC, the ATO will then distribute copies of the entire PWR,
including the SOW and IGCE, but exclusive of drawings and technical data
not required to understand the SOW, to the TO and CO.

## 4-5. CREATING A NEW WR - PWR. {#creating-a-new-wr---pwr. .unnumbered}

The PWR is generated in the FAA TSSC-II Unitrack System. You must be an
authorized user of the Unitrack System to create a WR. The following
table notes the authorized users:

(a) 

+---------------+---------+------+-------+------+------+------------+
|               | **      | **A  | **    | **F  | *    | **GUESTS/  |
|               | ADMIN** | CO** | ATO** | CO** | *ENG | Othe       |
|               |         |      |       |      | /Oth | rs\*\*\*** |
|               |         |      |       |      | er** |            |
+---------------+---------+------+-------+------+------+------------+
| **WR**        |         |      |       |      |      |            |
+---------------+---------+------+-------+------+------+------------+
| -   Create    | ---     | No   | Yes   | No   | Yes  |            |
+---------------+---------+------+-------+------+------+------------+
| -   View      | ---     | Yes  | Yes   | Yes  | Yes  |            |
+---------------+---------+------+-------+------+------+------------+
| -   Edit      | ---     | Y    | Yes   | Y    | Yes  |            |
|               |         | es\* |       | es\* |      |            |
+---------------+---------+------+-------+------+------+------------+
| -   Delete    | ---     | No   | Yes   | No   | Yes  |            |
+---------------+---------+------+-------+------+------+------------+
| -   Revise    | ---     | No   | Yes   | No   | Yes  |            |
+---------------+---------+------+-------+------+------+------------+
|               |         |      |       |      |      |            |
+---------------+---------+------+-------+------+------+------------+
| **WR STATUS** |         |      |       |      |      |            |
+---------------+---------+------+-------+------+------+------------+
| -   View      | ---     | Yes  | Yes   | Yes  | Yes  |            |
+---------------+---------+------+-------+------+------+------------+
| -             | ---     | Yes  | Yes   | Yes  | Yes  |            |
|    Update\*\* |         |      |       |      |      |            |
+---------------+---------+------+-------+------+------+------------+
|               |         |      |       |      |      |            |
+---------------+---------+------+-------+------+------+------------+
| **WRCA**      |         |      |       |      |      |            |
+---------------+---------+------+-------+------+------+------------+
| -   Create    | ---     | No   | Yes   | No   | No   |            |
+---------------+---------+------+-------+------+------+------------+
| -   View      | ---     | Yes  | Yes   | Yes  | Yes  |            |
+---------------+---------+------+-------+------+------+------------+
| -   Edit      | ---     | No   | Yes   | No   | No   |            |
+---------------+---------+------+-------+------+------+------------+
| -   Delete    | ---     | No   | Yes   | No   | No   |            |
+---------------+---------+------+-------+------+------+------------+
|               |         |      |       |      |      |            |
+---------------+---------+------+-------+------+------+------------+
| **WRCA        |         |      |       |      |      |            |
| STATUS**      |         |      |       |      |      |            |
+---------------+---------+------+-------+------+------+------------+
| -   View      | ---     | Yes  | Yes   | Yes  | Yes  |            |
+---------------+---------+------+-------+------+------+------------+
| -   Update    | ---     | Yes  | Yes   | Yes  | Yes  |            |
+---------------+---------+------+-------+------+------+------------+

Figure 4-1. WR Module Authorization

\*Limited editing capabilities

\*\*Only able to update when the user group has control of the document

\*\*\*Guests/others can view only on any/all actions

Figures 4-2 and 4-3 on the following pages depict the regional and
national WR flows.

![](media/image5.wmf)

Figure 4-2. Typical Regional WR Flow

![](media/image6.wmf)

Figure 4-3. Typical National WR Flow

## 4-6. PREPARATION OF WR SECTION A COVER SHEET. {#preparation-of-wr-section-a-cover-sheet. .unnumbered}

a.  The WR cover sheet is generated in Unitrack. The cover sheet also
    provides data used in measuring RSSC's performance. Therefore it is
    important that the cover sheet be accurate and complete. Each WR
    cover sheet should be completed in accordance with the Unitrack
    User's Guide and this chapter. The following page shows an example
    of a WR Cover Sheet.

**TSSC II Work Release Cover Sheet**

**17-Jul-96**

**WR Name :**

**Prog. Name :**

**a. WR #: b. EEP Item#:**

**c. Schedule Priority** **Work Release Site**

**d. Start Dates** **e. Completion Dates**

> **Target Start Date: Target Completion Date:**
>
> **Schedule Start Date** **:** **Scheduled Completion Date** **:**
>
> **Actual Start Date:** **Actual Completion Date:**

**f. Budget Ceiling Dollars** **g. Budget Ceiling Hours**

> **Prior Estimate Dollars: Prior Estimate Hours:**
>
> **Type I Change Dollars:** **Type III Change Hours** **:**
>
> **Budget at Completion Dollars** : **Budget at Completion Hours**
> **:**
>
> **Type II Changes:** **Type IV Change:**
>
> **LRE Dollars:** **LRE Hours** **:**

**h. Allocation Dollars** **i. Funding Provided For: Services**:

> **Prior Amount** :
>
> **This Adjustment:**
>
> **Total Allocation** :

**j. Description of Project Work**

**FAA Req. Contact:** **Routing:** **Phone:**

**k. Accounting Data Allocated Total :**

> **Loc. Id MOD JON Suffix Appr Prior Alloc Alloc Material Alloc Labor
> Cum. Alloc Amount**

**l. Signature Block Routing Symbol Date**

**FAA PE/LPE:**

**FAA UNIT SUPERVISOR :**

**TO/ATO:**

**FCO:**

**CO./ACO:**

**Contractor Acknowledgment: RSSC**

Figure 4-9. TSSC-II Work Release Cover Sheet

b\. **The WR Cover Sheet entry descriptions are as follows:**

\(1\) **WR Name** - a brief descriptive statement identifying the work,
this is a required FWR entry.

\(2\) **Block "a" WR Number**. The WR number will be assigned in the
Unitrack System during the "Create New Work Release" process. The WR
number is an alpha-numeric identification number on all WRs using the
following format: N1-AAA1-NN2-NNNN3-A2-NNN4-A3. **N = numeric; A =
alpha.**

**N1**  Will always be 2 to indicate TSSC-II .

**AAA1**  Represents the three letter designation for the organization
developing the WR; e.g., HQS for national WRs, or ASW, AEA, ASO, etc.
for regional WRs.

**NN2**  Represents the last two digits of the **fiscal year** when the
FWR was issued. This number will not change if revision(s) are issued in
subsequent years.

**NNNN3**  Represents the sequential issuance number; 0001, 0002, etc.
Sequential numbers are automatically assigned in Unitrack and will not
be reused.

**A2**  Will always be an "R" to signify that the latest revision
number is shown in the next field.

> R  Revision

**NNN4**  Represents sequential number of the revision; 000, 001, 002,
etc.

**A3**  Signifies revision type:

> P  Preliminary
>
> F  Final
>
> C  Cancellation
>
> X  Begins close-out process (required work completed)
>
> Z  Completion (close-out)

\(a\) Thus the sixth (6th) WR issued by Headquarters would be numbered
2-HQS-95-0006-R-000-P, if issued as a PWR in FY-95. If this WR is issued
as a FWR, the number would become 2-HQS-96-0006-R-000-F, if issued in
FY-96. The preliminary version of the second revision to this WR would
be 2-HQS-96-0006-R-002-P, and when made final  2-HQS-96-0006-R-002-F
 **regardless of the Fiscal Year (FY) issued**. If for any reason the
prelimi­nary to the revision is not finalized, the revision number would
not be reused for a subsequent preliminary revision, unless it is
deleted before a subsequent PWR is issued. Ultimately when the WR **is
physically and fiscally completed** and closed out, a final revision (if
three previous revisions had been issued, with the "X" being #R-003-X)
will become 2-HQS-96-0006-R-004-Z.

\(b\) Regional WRs are numbered in a similar fashion, i.e., the seventh
(7th) PWR issued in the Central region in FY-95 would be
2-ACE-95-0007-R-000-P, and would become 2-ACE-96-0007-R-000-F if issued
as final in FY-96.

\(3\) **Block "b" EEP Item \#**. Represents the appropriate Contract EEP
item number. An FWR cannot be issued if the modified Contract does not
contain an EEP Item that covers the WR scope. This block is a required
FWR entry.

\(4\) **Block "c" Schedule Priority.**

\(a\) **Priority.**

1.  Defaults: As an initial entry, Unitrack will assign a schedule
    priority number of 5 to every WR. See next paragraph, "How It Works"
    for an explanation of the meaning of priority 5. The Unitrack
    schedule priority will be used by RSSC to determine the relative
    importance of all projects assigned by the region. By establishing
    FWR priorities, it is intended that RSSC will be able to better
    manage its staffing and workload, thereby ensuring that RSSC is
    working on the projects which are most important to the region,
    while maintaining enough low priority projects as fill-in work
    during lulls to avoid erratic staffing levels. This will also help
    FAA by avoiding the cost of training new TSSC hires resulting from
    staffing-up because of "pop-up" projects, and seasonal workloads.

2.  How it Works: The Unitrack priority field may be selectively
    overridden by the engineer or ATO to obtain a specific schedule
    tracking response from RSSC. Setting every FWR to priority 1 will
    defeat the purpose of this field (and it could cause generation of a
    lot of schedule variance reports). The TSSC Program Office will from
    time-to-time review the priorities used by each region to determine
    whether this priority field is being used effectively. A schedule 1
    priority will have its schedule variance tracked and reported with a
    zero-day tolerance. If the Work Release schedule slips by so much as
    one day, a variance report will be generated and reported in the
    monthly PSR, and an alert (in e:mail) will have been transmitted to
    the ATO, ACO, and FWR Project Engineer (FWR PE) upon its discovery.
    Similarly, priority 2 will be tracked with a 2-week schedule
    variance; priority 3, 3 weeks, etc. The FWR schedule will only be
    reset after issuance of a FWR revision or Work Release Change Action
    (WRCA) for priorities 1-5. Projects assigned a schedule priority of
    5 will have no schedule variance reporting in the PSR; only the CPR
    will reflect the schedule variance.

3.  Low Priority Projects: A project with a schedule priority of 5 or
    greater will not generate a schedule variance report for the PSR. If
    a priority 5 is used, the schedule will not be automatically
    rebaselined. Using a priority 5 will have the same effect as what
    presently happens under the present TSSC, i.e., no schedule variance
    reports, no automatic schedule rebaselining. For schedule priority 6
    or greater, the ATO, ACO, and FWR PE will receive an alert each time
    a priority 6 - 9 FWR reaches a variance of 4 weeks to keep them
    aware of the project, but that is all they will receive. For
    schedule 6 or greater FWRs, the planned schedule will automatically
    be set to the actual or current schedule each month a 4-week
    schedule variance occurs, effectively erasing the FWR schedule
    variance. The maximum schedule variance is 4 weeks for all priority
    6 through 9 FWRs. There is no maximum schedule variance for priority
    1 through 5.

\(b\) **Special Notes**: The FWR priority will change only when there is
a manual change to the field on an FWR revision or WRCA. The Unitrack
default schedule priority will be 5. **However**, the FWR PE or ATO
**must** change the priority if that is what is desired when the FWR is
revised.

\(5\) **Invoice Category.** Indicate WR to be invoiced at the WR or
JON/site level (determined by the region).

\(6\) **Block "d" Start Dates**. Both target and actual start dates are
needed for RSSC to determine the intensity of the effort to be provided,
or for the duration of a task (i.e., a Resident Engineer).

\(a\) **Target Start Date**. This is entered on a PWR. It indicates the
date when work is anticipated to start. This date should be changed when
the FWR is issued later than initially anticipated.

\(b\) **Scheduled Start Date**. This is entered on an FWR.

\(c\) **Actual Start Date**. This can be entered on an FWR (optional)
but it MUST be entered on an "X" revision WR. This is when work is to
begin after an FWR is issued. This is the date that will be tracked on
the Summary Cost Performance Report (Summary CPR). This date can be
useful when the FAA knows that equipment or airport access will be
unavailable until a future date. It is strongly recommended that this
block be completed for all FWRs.

\(7\) **Block "e" Target Completion Dates.**

\(a\) **Target Completion Date**. Used on PWR, the date is for
anticipated completion of the work under the WR. It is provided as
planning information to RSSC. This will indicate the intensity of effort
that the FAA is expecting under a particular FWR. Costs can be affected
when projects are done concurrently versus sequentially.

\(b\) **Scheduled Completion Date**. Used on FWR, the date project is
scheduled for completion after the FWR is issued. This is the date that
will be tracked and reported on the Summary Cost Performance Report
(Summary CPR). If an FWR is for just one phase or one part of the work
described in the requirements, the scheduled completion date should
correspond to that part of the work. The completion date will (usually)
be changed when the amount of assigned work is changed. If an FWR is for
less than the entire scope of work detailed in the requirements, the
technical directions should state that the FWR is for phase one only, or
the \"xyz\" work only. This block is a required FWR entry.

\(c\) **Actual Completion Date**. This date is required on an "X"
revision WR.

\(8\) **BLOCK "f" Budget Ceiling Dollars**. This block consists of
several financial components. By keeping the budget financial changes
and the reason or cause for each change separated, RSSC cost performance
tracking will be facilitated. Type I and Type II changes, as explained
below, are used to differentiate those revisions due to
FAA-initiated/approved changes and those due to cost escalation under
RSSC's control**. Incremental funding would not be reflected in this
block. Incremental funding will show up in block h, with optional
comments in block i**. Incrementally funded FWRs should show the total
budgeted cost for the scope of work assigned by the WR regardless of the
funding provided. This may sometimes result in a budgeted cost higher
than the funds allocated to the WR.

\(a\) **Prior Estimate Dollars.** The value will be zero for all initial
FWRs. In FWR revisions, this block will contain the value from the
Budgeted at Completion (BAC) dollars, which preceded this FWR revision.
RSSC's estimate of the amount of funds required to complete all work
included in the requirements after the FAA agrees with RSSC's cost, will
first appear on the "Type I Change" line.

\(b\) **Type I Change Dollars**. Type I Change represents the
revised-per-agreement estimate of all FAA-requested changes to be
performed under the FWR at issue (for the initial FWR issued, it
represents the estimated cost of the requirements). Example of events
that would result in a Type I Change are the increase or decrease in
scope of the project, unforeseen conditions that change the complexity
of the project, and Davis-Bacon subcontractor costs that are in variance
with the Work Plan estimate. Type I Changes can be positive or negative.
A reduction in scope or Davis-Bacon subcontractor costs significantly
below the original estimate are examples of incidents that would reduce
cost and result in a negative Type I Change.

1.  The revised figure results when the FAA changes the WR scope to meet
    project needs or budget constraints, and RSSC then revises the
    requirements. The FAA and RSSC should be in agreement on the
    magnitude of the budget changes resulting from the changed
    requirements. This agreement is the result of technical discussions
    taking place while the requirements are being finalized. The TO/ATO
    and project engineers must be aware that RSSC cannot be made to
    perform work unless the FAA is prepared to pay RSSC for that work.

2.  For FWR revisions the \"Budgeted at Completion dollars (BAC)\" line
    will change only by the amount of any Type I Change. "Type I
    Change\" is an incremental block, while \"Prior Estimate\" is
    cumulative. Adjustments should be shown on the \"Type I Change\"
    line. \"Type II Change\" line does not change the "BAC" line. The
    \"Type I Change\" line is used to record the FAA-requested changes
    to the FWR funding due to changes in the delivery schedule, type, or
    quantity of work required by the FWR.

3.  Initial RSSC cost estimates may be incomplete due to site cost
    averaging or other assumptions required to provide project cost
    estimates without benefit of visiting the site. After completion of
    the site visit and delivery of the RSSC site engineering report
    (CSER), there may be significant changes in the project estimate.
    This is only normal and should not cause concern. What should cause
    concern is if the cost to deliver the CSER starts to increase by 15
    to 20 percent or more. There are two methods to track CSER cost:

\- Issue an FWR for up to the CSER development only, or issue for the
complete FWR, but incrementally fund in phases. This will have the
advantage of requiring RSSC to notify the Government of funding
requirements at the 75-percent spending level. Also, if there is a cost
growth in the CSER, those increases will usually be easily identified
and placed in the cost estimate \"Type II Change\" line. A disadvantage
to this method is that more FWR revisions will have to be issued because
the WR is only for one phase of the project.

\- Issue an FWR for the complete project. In the breakdown of the cost
estimate, there will be a line item for CSER. Tracking changes to that
line item will yield insight into RSSC's cost performance for the CSER.
(The same can be done for other elements in the breakdown of the work
shown in project cost performance reports. This break- down is called
the Work Breakdown Structure \[WBS\].) This method has the advantage of
not requiring extra FWR revisions, but there will be no notification for
cost overruns of single WBS elements, and the timeliness of the cost
information will limit the Government\'s ability to prevent overruns.
This method is better suited to large and or long-duration WRs.

\(c\) **Budgeted at Completion Dollars (BAC)**. BAC is the total of the
prior revision\'s BAC and any Type I Change in the current revision to
the FWR. For the initial FWR, the BAC should equal the estimated cost on
RSSC's requirements.

\(d\) **Type II Change**. Type II Changes are used to record
RSSC-requested changes to the funding, which is not a change caused by
the FAA. Type II Changes will occur if more than RSSC's estimate is
required to complete some phase of engineering the FWR. Other potential
areas of cost escalation that could be a Type II Change is project
management, site survey, and equipment installation where the effort is
being accomplished using RSSC resources. If RSSC finds additional work
(outside the existing FWR scope) that should be performed, and the FAA
agrees to having that work performed, the resulting change is a Type I
Change, not a Type II Change. It is program policy that cases involving
differing site conditions are to be recorded as a Type I Change. The
Type II Change line differs from the Type I Change line in that the
value recorded as a Type II Change is a **cumulative number**.
Conversely, a Type I Change is an **incremental value** and is **entered
only on the revision** that added the work represented by that value.

\(e\) **Latest Revised Estimate (LRE) Dollars**. Total LRE is the total
of BAC and Type II Changes. It is the estimated cost to perform all FWR
work for which the FAA must reimburse RSSC.

\(f\) **Note: Relationships**. Note the relationships between values
placed into Block f: A **Type I Change is a budgeted cost increase or
decrease initiated/approved by the FAA or increase to BAC** beyond the
control of RSSC. A **Type II Change is a cost in excess** of the
budgeted cost (Requirements Cost Estimate) **that is within RSSC's
control**. BAC reflects the cumulative estimate for work as requested by
the FAA. Latest Revised Estimate reflects the cumulative estimate for
work as per RSSC's best estimate. In the case where the initial RSSC
cost estimate turns out to be higher than required, the FAA often adds
more work to the FWR, up to the value of the original estimate. In that
case, the BAC will increase equal to the value of the work added, this
will show as a Type I increase. That will indicate RSSC's \"cost
savings." The Cost Performance Reports will reflect the BAC, and thus
reflect an overall \"cost savings\" when the FWR is closed out.

\(g\) **Completed WRs**. When the "Z" revision is issued to close out a
WR, there should be no adjustments to the "Type I Change" dollars and
"BAC" dollars lines unless it is to reflect a change in scope. There
will be a positive value if there was an increase in scope or a negative
value if the scope of the WR was reduced. The Final Invoice cost should
be entered in the "LRE Dollar" line. The "Type II Change" line will
automatically be filled in. "If the Type II Change" line is negative,
the WR was completed below budget and is a positive indicator as to the
Contractor's performance; conversely, a positive value is a negative
indicator as to the Contractor's performance.

\(9\) **BLOCK "g" Budget Ceiling Hours**. This block represents RSSC's
estimated hours to complete all the work budgeted in Block f.
Incremental funded work would not be reflected in this block.

\(a\) **Prior Estimate Hours**. The value will be zero for all initial
FWRs. This block represents RSSC's estimate of fee credit employee hours
required to complete all work included in the requirements after FAA and
RSSC reach agreement on the requirements. Initial Budget Ceiling Hours
will first appear on the "Type III Change" line. Budget Ceiling Hours
are basically all direct labor hours of RSSC's personnel and first-tier
subcontract personnel who are dedicated to the accomplishment of direct
work under the Contract or who are working on a CO‑approved
cost-reimbursable or labor-hour subcontract. Excluded from Budget
Ceiling hours are labor hours provided by subcontractors performing
Davis-Bacon Act work and hours to perform rework. Budget Ceiling Hours
are taken from the specifications budget estimate after agreement
between FAA and RSSC on the number of hours for the scope and quantity
of work.

\(b\) **Type III Change Hours**. A Type III Change represents the
revised-per-agreement estimate of all work to be performed under the FWR
at issue. The revised figure results when the FAA decreases the WR scope
to meet budget constraints, and RSSC then revises its time estimate in
the requirements. This agreement should be the result of technical
discussions taking place while the requirements are being finalized.
Type III changes reflect changes in hours resulting from FAA-requested
or caused actions. Also included on this line will be hours that result
from Type II Changes, which are not rework, but may result from Type II
cost growths. This line entry is incremental, and adds into Prior Budget
Ceiling Hours on subsequent revisions.

\(c\) **Budget at Completion Hours**. Represents the total employee
hours that that FAA and RSSC agree are required to facilitate
accomplishing the work required by the FWR at issuance. This line is the
sum of the \"Prior Estimate Hours\" and Type III changes.

\(d\) **Type IV Change**. A "Type IV Change" is hours not subject to fee
under the terms of the Contract. Hours spent to correct a defect found
to be RSSC's responsibility (rework) would fall into this category. This
line entry is cumulative and is counted in the "Total," but not in any
of the entries above it.

\(e\) **Latest Revised Estimate (LRE) Hours**. This block is the total
fee and non-fee hours to be expended on this FWR. The FAA is required to
reimburse RSSC for all hours expended under this Contract. However, all
labor hours may not qualify for fee recovery, as for example in the case
of rework hours to correct an error committed by RSSC. This line is the
sum of the \"BAC Hours\" and \"Type IV Change" lines.

\(10\) **Block "h" Allocation Dollars**. This represents the limit
beyond which the FAA has no obligation to reimburse RSSC. The value
placed on this line may not exceed the amount obligated on the Contract
that has been allotted to the Regional EEP covering the project. This
block must be completed for the FWR to be issued.

\(a\) **Prior Amount**. Total allocation from previous revision.

\(b\) **This Adjustment**. Amount to be allocated for this revision.

\(c\) **Total Allocation**. Sum of "Prior Amount" and "This Adjustment."

\(d\) **Notification:** RSSC will notify the TO/ATO and the CO/ACO when
**75 percent of the funds allocated has been expended**, and provide the
latest estimate of funds required to complete the WR. There are at least
two cases when this amount might be less than the amount in Block f:
Phasing of projects by site and phasing by funding for discrete
milestones. When all funds are expended, regardless of budget value,
RSSC is to stop work on the WR.

\(11\) **Block "i" Funding Provided For Services**. Indicate specific
task being funded.

\(12\) **Block "j" Description Of Work**. This block is for entering
remarks onto a WR and is a required FWR entry. Block "j" describes the
FAA work requirement or identifies where the requirement is described.
This may include a brief summary or list of tasks included in the work
statement. This block should also describe any requirement placed on
RSSC restricting expenditures at any particular site or for Activity 4
within an FWR. Unless such requirements are spelled out in the FWR, RSSC
is tasked only to track and report expenditures based on the funds
allocated shown in block h. Phasing by site may result in an entry like,
\"This FWR is incrementally funded for the first three sites only.\"
Phasing by funding for milestones may result in an entry like, \"This
FWR is incrementally funded through CSER stage only.\"

\(13\) **Block "k" Accounting Data**. This block is required to be
completed for FWR issuance. Enter appropriation, system, and project
codes, and job order numbers. The Loc ID is to allow tying sites
described in block j to the appropriation data by use of a site or
location identifier.

\(14\) **Block "l" Signature Block**. This block is required to be
completed for FWR issuance. FWRs require Program/Project
Manager/Engineer, TO/ATO, CO/ACO, Business Manager/FCO and RSSC
signatures prior to issuance. Business Manager/FCO signature indicates
that funds obligated on the Contract are available as shown on the WR.
Signature by the CO/ACO indicates the FWR has been reviewed for
compliance with the Contract and procurement requirements.

c\. **Attachments.**

In addition to the data on the WR Cover Sheet, the following information
must also be attached to the PWR package.

\(1\) Government Furnished Information. The Government is responsible
for making accessible to RSSC all available Government specifications,
engineering drawings, standards, Government forms, designs, regulations,
etc., which are standard and/or site-specific in nature and required for
the accomplishment of TSSC work. To the extent known, Project Managers/
Engineers will identify, in each WR, all information to be Government
furnished.

\(2\) RSSC Furnished Documentation. RSSC will provide all site-specific
documentation required for the accomplishment of the work effort, which
is not identified in the WR as the responsibility of the Government to
provide and/or develop.

\(3\) Provide a Statement of Work (SOW). The SOW will specify all work
that RSSC is to accomplish, either directly, by reference to some other
place in the WR, or invoking a referenced document. The work expected of
RSSC should be explained in clear and understandable terms setting forth
explicitly what the deliverable product will be. The SOW should include
the addition and/or deletion of sites and identification of any
additional specifications that might be required. The work must be
defined in terms of some tangible product that can be physically
provided. The general specifications to package, ship, and/or store
items will be mentioned in the SOW. Also, specifications for the
deliverable product must be specified in terms that permit verification
of the product\'s acceptability.

\(4\) Specify shipping and storage requirements for GFE and GFM provided
to RSSC. On-site storage of RSSC acquired items that RSSC will use in
accomplishing the WR will need to be covered, but shipping requirements
will not normally need to be specified. Procedures for packaging,
shipping and storage will be in accordance with Order 4650.30.

(5) Specify the procedures and requirements covering how FAA will
determine the acceptability of the delivered product. Each WR should
identify a process that demonstrates that each requirement identified in
the SOW has been satisfied.

\(6\) Provide a requirements‑traceability matrix listing requirements
for deliveries and services and identify the SOW paragraphs specifying
the requirements. List the documentation associated with the project
that is to be turned over to FAA upon completion of the project.
Examples would be such items as final drawings, pertinent communications
with property owners and other persons, legal descriptions, specific
design data used by the RSSC engineer or a subcontractor (e.g., weather
data, frost depths, soil boring data, flood conditions, calculations,
etc.), power company agreements, flight check plans, test data, JAI
notes/exceptions, project coordination review comments, etc.

\(7\) Provide a list of attachments that includes any schedules,
identification of Government furnished equipment, materiel, services or
data required to accomplish the work identified in the SOW and other
requirements type information. All schedules pertaining to the WR will
be provided or referenced. This includes the date when site(s) will be
available for work start, delivery date(s) for systems and equipment
being acquired by the FAA and date(s) GFE, GFM, and/or GFI will be
available for or delivered to RSSC.

\(8\) Provide any other supplemental information that may be used to
advise RSSC of any information that may be useful in understanding the
project and advise RSSC of situations and conditions that will or may
affect accomplishing the WR, but do not fall within the topical areas of
other informational areas.

\(9\) Provide any special requirements such as special interfaces or
activities that happen concurrently or any contractual prohibitions.

d\. **Independent Government Cost Estimate (IGCE)**.

RPMs/RPEs using RSSC services are required to provide an IGCE for the
WR. The cost estimate is for accomplishing all work within the WR.

(1) The IGCE is an independent estimate compiled by the RPMs/RPEs for a
    project. It is used as part of the qualitative and quantitative
    (Q&Q) process for verification of the effort and costs associated
    with RSSC's Work Plan in response to the PWR.

(2) A mistake often made in preparing the IGCE is for the RPMs/RPEs to
    provide an estimate of the construction activity that they want RSSC
    to accomplish; however, they **should not focus** on the creation of
    a detailed cost estimate for the construction portion of any WR. The
    IGCE **should be focused** on those non-construction portions of the
    estimate, and include a budgetary estimate for construction. Since
    the FAA is usually "hiring" RSSC to provide the engineering design
    for a project, it is senseless for the FAA engineer to provide a
    detailed estimate of the construction activity that RSSC is to
    design. That estimate can only be sensibly developed after the
    project is designed. If the FAA engineer does that, there is no
    point in having RSSC design the job. RSSC is responsible for
    creation of a detailed construction cost estimate prior to issuance
    of their solicitation of any construction subcontract.

(3) What an engineer normally requires from RSSC is engineering, site
    survey, design, construction, installation, and commissioning
    support. Under circumstances such as this, the IGCE must include
    figures detailing the resources RSSC should reasonably be expected
    to apply in accomplishing the WR. It shall contain a chart with
    appropriate explanations indicating the type or work and who will
    perform it from title or skill categories. A cost shall be estimated
    for each category of work. This requires an estimate of the
    engineering skill types (Civil, Electronic, Mechanical, etc.), and
    number of hours for each skill. RSSC travel requirements must also
    be estimated in the IGCE.

(4) The recommended approach to developing an IGCE for a WR is to think
    of what type of skilled person(s) you would have the FAA hire to
    accomplish your project; how long would you think they should take
    to get the job done; and how much travel would be reasonable during
    the project. Any special things that they would need to perform the
    engineering (video cameras, portable data acquisition device i.e.,
    computers, test equipment, etc.) that are "big ticket" items or
    personal accountable property, and which cannot be GFE on the WR,
    must also be included in the IGCE. Don't be concerned about small
    items like survey flagging, film, expendable items, and items that
    are not personal accountable property. As for the construction
    activity, all that is required is a "budget" or plug-in number as a
    gauge for the range you expect the construction to fall within;
    i.e., is the job going to cost \$100,000? Is it more or less? Is it
    closer to \$20,000 or to \$50,000? Greater specificity is
    unnecessary since RSSC is going to competitively award the
    subcontract.

(5) In the case where RSSC performs the installation with its own
    employees, it is recommended that the FAA engineer think of what
    skilled technicians or engineers the installation crew would have on
    it; how long the crew should be at a site; and what tools and
    materiel they will usually need to complete the job. If the
    installation crew will require any "big ticket" items or personal
    accountable property, and it cannot be GFE on the WR, it must also
    be included in the IGCE. If RSSC will furnish R/G cables or purchase
    tools for example, the FAA engineer should list the cables or tools
    and provide an estimated cost for them in the IGCE as "other direct
    costs" (ODC) or "materiel" for the installation. As a general rule,
    an ODC is something that is not installed at the site or consumed
    during the installation. Hand tools would be an ODC item; conduit
    would be materiel.

(6) Another area that is often overlooked is the JAI or commissioning
    support and project as-built drawings. The FAA engineer must
    estimate the type of engineering or technical support required for
    the JAI or commissioning of the project. Keep in mind that RSSC may
    support the FAA in these activities, but they may not represent the
    FAA in any capacity; that is illegal. Nor may the RSSC personnel
    sign any form or document, except as an RSSC observer or as the
    preparer of the document or drawing.

## 4-7. WORK RELEASE PLAN.  {#work-release-plan. .unnumbered}

a\. **Purpose and Submission.** The WR Plan is initiated by the issuance
of a PWR. It is prepared by RSSC under the TSSC-II. The WR Plan serves
several purposes. RSSC shall submit the WR Plan to the TO or ATO, with a
copy to the CO/ACO within **14 calendar days after receipt of the PWR**,
or agreed to date between FAA and RSSC. It provides:

(1) A means of feedback from RSSC indicating its understanding of the
    task being assigned.

(2) A basis for comparing the resources that will be required with the
    IGCE.

(3) A schedule of expected project completion that can be compared with
    the FAA\'s requirements.

b\. **Work Release Plan Contents.** The WR Plan will be prepared as
specified in the Contract and will include, as appropriate, the
information summarized below in sufficient detail to permit evaluation,
review, and issuance of a final WR by the FAA:

(1) **Organization**. Identify personnel by labor category and skill
    level to be assigned to the WR including designation of the WR
    Manager.

(2) **Impact on Other Work**. Identify proposed approach to assure
    minimal adverse impacts on costs and schedules and identification of
    unavoidable impact on other work.

(3) **Performance Standards**. Identify approach proposed for assuring
    uniform high quality work.

(4) **Acceptance Criteria**. Identify approach proposed for assuring
    satisfaction of all WR requirements.

(5) **Estimated Costs**. Provide a detailed cost profile to include
    direct labor category hours, labor rates, subcontracting costs, any
    other direct costs such as travel, all overhead costs and G&A. When
    specified in the PWR, multiple projects/sites and multiple job order
    numbers (JONs) will be addressed separately.

(6) **Equipment/Materiel Delivery**. When applicable, indicate where
    RSSC desires the shipment of any GFE, GFM, or GFI (i.e., the site,
    the nearest AF field location, a regional warehouse, etc.).

(7) **Long Lead-Time Procurement**. Identify items, recommended sources,
    and estimated time required for delivery.

(8) **Milestone Schedule**. RSSC shall propose a milestone schedule in
    which proposed effort will be completed. This proposed schedule
    shall take into consideration the necessity to utilize resources
    from other WRs and the availability of these resources for
    anticipated WR efforts and the impact of interdependent activities
    such as delivery of GFP and GFE.

(9) **Documentation**. Identify all applicable specifications,
    standards, engineering drawings, and any other documentation
    required to assure proper completion of the project.

(10) **Quality**. Specify measures that RSSC will undertake in assuring
     the quality of its services and deliverables.

(11) **Other**. Provide any other data or information as requested in
     the PWR.

c\. **Work Release Plan Format.** RSSC shall adhere to the following
format in developing its WR Plan:

(1) **Cover Sheet.** Each WR Plan shall have a cover sheet that contains
    the following information:

```{=html}
<!-- -->
```
(a) The unique WR number and revision **[level]{.underline}** assigned
    by the FAA.

(b) The name of the WR effort.

(c) The date when the WR Plan is issued by RSSC.

(d) RSSC's address, telephone, and facsimile numbers.

```{=html}
<!-- -->
```
(2) **Estimated Costs.** RSSC will provide the detailed breakout of the
    estimated costs to complete efforts identified under the PWR or RWR.

(3) **Technical Approach.** RSSC will define its technical approach and
    methodology required to accomplish the WR effort.

(4) **Packaging, Shipping, and Storage.** RSSC will identify its
    approach on how to handle and adhere to any unique packaging,
    shipping, and storage requirements.

(5) **Acceptance and Inspection.** RSSC will identify its approach to
    acceptance and inspection of work as it applies to the Work Release.

(6) **Deliveries.** RSSC will provide a milestone schedule containing
    milestones of all major events required to deliver an acceptable
    product or service within time frames established in the PWR. The
    items that shall be addressed in the milestone schedule shall
    include, but are not limited to, the placement of orders for
    long-lead items, award of subcontracts, and special interfaces such
    as FAA interim acceptance or approval and interfaces with other FAA
    contractors.

(7) **List of Attachments.** RSSC will list all attachments that are
    included in the WR Plan.

(8) **Supplemental Information.** RSSC will provide any additional
    information that will provide insight to the FAA on its approach to
    accomplishing the Work Release effort. RSSC shall also provide any
    assumptions on which it has based its technical approach, such as
    FAA-furnished information or equipment.

## 4-8. EVALUATION OF THE CONTRACTOR'S WORK RELEASE PLAN.  {#evaluation-of-the-contractors-work-release-plan. .unnumbered}

The contractor's WR Plan will be evaluated by the RPM/RPE with the
assistance of the TO/ATO, TSSC Program Manager, and CO/ACO as
appropriate.

a.  **Quantitative and Qualitative (Q&Q) Analysis.** The FAA will
    conduct an evaluation of the WR Plan, called a Q&Q analysis. The
    review and analysis will assure that the proposed cost, timeliness,
    and staffing are appropriate, and that the WR Plan will meet the
    intended objectives of the project. A summary of the evaluation will
    normally be included in the Q&Q. The Q&Q is conducted to officially
    document that the WR Plan has been reviewed and that FAA agrees with
    the contractor's proposal. The Work Plan costs will be compared with
    the previously prepared IGCE. When variances occur between the IGCE
    and Work Plan costs, a Q&Q explanation must be prepared and added to
    the official WR file. The purposes of the analysis are to:

```{=html}
<!-- -->
```
(1) Determine if the offered costs reflect the value of the product or
    other work proposed.

(2) Display an understanding of how the contractor proposes/intends to
    do the work.

(3) Evaluate the estimating assumptions reflected in the cost proposal
    and determine whether or not they are in agreement with the approach
    described in the technical proposal.

b\. **Cost Variance.** When the variance between the contractor's
estimated cost in the WR Plan cost estimate and the IGCE is greater than
15%, the RPM/RPE will review the original IGCE and provide an
explanation as appropriate. A revised IGCE form may be created at this
time, but is not necessary. Factors that could justify revising the
original IGCE amount are issues not originally considered, different
technology being used, or more current market cost estimates. The Q&Q is
forwarded to the ACO for the official WR file. Any variance in hours or
dollars greater than 15% in labor costs must be addressed in the Q&Q. A
cost variance over 15% for material cost (or total WR cost) is not
necessary to address in the Q&Q, since competitive subcontract,
fixed-price award(s) for material and/or construction will guarantee the
lowest cost for these categories.

c\. **Discussion**. Discussions will be conducted between the TO/ATO
and/or RPM/RPE and the contractor to resolve technical approach, cost
variance, or other ambiguous issues in the contractor's WR Plan that
surface during the WR Plan evaluation, and to arrive at FWR content. The
CO/ACO is to be notified of the discussion. After discussions are
concluded, the FAA will determine if it is cost effective to pursue the
accomplishment of the effort via a Work Release. If so, the contractor
will then be required to submit any and all revisions to the WR Plan to
make it compliant with the FAA\'s requirements**.** It is important to
understand that TSSC-II is a CPFF Contract and the contractor is to be
reimbursed for all allowable and allocable costs incurred in
accomplishing tasks assigned under TSSC-II. The discussion should be
reported, documented, and placed in the official WR files.

## 4-9. ISSUING THE FWR.  {#issuing-the-fwr. .unnumbered}

The TO/ATO will develop and issue the FWR to RSSC **within 15 calendar
days** (this time frame may be changed by agreement between FAA and
RSSC) after the revised and fully acceptable WR Plan is submitted by
RSSC. The FWR will embody the FAA-approved WR Plan, which will contain
among other things, the estimated cost for accomplishing the work. A FWR
will not be issued until after RSSC\'s WR Plan has been approved.

a.  **Start of Performance**. The issuance of the FWR may or may not be
    authorization for RSSC to start work on the WR. The start of RSSC's
    performance under a WR will be predicated on whether or not the
    requirement for a NTP has been stipulated in the PWR or FWR. A NTP
    is a written notice from the FAA to RSSC in which RSSC is authorized
    to proceed with the work specified within a WR, on a specific date,
    such as a phasing of a project by site. Where an NTP is required,
    RSSC [shall not]{.underline} commence work nor incur costs under the
    FWR until the NTP has been issued by the CO/ACO. If an NTP is not
    required, then the start date contained within the duly executed FWP
    will become RSSC\'s commencement date.

b.  **Cancellation of FWR**. The FAA reserves the right to cancel any
    and all efforts involved in the WR process at any time during the
    process. Should the effort be canceled prior to the issuance of the
    FWR, or after issuance of the FWR but prior to issuance of an NTP, a
    \"C\" revision will be utilized and the Government will be liable
    only for costs that are reasonable, allowable, and allocable in the
    development of the WR Plan. After the FWR has been issued and work
    efforts have begun, the Government will utilize the \"X\" and \"Z\"
    revisions to cease efforts and close out the WR.

c.  **Binding Commitment**. The issuance of an FWR/NTP, properly
    executed by the FAA and acknowledged by a duly authorized
    representative of RSSC, shall constitute a binding commitment on
    behalf of RSSC to carry out all duties, responsibilities, and work
    efforts as delineated within the WR.

d.  **Required Signatures.** The FWR must have as a minimum the
    signatures of the responsible RPM/RPE, TO/ATO, CO/ACO, and the TSSC
    Business Manager/FCO. The CO/ACO is responsible for assuring that
    the FWR is within the TSSC scope and substance. The TSSC Business
    Manager/FCO is responsible for certifying the availability of funds.

e.  **Delayed FWR.** It is important that RSSC be kept current on what
    the FAA\'s intentions are in the issuance of the FWR so that RSSC
    can effectively allocate its resources. RSSC will be advised as soon
    as possible when it is determined that the TSSC is not the method by
    which the project is to be accomplished. A FWR will be issued within
    15 calendar days after the revised and fully acceptable WR Plan is
    submitted by RSSC. If within 15 calendar days of receipt of RSSC's
    WR Plan, the FAA has not issued an FWR, the TO/ATO will advise RSSC
    of the anticipated date for issuing the FWR or indicate a need for
    additional review time. When additional time for review is required,
    the TO/ATO will notify RSSC of the reasons, and provide a estimated
    date when the review will be completed. If the delay is due to
    misunderstanding or disagreements on the WR Plan, early resolutions
    will be sought. Delays in issuing the FWR can impact the scheduled
    completion date and cost.

f.  **Distribution.** Upon issuance of a regional FWR, the ATO will
    forward one complete copy, including the Q&Q, to the TO and CO for
    review. If any changes were made to the PWR after it was issued, all
    signed documentation reflecting the changes shall also be forwarded.
    The documentation must be signed by both the ATO and ACO and shall
    include a revised IGCE as appropriate. "Complete," as used above,
    shall mean that third party reviewers will be able to determine what
    actions are being authorized by reviewing the submitted package. The
    Work Plan need not be sent since it is available from RSSC's
    headquarters office.

## 4-10. PROCESSING REVISIONS TO A WR. {#processing-revisions-to-a-wr. .unnumbered}

a\. **Revised Work Releases**. Besides the WRCA, there are five
different Revised Work Releases (RWR); C, X, Z, P, and F; each
identified with a unique alpha character in the A3 field of the WR
number. See paragraphs 4-3 and 4-5 of this Handbook.

b\. **Format of an RWR**. The reason for the revision will determine the
RWR format. Normally an RWR requires only a cover sheet, if there is no
change in scope; also, the special revisions, "C," \"X,\" and \"Z,"
would normally only have a cover sheet. However, **when there is a
change in scope, an IGCE** is required, along with the supporting
sections as noted:

(1) Format of the \"C\" RWR. The "C" revision requires only a cover
    sheet. Blocks \"f," \"g,\" and \"h\" of the cover sheet would
    withdraw the funding and authorized fee credit hours.

(2) Format of the \"X\" RWR. The "X" revision requires only a cover
    sheet. Block \"e\" requires the actual physical completion date. The
    intent of the \"X\" revision to notify all interested parties that
    the WR is now in close-out status. The FAA can unilaterally issue an
    \"X\" WR. It would notify RSSC that no further charges are
    authorized against the WR and that RSSC is to begin close out
    procedures.

(3) Format of the \"Z\" RWR. The "Z" revision requires only a cover
    sheet. Blocks \"f,\" \"g,\" and \"h\" of the cover sheet would make
    the final adjustments required to balance out the accounts.

(4) Format of the "P" RWR. If there is a change in scope, the "P"
    revision requires a cover sheet, SOW, and IGCE.

(5) Format of the "F" RWR. If there is a change in scope, the "F"
    revision requires a cover sheet, SOW, IGCE, a WR Plan by RSSC, and a
    Q&Q by FAA. If the revision is for incremental funding or for
    revising a completion date, only a cover sheet is needed.

c\. **Distribution**. Upon issuance of a revised regional WR, the ATO
will forward one complete copy, including the Q&Q, to the TO and CO for
review. If any changes were made to the PWR after it was issued, all
signed documentation reflecting the changes shall also be forwarded. The
documentation must be signed by both the ATO and ACO and shall include a
revised IGCE as appropriate. For definition of "complete," as used
above, see paragraph 4-9 f. The Work Plan need not be sent since it is
available from RSSC's headquarters office.

## 4-11. WR CHANGE ACTION PROCESS. {#wr-change-action-process. .unnumbered}

a.  During the performance of effort specified in a Final Work Release
    (FWR), unanticipated changes may be required in the scope of the
    required effort. RSSC has no authority to perform work beyond the
    scope of the final work release without prior written approval from
    the CO or cognizant ACO. The procedures described herein apply to
    those instances where WR changes are initiated by RSSC. Presently,
    these procedures do not permit center or regional modification of
    National FWR's. If the need to change a National FWR arises, it must
    be processed through the appropriate Headquarters offices.

b.  When RSSC perceives a need for additional work release effort which
    was not included in the approved FWR, RSSC shall notify the TO or
    cognizant ATO, through the regional PE, that a revision to the FWR
    may be required, and shall provide a WRCA proposal. This proposal is
    similar to a WR Plan, except that it is initiated by RSSC in
    response to a change situation, rather than provided in response to
    a PWR. Each WRCA proposal shall include, at a minimum, the
    following:

```{=html}
<!-- -->
```
(1) A complete description of the proposed scope change as it relates to
    the existing FWR scope.

(2) A justification as to why the scope change should be incorporated
    into the FWR.

(3) A date after which additional unavoidable costs will be incurred if
    the scope change is not authorized, along with a detailed
    explanation of those additional costs.

(4) A complete cost proposal which reflects the work elements that are
    proposed to be expanded or added to the FWR scope.

(5) If the cause of the scope change results from an RSSC subcontract
    under the FWR, RSSC shall also include an explanation as to why the
    requested scope change was not included in the original subcontract
    specifications.

(6) Each proposal shall include a summary of all previously executed
    WRCA's for that WR, to ensure proper funds tracking.

```{=html}
<!-- -->
```
c.  RSSC shall provide WRCA's which are signed by a duly authorized
    official. The above information shall be entered into an MS Excel
    file. The completed Excel file shall be transmitted to the FAA or
    provided on a disk with the signed hard copy of the WRCA proposal.
    RSSC shall transmit WRCA's to the FAA either via fax or other more
    expedient, cost effective method acceptable to the CO/ACO. The WRCA
    proposal shall include the FWR number and title and shall follow the
    requirements described above. To facilitate tracking, each WRCA
    shall have a unique identification number consisting of the building
    site's "three letter" identifier (in accordance with FAA Order
    7350.5) and a sequential number. For example, the first change order
    for Albuquerque (three letter site identification, ABQ) shall be
    assigned the number ABQ 01; the second change order shall be
    assigned the number ABQ 02; etc.

NOTE: WRCA's which gain FAA approval will also be assigned the next
available WR revision number for the WR under which the work is taking
place. These FAA approved WRCA's shall have the same effect as a WR
revision for budget, schedule, funds or hours allocation, scope or other
such WR data which may be changed via regular contract WR revision
procedures.

d.  The process for submission, review and approval of WRCA's will be:

```{=html}
<!-- -->
```
(1) RSSC transmits a complete WRCA (as described above) to the
    appropriate FAA PE ( with copies to the cognizant TO/ATO) with a
    filled out WRCA cover sheet attached.

(2) The FAA PE performs a written quantitative and qualitative
    evaluation (Q&Q) of the proposal. The FAA PE will evaluate all
    WRCA's for technical merit and cost and provide a written Q&Q for
    FAA records. If the FAA PE does not concur with the WRCA, it will be
    rejected and returned to RSSC without further action.

(3) An approved WRCA and Q&Q are routed to the cognizant TO/ATO for
    review and concurrence. The ATO must review the WRCA and Q&Q to
    determine whether the costs should be tallied as Type I or Type II,
    and whether there is a requirement for additional Type III Fee
    Credit Hours or if Type IV rework hours should be allocated. The
    WRCA shall be forwarded to the cognizant ACO after the ATO completes
    their position of the review.

```{=html}
<!-- -->
```
(4) The cognizant ACO will review the WRCA for scope and to ensure that
    all required components are provided. Upon approval , the CO/ACO
    shall then send it to RSSC.

```{=html}
<!-- -->
```
(5) RSSC shall acknowledge acceptance of the WRCA via signature on the
    WRCA cover sheet upon receipt from the CO/ACO; then return the
    original copy to the CO/ACO.

```{=html}
<!-- -->
```
(6) The original WRCA shall be placed into the official WR file in with
    other approved WR revisions.

    NOTE: Only the FAA CO or the ACO may authorize RSSC to incur costs
    in the performance of WRCA's . RSSC may not incur costs for any
    effort which exceeds the scope of the contract or/and approved final
    or revised Work Releases without prior written CO/ACO authorization.
    Prior to CO/ACO approval of the WRCA, any costs incurred by RSSC
    shall be at their own risk and may not be reimbursed, subject to the
    terms and conditions of the contract.

```{=html}
<!-- -->
```
e.  There is no limit on the value of WRCA's which may be approved by
    the ACO (subject to available obligations and any limits of the
    ACO's warrant) and available contract obligations.

f.  When RSSC perceives a need to change the scope of a FWR or issue a
    change order for the scope of a FWR due to changed circumstances of
    a subcontract, and the FAA determines that time is insufficient to
    process a fully executed WRCA, an unpriced WRCA will be processed.
    There is no authority to grant verbal approval for any WRCA to RSSC.
    In case of emergency, the following procedure is to be followed:

```{=html}
<!-- -->
```
(1) Work Release Change Action Emergency Procedure

In the event that an emergency arises on-site during performance of a
Work Release, it is understood that the process for issuing Change
Actions to the WR are sometimes insufficient to provide approval to
proceed with an emergency type change. Therefore, a process for
authorizing emergency changes is hereby provided. The term "emergency"
is somewhat subjective but the scope of the definition for this Handbook
is that an emergency is something that if not resolved quickly could
result in shutting down a facility, incurring additional damage to
property, may adversely impact personal safety, or may violate security.
These are issues that require immediate attention and can't wait longer
than approximately 24 - 48 hours for the standard Change Action
procedure to formally authorize the emergency change. The process for
authorizing emergency type change is as follows:

(a) The RSC Resident Engineer (RE), crew chief, or supervisor shall
    notify the FAA Project Engineer or ATO (verbally, Fax, e-mail is
    acceptable) of the emergency. A rough order of magnitude (ROM)
    estimate may be included with the request.

(b) The FAA PE shall then provide written request for an emergency
    Change Action (Fax or e-mail is acceptable) to the TO/ATO, the
    TO/ATO will then forward the request, recommending
    approval/disapproval to the CO/ACO. If the TO/ATO or Alternate is
    unavailable then the PE shall state such and forward the request for
    an emergency change action directly to the CO/ACO (as applicable).
    The request shall state the problem and briefly explain the
    emergency nature of the change (what is required and the emergency
    nature -- i.e., why it can't wait for the official Change Action).

(c) If the CO/ACO believes the action truly is an emergency, they shall
    then request, in writing (Fax, e-mail) a ROM estimate from the
    Contractor, if one has not been provided. The Contractor may provide
    a ROM (provided by signed FAX) in advance of the request from the
    CO/ACO in order to accelerate the process. The CO/ACO need not
    further request the ROM if one is provided in advance of the
    request. The ROM itself will suffice as a sufficient paper trail for
    the process.

(d) Once the CO/ACO receives the ROM, they must verify that funds exist
    in the EEP at least for the amount of the ROM. If funding does not
    already exist in the EEP, then the CO/ACO shall notify (FAX or
    e-mail) the Contractor with a copy to the TO/ATO and PE that the
    official Change Order Request process must be followed due to
    insufficient funding available to cover the emergency action.

(e) If funding does exist, the CO/ACO may approve and authorize the
    emergency request in writing (Fax or e-mail), for a not-to-exceed
    (NTE) amount equal to the ROM. The approval notice to the Contractor
    shall also state that the formal process for the Work Release Change
    Action must follow to back up the approved emergency as soon as
    practicable after the approval is granted. Every attempt shall be
    made to complete the official paperwork process within five business
    days after date of the emergency approval.

(f) Note: Approval of the emergency action in accordance with a NTE
    funding amount is designed only to continue work when an emergency
    arises and is not intended to replace the standard Change Action
    process. The ROM is not a NTE proposal from the Contractor but a
    best estimate per the emergency nature of the effort, thus providing
    a basis for an NTE approval from the CO to keep work moving during
    the standard Work Release Change Action (WRCA) process. It is not
    acceptable to issue another emergency request for the same emergency
    based solely upon the justification that the NTE amount may be
    exceeded prior to completion of the official WRCA.

```{=html}
<!-- -->
```
g.  In the event that the total cost of the WRCA cannot be definitized
    prior to commencement of effort, and the FAA determines that time is
    insufficient to process a fully executed WRCA, RSSC shall contact
    the CO/ACO to obtain written permission (via Fax if necessary) to
    negotiate a ceiling cost in order to begin the proposed work with
    its subcontractor, after the CO/ACO has established a not-to-exceed
    (NTE) amount, which RSSC shall use as the maximum authorized
    additional value for the subject work until the WRCA is definitized
    and fully executed. To the extent that the information is available,
    RSSC shall prepare a WRCA proposal as described above. If a NTE
    authorization is granted, RSSC shall ensure that they or their
    subcontractor will be able to halt work under the WRCA (if the NTE
    amount is reached before completion) such that the "work in
    progress" is safe and does not jeopardize any other work, system,
    equipment, etc., at the work site or any site related to the work
    site.

h.  The FAA PE will evaluate RSSC's WRCA proposal for technical merit
    and cost and provide a written Q&Q along with a recommendation to
    the CO/ACO of an acceptable final cost for the total work to be
    covered by the WRCA and sign the WRCA cover sheet. Upon CO/ACO
    receipt of the PE's recommendation, RSSC will be contacted to
    negotiate a final price for the WRCA. When RSSC provides the final
    price, the WRCA will be definitized. If the FAA PE does not concur
    with the proposal contained in the WRCA, it will be rejected and
    returned to RSSC. The CO/ACO will notify RSSC to terminate the work
    begun under the not-to-exceed authorization. Allowable costs will be
    reimbursed.

i.  As previously stated, RSSC is not authorized to incur costs for any
    effort which exceeds the scope of the approved FWR until FAA CO/ACO
    approval has been granted via an approved WRCA or written NTE
    authorization.

+----------+----------------+---------+----------+----------+---------+
|          | **TSSC II WORK |         |          |          |         |
|          | RELEASE CHANGE |         |          |          |         |
|          | ACTION**       |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         | RSSC     | (to be   |         |
|          |                |         | Proposal | proved   |         |
|          |                |         | #:       | by RSSC) |         |
+----------+----------------+---------+----------+----------+---------+
| Work     | 2-A??-#        |         | Date     | system   |         |
| Release  | #-####-R-###-F |         | R        | to       |         |
| No:      |                |         | eceived: | insert   |         |
|          |                |         |          | date     |         |
+----------+----------------+---------+----------+----------+---------+
| WRCA ID  | This & rev \#  |         |          | Action   | (to be  |
| No:      | assigned after |         |          | Deadline | proved  |
|          | FAA approves   |         |          | Dat      | by      |
|          |                |         |          | e(\*\*): | RSSC)   |
+----------+----------------+---------+----------+----------+---------+
| *Des     |                |         |          |          |         |
| cription |                |         |          |          |         |
| of       |                |         |          |          |         |
| proposed |                |         |          |          |         |
| scope    |                |         |          |          |         |
| change   |                |         |          |          |         |
| or TSSC  |                |         |          |          |         |
| overtime |                |         |          |          |         |
| work as  |                |         |          |          |         |
| it       |                |         |          |          |         |
| relates  |                |         |          |          |         |
| to       |                |         |          |          |         |
| existing |                |         |          |          |         |
| FWR      |                |         |          |          |         |
| scope:*  |                |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         |          | (to be   |         |
|          |                |         |          | proved   |         |
|          |                |         |          | by RSSC) |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         |          |          | Co      |
|          |                |         |          |          | ntinued |
|          |                |         |          |          | on      |
|          |                |         |          |          | att     |
|          |                |         |          |          | achment |
|          |                |         |          |          | as      |
|          |                |         |          |          | r       |
|          |                |         |          |          | equired |
+----------+----------------+---------+----------+----------+---------+
| *Justi   |                |         |          |          |         |
| fication |                |         |          |          |         |
| why      |                |         |          |          |         |
| overtime |                |         |          |          |         |
| hours    |                |         |          |          |         |
| should   |                |         |          |          |         |
| be       |                |         |          |          |         |
| approved |                |         |          |          |         |
| or       |                |         |          |          |         |
| existing |                |         |          |          |         |
| FWR      |                |         |          |          |         |
| scope    |                |         |          |          |         |
| should   |                |         |          |          |         |
| be       |                |         |          |          |         |
| c        |                |         |          |          |         |
| hanged:* |                |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         |          | (to be   |         |
|          |                |         |          | proved   |         |
|          |                |         |          | by RSSC) |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         |          |          | Co      |
|          |                |         |          |          | ntinued |
|          |                |         |          |          | on      |
|          |                |         |          |          | att     |
|          |                |         |          |          | achment |
|          |                |         |          |          | as      |
|          |                |         |          |          | r       |
|          |                |         |          |          | equired |
+----------+----------------+---------+----------+----------+---------+
| *(       |                |         |          |          |         |
| \*\*)Exp |                |         |          |          |         |
| lanation |                |         |          |          |         |
| of       |                |         |          |          |         |
| ad       |                |         |          |          |         |
| ditional |                |         |          |          |         |
| cost     |                |         |          |          |         |
| which    |                |         |          |          |         |
| may be   |                |         |          |          |         |
| incurred |                |         |          |          |         |
| if       |                |         |          |          |         |
| Action   |                |         |          |          |         |
| Deadline |                |         |          |          |         |
| Date is  |                |         |          |          |         |
| not      |                |         |          |          |         |
| met:*    |                |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         |          | (to be   |         |
|          |                |         |          | proved   |         |
|          |                |         |          | by RSSC) |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         |          |          | Co      |
|          |                |         |          |          | ntinued |
|          |                |         |          |          | on      |
|          |                |         |          |          | att     |
|          |                |         |          |          | achment |
|          |                |         |          |          | as      |
|          |                |         |          |          | r       |
|          |                |         |          |          | equired |
+----------+----------------+---------+----------+----------+---------+
| *If WRCA |                |         |          |          |         |
| is for a |                |         |          |          |         |
| sub      |                |         |          |          |         |
| contract |                |         |          |          |         |
| scope    |                |         |          |          |         |
| change,  |                |         |          |          |         |
| explain  |                |         |          |          |         |
| why this |                |         |          |          |         |
| req      |                |         |          |          |         |
| uirement |                |         |          |          |         |
| was not  |                |         |          |          |         |
| included |                |         |          |          |         |
| in       |                |         |          |          |         |
| original |                |         |          |          |         |
| sub      |                |         |          |          |         |
| contract |                |         |          |          |         |
| specif   |                |         |          |          |         |
| ications |                |         |          |          |         |
| during   |                |         |          |          |         |
| bidding* |                |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
| *(D      |                |         |          |          |         |
| iffering |                |         |          |          |         |
| Site     |                |         |          |          |         |
| Co       |                |         |          |          |         |
| nditions |                |         |          |          |         |
| must     |                |         |          |          |         |
| meet     |                |         |          |          |         |
| requ     |                |         |          |          |         |
| irements |                |         |          |          |         |
| of FAR   |                |         |          |          |         |
| 52.236-2 |                |         |          |          |         |
| &        |                |         |          |          |         |
| 52.      |                |         |          |          |         |
| 236-3):* |                |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         |          | (to be   |         |
|          |                |         |          | proved   |         |
|          |                |         |          | by RSSC) |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         |          |          | Co      |
|          |                |         |          |          | ntinued |
|          |                |         |          |          | on      |
|          |                |         |          |          | att     |
|          |                |         |          |          | achment |
|          |                |         |          |          | as      |
|          |                |         |          |          | r       |
|          |                |         |          |          | equired |
+----------+----------------+---------+----------+----------+---------+
| Type I   | Cost Summary   | Fee     | Labor    | Material | Total   |
|          | (this FWR)     | Credit  | Funds    | Funds    | Funds   |
|          |                |         |          |          |         |
|          |                | Hours   |          |          |         |
+----------+----------------+---------+----------+----------+---------+
| Change   | From prior     | From WR | From WR  | From WR  | 0       |
| \$       | Rev. #, Exist. | cov     | co       | co       |         |
| Amount   | Nat\'l FWR     | ersheet | versheet | versheet |         |
|          | EAC→           |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
| input by | Change (or     | p       | proposed | proposed | 0       |
| ATO      | N.T.E.\*)      | roposed | value    | value    |         |
|          | amount for     | value   | from     | from     |         |
|          | this WRCA→     | from    | RSSC/    | RSSC     |         |
|          |                | RSSC    | ATO      | /ATO     |         |
|          |                | /ATO    | input    | input    |         |
|          |                | input   |          |          |         |
+----------+----------------+---------+----------+----------+---------+
|          | New FWR LRE    | 0       | 0        | 0        | 0       |
|          | Dollars→       |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
|          | Total Prior    | From    | From     | From     | 0       |
|          | Site WRCA\'s→  | U       | trking   | tracking |         |
|          |                | nitrack | system   | system   |         |
+----------+----------------+---------+----------+----------+---------+
|          | Total all      | From    | From     | From     | 0       |
|          | Prior WRCA\'s→ | U       | trking   | tracking |         |
|          |                | nitrack | system   | system   |         |
+----------+----------------+---------+----------+----------+---------+
| Loc Id.  | Accounting     |         | This     | This     | Change  |
|          | Codes:         |         | Labor    | Mat\'l   | Amount  |
|          |                |         | Alloc.   | Alloc.   | per     |
|          |                |         |          |          | Code    |
+----------+----------------+---------+----------+----------+---------+
| Note:    | Selected From  |         | input by | input by | 0       |
| Only one | Unitrack by    |         | ATO      | ATO      |         |
|          | ATO            |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
| Loc. Id. | Selected From  |         | input by | input by | 0       |
| allowed  | Unitrack by    |         | ATO      | ATO      |         |
| per      | ATO            |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
| each     | Selected From  |         | input by | input by | 0       |
| WRCA.    | Unitrack by    |         | ATO      | ATO      |         |
|          | ATO            |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
| TSSC     |                | Title   | (to be   | Phone:   | (to be  |
| Contact  |                |         | proved   |          | proved  |
| Name:    |                |         | by RSSC) |          | by      |
|          |                |         |          |          | RSSC)   |
+----------+----------------+---------+----------+----------+---------+
| FAA Req. | From WR        | R       | From WR  | Phone:   | From WR |
| Contact  | coversheet     | outing: | co       |          | cov     |
|          |                |         | versheet |          | ersheet |
+----------+----------------+---------+----------+----------+---------+
|          | Signature      |         |          | Routing  | Date    |
|          |                |         |          | Symbol   |         |
+----------+----------------+---------+----------+----------+---------+
| Requ     |                |         | ( Agree  |          |         |
| irements |                |         | D        |          |         |
| E        |                |         | isagree) |          |         |
| ngineer: |                |         | with     |          |         |
|          |                |         | this     |          |         |
|          |                |         | req      |          |         |
|          |                |         | uirement |          |         |
+----------+----------------+---------+----------+----------+---------+
| (Q&Q     |                |         |          |          | From WR |
| Required |                |         |          |          | cov     |
| For      |                |         |          |          | ersheet |
| Changed  |                |         |          |          |         |
| Items)   |                |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+
| TO/ATO   |                | ( Agree |          |          |         |
|          |                |         |          |          |         |
|          |                | Di      |          |          |         |
|          |                | sagree) |          |          |         |
|          |                | with    |          |          |         |
|          |                | scope   |          |          |         |
|          |                | change  |          |          |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         |          | From WR  |         |
|          |                |         |          | co       |         |
|          |                |         |          | versheet |         |
+----------+----------------+---------+----------+----------+---------+
| FCO      |                | ( Agree |          |          |         |
|          |                |         |          |          |         |
|          |                | Di      |          |          |         |
|          |                | sagree) |          |          |         |
|          |                | with    |          |          |         |
|          |                | source  |          |          |         |
|          |                | of      |          |          |         |
|          |                | funds   |          |          |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         |          | From WR  |         |
|          |                |         |          | co       |         |
|          |                |         |          | versheet |         |
+----------+----------------+---------+----------+----------+---------+
| CO/ACO   | ( Approve      |         |          | (        |         |
|          | Disapprove)    |         |          | \*Check  |         |
|          | this           |         |          | here if  |         |
|          | acquisition    |         |          | this     |         |
|          |                |         |          | WRCA is  |         |
|          |                |         |          | not      |         |
|          |                |         |          | defi     |         |
|          |                |         |          | nitized) |         |
+----------+----------------+---------+----------+----------+---------+
|          |                |         |          | From WR  |         |
|          |                |         |          | co       |         |
|          |                |         |          | versheet |         |
+----------+----------------+---------+----------+----------+---------+
| Co       |                |         |          |          | RSSC    |
| ntractor |                |         |          |          |         |
| Proposal |                |         |          |          |         |
| Si       |                |         |          |          |         |
| gnature: |                |         |          |          |         |
+----------+----------------+---------+----------+----------+---------+

Figure 4-5 TSSC-II Work Release Change Action Form

TSSC-II WORK RELEASE FILE INDEX

WR \# \_\_\_\_\_\_\_\_\_\_\_\_\_\_ WR Title
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

Tab \#

\_\_\_\_\_ EEP Data Sheet

\_\_\_\_\_ IGCE

\_\_\_\_\_ Pre-Work Release Meeting Notes

\_\_\_\_\_ PWR w/SOW

\_\_\_\_\_ Waivers to FAA Orders, Specs, public design documents

\_\_\_\_\_ WP

\_\_\_\_\_ Q&Q

\_\_\_\_\_ FWR/NTP

\_\_\_\_\_ Revisions/WRCAs (Separate by Tabs)

\_\_\_\_\_ 75% Notice

\_\_\_\_\_ Justification of Award/Subcontract Notice

\_\_\_\_\_ Labor Interviews (DB Work)

\_\_\_\_\_ List of GFP/GFM (4650-12), Contractor Receipt of
GFP/GFM,Use/Disposition of GFP/GFM

\_\_\_\_\_ Invoice Payment Sheets/Signed Certification Letters/Final
Invoice

\_\_\_\_\_ Summary of Acquired Property Report

\_\_\_\_\_ TSSC Customer Satisfaction Survey - Project Engineer
(Semi-Annual and Work Release Completion)

\_\_\_\_\_ CAI/JAI

\_\_\_\_\_ Miscellaneous Correspondence

\_\_\_\_\_ Statement Indicating Location of Reference Documents,
Drawings, Specifications

\_\_\_\_\_ WR Close-out Checklist

**Figure 4-6 TSSC-II Work Release File Index**

## 4-12. SCHEDULING. {#scheduling. .unnumbered}

The Government and RSSC both have responsibilities for scheduling. The
Government will provide equipment delivery schedules and task sequencing
or priority schedules (see the bulleted heading in paragraph 4-6, Block
"e" Completion Dates). RSSC will develop specific accomplishment
schedules for inclusion in individual WRs. The WR will provide RSSC with
equipment delivery and/or priority schedules for RSSC use in planning
and sequencing the overall program effort.

a.  **National-Specific Work**. Scheduling for national-specific work
    tends to be driven by equipment delivery dates. For example, TSSC
    work on Mode S and AWOS site preparation must be completed and the
    site ready to accept Mode S and AWOS equipment prior to their
    delivery. ASR‑7 and 8 leapfrog scheduling is predicated on ASR‑7 and
    8 equipment availability that in turn is driven by ASR‑9 delivery
    and commissioning dates.

```{=html}
<!-- -->
```
a.  **Regional Work**. For regional work, prioritized implementation
    schedules will be included in each individual WR.

## 4-13. PRODUCT/WORK ACCEPTANCE. {#productwork-acceptance. .unnumbered}

a.  **Government Responsibility**. The Government bears overall
    responsibility for accepting the quantity and quality of
    TSSC-delivered products. Each WR will describe each deliverable
    sufficiently as to provide a means of judging acceptability. Where
    the WR is based on a Level-of- Effort basis, as is the case where
    RSSC is tasked with providing an on-site resident engineer (RE) to
    oversee the work of another Government contractor, measures of
    acceptable performance will be contained in the WR. All deliverable
    products will be accepted by the TO or ATO, as appropriate. In cases
    where deliverable products fail to meet acceptance criteria, the
    TO/ATO will notify the CO/ACO and RSSC.

b.  **Inspection Criteria**. In accordance with the procedures and
    requirements specified in the FWR for acceptance inspection, the FAA
    project manager or engineer will verify to the TO/ATO that work
    accomplished was accomplished in a satisfactory manner.

```{=html}
<!-- -->
```
(1) Witnessing and Inspection. Where appropriate, FAA personnel may
    witness RSSC's verification actions and verification data as a part
    of RSSC's CAI. Typically, WRs will require an acceptance inspection
    upon completion of the work. In the case of WRs where RSSC is
    responsible for only a part of the total work to be accomplished
    (such as site preparation or resident engineering) and another
    contractor installs the system or equipment, the acceptance actions
    will be completed separately for the work covered by the WR.

(2) Test and Evaluation. It may be desirable for the FAA to perform some
    tests and evaluations or to have another Government agency or
    contractor validate the acceptability of the deliverable product.
    This would include having a contractor inspect the contractor\'s
    site preparation work prior to commencing the follow-on work.

(3) Contractor Support. RSSC will be obligated to support the Government
    during acceptance inspections. Types of support work include:

```{=html}
<!-- -->
```
(a) Permitting Government or other personnel to observe testing.

(b) Providing copies of test data to the FAA.

(c) Establishing a test set-up and assisting Government or other
    personnel in performing test and evaluation.

(d) Participating in a partial JAI, and/or final JAI.

\(4\) RSSC-Prepared Drawings. When drawings have been prepared for the
FAA as a result of a national or regional WR, the FAA signs in the
submitting and approving blocks. For example, the FAA project engineer
would sign in the \"Submitted By:\" block, and the appropriate FAA
Manager would sign in the \"Approved By:\" block. RSSC may place its
name or company logo onto drawings that it prepared; it may sign as the
preparer or drafter.

\(5\) FAA-Prepared Drawings Used by RSSC. FAA drawings may be given to
RSSC for procurement. RSSC will place the seal of a state-registered
professional engineer (PE) on those drawings, when required by law. As a
result, there may be charges made against the project for time required
to review those drawings. RSSC will notify the FAA whenever this
requirement exists. In addition, RSSC will inform the FAA when changes
are made to FAA-prepared drawings.

\(6\) Contract Submittal Under Regional WRs. When RSSC performs work
under this type of WR, such as a RE, a third party contractor submittal
should be processed as follows: The RE may evaluate the submittal and
make a recommendation to the FAA project engineer/manager. It is the
responsibility of the FAA engineer/manager to then accept or reject the
submittal, based in part on the information provided by the RSSC RE.
RSSC is not permitted to approve or reject submittal or drawings on
behalf of the Government.

## 4-14. WR CLOSE-OUT AND RECORDKEEPING. {#wr-close-out-and-recordkeeping. .unnumbered}

WR close-out includes the following:

a.  **WR Close-Out Requirements**. Close-out of a WR requires that the
    following conditions be met:

```{=html}
<!-- -->
```
(1) Work contained in the FWR as revised is physically complete
    including the compilation of information needed for capitalization
    purposes when required by the WR,

(2) Government verification via JAI or some other predetermined means is
    completed, indicating that all work required by the FWR has been
    accomplished satisfactorily, and

(3) The WR is fiscally complete and RSSC confirms that all charges
    against the WR have been recorded.

b\. **WR Close-Out Process**. The F&E project close-out is the same
whether the project is completed using TSSC resources or FAA in-house
resources. When a project is physically complete including appropriate
documentation and the work has been accepted by the FAA, the following
steps shall be taken to close out a WR formally:

(1) RSSC shall advise the CO/ACO in writing that all work on the subject
    WR has been completed. RSSC will also at this time initiate internal
    close-out procedures. No further costs will be incurred against the
    WR by RSSC after the notification is given to the CO/ACO;

(2) The TO/ATO will prepare a WR, revision \"X." The purpose of the
    \"X\" revision is to alert all concerned parties that the WR is in
    the close-out process. The Project Manager will verify that all work
    has been completed including final documentation exclusive of the
    close-out package.

(3) RSSC is obligated to submit the final invoice and associated
    documentation as soon as possible but not later than 120 days after
    receipt of the "X" revision from the Government. When the WR is
    fiscally complete, RSSC will prepare a separate final invoice for
    the WR being closed out. In addition to the supporting information
    to RSSC's invoices, RSSC will submit a recap sheet showing the
    amount invoiced and received on each of RSSC's invoices for which
    payment was requested and/or received on the WR being closed out.
    RSSC will submit a cumulative list of all property costing \$100.00
    or more, installed or delivered to the sites covered by an FWR. This
    will be delivered to the FAA within 120 calendar days from the time
    the letter is sent notifying the FAA the project completed.

(4) The TO/ATO, upon receipt of the WR close-out package (final invoice,
    invoice recap sheet, and property list) will prepare a close-out
    revision to the WR using the letter \"Z\" as the final element in
    the WR revision number.

(5) The TO/ATO will get concurrence from the PE, CO/ACO, and Business
    Manager/FCO, and formally issue the "Z" WR revision to RSSC. A
    signed original will be retained for the official record/files.

(6) The CO/ACO will process the final invoice through the appropriate
    accounts payable office. A copy of the paid invoice will be retained
    in the official WR close-out file.

(7) The ACO will verify that the contents of the closed-out regional WR
    file are complete and will retain the complete file for disposition.

c\. **Official Recordkeeping**. The compilation and custody of the
Government\'s record/file for each active WR is the responsibility of
the ACO for regionally issued WRs and the CO for national WRs.
Similarly, the compilation and custody of the Government\'s technical
record/file for each active WR is the responsibility of the ATO for
regionally issued WRs and the TO for national WRs. A WR is considered to
be active from the issuance of the final WR until the WR is canceled or
closed out. If a preliminary WR is not finalized and no active
communication is underway after six months, the PWR will be considered
inactive. The content of the official close-out files will be as
indicated in the following paragraph. Items will be added to the files
as work progresses and they become available.

d.  **Official WR Contract Close-Out File Content**. A copy of the
    TSSC-II Work Release File Index (Figure 4-6), should be placed in
    each official WR file. As applicable documents are prepared, they
    should be placed in the official WR file, and the file index should
    be notated accordingly. The WR file must include the following, as
    applicable:

```{=html}
<!-- -->
```
(1) EEP Data Sheet.

(2) IGCE.

(3) Pre-Work Release Meeting Notes.

(4) PWR (with original signatures) and SOW.

(5) Waivers to FAA Orders, Specifications, public design documents.

(6) WP.

(7) Q&Q.

(8) FWR/NTP (with original signatures).

(9) Revisions/WRCA's (with original signatures - separate by tabs).

(10) 75% notice.

(11) Justification of Award/Subcontract Notice.

(12) List of GFP/GFM (Form 4650.12), Contractor Receipt of GFP/GFM,
     Use/Disposition of GFP/GFM.

(13) Invoice Payment Sheets/Signed Certification Letters/Final Invoice

(14) Summary of Acquired Property Report

(15) TSSC Customer Satisfaction Survey - Project Engineer (Semi-Annual
     and Work Release Completion).

(16) CAI/JAI.

(17) Miscellaneous correspondence.

(18) A narrative statement indicating location of all reference
     documents, drawings, and specifications identified in the WR.

(19) WR Close-out Checklist.

```{=html}
<!-- -->
```
e.  **WR Contract Close-Out File Disposition**. Closed-out files for
    national WRs will be retained by the CO. In order to simplify any
    potential audits, regional WR files will be retained by the ACO
    until the end of the Contract. After the termination of the TSSC,
    specific instructions will be provided on how the files will be
    archived. Long-term file disposition will be the responsibility of
    the CO and will be accomplished in accordance with standard Contract
    file retention procedures.

## 4-15. F&E PROJECT CLOSE-OUT (widely called Capitalization).  {#fe-project-close-out-widely-called-capitalization. .unnumbered}

a.  Close-out of F&E projects accomplished by RSSC will occur through
    the same process as projects accomplished by F&E resources.

b.  The RPM/RPE initiating a WR will be responsible for providing
    allocation information necessary for breaking total cost into
    appropriate cost codes and object classes (materiel or labor).

c.  Site-specific information regarding costs for labor and costs for
    the project itself will appear on the backup sheets accompanying
    RSSC invoices.

d.  The invoice and inventory process is identified in the
    materiel/property management procedures in the Contract.

e.  Regionally funded materiel purchases reflected in the 32-9F report
    will not match those on the Regional Project Materiel Management
    System (RPMMS) Project Materiel Cumulative (PMC) report. Accounting
    may, however, make a one-time adjustment between \"Materiel\" and
    \"Other Costs\" for Fund Source (FS) 2 charges at close-out, prior
    to capitalization.

f.  To determine the amount of RSSC purchases included on the PMC
    prepared by RSSC, add the purchases deleted on the PMC and then
    subtract the sum from the FS 2 total on the PMC. Because all
    regionally funded items (including labor, travel, materiel, other
    costs, and overhead costs) are included in the same Work-in-Process
    Account in DAFIS, this is not required.

# CONTRACTOR RESPONSIBILITIES

## 5-1. SCOPE.  {#scope. .unnumbered}

This chapter describes the activities and the role of RSSC in providing
the necessary resources, personnel, and materiel to respond to the WRs
issued by the FAA to complete the assigned work related to specific
programs supporting the NAS.

a.  RSSC must provide management and administrative facilities to
    support the work at all locations as needed.

b.  RSSC must meet all state, local, and airport authority laws,
    requirements, and regulations applicable to the specific work,
    including, but not limited to, insurance coverage, labor union
    agreements, permits, building codes, alteration applications,
    vehicle usage, and construction safety standards.

c.  RSSC must perform all work described in the WR at all locations
    specified therein.

## 5-2. RSSC'S OVERALL MANAGEMENT RESPONSIBILITIES. {#rsscs-overall-management-responsibilities. .unnumbered}

a\. Immediately after Contract award, a National WR for Program
Management (NPM WR) was issued that describes RSSC\'s overall management
plans and responsibilities. Listed are the six management plans:

(1) Program Management

(2) Contract Administration

(3) Subcontracts Management

(4) Quality Assurance/Control

(5) Resource Management

(6) Staffing

b\. A formal organization was established to conduct the overall TSSC-II
administration, supervision, and quality and financial control required
to perform under the Contract. In accordance with the NPM WR, the plans
have been provided to the TSSC Program Office and the CO and will be
adhered to by RSSC.

## 5-3. TSSC PERSONNEL/STAFFING.   {#tssc-personnelstaffing. .unnumbered}

a\. In accordance with the NPM WR, RSSC has designated the following key
personnel.

(1) National Program Manager.

(2) National Contracts Manager.

(3) Regional Program Managers (RPMs) assigned to the regions.

b\. The TSSC-II organization including names, titles, and telephone
numbers of all national and regional key personnel is included in
Appendix 2 of this Handbook.

c\. RSSC will provide skilled personnel as required to successfully meet
FAA requirements. Personnel assigned by RSSC for the performance of WRs
will be acceptable to the FAA in terms of personal and professional
conduct. **Should any person in RSSC\'s organization be deemed by the
TO/ATO or CO/ACO to conflict with the best interests of the FAA, that
person will be removed from the assignment**. Prior to initiating any
action that would result in the removal of a RSSC employee, coordination
with the CO is required. Such removal shall be in written form, issued
by the CO/ACO.

## 5-4. TSSC OFFICE LOCATIONS. {#tssc-office-locations. .unnumbered}

RSSC has established a national office at 600 Maryland Avenue, SW, Suite
895, Washington, DC, 20024. Regional offices have also been established
with responsibilities corresponding to FAA regional boundaries. TSSC
office locations and corresponding areas of responsibility are listed in
Appendix *2* of this handbook.

## 5-5. QUALITY CONTROL. {#quality-control. .unnumbered}

a.  RSSC has provided and will maintain a Quality Assurance/Control
    (QA/C) Plan to coordinate and monitor all inspection/test
    activities, to comply with the necessary QC policies and procedures,
    and to assure that all activities are performed in accordance with
    TSSC-II requirements. This QA/C Plan is primarily for RSSC's
    management; however, individual reports are available from RSSC.
    Copies of the TSSC-II QA/C Plan are available at each FAA Regional
    Office.

b.  The quality of the delivered product as initiated through a WR is an
    FAA responsibility. The PWR, prepared by FAA, addresses acceptance
    inspections and how FAA will determine if the delivered product is
    acceptable. The WR Plan prepared by RSSC should contain a section
    that addresses acceptance criteria. FAA has the responsibility to
    reject or accept the delivered product through JAI/CAIs.

## 5-6. STANDARDS OF CONDUCT. {#standards-of-conduct. .unnumbered}

RSSC employees performing work under the TSSC-II are required to comply
with the same standards of conduct applicable to Federal employees. All
persons employed by RSSC, and any subcontractor employed by RSSC, which
are assigned to perform the Contract work, shall be under the control of
RSSC at all times. In addition, they must comply with the following:

a.  RSSC shall provide personnel who are physically and emotionally
    competent to perform the work required by this Contract.

b.  RSSC shall be responsible for maintaining satisfactory standards of
    employee competency, conduct, appearance, and integrity.

c.  RSSC shall be responsible for taking such disciplinary actions with
    respect to its employees as may be necessary. The CO may, in
    accordance with TAR 1252.237-71, require those employees whom he/she
    deems incompetent, insubordinate, unsuitable, or otherwise
    objectionable, be dismissed from work.

d.  RSSC may not use any Government furnished materiel, services, or
    equipment for any purpose not related to TSSC-II.

e.  RSSC personnel may only conduct business covered by the Contract
    during periods paid for by the FAA and may not conduct any other
    business on Government premises.

f.  RSSC personnel are required to refrain from discussing any
    information obtained in the performance of work under TSSC-II with
    unauthorized persons.

## 5-7. SECURITY REQUIREMENTS.  {#security-requirements. .unnumbered}

RSSC is required to comply with all Department of Transportation (DOT)
and FAA orders, directives, and supplements relating to security. They
shall safeguard all classified material and shall provide and maintain a
system of security controls within its organization in accordance with
the requirements of the Contract.

a.  **Personnel Suitability Requirements.**

A suitability investigation is required for all RSSC employees
performing work under this Contract and will consist of either a
National Agency Check (NAC) or a National Agency Check and Inquiries
(NACI). If as a result of this investigation, or any other matter
brought to the attention of the Government, it is determined that
RSSC\'s employee is not suitable to perform work under the TSSC-II, RSSC
shall be advised in writing by the CO that access to FAA facilities
shall be denied or withdrawn for that RSSC employee, and that RSSC shall
not use, or shall promptly cease using, such employee for work under
this Contract. Waivers or exceptions to these requirements may be
approved only by the CO after coordination with the FAA Headquarters'
Investigations Division, ACO-300.

b\. **Investigation Requirements.**

Prior to the first visit by a RSSC employee to a FAA facility, and for
each new employee hired, RSSC is required to provide the forms listed
below to the FAA Investigations Division, ACO-300. Copies of these forms
and the cover letters provided by RSSC will be delivered to the CO.

(a) Questionnaire for Public Trust Positions, Standard Form Number 85P
    (SF-85P), December 1990 (original).

(b) Application for Federal Employment, Standard Form 171 (SF 171),
    Revised 6/88, (copy). Only the following questions need to be
    answered: 2-6, 19, 28, 36, 38-45, and 48-49.

(c) Applicant Fingerprint Card, Federal Document Number 258 (FD-258)
    (original).

\(2\) RSSC may provide one of the following as evidence of previous
investigations in lieu of the documentation requirements above:

(a) A security clearance presently in effect that has been issued by the
    Federal Government, or;

(b) A previously issued security clearance, which was administratively
    terminated without prejudice, less than 12 months ago, or;

(c) A previously issued NACI or higher-level investigation that was
    conducted for Federal employment that ended less than 12 months ago.

\(3\) At its sole discretion, the Federal Government may require a
current NACI regardless of previous investigations or clearances.

c\. **Suitability Clearance Process.**

The Investigations Division, ACO-300, will make arrangements to procure
the required security investigations and will provide monthly listings
of TSSC-II personnel who currently possess suitability clearance to the
TO and to each of the Regional Investigations and Internal Security
Branches of the Regional Civil Aviation Security Divisions (700's). The
700 Branch will provide copies to the ATOs. ATOs are responsible for
distribution of the listing to AF branches, SMOs and air traffic
divisions in accordance with regional procedures and requirements..

d\. **Airport Security Requirements.**

RSSC shall determine and comply with the specific security requirements
at each airport where TSSC-II work is to be performed. Advance
coordination with airport security is required. RSSC shall be required
to furnish a trained escort as appropriate.

e\. **Facility Security Requirements.**

RSSC shall provide such physical security at the facility where the
contract services are provided as is necessary to preclude unauthorized
intrusions and loss of or damage to Government property. The CO will
notify RSSC in writing to promptly correct any aspects of physical
security not in compliance with the Contract.

f\. **Department Of Defense Industrial Security Program.**

(1) In performing under certain WRs, it may be necessary for the
    Government to provide RSSC access to classified information or
    facilities in which case an industrial personnel security clearance
    will be required. When access to classified information or
    facilities is required, RSSC shall comply with the policies and
    procedures of the Department of Defense Industrial Security Program
    (DODISP).

(2) The Director, Defense Industrial Security Clearance Office, Defense
    Investigative Service (DIS), Columbus, Ohio 43216, is responsible
    for processing and granting all industrial personnel security
    clearances required by the Contract. The granting of personnel
    security clearances will be governed by the policies and procedures
    established by, and in accordance with, Department of Defense
    Directive 5220.22.

(3) The following forms, or any other forms as may be prescribed for use
    in the DODISP, can be obtained from the cognizant DIS Security
    Office:

```{=html}
<!-- -->
```
(a) Applicant Fingerprint Card, Federal Document Number 258, FD-258.

(b) Department of Defense (DOD), Contract Security Classification
    Specification, DD Form 254.

(c) Department of Defense (DOD), Security Agreement, DD Form 441.

g\. **Employee Termination.**

(1) **RSSC Personnel**. RSSC will be responsible for returning, or
    ensuring that the employee returns, all DOT-issued RSSC/employee
    identifications and all other DOT property.

(2) **Government Personnel**. If Government personnel obtain an
    identification card from RSSC, the card should be returned upon
    completion of an assignment or departure from the FAA, whichever
    comes first.

## 5-8. TSSC EMPLOYEE IDENTIFICATION. {#tssc-employee-identification. .unnumbered}

Employees performing work on TSSC are **required to wear identification
badges** provided by the Government, while working at or on a FAA
facility, identifying them as DOT RSSC employees.

## 5-9. SAFETY. {#safety. .unnumbered}

RSSC is required to maintain an active occupational safety program and
is required to conform to all applicable Occupational Safety and Health
Administration (OSHA) requirements, as well as FAA occupational safety
programs and requirements as set forth in the Master List of Applicable
Documents contained in the Contract. OSHA safety training is to be paid
for RSSC employees by an FWR.

## 5-10. PROGRAM STATUS REVIEW (PSR) MEETINGS. {#program-status-review-psr-meetings. .unnumbered}

a\. RSSC National and Regional Program Manager(s) will participate with
the FAA in monthly PSR meetings that will address activities of the
previous calendar month. These meetings will be co-chaired by FAA and
RSSC national/regional counterparts and may be held at either FAA or
RSSC\'s facilities. The meeting agenda will be prepared by RSSC, with
FAA input, and include appropriate supporting data.

b\. RSSC will prepare national and regional monthly PSR reports in
accordance with instructions contained in the Contract. The national and
regional reports will contain, but not be limited to, an executive
summary and a financial summary for all work covered by the report and a
separate section for each applicable WR containing:

(1) Status of work: schedules, problems.

(2) Financial status of individual WRs in accordance with the Contract.

(3) Near-term work schedules.

(4) Special interest items.

(5) Variance reports.

c\. In addition:

(1) The national report will include the details of each active National
    WR, the status of each regional WR, and the overall status of each
    regional TSSC effort.

(2) Each regional PSR report will address the detailed status of active
    regional WRs and that portion of each national WR occurring within
    the region. One copy of each regional report will be forwarded by
    the ATO to the TO, CO, and ACO upon receipt.

(3) RSSC will be responsible for preparing all audio/visual materials,
    graphic aids, and formal handouts. RSSC will prepare minutes of PSR
    meetings for approval by the TO/CO/ATO/ACO not later than 5 working
    days following the meeting. After approval, copies will be
    distributed.

## 5-11. WRITTEN ALERTS.  {#written-alerts. .unnumbered}

In addition to the periodic status reports described above, at any point
in the performance of this Contract, RSSC shall provide written alert
reports to the CO/TO or ACO/ATO, as appropriate, **immediately** when it
becomes apparent that schedule or cost deviations will occur or are
likely to occur in any WR. The alert report shall provide details on the
circumstances of the situation leading to the alert, potential impact on
cost and schedule if corrective measures are not taken, possible
alternatives to avoid cost and schedule impact including pros and cons
and a recommendation as to the most desirable course of action.

# SPECIAL REQUIREMENTS/SERVICES

## 6-1. RECRUITMENT AND ORGANIZATIONAL ACTIVITIES. {#recruitment-and-organizational-activities. .unnumbered}

The Ethics in Government Act and Standards of Conduct for Government
Employees set restrictions on Government personnel/former Government
personnel and their ability to be hired in the private sector. In
addition to those restrictions, RSSC shall not recruit for positions
within its organization (or subcontractors at any tier) FAA personnel on
Government property for work under this Contract.

## 6-2. ORGANIZATIONAL CONFLICTS OF INTEREST. {#organizational-conflicts-of-interest. .unnumbered}

a\. A potential, significant conflict of interest exists when the nature
of the work to be performed under the Contract may, or when past
contractual activities may, on future activities, result in a unfair
competitive advantage to RSSC, or impair RSSC's objectivity in
performing TSSC-II work.

(1) **Unfair Competitive Advantage**. An unfair competitive advantage
    may arise from a company having access to procurement information
    prior to competitors or by having access to information related to
    the FAA\'s deliberative acquisition process, or information that is
    proprietary, or otherwise privileged.

(2) **Impaired Objectivity**. An impaired ability to objectively perform
    TSSC-II work may arise from a company\'s ability under the Contract
    to evaluate its own work or to favor its own products or
    capabilities.

(3) **Business Relationships**. A conflict may also arise from a
    company\'s significant commercial business relationships with
    organizations whose work or capabilities it might be asked to
    evaluate under this Contract. For the purposes of this provision,
    significant business relationships are defined as one of the
    following:

```{=html}
<!-- -->
```
(a) Those relationships involving joint ventures, mergers, acquisitions
    of RSSC or subcontractors.

(b) When a substantial amount of RSSC's or any of RSSC's
    subcontractors\' gross revenues are derived from business with one
    of the companies listed in the Contract.

(c) When a company\'s viability may be affected by its relationship with
    an organization whose work or capabilities it might be asked to
    evaluate under this Contract.

b\. In the event that a WR is issued to RSSC that would require activity
that would create a potential conflict of interest, RSSC shall notify
the CO of the potential conflict. RSSC shall not commence work on a WR
related to a potential conflict of interest until specifically notified
by the CO to proceed. Despite a conflict of interest, a request for
waiver shall be submitted by the CO if he/she determines that it is in
the best interest of the Government to issue a WR.

## 6-3. SUBCONTRACTING REQUIREMENTS.  {#subcontracting-requirements. .unnumbered}

a.  A portion of the work to be completed under the TSSC-II will be of a
    construction nature and, of this portion, a great deal will be
    relatively small in scope. This type of work lends itself to
    accomplishment by small, local contracting firms.

b.  The TSSC-II requires that such construction work be subcontracted by
    RSSC on a competitive firm‑fixed‑price basis, although RSSC may,
    with CO approval, perform minor construction work with its own
    employees when it is cost effective to do so, and when the cost of
    such work does not exceed \$25,000 per individual project.

c.  Formal consent to subcontracts awarded by RSSC will be the
    responsibility of the CO/ACO, who will also be responsible for
    enforcing the minimum wage determinations required by the
    Davis‑Bacon Act.

d.  Wage interviews will be conducted by the CO/ACO with a sampling of
    RSSC and subcontractor employees subject to Davis‑Bacon minimum wage
    rates. At the discretion of the CO/ACO, sample sizes may be adjusted
    upward/downward depending on the sample results.

e.  FAA employees should exercise caution to avoid potential conflicts
    of interest when responding to requests for recommendations or
    assistance from RSSC personnel in locating or identifying sources of
    services or supplies.

## 6-4. SUBCONTRACTORS/CONSULTANTS/INTERDIVISIONAL TRANSFERS. {#subcontractorsconsultantsinterdivisional-transfers. .unnumbered}

a\. Before employment of any subcontractor/consultant or interdivisional
transfer under the Contract, RSSC shall obtain the consent of the
CO/ACO. The advanced notification to subcontract shall be submitted, [in
writing]{.underline}, to the CO/ACO to obtain consent. In requesting
such agreements, RSSC shall furnish all pertinent information required
by the CO/ACO, which may include, but not be limited to the following:

(1) Identification of the proposed subcontractor/consultant or
    interdivisional transfer and an explanation of why and how the
    proposed subcontractor/ consultant or interdivisional transfer was
    selected, including the competition obtained.

(2) A description of the supplies or services to be obtained.

(3) Identification of the type of subcontract/consultant or
    interdivisional transfer agreement to be used.

(4) The proposed subcontract/consultant or interdivisional transfer
    price and RSSC's cost or price analysis.

(5) The subcontractor's current, complete, and accurate cost or pricing
    data and a Certificate of Current Cost or Pricing Data, if required.

(6) The unexecuted subcontract/consultant or interdivisional transfer
    document.

(7) Identification of any potential conflicts of interest.

(8) The rate of reimbursement.

(9) Other information as requested by the CO/ACO.

b\. The CO/ACO's consent to subcontract does not constitute a
determination of the acceptability of the subcontract terms or price, or
the allowability of costs.

## 6-5. SUBCONTRACTING GOALS FOR SMALL BUSINESSES (SB), SMALL DISADVANTAGED BUSINESSES (SDB), AND WOMEN-OWNED BUSINESSES (WOB). {#subcontracting-goals-for-small-businesses-sb-small-disadvantaged-businesses-sdb-and-women-owned-businesses-wob. .unnumbered}

The following FAA minimum subcontracting goals for this Contract are
expressed below as percentages of total planned subcontracting efforts.
These goals shall be allocable over the full life of the Contract,
including the base period of performance and each option period, if
exercised. RSSC shall achieve the following minimum goals for SB, SDB,
and WOB participation within this Contract:

a.  **SB Concerns**. Overall goal, 45 percent of total planned
    subcontracting effort.

b.  **SDB Concerns**. Ten percent of the overall SB goal of 45 percent
    of total planned subcontracting effort.

c.  **WOB Concerns**. Four percent of the overall SB goal of 45 percent
    of total planned subcontracting effort.

## 6-6. BONDING AND INSURANCE. {#bonding-and-insurance. .unnumbered}

RSSC shall obtain performance and payment bonds, as required by the
Miller Act, to cover all Davis-Bacon Act Work performed under the
Contract.

**a. Bonding Requirements**. Specific Bonding Requirement Determined per
Work Site. Additionally, prior to the commencement of work, RSSC shall
satisfy the specific bonding requirements determined by particular work
sites identified in WRs issued under this Contract. RSSC will provide
the specific bonds to the extent required by each airport authority
where TSSC-II work is being performed. The amount of bonding required
may vary significantly among different airports.

**b. Insurance Requirements**. Insurance Requirement and Approval. RSSC
may not commence work at any airport until RSSC has obtained all
insurance required at that airport and such insurance has been verified
by the CO/ACO, nor may RSSC allow any subcontractor to commence work on
a subcontract at any airport until all insurance required of the
subcontractor has been so obtained and approved by the CO/ACO. Should
RSSC find it impossible to obtain coverage adequate to meet the
insurance requirements established for any airport or other work site,
the CO/ACO will be advised.

(1) General Liability Requirements. RSSC is required to maintain bodily
    injury liability and property damage liability insurance in its own
    name as protection against damages to persons or property, including
    injury or death, that may result from its performance of TSSC-II
    work. The coverage of each such policy will not be less than the
    amounts stated in the Contract.

(2) Specific Insurance Requirement Determined per Work Site. To the
    extent not covered by the above required insurance, RSSC is required
    to provide the specific insurance to the extent required by each
    airport or other authority where TSSC-II work is to be performed.
    The amount of insurance required may vary significantly among
    different airports.

# INVOICE PAYMENTS

## 7-1. INVOICE PREPARATION, BILLING CYCLE, AND SUBMISSION. {#invoice-preparation-billing-cycle-and-submission. .unnumbered}

a.  RSSC is required to submit a single, consolidated monthly invoice
    for national WRs, including the program management WR, to the FAA
    Accounts Payable Office (original and two copies in all cases) and
    two working copies to the TO and CO, one paper copy and one on disk.

b.  A single consolidated monthly invoice is required to be submitted
    for regional WRs (original and two copies in all cases) and two
    working copies to the ATO, one paper copy and one on disk. The
    original regional invoice will be submitted to the regional Accounts
    Payable Office.

c.  It is the responsibility of the Accounts Payable Office to time
    stamp the invoice for prompt payment tracking. Each invoice is
    required to consist of the following four documents:

```{=html}
<!-- -->
```
(1) SF‑1034 indicating total for all costs, fees, and fee credit hours
    for the current billing period and containing the Contractor\'s
    certification as to the accuracy, completeness, and currency of
    charges.

(2) A summary of current and cumulative cost, fee, and fee credit hour
    totals for each individual WR included in the total shown on the
    SF‑1034.

(3) A detailed cost and fee breakout for each WR listed on the summary.

(4) A detailed listing by WR/site, of the following: All materiel (more
    than \$100 in value) purchased for each WR; and breakout of labor
    and travel costs shown separately from the other project
    expenditures.

## 7-2. INVOICE CERTIFICATION AND PAYMENT. {#invoice-certification-and-payment. .unnumbered}

a.  RSSC submits an invoice on hard-copy and disk to the TO/ATO. The
    disk is imported into the Unitrack System. Unitrack generates an
    Invoice Coding Sheet and an Invoice Certification Letter (see
    Figures 7-1 and 7-2, Invoice Coding Sheet and Invoice Certification
    Letter, respectively). Refer to the Unitrack system Users Guide for
    detail information on creating, editing, and viewing the Invoice
    Coding Sheet and Invoice Certification Letter. The Invoice
    Certification Letter is printed out and distributed to the regional
    project engineer/project manager (person responsible for the WR) for
    verification that the charges are reasonable. See Figure 7-3,
    Invoice Module Authorization, for authorized users of the invoice
    process.

b.  The TO/ATO reviews the Invoice Certification Letter and invoice for
    agreement between the two. If the documents are in agreement and the
    TO/ATO concurs, the TO/ATO will go into the Unitrack System and
    approve the Invoice Coding Sheet that was generated upon receipt of
    the invoice.

c.  The Invoice Coding Sheet will then go forward electronically to the
    TSSC business manager/FCO, then to the CO/ACO for further review and
    concurrence. The business manager/FCO ensures that funds are
    available and that the correct appropriation codes are listed. A
    hard copy of the Invoice Coding Sheet will be printed, then signed
    by the TO/ATO and CO/ACO. The CO/ACO certifies the payment of
    invoices; then the invoice is forwarded to the Accounts Payable
    Office.

d.  In the event of nonconcurrence, the TO/ATO will recommend partial or
    nonpayment of the invoice prior to forwarding it to the CO/ACO. A
    brief statement will be forwarded by the CO/ACO with the voucher to
    the Accounts Payable Office stating the reason for suspension of
    nonpayment. Written notification must also be sent to RSSC by the
    CO/ACO. The CO/ACO will act promptly to resolve issues involving
    partial or nonpayment.

e.  Payment will be made by the applicable Accounts Payable Office in
    accordance with the Prompt Payment Act, 30 days from FAA's receipt
    of the invoice from RSSC. Copies of paid invoices will be forwarded
    to the CO/ACO and the TSSC National Program Manager.

f.  The accounting office will record the payments in the accounting
    records, liquidating the established obligations, and recording the
    expenditures against the proper appropriations, project, and job
    order numbers cited on the WR.

**TSSC II Invoice Coding Sheet**

02-Aug-96

Invoice #: 0002 Invoice Date: 5/14/96 Date From: 3/23/96 Date To:
4/19/96

  ---------- ------- --------- ------------ ---------- --------- -------- -------- ------ --------- ---------------- -----------------
  **WR \#**  **Loc   **JON**   **Suffix**   **Appr**   **Lim**   **C      **Prg    **Ob   **Short   **Inv Amt**      **Amt Pd**
             ID**                                                Cntr**   Elem**   Cl**   Pd**                       

  **0005**   HNL     30717     95-125       582A       0         8052     2C02A0   3202             \$11,309.38      \$11,309.38

             OAK     30727     95-126       582A       0         8052     2C02A0   3202             \$0              \$0

             RIU     30747     95-128       582A       0         8052     2C02A0   3202             \$0              \$0

             RNO     30757     95-129       582A       0         8052     2C02A0   3202             \$0              \$0

                                                                                                    **\$11309.38**   **\$11,309.38**

                                                                                                                     

  **0010**   PHX     42864     96-146       682A       0         8053     2B24A0   3202             \$789.20         \$789.20

                                                                                                    **\$789.20**     **\$789.20**
  ---------- ------- --------- ------------ ---------- --------- -------- -------- ------ --------- ---------------- -----------------

**Figure 7-1. Invoice Coding Sheet**

TSSC II Invoice Review Letter

**Today's Date:**

**Attention:**

**Regarding TSSC II Invoice For Work Release Number:**

**TSSC II Invoice Number:**

**For Performance Dates: From to**

**Date Invoice Received From Raytheon:**

**Work Release Invoice Amount:**

Based upon TSSC Program Office Records, the appropriations shown below
have unexpended obligations sufficient for payments as indicated. Unless
otherwise directed, the full amount of the invoice will be paid from the
appropriations shown below. The value shown under "Remaining WR Alloc."
represents the funds allocated to this WR, that will remain AFTER this
invoice is paid.

**WR# Loc ID JON Suffix Invoice Amount Remaining WR Alloc. Amount
With-held Amount Paid**

**0006** VAR 71959 97-833 \$36,517.53 \$0.00 \$0.00 \$36,517.53

**\$36,517.53 \$0.00 \$36,517.53**

Please review this billing and return one (1) signed copy of this sheet
to Linda Rainone, ANI-223. The other copy is provided for your file.

I acknowledge that the work on this work release is proceeding
satisfactorily from a technical standpoint and the labor hours and labor
categories are reasonable. Other direct costs appear reasonable in
accordance with the terms of the subject Work Release.

(Name)

(Date)

**Figure 7-2. Invoice Review Letter**

+--------------+----------+--------+--------+-------+--------+--------+
| **User       |          |        |        |       |        |        |
| Group**      |          |        |        |       |        |        |
+--------------+----------+--------+--------+-------+--------+--------+
|              | *        | *      | *      | **    | **     | **     |
|              | *ADMIN** | *ACO** | *ATO** | FCO** | ENG/** | GUEST/ |
|              |          |        |        |       |        | OTHE   |
|              |          |        |        |       |        | RS\*** |
+--------------+----------+--------+--------+-------+--------+--------+
| **INVOICE**  |          |        |        |       |        |        |
+--------------+----------+--------+--------+-------+--------+--------+
| -   Download | ---      | Yes    | Yes    | Yes   | Yes    | \*     |
+--------------+----------+--------+--------+-------+--------+--------+
| -   View     | ---      | Yes    | Yes    | Yes   | Yes    | \*     |
|     Invoice  |          |        |        |       |        |        |
+--------------+----------+--------+--------+-------+--------+--------+
| -   Edit     | ---      | Yes    | Yes    | Yes   | Yes    | \*     |
|     Invoice  |          |        |        |       |        |        |
+--------------+----------+--------+--------+-------+--------+--------+
| -   Delete   | ---      | Yes    | Yes    | Yes   | Yes    | \*     |
|     Invoice  |          |        |        |       |        |        |
+--------------+----------+--------+--------+-------+--------+--------+

Figure 7-3. Invoice Module Authorization

\* Guests/Others can view only on any/all actions.

![](media/image7.wmf){width="6.480555555555555in"
height="7.479861111111111in"}

Figure 7-4. Invoices - Work Flow Chart

# TSSC FIELD INTERFACES

## 8-1. GENERAL. {#general.-3 .unnumbered}

In accomplishing contractual functions, RSSC personnel will interface
with numerous FAA field facilities and personnel. It is the FAA\'s
intention that RSSC personnel, in the performance of duties under the
TSSC-II, function and be treated in a manner similar to agency F&E
personnel doing similar work. Constraints, privileges, and
responsibilities required of and afforded to F&E engineers and
technicians will be required of and afforded to RSSC engineers and
technicians.

## 8-2. COORDINATION WITH THE AF ORGANIZATION.  {#coordination-with-the-af-organization. .unnumbered}

In the course of performing under the Contract, RSSC will be in contact
with and deal with various segments of the FAA. However, due to the
nature of the work performed, RSSC personnel will be in closer and more
frequent contact with the Airway Facilities organization than with any
other FAA element.

a\. **Regional Office Support and Conditions.**

(1) Within each FAA region, the ATO is the principal point of contact
    between the FAA and RSSC. The ATO, with the assistance of the FAA
    RPM, issues WRs, evaluates Work Plans, and certifies work
    accomplishment and RSSC's billings.

(2) The ATO and RPM act jointly as the liaison between RSSC and FAA
    field personnel; they coordinate dates, accommodations, and
    attendance at meetings. They also schedule work starts, JAIs, and
    flight inspections.

(3) The regions will provide RSSC with access to all available technical
    and administrative documentation relevant to a particular WR
    request, including:

```{=html}
<!-- -->
```
(a) Standards.

(b) Specifications.

(c) Standard and site specific drawings.

(d) Layout plans.

(e) Airport, airport vicinity, and plot diagrams.

(f) Access to all known information relative to specific airport safety
    and security regulations.

(g) Other concurrent airport construction work.

(h) Any union/labor management agreements in effect that may impact
    TSSC-II operations.

```{=html}
<!-- -->
```
b.  **Regional F&E Interfacing.**

```{=html}
<!-- -->
```
(1) The ATO will be the principal focal point for interfacing between
    RSSC and the regional F&E organization.

(2) Once a WR has been issued, it is expected that RSSC\'s engineers
    will talk directly with the FAA engineers without involvement of the
    ATO, ACO, or FCO, unless a problem exists.

(3) Except for the initial national WRs issued as part of the Contract,
    the Contract contains only broad guidelines as to work to be
    performed or coordination required in regard to other WRs.

(4) Detailed specifics of work to be accomplished and necessary
    coordination should be described in the individual WR. However, this
    work must be within the scope of the Contract.

```{=html}
<!-- -->
```
c.  **National WRs.**

    The region may become involved in review of drawings and CSERs. The
    appropriate headquarters program manager will be the focal point for
    action and coordination for these WR reviews. Typically, regional
    involvement in national WR projects will be minimal and consist of
    providing:

```{=html}
<!-- -->
```
(1) Whatever site‑specific background information, drawings,
    specifications and standards are available and pertinent to the work
    to be accomplished.

(2) Order and follow‑up of delivery of Government Furnished Equipment.

(3) Review and approval of the contractor site engineering reports
    (CSER).

(4) Inspection and certification of work completion.

```{=html}
<!-- -->
```
d.  **Regional WRs.**

```{=html}
<!-- -->
```
(1) WRs for these projects will be prepared by the regional F&E
    organization.

(2) The interface required between RSSC and AF establishment engineering
    personnel will be a function of the work described in the WR. RSSC
    may be working nearly independent of, or side-by-side with, F&E work
    forces. Interface requirements need to be tailored to suit the
    specific activity of the WR.

## 8-3. SYSTEM MANAGEMENT OFFICES (SMO) AND OR SMO MANAGEMENT FIELD OFFICE INTERFACE. {#system-management-offices-smo-and-or-smo-management-field-office-interface. .unnumbered}

a\. AF SMO personnel will be ultimately involved in nearly every phase
of TSSC-II functioning. SMO and/or SMO/System Support Center (SSC)
representatives may participate in:

(1) Site selection surveys.

(2) Site engineering surveys.

(3) Engineering.

(4) Preconstruction and construction meetings.;

(5) Construction and installation work.

(6) The follow-on acceptance inspections and exception clearance
    efforts.

b\. Other TSSC-II functions that SMO and/or SMO/SSC representatives may
participate in are:

(1) Some regional AF divisions have in place a set of specific
    coordination procedures that define the official interface that must
    take place between the F&E and AF maintenance organizations.

(2) Where they exist in written form, RSSC will be provided copies of
    these procedures.

(3) Whether or not printed regional procedures are available, local AF
    and RSSC personnel should discuss such items as access, housekeeping
    details, site-specific precautions to be observed, and required
    coordination.

(4) These coordination requirements should be delineated in the PWR and
    be included in the WR Plan.

(5) Any specific coordination procedures issued by a region to describe
    the interface between AF establishment engineering and field
    facilities will apply equally to RSSC.

(6) RSSC will be responsible for carrying out all required coordination
    activities whether specific to a WR, site-specific, or regional
    standard.

(7) SMO personnel, on the other hand, are requested to recognize RSSC
    personnel as though they were F&E engineers. SMO personnel should
    cooperate fully in matters regarding the Contract and should support
    and assist RSSC to the extent that they would support and assist an
    in-house F&E work force.

(8) Complete SMO Customer Satisfaction Survey at the conclusion of TSSC
    work at a site, or group of sites under one WR. These forms will be
    used by the ATO and RSSC to incorporate regional improvements and
    will also be forwarded to Washington for national TSSC information
    and improvements.

## 8-4. FACILITY RESPONSIBILITY. {#facility-responsibility. .unnumbered}

Generally, the practices currently employed by each region and SMO with
regard to transfer of site responsibility will be employed whether RSSC
or AF establishment engineering is involved in the transfer. The AF
maintenance organization cannot transfer responsibility for an
operating, commissioned facility to RSSC or F&E personnel. However,
physical responsibility may be transferred for a decommissioned facility
or a temporarily nonoperational facility; i.e., a facility advertised in
the Airman\'s Information Manual (AIM) as being out of service for an
extended, but finite, period of time. **In any case, overall
responsibility for a facility must remain with the SMO.**

a.  **Commissioned Operational Facility.**

    \(1\) The possible interregional affect of shutdowns or outages on
    equipment such as navigational aids and communication facilities
    must be considered when a WR is being developed**.** Commissioned
    FAA facilities are the responsibility of the AF SMO Manager and this
    action notice does not alter the SMO Manager's responsibility or
    right to manage the facility in accordance with agency policy. The
    SMO Manager or designee will be responsible for:

```{=html}
<!-- -->
```
(a) Issuing any required Notices to Airmen (NOTAM) to permit essential
    short duration shutdowns, including accomplishing the necessary
    coordination with the Air Traffic organization.

(b) Any required recertification of the facility upon completion of
    RSSC\'s work.

(c) To whatever extent the SMO manager or designee deems appropriate,
    for observing RSSC during the course of the work.

\(2\) TSSC work must be coordinated closely with the SMO Manager or
his/her designee when it could interrupt or cause interference to a
commissioned, operating facility. This interference could occur if the
TSSC work is to be performed at the facility or in the following
situations outside the confines of such a facility:

(a) At a facility or equipment interconnected to, or operationally
    associated with, the commissioned, operating facility.

(b) In such close proximity to a commissioned, operating facility that
    the potential exists for interference.

\(3\) In the event of an emergency situation; e.g., the unanticipated
outage or an inordinate extension of scheduled outage or the unexpected
arrival of inclement weather:

(a) The FAA facility manager or SMO manager may temporarily stop any
    RSSC work that may affect the operational status of a commissioned,
    operational facility.

(b) The SMO manager will take whatever measures are required to restore
    the facility to operation.

(c) The ATO/ACO should be notified as soon as possible by RSSC.

```{=html}
<!-- -->
```
b.  **Commissioned Nonoperational Facilities.**

```{=html}
<!-- -->
```
(1) In some instances, WRs will call for RSSC to perform work on
    facilities that, while still commissioned, will be shut down for the
    minimum period of time essential to accomplish that work that cannot
    be accomplished with the facility operational. These periods of
    facility shutdown may vary from a matter of hours to months, and
    whenever feasible, will be advertised in advance by the National
    Flight Data Center (NFDC) in the Airman's Information Manual (AIM).
    The WR will identify individuals responsible for providing the
    advance notification to NFDC.

(2) The facility removed from service including the structure, grounds,
    plants and electronic equipment, tools, test equipment, and spare
    parts remains the responsibility of the SMO Manager. Based on a
    number of factors, including the anticipated duration of the
    shutdown period and the physical and electrical separation from
    other operating equipment, the region may authorize the SMO Manager
    to temporarily transfer physical control of the facility to RSSC.
    This action may free the SMO Manager from the day‑to‑day concern
    over the physical security of the site and equipment and allow RSSC
    access to the facility.

(3) Such transfer will only be effected in writing, when signed by the
    SMO manager and a representative of RSSC who has been authorized by
    the TSSC Regional Project Manager to accept temporary physical
    control.

(4) A copy of the transfer document will be sent to the ATO/ACO.
    Attached to the document will be a jointly accomplished and signed
    facility inventory; a set of facility meter readings; and ground
    check readings attesting to facility performance at the time of
    shutdown and transfer of responsibility.

(5) At the conclusion of TSSC work, the same procedures will apply when
    RSSC's responsibility for the facility is to be terminated and
    transferred back to the SMO, including remeasurement of facility
    performance parameters previously recorded.

```{=html}
<!-- -->
```
c.  **Decommissioned Facilities.**

```{=html}
<!-- -->
```
(1) Typically, TSSC work to be accomplished at a decommissioned facility
    may involve the removal and disposal of decommissioned equipment
    and, possibly, installation or reinstallation of new or replacement
    equipment.

(2) Temporary facility responsibility may be transferred to RSSC using
    the procedures described in the above paragraph.

(3) If appropriate, responsibility will be transferred back to the SMO
    manager upon completion of the work effort described in the WR.

(4) Where disposal of FAA equipment by RSSC is required by a WR, such
    disposal will be accomplished in accordance with FAA disposal
    requirements.

```{=html}
<!-- -->
```
d.  **Facility Access  Security.**

```{=html}
<!-- -->
```
(1) Access to all facilities within an SMO is typically controlled by
    the SMO manager through a locking system that provides the
    capability for enabling site access only to individuals having a
    need to access each particular site. It is the SMO manager's
    responsibility to provide RSSC personnel necessary access to
    facilities. It is also the SMO manager's prerogative to determine if
    RSSC access will be unrestricted; e.g., by issuing keys or divulging
    combination codes to RSSC employees, or restricted; e.g., by
    escorting employees.

    **(NOTE: TSSC-II personnel will follow all published security
    guidelines and/or regulations provided by local management at any
    region/SMO/ facility.)**

```{=html}
<!-- -->
```
(2) In the event that keys (or combination codes) are issued, RSSC
    personnel will sign and be accountable for their security. **Keys
    will not be copied, nor will they be loaned or transferred to
    anyone**. They will be returned to the issuer immediately upon
    completion of the project or if the individual possessing the key
    will be absent for a period exceeding two weeks.

(3) Loss of any key will be reported to the issuer immediately and RSSC
    will be required to reimburse the Government for any facility losses
    as well as the recore and/or rekey costs resulting from the loss of
    the key. The SMO manager will advise the ATO of the cost and
    consequences of any such loss.

## 8-5. NOTICE TO AIRMAN (NOTAM) ISSUANCES. {#notice-to-airman-notam-issuances. .unnumbered}

a\. At times, during the course of facility construction or
installation, it may be necessary that a NOTAM be issued prior to
accomplishing certain work. A NOTAM may be issued to cover temporary
aberrations or interruptions of up to several hours without advance
notification to the public in the AIM. Advance publication in the AIM to
supplement the actual NOTAM is required whenever a service change is to
be permanent; e.g., new commissioning, decommissioning, relocation, and
frequency change, or whenever an extended facility shutdown will be
required even though service will be identical when restored. In every
case, decisions regarding the requirement for issuing NOTAMs will be
made by FAA personnel. RSSC will not unilaterally take any action to
effect NOTAM issuance. Additional information relative to reporting
service interruptions can be found in Chapter 3 of Order 6000.15,
General Maintenance Handbook for Airway Facilities. A NOTAM is required:

(1) Before a facility or service may be permanently or temporarily
    interrupted or initiated.

(2) Before a noncommissioned facility can radiate a signal.

(3) Before a commissioned service can be modified such as by relocation,
    frequency change, or change in geographical service area and/or
    altitudes.

b\. **Extended Outages And Service Changes.**

(1) As indicated above, extended facility outages or permanent changes
    affecting the service a facility provides must be advertised in
    advance of the shutdown or change in the AIM.

(2) The wording of such advance notification, particularly regarding
    service changes, must be precise and is a function of the project
    engineering and design effort. WRs will specify establishment
    engineering engineers who are responsible for developing the wording
    and requesting publication in the AIM.

(3) Once published in the AIM, the actual NOTAM effecting the change or
    shutdown need only be a brief notification in standardized format
    that will be issued by the cognizant flight service
    station/automated flight service station (FSS/AFSS) upon the request
    of the SMO manager or designee subject to the approval of affected
    air traffic facility managers. The NOTAM is issued immediately prior
    to the shutdown or change.

c\. **Short Duration Interruption.**

(1) During the course of construction or installation projects, it may
    be necessary to temporarily interrupt the operation of a
    commissioned facility to accomplish work that cannot be accomplished
    with the facility in operation.

(2) All scheduled facility interruptions, extended or of short duration,
    are **subject to the requirements of the ATC system**. In such
    instances, where the interruption cannot be avoided or scheduled far
    enough in advance to make AIM notification feasible, and will not
    extend beyond several hours, the issuance of a NOTAM will be used to
    notify the public of the interruption. Before any NOTAM is issued,
    the approval of all impacted air traffic Facility Managers must be
    obtained.

(3) As soon as the need and timing for a service interruption becomes
    apparent, RSSC\'s representative in charge of the project will
    notify the SMO manager or designee of the details. The SMO manager
    or designee will arrange for the necessary coordination and, if
    possible, obtain tentative shutdown approval and so advise the RSSC
    representative.

(4) Approximately 30 minutes prior to the scheduled shutdown, the AF
    designee should be contacted by RSSC\'s representative, in person or
    by phone, to ascertain if shutdown approval is final or has been
    denied or delayed due to an unforeseen problem; e.g., weather,
    emergency, or unanticipated facility failures.

(5) It is the prerogative of the SMO manager, after given final approval
    for shutdown, to determine how and by whom the shutdown will be
    accomplished or, in fact, if an actual shutdown need occur. The
    nature of the work to be done will influence the SMO Manager\'s
    determination of whether the actual shutdown be accomplished by RSSC
    or AF maintenance personnel.

d\. **Facility Restoration Procedure.**

(1) Any work necessitating an extended or short-duration scheduled
    shutdown will be accomplished as expeditiously as possible. Should
    it at any time appear probable that the required work will not be
    completed by the scheduled end of the shutdown or that other
    problems may delay the restoration, the RSSC representative in
    charge should advise the SMO manager or designee as soon as
    apparent. If necessary, the SMO manager will request an extension of
    the scheduled outage and, depending on the severity of the problems
    encountered by RSSC, may choose to intervene by stopping the TSSC-II
    activity, and taking whatever actions deemed appropriate to restore
    the facility. In such situations, RSSC will take all possible
    actions to minimize costs and outage time.

(2) It is the responsibility of the AF SMO representative to ensure that
    any required facility or system certification is accomplished and to
    advise the cognizant AFSS/FSS and ensure cancellation of the NOTAM.

## 8-6. CONTRACTOR ACCEPTANCE INSPECTION (CAI). {#contractor-acceptance-inspection-cai. .unnumbered}

a.  Since a WR, which authorizes work to be performed under the TSSC-II,
    is not itself a Contract and since RSSC is, effectively, an
    extension of the regional F&E work force, a CAI will not normally be
    required for work performed under the TSSC-II. However, the region
    has the prerogative of requiring a CAI for any WR. When required,
    the CAI will be conducted as described in Paragraph 403 of the
    latest edition of Order 6030.45, Facility Reference Data File.
    Acceptance of work authorized by a WR may be accomplished via a JAI,
    as it would if the work were accomplished by an F&E work force.
    **RSSC IS NOT TO SIGN AS AN FAA REPRESENTATIVE AT ANY JAI.**

b.  In situations where the TSSC-II role, as described in the WR, is to
    provide Resident Engineer (RE) service to monitor and oversee the
    work of another contractor (one not functioning as a TSSC-II
    subcontractor), an RSSC employee serving as RE will, in all
    probability, be required to participate in a CAI. This requirement
    should be specified in the WR. RSSC has developed an RE handbook
    that is available at each regional TSSC office. All regional RE
    requirements should be included in the FWR if they are not
    specifically addressed in the RE handbook.

## 8-7. FACILITY COMMISSIONING/DECOMMISSIONING. {#facility-commissioningdecommissioning. .unnumbered}

a.  Commissioning or decommissioning of a facility or service can only
    occur after the requirements specified in Chapters 5 and 6 of Order
    6030.45 have been accomplished. Beyond participation in JAI and
    flight inspection activities, the TSSC-II will not normally be
    involved in the commissioning process. However, the WR may stipulate
    that RSSC is responsible for developing the facility commissioning
    data to be submitted to the NFDC for publication prior to
    commissioning.

b.  Depending on the content of a specific WR, RSSC may be assigned
    responsibility to accomplish any or all of the
    decommissioning actions.

## 8-8. LIAISON ACTIVITIES. {#liaison-activities. .unnumbered}

a\. At most TSSC-II work site locations, FAA personnel have established
working relationships with people and organizations outside of the FAA
with whom RSSC will be required to interface and interact. These include
airport management personnel, local government and community officials,
utility company officials and personnel, and property owners.

b\. Upon RSSC request, the appropriate FAA personnel; i.e., project
managers or engineers, AF SMO and/or SMO field office managers, and AT
facility managers will provide liaison between the RSSC personnel and
these local organizations. This liaison may, as appropriate, take the
form of an introduction or providing a name and telephone number. Once
initial contact is established, all necessary dealings between RSSC and
these external organizations may be handled directly.

# TSSC EXTERNAL RELATIONSHIPS

## 9-1. GENERAL. {#general.-4 .unnumbered}

a\. In the course of accomplishing work at FAA facilities, airports and
various other locations, RSSC may be required to interface with
personnel from numerous non‑FAA organizations. Unless otherwise
instructed by the ATO, RSSC should first advise the local FAA AF Manager
of its intention to contact any of the above. These include, among
others:

(1) Airport management officials.

(2) Other Federal Government agents; e.g., DOD military facilities
    personnel.

(3) State, local and regional officials.

(4) Airport authorities.

(5) Planning commissions.

(6) Licensing boards.

(7) Private property owners.

(8) Utility companies.

    b\. The local FAA Manager will, in coordination with the ATO:

```{=html}
<!-- -->
```
(1) Determine that TSSC-II personnel have the proper background,
    information, concern for safety and understanding of procedures to
    accomplish the necessary coordination; or

(2) Accompany and assist TSSC-II personnel in such contact.

c\. Neither FAA nor TSSC-II personnel shall attempt to, or give the
appearance of, negotiating for any rights in property and/or related
utility or janitorial services. Such authority has been delegated only
to FAA CO personnel, or as officially tasked, to Logistics Support
Service Contract (LSSC) personnel working in the Logistics Division. Any
unauthorized discussion on contractual actions regarding real property
and/or related services could be misinterpreted and jeopardize the
Government\'s position.

## 9-2. AIRPORT SPONSORS/AUTHORITIES. {#airport-sponsorsauthorities. .unnumbered}

a.  Coordination with airport sponsors and authorities may be necessary
    to obtain site access or information available only from or through
    the sponsor. RSSC is required to comply with all rules and
    regulations imposed by airport authorities.

b.  RSSC can be tasked with providing all pertinent data necessary for
    describing land requirements. This information should be contained
    in the CSER where required, or in site survey reports.

c.  The FAA is responsible for obtaining the necessary real estate
    licenses or leases from the airport sponsor or authority.

## 9-3. FACILITY SITE PROPERTY OWNERS. {#facility-site-property-owners. .unnumbered}

The requirement for any right-of-way acquisition should be determined by
the FAA and/or TSSC-II project engineers. The requirement is provided to
the Real Estate Branch for obtaining authorization prior to start of any
work at project sites. RSSC will provide a description of any land or
right‑of‑way acquisition required including a survey, plot description,
and ownership information adequate to permit the real estate personnel
to negotiate any necessary land rights. RSSC will maintain coordination
with the appropriate ATO to ensure that selected sites are obtainable.

## 9-4. UTILITY COMPANIES.  {#utility-companies. .unnumbered}

RSSC, while conducting work on or off airport property, may have an
unexpected requirement for access to or services from the local utility
companies. RSSC will develop and prepare a complete description of the
services or access required for inclusion on a PR to the Real Estate
Branch. **RSSC shall not negotiate or make agreements with utility
company or airport sponsor personnel**. This is only to be accomplished
by authorized FAA logistics personnel.

## 9-5 OTHER GOVERNMENT CONTRACTS, CONTRACTORS & ORGANIZATIONS. {#other-government-contracts-contractors-organizations. .unnumbered}

RSSC may be required to interface and/or coordinate with other FAA
contractors or Government agencies.

## 9-6. OTHER.  {#other. .unnumbered}

If, during this Contract, RSSC interfaces with an organization or
individual and encounters difficulties that may impact on RSSC\'s
ability to accomplish assigned work, the TO/ATO will be notified. The
TO/ATO is responsible for coordinating resolutions to any such
difficulties.

# LOGISTICS

## 10-1. GENERAL.  {#general.-5 .unnumbered}

RSSC will provide the administrative and logistics support required by
its work force at its national and regional headquarters locations.
These locations will be staffed and equipped to support such activities
as personnel services, accounting, payroll, drafting, typing, copying,
etc. However, there may be occasions when TSSC-II personnel, working
on-site at locations remote from TSSC headquarters or regional offices,
will require support that may be neither feasible nor practical to
provide from TSSC-II headquarters. In many cases, these services may be
available locally from FAA sources.

## 10-2. GOVERNMENT PROVIDED SERVICES. {#government-provided-services. .unnumbered}

a.  The TSSC-II requires that RSSC provide for whatever office space,
    furniture, and equipment is required for the performance of the
    Contract. However, at FAA job sites, when required and authorized by
    a WR, the Government may furnish certain facilities and/or services
    to TSSC-II personnel. This support will be provided on an \"as
    available\" basis and the requirements of the organization providing
    the service take precedence over RSSC\'s needs. These facilities and
    services will be used only for official purposes related to the
    performance of the TSSC-II. No personal or non-Contract use of these
    services or facilities is permitted.

b\. The TSSC-II is a cost‑plus‑fixed‑fee Contract and any cost savings
to RSSC resulting from cooperation and assistance provided by FAA
personnel will ultimately result in a cost savings to the FAA. However,
TSSC-II subcontract personnel may be working on a firm fixed‑price
contractual basis. Therefore, while FAA personnel are expected to be
cooperative in their relationships with TSSC-II subcontractors, any
assistance that involves the expenditure of FAA resources, whether
manpower, money, or materiel, should be in the best interests of the
Government. For example, it is clearly in the interest of the Government
to identify the location of buried cables in the vicinity of the work
site while it may or may not be in the Government\'s interest to permit
use of Government telephones or copying equipment.

c\. FAA personnel should judge each request for assistance on its
individual merit. In questionable situations, field supervisors may
contact the ATO, and the ATO with the ACO, provide guidance.

d\. Among the services that may be appropriate for the Government to
provide to RSSC are:

(1) Work space and furnishings, including office space.

(2) Forms and documents.

(3) Data processing support.

(4) Telephone services.

(5) Special purpose vehicles.

(6) Special purpose tools and test equipment.

## 10-3. USE OF GOVERNMENT FACILITIES AND EQUIPMENT.  {#use-of-government-facilities-and-equipment. .unnumbered}

RSSC personnel, when engaged in Contract work at locations away from
TSSC-II headquarters, may be permitted the use of available FAA
facilities, equipment, and services, when such facilities, equipment,
and services are required for the performance of work under the Contract
and can be provided at no additional cost to the FAA or at less cost
than they could be provided by RSSC.

a.  **Office Space, Work Space, Furnishings, And Equipment**.

```{=html}
<!-- -->
```
(1) Prior to the issuance of a WR, RSSC will advise the TO/ATO in
    writing what, if any, will be the TSSC-II requirement for office
    space, work space, furnishings, and equipment. The TO/ATO will
    determine, through coordination with the SMO manager(s), if local
    FAA capability exists to provide the necessary support.

(2) As a general rule, some form and quantity of work space will be
    required by RSSC for most WR efforts. However, RSSC-dedicated office
    space and furniture will not be considered unless TSSC-II personnel
    are expected to maintain a local presence for an extended period.
    Use of desk space and access to office equipment may be provided on
    an \"as available" and "as needed\" basis for short duration
    projects.

(3) When essential and available, space and equipment will normally be
    provided at the closest SMO or SSC location to the work site or at
    the work site itself.

(4) If the TO/ATO determines that available FAA space, furniture and
    access to office equipment (copier, word processor terminal, etc.)
    are inadequate to support the minimum essential requirements of the
    TSSC-II work force, the CO may authorize RSSC to rent or lease space
    and equipment as needed at prices not to exceed those determined by
    the CO/ACO to be appropriate to the area. Such authorization and
    costs must be requested separately from the CO.

b\. **Forms And Documents.**

As a general rule, all available forms and documentation useful to RSSC
in accomplishing a WR should be Government provided. Government/FAA
forms, publications, and documents required for accomplishment of WRs
that are not identified in the WR as being a Government responsibility
to provide will be furnished by RSSC.

c\. **Use Of Government Telephones.**

RSSC personnel are authorized use of FAA administrative telephones for
official use related to the Contract, including the authority to make
essential long distance calls. RSSC personnel will comply with the
latest edition of Order 1830.1, Policy for Non‑FAA Users and Foreign
Correspondents Access to FAA Operational Communications, as well as all
local administrative controls, restrictions, and documentation
requirements in effect where the telephone use occurs. RSSC personnel
will ensure that use of the FAA telephone is held to the minimum number
of calls and the shortest duration, consistent with job requirements.

d\. **Special Purpose and/or Interagency Fleet Management System (IFMS)
Vehicles**

(1) RSSC is responsible for providing transportation to, from, and
    between work sites covered under this Contract. However, when access
    to work sites is possible only by use of special purpose vehicles
    such as aerial tramway, boat, airplane, snow tractor or plow, and
    all-terrain vehicles, and the FAA has such special purpose vehicles
    available, RSSC's use of such vehicles may be authorized. When
    approving RSSC/subcontractor employees to drive special purpose
    and/or IFMS vehicles, the cognizant TO/ATO and CO/ACO will ensure
    that they understand the requirements of the Contract and any other
    requirements of FAA Order 4670.2B, "Motor Vehicle Management."

(2) RSSC will include its requirements for Interagency Fleet Management
    System (IFMS) and/or special purpose vehicles in the WR Plan,
    including the type of vehicle required and estimated date(s)
    required. When approved by the cognizant TO/ATO and CO/ACO in a Work
    Release, authorization to use special purpose and/or IFMS vehicles,
    including Government-owned of leased special purpose vehicles, may
    be granted. Such authorization shall be for official purposes only
    in performance of this Contract, provided that RSSC/the
    subcontractor assumes full responsibility for the drivers under the
    provisions of the Contract.

(3) Special purpose vehicles are defined as:

```{=html}
<!-- -->
```
(a) Vehicles used to provide transportation, but also may include work
    vehicles such as fork lift or bucket trucks which might be operated
    by Contractor personnel in performing Contract tasks. Use of
    construction equipment, such as graders, tractors, and front-end
    loaders by RSSC or subcontractor personnel is not included.

(b) Four-wheel drive passenger vehicles are not routinely considered
    special purpose vehicles, and when required for extended periods,
    are the RSSC's responsibility to provide. However, for brief periods
    due to snow or hazardous road conditions, when site access is only
    possible by a four-wheel drive vehicle, such vehicle will fit the
    category of special-purpose.

(c) Passenger-type vehicles or vans that have been specially equipped
    for access onto airport property. These vehicles generally are
    equipped with special license plates, markings, radios, and lights
    that allow them access to airports' controlled areas.

```{=html}
<!-- -->
```
(4) RSSC and subcontractors, and their employees who will be driving
    IFMS vehicles, are subject to the following:

```{=html}
<!-- -->
```
(a) Drivers must possess necessary state, local, and airport licenses,
    permits, and expertise for operation of the type of vehicle to be
    driven, and must report immediately any revocation or restriction of
    those licenses or permits.

(b) RSSC assumes liability for any personal injuries or property damage
    and liability resulting from RSSC's use, operation, and control.
    Assumption of liability will be in writing.

(c) Drivers are personally responsible for any payment of any traffic
    summonses received, including parking violations.

(d) Use of the vehicle by RSSC will not interfere with FAA requirements.

(e) Drivers may not pick up hitchhikers, and may not transport any
    passengers who are not on official business. Transportation of
    non-official/non-Government passengers in official Government
    passenger carriers creates the possibility of tort claims and public
    criticism. Therefore, it shall be strictly limited to those
    situations where a non-Government person is to be transported in
    IFMS vehicles on official business only (i.e., a civilian general
    aviation pilot requiring certification and needing transportation
    from the plane to the testing facility, a non-Government person
    performing volunteer work on behalf of the FAA, etc.).

(f) Drivers must operate the vehicle in a safe and prudent manner at all
    times, obey all speed limits and other laws, use seat belts and
    require all passengers to use seat belts. They must ensure that the
    vehicles and keys are secured when left unattended.

(g) Drivers must immediately report any vehicle accident involving
    damage or personal injury or any vehicle in unsafe driving
    condition, whether or not as the result of an accident. Drivers may
    be personally responsible for accidents involving misconduct.

```{=html}
<!-- -->
```
(5) Drivers will maintain all required records of miles driven by
    locations and dates. Vehicles will normally be dispatched and
    returned full of gas and oil.

e\. **Tools and Test Equipment.**

(1) It will be the responsibility of RSSC to obtain all common hand and
    portable power tools and surveying equipment required by TSSC-II
    personnel under this Contract. Such equipment shall be controlled
    and issued from each of RSSC's regional offices. Any equipment
    required to perform the work that is not available from the regional
    office shall be identified in RSSC's WR Plan.

\(2\) Special purpose tools, unique to a particular facility or system
and not readily obtainable on the open market, will be Government
provided. FAA-owned test equipment assigned to a particular facility may
be used by RSSC when working on that facility, provided that such usage
does not interfere with SMO requirements. When test equipment is not
available at the site, RSSC, in coordination with the FAA, will
determine how such equipment will be provided, unless it is equipment
normally carried by RSSC. Normally, this equipment will consist of such
items as voltage and current measuring devices, pressure gauges, and air
conditioning test sets. All equipment provided by RSSC will conform to
the requirements of the Contract, Materiel Management. Also see
paragraph 10-5 of this Handbook.

\(3\) It is RSSC\'s responsibility to ensure that RSSC-provided test
equipment will meet the calibration requirements described in the latest
edition of Order 6200.4, Test Equipment Management Handbook. To the
extent possible, test equipment calibration will be accomplished
utilizing FAA test equipment calibration facilities or contracts.

f\. **Government Furnished Property (GFP).**

(1) GFP, if any, will be described in individual WR and delivered in
    \"as‑is\" condition in accordance with the delivery date identified
    in the WR.

\(2\) This support will be provided only on an \"as available\" basis
and all requirements of the organization providing the service take
precedence over the needs of TSSC.

## 10-4. SMO LEVEL SUPPORT AND CONDITIONS. {#smo-level-support-and-conditions. .unnumbered}

a\. **Administrative Support Services.** Administrative support services
will be provided only to the extent that they can be provided within
available SMO resources. Services such as typing or copying will not
generally be provided except for requirements stated in Order 6030.45,
Chapter 4. As a rule, SMO-provided administrative services will be
limited to providing access to space and/or equipment. SMO/SSC
requirements for space, equipment, vehicles, and telephone take
precedence over the needs of RSSC.

b\. **GFE Acceptance, Storage, and Transfer Of Stewardship.**

(1) The SMO may be required to accept delivery, arrange for storage, and
    maintain custody of materiel received at the SMO or SMO field office
    for installation by RSSC.

(2) Responsibility for materiel and equipment shipped to designated F&E
    storage facilities will remain with the F&E organization until
    inventoried and turned over to RSSC.

(3) Subsequent to the issuance of a WR, on the first field visit by RSSC
    personnel, all installation equipment and materiel being held in
    storage for the project will be turned over to RSSC\'s
    representative in accordance with local and regional procedures.

(4) RSSC will be responsible for preparation of excess property lists
    for materiel or equipment provided, but not needed or used for the
    accomplishment of the project. The SMO will be responsible for
    preparation of excess property reports for materiel or equipment
    made surplus by the installation.

(5) RSSC involvement in notification, disposal, or shipment of excess
    property will be spelled out in the WR.

## 10-5 MATERIEL MANAGEMENT.  {#materiel-management. .unnumbered}

a\. All materiel obtained through or used as a result of TSSC-II
national and regional WRs will be managed by the FAA and RSSC in
accordance with FAA policy and procedures, as well as RSSC\'s approved
Materiel Management Plan. Materiel includes both nonexpendable and
expendable property.

(1) Nonexpendable materiel normally does not lose its identity in
    performance of a WR. Examples of nonexpendable equipment include
    towers, computer systems, measuring tools, cameras, and test
    devices.

(2) Expendable materiel is normally consumed in the performance of a WR.
    Examples of expendable materiel include installation hardware and
    gaskets.

b\. The regional PA will administer the Contract requirements and
obligations relating to authorized, accountable GFP or CAP.

c\. Government Furnished Equipment/Property (GFE/GFP) And Contractor
Acquired Property (CAP) Overview.

(1) RSSC will manage and control GFE/GFP and CAP in accordance with its
    FAA-approved contract government property system control plan.

(2) GFE/GFP consists of items formally provided to RSSC by the FAA for
    use in, or stored in, TSSC-II-owned or controlled locations.

(3) CAP are items procured by RSSC as a direct cost under a WR, and
    stored or used in TSSC-II-owned or controlled locations.

d\. Regional Materiel/Property Management Procedures. This information
relates only to materiel obtained under regional WRs. The materiel will
be processed in accordance with established FAA procedures. Normally,
the work to be accomplished under a WR will occur within the region
issuing the WR. In cases when a WR will accomplish work for, or within
another region, the information requested within this chapter should be
furnished to all regional logistic branches in the affected regions.

(1) FAA Materiel/Property Management Orders. All materiel received on
    site for a project, whether purchased by the FAA or RSSC, will be
    managed and accounted for by the FAA, in accordance with current
    agency project materiel management policies and procedures contained
    in FAA policy and procedural orders and desk handbooks pertaining to
    the management and control of NAS F&E project materiel.

(2) TSSC Purchased Property. Materiel can be property managed (when
    purchased under TSSC) only if proper documentation is supplied.
    Therefore, all materiel and property purchased by TSSC-II will be
    annotated on back‑up sheets included with RSSC invoices. These
    sheets are titled \"Acquired Property Report\" and \"Summary
    Acquired Property Report.\" The Acquired Property Report will be
    provided with RSSC\'s monthly invoice and will list items invoiced
    for the current period. The Summary Acquired Property Report will be
    furnished as part of the WR close-out information, and will provide
    a recap of all TSSC-II-purchased items chargeable to that WR.

(3) TSSC Property Tracking. The following procedure shall be followed in
    tracking property in the TSSC contract:

```{=html}
<!-- -->
```
a.  For GFP, a Form 4650-12 must be issued by FAA to transfer property
    to TSSC contract #DTFA01-95-000015 to a specific WR of to the
    Property Tracking WR, if the property is in simultaneous use on
    multiple WRs. After the completion of the WR, RSSC will transfer the
    property either to the Property Tracking WR (Form 4650-12 not
    necessary) or back to the FAA using Form 4650-12. If FAA chooses the
    first option, there is no need to move the property in and out of
    the Property Tracking WR for subsequent uses since Raytheon has an
    approved Government Property Tracking System which will provide the
    location of the property at all times.

b.  For CAP, RSSC will transfer the property to the Property Tracking WR
    after the completion of the WR. There is no need to move the
    property in and out of the Property Tracking WR for subsequent uses.

```{=html}
<!-- -->
```
(4) The FAA will prepare a "no-cost, \$0" FWR for the TSSC-II property
    that will be used for the duration of the Contract. This FWR would
    include property such as CAEG equipment, computers, and equipment
    used for program management functions.

(5) A 4650-12 shall be prepared and accompany a WR revision or WRCA
    which notes the property transfer from-to, to-from the "no-cost,
    \$0" FWR to track the property. If property is to be transferred to
    RSSC for a short time period (i.e., less than 1 year) the FAA WR
    engineer shall prepare, and sign, a 4650-12 as a hand receipt and
    attach a copy to the WR revision or WRCA which notes the property
    transfer. Upon return of the property, the hand receipt shall be
    duly noted and placed with the earlier copy attached to the earlier
    WR revision.

```{=html}
<!-- -->
```
(6) Upon the recommendation of the TO/ATO and with the authorization of
    the CO, the property will be transferred as needed first to another
    WR within the region and then to a WR in another region. A Form
    4650-12 is to be prepared and accompany the affected WRs.

(7) A discrete report will be furnished for each location included in a
    WR. This will provide regional PA and accounting offices the
    information necessary to relate the inventory to a specific job
    order number (JON), or site, when a WR includes multiple JONs or
    sites. For uninstalled GFP/CAP, either at the completion or
    termination of the WR or when the property becomes excess to the
    needs of the WR, RSSC shall report the property regardless of value,
    to the appropriate PA.

```{=html}
<!-- -->
```
(a) The total cost on the Acquired Property Report prepared by RSSC for
    all locations, both expendable and nonexpendable property and
    materiel purchases, should match the invoiced amount billed for
    materiel.

(b) The ATO will provide the ACO and PA with a cross reference of JONs
    and WR numbers, which ties them to a site. Whenever funds from one
    JON are used for a different JON, both the gaining and losing JON,
    along with relevant WR numbers, shall be identified on the cross
    reference.

(c) The ACO is to provide a copy of all property and materiel reports
    included with TSSC-II invoices, to the applicable regional PA.

(d) National program managers are to provide copies of the report to
    each affected regional PA.

e\. TSSC Materiel Removal/Shipping Authorization. RSSC shall not be
authorized to remove materiel from a site for any reason without prior
coordination with the applicable SMO manager, F&E project engineer, and
regional project materiel manager. The FAA shall not ship materiel to
RSSC unless it is so stated in the WR, and the shipment is accompanied
by FAA Form 4650‑12, signed by the applicable region/center/headquarters
TO/ATO and CO/ACO. A separate FAA Form 4650-12, signed by the TO/ATO and
CO/ACO is to accompany the property when it is returned to the FAA.
Internal TSSC-II movement of Government property by RSSC will be done in
accordance with the RSSC government property control plan.

# FAA TECHNICAL SUPPORT TO TSSC

## 11-1. GENERAL. {#general.-6 .unnumbered}

In the process of performing work on the variety of anticipated WR
activities, there may be occasions when FAA technical support to the
TSSC work effort is appropriate. This support may be due to
unanticipated emergency occurrences or may be routine. TSSC-II is a
cost-reimbursable contract; therefore, assistance given to RSSC can save
the Government money. The following paragraphs describe situations where
support might be appropriate and the various levels of available
support.

## 11-2. FAA INTERVENTION.  {#faa-intervention. .unnumbered}

Typically, technical support will be provided from the appropriate FAA
organization in response to RSSC's request for such support. There may
be occasions, however, when the FAA may consider it necessary to
intervene unilaterally in the TSSC-II work effort. These instances will
generally result from a need to restore to operation a facility
inadvertently shutdown, or a scheduled facility shutdown that RSSC
cannot restore. No hard and fast criteria will be established for a
time-frame or situations when FAA restoration activity or other types of
intervention will be initiated. Each situation will be considered
separately in light of its impact on safety and air traffic control.

a.  **Inadvertent Shutdown.**

```{=html}
<!-- -->
```
(1) As a general rule, the AF maintenance organization will intervene in
    the case of an inadvertent shutdown caused by TSSC-II activity. AF
    maintenance personnel will do whatever is deemed necessary by the
    SMO manager to restore operation, up to and including stopping all
    TSSC-II work on and around the affected facility and undoing the
    work already accomplished by RSSC prior to the shutdown.

(2) Prior to the arrival of AF personnel, RSSC personnel will make every
    effort to restore the facility to operational status, and will
    cooperate fully with AF personnel upon their arrival. RSSC will not
    attempt to place a certifiable facility in service prior to
    certification by AF personnel. The SMO manager will advise the
    TO/ATO of any situation requiring emergency intervention in TSSC-II
    activity or expenditure of AF maintenance manpower or funding as
    soon as the action is taken.

```{=html}
<!-- -->
```
b.  **Extended Scheduled Shutdown.**

```{=html}
<!-- -->
```
(1) As soon as it becomes apparent that a scheduled facility outage will
    need to be extended, the RSSC WR Manager will notify the SMO
    Manager, or designee, of the reasons for, and the anticipated
    duration of, the extension.

(2) Generally, no intervention by the FAA will occur in the case of a
    scheduled shutdown that must be extended because RSSC needs
    additional time to complete the work that required the shutdown.
    However, if a situation arises that creates or may create a serious
    problem in air traffic control, such as failure of an adjacent
    facility or anticipated arrival of inclement weather, the SMO
    manager may intervene.

(3) If, however, a scheduled facility shutdown needs to be extended
    because of the inability of RSSC to effect restoration upon
    completion of its work, the SMO will take whatever actions are
    appropriate to effect restoration.

(4) As in the case of inadvertent shutdown, the SMO manager will advise
    the TO/ATO of any situations requiring emergency cessation of
    TSSC-II activity or expenditure of AF maintenance manpower or
    funding for facility restoration as soon as the action is taken.

## 11-3. SMO SUPPORT. {#smo-support. .unnumbered}

a.  A significant amount of high-level technical expertise is available
    within AF SMO staffs. This expertise is available across the entire
    spectrum of the FAA facility inventory. It resides in the
    engineering, engineering/technician, and technician positions at
    both SMO headquarters and SMO field office locations. In addition to
    the practical and conceptual knowledge possessed by these people,
    they also possess in-depth site‑specific knowledge regarding such
    things as cable routing and inter-facility wiring, which may be
    extremely valuable in developing site preparation and installation
    details.

b.  Because the AF SMO assumes responsibility for F&E upon
    commissioning, a properly installed and soundly engineered system is
    in the best interests of the SMO. Therefore, the expertise of the
    SMO staff is generally available, informally, and upon request, to
    provide technical advice and support to FAA in‑house F&E
    installation and engineering personnel. The same relationship will
    exist as regards TSSC-II installation and engineering personnel.

c.  As with other services provided to RSSC by the AF maintenance
    organization, technical assistance can only be provided insofar as
    personnel are available to assist without impacting higher priority
    SMO responsibility for ensuring the integrity and continuous
    operation of the NAS.

d.  Nothing in the above paragraphs should be interpreted as requiring
    that SMO personnel should assist RSSC in the performance of its
    routine work. SMO technical assistance should be reserved for
    situations where site‑specific knowledge, previous experience,
    and/or high-level technical expertise may resolve or forestall a
    problem encountered by RSSC causing excessive costs or delay in the
    restoration or commissioning of a facility.

e.  SMO personnel may be requested to conduct field interviews in
    support of the ACO fulfilling the Davis-Bacon Act wage determination
    requirements.

## 11-4. REGIONAL OFFICE TECHNICAL SUPPORT. {#regional-office-technical-support. .unnumbered}

a.  Within the AF staff at regional headquarters (including ANI
    Implementation Service Centers) are engineers and specialists
    possessing high level skills over the entire range of AF functions.
    These skills range from design engineering and development of
    specifications to hands‑on installation and maintenance activities.
    These skills are available to assist RSSC on request on an \"as
    available\" basis.

b.  Regional AF divisions have specialists with experience and expertise
    in dealing with other governmental and non-governmental
    organizations regarding frequency management and leased
    communications. These staff people will be available to assist FAA
    Project Managers in support of TSSC efforts in such areas as
    obtaining frequency authorizations, determining source and areas of
    frequency interference, developing frequency coverage charts, and
    arranging for leasing and installation of telecommunication services
    from commercial services.

## 11-5. FAA LOGISTICS CENTER SUPPORT. {#faa-logistics-center-support. .unnumbered}

a.  The FAA Logistics Center, a subordinate element of the FAA
    Aeronautical Center, is the principal provider of equipment, spare
    parts, and materiel to support the installation, maintenance, and
    operation of the NAS.

b.  Typically, the development of a WR for facility construction and/or
    installation requires a list of GFE. Much, if not all, of this
    installation materiel and equipment is provided by the Logistics
    Center as identified in the Project Status Report.

c.  The WR may require RSSC to be responsible for developing the list of
    materiel and equipment identified in a WR Plan or approved CSER
    through the regional Materiel Management Branch in accordance with
    Order 4650.7.

d.  In emergency situations, the Logistics Center may provide
    replacement parts required in the installation process. SMO and
    regional logistic specialists and purchasing agents will provide
    assistance to RSSC personnel in obtaining emergency and
    failure-under-warranty supply support.

## 11-6. FAA HEADQUARTERS TECHNICAL ASSISTANCE.  {#faa-headquarters-technical-assistance. .unnumbered}

a.  Within the FAA, the very highest level of technical expertise
    relevant to the facilities and systems comprising the NAS is to be
    found at the FAA Technical Center at Atlantic City, New Jersey,
    which has responsibilities in radar automation and ATC computer
    equipment; and at the Aeronautical Center, Oklahoma City, Oklahoma,
    which has responsibilities oriented toward the navigational
    aids/communications/radar equipment and plants and structures areas.
    The principal responsibility of both groups is in maintenance and
    maintenance engineering. However, RSSC may request assistance from
    these groups, when SMO and regional technical assistance resources
    are unavailable or have been exhausted.

b.  Any request for support from the Technical or Aeronautical Centers
    must be routed through the TO/ATO. Assistance will be provided only
    insofar as it will not impact on their primary duties.

## 11-7. TRAINING SUPPORT. {#training-support. .unnumbered}

a.  It is not the intent of the FAA to provide general technical or
    management training for RSSC personnel. There may be occasions,
    however, when RSSC personnel will be performing work on systems or
    equipment that are new and/or unique to the FAA, for which in‑depth,
    theoretical knowledge of the system or equipment is required. On
    some of these occasions, it may be unreasonable to expect that RSSC
    will be able to provide employees who already possess the necessary
    expertise. In such situations, training of RSSC employees may be
    required and the cost of such training may be authorized as a direct
    charge to the Contract through a WR assigning the task.

b.  Essential training determined to be most appropriate for
    accomplishment by RSSC, by equipment vendors, or other commercial
    training facilities will be the responsibility of RSSC to arrange.
    RSSC\'s National Program Office will provide the FWR RPM/RPE with
    cost estimates for the necessary training. The FWR RPM/RPE, in
    conjunction with the TO/ATO and CO/ACO, will approve or disapprove
    the cost of training as a direct charge against the WR.

c.  WRs will not be issued for work that requires the training unless
    the training has been approved as chargeable to the FWR and is
    available.

d.  If RSSC personnel need training to accomplish a WR, RSSC arranges
    the training, and it is charged to the FWR.

> **[APPENDIX 1. LIST OF ACRONYMS]{.underline}**

ACO Administrative Contracting Officer

ADPE Automated Data Processing Equipment

AF Airway Facilities

AFSS Automated Flight Service Station

AIM Airman\'s Information Manual

ANI NAS Implementation

ANS NAS Transition and Integration

ASDE Airport Surface Detection Equipment

ASR Airport Surveillance Radar

ASU Office of Acquisitions

AT Air Traffic

ATE Automatic Test Equipment

ATC Air Traffic Control

ATO Associate Technical Officer

AWOS Automated Weather Observation System

BAC Budgeted at Completion

CAEG Computer Aided Engineering Graphics

CAI Contractor Acceptance Inspection

CAP Contractor Acquired Property

CBI Computer Based Instruction

CFCF Central Flow Control Function

CFM Contractor Furnished Materiel

CIP Capital Investment Plan

CL&T Contractor Labor and Travel

CO Contracting Officer, ASU-340

COB Close of Business

CPFF Cost Plus Fixed Fee

> **[APPENDIX 1. LIST OF ACRONYMS (CONTINUED)]{.underline}**

CPR Cost Performance Report

CSER Contractor Site Engineering Report

DAFIS Departmental Accounting & Financial Information System

DIS Defense Investigative Service

DPA Delegation of Procurement Authority

DOD Department of Defense

DODISP Department of Defense Industrial Security Program

DOL Department of Labor

DOT Department of Transportation

DUATS Dual User Access Terminal System

EAC Estimate at Completion

EDDA Environmental Due Diligence Audit

EEP Establishment Engineering Plan

ETC Estimate to Complete

F&E Facilities & Equipment

FAA Federal Aviation Administration

FAR Federal Acquisition Regulations

FCO Funds Certification Official

FS Fund Source

FSS Flight Service Station

FTS Federal Telecommunication System

FWR Final Work Release

G&A General & Administrative

GFD Government Furnished Document

**[APPENDIX 1. LIST OF ACRONYMS (CONTINUED)]{.underline}**

GFE Government Furnished Equipment

GFI Government Furnished Information

GFM Government Furnished Materiel

GFP Government Furnished Property

GSA General Services Administration

HAZMAT Hazardous Material

HQS Headquarters

IFB Invitation For Bid

IFMS Interagency Fleet Management System

IGCE Independent Government Cost Estimate

JAI Joint Acceptance Inspection

JON Job Order Number

JOTFOC Justification for Other Than Full and Open Competition

LRE Latest Revised Estimate

LRU Lowest Replaceable Unit

LSSC Logistics Support Service Contract

NAC National Agency Check

NACI National Agency Check and Inquiries

NAS National Airspace System

NFDC National Flight Data Center

NEFSD National Engineering Field Support Division

NLT No Later Than

NOTAM Notices To Airmen

NPM National Program Manager

NPM WR National Program Management Work Release

**[APPENDIX 1. LIST OF ACRONYMS (CONTINUED)]{.underline}**

NTE Not To Exceed

NTP Notice To Proceed

NWR National Work Release

ODC Other Direct Charges

OSHA Occupational Safety and Health Administration

PA Property Administrator

PA Project Authorization

PE Project Engineer

PM Program Manager

PMC Project Materiel Cumulative Report

PR Procurement Request

PSR Program Status Review

PWR Preliminary Work Release

QA/C Quality Assurance/Control

QC Quality Control

Q&Q Quantitative and Qualitative Analysis

RE Resident Engineer

REM Regional Engineering Manager

RCAG Remote Center Air/Ground

RML Radar Microwave Link

RMMS Remote Maintenance Monitoring System

ROM Rough Order of Magnitude

RPE Regional Project Engineer

RPM Regional Program Manager

**[APPENDIX 1. LIST OF ACRONYMS (CONTINUED)]{.underline}**

RPMMS Regional Project Materiel Management System

RSC Raytheon Service Company

RSSC Raytheon Support Services Company

RWR Regional Work Release

SEI System Engineering & Integration

SMO System Management Office

SOW Statement of Work

SSC System Support Center

T&E Test & Evaluation

TO Technical Officer

TPS Test Program Sets

TSS Technical Support Services

TSSC Technical Support Services Contract

TSSC-II Technical Support Services Contract-II

TSSC RPM TSSC Regional Program Manager

WBS Work Breakdown Structure

WR Work Release

WRCA Work Release Change Action

**[APPENDIX 2. TSSC OFFICE LOCATIONS]{.underline}**

> [Region]{.underline} [Name]{.underline} [Phone No.]{.underline}
> [Mailing Address]{.underline}
>
> Headquarters William Britz (202) 863-1690 Raytheon Support Services
> Co.

National FAX-(202) 863-1699 600 Maryland Ave., SW

Program Manager #895

Washington, DC 20024

Paul Plein (617) 238-2491 Raytheon Support Services Co.

National FAX-(617) 238-2485 2 Wayside Road

Contracts Manager Burlington, MA 01803

> Alaska M. Jean-Georges (907) 279-5400 Raytheon Support Services Co.

TSSC RPM FAX-(907) 276-0563 810 B Street

Anchorage, AK 99501

> Central Lloyd McIntyre (913) 621-2800 Raytheon Support Services Co.

TSSC RPM FAX-(913) 621-2891 10 E. Cambridge Circle Dr.

#120

Kansas City, KS 66103

> Eastern Jerry Kluba (516) 228-8828 Raytheon Support Services Co.

TSSC RPM FAX-(516) 228-8874 990 Stewart Avenue #810

Garden City, NY 11530

> Great Lakes Hugh Bannon (847) 699-8400 Raytheon Support Services Co.

TSSC RPM FAX-(847) 699-2345 10400 West Higgins Ave. #500

Rosemont, IL 60018

**[APPENDIX 2. TSSC OFFICE LOCATIONS (CONTINUED)]{.underline}**

[Region]{.underline} [Name]{.underline} [Phone No.]{.underline} [Mailing
Address]{.underline}

New England Sandra J. Wilk (781) 270-3002 Raytheon Support Services Co.

TSSC RPM FAX-(781) 270-3010 16 New England Exec. Park

Burlington, MA 01803

Northwest Ira Head (206) 204-5700 Raytheon Support Services Co.

Mountain TSSC RPM FAX-(206) 226-8590 1801 Lind Avenue, Bldg. A, #100

Renton, WA 98055

Southern Ed Fox (770) 907-3300 Raytheon Support Services Co.

TSSC RPM FAX-(770) 907-3301 1895 Phoenix Boulevard #200

Atlanta, GA 30349

Southwest Thomas Sprankle (817) 847-4800 Raytheon Support Service Co.

TSSC RPM FAX-(817) 847-4999 3910 Sandshell Drive

Ft. Worth, TX 76137

Western Charles Lazarou (310) 297-2200 Raytheon Support Service Co.

Pacific TSSC RPM FAX-(310) 536-6774 Continental Park

3601 Aviation Blvd. #2400

Manhattan Beach, CA 90266

Technical Philip Gray (609) 641-5544 Raytheon Support Service Co.

Center TSSC RPM FAX-(609) 641-8095 500 Scarborough Drive #304

Egg Harbor, NJ 08234

Aeronautical Thomas Sprankle (405) 954-8608 Raytheon Support Service
Co.TSSC

Center TSSC Regional FAX-(405) 954-5591 Headquarters Bldg, Rm 128

Project Engineer P.O. Box 25082

Oklahoma City, OK 73125

**APPENDIX 3. ATTACHMENT J.002**

**[LIST OF CANDIDATE PROJECTS FOR WORK RELEASES]{.underline}**

**1.0 GENERAL TASK AREAS**

The following is a list of technical areas contained in the CIP which
are candidates for Work Releases. The Contractor is cautioned that some
of the following areas of work may never be assigned to the TSSC-II.
Some may be completed prior to contract award and FAA regions may elect
to accomplish others in‑house or through other means. This list is
comprised of CIP project titles and short descriptions along with a
proposed synopsis of the scope of work. It is provided for planning
purposes only. CIP project numbers are indicated in parentheses. For
more information concerning the project descriptions and schedules,
refer to the Aviation System Capital Investment Plan publication.
Individual Work Releases will be prepared and processed as described in
Section H.3.0, Work Release Procedures. Planning and reporting
requirements will also be described in each individual Work Release.

**1.1.0 Traffic Management System (TMS)**. A program to upgrade present
flow control system into a fully integrated traffic management system
which will operate at the national level through the Central Flow
Control Function (CFCF) at FAA headquarters and at the local level
through traffic management units (TMU) in each ARTCC and designated
Level V terminals. En route metering will provide software which will
aid controllers in routing traffic into terminal area at an acceptable
rate. (21‑06)

**1.1.1 Scope of F&E Work**. Provide site preparation and installation
required to accomplish Phase II efforts. Phase III efforts will involve
enhancements to Phase II capabilities.

**1.2.0 Voice Switching and Control Systems (VSCS)**. Implementation of
a system to provide the flexible communication operations needed to
complement sector suite flexibilities in Air Route Traffic Control
Centers (ARTCCs)/Area Control Facilities (ACFs). (21‑11)

**1.2.1 Scope of F&E Work**. Provide Technical Onsite Representative
(TOR). Provide for installation of uninterruptible power to turnkey
equipment. Provide site preparation (raised floor, power, air
conditioning, raceways, etc.).

**1.3.0 Advanced Automation System (AAS)**. A new Air Traffic Control
(ATC) automated system that includes controller work stations, software,
processors, and associated equipment. AAS is to be implemented in
phases, beginning with the Peripheral Adapter Module Replacement Item
(PAMRI), Initial Sector Suite System (ISSS), followed by Terminal
Advanced Automation System (TAAS), and AAS Central Computer Complex
(ACCC) at ARTCCs. Along with TAAS, the Tower Control Computer Complex
(TCCC) will be implemented at Airport Traffic Control Towers (ATCT).
(21‑12)

**1.3.1 Scope of F&E Work**. Site preparation at ARTCCs and ATCTs,
including renovation and/or construction to accommodate AAS processors,
controller work stations, and associated equipment. Prepare training
facility areas. Remove equipment and renovate equipment rooms. For
ATCTs, work may include support of installation, integration, test, and
shakedown of ATC systems.

**1.4.0 Area Control Facilities (ACF)**. Consolidation of en route and
terminal functions into a common Area Control Facility. (21‑15)

**1.4.1 Scope of F&E Work**. Primary efforts post‑1995. Phase I
(Pre‑ACF) activities are contained in other programs, e.g.,
installation/commissioning of AAS, ARTCC building expansions,
ATCT/TRACON establishment/replacement, new communications networks, new
airport facilities, etc.

**1.5.0 ARTS IIA Interface with Mode-S/ASR-9**. Develop and implement
the necessary hardware and software modifications to allow ARTS IIA to
accept Mode‑S and ASR-9 sensor data. (22‑09)

**1.5.1 Scope of F&E Work**. Installation of modification kits plus
cables and software. Participation in testing efforts.

**1.6.0 Terminal Voice Switch Replacement (TVSR)**. A modern voice
communications switch and control system to accommodate future tower
construction and modernization. (22‑12)

**1.6.1 Scope of F&E Work**. Provide TOR. Provide cable raceways for
turnkey equipment, required power and panels.

**1.7.0 ATCT/TRACON Establishment, Replacement and Modernization**. The
establishment, replacement or modernization of Airport Traffic Control
Towers (ATCT\'s) or Terminal Radar Approach Control facilities
(TRACON\'s) as needed to meet operational requirements. (22‑13)

**1.7.1 Scope of F&E Work**. Varied degree of effort, dependent on scope
of work; i.e., to establish, relocate or modernize towers, add operating
positions, restore old sites, environmental remediation, etc.

**1.8.0 Establish Flight Service Automation System (FSAS)**. Replacement
and consolidation of existing manual Flight Service Stations (FSSs) and
enhancement of Model 1, Automated Flight Service Stations (AFSSs) into
Model 2 AFSSs. (23‑01)

**1.8.1 Scope of F&E Work**. Prepare ARTCCs and FSSs space to receive
FSAS equipment and software. Provide RE and/or TOR. Remove and dismantle
equipment at existing manual FSSs. Provide site preparation for and
installation of engine generator, consoles, power distribution, etc.
Consolidate, relocate, or install new equipment at the FSS. Plant site
preparation and/or environmental remediation may be required.

**1.9.0 Central Weather Processor (CWP)**. The automation of
weather‑data processing and dissemination of real‑time weather to
meteorologists and controllers. (23‑02)

**1.9.1 Scope of F&E Work**. Provide site preparation for turnkey
electronics, e.g., power, cables, ducts, etc. Provide TOR. Participate
in system integration and checkout.

**1.10.0 Weather Message Switching Center (WMSC) Replacement**.
Replacement of WMSC equipment with state‑of‑the‑art equipment. WMSC
replacement processors and related peripherals will be located at each
of the two National Airspace Data Interchange Network (NADIN) switch
sites, Salt Lake City and Atlanta. (23-04)

**1.10.1 Scope of F&E Work**. Site preparation, e.g., power, cables,
etc. Provide TOR at two NADIN Switch sites, Salt Lake City and Atlanta.
Restoration work at Kansas City National Communications Center (NATCOM),
the present WMSC area.

**1.11.0 Aeronautical Data-Link (ADL)**. The interface between Mode-S
equipped aircraft and weather information and ATC services resident in
the NAS. (23‑05)

**1.11.1 Scope of F&E Work**. Minimal site preparation for turnkey,
e.g., power, ducts, etc. To be installed at each ARTCC, FAA Technical
Center and Academy. Provide TOR.

**1.12.0 Automated Weather Observing System (AWOS)**. Installation of
automated systems used to observe, read, send, determine, warn, or
display parameters related to weather conditions at airports or FAA
facilities. Also includes connection to and installation of AWOS data
acquisition system (ADAS) at ACFs. (23‑09)

**1.12.1 Scope of F&E Work**. Provide site survey, site preparation,
involvement and drawings (plan views). Provide power and communications
availability.

**1.13.0 Integrated Communications Switching System (ICSS)**.
Implementation of integrated telephone/radio services,
computer‑controlled circuit reconfiguration and other advanced features.
(23‑13)

**1.13.1 Scope of F&E work**. Site preparation for ICSS and other
communications equipment. May be combined with ATCT/TRACON modernization
projects. Type 2 system (large TRACONS 16 to 80 positions) may be
implemented as part of ACF program.

**1.14.0 Communication Facilities Consolidation/Network**. Consolidation
of remote communications outlets into a lesser number and dismantling of
unused facilities. (24‑02)

**1.14.1 Scope of F&E Work**. Establishment of Remote Communications
Facilities (RCFs) by location; collocation of equipment and
modernization of existing facilities. Site preparation of some new
locations (buildings) may be required. Scope of work determined on an
individual case-by-case basis. Includes dismantling old facilities.

**1.15.0 VORTAC Program**. Relocation, conversion, addition or deletion
of VORTAC facilities. VORTAC facilities include VOR, DVOR, VOT, and DME.
(24‑03)

**1.15.1 Scope of F&E work**. Accomplishment of modifications required
to prepare for turnkey. Replacements, relocations, deletions and
establishments will be generated as part of the VORTAC networking plan.

**1.16.0 Microwave Landing System (MLS)**. Phase 1 is the establishment
of approximately 464 MLS\'s as a more flexible replacement for the ILS.
MLS phase 2 is included in the CIP as project 34-07. (24‑07)

**1.16.1 Scope of F&E Work**. Provide data for environmental impact
assessments/statements; provide Resident Engineers (RE\'s) and/or
TOR\'s. Where power is not readily available on an individual
case‑by‑case basis, may have to provide power/transformers to point
where turnkey contractor picks up installation efforts.

**1.17.0 Runway Visual Range (RVR)**. Upgrade and establish RVR
equipment at airports to provide a standard real‑time method of
measuring visibility along runways in support of precision approaches.
(24‑08)

**1.17.1 Scope of F&E Work**. Site selection and preparation, power and
control cabling, and equipment installation and test.

**1.18.0 Visual NAVAIDS (VISAIDS)**. The implementation, improvement,
retrofit, or standardization of lighting systems used for visual
guidance at airports. (24‑09)

**1.18.1 Scope of F&E Work**. Involves MALSR, REIL, VASI, PAPI and
ODALS. Includes site selection, site preparation, equipment installation
and adjustment, and flight check.

**1.19.0 Direction Finder (DF)**. The establishment, relocation, and
upgrading of DF equipment to provide expanded and improved coverage.
(24‑11)

**1.19.1 Scope of F&E Work**. Replace tube‑type equipment with
solid‑state equipment. Results of networking studies will generate
relocates/collocates and establishments requirements. Perform
environmental studies, surveys, site preparations and electronics
installations. Provide RE/TOR.

**1.20.0 Terminal Radar (ASR) Program**. The replacement of all tube
type 4/5/6 Radar Systems with solid‑state systems. May involve the
replacement of solid‑state ASR‑7/8 equipment with ASR‑9s at selected
locations and the subsequent reinstallation of the replaced ASR‑7/8s at
ASR‑5/6/7 locations (Leapfrog Program), as well as the direct
replacement of ASR‑4/5/6 facilities at selected locations with ASR‑9
equipment. Also includes the relocation of ATC Beacon interrogator
(ATCBI‑5) equipment as required and the establishment of additional ASR
facilities as required. (24‑13)

**1.20.1 Scope of F&E Work**. At ASR‑4/5/6 sites accomplish site
preparation required to receive ASR‑9 equipment, using existing building
and power. For leapfrog ASR‑4/5/6 sites receiving ASR‑7/8 systems,
perform total regional effort (electronics and plants) to install new
equipment in the existing buildings. ATCBI relocations may be included.
May include removal and disposal of ASR 4/5/6 equipment and
refurbishment of ASR-7/8 equipment.

**1.21.0 Long Range Radar (LRR) Program**. Upgrades older radar,
procures new ARSR‑4 radars and relocates ARSR‑3 equipment removed from
old sites, and the modernization of tube-type LRR systems. Also provide
for expansion of joint use military radar to supplement existing
coverage in the en route air space. (24‑15)

**1.21.1 Scope of F&E Work**. Accomplish required rehabilitation of
buildings, towers, roads, equipment, etc. Installation of the
electronics/antenna systems are planned for accomplishment by turnkey
contract. Mobile Emergency Radar Facilities (MERF) installations may be
required for in‑service change out. Relocate equipment required to
effect in‑service change out. Some site relocates may be required. If
so, prepare environmental documentation and all work necessary to
prepare new site for turnkey installation.

**1.22.0 Weather Radar Program**. Provide a nationwide network Next
Generation Weather Radar (NEXRAD) for en route and terminal Doppler
weather radar capable not only of aircraft detection, but for providing
real‑time weather information to meteorologists, controllers, FSS
specialists and pilots. (24‑16)

**1.22.1 Scope of F&E Work**. Provide packages for interface with CWPs.
Locate and accomplish site preparation, provide roads, power, grading,
and environmental impact assessment, etc.

**1.23.0 Terminal Doppler Weather Radar (TDWR)**. TDWR will provide
warnings of hazardous weather conditions, especially wind shear and
microburst. (24-18)

**1.23.1 Scope of F&E Work**. Provide for site selection, site
preparation, power, and environmental impact assessments, and construct
roads, etc. for turnkey installation of TDWR equipment. Provide
TORs/REs.

**1.24.0 Data Multiplexing (DMN) Network**. Installation, integration,
and testing of high‑speed MUX modems, discrete multiplexers, a network
management system, automation calling equipment and associated
equipment, in order to achieve lower leased‑line costs, higher
reliability and increased data capacity. (25‑02)

**1.24.1 Scope of F&E Work**. Provide site preparation for and
installation of multiplexing equipment at ARTCCs, radars, terminal
facilities and FSAS/FSDPS facilities.

**1.25.0 Radar Microwave Link (RML) Replacement and Expansion**.
Replacement of existing hybrid of FAA‑owned and leased landlines, radio
links and satellite media with a national area transmission system
utilizing Radio Communication Link (RCL) equipment. (25‑03)

**1.25.1 Scope of F&E Work**. Remove existing equipment, including
engine generators and Power Conditioning Systems (PCS\'s). Based on
national network design, accomplish site surveys and preparation,
construct roads, provide power, conduct environmental assessments,
construct/rehabilitate buildings, towers, etc. Provide TORs/REs. Provide
site preparation required for turnkey installation.

**1.26.0 Radio Control Equipment (RCE)**. Replacement of existing
signaling/tone control equipment with standardized modular digital
remote control equipment for ARTCCs/RCAGs, FSSs/RCOs and ATCTs/RTRs
application and associated remote facilities. (25‑08)

**1.26.1 Scope of F&E Work**. Accomplish site preparation for
replacement of present signaling tone control equipment with
standardized modular remote control equipment at ARTCC, ATCT/TRACON,
FSS, RCAG, RCO, and RTR facilities.

**1.27.0 Remote Maintenance Monitoring System (RMMS)**. Establishment of
a system to enable maintenance, monitoring, control, and certification
accomplishment from a central location. Consisting of processors,
software, concentrators, and consoles. (26‑01)

**1.27.1 Scope of F&E Work**. Prepare space, power, grounding as
required. Provide TOR for turnkey installation of En Route and General
NAS Sector MPS\'s and MPS enhancements.

**1.28.0 Maintenance Control Center (MCC)**. Establishment of work
centers for performing routine maintenance, system monitoring, and
dispatching personnel for necessary on‑site maintenance. (26‑04)

**1.28.1 Scope of F&E Work**. Locate adjacent to Maintenance Processor
System (MPS). Fabricate desk, partitions, etc. at General NAS (GNAS)
Sectors and as required, at ARTCC Sectors.

**1.29.0 ARTCC Building Modernization**. Provides for ARTCC facility
rehabilitations/expansions, HVAC improvements, asbestos control, wiring
replacement, and security, grounds, roofing, and other upgrades. (26-09)

**1.29.1 Scope of F&E Work**. Accomplish work effort coordination, site
preparation and other activities required for HVAC replacement,
refurbish interiors, asbestos control, OSHA compliance, security
enhancements, energy conservation, upgrading roads, grounds, parking
lots, reroofing, and etc. to modernize the ARTCCs.

**1.30.0 Provide ARTS IIIE Upgrades for Select Air Traffic Facilities**.
Provides upgrades at selected ARTS IIIA facilities to accommodate growth
in air traffic and continue the present levels of air traffic control
services and reliability until implementation of the AAS. This project
will implement an enhanced system architecture based on proven
hardware/software upgrades provided to the New York TRACON. (32-04)

**1.30.1 Scope of F&E Work**. Installation of modification kits plus
cables and software. Participation in testing efforts.

**1.31.0 Expand ARTS IIA Capacity and Provide MCI Capability**. Provides
more ARTS IIA peripheral proces­sors to support increases in aircraft
tracking and transponder equipage, and the addition of Mode C Intruder
capability. (32-06)

**1.31.1 Scope of F&E Work**. Installation of modification kits plus
cables and software. Participation in testing of modified systems.

**1.32.0 Enhanced Terminal Voice Switch (ETVS)**. A new generation of
communication switches to meet the ATC requirements in the terminal
area. The ETVS will provide access to air/ground and ground/air
facilities and interface to AAS, backbone networks. (32-12)

**1.32.1 Scope of F&E Work**. Provide TOR. Provide raceways for turnkey
installed equipment, required power and panels. (Requirements may change
as project develops.)

**1.33.0 ATCT Establishment**. Establishes terminal air traffic control
services at new ATC facilities and provides for FAA assumption of
ownership and maintenance of selected sponsor‑owned towers. (32-13)

**1.33.1 Scope of F&E Work**. Varied degree of effort, dependent on type
of tower to be established, may include site selection, site preparation
for national designed tower, environmental and economic studies,
electronic equipment test, installation and/or relocation, provide
REs/TORs, etc.

**1.34.0 Establish/Expand Digital BRITE**. Acquire additional Digital
Bright Radar Indi­cator Tower Equipment (DBRITE) to establish radar
displays and interface capabilities for satellite ATCTs that do not have
radar. Systems will also be provided to expand service at those sites
currently operational with DBRITE. (32-16)

**1.34.1 Scope of F&E Work**. Expand DBRITE systems, install display
systems for satellite ATCT\'s which do not have ATC radar information
available.

**1.35.0 Expand ARTS IIIA Capacity and Provide Mode C Intruder (MCI)
Capability**. Provides additional ARTS IIIA input/output processors to
support increases in aircraft tracking and transponder equipment,
including the addition of a Mode-C Intruder capability. (32-20)

**1.35.1 Scope of F&E Work**. Installation of modification kits plus
cables and software. Participation in testing efforts.

**1.36.0 Dallas/Fort Worth Metroplex**. Provides for the establishment,
expansion, and modernization of FAA facilities and equip­ment needed to
increase capacity and efficiency of aircraft operations at new/expanded
commercial service airports in the Dallas/Fort Worth area. (32-22)

**1.36.1 Scope of F&E Work**. Installation of equipment in new tower
and/or TRACON, provide: power, cables, raceways, integration testing and
system shakedown.

**1.37.0 Establish New Chicago TRACON Facility**. Establish a new
Chicago Terminal Radar Ap­proach Control facility away from O\'Hare
Airport. (32-24)

**1.37.1 Scope of F&E Work**. Prepare new TRACON for installation of
equipment, may include installation and test of equipment in new TRACON,
provide: power, cables, raceways, integration testing and system
shakedown.

**1.38.0 Southern California TRACON (SCT)**. The SCT involves
consolidation of five Southern California ARTS III TRACONs into a common
facility located in San Diego, California. (32-26)

**1.38.1 Scope of F&E Work**. Installation of consoles and associated
equipment, provide: power, cables, raceways, integration testing and
system shakedown.

**1.39.0 DOD/FAA ATC Facility Transfer/Modernization**. Provide for the
transfer of operations of several DOD approach control facilities into
existing FAA facilities; consolidation of other DOD approach con­trol
facilities into ACFS; and modernization of the Guam combined center
radar approach control and the Edwards AFB radar approach control
facilities. (32-27)

**1.39.1 Scope of F&E Work**. Varied degree of effort, dependent on
individual site requirements, i.e., site survey to determine efforts
necessary to transition or upgrade DOD operational facilities for use in
civil ATC operations. Perform environmental studies, electronic
equipment installation and test.

**1.40.0 DOD Base Closures**. Public Law provides for closure of
numerous military establishments. A number of these establishments
provide civilian ATC functions and will require the FAA to assume air
traffic control services of the affected airspace. This will require FAA
to equip and upgrade these facilities for civilian use. (32-28)

**1.40.1 Scope of F&E Work**. Varied degree of effort, dependent
individual site requirements, i.e., site survey to determine efforts
necessary to transition DOD operational facilities into FAA civilian air
traffic operations. Perform environmental studies, electronic equipment
installation and test.

**1.41.0 Establish Additional Radar Positions**. Install necessary
equipment at automated Level IV and V TRACONs that will provide
addi­tional terminal radar approach control services to meet increased
capacity requirements. Replaced older equipment will be refurbished and
redis­tributed for reuse at other ARTS facilities. (32-29)

**1.41.0 Scope of F&E Work**. Installation of additional displays,
provide power, cables, ducts, etc. Provide TOR, participate in system
integration and checkout.

**1.42.0 AFSS Support Space**. This project provides additional
Automated Flight Service Station operational support space at multiple
AFSS locations, and addresses deficiencies in power, heating, venting,
and air conditioning (HVAC) systems. (33-20)

**1.42.1 Scope of F&E Work**. Varied degree of effort, dependent on
individual site requirements, i.e., to add power, HVAC, prepare space
for operational use, add operating positions, etc. Provide REs and/or
TORs.

**1.43.0 Establish Locator Outer Markers (LOM)**. Provides additional
off‑the‑shelf LOMs using a nondirectional beacon for existing and
planned instrument landing system installations. These systems provide
fixes and transition routes for ILS approaches. (34-04)

**1.43.1 Scope of F&E Work**. Site selection and preparation, power and
control cabling, equipment installation, and checkout.

**1.44.0 Instrument Landing System (ILS)**. Additional ILSs will be
acquired for upgrading existing or establishing new systems. These new
systems will provide precision approach guidance for aircraft until
transition to the microwave landing system is accomplished. (34-06)

**1.44.1 Scope of F&E Work**. Site selection and preparation, power and
control cabling, equipment installation, and checkout.

**1.45.0 Microwave Landing System (MLS) ‑ Production Phase II**. Phase
II of the MLS program (see project 24‑07 for Phase 1) will provide an
MLS at each ILS site and additional systems for qualifying locations.
(34-07)

**1.45.1 Scope of F&E Work**. Site selection and preparation, power and
control cabling, equipment installation, and checkout.

**1.46.0 Runway Visual Range (RVR) Establishment**. RVR systems will be
acquired for locations with increased operations and new locations
arising from the construction of airports, runways, and runway
extensions. (34-08)

**1.46.1 Scope of F&E Work**. Site selection and preparation, power and
control cabling, equipment installation, and checkout.

**1.47.0 Establish Visual Navaids for New Qualifiers**. This project
will provide lighting systems (e.g., MALSR, ALSF‑2, REIL, PAPI, or
ODALS) and remote radio control equipment at airports to meet air
traffic requirements, new airport estab­lishments, and new runway
construction. (34-09)

**1.47.1 Scope of F&E Work**. Involves MALSR, REIL, VASI, PAPI, and
ODALS. Includes site selection and preparation, power and control
cabling, equipment installation, and flight check.

**1.48.0 Air Traffic Control Beacon Interrogator (ATCBI)**. ATCBI units
will be acquired to established required surveillance capability at
newly qualifying ATC facilities. (34-12)

**1.48.1 Scope of F&E WORK**. Site selection and preparation, provide
roads power and environmental assessments. May be in conjunction with
establishment of primary radar.

**1.49.0 Terminal Radar Digitizing, Replacement, and Establishment**.
Provides digitized radar data for use with AAS equipment. Digitized
radar will also be provided for terminals which require radar
replacement and for those terminals expected to qualify for radar
approach control by the year 2000. (34-13)

**1.49.1 Scope of F&E Work**. Provide for interface with AAS equipment
and change out of analog type equipment as required.

**1.50.0 Additional Airport Surface Detection Equipment (ASDE)
Establishment**. ASDE pro­vides surveillance of aircraft and ground
vehicles on the airport surface. This project will acquire and install
additional ASDE radars with runway incur­sion detection capability at
high‑activity airports. (34-14)

**1.50.1 Scope of F&E Work**. Prepare ATCT for installation of ASDE
equipment on top of tower cab. In some instances remote towers may be
required. Install and test ASDE equipment.

**1.51.0 Surveillance System Enhancements**. This project will improve
the timing, tracking, and display of aircraft position data and the
orderly transition of the ATC system from the present configuration to
the ACF environment. (34-20)

**1.51.1 Scope of F&E Work**. Project under development.

**1.52.0 Communications Facilities Expansion**. This project will
establish additional remote communications capabilities by expanding,
relocating, or establishing new remote communications facilities.
(34-23)

**1.52.1 Scope of F&E Work**. Involves RCAGs, RCOs, and RTRs. Includes
site selection and preparation, power and control cabling, equipment
installation, and checkout.

**1.53.0 National Airspace Data Interchange Network (NADIN) II
Continuation**. This project will provide for Phase II growth to the
National Airspace Data Interchange Net­work II Packet Switched Network
(PSN) which supports new requirements for network expansion/enhancement
not covered under NADIN Phase I. (35-07)

**1.53.1 Scope of F&E Work**. Site preparation, e.g., power, cables,
etc. to support Network Control Centers (NCCs) at Atlanta and Salt Lake
City, and support node and packet switches at the 20 conus ARTCCs, the
NY TRACON and other sites. Provide TOR at two NADIN NCCs sites, Salt
Lake City and Atlanta.

**1.54.0 Interfacility Data Transfer System for Edwards AFB RAPCON**.
This project provides for development of systems software that will
support interfacility data transfer between Edwards AFB and the Los
Angeles ARTCC. (35-20)

**1.54.1 Scope of F&E Work**. Installation of modification kits plus
cables and software. Participation in system integration and testing.

**1.55.0 ARTCC/ACF Support Space**. Additional ARTCC/ACF space is
required to accommodate increased staffing levels and func­tional
requirements. These additions will resolve shortfalls within the current
ARTCC facilities and provide for future space requirements as TRACON
consolidation occurs. (36-20)

**1.55.1 Scope of F&E Work**. Reconfiguration of existing space in the
ARTCCs to accommodate future ATC operational consolidations and
equipment installations.

**1.56.0 ATCT/TRACON Modernization**. Modernizes terminal facilities by
increasing tower cab height to improve visibility, replacing obsolete
equipment, and rehabilitating space in support of growth and expansion.
(42-13)

**1.56.1 Scope of F&E Work**. Varied degree of effort, dependent on
scope of work required to modernize towers, add operating positions,
restore older equipment, etc.

**1.57.0 ATCT/TRACON Replacement**. Replaces facilities that have
exceeded their economic life cycle with air safety enhancements to meet
operational requirements. (42-14)

**1.57.1 Scope of F&E Work**. Provide site preparation for and
installation of engine generator, consoles, power distribution, etc.
Consolidate, relocate, or install new equipment at the ATCT. Plant site
preparation may be required.

**1.58.0 Sustain San Juan Facilities**. Replaces/upgrades the Combined
Center Radar Approach Control (CERAP) operation until consolidation into
an ACF. Also upgrades the IFSS to an automated IFSS. (42-22)

**1.58.1 Scope of F&E Work**. Replace/upgrade engine generator,
consoles, power distribution, and consolidate, relocate, or install new
equipment at the CERAP.

**1.59.0 National Graphic Weather Display System (GWEDS)**. Provide a
uniform near real-time GWEDS capability at Automated Flight Service
Stations for timely dissemination of weather information and flight
hazards to pilots.

**1.59.1 Scope of F&E Work**. Project F&E work definition and schedule
under development.

**1.60.0 Meteorological Weather Processor (MWP) II**. This project will
extend the current level of service and performance and availability.
MWP II will add new capabilities and enhancements.

**1.60.1 Scope of F&E Work**. Projected F&E work definition and schedule
under development.

**1.61.0 Provide FSAS Power Conditioning Systems**. Provides power
conditioning equipment and battery backup at AFSSs to improve power
avail­ability. (43-03)

**1.61.1 Scope of F&E Work**. Site preparation for installation of power
conditioning system, may require installation or replacement of older
standby power systems to allow PCS to operate efficiently.

**1.62.0 FSAS Computer Replacement**. Develops the requirements and
procurement methodology for replacement of current flight service
automation system equipment. (43-04)

**1.62.1 Scope of F&E Work**. Site preparation at FSDPS, AWP, and AFSS
sites to accommodate replacement of current computer systems. Remove
equipment, renovate equipment rooms, may also include installation and
system shakedown testing.

**1.63.0 Upgrade Low Level Windshear Alert System (LLWAS) to Expanded
Network Configuration**. Significantly increases the effectiveness of
the LLWAS by integrating LLWAS with TDWR when both sensors are
collocated, and by evaluating ice‑free LLWAS sensors. (43-12)

**1.63.1 Scope of F&E Work**. For new LLWAS installations; provide site
selection and preparation, environmental assessments as required,
install towers/poles, provide power to tower/poles, ATCT wiring from
master stations to TRACON and tower cab. For existing sites; prepare for
replacement of existing sensors and provide for increasing the number of
sensor at some airports.

**1.64.0 A/G Communication Radio Frequency Interference (RFI)
Elimination**. Provides selected Remote Communication Facilities (RCFs)
with modern Air/Ground radio equipment and ancillary equipment to
improve operational performance and resolve RFI problems. (44-03)

**1.64.1 Scope of F&E Work**. Accomplishment of modifications required
to eliminate crowded antenna conditions, reduce RFI problems, and
replace older communications equipment. Relocations, deletions, and
establishments will be generated as part of the RFI Elimination Plan.

**1.65.0 A/G Radio Replacement**. Provides remote communications
facilities with modem radio transmitter, receiver, and transceiver
equipment to ensure the integrity of air/ground voice communications.
(44‑04)

**1.65.1 Scope of F&E Work**. Prepare site to receive new generation of
communications equipment, remove older equipment, install check and test
new equipment.

**1.66.0 Interim Backup Emergency Communications (BUEC) Improvement**.
Provides additional BUEC equipment at ARTCCs in response to expanded Air
Traffic requirements. (44‑05)

**1.66.1 Scope of F&E Work**. Accomplish site preparation for new
generation of communications equipment, remove old equipment install,
checkout, and test new equipment.

**1.67.0 Emergency Transceiver Replacement**. Replaces obsolete
emergency transceivers at ATCTs and TRACONs. (44‑07)

**1.67.1 Scope of F&E Work**. Prepare site to receive new generation of
communications equipment, remove older equipment, install, check, and
test new equipment.

**1.68.0 Low‑Power TACAN Antennas**. Replaces obsolete Tactical Air
Navigation (TACAN) antennas with low‑power antennas which can op­erate
from a backup battery, eliminating the need for engine generator backup
power. (44‑12)

**1.68.1 Scope of F&E Work**. Remove old mechanical TACAN antenna
install new solid state antennas, at most sites, remove engine
generator, fuel tank, perform environmental clean up of the site as
necessary, install battery backup power system.

**1.69.0 Sustain VOR/VORTAC**. Enhances second generation technology to
permit VORTAC to meet NAS operational requirements. (44-14)

**1.69.1 Scope of F&E Work**. Install Remote Maintenance Monitoring
(RMM) retrofit kits and TACAN battery backup modification kits, checkout
and test modifications.

**1.70.0 AN/GRN‑27 ILS Replacement**. Replaces the current AN/GRN‑27
Instrument Landing Systems which have severe logistics sup­port problems.
Replacement units will have RMM capabilities. (44-20)

**1.70.1 Scope of F&E Work**. Accomplish site preparation for
replacement of Instrument Landing System equipment with new generation
ILS equipment at existing locations. Install, checkout, and assist in
flight test of new ILSs.

**1.71.0 Wilcox CAT II/III ILS Replacement**. Replaces all obsolete
Wilcox CAT II/III Instrument Landing System units with equipment which
will have an embedded RMM capability. (44-21)

**1.71.1 Scope of F&E Work**. Accomplish site preparation for
replacement of existing ILS equipment with new generation of equipment
at existing locations. Install, checkout and assist in flight test of
new ILSs.

**1.72.0 Replace Mark IA/lB/lC ILS**. Replaces Mark IA, IB, and IC
Instrument Landing Systems which have maintenance and support problems.
(44-22)

**1.72.1 Scope of F&E Work**. At CAT I Mark IA site accomplish site
preparation for replacement of existing ILSs with new generation
equipment. Install checkout and assist in flight test of new ILSs.

**1.73.0 Takeover of AIP/ADAP Funded Non‑Federal ILS and Associated
Equipment**. Public law takeover of AIP/ADAP funded Instru­ment Landing
Systems. Nonstandardized systems are to be modified for inclusion into
the FAA inventory. (44‑23)

**1.73.1 Scope of F&E Work**. These facilities usually require extensive
refurbishment to meet FAA standards due to improperly buried cables,
construction of light supports and sizing of engine generators and other
features. Installation of modification, checkout, and flight testing
will be required.

**1.74.0 ILS and Visual Navaids Engineering and Sparing**. Provides
continued engineering support of deployed Instrument Landing Systems and
visual navaids. Also replaces all localizer Traveling Wave Antennas
(TWAs) and associated radio frequency distribu­tion networks. (44-24)

**1.74.1 Scope of F&E Work**. Replace Localizer antenna arrays with new
antennas under development.

**1.75.0 RVR Replacement**. Replacement of obsolete Tasker 500 Runway
Visual Range systems. (44‑29)

**1.75.1 Scope of F&E Work**. Prepare site to receive new generation of
RVR equipment, remove older equipment, install, checkout, and test new
equipment.

**1.76.0 Sustain DME**. Replaces outdated Distance Measuring Equipment
collocated with ILS and terminal NDBs with modern units which have RMM
capa­bility. (44‑30)

**1.76.1 Scope of F&E Work**. Prepare site to receive new generation of
DME equipment, remove older equipment, install checkout and test new
equipment.

**1.77.0 Replace Type FA9964 Direction Finder (DF)**. Replaces obsolete
FA9964 DF systems in Automated Flight Service Stations. (44‑31)

**1.77.1 Scope of F&E Work**. Prepare site to receive new generation of
DF equipment, remove older equipment, install checkout and test new
upgraded solid state equipment.

**1.78.0 Airport Lighting System Improvement Program (ALSIP)
Continuation**. The ALSIP continues the retrofit of runway lights with
low‑impact, frangible approach light sup­ports. (44‑33)

**1.78.1 Scope of F&E Work**. Involves site preparation, removal and
disposal of existing equipment, installation of replacement equipment,
system adjustments and assist in flight check.

**1.79.0 LORAN‑C Monitors and Transmitter Enhancements**. Modifies Long
Range Navigation signal monitors to recognize new midcontinent gap
transmitters, relocates some units to maximize system capability, and
enhances monitors to upgrade performance. (44‑35)

**1.79.1 Scope of F&E Work**. Installation and check of modification
kits at existing sites. For relocation sites; perform site selection and
preparation, install power and control cabling, accomplish equipment
installation, and checkout.

**1.80.0 Sustain/Relocate ARSR**. Relocates long range Air Route
Surveillance Radars to enhance and improve airspace coverage to meet Air
Traffic requirements. (44‑39)

**1.80.1 Scope of F&E Work**. Accomplish required rehabilitation of
buildings, towers, roads, and/or electronic equipment. Install
modification kits. At relocation sites prepare environmental
documentation and all work necessary to prepare site for installation of
relocated radar. Mobile Emergency Radar Facilities (MERF) installations
may be required for in‑service change out. Relocate equipment required
to effect in‑service change out.

**1.81.0 Long Range Radar Improvements**. Improves the current inventory
of long range radars by extending their useful life. (44-40)

**1.81.1 Scope of F&E Work**. Accomplish required rehabilitation of
buildings, towers, roads, clean up cable trays, correct grounding
problems, etc., install modification kits.

**1.82.0 Long Range Radar Radome Replacement**. Replaces obsolete
radomes at long range radar sites and those radomes that are not
compatible with Mode-S antennas. (44‑42)

**1.82.1 Scope of F&E Work**. Remove and dispose of old radome and
install new Mode-S compatible radome.

**1.83.0 Radar Pedestal Vibration Analysis**. Provides vibration
monitoring sensors on radar pedestals and vibration analysis equipment
to analyze the monitored data. (44‑43)

**1.83.1 Scope of F&E Work**. Install vibration monitoring sensors on
radar pedestals.

**1.84.0 Air Traffic Control Radar Beacon System (ATCRBS) Relocation**.
Provides relocation of the newer ATCBI sys­tems replaced by Mode-S or the
ASR‑9 optional systems at sites that currently use the tube‑type ATCBI‑3
as well as certain RBPM locations. (44‑45)

**1.84.1 Scope of F&E Work**. Prepare environmental documentation and
all work necessary to prepare site for installation of relocated ATCBI
equipment. Provide for relocate of equipment required to accomplish
in‑service change out. Mobile Emergency Radar Facilities (MERF)
installations may be required for in‑service change out.

**1.85.0 Air Traffic Control Beacon Interrogator (ATCBI) Replacement**.
Replaces aging and obsolete ATCBI equip­ment with Mode-S compatible units
to establish a complete secondary radar system. (44‑46)

**1.85.1 Scope of F&E Work**. At ATCBI‑3/4/5 sites accomplish site
preparation required to receive replacement beacon equipment, using
existing building and power. Actual equipment configuration will depend
upon results of the MODE-S alternative study.

**1.86.0 AN/FPS‑117 Beacon Improvement**. Improves beacon performance of
USAF FPS‑117 minimally attended radar systems in Alaska to allow use of
Air Traffic separation stan­dards. (44‑48)

**1.86.1 Scope of F&E Work**. Install modifications and upgrade kits to
existing AN/FPS-117 military radar equipment to bring to FAA standards.

**1.87.0 Sustain/Relocate ASR**. Relocates and refurbishes terminal
Airport Surveillance Radars after initial deployment due to new
construction or changes in air traffic volume. (44‑60)

**1.87.1 Scope of F&E Work**. Accomplish required rehabilitation of
buildings, towers, roads, etc., install modification kits. At relocation
sites prepare environmental documentation and all work necessary to
prepare site for installation of relocated radar. Mobile Emergency Radar
Facilities installations may be required for in‑service change out.
Relocate equipment required to achieve in‑service change out.

**1.88.0 DMN Continuation**. Continues and completes Phase III of the
Data Multiplexing Network effort to provide circuit ­end equipment for
data transmission requirements. (45-02)

**1.88.1 Scope of F&E Work**. Provide site preparation for and
installation of multiplexing equipment at ARTCC\'s, radars, terminal
facilities and FSAS/FSDPS facilities.

**1.89.0 Expansion/Reconfiguration of Low Density Radio Communications
Link (LDRCL)**. Provides the interfacility communications system with
the ability to establish a microwave LDRCL to support new NAS
requirements not previously covered under the RML replacement program.
(45‑05)

**1.89.1 Scope of F&E Work**. Based on RML network design,
accomplish‑site surveys and preparation, roads, power, environmental
assessments, buildings, towers, etc. Provide TORs/REs.

**1.90.0 Expansion/Reconfiguration of Routing and Circuit Restoral
(RCR)**. This project continues the modernization of digital switching
and multiplexing equipment to restore and reroute critical NAS voice and
data services. (45‑06)

**1.90.1 Scope of F&E Work**. Provide site preparation and installation
of RCL nodes in ARTCCs.

**1.91.0 Critical Telecommunications Support**. Establishes resources
and provides equipment to reduce dependence on leased
telecommunica­tions, and implements FAA‑owned airport telecommunications.
(45‑20)

**1.91.1 Scope of F&E Work**. Accomplish site preparation and
installation of mini demarcation systems, automated line test equipment,
RCL drop and insertion equipment, NADIN IA memory enhancements and RCL
circuit diversity enhancements.

**1.92.0 Establish Alaska NICS (ANICS) Satellite Network**. Provides for
the establishment of an FAA owned, reliable, and cost effective Alaskan
region NAS Interfacility Communications System using satellite
technology. (45‑24)

**1.92.1 Scope of F&E Work**. Site selection and preparation to include
roads, power, buildings, towers and equipment installation, and checkout
of ground stations.

**1.93.0 Sustain RMMS**. Enhances the maintenance automation capability
by expanding the existing Remote Maintenance Monitoring System network,
replac­ing aging commercial off‑the‑shelf (COTS) components, and
upgrading existing maintenance automation software. (46‑01)

**1.93.1 Scope of F&E Work**. Project under development.

**1.94.0 MCC Enhancements**. Enhances/upgrades Maintenance Control
Centers in all Airway Facilities Sectors. Backup power to sustain sector
MCC operation during extended power outages will be added to the MCCs.
(46-04)

**1.94.1 Scope of F&E Work**. Project under development.

**1.95.0 Airport Cable Loop Systems Sustained Support**. Provides for
the continuance of the airport cable loop project by upgrading power and
signal distribution systems at Level III, IV, and V airports. (46‑05)

**1.95.1 Scope of F&E Work**. Work includes; trenching, adding/upgrading
duct banks, installation/replacement of signal and power cables on and
around airports.

**1.96.0 Power Systems Sustained Support**. Provides the optimum type
and quality of main and standby electrical power (and grounding) to
reduce electrical interference, operating cost, and energy consumption
at NAS facilities. (46‑07)

**1.96.1 Scope of F&E Work**. Refurbish, overhaul, and replace aging
power systems; including power conditioning systems, engine generators,
batteries and power switching equipment. Correct grounding problems and
other task to assure high quality reliable power.

**1.97.0 Modernize and Improve FAA Buildings and Equipment Sustained
Support**. Develops new standard facility designs for upgrading or
replacement of buildings and plant equipment which house and support NAS
naviga­tion, communications, surveillance, and visual/electronics landing
systems. (46‑08)

**1.97.1 Scope of F&E Work**. Accomplish various requirements for
rehabilitation or improvements of electrical systems, grounds, roads,
mechanical systems, HVAC, building roofs, structures, fencing, and other
appurtenances at other than ATCTs and ARTCCs.

**1.98.0 Sustain ARTCC/ACF Facilities**. Provides for rehabilitation or
replacement of various components of original ARTCC/ACF facilities as
they become obsolete or require refurbishment. (46‑09)

**1.98.1 Scope of F&E Work**. Accomplish coordination, site preparation
and other activities required for HVAC replacement, refurbish interiors,
asbestos control, OSHA compliance, security enhancements, energy
conservation, upgrading roads, grounds, parking lots, reroofing, and
etc.

**1.99.0 Continued General Support**. Provides continued general support
for NAS initiatives and activities. Included are regional originated
projects that respond to changing routes, hubbing, or airspace
resectorization, and small nonrecurring national programs not covered in
other CIP projects. (46-16)

**1.99.1 Scope of F&E Work**. This program includes local project,
regional originated projects and other projects not specifically
included in other CIP programs. Provide site preparation, equipment
installation, equipment relocation, general drafting, etc., on a
case-by-case basis. The accomplishment of OSHA and environmental
compliance type work, along with encapsulation of asbestos or asbestos
products may also be required.

**1.100.0 Fuel Storage Tanks**. Replaces/removes leaking underground
fuel storage tanks and provides monitoring of under­ground storage tanks.
(46‑22)

**1.100.1 Scope of F&E Work**. Remove, replace, dispose of, and provide
for monitoring of fuel storage tanks. Accomplish site cleanup and
decontamination of fuel storage sites.

**1.101.0 Environmental Cleanup**. Provides for the cleanup and removal
of all hazardous substances at contaminated FAA facilities. (46‑23)

**1.101.1 Scope of F&E Work**. Provide site investigation, site
assessment of environmental damages and accomplish removal and

restoration of site.

**1.102.0 ATCT Safety Upgrades**. Upgrades ATC tower facilities to
current OSHA life fire safety standards. (46‑26)

**1.102.1 Scope of F&E Work**. Accomplish modifications to existing
tower facilities to provide for OSHA and personnel safety compliance,
and asbestos encapsulation or removal.

**1.103.0 NAS Recovery Communication (RCOM)**. Ensures a capability
exists for a national FAA network of command and control communications
during national emergency if normal telecommunication between facilities
is interrupted. (46‑28)

**1.103.1 Scope of F&E Work.** Provides for National Radio
Communications System (NARACS) expansion and upgrade, which includes
replacement for existing NARACS hardware deemed obsolete or
unsupportable. Provides for continued expansion of the secure telephone
network.

**1.104 ARTS IIIA Peripheral Adapter Module (PAM) Modernization**. This
project modernizes the ARTS IIIA PAM by emulating its func­tions (IMT,
TTY, and ICA) with state‑of‑the‑art capability to enhance its efficiency
and support­ability. (52‑21)

**1.104.1 Scope of F&E Work**. Installation of modifications at ARTS
IIIA sites to replace the ARTS IIIA PAM.

**1.105.0 System Support Laboratory Sustained Support**. Provides
facilities and equipment at the FAA Technical Center for the test,
evaluation, and integration of new systems. (56‑17)

**1.105.1 Scope of F&E Work**. This project includes development of
test, evaluation and integration plans, participation in test at various
locations, collecting and analyzing data to verify systems under test
and evaluation meet total system requirements.

**1.106.0 General Support Laboratory Sustained Support**. Provides
facilities, equipment, aircraft, and general computer systems to support
engineering, development, and testing programs at the FAA Technical
Center. (56‑18)

**1.106.1 Scope of F&E Work**. Provides the necessary enhancements,
modifications or replacements to support the engineering, development,
and testing programs assigned to the Technical Center.

**1.107.0 Aeronautical Center Training and Support Facilities**. This
project provides training complexes and support buildings to house
facilities and equipment required to accomplish FAA training. It also
provides logistics and engineering support at the Aeronautical Center.
(56‑30)

**1.107.1 Scope of F&E Work**. Provide the necessary site adaption and
installation drawings and details to locate, install and test various
NAS systems and equipments in the space provided at the Aeronautical
Center.

**1.108.0 NAS Training**. Procures and installs modem training media,
automated training development systems, and communications equipment at
the FAA Academy. Also retrofits Academy classrooms, laboratories, and
work areas. (56‑35)

**1.108.1 Scope of F&E Work**. Provide the necessary construction
details and installation assistance to install training equipment and
instructional systems in classrooms, laboratories, and administrative
space.

**1.109.0 Logistics Support Systems and Facilities**. Provide responsive
life-cycle support to the FAA Logistics Center to identify
obsolete/deteriorated parts/equipment and provide additional material
handling and testing capability and replacement of the Logistics
Inventory system (LIS)/DCS equipment. Replacement of the mobile
facilities fleet is also planned. (56-37)

**1.109.1 Scope of F&E Work**. Provide the necessary layouts for the
installation of testbeds and related logistics support systems and
equipments, and perform installation of the systems and related
equipment to upgrade supply and material handling systems.

**1.110.0 Refurbish AN/FPS‑20 Radars**. Surplus military long‑range
surveillance radars will be removed and refurbished for subse­quent FAA
use. (56‑53)

**1.110.1 Scope of F&E Work**. Dismantle decommissioned U.S. Air Force
radars and prepare for shipment to the FAA Logistics Center for
refurbishment. Reinstall refurbished radars per the Long Range Radar
program.

**1.111.0 Provide FAA Housing**. This project provides for the
establishment, replacement, and refurbishment of FAA housing units at
remote locations where commercial housing is unavailable or inadequate.
(56‑54)

**1.111.1 Scope of F&E Work**. Provide site selection, site preparation,
environmental assessments, construction or refurbishment of housing
units.

**END OF DOCUMENT**