Federal Aviation Administration

ATC Spectrum Engineering Services (AJW-6)

![](media/image1.png){width="6.34375in" height="2.2395833333333335in"}

Radio Frequency Interference and Spectrum Monitoring System (RFISMS)

Fiscal Year 2007 to 2011 Statement of Work (SOW)

Spectrum Assignment and Engineering Office (AJW-63)

  ---------------------------------------------------- ------------------- -------------------------------------
  ![](media/image2.png){width="0.6465277777777778in"   Last Updated:\      12/14/2006\
  height="0.6in"}                                      Document Version:\  **.01**\
                                                       Document Status:\   DRAFT\
                                                       Document ID:\       **FOREST GREEN** **(EXTENDED)\
                                                       Reviewed By:\       **Jerrold B. Sandors\
                                                       Prepared By:        James S. Aviles

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

## Purpose

This statement of work is issued under task name Radio Frequency
Interference and Spectrum Monitoring System (**RFISMS**) to define the
project management, radio frequency engineering, telecommunications
engineering and software development support tasks required to implement
RFISMS with four-year options. The goal is for engineering, analyzing,
monitoring, detecting and locating electromagnetic signals (analog or
digital), disrupting National Airspace System (**NAS**) Communications,
Navigation and Surveillance (**CNS**) radio services.

## Requirement Description

The FAA Spectrum Engineering Services organization requires engineering
support to manage the radio spectrum used by NAS equipment providing CNS
products and services to aviation. To maintain CNS equipment operations
interference free, Spectrum Engineering Services has implemented a
national pilot project named Interference Monitoring Detection System
(**IMDS**). This pilot project's goal is to monitor, detect and quickly
locate radio frequency interference (**RFI**) disrupting NAS CNS
services and minimize air traffic delay impact. This Statement of Work
(**SOW**) describes the engineering support, hardware and software
improvements required for the availability and reliability of IMDS to
maintain Spectrum Engineering Monitoring capabilities. The IMDS national
test bed requires fixed direction finding sites with portable,
transportable and aircraft units participating in an enterprise web
based networked configuration.

## Scope of Work Description

The scope of work required covers engineering support, project status
reporting, Local and Wide area telecommunications configuration
upgrades, signal geolocation equipment, server infrastructure equipment,
software upgrades, integration activities and project management.

## RFISMS First Year High Level Tasks

1.  RFISMS Project Support Office Operations.

2.  Revise the RFISMS Project Master Plan.

3.  Update RFISMS Network Support Operations Center.

4.  Update IMDS LAN/WAN/VPN Systems Infrastructure.

5.  Complete Part 2 of IMDS v3.0 Upgrade Integrating TDOA.

6.  Reinstate Miami Net on a TIMDS configuration.

7.  Implement Technical Center IMDS v3.0 Test Bed.

8.  Deploy PIMDS system for each Operational IMDS Net.

9.  Implement Broadband Telecommunications at sites without
    connectivity.

## RFISMS Four Year Optional High Level Tasks

SECOND OPTION YEAR

10. RFISMS Project Support Office Operations.

11. Revise the RFISMS Project Master Plan.

12. Update RFISMS Network Support Operations Center.

13. Update IMDS LAN/WAN/VPN Systems Infrastructure.

14. Implement Broadband Telecommunications at sites without
    connectivity.

THIRD OPTION YEAR

15. RFISMS Project Support Office Operations.

16. Update RFISMS Network Support Operations Center.

17. Update IMDS LAN/WAN/VPN Systems Infrastructure.

18. Deploy PIMDS Equipment to Selected SMO field offices

19. Upgrade All Existing RFIM Vans to IMDS v3.0

20. Develop New IMDS Surface Vehicle for IMDS v3.0

21. Implement Atlanta Net on IMDS v3.0

22. Implement Washington DC Net on IMDS v3.0

23. Implement Broadband Telecommunications at sites without
    connectivity.

FOURTH OPTION YEAR

24. RFISMS Project Support Office Operations.

25. Update RFISMS Network Support Operations Center.

26. Update IMDS LAN/WAN/VPN Systems Infrastructure.

27. Deploy PIMDS Equipment to Selected SMO field offices.

28. Upgrade Existing Kansas City Net to IMDS v3.0.

29. Deploy New IMDS Surface Vehicle to selected Service Areas.

30. Implement Dallas-Ft. Worth Net on IMDS v3.0.

31. Implement Broadband Telecommunications at sites without
    connectivity.

FIFTH OPTION YEAR

32. RFISMS Project Support Office Operations.

33. Update RFISMS Network Support Operations Center.

34. Update IMDS LAN/WAN/VPN Systems Infrastructure.

35. Deploy New IMDS Surface Vehicle to selected Service Areas.

36. Implement Detroit Net on IMDS v3.0.

37. Implement Seattle Net on IMDS v3.0

38. Implement Broadband Telecommunications at sites without connectivity

39. 

40. 

41. 

42. 

43. 

## RFISMS Tasks General Descriptions

The contractor must perform the following general description for each
RFISMS task contained in section 1.4 above. Greater detail of the work
breakdown structure (**WBS**) for each task will be published in the
RFISMS Master Plan and associated specific project plan documents:

1.  RFISMS Project Support Office Operations. Operate the establish
    RFISMS Project Support Office to assist and support ATC Spectrum
    Engineering Services in the execution of spectrum engineering
    functions, service delivery and the development of spectrum
    engineering tasks described in greater detail in the RFISMS Master
    Plan. This task requires the operations at the project support
    office and must include requirements for revised engineering
    analysis, equipment procurements, software developments, system
    deployments and systems integration into the NAS. The contractor
    must maintain specialized hardware and software engineering teams
    under a consolidated project support office to work on technical
    tasks described in the Master Plan and the related project
    improvements for RFISMS. ([Link](#_Hlk128889170))

2.  Revise the RFISMS Project Master Plan describing project tasks
    management and milestones for FY-07. The RFISMS Master Plan is the
    document describing technical engineering functions, system
    requirements, operational tests and evaluations and concept
    descriptions of Spectrum Engineering Services business. The document
    delineates detailed plans and requirements for technical projects
    under RFISMS and their system sub elements (i.e., software,
    hardware, network, etc.). The contractor must deliver a revised
    document with a three-year projected outlook.
    ([Link](#_Hlk128889448))

3.  Update RFISMS Network Support Operations Center. This facility
    monitors subsystem outages (i.e., Angle of Arrival (AOA) direction
    finding equipment, Time Difference of Arrival (TDOA) geolocation
    equipment, server computing equipment, etc.) for performing
    restoration actions. The facility is a division of the Project
    Support Office in Uniontown, PA. Network Support Operations Center
    must conduct remote maintenance and provide a central Network
    Management System to monitor status, manage network impact, conduct
    root-cause-analysis and perform troubleshooting. The contractor must
    perform this function with Commercially Off The Shelf (COTS) network
    management tools in accordance with FAA Information Systems Security
    policies. The RFISMS Network Support Operations Center must assist
    users with system problem and maintain a log of help tickets open,
    pending and completed. The RFISMS Network Operations Center must
    maintain an up to date equipment master list of all RFISMS equipment
    inventory with precise location of each item in the master list.
    ([Link](#_Hlk128890101))

4.  Update IMDS LAN/WAN/VPN Systems Infrastructure. IMDS Software
    upgrades require telecommunications infrastructure reconfiguration
    or redesign to meet system performance and service delivery. The
    contractor must assess telecom infrastructure requirements, prepare
    test plans and conduct Operational Test and Evaluation (OT&E) on new
    telecom reconfiguration to maintain IMDS service delivery at the
    RFISMS Network Support Operations Center and all NAS operational
    IMDS Nets. The contractor must complete Security Certification
    Authorization Process (SCAP) certification for all existing IMDS
    hardware. The contractor must operate and maintain all IMDS data
    backup and archiving server systems within the telecom architecture
    at each of the existing operational national test bed locations
    (i.e., New York Net, Miami Net, Chicago Net and the Los Angeles Net)
    including the experimental Atlantic City Net. The contractor must
    integrate all national test bed locations with the National
    Operations Control Center (NOCC) and certify IMDS software upgrades
    provides 90 percent system availability and reliability.
    ([Link](#_Hlk128890445))

5.  Complete Part 2 of IMDS v3.0 Upgrade Integrating TDOA. The second
    part of the IMDS software version 2.0 upgrade to version 3.0
    integrates TDOA technology equipment and functionality with existing
    AOA equipment and capabilities. This IMDS version 3.0 upgrade must
    implement the Concept Visualization (CV) document graphical user
    interface (GUI) integration between TDOA and AOA equipment. Software
    Requirement Specification (SRS) outlining the details of the
    software functional requirements and coding must be completed. The
    contractor must execute the knowledge base obtained in Part 1 of the
    integration between TDOA and AOA with prototyping the Portable and
    Transportable IMDS systems as key platforms for testing this version
    3.0 upgrade. The contractor must complete experimental test runs on
    the combined AOA and TDOA equipment environment established around
    the RFISMS Project Support Office facilities. The PIMDS and TIMDS
    must be implemented with required components to meet ATC Spectrum
    Engineering Services requirements for system connectivity,
    scalability, interoperability, maintainability and mobility. The
    contractor must clearly document all the source code and deliver all
    software components to the FAA Spectrum Engineering Services office.
    The contractor must complete the FAA Security Certification
    Authorization Process (SCAP) certification for the PIMDS and TIMDS
    configurations prior to field deployment. The revised RFISMS Master
    Plan shall list companion PIMDS and TIMDS system documents to
    further describe in greater detail the requirements for
    transportability, physical security, interoperability and
    maintainability of these platforms (i.e., system architecture
    describing the new platform components, some sub components may
    include transportable trailer, collapsible masts, remote power
    management, fuel cell power, solar panel power, equipment HVAC,
    shelter enclosure, etc). ([Link](#_Hlk128892483))

6.  Reinstate Miami Net on a TIMDS configuration. The Miami IMDS Net
    became out of service when hurricane Rita made landfall in south
    Florida. IMDS equipment that was not destroyed was sent to
    contractor facilities for the design of a Tactical and Transportable
    IMDS configuration. This TIMDS configuration will provide greater
    survivability under severe weather. The contractor must reinstate
    the Miami IMDS Net with a TIMDS platform configuration as developed
    for the FAA under version 2 for later upgrade to version 3. The
    reinstatement of the Miami IMDS Net must also include one Portable
    IMDS (PIMDS) unit that will work seamlessly with the TIMDS Net
    configuration as an active interchangeable mobile unit and with a
    second or more PIMDS or TIMDS units as a tactical mobile micro-net.
    The contractor must include the technical design document for both
    the PIMDS and TIMDS platforms to be self-sustained stand-alone
    systems operable by one individual or as part of the Miami IMDS Net.
    The contractor must coordinate in collaboration with the FAA
    Southern Region Frequency Management Office for transport and
    delivery of PIMDS and TIMDS units for covering the International
    Airport area as part of a tactical network. ([Link](#_Hlk128892840))

7.  Implement Technical Center IMDS v3.0 Test Bed. The Atlantic City
    International Airport (ACY) located in the state of New Jersey is
    shared with the research FAA William J. Hughes Technical Center
    facility. The contractor must support the Spectrum Testing and
    Engineering Analysis Office personnel in the implementation of a
    test bed Net in the vicinity of the Atlantic City airport. This test
    bed Net will be configured to execute Operational Tests and
    Evaluations (OT&E) of existing and new hardware and software
    versions of the IMDS equipment, tools and platforms. The contractor
    must provide all necessary equipment and assist Spectrum Engineering
    personnel to configure network telecommunications connectivity as
    well as provide required AOA and TDOA equipment components. The
    contractor must implement one PIMDS, one TIMDS and prototype an IMDS
    upgrade to the Radio Frequency Interference Monitoring (RFIM) Van to
    work seamlessly with the fixed sites (FIMDS) as a complete coherent
    IMDS Net with connectivity to the rest of the national test bed
    sites in the NAS. ([Link](#_Hlk128893012))

8.  Deploy PIMDS system for each Operational IMDS Net. The Portable IMDS
    system is the platform that is capable of operating as a
    self-sustained stand-alone system operable by one individual or as
    part of a micro-net of PIMDS units in close proximity or as part of
    a fixed IMDS Net with other platforms such as the TIMDS. The
    contractor must deploy one PIMDS for each operational IMDS Net.
    ([Link](#_Hlk128893299))

9.  Implement Broadband Telecommunications at sites without
    connectivity. The remote fixed IMDS site is selected based on Radio
    Line of Sight (RLOS) geometry. Thus some locations lack broadband
    telecommunications service. The contractor must engineer and provide
    wireless network technology for these IMDS locations without LAN/WAN
    connectivity. ([Link](#_Hlk153854616))

## Deliverables

+---+----------------------------------+--------------+---------------+
| * |                                  |              |               |
| * |                                  |              |               |
| T |                                  |              |               |
| A |                                  |              |               |
| B |                                  |              |               |
| L |                                  |              |               |
| E |                                  |              |               |
|   |                                  |              |               |
| 1 |                                  |              |               |
| . |                                  |              |               |
| S |                                  |              |               |
| C |                                  |              |               |
| H |                                  |              |               |
| E |                                  |              |               |
| D |                                  |              |               |
| U |                                  |              |               |
| L |                                  |              |               |
| E |                                  |              |               |
| O |                                  |              |               |
| F |                                  |              |               |
| D |                                  |              |               |
| E |                                  |              |               |
| L |                                  |              |               |
| I |                                  |              |               |
| V |                                  |              |               |
| E |                                  |              |               |
| R |                                  |              |               |
| A |                                  |              |               |
| B |                                  |              |               |
| L |                                  |              |               |
| E |                                  |              |               |
| S |                                  |              |               |
| / |                                  |              |               |
| A |                                  |              |               |
| C |                                  |              |               |
| T |                                  |              |               |
| I |                                  |              |               |
| V |                                  |              |               |
| I |                                  |              |               |
| T |                                  |              |               |
| I |                                  |              |               |
| E |                                  |              |               |
| S |                                  |              |               |
| * |                                  |              |               |
| * |                                  |              |               |
|   |                                  |              |               |
| * |                                  |              |               |
| * |                                  |              |               |
| ( |                                  |              |               |
| A |                                  |              |               |
| s |                                  |              |               |
| o |                                  |              |               |
| f |                                  |              |               |
| D |                                  |              |               |
| e |                                  |              |               |
| c |                                  |              |               |
| e |                                  |              |               |
| m |                                  |              |               |
| b |                                  |              |               |
| e |                                  |              |               |
| r |                                  |              |               |
| 1 |                                  |              |               |
| , |                                  |              |               |
| 2 |                                  |              |               |
| 0 |                                  |              |               |
| 0 |                                  |              |               |
| 6 |                                  |              |               |
| ) |                                  |              |               |
| * |                                  |              |               |
| * |                                  |              |               |
+---+----------------------------------+--------------+---------------+
| R | **ACTIVITY**                     | **D          | **Date After  |
| e |                                  | eliverable** | Contract      |
| f |                                  |              | Award         |
| . |                                  |              | (DACA)**      |
| N |                                  |              |               |
| o |                                  |              |               |
| . |                                  |              |               |
+---+----------------------------------+--------------+---------------+
| [ | RFISMS Project Support Office    |              |               |
| 1 | Operations                       |              |               |
| . |                                  |              |               |
| 0 |                                  |              |               |
| ] |                                  |              |               |
| ( |                                  |              |               |
| # |                                  |              |               |
| _ |                                  |              |               |
| H |                                  |              |               |
| l |                                  |              |               |
| k |                                  |              |               |
| 1 |                                  |              |               |
| 2 |                                  |              |               |
| 8 |                                  |              |               |
| 8 |                                  |              |               |
| 8 |                                  |              |               |
| 6 |                                  |              |               |
| 7 |                                  |              |               |
| 8 |                                  |              |               |
| 7 |                                  |              |               |
| ) |                                  |              |               |
+---+----------------------------------+--------------+---------------+
|   | 1.1 RFISMS Project Support       | Bi-Weekly    | 14 Days       |
|   | Office Status                    | Report       |               |
+---+----------------------------------+--------------+---------------+
| [ | []{#_Hlk128889448 .anchor}Revise |              |               |
| 2 | the RFISMS Project Master Plan   |              |               |
| . |                                  |              |               |
| 0 |                                  |              |               |
| ] |                                  |              |               |
| ( |                                  |              |               |
| # |                                  |              |               |
| _ |                                  |              |               |
| H |                                  |              |               |
| l |                                  |              |               |
| k |                                  |              |               |
| 1 |                                  |              |               |
| 0 |                                  |              |               |
| 3 |                                  |              |               |
| 4 |                                  |              |               |
| 1 |                                  |              |               |
| 8 |                                  |              |               |
| 2 |                                  |              |               |
| 4 |                                  |              |               |
| 5 |                                  |              |               |
| ) |                                  |              |               |
+---+----------------------------------+--------------+---------------+
|   | 2.1 RFISMS Master Project Plan   | Revision     | 45 Days       |
|   | Review                           | Draft        |               |
|   |                                  |              | 90 Days       |
|   |                                  | Revision     |               |
|   |                                  | Report       |               |
+---+----------------------------------+--------------+---------------+
| [ | Update RFISMS Network Support    |              |               |
| 3 | Operations Center                |              |               |
| . |                                  |              |               |
| 0 |                                  |              |               |
| ] |                                  |              |               |
| ( |                                  |              |               |
| # |                                  |              |               |
| _ |                                  |              |               |
| H |                                  |              |               |
| l |                                  |              |               |
| k |                                  |              |               |
| 1 |                                  |              |               |
| 2 |                                  |              |               |
| 8 |                                  |              |               |
| 8 |                                  |              |               |
| 9 |                                  |              |               |
| 0 |                                  |              |               |
| 0 |                                  |              |               |
| 7 |                                  |              |               |
| 1 |                                  |              |               |
| ) |                                  |              |               |
+---+----------------------------------+--------------+---------------+
|   | 3.1 Network Support Operations   | Updated      | 60 Days       |
|   | Center Management                | Operations   |               |
|   |                                  | Document     | 14 Days       |
|   | 3.2 Network Support Operations   |              |               |
|   | Center Status                    | Bi-weekly    |               |
|   |                                  | Status       |               |
|   |                                  | Report       |               |
+---+----------------------------------+--------------+---------------+
| [ | Update IMDS LAN/WAN/VPN Systems  |              |               |
| 4 | Infrastructure                   |              |               |
| . |                                  |              |               |
| 0 |                                  |              |               |
| ] |                                  |              |               |
| ( |                                  |              |               |
| # |                                  |              |               |
| _ |                                  |              |               |
| H |                                  |              |               |
| l |                                  |              |               |
| k |                                  |              |               |
| 1 |                                  |              |               |
| 2 |                                  |              |               |
| 8 |                                  |              |               |
| 8 |                                  |              |               |
| 9 |                                  |              |               |
| 0 |                                  |              |               |
| 3 |                                  |              |               |
| 4 |                                  |              |               |
| 3 |                                  |              |               |
| ) |                                  |              |               |
+---+----------------------------------+--------------+---------------+
|   | 4.1 Complete Infrastructure      | C            | 120 Days      |
|   | Configurations                   | onfiguration |               |
|   |                                  | Plan         | 180 Days      |
|   | 4.2 Complete Infrastructure      |              |               |
|   | Updates                          | Updated      |               |
|   |                                  | In           |               |
|   |                                  | frastructure |               |
+---+----------------------------------+--------------+---------------+
| [ | Complete Part 2 of IMDS v3.0     |              |               |
| 5 | Upgrade Integrating TDOA         |              |               |
| . |                                  |              |               |
| 0 |                                  |              |               |
| ] |                                  |              |               |
| ( |                                  |              |               |
| # |                                  |              |               |
| _ |                                  |              |               |
| H |                                  |              |               |
| l |                                  |              |               |
| k |                                  |              |               |
| 1 |                                  |              |               |
| 2 |                                  |              |               |
| 8 |                                  |              |               |
| 8 |                                  |              |               |
| 9 |                                  |              |               |
| 2 |                                  |              |               |
| 1 |                                  |              |               |
| 8 |                                  |              |               |
| 9 |                                  |              |               |
| ) |                                  |              |               |
+---+----------------------------------+--------------+---------------+
|   | 5.1 IMDS version 3.0 upgrade     | IMDS v3.0    | 200 Days      |
|   | beta release                     | Beta         |               |
|   |                                  |              | 240 Days      |
|   | 5.2 IMDS version 3.0 upgrade     | IMDS v3.0    |               |
|   | source code                      | Code         |               |
+---+----------------------------------+--------------+---------------+
| [ | Reinstate Miami Net on a TIMDS   |              |               |
| 6 | configuration                    |              |               |
| . |                                  |              |               |
| 0 |                                  |              |               |
| ] |                                  |              |               |
| ( |                                  |              |               |
| # |                                  |              |               |
| _ |                                  |              |               |
| H |                                  |              |               |
| l |                                  |              |               |
| k |                                  |              |               |
| 1 |                                  |              |               |
| 2 |                                  |              |               |
| 8 |                                  |              |               |
| 8 |                                  |              |               |
| 9 |                                  |              |               |
| 2 |                                  |              |               |
| 7 |                                  |              |               |
| 7 |                                  |              |               |
| 7 |                                  |              |               |
| ) |                                  |              |               |
+---+----------------------------------+--------------+---------------+
|   | 6.1 Reinstate Miami IMDS Net on  | MIA TIMDS    | 120 Days      |
|   | v2.0                             | Net          |               |
|   |                                  |              | 240 Days      |
|   | 6.2 Upgrade Miami IMDS Net to    | MIA TIMDS    |               |
|   | v3.0                             | v3.0         |               |
+---+----------------------------------+--------------+---------------+
| [ | Implement Technical Center IMDS  |              |               |
| 7 | v3.0 Test Bed.                   |              |               |
| . |                                  |              |               |
| 0 |                                  |              |               |
| ] |                                  |              |               |
| ( |                                  |              |               |
| # |                                  |              |               |
| _ |                                  |              |               |
| H |                                  |              |               |
| l |                                  |              |               |
| k |                                  |              |               |
| 1 |                                  |              |               |
| 2 |                                  |              |               |
| 8 |                                  |              |               |
| 8 |                                  |              |               |
| 9 |                                  |              |               |
| 2 |                                  |              |               |
| 9 |                                  |              |               |
| 9 |                                  |              |               |
| 1 |                                  |              |               |
| ) |                                  |              |               |
+---+----------------------------------+--------------+---------------+
|   | 7.1 Atlantic City (ACY) IMDS Net | ACY IMDS Net | 180 Days      |
|   |                                  |              |               |
|   | 7.2 Atlantic City PIMDS Platform | ACY PIMDS    | 90 Days       |
|   |                                  |              |               |
|   | 7.3 Atlantic City TIMDS Platform | ACY TIMDS    | 180 Days      |
|   |                                  |              |               |
|   | 7.4 RFIM IMDS Upgrade Prototype  | RFIM IMDS    | 90 Days       |
+---+----------------------------------+--------------+---------------+
| [ | Deploy PIMDS system for each     |              |               |
| 8 | Operational IMDS Net             |              |               |
| . |                                  |              |               |
| 0 |                                  |              |               |
| ] |                                  |              |               |
| ( |                                  |              |               |
| # |                                  |              |               |
| _ |                                  |              |               |
| H |                                  |              |               |
| l |                                  |              |               |
| k |                                  |              |               |
| 1 |                                  |              |               |
| 3 |                                  |              |               |
| 0 |                                  |              |               |
| 7 |                                  |              |               |
| 1 |                                  |              |               |
| 9 |                                  |              |               |
| 5 |                                  |              |               |
| 6 |                                  |              |               |
| 6 |                                  |              |               |
| ) |                                  |              |               |
+---+----------------------------------+--------------+---------------+
|   | 8.1 Deploy PIMDS Units           | PIMDS Units  | 90 Days       |
+---+----------------------------------+--------------+---------------+
| [ | Implement Broadband              |              |               |
| 9 | Telecommunications at sites      |              |               |
| . | without connectivity             |              |               |
| 0 |                                  |              |               |
| ] |                                  |              |               |
| ( |                                  |              |               |
| # |                                  |              |               |
| _ |                                  |              |               |
| H |                                  |              |               |
| l |                                  |              |               |
| k |                                  |              |               |
| 1 |                                  |              |               |
| 5 |                                  |              |               |
| 3 |                                  |              |               |
| 8 |                                  |              |               |
| 5 |                                  |              |               |
| 4 |                                  |              |               |
| 4 |                                  |              |               |
| 0 |                                  |              |               |
| 5 |                                  |              |               |
| ) |                                  |              |               |
+---+----------------------------------+--------------+---------------+
|   | 9.1 Implement Wireless (WiFi)    | Wireless     | 120 Days      |
|   | LAN/WAN                          | LAN/WAN      |               |
+---+----------------------------------+--------------+---------------+

The contractor must provide status reports to the Spectrum Engineering
Services Contracting Officer Technical Representative (COTR) due
bi-weekly every other Tuesday and a minimum of twice each month. The
status report must contain at a minimum

a.  A summary of work accomplished during the reporting period,

b.  Identification of problems or concerns encountered,

c.  Identification of proposed work for the next reporting period.

The contractor must develop and maintain documentation concerning the
RFISMS system architecture and all file server configurations.

## Cost Considerations

**Travel Requirements**

In support of RFISMS requirements the contractor must plan on local
travel within the metropolitan Washington, DC area and travel to FAA
regional offices and other locations in the National Airspace System as
necessary. Travel requirements will be identified in the plans and
scheduled for approval according to the needs of the tasks outlined
herein.