ASTI_Att_J-1_ASTI_Technical_Specification_00039_Amendment_5

Document Sample
ASTI_Att_J-1_ASTI_Technical_Specification_00039_Amendment_5 Powered By Docstoc
					ATTACHMENT J-1
ASTI TECHNICAL SPECIFICATION
ASTI                                                      Amendment 5                                          DTFAWA-10-R-00039


SECTION J-1: ASTI TECHNICAL SPECIFICATION ......................................................... 1
  SPEC.1 ALASKAN SATELLITE TELECOMMUNICATIONS INFRASTRUCTURE ........ 1
    SPEC.1.1 Purpose of the FAA ASTI Technical Specification ................................................. 1
    SPEC.1.2 Document Overview ................................................................................................ 1
  SPEC.2 REFERENCE DOCUMENTS ............................................................................................. 2
    SPEC.2.1 Government Specifications, Standards, Orders, Acts, Memorandums, Manuals,
    and Handbooks ........................................................................................................................ 2
    SPEC.2.2 Industry and Commercial Standards ...................................................................... 4
    SPEC.2.3 Order of Precedence ............................................................................................... 6
  SPEC.3 ASTI SERVICE AND SYSTEM REQUIREMENTS .............................................................. 7
    SPEC.3.1 System, Equipment, and Software Reliability ......................................................... 7
    SPEC.3.2 Automatic Circuit Protection Switching ............................................................... 10
    SPEC.3.3 System Latency ...................................................................................................... 12
    SPEC.3.4 Compatibility with Existing Space Segment ......................................................... 12
    SPEC.3.5 Interoperability Requirements .............................................................................. 12
    SPEC.3.6 Network Timing Architecture and Requirements.................................................. 12
    SPEC.3.7 Facility and Equipment Requirements .................................................................. 13
  SPEC.4 REQUIREMENTS FOR REPLACED ASTI COMPONENTS ................................................ 25
    SPEC.4.1 Radio Frequency (RF) Components ..................................................................... 25
    SPEC.4.2 Modem Component ............................................................................................... 45
    SPEC.4.3 Multiplexer Component ........................................................................................ 49
    SPEC.4.4 ASTI Demarcation Point (ADP) Components .................................................. 5655
  SPEC.5 NETWORK MANAGEMENT AND CONTROL SYSTEM (NMCS) REQUIREMENTS ....... 5958
    SPEC.5.1 Overview ........................................................................................................... 5958
    SPEC.5.2 General NMCS Functional Requirements ............................................................ 59
    SPEC.5.3 Environmental Requirements ............................................................................ 6160
    SPEC.5.4 Physical Requirements .......................................................................................... 61
    SPEC.5.5 NMCS Hardware and Software Component Requirements .................................. 65
    SPEC.5.6 Fault Management Requirements ..................................................................... 7473
    SPEC.5.7 Configuration Management Requirements ........................................................... 88
    SPEC.5.8 Administrative Management Requirements .......................................................... 99
    SPEC.5.9 Performance Management Requirements ........................................................... 106
    SPEC.5.10 Security Management Requirements .............................................................. 109




10/07/10                                                    SECTION J-1: ASTI TECHNICAL SPECIFICATION - i
ASTI                                         Amendment 5                           DTFAWA-10-R-00039


SECTION J-1:             ASTI TECHNICAL SPECIFICATION

SPEC.1    ALASKAN SATELLITE TELECOMMUNICATIONS
    INFRASTRUCTURE

SPEC.1.1          Purpose of the FAA ASTI Technical Specification

This document describes the technical requirements, including functional, performance and security
requirements, for modernization of the Federal Aviation Administration’s (FAA) Alaskan Satellite
Telecommunications Infrastructure (ASTI). This modernization will include replacing existing ASTI
system components and the Network Management and Control System (NMCS), identified herein, in
order to meet the FAA’s telecommunications needs.

SPEC.1.2          Document Overview

This technical specification is organized as follows:

Section 1     Introduction – Provides the purpose, specification overview, ground rules, and assumptions
              contained in the specification.

Section 2     Reference Documents — Lists the standards, specifications, and other policy
              documentation that are referenced in this specification.

Section 3     ASTI System Requirements — Provides the overall system level requirements for the ASTI
              network to include ASTI Channel Protection Switching (A/B path switching), overall
              Availability, Network Management and Control System (NMCS) and
              environmental/facilities.

Section 4     Requirements for ASTI Network Components — Identifies all the ASTI network
              components to be upgraded and provides the technical requirements for the network
              components that the Contractor must furnish and integrate.

Section 5     Requirements for ASTI Network Management and Control System (Including Security) —
              Provides the technical and functional requirements for the network management system,
              including security requirements, that the Contractor must furnish and integrate.

Appendices    Appendices A through K — Provide additional information related to the specifications and
              requirements in this document.




10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 1
ASTI                                      Amendment 5                              DTFAWA-10-R-00039



SPEC.2          Reference Documents

           The following tables reflect Government and Industry specifications, standards, and
           handbooks applicable to this procurement and functional specification:

SPEC.2.1     Government Specifications, Standards, Orders, Acts, Memorandums, Manuals,
      and Handbooks

            Identifier & Date          Title

            29 CFR 1903-1910           Title 29, Labor, Chapter XVII – Occupational Safety and Health
                                       Administration, Department of Labor, Parts (a) – (g)

            29 CFR 1926                Safety and Health Regulations for Construction

            29 CFR 1960.20             Alternate Standard for Fire Safety in Airport Traffic Control
                                       Towers (ATCT)

            40 CFR Part 82             Protection of Stratospheric Ozone

            FCC Part 25                Title 47, Telecommunications, Vol. 2, Chapter I – Federal
                                       Communications Commission, Part 25, Satellite
                                       Communications

            ATO Memorandums            ATO Authorizing Official (AO) Security Implementation
            ATO-ISS-09-01 through      Guidance Memorandums, 17 ea.
            ATO-ISS-09-17

            DOT Handbook 10-202        Departmental Guide to Network Security

            E-Government Act of        Title III: Information Security - Federal Information Security
            2002, Public Law 107-347   Management Act of 2002.

            FAA ATO Networking         FAA ATO Networking Standards
            Standards v 1.2

            FAA-C-1217F                Electrical Work, Interior

            FAA C&A Handbook           Security Certification and Accreditation (C&A) Handbook

            FAA-G-2100H                Electronic Equipment, General Requirements

            FAA Order 1050.1E          Policies and Procedures for Considering Environmental Impacts

            FAA Order 1050.10C         Prevention, Control, and Abatement of Environmental Pollution
                                       at FAA Facilities

            FAA Order 1050.14A         Polychlorinated Biphenyls (PCBs) in the National Airspace
                                       System (NAS)

            FAA Order 1050.20A         Airway Facilities Asbestos Control Program

10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 2
ASTI                                      Amendment 5                             DTFAWA-10-R-00039

           Identifier & Date           Title

           FAA Order 1370.82A          Information Systems Security Program

           FAA Order 1370.89,          FAA Information Operations Conditions

           FAA Order 1370.92,          Password & Pin Management

           FAA Order 3900.19B          Occupational Safety and Health Program

           FAA Order 3900.57           Pre-Construction and Maintenance Project Safety and Health
                                       Checklist

           FAA Order 4600.27           Personal Property Management

           FAA Order JO 6580.3B        Remote Communications Facilities Installations Standards
                                       Handbook

           FAA Order 6630.4A           En Route Communications Installation Standards Handbook

           FAA Order 6950.2D           Electrical Power Policy Implementation at National Airspace
                                       Systems Facilities

           FAA Order JO6980.25C        Maintenance of Batteries for Standby Power

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

           DOT/FAA/CT-03-05, HF-       Human Factors Design Standard
           STD-001

           6470.33A                    Control of Power, Space, and Environmental Interfaces at
                                       Enroute Air Traffic Control Facilities

                                       Anchorage ARTCC Communications Systems Plan

                                       Resource Conservation and Recovery Act (RCRA)

           Homeland Security           Policy for a Common Identification Standard for Federal
           Presidential Directive 12   Employees and Contractors
           (HSPD 12)


           MIL-DTL-26482H              Connectors, Electrical, (Circular, Miniature, Quick Disconnect,
                                       Environment Resisting), Receptacles and Plugs, General
                                       Specification For

           MIL-C-24308                 Rectangular, Miniature, Polarized Shell, Crimp And Solder
                                       Contacts, Electrical Connector

           MIL-STD-1472F               Human Engineering


10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 3
ASTI                                   Amendment 5                            DTFAWA-10-R-00039

           Identifier & Date        Title

           NIST FIPS PUB 197        Advanced Encryption Standard

           NIST FIPS PUB 199        Standards for Security Categorization of Federal Information
                                    and Information Systems

           NIST FIPS PUB 201        Personal Identity Verification (PIV) of Federal Employees and
                                    Contractors

           NIST SP 800-53           Recommended Security Controls for Federal Information
                                    Systems

           NIST SP 800-63           Electronic Authentication Guideline: Recommendations of the
                                    National Institute of Standards and Technology
           Version 1.0.2,

           NIST SP 800-86           Guide to Integrating Forensic Techniques into Incident Response

           NIST SP 800-92           Guide to Computer Security Log Management

           NIST SP 800-94           Guide to Intrusion Detection and Prevention Systems (IDPS)



SPEC.2.2         Industry and Commercial Standards

           Identifier & Date         Title

           ANSI/EIA/TIA-RS232-C      Interface Between Data Terminal Equipment and Data
                                     Communication Equipment Employing Serial Binary Data
                                     Interchange
           ANSI/EIA/TIA-RS232-D      Interface Between Data Terminal Equipment and Data
                                     Communication Equipment Employing Serial Binary Data
                                     Interchange

           ANSI/EIA/TIA-232-E        Interface Between Data Terminal Equipment and Data
                                     Communication Equipment Employing Serial Binary Data
                                     Interchange

           ANSI/EIA/TIA-232-F        Interface Between Data Terminal Equipment and Data
                                     Communication Equipment Employing Serial Binary Data
                                     Interchange

           ANSI/EIA/TIA-449          High Speed 25-Position Interface for Data Terminal Equipment and
                                     Data Circuit-Terminating Equipment, Including Alternate 26-
                                     Position Connector )

           ANSI/EIA-530              High Speed 25-Position Interface for Data Terminal Equipment and
                                     Data Circuit-Terminating Equipment




10/07/10                                    SECTION J-1: ASTI TECHNICAL SPECIFICATION - 4
ASTI                                  Amendment 5                             DTFAWA-10-R-00039

           Identifier & Date        Title

           ANSI/EIA/TIA-530-A       High Speed 25-Position Interface for Data Terminal Equipment and
                                    Data Circuit-Terminating Equipment, Including Alternate 26-
                                    Position Connector

           ANSI T1.403              Telecommunications - Network-to-Customer Installation - DSI
                                    Metallic Interface ATIS

           ANSI Z358.1              American National Standard for Emergency Eye Wash and Shower
                                    Equipment

           Bellcore TR-NWT-000335   Voice Grade Special Access Service Transmission Parameter Limits
                                    and Interface Combinations

           BOCA                     National Building Code
           1999

           EIA-310-D                Cabinets, Racks, Panels, and Associated Equipment

           EIA/TIA 568-B            Commercial Building Telecommunications Cabling Standard

           EIA/TIA TSB-67           Transmission Performance Specifications for Field Testing of
                                    Unshielded Twisted-Pair Cabling Systems

           IESS-308                 Performance Characteristics for Intermediate Data Rates Digital
                                    Carriers Using Convolutional Encoding/Viterbj Decoding and
                                    QPSK Modulation (QPSK/IDR)

           IESS-309                 Performance Characteristics for Intelsat Business Services (IBS)

           IESS-310                 Performance Characteristics for Intermediate Data Rates Digital
                                    Carriers Using Rate 2/3 TCM/8PSK and Reed-Solomon Outer
                                    Coding (TCM/IDR)

           ISO/IEC 9075-3:2008      ODBC (Open Database Connectivity), Information Technology –
                                    Database Languages SQL – Part 3: Call-Level Interface (SQL/CLI)

           ITU-T G.711              Pulse code modulation (PCM) of voice frequencies


           ITU-T G.726              CCITT Recommendation G.726 (1990), General Aspects of Digital
                                    Transmission Systems, Terminal Equipment - 40, 32, 24,16 kbit/s
                                    Adaptive Differential Pulse Code Modulation (ADPCM).

           M.3010                   Principles for a Telecommunications Management Network: TMN
                                    and Network Maintenance: International Transmission Systems,
                                    Telephone Circuits, Telegraphy, Facsimile and Leased Circuits




10/07/10                                SECTION J-1: ASTI TECHNICAL SPECIFICATION - 5
ASTI                                        Amendment 5                             DTFAWA-10-R-00039

           Identifier & Date             Title

           M.3400                        TMN Management Functions: TMN and Network Maintenance:
                                         International Transmission Systems, Telephone Circuits,
                                         Telegraphy, Facsimile and Leased Circuits

           NFPA 70                       National Electrical Code

           NFPA 70E                      Electrical Safety in the Workplace

           NFPA 101®                     Life Safety Code

           NTP (Network Time             Network Time Protocol (Version 1): Specification and
           Protocol), Ver 1, RFC-1059    Implementation

           NTP (Network Time             Network Time Protocol (Version 2): Specification and
           Protocol), Ver 2, RFC-1119    Implementation
           September 1989

           NTP (Network Time             Network Time Protocol (Version 3): Specification, Implementation
           Protocol), Ver 3, RFC-1305    and Analysis

           SBCCI                         Standard Building Code

           SNTP (Simple Network          Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6
           Time Protocol), RFC-4330      and OSI
           (obsoletes 2030)

           SNMP v2, RFC-2578             Structure of Management Information Version 2 (SMIv2)

           SNMP v3, RFC-3411             An Architecture for Describing Simple Network Management
                                         Protocol (SNMP) Management Frameworks

           UBC                           Uniform Building Code




SPEC.2.3         Order of Precedence

In case of a conflict between the body of this document and the above documentation, the requirements
within the body of this document must take precedence. In case of a conflict between requirements in the
above documentation which is not specifically arbitrated within the body of this document, please contact
your FAA point of contact.




10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 6
ASTI                                              Amendment 5                                   DTFAWA-10-R-00039

SPEC.3            ASTI Service and System Requirements

SPEC.3.1            System, Equipment, and Software Reliability

SPEC.3.1.1          General

SPEC.3.1.1.1     The following system level and equipment requirements must apply to all components
and equipment identified in this specification.

SPEC.3.1.1.2      ASTI is divided into three sub-networks, each associated with an AFSS Hub. Under
various ASTI-communications failure and degraded conditions (including the complete loss of ZAN
ARTCC), each AFSS hub sub-network must be capable of meeting all functional and performance
requirements as stated in Sections SPEC.3 and SPEC.4.



SPEC.3.1.2          System Availability

The following are the system availability requirements for: Phase I1 Remote-to/from-hub2 sites, Phase II3
Remote-to/from-hub sites & hub-to/from-hub sites:

SPEC.3.1.2.1     Phase I remote site -to/from- hub, hub -to/from-hub, and ZSE remote-to/from- remote
sites - The ADP-to-ADP availability must meet the following requirements at a minimum:

             a) Critical circuits .9999
             b) Essential circuits .999
             c) Routine circuits .99

SPEC.3.1.2.2   Phase II remote site-to/from-hub sites - The ADP-to-ADP availability must be a
minimum of 0.999.

SPEC.3.1.2.3   The following availability assumptions with respect to the Government Furnished
Equipment (GFE) must be made when calculating availability:

             a) The availability for the space segment (includes antenna component) is 0.999902
             b) The availability for each FAA GFE, including power and cables is 0.99995. GFE power
                for ASTI components, are protected by a GFE Uninterrupted Power System (UPS) except
                antenna de-icers, antenna motor controls, and HVAC.




1
  Refer to Appendix E for the definition of Phase I and Phase II ASTI sites. Phase I sites include remote sites, Hub
sites and ZAN ARTCC. Phase I sites access two satellites.
2
  Hub, when used alone, refers to all four hubs: ZAN ARTCC, Kenai (ENA) AFSS, Fairbanks (FAI) AFSS, and
Juneau (JNU) AFSS. AFSS hub nomenclature is used to specify the three AFSS hubs, ENA, FAI, and JNU.
3
  Refer to Appendix E for the definition of Phase I and Phase II ASTI sites. Phase II sites are all remote sites. Phase
II sites access only one satellite.
10/07/10                                            SECTION J-1: ASTI TECHNICAL SPECIFICATION - 7
ASTI                                             Amendment 5                               DTFAWA-10-R-00039

SPEC.3.1.3          Telecommunications Equipment and Software Reliability and Redundancy

SPEC.3.1.3.1        Telecommunications Equipment Reliability and Redundancy

SPEC.3.1.3.1.1 Component reliability must be measured as a Mean Time Between Failures (MTBF)
requirement for the replaced components. These requirements are specified in Section SPEC.4 for each
component.

SPEC.3.1.3.1.2 The ground station components must have the minimum redundancy as specified in the
following table:

     ASTI Facility             RF                 Modem                 Multiplexer Components
                            Components         Components
    Phase I Remote            None           Only BET and     Power supplies must be redundant.
         Sites                               ZSE require 1
                                             for 8            Note: The following depicts the existing
                                             redundancy       redundancy approach used to comply with
    Phase II Remote        1 for 1, except 1 for 1            availability requirements:
         Sites             LNA or LNB                      1.     Aggregate Control Card (primary) – 1:1
       Hub Sites               1 for 1       1 for 8       2.     Channel Interface Card – 1:1
                                                           3.     Enterprise System Control Card – 1:1
                                                           4.     Expansion Module – 1:1
                                                           5.     Redundant Power supplies
                                     Table 3.1.3-1: Component Redundancy


SPEC.3.1.3.1.3 In the event of any single hardware failure or degradation, the equipment must
automatically detect and switch within 600 ms to a redundant module, if available.

SPEC.3.1.3.1.4 All replaceable hardware modules within a replaced component or equipment must be
“hot swappable”4.


SPEC.3.1.3.2        Telecommunications Software Recovery, Availability, and Upgrade

SPEC.3.1.3.2.1 All ASTI equipment which incorporates digital processors or controllers must monitor
the operation of the software running on the processors or controllers.

SPEC.3.1.3.2.1.1 All software must be upgradeable remotely.

SPEC.3.1.3.2.1.2 Service interruption due to in-service software upgrades must not exceed 30 seconds.


SPEC.3.1.4          Digital Aggregate Level Path Performance

The following are the aggregate level performance requirements for all aggregate paths, as depicted in
figure 3.1.4-1, Availability States:

SPEC.3.1.4.1        All aggregate paths must be classified as being Available, Degraded, or Unavailable.



4
    “Hot swappable” means that it must not be necessary to power down the equipment prior to replacement.
10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 8
ASTI                                              Amendment 5                                  DTFAWA-10-R-00039

SPEC.3.1.4.2     The aggregate level path5 must be declared Unavailable when the aggregate level Bit
Error Rate (BER) is greater than the configured BER Unavailable threshold. Methodology for
measurement of aggregate path level BER is TBP.

SPEC.3.1.4.2.1      The BER Unavailable threshold must be configurable by the user.

SPEC.3.1.4.2.2      The default value for the BER Unavailable threshold must be BER > 1.0×10E-3.

SPEC.3.1.4.3       The Degraded state must be composed of a BER range (a hysteresis6 state) and a soak
interval7 as defined below.

SPEC.3.1.4.4       The aggregate level path must be declared Degraded when the aggregate level BER is
greater than the configured BER Degraded threshold but less than or equal to the BER Unavailable
threshold.

SPEC.3.1.4.4.1 The BER Degraded threshold must be configurable by the user and be less than or equal
to the BER Unavailable threshold.

SPEC.3.1.4.4.2      The default value for the BER Degraded threshold must be BER > 1.0×10E-6.

SPEC.3.1.4.5     Soak interval condition of the Degraded state: following a transition from Degraded and
Unavailable to Available BER threshold, the following applies:

SPEC.3.1.4.5.1 The aggregate state will remain Degraded throughout a user configurable time period
where the BER must remain below the Degraded threshold.

SPEC.3.1.4.5.2      After the time period elapses, the aggregate must be declared Available.

SPEC.3.1.4.5.3      If the aggregate BER increases above the Degraded threshold, the time period must
restart.

SPEC.3.1.4.5.4      The default time period must be 2 hours.

SPEC.3.1.4.6        For purposes of aggregate availability calculations:

SPEC.3.1.4.6.1      Total raw8 available time must include time spent in the Available state.

SPEC.3.1.4.6.2      Default threshold values must be applied.




5
  See Appendix E for more information on aggregate level path.
6
   “Hysteresis” is a technique used in the telecom industry whereby the protection switch “restore” threshold is set to
a different value than the “initiate” threshold value. Hysteresis is used to minimize unnecessary actions / transitions
which could otherwise occur when the monitored parameter vacillates slowly near the “initiate” threshold value (a
fairly common occurrence, particularly with analog signals).
7
  "Soak Interval" is defined in the telecom industry as a configurable time interval during which a condition should
continuously exist in order to be considered "real". This concept is used to ignore transient "hits" and momentary
conditions on telecom circuits; thereby avoiding unnecessary alarm reports and protection switch actions.
8
  Raw indicates unadjusted time.
10/07/10                                            SECTION J-1: ASTI TECHNICAL SPECIFICATION - 9
ASTI                                                Amendment 5                             DTFAWA-10-R-00039

              0                            1×10E-6**                 1×10E-3**                         1




                             Available*                Degraded                    Unavailable
                                                    (Hysteresis state)
                        Degraded
                      (Soak interval)

             * Available and not in soak
             interval

             ** Adjustable
                                            Figure 3.1.4-1: Availability States


SPEC.3.1.5          Network-wide Reduction in Transponder Bandwidth

The modem and multiplexer components together must enable the user to achieve at least a 35%
reduction in transponder bandwidth compared to today’s bandwidth utilization (see Appendix H for
today’s bandwidth utilization).

SPEC.3.1.5.1       The modem must maintain the same BER performance and system margin while
maintaining or reducing the power spectral density (as measured at the transponder downlink) as specified
in SPEC.3.1.4. The modems currently use Quadrature Phase Shift Keying (QPSK) and VITERBI ¾ rate
FEC. The multiplexer current technology is Time Division Multiplexing (TDM) with sub-rate aggregate
output capability.



SPEC.3.2            Automatic Circuit Protection Switching

    In order to support the overall service availability requirements contained in Section Error! Reference
    source not found.SPEC.3.1.2, the ASTI system implements automatic circuit protection switching9
    functionality at the channel level for high availability services provided between Phase I sites.


SPEC.3.2.1          General

SPEC.3.2.1.1        All ASTI Phase I sites must support automatic circuit protection switching
functionality.10

SPEC.3.2.1.2       All ASTI Phase I sites supporting automatic circuit protection switching must switch at
the channel level.



9
  Automatic Circuit Protection Switching (ACPS) describes the required functionality, which may be implemented
in a variety of ways. SPEC.4.4 includes additional switch requirements when ACPS is implemented at the physical
layer through a mechanical switch.
10
   The automatic circuit protection switching capability may be integral to the multiplexer component or it may be
distributed over multiple components.
10/07/10                                               SECTION J-1: ASTI TECHNICAL SPECIFICATION - 10
ASTI                                            Amendment 5                                DTFAWA-10-R-00039

SPEC.3.2.2          Automatic Circuit Protection Switching Requirements

     The following provides high-level generic automatic circuit protection requirements. ASTI automatic
     circuit protection switching systems must support the following functions:

SPEC.3.2.2.1       The automatic circuit protection switching function must provide detection and
reporting of telecom signal defects and failures at the channel and aggregate levels11.

SPEC.3.2.2.2      The automatic circuit protection switching function must provide in-service monitoring
and reporting of aggregate-level performance (e.g., BER).

SPEC.3.2.2.3    The automatic circuit protection switching function must provide status (Available,
Degraded, or Unavailable) and reporting of active and back-up aggregates.

SPEC.3.2.2.4     Automatic circuit protection switching must be implemented at the channel level based
on aggregate performance.

SPEC.3.2.2.5        The automatic circuit protection switching function must perform protection switching
of service(s) to a backup channel if the working channel status is Unavailable (and the backup channel
status is better).

SPEC.3.2.2.6        The automatic circuit protection switching function must perform protection switching
of service(s) to a backup channel if the working channel status is Degraded (and the backup channel state
is Available).

SPEC.3.2.2.7      The automatic circuit protection switching function must support both the revertive and
non-revertive12 automatic protection switch operating modes.

SPEC.3.2.2.8      The automatic circuit protection switching function must support assigning either path
(A or B) as the preferred path at the channel level.

SPEC.3.2.2.9       The automatic circuit protection switching function must support remote automatic
circuit protection switch control (e.g., remote override of automatic protection switch operation, including
a “Force To” function).

SPEC.3.2.2.9.1 The automatic circuit protection switching function must support manual switching
remotely on a single circuit at either end using a single control.

SPEC.3.2.2.9.2 The automatic circuit protection switching function must support manual switching
remotely on a single circuit at both ends using a separate single control.

SPEC.3.2.2.9.3 The automatic circuit protection switching function must support manual switching for
all circuits associated with an aggregate as a group at both ends using a separate single control.

SPEC.3.2.2.9.4      Switching of one circuit must not affect the operation of another circuit.

SPEC.3.2.2.10    From the time of failure or state change, the average circuit switching time must not
exceed 20 seconds, including all verification and reporting.


11
  Signal defects and failures are defined by the equipment designer based on telecom industry standards
12
  Revertive mode automatically switches traffic back to the restored preferred channel. Non-revertive mode only
switches upon failure of the working channel.

10/07/10                                         SECTION J-1: ASTI TECHNICAL SPECIFICATION - 11
ASTI                                               Amendment 5                                  DTFAWA-10-R-00039

SPEC.3.2.2.11    From the time of failure or state change, the maximum circuit switching time must not
exceed 30 seconds, including all verification and reporting.



SPEC.3.3            System Latency

SPEC.3.3.1    The ADP-to-ADP Latency13 must be less than or equal to 300 ms including the Space
        Segment.



SPEC.3.4            Compatibility with Existing Space Segment

SPEC.3.4.1          ASTI Space Segment

SPEC.3.4.1.1        All equipment proposed for ASTI must be compatible with the current ASTI space
segment.

SPEC.3.4.1.2      The upgraded ground station equipment must not degrade the current link designs i.e.,
reduce the current link margins for signal fades. See Appendix H.

SPEC.3.4.1.2SPEC.3.4.1.3 Satellite bandwidth apportioning between sites must be by discrete carrier
Frequency Division Multiplexing.

SPEC.3.5            Interoperability Requirements

SPEC.3.5.1          Component Compatibility

SPEC.3.5.1.1     When a new ASTI component is transitioned, it must interoperate with ASTI legacy
components that have not transitioned.



SPEC.3.6            Network Timing Architecture and Requirements14

The current ASTI network is synchronized via clock signals generated by Laurus Tiempo network clock
box timing sources located at each of the hub ground stations; these timing sources are available for
vendor use. Please refer to Appendix E Sub-section 1.1.3 for details concerning the current ASTI
network synchronization scheme.

SPEC.3.6.1          Network Timing Synchronization

SPEC.3.6.1.1        ASTI network timing signals must be traceable to the existing network clock box
timing sources.

SPEC.3.6.1.2        ASTI network must accommodate fall back network timing source(s).

13
  Latency is defined as the mean delay experienced by user information (analog or digital) during transit between
the input and output points. For bi-directional services, the round trip delay (i.e., circuit looped back at the far end)
may be measured and divided by two to determine the service Latency.
14
  This should not be confused with Time Of Day (TOD) synchronization, which is used for reporting purposes only
and is defined in section 5.8.1.2.
10/07/10                                            SECTION J-1: ASTI TECHNICAL SPECIFICATION - 12
ASTI                                            Amendment 5                                 DTFAWA-10-R-00039

SPEC.3.6.1.3       Every multiplexer must allow for a user configurable hierarchy of multiple clocking
inputs.

SPEC.3.6.1.4      Remote ASTI facilities must receive the network timing signal from ZAN through a
primary or alternate satellite path.

SPEC.3.6.1.5     Remote ASTI facilities, excluding SYA, must be capable of receiving a fallback
network timing signal from a location other than ZAN through a primary or alternate satellite path.

SPEC.3.6.1.6       Hub ASTI facilities must be capable of receiving network timing from another hub
facility.



SPEC.3.7           Facility and Equipment Requirements

SPEC.3.7.1         Equipment15 and Enclosure Space Requirements

SPEC.3.7.1.1       Limited and Distributed Space Available

SPEC.3.7.1.1.1 The ASTI equipment must be sized to permit access through existing doorway(s) and
installed in available ASTI FAA-provided space, unless otherwise approved by the FAA.

SPEC.3.7.1.1.2 The ASTI equipment must be installed and located in the existing enclosures or if
approved by the FAA, in new enclosures16 on the existing floor space at each facility.

SPEC.3.7.1.1.2.1 The ASTI equipment may be installed in new enclosures at temporary locations at each
facility, but must not exceed the maximum floor space requirements delineated in Table 3.7.1-1 below.

SPEC.3.7.1.1.2.2 ASTI Hub NMCS equipment must be installed in new enclosures IAW section SPEC.5.

SPEC.3.7.1.1.3 New ASTI equipment enclosures must not exceed the maximum permanent enclosure
space allocations for floor and enclosure space delineated in Table 3.7.1-1. Space allocations apply to
the sum of all space that ASTI equipment takes whether distributed throughout the facility or
concentrated in a single location within the facility.


SPEC.3.7.1.2       Equipment Enclosures

SPEC.3.7.1.2.1 ASTI equipment that is rack mountable must be capable of being mounted in the
existing standard “19 inch” enclosures.

SPEC.3.7.1.2.2     New enclosures must comply with the following requirements:

SPEC.3.7.1.2.2.1 Outside dimensions of the width and depth of each enclosure must not exceed the
dimensions as delineated in Table 3.7.1-2.

SPEC.3.7.1.2.2.2 Maximum outside height dimension for new enclosures must not exceed 84” and
contain a minimum of 42 rack units (RU) equivalents.


15
   Equipment referred to in this section includes all replaced components and support hardware necessary to meet
the technical requirements of this specification.
16
   For purposes of this specification, cabinet and enclosure are synonyms and are defined in appendix K.
10/07/10                                          SECTION J-1: ASTI TECHNICAL SPECIFICATION - 13
ASTI                                        Amendment 5                              DTFAWA-10-R-00039

SPEC.3.7.1.2.2.3 Enclosures must be configurable to allow for the following options: door front, door
rear, door locks, and removable side panels.

SPEC.3.7.1.2.2.4 Enclosures must contain at a minimum front and rear rails.

SPEC.3.7.1.2.2.5 Rails inside the enclosures must be pre-threaded (10-32) at increments specified by
EIA-310D for ease of equipment installation and removal.

SPEC.3.7.1.2.2.6 Enclosures must provide a full length pre-threaded (minimum of twenty 10-32 tapped
holes) ground bar IAW FAA-STD-019E.

SPEC.3.7.1.2.2.7 Enclosures must have two each racked outlet bars with minimum 12 NEMA 5-15
outlets using a NEMA L5-20 plug.

SPEC.3.7.1.2.2.8 Convenience power outlets must be provided on toe kick front and back for connection
to GFE breaker.

SPEC.3.7.1.2.2.9 Enclosure colors must be FAA approved.

SPEC.3.7.1.2.3   Blank panels must be used to fill unoccupied front rail space greater than or equal to
one RU.

SPEC.3.7.1.2.3.1 Where blank panels are used, they must be black and no larger than three RU.

SPEC.3.7.1.2.4   All enclosure mounting hardware (i.e. screws, washers) must be stainless steel.

SPEC.3.7.1.2.5 All ASTI indoor enclosures must be capable of keeping the ambient temperature in the
rack to within +/-5° C of ambient room temperature.

SPEC.3.7.1.2.5.1 ASTI equipment must meet the requirements listed in Table 3.7.1-1 and Table 3.7.1-2.




10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 14
ASTI                                                    Amendment 5                                     DTFAWA-10-R-00039

                         Maximum Permanent Enclosure Space (existing)          Maximum Transition          Maximum Transition
                                                                              Floor Space (enclosure       Enclosure Space (in
      Facility     ADP        Modem      MUX       RF     NMCS     Total     floor space equivalents)      existing enclosures)

Phase I Remote
Sites

MEB 8’x18’ &         1           1         1        *      ***          3             None                        18 RU
 8’x20’ sites
RCAG Bldgs.
ANI, CDV

MEB 8’x22’ &         1           1         1        *      ***          3               1                         18 RU
 10’x24” sites
VOR Bldgs.
ORT, MDO

BET, CDB, MCG        2           1         1        *      ***          4               1                         18 RU

AKN                  1           1         2        *      ***          4               1                         18 RU

ZSE                  1           2         2        *      ***          4               1                         18 RU

Phase II Remote                                                                                                   18 RU
Sites

All except IKO      **          **         **       *      ***          1             None                        18 RU

IKO                 **          **         **       *      ***          1             None                        None

AFSS Hub Sites

ENA                  4           7         9        2       1           22              2                           0

FAI                  5           6         7        2       1           20              2                           0

JNU                  3           4         6        2       1           15              2                           0

ZAN ARTCC           20          16         28       4       5           68              6                           0




           * RF Equipment at remote sites is either mounted outside, on an interior wall or on a seismic rack.
           ** All components in same rack.
           *** Included in ADP

                                  Table 3.7.1-1 Space Allocations for ASTI equipment




10/07/10                                                 SECTION J-1: ASTI TECHNICAL SPECIFICATION - 15
ASTI                                             Amendment 5                         DTFAWA-10-R-00039




                                  Enclosure Outside Dimensions             Enclosure Inside Dimensions
Facility Enclosure
Types
                               Width         Depth          Height      Width        Depth         Height

Phase I Remote Sites


     ADP Racks                  22.5”         25.5”          78.5”       19”          17.5           72”

     MUX Racks                  23”           26”             76”        19”          16.5           70”


     Modem Racks                23”           25.5”          78.5”       19”          17.5”          72”


Modem Rack 1 at ZSE             23”           25.5”          81.5”       19”          17.5”          71”


Modem Rack 2 at ZSE             23”           31”             82”        19”           21”          77.25”


Phase II Remote Sites


     Dual Rack                  48”           30”             72”        19”         1417.5”         61”


Hub Sites


     ADP                        22.5”         25.5”          78.5”       19”          17.5”          72”


     MUX                        23”           26”             76”        19”          16.5           70”


     Modem                      23”           31”             82”        19”           21”          77.25”


     RF racks 1 and 2           22”           30.5”          86.5”       19”          29.5”          78”

     RF racks 3 and 4           24”           30.5”           75”        19”          26.5”          70”


NMCS                            23”           32”             76”        19”           26"           70”




                               Table 3.7.1-2 Rack Dimensions for ASTI Components


SPEC.3.7.1.3            Health and Safety

SPEC.3.7.1.3.1 ASTI must comply with all relevant federal occupational safety and health standards,
including Occupational Safety and Health Administration (OSHA) 29 CFR 1910, Occupational Safety and
Health Standards (General Industry), 29 CFR 1926, Safety and Health Regulations for Construction,
National Fire Protection Association (NFPA) codes and standards, and all FAA Orders pertaining to
occupational safety and health, including but not limited to 3900.19B, FAA Occupational Safety and Health


10/07/10                                              SECTION J-1: ASTI TECHNICAL SPECIFICATION - 16
ASTI                                         Amendment 5                             DTFAWA-10-R-00039


Program, 3900.57, Pre-Construction and Maintenance Project Safety and Health Checklist, and
DOT/FAA/CT-03-05, HF-STD-001, Human Factors Design Standard.

SPEC.3.7.1.3.2 ASTI must comply with all relevant federal standards, FAA/DOT Orders and
Specifications, and consensus standards pertaining to electrical safety, including but not limited to 29 CFR
1910, Subpart S, Electrical, DOT Specification FAA-G-2100H, Electronic Equipment, General
Requirements, Section 3 (Requirements), National Fire Protection Association (NFPA) 70, National
Electrical Code®, and NFPA 70E, Electrical Safety in the Workplace.

SPEC.3.7.1.3.3 Electrical enclosures, junction boxes, power strips, cabling, and wiring used for ASTI
equipment must be approved by a nationally recognized testing laboratory, in accordance with requirements
in DOT Specification FAA-G-2100H, Electronic Equipment, General Requirements, Section 3
(Requirements).

SPEC.3.7.1.3.4 ASTI must meet Electrostatic Discharge (ESD) requirements referenced in FAA-STD-
019E, Lightning and Surge Protection, Grounding, Bonding and Shielding Requirements for Facilities and
Equipment, and DOT Specification FAA-G-2100H, Electronic Equipment, General Requirements.

SPEC.3.7.1.3.5 In accordance with NFPA 70E, Electrical Safety in the Workplace, and NFPA 70,
National Electrical Code®, ASTI must ensure that personnel are protected from arc flash hazards.

SPEC.3.7.1.3.6 ASTI must comply with FAA’s JO Order 3900.XX, Draft ATO Fall Protection Program,
FAA Order 3900.19, FAA Occupational Safety and Health Program, and all regulations and standards
governing fall protection, including 29 CFR 1910, Occupational Safety and Health Standards (General
Industry), and 29 CFR 1926, Safety and Health Regulations for Construction.

SPEC.3.7.1.3.7 ASTI equipment shall be designed to avoid and minimize fire hazards in accordance with
DOT/FAA/CT-03-05, HF-STD-001, Human Factors Design Standard, Chapter 12.11, Fire Protection.

SPEC.3.7.1.3.8 Exits in the building or structure where ASTI equipment is housed must be arranged and
maintained to provide free and unobstructed egress from all parts of the building/structure at all times when
it is occupied.

SPEC.3.7.1.3.9    Installation of ASTI equipment must not impact building fire stops and/or floor
penetration.

SPEC.3.7.1.3.10 ASTI equipment must be handled in accordance with applicable material handling
requirements, including but not limited to FAA Order 3900.19B, FAA Occupational Safety and Health
Program, and all relevant regulations and standards including 29 CFR 1910, Occupational Safety and
Health Standards (General Industry), Subpart N, Materials Handling and Storage. ASTI equipment shall be
designed and marked in accordance with DOT/FAA/CT-03-05, HF-STD-001, Human Factors Design
Standard, Chapter 12, Personnel Safety, and Chapter 4, Designing Equipment for Maintenance, and FAA-
G-2100H, Electronic Equipment, General Requirements.

SPEC.3.7.1.3.11 In accordance with 29 CFR 1910.132, Personal Protective Equipment (General
Requirements) and FAA Order 3900.19B, FAA Occupational Safety and Health Program, Chapter 25, the
Contractor must provide personal protective equipment (PPE) to Contractor personnel working on or near
ASTI equipment whenever it is necessary by reason of hazards of processes or environment, chemical
hazards, radiological hazards, or mechanical irritants.



10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 17
ASTI                                        Amendment 5                            DTFAWA-10-R-00039


SPEC.3.7.2       Power Requirements

SPEC.3.7.2.1     Power and Grounding Connections and Wiring

SPEC.3.7.2.1.1 Power connections with branch circuits must comply with FAA-C-1217F, Electrical
Work, Interior, FAA-STD-019E, Short Circuit Analysis and Protective Device Coordination Study,
National Fire Protection Association (NFPA) 70, National Electrical Code®, and state and local codes.


SPEC.3.7.2.1.2   Standard Power Wiring

SPEC.3.7.2.1.2.1 Power wiring must comply with the NEC and the requirements of FAA-STD-019E and
FAA-C-1217F.

SPEC.3.7.2.1.2.2 FAA-C-1217F, Electrical Work, Interior; note that FAA-C-1217F raises the minimum
requirements contained in NFPA 70.

SPEC.3.7.2.1.2.3 Equipment-grounding conductors must be routed and connected to minimize electrical
noise.

SPEC.3.7.2.1.2.4 ASTI equipment power cables, which are required to interface with facility power, must
be mechanically capable of interconnecting with the Government's designated facility power panels. The
interfaces are NEMA: 5-15, L5-20, L6-15 and L14-20.


SPEC.3.7.2.1.3   Equipment Grounding

SPEC.3.7.2.1.3.1 ASTI equipment installed must comply with design practices specified in FAA-G-2100H,
Section 3.1.1.9, titled Grounding and Bonding, and FAA-STD-019E.


SPEC.3.7.2.1.4   FAA Multi-point Ground System

SPEC.3.7.2.1.4.1 All connections to the FAA Multi-point Ground System must comply with FAA-STD-
019E.

SPEC.3.7.2.1.4.2 Non-current-carrying metal objects must be connected to the multi-point ground system.

SPEC.3.7.2.1.4.3 No power or signal returns must use the multi-point ground system as an intentional
ground path.

SPEC.3.7.2.1.4.4 Connections to the multi-point ground system must conform to the Bonding
Requirements of the FAA standards listed in FAA-STD-019E.


SPEC.3.7.2.2     Electrical Interface to Government Power Sources

SPEC.3.7.2.2.1 The ASTI equipment must operate on any of the following voltages/frequency of power
as designated by the Government.


10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 18
ASTI                                       Amendment 5                            DTFAWA-10-R-00039


             a) 120/240 VAC 60Hz nominal, single-phase
             b) 120/208 VAC 60 Hz nominal three-phase
             c) 120/208 VAC 60 Hz nominal single-phase (two-pole)

SPEC.3.7.2.2.2    ASTI equipment must comply with the requirements of FAA-G-2100H and FAA order
6950.2D.

SPEC.3.7.2.2.3 ASTI service must continue to operate without degradation when an interruption of 20
milliseconds or less occurs to the Government supplied power

SPEC.3.7.2.2.4 ASTI equipment being installed in the RF building at ZAN ARTCC must meet all critical
bus requirements contained in FAA orders 6950.2D Electrical Power Policy Implementation at National
Airspace Systems Facilities, Anchorage ARTCC Communications Systems Plan and 6470.33A Control of
Power, Space, and Environmental Interfaces at En route Air Traffic Control Facilities.

SPEC.3.7.2.3      Redundant Power Supplies

SPEC.3.7.2.3.1 Where used in the ASTI equipment, redundant power supplies must be wired to enable
each one to be connected to a separate source of power.


SPEC.3.7.3        Environmental Requirements

SPEC.3.7.3.1      Operating Environment

SPEC.3.7.3.1.1 ASTI equipment installed indoors must operate between 05° and +4540° C with humidity
from 0 to 95%, non-condensing at altitudes between zero (0) and 5,000 feet above mean sea level.

SPEC.3.7.3.1.2 ASTI equipment installed outdoors must operate between -40° and +40° C with relative
humidity between 0 % and 100%.

SPEC.3.7.3.1.3    ASTI equipment must operate at altitudes between zero (0) and 105,000 feet above mean
sea level.

SPEC.3.7.3.1.4 ASTI equipment exclusively for use indoors must be capable of withstanding, without
sustaining damage, storage in ambient temperatures between -40° to +70° C during transport.
SPEC.3.7.3.1.4                                                                                             Formatted: Normal


SPEC.3.7.3.1.5 ASTI equipment for outdoor use must be capable of withstanding, without sustaining
damage, storage in ambient temperatures between -40° to +70° C.


SPEC.3.7.3.2      Acoustic Noise

SPEC.3.7.3.2.1 ASTI equipment shall comply with DOT/FAA/CT-03-05, HF-STD-001, Human Factors
Design Standard, Chapter 12.12, Noise Hazards. The total acoustic noise generated by ASTI equipment
installed in any ASTI user location must not exceed the specifications defined in DOT Specification FAA-
G-2100H, Electronic Equipment, General Requirements, Section 3.3.6.1 (Noise Criteria Requirement).



10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 19
ASTI                                          Amendment 5                             DTFAWA-10-R-00039


SPEC.3.7.3.3      Ventilation

SPEC.3.7.3.3.1 All ventilation openings must be designed and located to comply with electromagnetic
interference requirements as specified in Section Error! Reference source not found.SPEC.3.7.3.5.

SPEC.3.7.3.3.2 All air ventilation equipment supplying ventilation to an equipment enclosure
(SPEC.3.7.1.2 ) must utilize air filters.

SPEC.3.7.3.3.3    Air filters must not project outside the equipment enclosure.

SPEC.3.7.3.3.4    Any new air filter equipment mounted in racks must use disposable filters.


SPEC.3.7.3.4      Fire Resistance

SPEC.3.7.3.4.1    ASTI equipment and cables must comply with the fire resistance requirements of:
           a)    NFPA 70
           b)    State government
           c)    Local government, as appropriate
           d)    Local airport authority codes, as appropriate for the particular installation


SPEC.3.7.3.5      Electromagnetic Compatibility

SPEC.3.7.3.5.1 ASTI equipment must operate without causing malfunction or discernible electromagnetic
interference to the operation of other equipment.

SPEC.3.7.3.5.2 ASTI components must operate in proximity to L-Band military or FAA radar systems
and other equipment causing radio frequency interference (e.g., L-Band, X-Band, Beacon, Mode S,
TACAN/DME, and ADS-B) IAW Sections SPEC.3 and SPEC.4 of this document.

SPEC.3.7.3.5.3 ASTI equipment must comply with the requirements of FAA-G-2100H, Section 3.3.2
Electromagnetic Compatibility and including FCC Type Acceptance IAW FCC Rules and Regulations.


SPEC.3.7.3.6      Protection of the Environment

SPEC.3.7.3.6.1 The design and installation of ASTI must comply with all relevant federal, state and local
regulations pertaining to protection of the environment, including but not limited to, air emissions limits on
equipment and local noise ordinances.


SPEC.3.7.3.7      Hazardous Materials

SPEC.3.7.3.7.1 ASTI equipment must be delivered free of asbestos, polychlorinated biphenyls (PCBs),
lead (except for lead-acid batteries, and lead-based solder on circuit boards if no acceptable substitute is
available), mercury-containing equipment, any Class I ozone-depleting substances (ODSs), and some Class
II ODSs (i.e., HCFC-22, HCFC-141b, and HCFC-142b) in accordance with relevant federal regulations and
FAA Orders. These include, but are not limited to: FAA Order 1050.10C, Prevention, Control, and
Abatement of FAA Environmental Pollution, FAA Order 1050.20A, Airway Facilities Asbestos Control

10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 20
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


Program, FAA Order 1050.14A, Polychlorinated Biphenyls (PCBs) in the National Airspace System
(NAS), and 40 CFR Part 82, Protection of Stratospheric Ozone.

SPEC.3.7.3.7.2 The use of all other hazardous materials in the design, manufacture, and installation of
ASTI equipment must be minimized to the extent possible.


SPEC.3.7.4       Installation Requirements

SPEC.3.7.4.1     General

SPEC.3.7.4.1.1 ASTI equipment must be installed IAW the following:
           a) National Electrical Code (NFPA 70)
           b) FAA Order 6630.4A, En-route Communications Handbook
           c) FAA-STD-019E, Lightning Protection, Grounding, Bonding, and Shielding Requirements
              for Facilities
           d) FAA-C-1217F, Electrical Work, Interior; note that FAA-C-1217F raises the minimum
              requirements contained in NFPA 70
           e) FCC Part 25
           f) State and local government codes and regulations
           g) Local airport authority codes and guidelines (if applicable)
           h) FAA Order JO 6580.3B Remote Communications Facilities Installations Standards
              Handbook
           i) FAA Order 6630.4A En route Communications Handbook
           j) FAA-G-2100H, Electronic Equipment, General Requirements


SPEC.3.7.4.2     Equipment Mounting

SPEC.3.7.4.2.1 ASTI equipment utilizing enclosure mounting must use standard Electronic Industries
Association-310 (EIA-310) mounting methods. In addition to using enclosure mounting, the following
mounting methods may be used:

SPEC.3.7.4.2.1.1 Wall mounting (for RF equipment only)

SPEC.3.7.4.2.1.2 Equipment packaged in stand-alone units

SPEC.3.7.4.2.2 Block Up Converter / Solid State Power Amplifier (BUC/SSPA), Up Converters, SSPA,
and Down Converter components must be mounted in the equipment shelter unless the system design /
length of the Intra Facilities Link (IFL) requires that they must be located closer to the antenna.

SPEC.3.7.4.2.3 Components equipped with dual power supplies must be connected to dual independent
power sources, i.e., branch circuits on separate breakers.


SPEC.3.7.4.3     Cable Routing

SPEC.3.7.4.3.1 Cables must be run in cable trays, conduits, or under raised floors in cable trays or conduit
with appropriate separation of the power and Signal Cables IAW FAA-STD-019E, FAA-C-1217F, and
FAA Order 6950.2D.

10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 21
ASTI                                         Amendment 5                              DTFAWA-10-R-00039


SPEC.3.7.4.3.2    When routing cables within racks the contractor must use industry best standards.


SPEC.3.7.4.4      Seismic Safety

SPEC.3.7.4.4.1 ASTI equipment must be constructed and anchored in accordance with current seismic
safety and earthquake protection requirements for Seismic Zone 4 of the local and national building codes
(Uniform Building Code - UBC, Sections 2330-2338, National Building Code - BOCA, and Standard
Building Code - SBCCI), and DOT Specification FAA-G-2100H, Electronic Equipment, General
Requirements, Section 3.3.5, Personnel Safety and Health.


SPEC.3.7.5        System Level Requirements

SPEC.3.7.5.1       System Cold Start - any site must return to service from a powered off state to an
operational state in 5 minutes or less.

SPEC.3.7.5.2       System Cold Start - any site must return to service from a powered off state to an
operational state in 5 minutes or less.



SPEC.3.7.5.3      Transmitter Gain Flatness and Phase Noise

SPEC.3.7.5.3.1    The combined Converter/SSPA or BUC/SSPA must meet the following:
                           a) Transmit Phase Noise: -80dbc/hz @ >10khz
                           b) Gain Flatness: ± .75dB over full RF band; : ± .75dB per 36Mhz


SPEC.3.7.5.4      Intermodulation

SPEC.3.7.5.4.1 The combined Converter/SSPA or BUC driven by transmission of multiple carriers, must
not exceed SSPA intermodulation with 2 equal carriers:
            a) Saturation: -9 dBc
            b) Saturation -7dB: -16 dBc
            c) Saturation -14 dB: -27 dBc


SPEC.3.7.5.5      System Voice Grade Channel

SPEC.3.7.5.5.1 The operating parameters of a circuit (ADP to ADP) must meet the VG as required to
meet the various levels as described in SPEC 4.4.4.1.


SPEC.3.7.5.6      System Digital Grade Channel

SPEC.3.7.5.6.1 The ADP to ADP system digital grade channel Bit Error Rate (BER) must be better than 1
x 10 e-6 through all devices with zero error seconds over a calculated period of time (dependent on the
speed of the circuit).

10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 22
ASTI                                        Amendment 5                              DTFAWA-10-R-00039


SPEC.3.7.6       Equipment Identification

SPEC.3.7.6.1     Equipment and Rack Labeling

SPEC.3.7.6.1.1   All ASTI equipment and racks must be labeled as specified in Appendix G.


SPEC.3.7.6.2     Cable Labeling and Markings

SPEC.3.7.6.2.1   ASTI cabling must be labeled as specified in Appendix G.

SPEC.3.7.6.2.2 In addition to the requirements in Appendix G, Equipment grounding conductors must be
appropriately color-coded. All ASTI-provided cables must be clearly marked by indicating the following
location data on the cable ends:
                          a) enclosure
                          b) chassis
                          c) card (if applicable)
                          d) connector

SPEC.3.7.6.2.3   Every cable must be uniquely identified by cable identifier.

SPEC.3.7.6.2.4 Cable labels must contain all other information that is required by MIL-STD-1472:
Sections 5.5.1, Labeling, General; 5.5.2, Labeling, Orientation; and 5.5.3, Labeling, Contents.

SPEC.3.7.6.2.5   All cable labels must be readable in situ.


SPEC.3.7.7       Cables and Connectors

SPEC.3.7.7.1     General

SPEC.3.7.7.1.1   All cables must not exceed 2.5 feet in excess of the required length.

SPEC.3.7.7.1.2 All cables must meet the requirements of the environment they transit (e.g. Outside,
Plenum, Inter-rack).

SPEC.3.7.7.1.3 All cabling and connectors connecting new components, and new components to legacy
components within the ADP must be replaced with new cables.


SPEC.3.7.7.2   Non-Ethernet Digital Data Cables for ASTI (e.g., Channel-level, Aggregate, and
NMCS Applications)

SPEC.3.7.7.2.1 All digital data cables must have a metallic back shell in contact with cable shielding
IAW Tyco Electronics Instruction Sheet 408-6609 or equivalent.

SPEC.3.7.7.2.1.1 COTS cables supplied with COTS equipment for intra-rack use are excluded from this
requirement.

SPEC.3.7.7.2.2   All digital data cables must have braided and foil shield with drain.

10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 23
ASTI                                         Amendment 5                            DTFAWA-10-R-00039


SPEC.3.7.7.2.3   All digital data connectors must allow for disassembly and pin extraction.

SPEC.3.7.7.2.3.1 All cable pins must be mil-spec crimp type IAW MIL-C-24308.

SPEC.3.7.7.2.3.2 COTS cables supplied with COTS equipment for intra-rack use are excluded from this
requirement.

SPEC.3.7.7.2.4   All serial cables must be certified IAW TBP.


SPEC.3.7.7.3     Coax/Waveguide for RF and IF Applications

SPEC.3.7.7.3.1   All RF connectors must be N Type unless otherwise specified.

SPEC.3.7.7.3.2 Coaxial cable for RF frequencies greater then 100MHz must be constructed with a
corrugated solid copper outer jacket and copper clad or solid inner-conductor (e.g., LDF4-50, FSJ1-50).

SPEC.3.7.7.3.2.1 Coaxial cable for RF frequencies greater then 100MHz used intra rack and internal to
COTS components are excluded from this requirement.

SPEC.3.7.7.3.3 Coaxial cable for RF frequencies less then or equal 100MHz must be constructed with a
braided copper outer jacket and solid inner-conductor (e.g., Belden 8281).

SPEC.3.7.7.3.4 All coax cables and waveguide must have a VSWR of 1.5:1 or better for the frequency
span of operation.

SPEC.3.7.7.3.5   Solderless (e.g., captive, crimped) connectors must be used, when commercially
available.

SPEC.3.7.7.3.5.1 Connectors using crimped center pins must use 12 pt crimpers when available.

SPEC.3.7.7.3.5.2 All crimps must use the manufacturer recommended tooling.

SPEC.3.7.7.4     All coax connectors must be matched to the specific cable type.

SPEC.3.7.7.4.1   Adaptors are not allowed.


SPEC.3.7.7.5     Ethernet Cables for ASTI (e.g., Channel-level and NMCS Applications)

SPEC.3.7.7.5.1 The NMCS must follow the FAA ATO Network Standards version 1.2 or higher, for
LAN Cable Specifications. In addition, the NMCS LAN cabling must also comply with the following:

SPEC.3.7.7.5.1.1 Type STP Category 5E, or better, network cable must be used and must comply with or
exceed the requirements of EIA/TIA 568-B and tested IAW EIA/TIA TSB67.

SPEC.3.7.7.5.1.2 Cables and connectors used outdoors must be rated for the environment that they will be
installed in. (e.g. MIL-DTL-26482H.)


SPEC.3.7.7.6     Voice Cables for ASTI (e.g., Channel-level Analog Voice Applications)
10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 24
ASTI                                        Amendment 5                               DTFAWA-10-R-00039


SPEC.3.7.7.6.1    Voice Cables transporting more than one voice circuit must be CAT 3 24AWG at a
minimum.

SPEC.3.7.7.6.2    Voice Cables transporting one voice circuit must be flat cord 26AWG at a minimum (e.g.
silver satin).


SPEC.3.7.7.7      Armored Cables

SPEC.3.7.7.7.1 Buried or external cables that use armor for mechanical protection must be bonded to the
Earth Electrode System (EES) at each end and immediately after entering the facility, shelter, building, or
immediately prior to attachment to outdoor ASTI equipment.


SPEC.3.7.8        General Equipment Requirements

SPEC.3.7.8.1      All remote equipment must use the same hardware, software and firmware from site to
site except where scale requires a different hardware model.

SPEC.3.7.8.2     All hub equipment must use the same hardware, software and firmware from site to site
except where scale requires a different hardware model.

SPEC.3.7.8.3       As installed, all new cables, connectors and mats for ASTI equipment must be arranged
so as not to present a trip hazard.



SPEC.4         Requirements for Replaced ASTI Components

This section contains requirements for the new ASTI telecommunications components. All components
provided under this contract must meet the requirements of FCC Part 25.

SPEC.4.1          Radio Frequency (RF) Components

This section contains requirements for ASTI Radio Frequency (RF) Components. C-band is used for
satellite uplink and downlink transmissions. The Intermediate Frequency (IF) used between the satellite
radios and the modems will be L-band or 70 MHz depending on the technical suitability which will be
determined on a site-by-site basis. Consequently, requirements are provided herein for both L-band and 70
MHz IF components.

SPEC.4.1.1        Radio Frequency Components - C-Band

SPEC.4.1.1.1      Solid State Power Amplifier (SSPA)

SPEC.4.1.1.1.1    The SSPA must comply with the specs of Table 4.1.1.1-1.
                     Parameter                                  Specifications/Requirements
   Frequency                                    5.925-6.425 GHz
   Output Power (Psat typical)                  600 W, 400 W, 200 W, 50 W, 30 W
   RF Level Adjust Range                        20 dB min. (via PIN diode attenuator)
   Gain Stability
   -- At constant drive & temp.                 ±0.25 dB24 hrs. max. (after 30 min. warm-up)
10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 25
ASTI                                        Amendment 5                               DTFAWA-10-R-00039


                    Parameter                                 Specifications/Requirements
  -- Over temp., constant drive,               ±1.5 dB over operating. temp. range
  -- (any frequency)                           ±0.75 dB over ±10°C
  Small Signal Gain Slope                      ±0.1 dBMHz max.
  Small Signal Gain Variation
  -- Across any 40 MHz band                    0.6 dB peak-peak max.
  -- Across the 500 MHz band                   2.5 dB peak-peak max.
  Input VSWR                                   1.30:1 max.
  Output VSWR                                  1.30:1 max.
  Load VSWR
  -- Continuous operation                      1.5:1
  -- Full spec compliance                      1.5:1
  -- Operation without damage                  Any value
  Residual AM, max
  -- below 10 kHz                              -50 dBc
  -- 10 kHz to 500 kHz,                        -20 (1.5 + log F kHz) dBc,
  -- above 500 kHz                             -85 dBc
  Phase Noise
  -- IESS-308/309 phase noise continuous       12 dB below mask
  -- AC fundamentals related                   -36 dBc
  -- Sum of spurs (370 Hz to 1 MHz)             -47 dBc
  AM/PM Conversion                             3.5°/dB max. for a single-carrier at 8 dB below rated power
                                               (at 3 dB back off with optional linearizer)
  Harmonic Output                              -60 dBc at P1dB-1dB, second and third harmonics, Psat >
                                               200W; -50dBc at P1dB-3dB, second and third harmonics ,
                                               Psat <= 200W.
  Noise and Spurious
  3.4 to 4.2 GHz;                              ≤ 130 dBW/4 kHz
  4.2 to 12.0 GHz;                             ≤ -65 dBW/4 kHz
  w/ optional linearizer                       ≤ 60 dBW/4 kHz
  12.0 to 40.0 GHz                             ≤ 110 dBW/4 kHz
  Inter-modulation                             -25 dBc max. with two equal carriers @ -3dB total backoff
                                               from P1dB (-6dBc single carrier level) separated by 1Mhz.
  Group Delay (in any 40 MHz band)
  -- linear max.                               0.03 ns/MHz
  -- parabolic max.                            0.003 ns/(MHz)2
  -- peak-peak ripple max                      1.0 ns.
  Shock and Vibration                          Designed for normal transportation Environment per Section
                                               514.4 MIL-STD-810E. Designed to withstand 20G at 11 ms
                                               (1/2 sine pulse) in non-operating condition.
  Acoustic Noise                               68 dBA (as measured at 3 ft.)
  Mechanical
  Cooling                                      Forced air w/ integral blower.
  RF Output Connection                         CPR-137 waveguide flange, grooved, threaded UNF 2B 10-
                                               32
  RF Output Monitor                            Type N Female using built in monitor port or an externally
                                               mounted cross wave guide coupler )
  Heat Dissipation
  -- Ducted                                    2000 W
  Management & Control                         Ethernet using outdoor rated connectors (e.g., Miniature
                                               Cylindrical Connector meeting MIL-C-26482)
                                       Table 4.1.1.1-1 SSPA Specifications
10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 26
ASTI                                          Amendment 5                               DTFAWA-10-R-00039




SPEC.4.1.1.2      Receive Band Pass Filter

SPEC.4.1.1.2.1    Receive Band Pass Filter performance must comply with the specs of Table 4.1.1.2-1.
                                  Parameter                 Specification/Requirement

                 Band pass                              3.7-4.2 GHz

                 Insertion Loss                         0.4 dB (Typical at Fo) 0.5 dB
                                                        (roll off at band edge)

                 VSWR                                   1.33:1 (max.)

                 Group Delay                            Less than 8 ns (Typical)

                 Rejection                              60 dB min
                 -- DC to 3.185 GHz

                 Rejection                              60 dB min
                 -- 4.55 to 11 GHz

                 Flanges

                 -- Input                               CPR229G

                 -- Output                              CPR229F



                                  TABLE 4.1.1.2-1 Band Pass Filter Specifications

SPEC.4.1.1.3      Waveguide switches

SPEC.4.1.1.3.1    Transmit waveguide switches must comply with the specs of Table 4.1.1.3-1
                                  Parameter                      Specification/Requirement

                 Frequency Range                        5.925 to 6.425 GHz

                 Waveguide Type / Size                  WR-137

                 VSWR                                   1.05:1 (Max)



10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 27
ASTI                                            Amendment 5                             DTFAWA-10-R-00039


                 Insertion Loss                            0.02 dB (Max)

                 Isolation                                 60 dB (Min)

                 Switching                                 60 msec (Typical)

                 Pressure                                  To 30 PSIG (RF Head)

                             Table 4.1.1.3-1 Transmit Waveguide Switch Specifications

SPEC.4.1.1.3.2    Receive waveguide switches must comply with the specs of Table 4.1.1.3-2
                                         Parameter                         Specification/Requirement

                        Frequency Range                          3.7 to 4.2 GHz

                        Waveguide Type / Size                    WR-229

                        VSWR                                     1.05:1 (Max)

                        Insertion Loss                           0.02 dB (Max)

                        Isolation                                80 dB (Min)

                        Switching                                100 msec (Typical)

                        Pressure                                 To 30 PSIG (RF Head)

                        Finish                                   Flange Face, Iridite

                             Table 4.1.1.3-2 Receive Waveguide Switch Specifications


SPEC.4.1.1.4      Terminations

SPEC.4.1.1.4.1    Transmit Terminations must comply with the specs of Table 4.1.1.4-1.
                                      Parameter                            Specification/Requirement

                   Frequency Range                               5.925 – 6.425 GHz

                   Type                                          Waveguide 137; or Type N

                   VSWR                                          1.10:1 (Max)

                   Power Rating                                  6 dB above max output power of equipment
                                                                 to be terminated

                                  Table 4.1.1.4-1 Transmit Terminations Specifications



10/07/10                                          SECTION J-1: ASTI TECHNICAL SPECIFICATION - 28
ASTI                                           Amendment 5                              DTFAWA-10-R-00039




SPEC.4.1.1.4.2    Receive Terminations must comply with the specs of Table 4.1.1.4-2.
                                       Parameter                            Specification/Requirement

                   Frequency Range                                  3.7-4.20 GHz

                   Type                                             Waveguide WR229 (CPRF 229 Flange)

                   VSWR                                             1.10:1 (Max)

                   Power Rating                                     6 dB above max output power of equipment
                                                                    to be terminated

                                Table 4.1.1.4-2 Receive Terminations Specifications


SPEC.4.1.2        Radio Frequency (RF) Components - L-Band IF

SPEC.4.1.2.1      Block Up Converter / Solid State Power Amplifier

SPEC.4.1.2.1.1 The BUC/SSPA must convert frequencies from the L-Band intermediate frequency to the
C band and amplify the signal for transmission to the satellite.

SPEC.4.1.2.1.2 All BUC/SSPAs must have integrated power supplies, synthesizers, and internal 10 MHz
reference signal generator.

SPEC.4.1.2.1.3    The BUC/SSPA must accept an external reference generator signal.

SPEC.4.1.2.1.4    The BUC/SSPA must comply with the specifications contained in Table 4.1.2.1-1.


                     Parameter                                   Specification/Requirement

       Input Frequency range –IF                   950-1450 or 950-1950 or 950-2050 MHz non-segmented

       Output Frequency range -RF                  5.85-6.425 GHz

       Output Power (Psat typical)                 600 W, 400 W, 200 W, 50 W, 30 W

       Gain Flatness over full band                ± 1.5 dB

       Gain variation over full band               ± 2 dB within operating temp range

10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 29
ASTI                                        Amendment 5                                DTFAWA-10-R-00039


                       Parameter                             Specification/Requirement

       Gain Flatness over 40 MHz segment      ± 0.5 dB

       Gain variation 40 MHz segment          ± 1 dB within operating temp range

       Gain Adjust                            20 dB in .25dB steps

       AM/PM conversion                       3.5º max @ rated P1dB

       RF mute isolation                      -60dBc minimum

       Input / Output Return Loss             14 dB min.

       Spurious at rated power                -60 dBc max

       Third order IMD (two equal tones 5     -26 dBc max @ 3 dB back off (SCL 6 dB back off from
       MHz apart)                             P1 db)

                                              Linear: ±0.03ns/Mhz
       Group Delay variation                  Parabolic: ±.003ns/Mhz2
                                              Ripple: ±1.0ns pk-pk

                                              -75 dBW/4 kHz in transmit band, -135 dBW/4 kHz from
       Noise Power Density
                                              3.7 to 4.2 GHz

       Phase Noise

       -- @ 1 KHz offset                      -75 dBc/Hz

       -- @ 10 KHz offset                     -85 dBc/Hz

       -- @ 100 KHz offset                    -95 dBc/Hz

       -- @ 1 MHz offset                      -105 dBc/Hz

       Physical Interfaces

       -- RF Input                            Type N Female

       -- RF Output                           CPR-137

                                              Type N Female using built in monitor port or an externally
       -- RF Output sample
                                              mounted cross wave guide coupler.

                                              Ethernet using outdoor rated connectors (e.g., Miniature
       -- Management and Control
                                              Cylindrical Connector meeting MIL-C-26482)

                                     Table 4.1.2.1-1 BUC/SSPA Specifications

SPEC.4.1.2.2         Block Up Converter – Indoor, Rack Mount

10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 30
ASTI                                           Amendment 5                             DTFAWA-10-R-00039


SPEC.4.1.2.2.1 The indoor, rack mounted BUC must convert frequencies from the L-Band intermediate
frequency to C band for output to an indoor rated SSPA.

SPEC.4.1.2.2.2 The indoor, rack mounted BUC must have integrated power supplies, synthesizers, and
internal 10 MHz reference signal generator

SPEC.4.1.2.2.3     The indoor, rack mounted BUC must accept an external reference generator signal

SPEC.4.1.2.2.4 All indoor, rack mounted BUC’s must comply with the specifications contained in
Table 4.1.2.2-1.


                                Parameter                           Specification/Requirement

                 Frequency Range                         950 – 2050 MHz

                 Input Return Loss                       15dB (min)

                 Output Return Loss                      18dB (min)

                 Amplitude Response (Band)               ±1dB

                 Variable Gain Control                   20dB

                 Nominal Input Level                     -25 dBm

                 Gain Stability (24hrs)                  ±0.25dB

                 3rd Order Intercept                     18dBm

                 Output Power (P1dB)                     15dbm

                 Frequency Stability (temperature)       ± 2 x 10-8

                 Frequency Stability (temperature)       ± 5 x 10-9

                 Input/Output Impedance                  50 ohm

                 Operating Temperature                   0 to 50 º C

                 Operating Relative Humidity (@30 º C)   95% non condensing

                 Management and Control                  Ethernet

                             Table 4.1.2.2-1 Indoor Rack Mounted BUC Specifications


SPEC.4.1.2.3       Low Noise Block Converter (LNB)

SPEC.4.1.2.3.1     LNBs must be powered over the L-Band IF coaxial cable.

SPEC.4.1.2.3.2     LNBs must receive external clock signal through the L-Band IF coaxial cable.
10/07/10                                         SECTION J-1: ASTI TECHNICAL SPECIFICATION - 31
ASTI                                          Amendment 5                                 DTFAWA-10-R-00039


SPEC.4.1.2.3.3   The LNB must comply with the specs contained in Table 4.1.2.3-1.
                            Parameter                    Specification/Requirement

                   Input Frequency            3.7 to 4.2 GHz

                   Output Frequency           950 - 1450 MHz or 950-1950 or 950-2150 MHz

                   Noise Temperature          30°K @ 25°C

                   Gain                       60 dB

                   Gain Flatness              ±0.5dB Max per 40MHz segment

                   Gain Flatness              ± 2.5 dB pk-pk per 500 MHz

                   Image Rejection            45 dBc Min

                   Output VSWR                2.5:1 Max

                   LO Frequency Stability     ± 25 KHz

                   Phase Noise                -75 dBc/Hz @ 1 KHz

                   Input Interface            Flange, WR 229G

                   Output Interface           Type N Female

                               Table 4.1.2.3-1 Low Noise Block CONVERTER Specifications


SPEC.4.1.2.4     Band Pass Filter

SPEC.4.1.2.4.1   Band pass filter performance must comply with the specification of Table 4.1.2.4-1.
                                  Parameter                      Specification/Requirement

                 Band Pass                                     0.9 – 1.45 GHz

                 Insertion Loss                                0.5 dB (Max)

                 VSWR                                          1.3:1 (Typical)

                 Group Delay                                   Less than 8 ns (Typical)

                 -- Input                                      Type N

                 -- Output                                     Type N

                 Impedance                                     Impedance must match the
                                                               system cable and component
                                                               impedances.

10/07/10                                        SECTION J-1: ASTI TECHNICAL SPECIFICATION - 32
ASTI                                            Amendment 5                            DTFAWA-10-R-00039


                                     Table 4.1.2.4-1 Band Pass Filter Specifications




SPEC.4.1.2.5        Combiner and Divider

SPEC.4.1.2.5.1      The combiner and divider components must comply with the specs of Table 4.1.2.5-1
                            Parameter                            Specification/Requirement
           Frequency                                   0.8 – 2.2 GHz
           Power                                       6 dB greater than application
           Isolation                                   20 dB (Min)
           Insertion Loss                              0.3 dB
           Amplitude Balance                           0.1 dB (Max)
           Phase Balance                               2 Deg (Max)
           VSWR
           -- Input                                    1.15:1 (Max)
           -- Output                                   1.15:1 (Max)
           Power Pass Capability                       Yes, as required
           Connector(s)                                Type N, type BNC where Type N is not
                                                       commercially available
           Impedance                                   Impedance must match the component and cable
                                                       requirements.
                                   Table 4.1.2.5-1 Combiner and Divider Specifications



SPEC.4.1.2.6        Terminations

SPEC.4.1.2.6.1      Terminations must comply with the specs of Table 4.1.2.6-1.
                                    Parameter                  Specification/Requirement

                     Frequency Range                       0.9 – 1.45 GHz

                     Type                                  Type N

                     VSWR                                  1.10:1 (Max)

                     Power Rating                          Contingent on application
                     Impedance
                                                           Impedance must match the
                                                           component and cable requirements.

                                       Table 4.1.2.6-1 Terminations Specifications




10/07/10                                         SECTION J-1: ASTI TECHNICAL SPECIFICATION - 33
ASTI                                              Amendment 5                               DTFAWA-10-R-00039


SPEC.4.1.2.7        DC Blocks

SPEC.4.1.2.7.1      DC block must comply with the specs of Table 4.1.2.7-1.
                                 Parameter                      Specification/Requirement
                     Frequency Range:                    5MHz –2050 MHz
                     VSWR:                               1.35:1 (Max)
                     Insertion Loss:                     0.5 dB (Max)
                     Material:                           Stainless Steel
                     Voltage Maximum:                    200 VDC
                     Type                                Center Pin Block
                     Connector (Input & Output)          Type N

                                        Table 4.1.2.7-1 DC Block Specifications


SPEC.4.1.2.8        Remote ASTI Facility Reference Source (e.g., 5/10 MHz)

SPEC.4.1.2.8.1      Reference source must comply with the specs of Table 4.1.2.8-1.
                         Parameter                                Specifications/Requirements
       Impedance                                       50 Ohms or 75 Ohms
       Return Loss                                     >18 dB
       Frequency                                       As required
       Output Level Tolerance                          ± 1 dBm
       Harmonics                                       < -30 dBC, < -40 typ.
       Spurious                                        < -75 dBC
       Oscillator Stability
       -- Over temperature                             ± 0.01 ppm max 0°C to +50°C
       -- Aging, per day                               ± 0.001 ppm
       -- Aging, per year                              ± 0.1 ppm
       -- Warm up, in 4 minutes                        ± 0.1 ppm
       -- Warm up, in 1 hour                           ± 0.01 ppm
       -- Mechanical adjustment                        ± 1 ppm
       Oscillator Phase Noise
       -- Phase Noise @ Freq                           dBC/Hz
       ---- 10Hz                                       < -110 dBC/Hz
       ---- 100Hz                                      < -140 dBC/Hz
       ---- 1kHz                                       < -149 dBC/Hz
       ---- 10kHz                                      < -149 dBC/Hz

                            Table 4.1.2.8-1 Oscillator/Synthesizer Source Specifications



10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 34
ASTI                                         Amendment 5                              DTFAWA-10-R-00039


SPEC.4.1.2.9      Bias-T

SPEC.4.1.2.9.1    Bias-Ts must comply with the specs of Table 4.1.2.9-1.
                     Parameter                              Specifications/Requirements
       Frequency Range :                         900 - 2050 MHz
       DC Current Input :                        Max DC current supplied compatible with selected LNB.
       Insertion Loss:
       900-1525 MHz :                            1.5 dB max.
       10 MHz :                                  Compatible with selected LNB.
       Input Impedance :                         50 OHM
       Output Impedance :                        50 OHM
       In/Out VSWR :                             2:1 max
       Input Connector :                         N Type 50 OHMS
       Output Connector :                        N Type 50 OHMS
       10 MHz Reference Connector :              N Type 50 OHMS
       DC Connector :                            Optional:
                                                 L.P.F. Solder pin
                                      Table 4.1.2.9-1 BIAS-T Specifications



SPEC.4.1.2.10     L-Band IF distribution panel

SPEC.4.1.2.10.1 The new ASTI RF components must include an L-Band IF distribution panel which must
be a rack mounted chassis that contains, at a minimum, a network of splitter(s), divider(s), filter(s), and
monitoring jack(s). The L-Band IF distribution panel interfaces satellite modem(s) to the RF equipment
and may contain one or more networks to accommodate multiple satellites.

SPEC.4.1.2.10.1.1        The L-Band IF distribution panel must support the capability to physically "open"
the uplink and downlink path, from the front panel, insuring that no signal is transmitted to or received from
the satellite during maintenance activities.

SPEC.4.1.2.10.1.2        The L-Band IF distribution panel must provide coupled monitor ports for test
access for each uplink and downlink path.

SPEC.4.1.2.10.1.3       The L-Band IF distribution panel must have the ability to monitor signal downlink
when the looping plug is removed.

SPEC.4.1.2.10.1.4        The L-Band IF distribution panel must have the ability to monitor signal downlink
when the looping plug is installed.

SPEC.4.1.2.10.1.5       Cabling for the L-Band IF distribution panel must have solid copper shield with
appropriate bend radius (e.g., FSJ1-50).

SPEC.4.1.2.10.1.6       Solderless (e.g., captive, crimped) connectors must be used, when commercially
available.

SPEC.4.1.2.10.1.7       Connectors using crimped center pins must use 12 pt crimpers when available.

SPEC.4.1.2.10.1.8          All crimps must use the manufacturer recommended tooling.


10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 35
ASTI                                         Amendment 5                             DTFAWA-10-R-00039


SPEC.4.1.2.10.1.9    All external connections to the L-Band distribution panel must be through Type N
50 Ohm female bulkhead connectors.

SPEC.4.1.2.10.1.10      Within the L-Band distribution panel all connectors may use BNC type quick-
release connectors.

SPEC.4.1.2.10.1.11      The contractor must size the different IF distribution panels to comply with the
following configurations:
            a) Four modems selected through two 1:1 switches to one satellite.
            b) Four modems to two satellites. Two each per satellite.
            c) Eight modems to two satellites. Four each per satellite.
            d) M:N modem switch to two satellites.
            e) M:N modem switch to one satellite.
            f) One to eight modem switches to one satellite.
            g) One to sixteen modem switches (up or downlink) to one satellite.


SPEC.4.1.2.11     Signal Interface Requirements

SPEC.4.1.2.11.1 The BUC/SSPA RF output signal requirements are provided in Table 4.1.2.1-1.

SPEC.4.1.2.11.2 The LNB RF input signal requirements are provided in Tables 4.1.2.3-1.


SPEC.4.1.2.11.3 L-Band Intermediate Frequency (IF) Signal

SPEC.4.1.2.11.3.1   The L-Band IF output frequency must operate between 950 MHz to 1450 MHz, or
950 MHz to 1950 MHz or 950 MHz to 2150 MHz.

SPEC.4.1.2.11.3.2       The interfaces for standard L-Band transmit and receive spectrum must support
both inverted and non-inverted signals (user configurable).

SPEC.4.1.2.11.3.3         Signals (data, reference frequency, monitor & control) and power provided over the
L-Band IF must be compatible with the modem(s) and associated components selected. Specific
requirements are left to the system designer / integrator.


SPEC.4.1.3        Radio Frequency (RF) Components - 70 MHz IF

SPEC.4.1.3.1      Up Converter

SPEC.4.1.3.1.1 The up converter must accept signals from the IF combining / distribution system and
convert them through a dual-conversion balanced mixing process to the final RF transmit frequency.

SPEC.4.1.3.1.2 The up converter must suppress carrier signals used in the mixing processes and provide
an adjustable amplified output for application to the SSPA.

SPEC.4.1.3.1.3    Up Converter performance must comply with the specs of Table 4.1.3.1-1.
                 Parameter                                   Specifications/Requirements
IF Frequency Range                              50-90 MHz

10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 36
ASTI                                             Amendment 5                                DTFAWA-10-R-00039


                   Parameter                                         Specifications/Requirements
IF Return Loss                                         ≥ 20 dB
IF Noise Figure                                       ≤ 15 dB
RF Frequency Range                                    5.85-6.425 GHz
RF Return Loss                                        ≥ 20 dB
RF Spurious-Non-Carrier                               ≤ -80 dBm
RF Spurious-Carrier (Carrier leakage)                 ≤ -60 dBm
RF Output Level Adjustment Range                      20 dB Min
Third Order Inter-modulation at 10 dB backoff         ≤ -50 dBc
from rated output power
Third Order intercept                                 ≥ 23 dBm
Conversion-Gain                                       Conversion-Gain must match the output frequencies, impedance,
                                                      and levels of the IF system to the input to the SSPA without
                                                      inversion, distortion, or degradation in spectrum quality.
Gain Flatness                                         ≤ 0.5 dB
Gain Stability vs. Temperature at 0-50 Deg C          ≤ ± 1 dB
Gain Stability vs. Temperature: 24 Hr. at constant    ≤ ± 0.25 dB
drive and temp.
AM/PM conversion at rated output power                ≤ 0.1 °/dB
Group Delay (per 40 MHz)
-- Linear                                             ≤ ± 0.05 ns/MHz
-- Parabolic                                          ≤ ± 0.01 ns/MHz2
-- Ripple                                             ≤ 1 ns peak to peak
Frequency Stability
-- Daily                                              ≤ 5 x 10-9
-- Yearly                                             ≤ 1 x 10-7
-- Over Operating Temperature                         ≤ 1 x 10-8
Phase Noise (IESS 308/309 phase noise profile)
-- 10 Hz                                              ≤ -30 dBc/Hz
-- 100 Hz                                             ≤ -60 dBc/Hz
-- 1 kHz                                              ≤ -70 dBc/Hz
-- 10 kHz                                             ≤ -80 dBc/Hz
-- 100 kHz                                            ≤ -90 dBc/Hz
-- 1 MHz                                              ≤ -90 dBc/Hz
Mechanical
Input Connector                                       Type N Female
Output Connector                                      Type N Female
Management & Control                                  Ethernet using outdoor rated connectors (e.g., Miniature
                                                      Cylindrical Connector meeting MIL-C-26482) for
                                                      indoor/outdoor Up Converters; indoor rated connectors for rack-
                                                      mount Up Converters




10/07/10                                             SECTION J-1: ASTI TECHNICAL SPECIFICATION - 37
ASTI                                            Amendment 5                                DTFAWA-10-R-00039


                                       Table 4.1.3.1-1 UP Converter Specifications



SPEC.4.1.3.2           Down Converter

SPEC.4.1.3.2.1         Down Converter performance must comply with the specs of Table 4.1.3.2-1
                               Parameter                         Specifications/Requirements
           Type                                          Dual Conversion
           Frequency                                     Positive (No Inversion)
           Frequency Selection (Local or Remote)         Synthesizer tuned, 125 KHz steps
           Frequency Stability                           +/-1 x 10-9/day; 1 x 10-8 over temp range of 0 to
                                                         50 C.
           First IF Frequency                            Above 1 GHz
           Reference Frequency                           Front Panel Adjust and Monitor
           Input
           -- Frequency                                  3.7-4.2 GHz (Std.)
           -- Impedance                                  50 Ohms
           -- Return Loss                                20 dB (min.)
           -- Connector                                  Type “N”
           Noise Figure                                  13 dB (max.)
           Output
           -- Frequency                                  70 MHz (+/- 18 MHz)
           -- Impedance                                  75 Ohms
           -- Return Loss                                ≥ 23 dB (nom.)
           -- Connector                                  Type N
           Level (1 dB compr.)                           +15 dBm (min.)
           Muting                                        80 dB (min.)
           RF – IF Transfer Characteristics
           -- Conversion-Gain                            50 dB (min.)
           -- Bandwidth and Ripple                       40 MHz, +/-0.25 dB (max.)
           -- Gain Slope                                 +/- 0.05 dB/MHz (max.)
           -- Gain Stability                             +/- 0.25 dB/day (max.)
           Group Delay (+/-18 MHz)
           -- Linear                                     +/-0.05 ns/MHz (max)
           -- Parabolic                                  0.01 ns/ (MHz)2 (max.)
           -- Ripple                                     1.0 ns p-p (max.)
           Phase Noise                                   5 dB better than IESS 308/309
           In-band LO Leakage                            -70 dBm (max.) at input
           AM to PM Conversion                           0.1°/dB @ -5 dBm output power
           Intermodulation (Third Order)                 -50 dBc, for two carriers at 0 dBm output
           Gain Adjust                                   30.0 dB in 0.25 dB steps Front Panel Control
           Remote Control                                RS232, RS485


10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 38
ASTI                                            Amendment 5                              DTFAWA-10-R-00039


           M&C                                           Ethernet using outdoor rated connectors (e.g.,
                                                         Miniature Cylindrical Connector meeting MIL-
                                                         C-26482) for indoor/outdoor Down Converters;
                                                         indoor rated connectors for rack-mount Down
                                                         Converters
                                     Table 4.1.3.2-1 Down Converter Specifications




SPEC.4.1.3.3           Low Noise Amplifier (LNA)

SPEC.4.1.3.3.1         LNA performance must comply with the specs of Table 4.1.3.3-1
                                 Parameter                          Specifications/Requirements
           Frequency Range                                       3.7 - 4.2 GHz
           Gain                                                  60 dB
           Gain Flatness Full Band                               ±0.5 dB
           Gain Flatness Per 40 MHz (dB)                         ±0.2 dB
           Input VSWR                                            1.25 :1
           Output VSWR                                           1.25 :1
           Noise Temperature At +23 °C                           30 °K (Max.)
           Output
           -- 1 dB compression                                   +20 - +22 dBm
           -- 3rd Order Output                                   +22 - +25 dBm
           - Intercept Point -                                   +30 - +32 dBm
           Group Delay per 40 MHz
           -- Linear                                             0.01 ns/MHz
           -- Parabolic                                          0.001 ns/MHz2
           -- Ripple                                             0.1 ns p-p
           AM/PM Conversion (-5 dBm output power)                0.05 °/dB
           Gain Stability (Constant Temp.)
           -- Short term (10 min)                                ±0.1 dB
           -- Medium term (24 hrs)                               ±0.2 dB
           -- Long term (1 week)                                 ±0.5 dB
           Gain Stability Versus temperature                     -0.04 dB per °C
           Maximum Input Power Damage threshold                  0 dBm
           Connectors
           -- Input                                              WR229 Cover Flange
           -- Output                                             Type N Female
           Power, standard                                       Outdoor type rated (mate supplied)



10/07/10                                         SECTION J-1: ASTI TECHNICAL SPECIFICATION - 39
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


                                       Table 4.1.3.3-1 LNA Specifications



SPEC.4.1.3.4     IF Distribution System and Panel

SPEC.4.1.3.4.1   ASTI 70 MHz components must reuse the existing rack mounted IF distribution panel.


SPEC.4.1.3.5     Combiner and Divider

SPEC.4.1.3.5.1   The combiner and divider components must comply with the specs of Table 4.1.4.4-1
                                  Parameter              Specification/Requirement
                      Frequency                          50 – 90 MHz
                      Power                              20 W
                      Isolation                          25 dB (Min)
                      Insertion Loss                     0.3 dB
                      Amplitude Balance                  0.1 dB (Max)
                      Phase Balance                      2 Deg (Max)
                      VSWR
                      -- Input                           1.15:1 (Max)
                      -- Output                          1.15:1 (Max)
                      Power Pass Capability              Yes, as required
                      Connector(s)                       Type N
                      Impedance                          Impedance must match the
                                                         component and cable
                                                         requirements.
                             Table 4.1.3.4-1 Combiner and Divider Specification


SPEC.4.1.3.6     Terminations

SPEC.4.1.3.6.1   Terminations must comply with the specs of Table 4.1.3.6-1.
                             Parameter                    Specification/Requirement

                 Frequency Range                      50 – 70 MHz

                 Type                                 Type N or BNC

                 VSWR                                 1.10:1 (Max)

                 Power Rating                         Contingent on application
                 Impedance
                                                      Impedance must match the
                                                      component and cable requirements,
                                                      e.g. 50 or 75 Ohm.

                                   Table 4.1.3.6-1 Terminations Specifications


10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 40
ASTI                                             Amendment 5                                   DTFAWA-10-R-00039


SPEC.4.1.3.7       DC Blocks

SPEC.4.1.3.7.1     DC Block must comply with the specs of Table 4.1.3.7-1.
                                Parameter                          Specification/Requirement
                    Frequency Range:                       5MHz – 1450 MHz
                    VSWR:                                  1.35:1 (Max)
                    Insertion Loss:                        0.5 dB (Max)
                    Material:                              Stainless Steel
                    Voltage Maximum:                       200 VDC
                    Type                                   Center Pin Block
                    Connector (Input & Output)             Type N

                                        Table 4.1.3.7-1 DC Block Specifications



SPEC.4.1.3.8       Transceiver

SPEC.4.1.3.8.1     Transceiver must comply with the specs of Table 4.1.3.8-1
                  Parameter                                          Specifications/Requirements
IF output Frequency Range                             52-88 MHz
IF input Frequency Range                              52-88 MHz
RF output Frequency Range                             5845-6425 MHz
RF input Frequency Range                              3700-4200
Output Power (psat typical)                           200W,150W, 100W, 50W, 30 W
RF Return Loss                                        ≥ 20 dB
RF Spurious-Non-Carrier                               ≤ -80 dBm
RF Spurious-Carrier (Carrier leakage)                 ≤ -60 dBm
RF Output Level Adjustment Range                      20 dB Min
Third Order Inter-modulation at 10 dB backoff         ≤ -50 dBc
from rated output power
Third Order intercept                                 ≥ 23 dBm
Conversion-Gain                                       Conversion-Gain must match the output frequencies, impedance,
                                                      and levels of the IF system to the input to the SSPA without
                                                      inversion, distortion, or degradation in spectrum quality.
Gain Flatness                                         ≤ 0.5 dB
Gain Stability vs. Temperature at 0-50 Deg C          ≤ ± 1 dB
Gain Stability vs. Temperature: 24 Hr. at constant    ≤ ± 0.25 dB
drive and temp.
AM/PM conversion at rated output power                ≤ 0.1 °/dB
Group Delay (per 40 MHz)
-- Linear                                             ≤ ± 0.05 ns/MHz
-- Parabolic                                          ≤ ± 0.01 ns/MHz2
-- Ripple                                             ≤ 1 ns peak to peak
Frequency Stability

10/07/10                                             SECTION J-1: ASTI TECHNICAL SPECIFICATION - 41
ASTI                                              Amendment 5                                  DTFAWA-10-R-00039


                   Parameter                                         Specifications/Requirements
-- Daily                                              ≤ 5 x 10-9
-- Yearly                                             ≤ 1 x 10-7
-- Over Operating Temperature                         ≤ 1 x 10-8
Phase Noise (IESS 308/309 phase noise profile)
-- 100 Hz                                             ≤ -60 dBc/Hz
-- 1 kHz                                              ≤ -70 dBc/Hz
-- 10 kHz                                             ≤ -80 dBc/Hz
-- 100 kHz                                            ≤ -90 dBc/Hz
-- 1 MHz                                              ≤ -90 dBc/Hz
Mechanical
Input Connector                                       Type N Female
Output Connector                                      Type N Female using built in monitor port or an externally
                                                      mounted cross wave guide coupler
Management & Control                                  Ethernet using outdoor rated connectors (e.g., Miniature
                                                      Cylindrical Connector meeting MIL-C-26482) for
                                                      indoor/outdoor transceivers; indoor rated connectors for rack-
                                                      mount transceivers
                                        Table 4.1.3.8-1 Transceiver Specifications



SPEC.4.1.4          Redundancy Requirements

SPEC.4.1.4.1        RF Redundancy Switches

SPEC.4.1.4.1.1      Equipment redundancy with RF redundancy switching must be supported.

SPEC.4.1.4.1.1.1 RF redundancy switching must be supported, including support for the 1+1 17 or 1:118
modes of operation.

SPEC.4.1.4.1.1.2 RF redundancy switching must be completed within 2 sec.

SPEC.4.1.4.2      When the RF equipment requires a physically separate component to perform the
switching, the component must comply with the following requirements.

SPEC.4.1.4.2.1 When an RF switching component is required it must be mounted using the same methods
as the RF components it is switching.

SPEC.4.1.4.2.2 When an RF switching component is required it must comply with the same
indoor/outdoor requirements as the RF components it is switching.




17
   1+1 (1 plus 1) redundancy implies that each of the redundant units / paths carry the signal, with selection done at the
output.
18
   1:1 (1 for 1) redundancy implies that only one of the redundant units / paths carry the signal, i.e., RF redundancy
switch is provided at both the input and output. 1:1 is a special case of M:N redundancy, where M spare units / paths
backup N working units / paths.
10/07/10                                            SECTION J-1: ASTI TECHNICAL SPECIFICATION - 42
ASTI                                          Amendment 5                               DTFAWA-10-R-00039


SPEC.4.1.5        Physical Requirements

SPEC.4.1.5.1      The SSPA(s), Up Converter(s), Down Converter(s), transceiver(s), and BUC/SSPA(s)
deployed at remote sites must be mountable on walls, Unistrut frames, and antenna structures and must be
rated for outdoor operation.

SPEC.4.1.5.1.1    Equipment must be mounted using a tool-less bracket style mounting (e.g. thumbscrews).

SPEC.4.1.5.2      The LNA(s) and LNB(s) must be mounted within the existing antenna feed can enclosure
and rated for outdoor operation.

SPEC.4.1.5.3      All RF components deployed at hub sites must be mountable in 19” racks and must be
rated for indoor operation.

SPEC.4.1.5.4      The L-Band IF distribution panel must be mountable in 19” racks and must be rated for
indoor operation.

SPEC.4.1.5.5      The maximum dimensions of rack mountable RF components (including protection
switches and the IF distribution panel) must support the currently available rack space.



SPEC.4.1.6        Power Requirements

SPEC.4.1.6.1  The RF component(s) power supplies for sites other then ZAN, ZSE, ENA, FAI, JNU and
MDO must connect to GFE single phase, two pole, 60Hz nominal, critical power panels, through GFE
provided NEMA L5-20 single phase 120VAC receptacles inside or hardwired for outside mounted
equipment.

SPEC.4.1.6.2      The RF component(s) power supplies for ZSE must connect to GFE single phase, two
pole, 60Hz nominal, critical power equipment through integral NEMA L5-20 or 5-15 single phase 120VAC
receptacles or L14-20 single phase, two pole, 208VAC receptacles.

SPEC.4.1.6.3      The RF component(s) power supplies at ZAN, ENA, FAI, JNU, and MDO, must connect
to GFE three phase, 60Hz nominal, four wire critical power panels through GFE provided NEMA L6-15
single phase, two pole, 208VAC receptacles for BUC/SSPA equipment and NEMA 5-15 single phase,
120VAC receptacles for all other RF gear or hardwired for outside mounted equipment.



SPEC.4.1.7        Management Interfaces

SPEC.4.1.7.1     The Up/Down Converter(s), SSPA, Transceiver, BUC/SSPA and RF switch(s) must
support both remote19 and local management interfaces.

SPEC.4.1.7.2      LNA(s), LNA switches, LNB(s), and LNB switches, must be capable of being monitored
by the NMCS.


19
  The “remote” management interface enables management of the component from a location other than the physical
location of the component.
10/07/10                                        SECTION J-1: ASTI TECHNICAL SPECIFICATION - 43
ASTI                                        Amendment 5                            DTFAWA-10-R-00039


SPEC.4.1.7.3     LNA and LNB switches must be capable of being controlled by the NMCS.

SPEC.4.1.7.4     Detection and processing latency for all alarm / event reports must be ≤ 500 msec to the
local SNMP agent.



SPEC.4.1.7.5      Remote Management Interface

SPEC.4.1.7.5.1 All RF components must be managed via Simple Network Management Protocol (SNMP)
- based remote management and control over 10, 100, or 1000 Base T Ethernet.

SPEC.4.1.7.5.2 All Up/Down Converter, SSPA, transceiver, BUC/SSPA components must be directly
and individually managed via SNMP v1 or higher.

SPEC.4.1.7.5.3 RF components that are proxy managed must be managed by separate devices, one for the
primary and one for the alternate paths.

SPEC.4.1.7.5.4 The Up/Down Converter, SSPA, transceiver, and BUC/SSPA components must support a
terminal / command line-based remote management and control interface via an EIA-232 interface or a 10,
100, or 1000 Base T Ethernet connection.

SPEC.4.1.7.5.5 All RF components with SNMP agentsEthernet interfaces must synchronize their Time
Of Day (TOD) clock as specified in Section SPEC.5.8.1.2.
                                                                                                            Formatted: Heading 6
SPEC.4.1.7.5.5.1SPEC.4.1.7.5.6 All reportable events generated by the RF SNMP agents must utilize the
TOD when time stamping eventsbe stamped with the TOD upon receipt by the local collector.

SPEC.4.1.7.5.6SPEC.4.1.7.5.7 All alarm and fault conditions which are reported active must also be
reported cleared when the alarm and fault conditions are cleared.

SPEC.4.1.7.5.7SPEC.4.1.7.5.8 All RF equipment must provide all Reportable Events(REs) for faults and
status as listed in Section SPEC.5.6.3.5.2 – RF BUC/SSPA NE Management and Control, Section
SPEC.5.6.3.5.3 RF LNB Network Element (NE) Management and Control, Section SPEC.5.6.3.5.4 RF
Waveguide Switch NE Management and Control, Section SPEC.5.6.3.5.5 – RF 70 MHz IF Replacement
SSPA/Converter NEs Management and Control at a minimum.


SPEC.4.1.7.6     Local Management Interface

SPEC.4.1.7.6.1 The Up/Down Converter, SSPA, Transceiver, and BUC/SSPA components must support
local management and control via a laptop computer using EIA-232 or Ethernet.


SPEC.4.1.8       Mean Time Between Failure

SPEC.4.1.8.1   The RF components must have calculated or historical Mean Time Between Failure
(MTBF) performance of greater than 24,000 hours.




10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 44
ASTI                                        Amendment 5                                DTFAWA-10-R-00039


SPEC.4.2          Modem Component

SPEC.4.2.1        Modem General Requirements

SPEC.4.2.1.1      The modem must be configurable for full redundancy.

SPEC.4.2.1.1.1     The modem must support automatic protection switching.

SPEC.4.2.1.2      Modem automatic protection switching must be completed within 600 msec.

SPEC.4.2.1.3      The modem component must support both L-Band IF and 70 MHz IF.

SPEC.4.2.1.4    The modem must provide inherent fault / defect detection and reporting for both
equipment and data.

SPEC.4.2.1.5     The modem must provide inherent maintenance features (e.g., BER tests, Loopback (local
& remote), spectrum analyzer with local and remote views.)

SPEC.4.2.1.6         The modem must support at a minimum the user configurable capabilities in Table
4.2.1-1 .for all sites and all aggregate sizes.

                 Feature, Function         Specification/Requirement
                 Modulation                BPSK, QPSK, 8PSK, 8QAM, 16QAM
                 Coding                    Sequential, Viterbi (K=7), Turbo Product, Low Density Parity
                                           Check (LDPC), and Reed-Solomon
                 Data Scrambling           Intelsat IESS-308, IESS-309, and IESS-310 specifications
                 Uplink Power Control      Automatic and manual
                 Spectrum Efficiency       Double talk Carrier in Carrier (CnC), Paired Carrier Multiple Access
                                           (PCMA) or similar functionality
                              Table 4.2.1-1 User Configurable Capabilities



SPEC.4.2.2        Modulator

SPEC.4.2.2.1      The Modulator Output power must be:

             a) Adjustable between -25 dBm and 0 dBm for 70Mhz IF (impedance 75 ohms)
             b) Adjustable between -30 dBm and -5 dBm for L-Band (impedance 50 ohms)
             c) Adjustable in 10, 1, and 0.1 dB increments

SPEC.4.2.2.2      The power output must be stable to ±0.5 dB (independent of operating frequency, data
rate, modulation type, and temperature).

SPEC.4.2.2.2.1 The L-Band IF output frequency must be between 950 to 1450 MHz, or 950 to 1950
MHz, or 950 to 2150 MHz; adjustable in 100 Hz increments.

SPEC.4.2.2.2.2    The 70 MHz IF output frequency must be between 50 MHz to 90 MHz, adjustable in 100
Hz increments.

SPEC.4.2.2.3      IF output frequency deviation must be less than ±10 PPM measured over a 72 hour
interval.
10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 45
ASTI                                           Amendment 5                           DTFAWA-10-R-00039


SPEC.4.2.2.4       The output Spurious radiation must be < -55 dBc over F0 ±500 MHz using 4 KHz filter.

SPEC.4.2.2.5      The output Spurious radiation must be < -55 dBc over the operating frequency range
using 4 KHz filter.

SPEC.4.2.2.6       IF input return loss must be ≥ 14 dB over operating frequency range.



SPEC.4.2.3         Demodulator

SPEC.4.2.3.1     The Demodulator must operate with an IF input power level between -30 to -55 dBm
(with impedance equal 50 ohms for L Band and 75 ohms for 70 MHz).

SPEC.4.2.3.2    The L-Band IF input frequency must be between 950 to 1450 MHz, or 950 to 1950 MHz,
or 950 to 2150 MHz; adjustable in 100 Hz increments.

SPEC.4.2.3.3       The 70 MHz IF input frequency must be between 50 MHz to 90 MHz, adjustable in 100
Hz increments.

SPEC.4.2.3.4       IF input return loss must be ≥ 14 dB over operating frequency range.

SPEC.4.2.3.5     The Demodulator must incorporate a receive data buffer to accommodate plesiochronous
and Doppler timing differences.

SPEC.4.2.3.5.1     The receive data buffer output must be clockable by the transmit timing (TT) signal.

SPEC.4.2.3.5.2 The modem must supply receive demodulator clock serial timing (ST) post-demodulator
and pre-receive data buffer to the baseband serial aggregate.

SPEC.4.2.3.6       The Demodulator must detect and report, as a minimum:

             a)   Received Signal Level
             b)   Estimated Eb/No
             c)   Uncorrected (i.e. raw) BER
             d)   Corrected BER
             e)   Carrier Detect (CD) Status
             f)   Frequency Offset
             g)   Receive data buffer usage

SPEC.4.2.4         Modem Automatic Protection Switches

SPEC.4.2.4.1       Modem redundancy with automatic protection switching must be supported.

SPEC.4.2.4.1.1 Modem automatic modem protection switch configurations must support 1:1 and 1:8 (one
protection unit for (up to) eight) at a minimum.

SPEC.4.2.4.1.2 Where M:N protection switching is implemented, the user must have the ability to
configure a unique protection priority scheme of each of the N protected units.



10/07/10                                        SECTION J-1: ASTI TECHNICAL SPECIFICATION - 46
ASTI                                       Amendment 5                             DTFAWA-10-R-00039


SPEC.4.2.4.1.3 Where L-Band is used, the M:N protection switch must provide for connection to a
minimum of two satellites .

SPEC.4.2.4.1.4 Where 70 MHz IF is used, the M:N protection switch must provide for connection to a
minimum of four transponders.

SPEC.4.2.4.1.5 Protection switches must be configurable for either dependent (i.e., simultaneous) and
independent switching of transmit and receive paths.


SPEC.4.2.5       Physical Requirements

SPEC.4.2.5.1      The modem and 1:1 modem switch must be rack mountable in standard 19” racks and
rated for indoor operation.

SPEC.4.2.6       Power Requirements

SPEC.4.2.6.1      The modem component(s) power supplies must connect to GFE-provided NEMA 5-15
single phase, 120 VAC, 60Hz nominal, receptacles.



SPEC.4.2.7       Signal Interface Requirements

SPEC.4.2.7.1    The modem must accept and generate an aggregate digital signal from and to the
multiplexer component at a base rate between 56 Kbps to 2048 Kbps at a minimum.

SPEC.4.2.7.1.1    The modem must be remotely incrementally configurable via the user to at least 10
Mbps.

SPEC.4.2.7.1.2 The aggregate input and output signals must at a minimum comply with the standard
aggregate interface supported by the multiplexer component.

SPEC.4.2.7.2     Intermediate Frequency (IF) Signal

SPEC.4.2.7.2.1   The L-Band IF output frequency must be between 950 to 2050 MHz; adjustable in 100 Hz
increments.

SPEC.4.2.7.2.2   The 70 MHz IF output frequency must be between 50 MHz to 90 MHz, adjustable in 100
Hz increments.

SPEC.4.2.7.2.3 Signals (data, reference freq, monitor & control) and power provided over the L-Band IF
must be compatible with the RF components selected.


SPEC.4.2.7.3     Synchronization Signals

SPEC.4.2.7.3.1   The source of synchronization must be configurable by the user.




10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 47
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


SPEC.4.2.8       Management Interfaces

SPEC.4.2.8.1     The modem component must support both remote and local management interfaces.

SPEC.4.2.8.2     Detecting and processing latency for all event reports must be ≤ 500 msec to the local
SNMP agent.



SPEC.4.2.8.3     Remote Management Interface

SPEC.4.2.8.3.1 The modem and modem switch components must support Simple Network Management
Protocol (SNMP) version 2 or higher - based remote management and control over 10, 100, or 1000 Base T
Ethernet.

SPEC.4.2.8.3.2 The modem and modem switch components must support a terminal / command line-
based remote management and control interface via an EIA-232 interface or a 10, 100, or 1000 Base T
Ethernet connection.

SPEC.4.2.8.3.3 Modem components (other than modem, modem switch components, and components
proxy-managed through them) must be managed via SNMP IAW Section SPEC.5.6.3.4.3.

SPEC.4.2.8.3.4 All modem and modem switch components with Ethernet interfacesSNMP agents must
synchronize their TOD clock as specified in Section SPEC.5.8.1.2.
                                                                                                          Formatted: Heading 6
SPEC.4.2.8.3.4.1SPEC.4.2.8.3.5 All reportable events generated by the SNMP agents must utilize the TOD
when time stamping eventbe stampeds with the TOD upon receipt by the local collector.

SPEC.4.2.8.3.5SPEC.4.2.8.3.6 All alarm and fault conditions which are reported active must also be
reported cleared when the alarm and fault conditions are cleared.

SPEC.4.2.8.3.6SPEC.4.2.8.3.7 All modem and modem switches must provide all REs for faults and status
as listed in Section SPEC.5.6.3.5.7 Modem NE Management and Control, Section SPEC.5.6.3.5.8 Modem
M:N Switch NE Management and Control, and Section SPEC.5.6.3.5.9 Modem 1:1 Switch Function NE
Management and Control at a minimum.


SPEC.4.2.8.4     Local Management Interface

SPEC.4.2.8.4.1 The modem and modem switch components must support local management and control
via a front panel interface.


SPEC.4.2.9       Mean Time Between Failure

SPEC.4.2.9.1   The modem component must have a calculated or historical Mean Time Between Failure
(MTBF) performance of greater than 36,000 hours.




10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 48
ASTI                                        Amendment 5                            DTFAWA-10-R-00039


SPEC.4.3         Multiplexer Component

Multiplexer components may consist of one or more multiplexers and any supplemental equipment
necessary to meet the multiplexer functionality described with SPEC.4.3.To achieve the multiplexer
functionality described below, the multiplexer components at an ASTI site may consist of:
              one or more different types of equipment, and.
              one or more of the same type of equipment.


SPEC.4.3.1       Multiplexer Component Overview

SPEC.4.3.1.1     Integrated Channel-Level Test Requirements

SPEC.4.3.1.1.1 For each discrete channel, the multiplexer components must provide four types of
Loopback as follows: local-local, local-remote, remote-local, and remote-remote (reference Appendix I).
Local and remote are with respect to Port module.

SPEC.4.3.1.1.1.1 For each discrete digital channel, the multiplexer components must provide an integrated
Bit Error Rate Test (BERT) generator function.

SPEC.4.3.1.1.1.2 Capability to use an external BERT must be provided.

SPEC.4.3.1.1.2   Discrete channel-level loopbacks must not affect any other channel.

SPEC.4.3.1.1.3 For each discrete analog channel, the multiplexer components must provide an integrated
milliwatt generator (1004 Hz tone) function.

SPEC.4.3.1.1.3.1 Capability to use an external tone generator must be provided.


SPEC.4.3.1.2     Multiplexer Requirements

SPEC.4.3.1.2.1   Multiplexer channels and circuits must be full period.

SPEC.4.3.1.2.2   Satellite bandwidth apportioning between sites must be by Frequency Division
Multiplexing..

SPEC.4.3.1.2.3SPEC.4.3.1.2.2 Inspecting content or decoding OSI Layer 1-2 inputs for the
purposes of applying a higher layer (3-7) OSI protocol is prohibited..

SPEC.4.3.1.2.4SPEC.4.3.1.2.3 Co-located multiplexer components of the same equipment type (as
allowed by SPEC.4.3), OSI Layer 3 interconnections are only allowed for management interfaces.

SPEC.4.3.1.2.5SPEC.4.3.1.2.4 Multiplexer component management interfaces must be a physically
separate interface from interconnections supporting operational services.

SPEC.4.3.1.2.6SPEC.4.3.1.2.5 The multiplexer component management and configuration must not be
accessible by customer circuit traffic.


SPEC.4.3.1.3     Multiplexer In-Service Monitoring and Reporting Requirements
10/07/10                                  SECTION J-1: ASTI TECHNICAL SPECIFICATION - 49
ASTI                                            Amendment 5                                 DTFAWA-10-R-00039


SPEC.4.3.1.3.1 The ASTI multiplexer component must continuously monitor the performance of each
received aggregate data stream in real time.

SPEC.4.3.1.3.2 The multiplexer componentASTI system must classify each aggregate link’s State as
Available, Degraded, or Unavailable based upon monitored parameters, including as a minimum:
            a) Frame synchronization status; and
            b) End-to-end Bit Error Rate (BER) performance.

SPEC.4.3.1.3.3 Transition between aggregate link states must incorporate the “soak interval”20 and
hysteresis control mechanisms.

SPEC.4.3.1.3.3.1 The multiplexer componentASTI system must support user configurable “soak interval”
and “hysteresis” parameters.
                                                                                                                        Formatted: Outline numbered + Level: 7 +
                        SPEC.4.3.1.3.3.2a)      The “soak interval” parameter must be user configurable                 Numbering Style: a, b, c, … + Aligned at:
                            between 0 to 127 seconds, in 1 second increments.                                           1.38" + Tab after: 1.73" + Indent at: 1.73"


                        SPEC.4.3.1.3.3.3b)        The hysteresis values must be user configurable as
                            follows: The BER Degraded Threshold must be configurable by the user to10-
                            n, where n is any integer between three and eight.

SPEC.4.3.1.3.4 Changes in the aggregate signal state must be time stamped and reported21 within 50 msec
of declaration (e.g., after the “soak interval”).


SPEC.4.3.1.4       Multiplexer Provisioning Requirements

SPEC.4.3.1.4.1 The multiplexer components must support configuration of Port Module operating and
interface parameters.

SPEC.4.3.1.4.2     In-service channel Adds, Deletes, and Changes must be supported.

SPEC.4.3.1.4.3     Channel provisioning activities must not impact other channels.

SPEC.4.3.1.4.4     Aggregate provisioning activities must not impact other aggregates.

SPEC.4.3.1.4.5     The multiplexer components must be capable of being configured remotely.

SPEC.4.3.1.4.6     A multiplexer component must be capable of persistent storage of its configuration.

SPEC.4.3.1.4.7 The multiplexer components must be capable of manually re-routing circuits over
alternate aggregates or paths.

SPEC.4.3.1.4.8 The multiplexer components must provide controls to support viewing available
bandwidth at both the per-aggregate and per-node levels.

20
   "Soak Interval" is defined in the telecom industry as a configurable time interval during which a condition should
continuously exist in order to be considered "real". This concept is used to ignore transient "hits" and momentary
conditions on telecom circuits; thereby avoiding unnecessary alarm reports and protection switch actions.
21
   In this context, “reported” means displayed on the local management interface and delivered to the communications
channel supporting the remote management interface.
10/07/10                                          SECTION J-1: ASTI TECHNICAL SPECIFICATION - 50
ASTI                                       Amendment 5                            DTFAWA-10-R-00039


SPEC.4.3.1.4.9   The multiplexer components must be capable of operating without a provisioning system.

SPEC.4.3.1.4.10 The multiplexer components must support the proposed automated channel protection
switching architecture (reference Section 3.2).


SPEC.4.3.2       Physical Requirements

SPEC.4.3.2.1      The multiplexer components must be must be rack mountable in standard 19” racks and
rated for indoor operation.



SPEC.4.3.3       Power Requirements

SPEC.4.3.3.1      The multiplexer component(s) power supplies must connect to GFE provided NEMA 5-
15 single phase, 120 VAC, 60Hz nominal, receptacles at all sites other then ZAN and the AFSS Hubs. The
multiplexer components have the option of connecting to 20 AMP, 208 VAC, 60Hz nominal service at
ZAN and the AFSS Hubs..

SPEC.4.3.3.2      The multiplexer components must use redundant power supplies, each connected to one
of two separate GFE provided NEMA 5-15 single phase, 120VAC, 60Hz nominal receptaclespower circuits
sourced from separate GFE breakers . at ZAN and the AFSS Hubs. At all other locations where the
manufacturer of multiplexer components used in the ASTI network provides the option of having redundant
power supplies, or accepts redundant power feeds, redundant supplies and power feeds shall be used.

SPEC.4.3.3.2.1 The loss of one of the redundant power supplies must not cause the loss of any of the
multiplexer functions.


SPEC.4.3.4       Signal Interface Requirements

SPEC.4.3.4.1     Analog Port Interfaces

SPEC.4.3.4.1.1 The multiplexer component must support Voice Grade 1 (VG-1), VG-3, VG-6, and VG-8
private line analog port interfaces IAW Bellcore TR-NWT-000335 requirements.

SPEC.4.3.4.1.2   The Impedance of analog port interfaces must be 600 ohms nominal measured at 1004
Hz.

SPEC.4.3.4.1.3 Analog port interfaces must support both four Wire (4 W) and two Wire (2 W)
transmission paths and E&M signaling leads (Types I, II & III).

SPEC.4.3.4.1.4 Analog port interfaces must provide a zero transmission level point (0 TLP) for
transmitted and received signals at the ASTI Demarcation Point (ADP).

SPEC.4.3.4.1.5 All VG-n interfaces must support 64 Kbps Pulse Code Modulation (PCM) (with µ-Law
companding) encoding IAW ITU-T G.711.




10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 51
ASTI                                         Amendment 5                              DTFAWA-10-R-00039


SPEC.4.3.4.1.6 The VG-6 interface must support 32 Kbps, 24 Kbps, and 16 Kbps Adaptive Differential
Pulse Code Modulation (ADPCM) encoding IAW ITU-T G.726. Other voice encoding technology may be
substituted for ADPCM where ADPCM is not supported.

SPEC.4.3.4.1.7 The VG-3 and VG-1 interfaces must at a minimum support 8 or 9.6 Kbps voice encoding
technology providing wherewhere the voice quality is rated by one or both of the following::
           a) The Mean Opinion Score (MOS) ratings must be 3.5 or better
           b) The Diagnostic Acceptability Measure (DAM) ratings must be 65 or better.

SPEC.4.3.4.1.8    The ASTI multiplexer components must support switched services analog port interface
requirements.

SPEC.4.3.4.1.8.1 The following services must be supported: Ringdown (auto and manual), Foreign
Exchange (FXO and FXS); and inter-switch Tie Line services.

SPEC.4.3.4.1.8.2 Switched services analog port interfaces must support the standard 600 ohm impedance.

SPEC.4.3.4.1.8.3 Both Loopstart and Ground start signaling options must be supported.

SPEC.4.3.4.1.8.4 Four Wire Tie Line interfaces must support optional provisioning of talk battery on the
transmit pairs.


SPEC.4.3.4.2      Digital Data Port Interfaces

SPEC.4.3.4.2.1    The multiplexer components must support the following digital data port interfaces:

SPEC.4.3.4.3      Synchronous serial data with network, external, internal, or loop timing as required; at
rates from 2.4 kbps to 2.048 Mbps as shown in Table 4.4.4-1.

SPEC.4.3.4.4      Asynchronous serial data at rates from 1200 bps to 19.2 kbps as shown in Table 4.4.4-1.

SPEC.4.3.4.4.1 The direct digital connectivity, Digital Data Service (DDS), Fractional T1, Fractional E1,
T1, and E1 interfaces using EIA-232, EIA-422, EIA-530, ITU-T V.35, and DSX-1 physical interface,
electrical interface, and protocol standards as applicable, must be supported at a minimum.

SPEC.4.3.4.4.1.1 The Fractional T1 and T1 ports must support the Extended Super Frame (ESF) format per
the ANSI T1.403-1999 specification and B8ZS line encoding IAW Section 8.1 of the ANSI T1.403-1999
requirements.

SPEC.4.3.4.4.1.2 The Fractional E1 and E1 ports must conform to ITU G.703, G.704, and G.823
specifications with AMI and HDB3 line coding.

SPEC.4.3.4.4.2 At a minimum the multiplexer components must support EIA-232, EIA-422, EIA-530,
and V.35 serial digital channel interfaces.

SPEC.4.3.4.4.2.1 Multiplexer components must allow user configuration of discrete serial data control
signals (e.g., RTS, CTS.)

SPEC.4.3.4.4.2.2 Multiplexer components must allow user configuration of data interface clocking source.

10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 52
ASTI                                         Amendment 5                            DTFAWA-10-R-00039


SPEC.4.3.4.4.2.3 Multiplexer components must provide user configurable receive and transmit data buffers
each with user configurable clocking for data input and output.

SPEC.4.3.4.4.2.4 Multiplexer components must allow user configuration of DTE/DCE selection.


SPEC.4.3.4.4.3     Channel Data Rates

SPEC.4.3.4.4.3.1 The multiplexer components must support at a minimum, digital Channel data rates
reflected in Table 4.4.4-1.


                             1.2 K        1.6 K      1.8 K       2.0 K      2.4 K        3.2 K        3.6 K

   4.0 K          4.8 K      6.4 K        7.2 K      8.0 K       9.6 K     12.0 K       14.0 K       14.4 K

  16.0 K         19.2 K     24.0 K       25.0 K     28.0 K      28.8 K     32.0 K       36.0 K       38.4 K

  39.0 K         40.8 K     48.0 K       50.0 K     56.0 K      57.6 K     64.0 K       72.0 K       76.8 K

  96.0 K     100.0 K       112.0 K      115.2 K    128.0 K     144.0 K    153.6 K      168.0 K      192.0 K

 224.0 K     230.0 K       256.0 K      280.0 K    288.0 K     307.2 K    320.0 K      336.0 K      338.0 K

 384.0 K     392.0 K       394.0 K      448.0 K    460.8 K     504.0 K    512.0 K      560.0 K      576.0 K

 616.0 K     640.0 K       672.0 K      704.0 K    728.0 K     768.0 K    784.0 K      832.0 K      840.0 K

 896.0 K     921.0 K       952.0 K      960.0 K    1.008 M    1.024 M    1.064 M       1.088 M      1.120M

 1.152 M     1.176 M      1.213 216     1.232 M     1.28 M    1.288 M    1.344 M       1.408 M      1.472 M
                                 M
 1.528 M     1.536 M       1.544 M      1.600 M    1.664 M    1.728 M    1.792 M       1.856 M      1.920 M

 1.984 M     2.048 M
                                      Table 4.4.4-1 Channel Data Rates

SPEC.4.3.4.4.4     High Speed Aggregate Digital Interface

SPEC.4.3.4.4.4.1 The multiplexer components must generate and accept aggregate digital signals to and
from the modem at effective data rates up to 10 5 Mbps.

SPEC.4.3.4.4.4.2 The multiplexer components must support, at a minimum, the selectable aggregate data
rates of either:

           a) 56 Kbps and all multiples of 56Kbps up to 1.344 Mbps; or
           b) 56 Kbps or 64 Kbps and all multiples of 64 Kbps up to 1.536 Mbps.

SPEC.4.3.4.4.4.3 Selectable Aggregate aggregate data rates above between 1.536 Mbps and 105 Mbps are
TBP.




10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 53
ASTI                                           Amendment 5                              DTFAWA-10-R-00039


SPEC.4.3.4.5      Synchronization Interface and Signals22

SPEC.4.3.4.5.1 The ASTI multiplexer components must accept at a minimum a user configurable external
synchronization (clock) input at either 1.544 or 2.048 MHz into a 75 ohm load with a power level between -
6 dBm to +10 dBm.

SPEC.4.3.4.5.2 The multiplexer components must be capable of utilizing either Rx satellite clock
signal(s) for synchronization or an internally generated (“holdover”) clock signal for synchronization.

SPEC.4.3.4.5.3 The multiplexer components must be capable of utilizing an internally generated clock
signal for synchronization.

SPEC.4.3.4.5.3.1 The multiplexer internal clock must have an accuracy of at least Stratum 4E.

SPEC.4.3.4.5.4 The multiplexer sync (clock) sources and the source selection order of preference
algorithms must be fully configurable by the user.

SPEC.4.3.4.5.4.1 Multiplexer components must accommodate accept an external clock input, modem
aggregate inputs, and provide an internal oscillator. The multiplexer components musta minimum of four
synchronization sources and select the "best" source based upon a predetermined user configurable priority
scheme.

SPEC.4.3.4.5.5    Transfer between sync sources must be accomplished within 60500 msec.


SPEC.4.3.5        Management Interface Requirements

SPEC.4.3.5.1    The multiplexer equipment components must support both remote23 and local
management interfaces.

SPEC.4.3.5.2    Detection and processing latency for all alarm / event reports must be ≤ 500 msec to the
local SNMP agent.



SPEC.4.3.5.3      Remote Management Interface.

SPEC.4.3.5.3.1 The multiplexer components must support Simple Network Management Protocol
(SNMP) version 3 or higher - based remote management and control over 10, 100, or1000 Base T Ethernet.

SPEC.4.3.5.3.2 The multiplexer components must support a terminal / command line-based remote
management and control interface via an EIA-232 interface or a 10, 100, or1000 Base T Ethernet
connection.

SPEC.4.3.5.3.3    Multiplexer components must be managed via SNMP IAW Section SPEC.5.6.3.4.3.


22
   This should not be confused with time Of Day (TOD) synchronization, which is used for reporting purposes only
and is defined in section 5.8.1.2.
23
   The “remote” management interface enables management of the component from a location other than the physical
location of the component.
10/07/10                                        SECTION J-1: ASTI TECHNICAL SPECIFICATION - 54
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


SPEC.4.3.5.3.4 All multiplexer components with Ethernet interfacesSNMP agents must synchronize their
TOD clock as specified in Section SPEC.5.8.1.2.
                                                                                                              Formatted: Heading 6
SPEC.4.3.5.3.4.1SPEC.4.3.5.3.5 All reportable events generated by the SNMP agents must be stamped with
the TOD upon receipt by the local collectorutilize the TOD when time stamping events.

SPEC.4.3.5.3.5SPEC.4.3.5.3.6 All alarm and fault conditions which are reported active must also be
reported cleared when the alarm and fault conditions are cleared.

SPEC.4.3.5.3.6SPEC.4.3.5.3.7 The multiplexer components must provide all REs for faults and status as
listed in Section SPEC.5.6.3.5.1 – Multiplexer NE Management and Control at a minimum.


SPEC.4.3.5.4     Local Management Interface

SPEC.4.3.5.4.1   The multiplexer components must provide local status displaysindicators using LEDs.

SPEC.4.3.5.4.1.1 A Each multiplexer chassis must provide at least one Power status LED. The
PowerPower LED(s)indicator must be illuminated Green when correct power is available at the chassisto
the multiplexer components.

SPEC.4.3.5.4.1.2 The multiplexer components must have An a visual Alarm alarm indicationindicator for
failure, using an illuminated Red LED, must be provided on the face plate of each field replaceable module.

SPEC.4.3.5.4.1.3 The Alarm alarm LED must be illuminatedindicate when a fault in the replaceable
module is detected and extinguished when the fault ceases to exist.

SPEC.4.3.5.4.1.4 Port modules must provide a per channel status LED indicator mounted on the face plate.
If multi-channel Port modules are deployed, these modules must incorporate multiple channel status
LEDsindicators.

SPEC.4.3.5.4.1.5 The channel status LED(s)indicators must beindicate illuminated Red when the associated
channel is Unavailable. Other per channel visual status indications may be provided.

SPEC.4.3.5.4.1.6 A Test / Loopback visual indicator (i.e., LED) must be provided on the front panel of the
multiplexer chassis or on the individual LRUs comprising the multiplexer.

SPEC.4.3.5.4.1.7 The Test / Loopback LED visual indicator must be illuminatedindicate while when one or
more associated channels are in the test or loopback mode.

SPEC.4.3.5.4.1.8 The multiplexer components must support local management and control via a laptop
computer using EIA-232 or Ethernet.


SPEC.4.3.6       Mean Time Between Failure

SPEC.4.3.6.1    The multiplexer components must have calculated or historical Mean Time Between
Failure (MTBF) performance of greater than To Be Proposed (TBP) hours.




10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 55
ASTI                                         Amendment 5                              DTFAWA-10-R-00039


SPEC.4.4          ASTI Demarcation Point (ADP) Components

SPEC.4.4.1        A/B Switch Chassis Requirements

SPEC.4.4.1.1      A/B chassis must support a minimum of 16 A/B switched circuits.

SPEC.4.4.1.2      A/B digital chassis must be user configurable to support multiple digital interface types
within a single chassis, at a minimum RS-232, V.35, and RS-530.

SPEC.4.4.1.3      A/B analog chassis must be user configurable to support multiple analog interface types
within a single chassis, at a minimum 4-wire E&M, and 2-wire E&M.

SPEC.4.4.1.4      A/B chassis must be powered by redundant power supplies with two independent inputs.

SPEC.4.4.2        Analog Circuit A/B Switch Requirements

SPEC.4.4.2.1      Analog circuit A/B switches must switch a single discrete circuit between either of the
two channels.

SPEC.4.4.2.2    Analog A/B switches must not change position due to a loss of power, loss of control
communications, or a normal / typical hardware failure mode. (i.e., “latching”)

SPEC.4.4.2.3    Analog A/B switches must support all of the ASTI standard interfaces as specified in
Section SPEC 4.3.4.1.1.

SPEC.4.4.2.4      Analog A/B switches must have an insertion loss of ≤ 0.1 dB.

SPEC.4.4.2.5      Analog A/B switches must exhibit a characteristic impedance of 600 and 900 ohms.

SPEC.4.4.2.6      The open interval during transfer from one path to the other must be  2 msec.



SPEC.4.4.3        Digital Circuit A/B Switch Requirements

SPEC.4.4.3.1      Digital circuit A/B switches must switch a single discrete circuit between either of the two
data channels.

SPEC.4.4.3.2    Digital A/B switches must not change position due to a loss of power, loss of control
communications, or a normal / typical hardware failure mode. (i.e., “latching”)

SPEC.4.4.3.3     Digital A/B switches must support all of the ASTI standard interfaces as specified in
Section SPEC.4.3.4.2.

SPEC.4.4.3.4      The open interval during transfer from one path to the other must be  2 msec.

SPEC.4.4.3.5      Digital A/B switches must contain the ability to allow manual patching between circuits.




10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 56
ASTI                                          Amendment 5                              DTFAWA-10-R-00039


SPEC.4.4.4        Analog Circuit and Channel Test Access Requirements

SPEC.4.4.4.1      Analog circuit and channel line, drop, and monitor access jacks must support monitoring
and test access functions for all ASTI analog circuits.

SPEC.4.4.4.1.1    Use of the monitor jacks must not cause a break in the transmission path.

SPEC.4.4.4.1.2    Use of the test access jacks must not affect the function of other circuits or channels.

SPEC.4.4.4.2        For A/B switched analog circuits, the channel line access jack(s) must support the
capability to test the channel not in service.

SPEC.4.4.4.3     Analog circuit and channel line, drop, and monitor access jacks must support all of the
standard ASTI interfaces as reflected in Section SPEC.4.3.4.1



SPEC.4.4.5        Digital Circuit and Channel Test Access Requirements

SPEC.4.4.5.1     Digital circuit and channel line (DCE or modem), drop (DTE, equipment, or computer),
and monitor access jacks must support monitoring and test access functions for all ASTI digital circuits.

SPEC.4.4.5.1.1    Use of the monitor jacks must not cause a break in the transmission path.

SPEC.4.4.5.1.2    Use of the test access jacks must not affect the function of other circuits or channels.

SPEC.4.4.5.2      For A/B switched digital circuits, the channel line (DCE or modem) access jack(s) must
support the capability to test the channel not in service.

SPEC.4.4.5.3     Digital circuit and channel line, drop, and monitor access jacks must support all of the
standard ASTI interfaces as reflected in Section SPEC.4.3.4.2.

SPEC.4.4.5.3.1 The connectors for the digital circuit and channel test access capability must conform to
the applicable interface specifications.


SPEC.4.4.6        Physical and Environmental Requirements

SPEC.4.4.6.1      Physical

SPEC.4.4.6.1.1    The ADP components must be must be rack mountable in standard 19” racks.

SPEC.4.4.6.2      Environmental

SPEC.4.4.6.2.1 The ADP components must operate satisfactorily in an indoor environment in accordance
with Section SPEC.3.7.1.2.




10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 57
ASTI                                        Amendment 5                            DTFAWA-10-R-00039


SPEC.4.4.7       Power

SPEC.4.4.7.1     The A/B switch chassis must use redundant power supplies, each connected to one of two
separate GFE provided NEMA 5-15 single phase, 120VAC, 60Hz nominal receptacles sourced from
separate GFE breakers.

SPEC.4.4.7.1.1 The loss of one of the redundant power supplies must not cause the loss of any of the A/B
switch chassis functions.


SPEC.4.4.8       Management Interfaces

SPEC.4.4.8.1    The active ADP components, i.e., the A/B switches must support both remote and local
management interfaces.

SPEC.4.4.8.2     Detecting and processing latency for all event reports must be ≤ 500 msec to the local
SNMP agent.



SPEC.4.4.8.3     Remote Management Interface

SPEC.4.4.8.3.1 The A/B switch components must support Simple Network Management Protocol
(SNMP) version 1 or higher - based remote management and control over 10, 100, or 1000 Base T Ethernet.

SPEC.4.4.8.3.2 Channel A/B switch components must be managed via SNMP in accordance with Section
SPEC.5.6.3.4.3.

SPEC.4.4.8.3.3 All A/B switch components with Ethernet interfacesSNMP agents must synchronize their
TOD clock as specified in Section SPEC.5.8.1.2.
                                                                                                           Formatted: Heading 6
SPEC.4.4.8.3.3.1SPEC.4.4.8.3.4 All reportable events generated by the SNMP agents must be stamped with
the TOD upon receipt by the local collectorutilize the TOD when time stamping events.

SPEC.4.4.8.3.4SPEC.4.4.8.3.5 All alarm and fault conditions which are reported active must also be
reported cleared when the alarm and fault conditions are cleared.

SPEC.4.4.8.3.5SPEC.4.4.8.3.6 The automatic circuit protection switches must provide all REs for faults
and status as listed in Section SPEC.5.6.3.5.14 Automatic Circuit Protection Switch Management and
Control at a minimum.


SPEC.4.4.8.4     Local Management Interface

SPEC.4.4.8.4.1 The A/B switch components must support local management and control via individual
channel-level front-panel status LEDs, enable switch, and toggle switches.




10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 58
ASTI                                            Amendment 5                                DTFAWA-10-R-00039


SPEC.4.4.9         Mean Time Between Failure

SPEC.4.4.9.1     The Channel A/B switch components must have a calculated or historical MTBF
performance of greater than TBP hours.

SPEC.4.4.9.2  The channel Monitor and Test Access components must have a calculated or historical
MTBF performance of greater than TBP hours.



SPEC.5           Network Management and Control System (NMCS) Requirements

SPEC.5.1           Overview

 This section contains requirements for the NMCS 24. The NMCS will manage and control the ASTI
 network. The NMCS requirements are based on the International Telecommunication Union standard
 model for enterprise management - Fault management, Configuration management, Administrative
 management, Performance management, and Security management (FCAPS).
           M.3400 (02/2000) TMN management functions – TMN and Network Maintenance: International
            Transmission Systems, Telephone Circuits, Telegraphy, Facsimile and Leased Circuits
           M.3010 (02/2000) Principles for a telecommunications management network – TMN and
            Network Maintenance: International Transmission Systems, Telephone Circuits, Telegraphy,
            Facsimile and Leased Circuits

SPEC.5.2           General NMCS Functional Requirements

SPEC.5.2.1         Interfaces and Protocols

SPEC.5.2.1.1      The NMCS must be standards-based with attributes that are used by the Network
Management and Control industry to provide flexibility for accommodating electrical interfaces and
protocols (e.g. SNMP25 v1, v2 and v3, Transmission Control Protocol (TCP), Internet Protocol (IP), EIA-
232, and EIA-422).

SPEC.5.2.2         ASTI Network Management

SPEC.5.2.2.1     The management and control of the ASTI network must be centralized at ZAN ARTCC,
sub-networked at the 3 AFSS hubs, and distributed throughout the ASTI network. 26

SPEC.5.2.2.2     The NMCS must manage and control all the ASTI Network27 Network Elements (NEs)28
using automatic and manual controls for each NE.


24
   The NMCS consists of all hardware, software, and services installed to meet the requirements of section SPEC 5 –
Network Management and Control System (NMCS) Requirements.
25
   SNMP is defined in RFC-3411and RFC-2578.
26
   The ASTI network contains a fourth sub-network, ZAN ARTCC, which does not have independent, alternate
network management sites with AFSS hub NMCS communications channels for these remotes. Today, these remotes
include SYA, TTF, and ZSE.
27
   The NMCS will not manage, monitor, nor control the satellite(s).
28
   The term “Network Element (NE)” refers to (1) any of the ASTI Network telecommunications components (Telco
NE), (2) any of the components of the ASTI Network NMCS that are addressed in this section (Section 5) of this
10/07/10                                          SECTION J-1: ASTI TECHNICAL SPECIFICATION - 59
ASTI                                             Amendment 5                                 DTFAWA-10-R-00039


SPEC.5.2.2.3      A failure of any portion of the NMCS or the entire NMCS must not affect the FAA
operational services that are transported by the ASTI Network.

SPEC.5.2.2.4       The NMCS must allow each user simultaneous and independent management of the ASTI
network.

SPEC.5.2.2.5     The NMCS must present view(s) of the ASTI Network topology, configuration, and status
on workstation(s).

SPEC.5.2.2.6    The NMCS must enable quick deployment of new services at existing sites with minimal
manual involvement in changing the configuration of the system.

SPEC.5.2.2.7    The NMCS must be easily reconfigurable to support the deployment of new remote sites
with minimal manual involvement in changing the configuration of the system.

SPEC.5.2.2.7.1 Changes to the network topology and configuration must be capable of being
implemented manually by a user29.

SPEC.5.2.2.8     Changes to the network topology and configuration must be capable of being
implemented through auto discovery (see Section SPEC.5.7.2.2- Auto Discovery of IP enabled Devices)
and accepted by a user.



SPEC.5.2.3         ASTI Operations Independence of the NMCS

This section addresses how changing NMCS components affect the operation of the ASTI Network and the
capability of the NMCS to perform its functionality.

SPEC.5.2.3.1    The activities associated with changing the NMCS topology and configuration
modifications must not impact performance of the FAA services on the ASTI Network.

SPEC.5.2.3.2      The activities associated with changing the NMCS due to ASTI network topology and
configuration modifications must not degrade or interrupt the management and control of the ASTI network
for more than 15 seconds.

SPEC.5.2.3.2.1     The changes must either be accepted by the operator through a dialog box or updated
dynamically.


SPEC.5.2.4         Compatibility with Legacy ASTI Network

SPEC.5.2.4.1       All NEs within the ASTI Network must be managed and controlled by an NMCS during
the transition from the legacy ASTI equipment to the new ASTI equipment and during steady state
operations.


specification, including any of the devices that allow monitoring or control of environmental and physical conditions
at the ASTI facilities.
                                      ASTI NEs = Telco NEs + NMCS NEs = NEs
29
   The term “user” in the document refers to an authenticated user. Actual user roles and privileges are defined in
Section 5.8.
10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 60
ASTI                                               Amendment 5                               DTFAWA-10-R-00039


SPEC.5.2.4.2      The NMCS must be capable of management and control of legacy ASTI equipment which
will remain in the ASTI network. See Appendix E for Legacy Configuration.



SPEC.5.2.5            Compatibility with Other NMS

SPEC.5.2.5.1  The ASTI NMCS must have standards-based capability for integrating with other
Network Management Systems (NMSs) and element managers.

SPEC.5.3              Environmental Requirements

SPEC.5.3.1            Environmental Exception

The NMCS equipment must comply with Section SPEC.3.7.3 – Environmental Requirements for common
ASTI environmental requirements with the following exception.

SPEC.5.3.1.1          ASTI NMCS equipment must be capable of withstanding, without sustaining damage,
operation in:

                a) Temperature: 10 to +40° C,
                b) Humidity: 5% – 85% relative humidity, non-condensing.

SPEC.5.3.1.2     ASTI NMCS monitors must be capable of withstanding, without sustaining damage,
storage in ambient temperatures between -20° to +70° C.




SPEC.5.4              Physical Requirements

The NMCS equipment must be sized to accommodate the physical requirements of the sites where it will be
deployed while complying with all functional requirements as specified herein.

SPEC.5.4.1            Network Operations Control Center (NOCC) Space Requirements

SPEC.5.4.1.1       NMCS equipment, installed in the NOCC, must fit within four GFE NMCS consoles and
a single printer space. Refer to Figure 5-1 – NMCS Operator Positions in the NOCC.

                a) Computer 30 Space 20” x 24” x 18” (H x W x D)
                b) Monitor Space: 16 ¾” x 22 ½” x 19” (H x W x D)
                c) Viewable area (due to sliding door): 13” x 14 ¾” (H x W)

30
     For purposes of this specification, computer includes motherboard, memory, case, etc.
10/07/10                                             SECTION J-1: ASTI TECHNICAL SPECIFICATION - 61
ASTI                                                Amendment 5                                       DTFAWA-10-R-00039


             d) Desk Top Space: 24”x 22’ (W x D)
             e) Keyboard Tray: 22 ¼” x 11 1/8 ” (W x D)
             f) Printer: 20” x 24” x 18” (H x W x D)


              ASTI Console     NMCS Console        NMCS Console       NMCS Console         NMCS Console     ASTI Console




              Reserved       Multi-Function     Multi-Function       Multi-Function    Multi-Function       Reserved
               Space            Space              Space                Space             Space              Space




             Link Monitor    Link Monitor       Multi-Function       Multi-Function    Multi-Function       Reserved
               Space 2         Space 2             Space                Space             Space              Space




             Link Monitor    Link Monitor        Link Monitor         Link Monitor      Link Monitor      Administrative
                Space           Space               Space                Space             Space             Space


                                   Reserved Space                           Reserved Space
                                     For NMCS                                 For NMCS
       Desk Top



              Reserved         Reserved           Reserved             Reserved          Reserved           Reserved
               Space            Space              Space                Space             Space              Space


                               Work Space 1         Work Space 2      Work Space 1         Work Space 2


                                      Operator Position                     Operator Position



                                                               NOCC
                                          Figure 5-1 NMCS Operator Positions in the NOCC


SPEC.5.4.2           Auxiliary NOCC (ANOCC) Space Requirements

SPEC.5.4.2.1       NMCS equipment, installed in the ANOCC, must fit within three GFE NMCS consoles
and a single printer space. Refer to Figure 5-2 – NMCS ANOCC Position #1, and Figure 5-3 – NMCS
ANOCC Position #2.

             a) Computer Space: 20” x 24” x 18” (H x W x D)
             b) Monitor Space: 16 ¾” x 22 ½” x 19” (H x W x D)
             c) Viewable area (due to sliding door): 13” x 14 ¾” (H x W)
             d) Desk Top Space: 24”x 22’ (W x D)
10/07/10                                              SECTION J-1: ASTI TECHNICAL SPECIFICATION - 62
ASTI                                          Amendment 5                            DTFAWA-10-R-00039


           e) Keyboard Tray: 22 ¼” x 11 1/8 ” (W x D)
           f) Printer: 20”x 22 ½ “x 16” (H x W x D)

                               ASTI Console        NMCS Console      NMCS Console




                              Reserved            Link Monitor     Multi-Function
                           Reserved Space
                               Space                Space 2           Space




                                                  Link Monitor      Link Monitor
                           Reserved Space
                                                     Space             Space


                                                        Reserved Space
                          Desk Top
                                                          For NMCS



                           Reserved Space Reserved Space Reserved Space


                                                   Work Space 1       Work Space 2


                                                         Operator Position



                                     ANOCC Position # 1
                                     Figure 5-2 NMCS ANOCC Position #1




10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 63
ASTI                                           Amendment 5                          DTFAWA-10-R-00039


                                ASTI Console        NMCS Console




                               Reserved            Link Monitor
                                Space                Space 2




                             Administrative        Link Monitor
                                Space                 Space              Desk Top

                                                   Reserved
                                                    Space
                                                     For
                               Reserved
                                                    NMCS
                                Space
                                                    Reserved
                                                     Space


                                                    Work Space 1

                                                     Operator #2
                                                      Position




                                  ANOCC Position #2

                          Figure 5-3 NMCS ANOCC Position #2


SPEC.5.4.3      Remote Sites Space Requirements

SPEC.5.4.3.1    The NMCS equipment must be mountable in a 19” enclosure at the site.

SPEC.5.4.3.2    The NMCS equipment must fit within a maximum of five (5) rack-units, with the
following measurements per rack-unit:

                 a)    1.75 inches high,
                 b)    19 inches wide, and
                 c)    18.25 17.5 inches deep from front to rear rails, with approximately 1 inch of
                               adjustment.
                 Note: At the present Phase II sites only one rack-unit is used for the NMCS equipment.
                 To use a total of five (5) rack-units the changes to the non-NMCS components of the
                 ASTI Network will have to recover four (4) rack-units of space on the ASTI equipment
                 side of double wide communications enclosure.




10/07/10                                        SECTION J-1: ASTI TECHNICAL SPECIFICATION - 64
ASTI                                         Amendment 5                           DTFAWA-10-R-00039


SPEC.5.4.4         AFSS Hubs Space Requirements

SPEC.5.4.4.1     All NMCS equipment must fit within one new 19-inch enclosure. See Section
SPEC.3.7.1.2 - Equipment Racks and Enclosures for enclosure requirements.

SPEC.5.4.4.1.1 Enclosures used for NMCS equipment must comply with the requirements of Section
SPEC.3.7 - Facility and Equipment Requirements .

SPEC.5.4.4.1.2     Enclosures for NMCS equipment must be equipped with front and rear locking doors and
side panels.

SPEC.5.4.5         ZAN ARTCC Equipment Room Space Requirements

SPEC.5.4.5.1     The NMCS equipment must fit within five new 19-inch enclosures. See Section
SPEC.3.7.1.2 - Equipment Racks and Enclosures for the enclosure requirements.

SPEC.5.4.5.1.1     All NMCS equipment dedicated to providing security must fit within one enclosure.

SPEC.5.4.5.1.2     All non-security equipment must fit within four enclosures.

SPEC.5.4.5.1.3 Enclosures used for NMCS equipment must comply with Section SPEC.3.7 - Facility and
Equipment Requirements. .

SPEC.5.4.5.1.4     Enclosures for NMCS equipment must be equipped with front and rear locking doors and
side panels.

SPEC.5.5           NMCS Hardware and Software Component Requirements

SPEC.5.5.1         General NMCS Component Requirements

SPEC.5.5.1.1      For all NMCS components fulfilling the performance requirements specified in Section
SPEC.5.9.1.3.1, the component must not exceed 25% utilization during steady-state operation in the
following areas:

             a)   Memory
             b)   CPU
             c)   Disk I/O
             d)   Bus I/O
             e)   NIC I/O

SPEC.5.5.1.2      For all NMCS components fulfilling the performance requirements specified in Section
SPEC.5.9.1.3.2, the component must not exceed 50% utilization during steady-state operation in the
following areas:

             a)   Memory
             b)   CPU
             c)   Disk I/O
             d)   Bus I/O
             e)   NIC I/O



10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 65
ASTI                                       Amendment 5                            DTFAWA-10-R-00039


SPEC.5.5.1.3        All NMCS processes must be shown, through FAA approved, industry-standard 3rd party
tools, to be free from memory leaks and other defects such as those vulnerable to buffer overruns.

SPEC.5.5.1.4      NMCS components must not require a user to be logged in to meet requirements, except
where user interaction is required.

SPEC.5.5.1.5     NMCS components must not use or require auto-login capability.

SPEC.5.5.1.6      NMCS components must be capable of operational uptimes in excess of 270 calendar
days without a reboot.

SPEC.5.5.1.6.1   NMCS components must not require periodic reboots.


SPEC.5.5.2       Keyboard, Video Monitor, and Mouse (KVM) Equipment

SPEC.5.5.2.1     General

SPEC.5.5.2.1.1   KVM equipment types must include console, rack mountable, and one suited for the
desktop.

SPEC.5.5.2.1.2   Keyboard must be full size, standard QWERTY keyboard.

SPEC.5.5.2.1.3   All KVM must be wired (i.e., not wireless).


SPEC.5.5.2.2     Console KVM

SPEC.5.5.2.2.1 Console KVM must fit within the space requirements described in Section SPEC.5.4 -
Physical Requirements unless otherwise specified.


SPEC.5.5.2.3     Rack-Mountable KVM

SPEC.5.5.2.3.1   Rack mounted video monitor must be flat panel and a minimum 15 inch, diagonally
measured.

SPEC.5.5.2.3.2   Rack-mountable KVMs must not be more than 1 RU.

SPEC.5.5.2.3.3   A KVM switch must be used for intra-rack equipment.

SPEC.5.5.2.3.4   A KVM switch must not be used to provide inter-rack connections.


SPEC.5.5.2.4     Desktop KVM

SPEC.5.5.2.4.1   Desktop video monitors must be flat panel and a minimum of 21 inch, diagonally
measured.



10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 66
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


SPEC.5.5.3       ZAN ARTCC and AFSS Server Requirements

SPEC.5.5.3.1     NMCS servers must utilize products which are rated for use in data centers.

SPEC.5.5.3.2    NMCS servers at the hubs must continue to operate without loss of data or interruption in
NMCS service in the event of a single drive failure.

SPEC.5.5.3.3     Each hub site must have a local collector(s).

SPEC.5.5.3.4     All NMCS servers must use the same operating system.

SPEC.5.5.3.5     Office 2007 and Internet Explorer 7 must not be used on the servers.

SPEC.5.5.3.6        All hub NMCS equipment must use the same hardware, software, and operating system
from site to site, except where functional or performance requirements dictate a different hardware model.

SPEC.5.5.3.7     A specific function must be provided by the same type of NMCS equipment at each site
(e.g., a DHCP service cannot run at one hub on the switch, another hub on the router.)



SPEC.5.5.4       Remote NMCS Equipment Requirements

SPEC.5.5.4.1     Each remote site NMCS must have a local collector(s).

SPEC.5.5.4.2     Each remote site NMCS must be capable of presenting a local management interface.

SPEC.5.5.4.3      Remote Site NMCS equipment must use internal COTS Solid State Drives (SSDs) when
hard drives are used.

SPEC.5.5.4.3.1 SSDs must support a MTBF that is consistent with the availability requirements of
Section SPEC.5.9.1.3 - NMCS AvailabilityNMCS Availability, and be no less than 1.5 million hours.            Formatted: Font: Not Bold


SPEC.5.5.4.3.2   The SSDs must be compatible with NMCS equipment’s native bus architecture.

SPEC.5.5.4.4      All remote NMCS equipment must use the same hardware, software, and operating
system for each site.

SPEC.5.5.4.5    NMCS must be capable of having a rack-mountable KVM (as specified in SPEC.5.5.2,
Keyboard, Video Monitor, and Mouse (KVM) Equipment) attached to access the local management
interface.

SPEC.5.5.4.6     In lieu of using the KVM detailed above, the NMCS must allow a user to use FAA
laptops.

SPEC.5.5.4.7      The NMCS must allow a user to access the local management interface using Internet
Explorer (version 6.5 and higher) and Mozilla Firefox (version 3.0 and higher) without the need for
additional software or changing software versions (i.e. Internet Explorer or any plug-in software).




10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 67
ASTI                                             Amendment 5                                 DTFAWA-10-R-00039


SPEC.5.5.4.7.1 Client-server technologies that do not require installation or modification of additional
software (i.e. mobile code technologies31) are acceptable. For example, Java (version 1.6 and higher) or
Flash32 (version 10.0 and higher.)

SPEC.5.5.4.8       The NMCS local management interface must function on:

             a) The KVM
             b) An FAA laptop with or without the user having administrative privileges to the laptop.

SPEC.5.5.4.9       The NMCS must have the capability to remotely disable the laptop local management
interface.

SPEC.5.5.4.10      Office 2007 and Internet Explorer 7 must not be used on the remote equipment.

SPEC.5.5.4.11 A specific function must be provided by the same type of NMCS equipment at each site
(e.g., a DHCP service cannot run at one hub on the switch, another hub on the router.)



SPEC.5.5.5         Workstation Requirements

SPEC.5.5.5.1     The NMCS must have the capability to support the simultaneous operation of a minimum
of twenty (20) workstations, each having complete functional capability as required by Section SPEC.5 -
Network Management and Control System (NMCS) RequirementsNetwork Management and Control
System (NMCS) Requirements.

SPEC.5.5.5.2      From a single NMCS workstation, a user must be capable of accessing all authorized
features and performing all authorized functions IAW Section SPEC.5 - Network Management and Control
System (NMCS) RequirementsNetwork Management and Control System (NMCS) Requirements for the
ASTI network.

SPEC.5.5.5.3       All NMCS workstations must use the same hardware and operating system.

SPEC.5.5.5.4       The management and control of all ASTI Network NEs must be via a graphical user
interface.

SPEC.5.5.5.5       Each NMCS workstation must include a KVM and a computer.

SPEC.5.5.5.6       Workstations must be of a quality that is used in a data center environment.

SPEC.5.5.5.7       The AFSS Hub workstations must be rack mountable.

SPEC.5.5.5.8   In the event of a server failure the workstation must continue to function and access other
NMCS services IAW user authorization(s).

31
   Mobile code is software obtained from remote systems, transferred across a network, and then downloaded and
executed on a local system without explicit installation or execution by the recipient. Examples of mobile code include
scripts (JavaScript, VBScript), Java applets, ActiveX controls, Flash animations, Shockwave movies (and Xtras).
32
   For example, Flash could be used, as long as it is compatible with the version of Flash on the GFE laptop, which is
not under control of the ASTI program. Software is approved by WSA IT Service Center, and implemented via
automated updates from local IT support groups.
10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 68
ASTI                                          Amendment 5                            DTFAWA-10-R-00039


SPEC.5.5.5.9   The failure of one or more workstations must not impact the operation of the ASTI
network or NMCS.

SPEC.5.5.5.10       Workstations must accommodate individual profiles that are user-specified groupings of
windows which require user authentication permission to access (See Section SPEC.5.8.1.4 for single point
of administration.)

SPEC.5.5.5.11      The workstation must be compatible with the communications requirements and
bandwidth restrictions of the NMCS (See Section SPEC.5.7.1.5 - NMCS Communication CircuitsNMCS               Formatted: Font: Not Bold
Communication Circuits.)

SPEC.5.5.5.12   The workstation must operate as a client in a client server relationship, accessing and
displaying NMCS applications running on NMCS servers and appliances.

SPEC.5.5.5.13     The workstation must provide “print screen” capability to save the graphical information
displayed on the monitor or a specified window to an electronic file (e.g., .jpg, .gif.)

SPEC.5.5.5.14  The workstation must provide controlled and logged USB access for retrieval of data
from the NMCS.

SPEC.5.5.5.15       Office 2007 and Internet Explorer 7 must not be used on a workstation.

SPEC.5.5.5.16      A user must be capable of unlocking a locked workstation display without forcing the
user to logoff.



SPEC.5.5.6         Printer Requirements

SPEC.5.5.6.1       The NMCS must have the capability to support the simultaneous operation of a minimum
of ten (10) printers, each having complete functional capability as required by this Section SPEC.5 -
Network Management and Control System (NMCS) RequirementsNetwork Management and Control
System (NMCS) Requirements.

SPEC.5.5.6.2     NMCS printers must be capable of producing a hard copy of graphical information that is
displayed on both the monitor and a specified window.

SPEC.5.5.6.3      NMCS printers must be capable of producing a hard copy of information that is prepared
by the graphical user interface but is not necessarily displayed on the monitor.

SPEC.5.5.6.4    A compact printer must meet the size constraints of Section SPEC.5.4 -Physical
Requirements and have the following characteristics:

             a)   laser-jet
             b)   full-color
             c)   print 17 pages per minute in black & white mode
             d)   using 8-1/2” X 11” sheets of 20 pound paper

SPEC.5.5.6.5       A full-size printer must have the following characteristics:

             a) laser-jet

10/07/10                                        SECTION J-1: ASTI TECHNICAL SPECIFICATION - 69
ASTI                                           Amendment 5                               DTFAWA-10-R-00039


             b)   full-color
             c)   print 17 pages per minute in black & white mode
             d)   using 8-1/2” X 11” sheets of 20 pound paper
             e)    using 11” x 17” sheets of 20 pound paper.
             f)   capable of full duplex printing without manual paper feed

SPEC.5.5.6.6       Printers must have an Ethernet port and support TCP/IP.

SPEC.5.5.6.7       All printers must be accessible from all NMCS workstations located at the ZAN ARTCC
and the Hubs.



SPEC.5.5.7         Operating Systems

SPEC.5.5.7.1        All Operating Systems (OS) used in the NMCS must be COTS product(s) which are
utilized in a data center environment.

SPEC.5.5.7.2    The OS must have native capability to support disk configurations of Redundant Array of
Independent Disks (RAID) 0, 1, and 5.

SPEC.5.5.7.3       Microsoft Vista must not be used.

SPEC.5.5.7.4       The NMCS server(s) OS file system(s) must utilize a file system metadata logging
technology that ensures the OS writes file system updates (metadata) to a log prior to applying the updates
to the file system.33

SPEC.5.5.7.5       Upon an application’s fatal error (e.g., abnormal termination), the OS must automatically
trigger the creation of a core dump.

SPEC.5.5.7.5.1     A core dump must be comprised of, at a minimum:
             a)   Recorded state of the working memory of the application
             b)   Specific time when the program abnormally terminated
             c)   Processor registers (including program counter & stack pointer)
             d)   Memory management information
             e)   Other processor, OS flags, and information that is useful in troubleshooting the abnormal
                  application termination.

SPEC.5.5.7.6      Every OS must have native capability to reliably transmit encrypted syslog data from
remote and local sites to the log aggregation subsystem, including mechanisms to enable the syslog data to
be authenticated.

SPEC.5.5.7.6.1 Reliable, encrypted, and authenticated log aggregation must be IAW NIST SP 800-92,
Guide to Computer Security Log Management.


SPEC.5.5.7.7       Patches must be traceable to a unique patch LRU regardless of delivery and bundling
method.34

33
   Logging file systems borrows from database technology and adds the concept of transactions and two-phase commit
to the file system.
10/07/10                                         SECTION J-1: ASTI TECHNICAL SPECIFICATION - 70
ASTI                                             Amendment 5                                 DTFAWA-10-R-00039


SPEC.5.5.7.8       Patches must track obsolescence of previous patches.

SPEC.5.5.7.9       Patches must track incorporation of other patches.

SPEC.5.5.7.10      Patches must be capable of being backed out.



SPEC.5.5.8         NMCS Networking Equipment

SPEC.5.5.8.1       NMCS Networking Equipment must utilize COTS products which are rated for use in
data centers.

SPEC.5.5.8.2       The NMCS must not include Ethernet hubs or unmanaged switches.

SPEC.5.5.8.3       A specific function must be provided by the same type of network equipment at each site.

SPEC.5.5.8.4       At hubs, servers must not perform IP routing functions.

SPEC.5.5.9         NMCS Networking Standards

SPEC.5.5.9.1       The NMCS must function without connection to the internet or any other network or
outside device.

SPEC.5.5.9.2       The NMCS must be a closed network.35

SPEC.5.5.9.3       Every IP addressable NE must have a unique host name.

SPEC.5.5.9.4   The NMCS must follow the FAA ATO Network Standards version 1.2 or higher, for
LAN Cable Specifications. In addition, the NMCS LAN cabling must also meet the following:

SPEC.5.5.9.4.1 Type UTP Category 5E, or better, network cable must be used and must meet or exceed
the requirements of EIA/TIA 568-B and tested IAW EIA/TIA TSB-67.

SPEC.5.5.9.5     Where Ethernet ports are used that face outward from the front of the rack, feed-through
patch panels must be used.

SPEC.5.5.9.6      At hub sites where multiple Ethernet cables are used, patch panels must be used for
Ethernet within each rack.

SPEC.5.5.9.7       Ethernet patch panels must be labeled.

SPEC.5.5.9.8       The NMCS must follow the FAA ATO Network Standards version 1.2 or higher for the
following:

             a) Access Control
             b) VLANs
             c) UDLD

34
   In other words, patch 123456-78 must be identified as such whether it is downloaded individually or as part of a
patch cluster.
35
   Dial backup for Phase 2 sites is an exception to this requirement.
10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 71
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


SPEC.5.5.9.9       When used, the NMCS must follow the FAA ATO Network Standards version 1.2 or
higher for the following:

            a)   Spanning Tree (including Spanning Tree Protocol [STP] Root Determination)
            b)   Protocol Selection
            c)   Ether Channel
            d)   Trunks
            e)   Dynamic Routing Protocols
            f)   Static Routes

SPEC.5.5.10       General Database Requirements

SPEC.5.5.10.1   All NMCS databases must allow for Open Database Connectivity (ODBC) IAW
ISO/IEC 9075-3.

SPEC.5.5.10.2      All NMCS databases must be of an enterprise level, data center grade.

SPEC.5.5.10.3      NMCS database data must be accessible and modifiable by a user.

SPEC.5.5.10.4      NMCS database schema must be accessible and extendable by a user.

SPEC.5.5.10.5     All NMCS DataBase Management Systems (DBMS) must be capable of importing data
via ODBC or flat file.



SPEC.5.5.11       General Reporting Requirements

SPEC.5.5.11.1    The NMCS must contain report generation functions consistent with the requirements in
Section SPEC.5 - Network Management and Control System (NMCS) RequirementsNetwork Management
and Control System (NMCS) Requirements.

SPEC.5.5.11.1.1 The NMCS must contain standard reports IAW Section SPEC.5 - Network Management
and Control System (NMCS) RequirementsNetwork Management and Control System (NMCS)
Requirements.

SPEC.5.5.11.1.2 The NMCS must contain standard reports which can be customized without having to
write code, write SQL statements, or have understanding of the schema.

SPEC.5.5.11.1.3 The NMCS must be capable of creating and modifying reports without writing code or
SQL statements.

SPEC.5.5.11.1.4 The NMCS must be capable of creating and modifying reports by writing code and SQL
statements.

SPEC.5.5.11.2      The NMCS must have the capability to schedule report generation with a user specified
time, date, and frequency.

SPEC.5.5.11.3   Development, deployment, processing, and printing of reports must not interfere with the
performance, management, and control of the ASTI network.


10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 72
ASTI                                             Amendment 5                                  DTFAWA-10-R-00039


SPEC.5.5.11.4       The reports must be generated using information in the NMCS databases.

SPEC.5.5.11.5 The NMCS report output format must use standard formats which include at a minimum,
PDF and HTML.

SPEC.5.5.11.6     The NMCS must have the capability to export reports in standard formats, which
includes at a minimum, configurable character delimited format and XLS.

SPEC.5.5.11.7       The NMCS must be capable of displaying reports via workstations.



SPEC.5.5.12        NMCS Component Redundancy

 If NMCS component redundancy is used, the NMCS must meet the following requirements.

SPEC.5.5.12.1       Any NMCS components that are redundant must be capable of automatic failover.

SPEC.5.5.12.2       Any NMCS components that are redundant must operate in a hot standby configuration.

SPEC.5.5.12.3 Redundant NMCS components must be capable of having automatic failover disabled
through the NMCS.

SPEC.5.5.12.4   Automatic and manual failover must switch within 30 seconds to a hot standby
component and achieve full operation.

SPEC.5.5.12.5       All hot standby NMCS components must continually monitor the status of the primary
component.

SPEC.5.5.12.6   All redundant NMCS components must have the capability to provide network
management functions currently being provided by the primary component.

SPEC.5.5.12.7     The failover to the hot standby NMCS component must be capable of being initiated
automatically by the NMCS or manually by a user.

SPEC.5.5.12.8    Manual failover must have options for graceful and immediate modes, where graceful
mode must include proper shutdown and startup of processes, closure of files, etc.

SPEC.5.5.12.9    The automatic failover capability must be configurable by a user based on hardware and
software Reportable Events (RE)36.

SPEC.5.5.12.10 Automatic failover must have options for graceful and immediate modes, where it is
configurable by a user based on the RE.

SPEC.5.5.12.11 The NMCS must monitor the status of the backup component.



36
  The term “reportable event (RE)” refers to normal conditions and abnormal conditions (states) of hardware and
software. Reportable events can be configured as faults, and have several levels of severity. The values of the limits
and constraints for each severity level will be configurable by the FAA. For purposes of this document, faults, alarms,
and alerts will be considered the same.
10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 73
ASTI                                             Amendment 5                                DTFAWA-10-R-00039


SPEC.5.6           Fault Management Requirements

NMCS Fault Management must detect, isolate, notify, correct, and log faults37 encountered in the ASTI
Network and NMCS. A fault is an event which has a negative significance.

SPEC.5.6.1         General Requirements

SPEC.5.6.1.1     The AFSS hub NMCS must be able to perform fault management functions of the ASTI
network as described in Section SPEC.5.7.1.3 - Network Management and Control from the AFSS                            Formatted: Font: Not Bold
HubNetwork Management and Control from the AFSS Hub.

SPEC.5.6.1.2       NMCS Fault Management Servers at the Hubs

SPEC.5.6.1.2.1     Software upgrades, patches, releases, etc. must be testable in a production environment.

SPEC.5.6.1.2.2 Servers must be capable of being isolated and tested off-line, during which all NMCS
functions, including fault management, must continue to operate.

SPEC.5.6.1.2.3 Updates must be capable of being rolled in or out within 30 seconds not including the
time to download.38


SPEC.5.6.2         Local Management39 of Remote Site Equipment

SPEC.5.6.2.1       The NMCS must allow a user local element-level management of the remote site.

SPEC.5.6.2.1.1 Local management of a remote site must continue to operate when NMCS
communications fails between the hubs and a remote site.

SPEC.5.6.2.1.2     Local REs must be capable of being displayed on a FAA laptop and the local KVM.

SPEC.5.6.2.1.3 Local NEs must be capable of being configured though the local collector from a FAA
laptop and the local KVM.

SPEC.5.6.2.1.4 Local diagnostic features of local NEs must be capable of being used through the local
collector from a FAA laptop and the local KVM.

SPEC.5.6.2.2       The NMCS must prevent a user at a remote site from remotely accessing any other site.

SPEC.5.6.2.3       The NMCS must provide local authentication and authorization for a user at the site to
enable the user to use the NMCS to work on the ASTI Network.

SPEC.5.6.2.4       The NMCS must maintain a rolling one-week worth of RE data for each site and be
available to a user located at each site.



37
   A fault is defined as a condition within one or more NEs which results in improper behavior of some aspect of the
network.
38
   This does not apply to equipment in standby mode.
39
   Local management is defined as managing and controlling the NEs at the ASTI site where the user physically is
located.
10/07/10                                          SECTION J-1: ASTI TECHNICAL SPECIFICATION - 74
ASTI                                         Amendment 5                              DTFAWA-10-R-00039


SPEC.5.6.2.5       Data not transmitted when first occurring due to loss of NMCS communications must be
transmitted after NMCS communications are restored.

SPEC.5.6.2.6       The network management system must enable a user to pass-through the
controller/collector to connect to the local network element interface using native interface language.



SPEC.5.6.3        Element Management

SPEC.5.6.3.1      General Functional Requirements

SPEC.5.6.3.1.1    All NEs must have a unique resource name using the naming convention defined in
Appendix G.

SPEC.5.6.3.1.2    All NEs must use the NMCS resource name as its host name.

SPEC.5.6.3.1.3    The presence of a RE must not inhibit normal control of the display by the user.


SPEC.5.6.3.2      General Element Interface Requirements

SPEC.5.6.3.2.1 The element manager must provide a standard form of indication or summary of the
overall health of the NE.

SPEC.5.6.3.2.2 The element manager must have a standard form of indicating communication status
between the NE and NMCS.

SPEC.5.6.3.2.3 All element manager user commands must give user feedback as to the beginning and end
of an operation, as well as outcome and time stamp.

SPEC.5.6.3.2.4 A user command must be delivered to the agent managing the recipient NE within five
seconds of issuance.

SPEC.5.6.3.2.4.1 Acknowledgement of the user command delivery must be provided to the user within ten
seconds of receipt of the command.

SPEC.5.6.3.2.5    The NMCS must provide incremental status updates throughout the completion of any
user command.

SPEC.5.6.3.2.6    For all parameters, the element manager must provide parameters by reading current data
from the NE.


SPEC.5.6.3.3      Element Management for Legacy NEs.

SPEC.5.6.3.3.1 The NMCS must provide for the management and control of all legacy network elements
as required throughout transition and the end-state configuration. – see Appendix D.

SPEC.5.6.3.4      Element Management for New ASTI NEs

10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 75
ASTI                                             Amendment 5                                  DTFAWA-10-R-00039


SPEC.5.6.3.4.1 The NMCS must provide for the management and control of all network elements of the
new ASTI Network.

SPEC.5.6.3.4.2      NMCS must use SNMP v3 to manage ASTI NEs as applicable for the specific NE.

SPEC.5.6.3.4.3 The NE must use SNMP v3 except where specifically described otherwise in Section
SPEC.4 - Requirements for Replaced ASTI Components.

SPEC.5.6.3.4.4      Management of SNMP v3 NEs must use authentication.

SPEC.5.6.3.4.5      Management of SNMP v3 NEs must use TCP.




SPEC.5.6.3.5        ASTI Telco NE Management Interface

     The NMCS must have the capability to analyze operational performance data from all ASTI telco NEs,
     identify problems and trends with regard to telecommunications circuit and channel performance as well
     as individual component performance. The generic minimum set of management interface requirements
     are listed below, and must be tuned for each specific equipment type provided by the contractor.


SPEC.5.6.3.5.1      Multiplexer NE Management and Control

SPEC.5.6.3.5.2 The NMCS must provide REs for faults and status for multiplexer features specified in
Section SPEC.4 - Requirements for Replaced ASTI Components with the following as a minimum:
              a) All native channel-level and aggregate-level faults by channel, aggregate, or endpoint
              b) Un-routed channels
              c) E and M, 2-wire, and 4-wire signaling faults
              d) E and M, 2-wire, and 4-wire signaling status
              e) Aggregate-level BER performance
              f) Aggregate-level sync status
              g) All native node-level40 faults by node
              h) All channel-level and aggregate-level clocking faults
              i)   All channel-level and aggregate-level loopback status
              j)   All aggregate-level errored seconds, SES, CSES, and LOS


SPEC.5.6.3.5.3      RF BUC/SSPA NE Management and Control



40
  For purposes of this specification, multiplexer node (or node) is defined generically as an addressable (uniquely
identifiable) entry and exit point for channels and aggregates.
10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 76
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


SPEC.5.6.3.5.4 The NMCS must provide management and control for BUC/SSPA features specified in
Section SPEC.4 - Requirements for Replaced ASTI Components with the following as a minimum:
           a)     Provide RF output status in terms of power out, TX/RX attenuation, DC current, DC
                  voltage, and temperature
           b)     Control RF output (On, Off)
           c)     Provide RF output status (On, Off)
           d)     Control transmit and receive attenuation in minimum 1 dB steps
           e)     Configure BUC/SSPA addresses and names (redundant units)
           f)     Provide status of unit-to-unit communications (redundant units)
           g)     Provide auto/manual control (redundant units)
           h)     Switch BUC/SSPA (redundant units)
           i)     Provide status of reference signal (external, internal)
           j)     Provide all additional native BUC/SSPA faults and controls

SPEC.5.6.3.5.5   RF LNB NE Management and Control

SPEC.5.6.3.5.6 The NMCS must provide management and control for LNB features specified in Section
SPEC.4 - Requirements for Replaced ASTI Components with the following as a minimum:
           a) Provide IF L-Band output status
           b) Provide power supply status in terms of faults, high and low current thresholds
           c) Provide status of reference signal (external, internal)
           d) Provide all native LNB faults


SPEC.5.6.3.5.7   RF Waveguide Switch NE Management and Control

SPEC.5.6.3.5.8 The NMCS must provide management and control for waveguide switch features
specified in Section 4 with the following as a minimum:
           a)     Control waveguide switch position (A->B, B->A)
           b)     Control waveguide switch mode (manual, automatic)
           c)     Provide waveguide switch position status
           d)     Provide waveguide switch mode status
           e)     Provide all native waveguide switch faults

SPEC.5.6.3.5.9   RF 70 MHz IF Replacement SSPA/Converter NEs Management and Control

SPEC.5.6.3.5.10 If used, management of replacement NE types for SSPA, LNA, and Up/Down Converter
in 70 MHz must be consistent with the L-Band BUC/SSPA and LNB configuration, except for the
following:
           a)     Control and status of up and down frequencies in minimum 2.5 Mhz. steps

10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 77
ASTI                                         Amendment 5                           DTFAWA-10-R-00039


           b)      External frequency reference, where implemented, must be managed ,
           c)      DC voltage to LNA must be managed.


SPEC.5.6.3.5.11 RF Legacy NEs

SPEC.5.6.3.5.12 The interfaces for the management and control of the remaining Legacy RF NE types
(e.g., dehydrators, beacon receivers) must meet the requirements of Appendix D.


SPEC.5.6.3.5.13 Modem NE Management and Control

SPEC.5.6.3.5.14 The NMCS must provide management and control for modem features specified in
Section SPEC.4 – Requirements for Replaced ASTI Components, with the following as a minimum:
           a) Control of modulator and demodulator frequencies in terms of L-Band (if applicable) and
              70 MHz IF (if applicable) frequencies
           b) Status of modulator and demodulator frequencies in terms of L (if applicable), 70 MHz IF
              (if applicable) and C (for L band applications) band frequencies
           c) Calculate accurate C-Band up and down frequencies based on current L-Band modem
              frequencies in both modulator and demodulator frequencies.
           d) The resultant calculations must be REs.
           e) Control and status of modulator state (On, Off)
           f) Control and status of modulator output power in a minimum of 0.1 dB increments
           g) Control and status of paired carrier multiple access configuration (On, Off)
           h) Control and status of modulator and demodulator encoding, decoding, and FEC schemes
              IAW Section SPEC.4 - Requirements for Replaced ASTI Components
           i)   Control and status of modulator and demodulator encoding and decoding rates
           j)   Control and status of single and dual Continuous Wave (CW) signals
           k) Control and status of RF, IF, baseband, and any other native loopbacks
           l)   Control and status of all clocking parameters
           m) Control and status of buffer
           n) Status of performance diagnostics, including raw BER, corrected BER, Eb/No, Rx level,
              buffer status, paired carrier ratio, pair carrier delay
           o) Control and status of sweep center, width range, sweep reacquisition time
           p) Control and status of differential encoder and decoder
           q) Control and status of scrambler and descrambler
           r) Control and status of spectrum inversion
           s) Provide status of fault tolerant communications (redundant units)
           t)   Control and status of modem settings of receive LNB local oscillator (LO) and transmit
                BUC local oscillator (LO)
10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 78
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


           u) Provide pass through for NE’s spectrum analyzer
           v) Provide control and status of upgradeable modem firmware options (e.g. status and
              capability to turn on paired carrier multiple access, presence of option boards, including
              any data entry required by the modem.)
           w) Provide polled fault status every 25-35 seconds, for similar types of data described by
              Modem Fault Status, Modulator Status, Demodulator Status, and Bulk Consolidated Status
              Faults as described for the most current satellite modem used in ASTI as listed in Appendix
              D
           x) Provide all additional pertinent native modem faults and controls required to manage the
              ASTI network




SPEC.5.6.3.5.15 Modem M:N Switch NE Management and Control

SPEC.5.6.3.5.15.1       The NMCS must provide management and control for M:N switch features
specified in Section SPEC.4 - Requirements for Replaced ASTI Components with the following as a
minimum:
           a) Control and status of the prime modem(s)
           b) Control and status of the backup modem(s)
           c) Status of prime and backup modems in terms of backup status, transmit and receive faults
           d) Load configurations of prime modems (single or all)
           e) Verify configurations of prime modems (single or all)
           f) Configure switch to add or delete prime modem
           g) Configure modem addresses and communications
           h) Configure switch priorities
           i)   Control modem switch mode (manual, automatic)
           j)   Provide all native modem switch faults

SPEC.5.6.3.5.16 Modem 1:1 Switch Function NE Management and Control

SPEC.5.6.3.5.16.1      The NMCS must provide management and control for 1:1 switch features specified
in Section SPEC.4 - Requirements for Replaced ASTI Components with the following as a minimum:
           a) Control for manually, dependently or independently switch modem modulator and/or
              demodulator into service (A or B modem)
           b) Status of A and B modems in terms of backup status, transmit and receive faults
           c) Verify configurations of A and B modems
           d) Load modem configurations (B->A or A->B)

10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 79
ASTI                                         Amendment 5                             DTFAWA-10-R-00039


            e) Control modem switch mode (manual, automatic)
            f) Configure modem addresses and communications
            g) Provide status of fault tolerant communications (redundant units)
            h) Provide all native modem switch faults

SPEC.5.6.3.5.17 UPS NE management and control

SPEC.5.6.3.5.17.1     The interface for the management and control of the UPS NE type must meet the
requirements of Appendix D.


SPEC.5.6.3.5.18 SCADA management and control

SPEC.5.6.3.5.18.1         The interfaces for the management and control of the SCADA NE type and the
multiple, site specific configurations must meet the requirements of Appendix D.


SPEC.5.6.3.5.19 Antenna De-icer management and control

SPEC.5.6.3.5.19.1      The interfaces for the management and control of the Antenna De-icer NE types
must meet the requirements of Appendix D.


SPEC.5.6.3.5.20 Antenna Controllers management and control

SPEC.5.6.3.5.20.1      The interfaces for the management and control of the Antenna Controller NE type
must meet the requirements of Appendix D.

SPEC.5.6.3.5.21 Automatic Circuit Protection Switch Management and Control - The NMCS must provide
management and control for all automatic circuit protection switch features and functionality as specified in
Sections SPEC.3 - ASTI Service and System Requirements and SPEC.4 - Requirements for Replaced ASTI
Components with the following as a minimum:
            a) Status of the current position of the automatic channel protection switches.
            b) Provide history of all switch activity.
            c) Provide status and control to support service level management requirements in Section
               SPEC.5.6.5.2 - Network and Service Status and ControlNetwork and Service Status and              Formatted: Font: Not Bold
               Control.

SPEC.5.6.3.5.22 The NMCS must provide management and control for any other components provided to
meet the requirements specified in Sections SPEC.3 - ASTI Service and System Requirements and SPEC.4
- Requirements for Replaced ASTI Components.


SPEC.5.6.3.6      ASTI NMCS NE Management Interface (Self-Management)

SPEC.5.6.3.6.1    General – The NMCS must provide status for the following at a minimum:
            a) NMCS NE warm and cold starts
10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 80
ASTI                                          Amendment 5                         DTFAWA-10-R-00039


           b) NMCS NE uptime
           c) NMCS NE environmental conditions
           d) NMCS NE CPU and memory utilization
           e) NMCS NE power supply

SPEC.5.6.3.6.2    Routers and Switches – The NMCS must provide status for the following at a minimum:
           a) Interface Up/Downs
           b) Interface Resets
           c) Interface Incoming Traffic in Bits per Second
           d) Interface Outgoing Traffic in Bits per Second
           e) Interface % utilization over time
           f) Interface CRC errors over time
           g) Interface Fragments over time
           h) Interface Runts over time
           i)    Interface Giants over time
           j)    Interface I/O errors
           k) Trap on dynamic routing changes
           l)    Trap on spanning tree changes
           m) Dial backup status (Phase II remotes only)
           n) If dial backup is implemented, management interface must provide user control to initiate
              and terminate dial backup session.
           o) Where dial backup is implemented, management interface must allow a user to disable any
              and all dial backup access points IAW FAA order 1370.89.
           p) Where dial backup is implemented, it must conform to guidance listed in DOT 10-202
              under Section 4.1.3.3, Dial-in Controls, items u, v, and x.

SPEC.5.6.3.6.3    Servers – The NMCS must provide the status for the following at a minimum:
           a) Disk space
           b) Disk and disk controller utilization
           c) Application (implementation dependent)
           d) Network interface utilization and status
           e) Socket connection utilization and status for NMCS to legacy serial based NEs
           f) Synchronous and asynchronous ports connected to NEs for network management and
              control which are in use for pass-through to NE’s native management interface (e.g. an RE
              to indicate a technician is using a VT100 interface on an SSPA)


SPEC.5.6.3.7      SNMP Management Information Base (MIB) Browser

10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 81
ASTI                                                          Amendment 5                                             DTFAWA-10-R-00039


SPEC.5.6.3.7.1 The MIB Browser must provide all MIB data to provide the status of the ASTI Network
and the control, diagnosis and configuration of the SNMP-based ASTI Network NEs.

SPEC.5.6.3.7.2           The MIB Browser must be integrated into the NE element manager.

SPEC.5.6.3.7.3           The MIB Browser application must have the capability to read MIB files.

SPEC.5.6.3.7.4 Standard IANA MIBs, the RFC MIBs and the private MIBs from the new ASTI
hardware/server manufacturers must be readable and importable throughout the NMCS.

SPEC.5.6.3.7.5           The MIB Browser application must have the ability to visualize and navigate the MIB
tree.

SPEC.5.6.3.7.6 The MIB Browser must have the capability to query, change and monitor the raw value of
the management objects.

SPEC.5.6.3.8             Agent Development Environment41

SPEC.5.6.3.8.1           The NMCS must have an open, integrated agent development environment.

SPEC.5.6.3.8.2           The agent development environment must be object-oriented.

SPEC.5.6.3.8.3           The agent development environment must use visual programming (e.g., drag and drop.)

SPEC.5.6.3.8.4 The agent development environment must have the option to modify agents via Character
User Interface (CUI).

SPEC.5.6.3.8.5 The agents delivered must be developed with and capable of being modified by the agent
visual development environment.

SPEC.5.6.3.8.6 Where required, the agent development environment must use industry-standard, high
level languages such as Java.

SPEC.5.6.3.8.7 Agents developed must be capable of interpreting, transforming, and reporting native NE
interface data into REs using functions such as string manipulation, numerical operations, data persistence,
delta values, and thresholds.

SPEC.5.6.3.8.8           The agent development environment must have an integrated, run-time debugger.

SPEC.5.6.3.8.9 The agent development environment must have functions to document agent
implementation.

SPEC.5.6.3.8.10 The agent development environment must be integrated with the functionality associated
with configuration management of agents described in Section SPEC.5.7 - Configuration Management
Requirements.




41
  The agents referenced here and throughout this text are also referred to in industry products as scripts or drivers, and should not be confused with
SNMP agents.
10/07/10                                                        SECTION J-1: ASTI TECHNICAL SPECIFICATION - 82
ASTI                                         Amendment 5                             DTFAWA-10-R-00039


SPEC.5.6.4        Reportable Events (REs)

SPEC.5.6.4.1      The NMCS must display REs.

SPEC.5.6.4.2      REs must be created by agents on collector(s) local to the NEs.

SPEC.5.6.4.3      REs must be derived from data (or lack of data) from the NEs.

SPEC.5.6.4.4      Agents must determine severity of REs.

SPEC.5.6.4.4.1    Severity levels must be configurable by a user.

SPEC.5.6.4.4.2 The values of the limits and constraints (e.g., thresholds, deltas) for each severity level
must be user configurable.

SPEC.5.6.4.5      The following data types, at a minimum, must be supported as REs from the collector(s):

             a) Statistical data
             b) Attribute (Configuration and State) data
             c) Fault data

SPEC.5.6.4.6      A RE must be user configurable as a fault.

SPEC.5.6.4.7      A RE textual description must be user configurable.

SPEC.5.6.4.8      REs with severity levels must be user configurable.

SPEC.5.6.4.8.1    The NMCS must allow for a minimum of five severity levels.

SPEC.5.6.4.9      When an RE is based on polled data, the polling rate must be user configurable.

SPEC.5.6.4.9.1    Polling rates must be in second increments at a minimum.

SPEC.5.6.4.9.2    Polling rates must support between zero and 3600 second intervals at a minimum.

SPEC.5.6.4.10      The REs must be user configurable for audible notifications.

SPEC.5.6.4.10.1 The NMCS must have the capability for the user to silence the audible notification.

SPEC.5.6.4.10.2 The NMCS must have the capability for the user to enable and disable the audible
notification feature.

SPEC.5.6.4.11      The NMCS must automatically report, within 90 seconds of occurrence, all fault
conditions, including but not limited to degradations and failures involving NEs, hubs, remotes, nodes,
paths, and channels



SPEC.5.6.5        Network and Service Management

SPEC.5.6.5.1      ASTI Network Views
10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 83
ASTI                                              Amendment 5                             DTFAWA-10-R-00039


SPEC.5.6.5.1.1 ASTI network views (henceforth referred to as views) must be configurable, graphical,
and resemble the logical and physical network.

SPEC.5.6.5.1.2 The view(s) must be presented in a hierarchy of scenes with reducing scope but increasing
clarity and detail for effective presentation, at minimum to the NE level, with views organized by:
            a) Geographical
            b) Functional
            c) Service-level
                  i.     LID/FAC (e.g., radar)
                  ii. ASTI circuit number
                  iii. Telco circuit number
                  iv. ASTI circuit-level view

SPEC.5.6.5.1.3         Each network view must capable of being assigned independent user and group
authorizations.

SPEC.5.6.5.1.4 Each RE and individual control (used to perform tasks such as configure and diagnose
NEs) must capable of being assigned independent user and group authorizations.

SPEC.5.6.5.1.5         The location, nature and extent of any degradations or failures must be clearly indicated
and organized.

SPEC.5.6.5.1.6         The view must provide a hierarchical tree view of the ASTI Network at a minimum to the
NE level.

SPEC.5.6.5.1.6.1 The hierarchical tree must provide the capability to select any level within the tree and
show the corresponding scene within the view.

SPEC.5.6.5.1.6.2 The hierarchical tree must provide the status of each level within the tree.

SPEC.5.6.5.1.7 The view must provide information and data documenting the routing of the
communications circuit through the ASTI NEs from ADP to ADP with sufficient detail to trace it
throughout the ASTI network.

SPEC.5.6.5.1.8 The view must depict the aggregates, circuits, and channels associated with any selected
hub, remote, node, or ADP and list those that are under test.

SPEC.5.6.5.1.8.1 The view must be provided in graphical and list formats.

SPEC.5.6.5.1.9 Within the NMCS, the labeling of designators (e.g., names, codes or abbreviations) must
be user configurable and use conventions specified in Appendix G.

SPEC.5.6.5.1.9.1 At a minimum, each hub, remote, node, NE, LRU, circuit and channel must have user
configurable designators,

SPEC.5.6.5.1.9.2 The NMCS must allow a user to modify, delete, and add designators.

SPEC.5.6.5.1.10 A view must be configurable to provide the user with access to all NE element managers.
10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 84
ASTI                                          Amendment 5                             DTFAWA-10-R-00039


SPEC.5.6.5.1.11 From any NE or RE within a view, NMCS must provide view-integrated reporting as              Formatted: Font: Not Bold
described in Section SPEC.5.6.7.1 - View Integrated ReportingView Integrated Reporting.

SPEC.5.6.5.1.12 A view must clearly label every scene or window with the appropriate site name and the
appropriate ASTI service (e.g., path, aggregate, circuit, channel.)

SPEC.5.6.5.1.13 A view must provide a dynamic representation of network elements under the following
conditions:
            a) Agent discovery of element
            b) Management (e.g. completion of updates) of the configuration management database
            c) Discrepancy identification (e.g. discovery and configuration management database
               disagreement)

SPEC.5.6.5.1.14 A view must be capable of accessing and displaying the contents of an associated
database.

SPEC.5.6.5.1.15 A view must be capable of providing pass through to external application.

SPEC.5.6.5.1.16 The view must allow a user to acknowledge REs.

SPEC.5.6.5.1.17 The view must allow a user to enter maintenance data (e.g., notes, trouble ticket
references, etc.)


SPEC.5.6.5.2       Network and Service Status and Control

SPEC.5.6.5.2.1 NMCS must provide control to manually re-route circuits onto other aggregates or paths
(see SPEC.4.4.1.4 - Multiplexer Provisioning Requirements)

SPEC.5.6.5.2.2 NMCS must provide status and control for all channel and aggregate-level diagnostic
controls as specified in Sections SPEC.4 - Requirements for Replaced ASTI Components , including, but
not limited to, loopbacks and BERTs.

SPEC.5.6.5.2.3 NMCS must provide status and control for manual switching of all channels within an
aggregate from a single control from A to B, or B to A.

SPEC.5.6.5.2.4     NMCS must provide status and control for the manual switch of a single channel from A
to B, or B to A.

SPEC.5.6.5.2.5     NMCS must provide status and control for the manual switch of a single switch from A to
B, or B to A.

SPEC.5.6.5.2.6 NMCS must provide status and control for the state of the link and its aggregates in terms
of traffic (“in use”, “not in use”), and quality (“Available”, “Degraded”, “Under Test”, “Unavailable”).

SPEC.5.6.5.2.7 NMCS must provide the capability to reset individual aggregate and channel-level (if
implemented) performance BERTs specified in Section 3.2.

SPEC.5.6.5.2.8     NMCS must allow a user to force traffic for a specific link onto a specified aggregate.

10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 85
ASTI                                                 Amendment 5                         DTFAWA-10-R-00039


SPEC.5.6.5.2.9        NMCS must allow a user to disable switching.

SPEC.5.6.5.2.10 NMCS must support the time constraints for channel level protection switching as
specified in Sections SPEC.3 - ASTI Service and System Requirements and SPEC Appendix E of this text.


SPEC.5.6.5.3          Performance Degradation

SPEC.5.6.5.3.1 The views must identify the status of the primary and alternate42 routes IAW the status
definitions in Section SPEC.3.1 - System, Equipment and Software Reliability by indicating the following:
                a) The aggregates and associated channels that are “available”, “degraded”, “under test”, and
                   “unavailable”.
                b) The aggregates and associated channels that are “in use” and “not in use”.
                c) Those aggregates and associated channels for which a viable alternate channel is not
                   currently “available”.


SPEC.5.6.5.4           Event Correlation

SPEC.5.6.5.4.1 The NMCS must be capable of accepting input from multiple NEs, correlating the
information received (also referred to as Root Cause Analysis), and identifying the event.

SPEC.5.6.5.4.2        Event correlation must take place within 5 seconds of the trigger event(s).

SPEC.5.6.5.4.3 The NMCS must be capable of concealing or exposing the correlated data details as
required by the user.


SPEC.5.6.5.5           Expert System

SPEC.5.6.5.5.1 The NMCS must be user configurable for taking action upon a RE, based on a set of user
configurable rules.

SPEC.5.6.5.5.2        Action must be taken within 5 seconds of the trigger event(s).


SPEC.5.6.6            Logging

SPEC.5.6.6.1          Time-of-Day (TOD)

SPEC.5.6.6.1.1        TOD data (i.e. date/time) must be tagged to logged items.

SPEC.5.6.6.1.2 Each NE must have a clock-calendar that is referenced to the network synchronization
source IAW Section SPEC.5.8.1.2 - Time-Of-Day (TOD).

SPEC.5.6.6.2     Logged Events – logged events include Reportable Events, Commands, Correlated
Events, and Expert System Events.

42
     When alternate routes, as defined by the user, exist.
10/07/10                                               SECTION J-1: ASTI TECHNICAL SPECIFICATION - 86
ASTI                                               Amendment 5                                   DTFAWA-10-R-00039




SPEC.5.6.6.2.1      Reportable Events

SPEC.5.6.6.3      The NMCS must record in the log aggregation subsystem the following for each
reportable event generated by the ASTI Network:

              a) NE by resource name
              b) A description of the event
              c) TOD of occurrence
              d) TOD of fault acknowledgement
              e) TOD of fault resolution43
              f) Any associated maintenance data (e.g., trouble ticket references, notes, etc.)


SPEC.5.6.6.3.1      Commands
The NMCS must record the following in the log aggregation subsystem:
              a) Command data (e.g., user, workstation, resource, parameters, etc.)
              b) Acknowledgement of receipt of the command by the collector local to the NE
              c) The results of the command - all corresponding data (e.g., statistics, parameters, etc.)


SPEC.5.6.6.3.2      Event Correlation
The NMCS must record the following in the log aggregation subsystem:
              a) Correlated Event
              b) Reportable events used in triggering the correlation


SPEC.5.6.6.3.3      Expert Systems
The NMCS must record the following in the log aggregation subsystem:
              a) Command data (e.g., user, workstation, resource, parameters, etc.)
              b) Reportable events used in triggering the rule
              c) Acknowledgement of receipt of the command by the collector local to the NE, if
                 applicable.
              d) The results of the command - all corresponding data (e.g., statistics, parameters, etc.)




43
 For purposes of this specification, fault resolution is defined as the clearing of a fault due to a change in state on the
NE, as interpreted by the NE’s agent within the NMCS.
10/07/10                                             SECTION J-1: ASTI TECHNICAL SPECIFICATION - 87
ASTI                                            Amendment 5                           DTFAWA-10-R-00039


SPEC.5.6.7        Reporting

SPEC.5.6.7.1      View Integrated Reporting

SPEC.5.6.7.1.1 The view must be capable of performing basic reporting and graphing functions based on
current selected NE, NE attribute, aggregate, etc.

SPEC.5.6.7.1.1.1 The view-integrated reporting must be capable of showing a list of REs for an associated
NE.

SPEC.5.6.7.1.1.2 A user must be able to select a RE from the list and graph its values over a period of user
configurable specified start and stop points in terms of dates and times (i.e. a date/time range). The amount
of time specified by the date/time range must be configurable up to a maximum TBP amount of time.

SPEC.5.6.7.1.2 The view-integrated reporting must be capable of being filtered and/or sorted by the
following attributes, at a minimum:
             a)   time period for the network
             b) NE
             c) NE sub component
             d) site
             e) aggregate
             f) link
             g) severity
             h) logged event type


SPEC.5.6.7.2      Reporting Functions

SPEC.5.6.7.2.1    The NMCS must support the following reporting functions:
             a) View current acknowledged and/or unacknowledged faults.
             b) Sort and/or filter logged event history by attributes (e.g., time period for the network, NE,
                NE sub component, site, aggregate, link, severity, logged event type, or regular expression.)
             c) Graph logged event values by user configurable time period.


SPEC.5.7          Configuration Management Requirements

NMCS Configuration Management must include a collection of processes, functions, and tools that promote
ASTI network consistency, track ASTI network changes, and provide up to date ASTI network
documentation and visibility. This includes, but is not limited to configuration file management, asset
management, software management, provisioning, backup and recovery, disaster recovery, and capacity
planning of the ASTI network.




10/07/10                                         SECTION J-1: ASTI TECHNICAL SPECIFICATION - 88
ASTI                                           Amendment 5                            DTFAWA-10-R-00039


SPEC.5.7.1          ASTI Architecture and Configuration

SPEC.5.7.1.1        ASTI Sites

     The NMCS must support the operation of the ASTI network that is initially deployed at 64 sites (4 hubs
     and 60 remote sites) (J-3 List of ASTI Facilities).


SPEC.5.7.1.2        Growth to Accommodate ASTI

     The NMCS must be designed and installed at initial delivery to accommodate a fifteen (15) percent
     growth in the number of sites serviced by the NMCS and a twenty (20) percent growth in the number of
     NEs located at each of the initial sites.


SPEC.5.7.1.3        Network Management and Control from the AFSS Hub

     ASTI is divided into three NMCS sub-networks each associated with an AFSS Hub. In addition to
     providing management from the ZAN ARTCC, the NMCS must enable a user located at any one of the
     Hubs to utilize the local NMCS workstation to provide network management and control services to the
     sub-network which is associated with the Hub and under various ASTI-communications failure
     conditions.

SPEC.5.7.1.3.1 The following list defines the NEs that comprise the sub-networks that must be controlled
from the associated hub:
               a) All NEs at the hub
               b) All NEs at the remote sites that are connected to the hub
               c) The NEs at the ZAN ARTCC that are connected to the hub
               d) The NEs at the ZAN ARTCC that are connected to the remote sites; where the remote sites
                  are those that are connected to the hub


SPEC.5.7.1.3.2 In addition to the sub-network, the AFSS hub must manage and control any remotes or
NEs at ZAN ARTCC that have no sub-network44.

SPEC.5.7.1.3.3 ZAN ARTCC communication failure conditions must not affect the management and
control of the sub-network NEs except where the communication failure directly prohibits communication
to that NE’s corresponding collector.

SPEC.5.7.1.3.4 Network views available from ZAN ARTCC must be available either locally or remotely
at the AFSS hubs.


SPEC.5.7.1.4        NMCS Remote Restart


44
  Remotes that have no sub-network may be controlled through communications from ZAN. If ZAN is unavailable,
the control of these remotes will not be required.
10/07/10                                        SECTION J-1: ASTI TECHNICAL SPECIFICATION - 89
ASTI                                                 Amendment 5                           DTFAWA-10-R-00039


SPEC.5.7.1.4.1 All NMCS NEs must have the capability to be remotely commanded by a user to
gracefully restart NMCS processes without additional human intervention.

SPEC.5.7.1.4.2 All NMCS NEs must have the capability to be remotely commanded by a user to
gracefully reboot.

SPEC.5.7.1.4.2.1 After reboot, the NMCS NEs must return to the normal operation without human
intervention.

SPEC.5.7.1.4.3 The remote site NMCS NEs must be configured such that it can be remotely restarted by a
user by cycling power to initiate a cold start.

SPEC.5.7.1.4.3.1 After cold start, the NMCS NEs must return to the normal operation without human
intervention.

SPEC.5.7.1.4.4        The remote cold start feature must be available after any single point of failure.

SPEC.5.7.1.4.5        All NMCS remote restart features must provide status feedback throughout the restart or
reboot process.


SPEC.5.7.1.5          NMCS Communication Circuits

SPEC.5.7.1.5.1        Unless authorized by the FAA, the NMCS data must be routed over ASTI circuits.

SPEC.5.7.1.5.2 The NMCS located at the ZAN ARTCC must have access to the Phase II site NEs if the
ASTI network is not operational to that site.

SPEC.5.7.1.5.3        Where used, dial back up channels to sites45 must have the following characteristics:
                a) user activated
                b) Dial On-Demand Routing (DDR)
                c) router callback
                d) authentication (see Section SPEC.5.10 - Security Management Requirements)
                e) use the existing multi-use commercial POTS lines installed for use with ASTI (see
                   Attachment J-2, Transition Requirements and Constraints for more information on existing
                   multi-use POTS lines)
                f) POTS line available for phone calls when not in user activated dial backup mode

SPEC.5.7.1.5.4        Unless authorized by the FAA, the use of dial backup must be limited to Phase II sites.

SPEC.5.7.1.5.5 The NMCS communication paths must be redundant such that any single failure of a
network element does not prohibit management and control of any NE.

SPEC.5.7.1.5.5.1 The NMCS must have mechanisms to control NMCS traffic such that during the failure of
a single path the NMCS still meets the time constraints described in Section SPEC.5 - Network


45
     Dial backup is only employed at all Phase II sites.
10/07/10                                              SECTION J-1: ASTI TECHNICAL SPECIFICATION - 90
ASTI                                               Amendment 5                                  DTFAWA-10-R-00039


Management and Control System (NMCS) RequirementsNetwork Management and Control System
(NMCS) Requirements.

SPEC.5.7.1.5.6 The total bandwidth of the NMCS circuits between any hub and ZAN ARTCC must not
exceed a total budget of 224 Kbps to accommodate all functionality.

SPEC.5.7.1.5.7 The total bandwidth of the NMCS circuits between a remote site and two hubs must not
exceed a total budget of 48 kbps46.

SPEC.5.7.1.5.8 All functions must be accommodated within the total bandwidth budget including, but not
limited to the following:
              a) Polling commands and responses,
              b) All fault management functions,
              c) Implementation of redundant functions,
              d) TOD synchronization,
              e) NMCS software upgrades,
              f) NMCS software maintenance,
              g) Security functions, and
              h) Other functionality as defined in this specification (e.g. performance management, if
                 applicable by design).


SPEC.5.7.2          Functionality

SPEC.5.7.2.1        ASTI System Baseline47

SPEC.5.7.2.1.1 System baseline must consist of, at a minimum the types, quantities, configuration,
revision level, and location of all ASTI hardware and software.

SPEC.5.7.2.1.2 The NMCS must provide updating, adding, removing, versioning, and branching for
configuration managed objects, such as a NE type agent configuration.


SPEC.5.7.2.2        Auto Discovery of IP enabled Devices

SPEC.5.7.2.2.1      The NMCS must have the functionality to auto discover hardware48 and software changes.

SPEC.5.7.2.2.1.1 The auto discovery process must gather configuration data and identify changes in
hardware or software, including the following at a minimum:
                                a) Additions or deletions of any device on the NMCS network, including NEs
                                b) Model numbers of NEs, including both NE chassis and cards

46
   For example, 24 kbps from remote to ARTCC and 24 kbps from remote to the AFSS hub.
47
   System baseline consists of the types, quantities, configuration, bar code number, revision level, and location of all
ASTI hardware (to the LRU) and software.
48
   Includes firmware.
10/07/10                                            SECTION J-1: ASTI TECHNICAL SPECIFICATION - 91
ASTI                                        Amendment 5                            DTFAWA-10-R-00039


                            c) Serial numbers of NEs
                            d) Software and firmware revision information
                            e) Configuration of NEs in terms of installed cards and options

SPEC.5.7.2.2.1.2 The NMCS must monitor for and identify new NEs and provide a user acknowledgement
for new NE.

SPEC.5.7.2.2.1.3 Auto discovery must dynamically update the fault management view with newly
discovered NEs and NE components.

SPEC.5.7.2.2.2 In addition to the auto discovery process being based on an RE (the default auto discovery
mode of operation), the auto discovery process must also be capable of being scheduled and initiated
manually.




SPEC.5.7.2.3     Hardware Asset Management

SPEC.5.7.2.3.1 The NMCS must have both manual and automated controls (i.e. manual input and auto
discovery) to maintain an ASTI hardware database for configuration management. The database must
contain an equipment inventory and history to the LRU level, and contain the following at a minimum:
            a) Serial Number
            b) Make and model
            c) Hardware ID
            d) Firmware version
            e) Revision levels
            f) Location (e.g., LID, rack, elevation, slot when applicable)
            g) Install history by location and hardware instance

SPEC.5.7.2.3.2 The NMCS must have the functionality to allow a user to manually input entries and
updates (e.g., legacy equipment or components, cards, options of NEs that do not support auto discovery
capability) to the ASTI hardware database from a GUI-based application on a NMCS workstation.


SPEC.5.7.2.4     Hardware Configuration Baseline and Operational Baseline

SPEC.5.7.2.4.1   The NMCS must maintain a database of hardware configuration baseline parameters.

SPEC.5.7.2.4.2 The NMCS must maintain a database of hardware operational parameters (e.g.,
frequency) based on location.


SPEC.5.7.2.5     Service Level Configuration Management

10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 92
ASTI                                               Amendment 5                             DTFAWA-10-R-00039


SPEC.5.7.2.5.1        The NMCS must maintain a historical database of ASTI services to include the following,
at a minimum:
                a) Corresponding ASTI circuits
                b) Channel Protection
                c) Channels
                d) Aggregates
                e) Network mapping and channel assignment
                f) Mapping of ASTI circuit to customer services
                g) Circuit information (e.g., tail circuits)
                h) Corresponding cable numbers
                i)   Parameters associated with the Multiplexer NE(s) (e.g., circuit type, data rate)
                j)   All associated NE with specific hardware and software assignments

SPEC.5.7.2.5.2 The NMCS must have the capability to export the service level database to an offline
information system for pre-provisioning, planning and engineering purposes.


SPEC.5.7.2.6          Software Packaging

SPEC.5.7.2.6.1 The NMCS must utilize and document software packaging for both object code and
element interfaces (e.g., agents).

SPEC.5.7.2.6.2        The NMCS must provide the ability to update existing or produce new agent versions.

SPEC.5.7.2.6.3 All ASTI network and NMCS software, firmware, and vendor documentation must
include the following at a minimum:
                a) Versions
                b) Packages
                c) Be verifiable using a package integrity check based on version, package contents,
                   checksum, file system permissions, and ownership (user and group)
                d) Be accessible on the NMCS network
                e) Be manually and automatically downloadable from a centralized repository


SPEC.5.7.2.7          Software Maintenance

SPEC.5.7.2.7.1 After staging49, software maintenance, patches, and upgrades must be capable of being
operational within 2-1/2 minutes of the time that the maintenance initiated or upgrade started. This
requirement applies to all components with the exception of Fault Management Servers which must be
operational within 30 seconds as specified in SPEC.5.6.1.2.3.


49
     Staging, for the purpose of this requirement, includes downloading to the NE.
10/07/10                                             SECTION J-1: ASTI TECHNICAL SPECIFICATION - 93
ASTI                                           Amendment 5                              DTFAWA-10-R-00039


SPEC.5.7.2.8      Provisioning

SPEC.5.7.2.8.1 The NMCS must enable the user to provision the ASTI Network services, including
activation, modification, deactivation, relocation of the channels, services, and transport paths (i.e.
aggregates), e.g., initial circuit establishment, and circuit termination.

SPEC.5.7.2.8.2    The NMCS must track ASTI network configuration changes which are made to the ASTI
network.


SPEC.5.7.2.8.3    Circuit-Level Provisioning

SPEC.5.7.2.8.3.1 Circuit provisioning must only affect the circuit being provisioned and be transparent to
all other ASTI circuits.

SPEC.5.7.2.8.3.2 NMCS must provide status and control of clocking schemes consistent with FAA’s
existing circuits and Sections SPEC.3 - ASTI Service and System Requirements and SPEC.4 -
Requirements for Replaced ASTI Components.

SPEC.5.7.2.8.3.3 NMCS must provide controls for selecting digital circuit data rates.

SPEC.5.7.2.8.3.4 NMCS must provide controls for selecting clocking options (internal-internal, external-
external, internal-external, and external-internal).

SPEC.5.7.2.8.3.5 NMCS must provide controls for viewing available channel level resources (e.g. slots
within a node, available ADP slots, etc.).

SPEC.5.7.2.8.3.6 The NMCS must provide controls for provisioning of channel-level circuits that utilize
redundant transport paths to designate either the Primary satellite path or the Alternate satellite path as the
preferred path.

SPEC.5.7.2.8.3.7 The NMCS must provide controls for channel-level circuits provisioned such that only a
single transport path is assignable to either the Primary or the Alternate satellite path.

SPEC.5.7.2.8.3.8 NMCS must provide controls to manually re-route circuits on alternate aggregates or
paths.

SPEC.5.7.2.8.3.9 NMCS must provide controls and status for all channel-level diagnostic controls as
specified in Section SPEC 4 - Error! Reference source not found.Requirements for Replaced ASTI
Components, including, but not limited to, loopbacks and BERTs.


SPEC.5.7.2.8.4    Aggregate-Level Provisioning

SPEC.5.7.2.8.4.1 Aggregate provisioning must only affect the aggregate being provisioned and be
transparent to all other ASTI aggregates.

SPEC.5.7.2.8.4.2 NMCS must provide status and control of timing scheme consistent with contractor’s
timing architecture and Section Error! Reference source not found.SPEC.3 - Error! Reference source
not found.ASTI Service and System Requirements.

10/07/10                                        SECTION J-1: ASTI TECHNICAL SPECIFICATION - 94
ASTI                                       Amendment 5                            DTFAWA-10-R-00039


SPEC.5.7.2.8.4.3 NMCS must provide control for selecting individual channel priority within an aggregate.

SPEC.5.7.2.8.4.4 NMCS must provide controls and status for all aggregate-level diagnostic controls as
specified in Section Error! Reference source not found.SPEC.4 - Error! Reference source not
found.Requirements for Replaced ASTI Components, including, but not limited to, loopbacks and BERTs.

SPEC.5.7.2.8.5 NMCS must support circuit and aggregate names consistent with current naming
conventions IAW Appendix G – ASTI Labeling Formats.

SPEC.5.7.2.8.6 NMCS must provide controls for viewing available bandwidth at both the per-aggregate
and per-node levels.

SPEC.5.7.2.8.7 NMCS must support all equipment options supported by the multiplexer NE as described
in Section Error! Reference source not found.SPEC.4.4 - Error! Reference source not
found.Multiplexer Component.


SPEC.5.7.2.9     NMCS Operating Systems Management

SPEC.5.7.2.9.1 The NMCS must be user configurable to track operating systems changes, including
configuration changes, which are made to the underlying NMCS operating systems.

SPEC.5.7.2.9.2 The NMCS must be user configurable to automate updates to operating systems from a
centralized server at ZAN ARTCC.

SPEC.5.7.2.9.3 The NMCS must be user configurable to monitor operating systems software to the file
level for the presence of operating system changes, including operating systems configuration changes.


SPEC.5.7.2.10     Application and Application Configuration Management

SPEC.5.7.2.10.1 The NMCS must be user configurable to track ASTI application configuration changes,
which are made to the file level.

SPEC.5.7.2.10.2 The NMCS must validate authenticity of applications and configurations.

SPEC.5.7.2.10.3 The NMCS must be user configurable to monitor and prevent unapproved applications
and application configuration changes to the file level.


SPEC.5.7.2.11     IP Address Management

SPEC.5.7.2.11.1 The NMCS must have the capability to manage the IP address space, including, at a
minimum the following for every IP addressable NE on the NMCS network:
           a) Host name (including DNS name, if DNS is employed)
           b) Site
           c) IP address
           d) MAC address

10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 95
ASTI                                           Amendment 5                               DTFAWA-10-R-00039


             e) Switch (including port number)
             f) VLAN
             g) Application - a short textual description ( i.e. router, switch, collector, UPS, etc.)


SPEC.5.7.3         Logging

The NMCS must log all configuration changes to the ASTI Network as described in Section SPEC.5.7.2 -
Functionality.


SPEC.5.7.4         Reporting

SPEC.5.7.4.1       ASTI System Baseline Configuration Report - The NMCS must be capable of providing
report(s) detailing pertinent information for hardware and software configurations, e.g., the identification of
the basic software, and the software configurations for each NE in the ASTI Network and NMCS.

SPEC.5.7.4.2      Change Management Report - The NMCS must be capable of providing report(s)
detailing changes to the ASTI network and show a correlation of changes to change-approvals.

SPEC.5.7.4.3      Asset Inventory Report(s) - The NMCS must be capable of providing report(s) by Site,
Link, Aggregate, or Circuit – detailing all associated hardware and software by location(s) (see Appendix
G) and/or functional area.

SPEC.5.7.4.3.1     The report must have an option to include unused equipment physical space.

SPEC.5.7.4.4       Circuits Report – The NMCS must be capable of providing report(s) by aggregate or link
on circuits and associated customer services.

SPEC.5.7.4.5      Channel and Aggregate Configuration Reports - The NMCS must be able to produce
channel-level circuit and aggregate circuit configuration reports.

SPEC.5.7.4.5.1 The report must have an option to include available bandwidth and other multiplexer
bandwidth constraints.

SPEC.5.7.4.6      Aggregate Detail Report – The NMCS must be able to produce a report providing details
of an aggregate(s), e.g. frequencies, bandwidth, available bandwidth, etc.

SPEC.5.7.4.7      Operational Configuration and Performance Detail Report – The NMCS must be able to
produce a report providing details of operational configuration and performance (e.g. transmit levels by site,
frequency, carrier size.)

SPEC.5.7.4.8      HW History by Hardware ID Report(s) – The NMCS must be able to produce report(s)
providing details of the history of component(s) throughout its lifecycle.

SPEC.5.7.4.9       HW Change History Report – The NMCS must be able to produce a report providing
details of component replacement, by location or component type, of components either in a specific
location or across network.


10/07/10                                        SECTION J-1: ASTI TECHNICAL SPECIFICATION - 96
ASTI                                         Amendment 5                              DTFAWA-10-R-00039


SPEC.5.7.4.10     SW Change History Report - The NMCS must be able to produce a report providing
details of SW changes and approvals.

SPEC.5.7.4.11     Network Element Configuration Change Report – The NMCS must be able to produce a
report providing details of NE configuration changes, to include date, time, and operator.



SPEC.5.7.5        Data Replication, Backup, and Recovery

SPEC.5.7.5.1      General

SPEC.5.7.5.1.1    All fault management data (historical) must be stored in a centralized server(s) at ZAN
ARTCC.

SPEC.5.7.5.1.2    Configuration data (baseline and operational) must be stored in a centralized server(s) at
ZAN ARTCC.

SPEC.5.7.5.1.3    All log (audit) data must be stored in a centralized server at ZAN ARTCC.

SPEC.5.7.5.1.4    Schedule for centralized backup at ZAN ARTCC must be user configurable and set to the
following:
             a) Management data: daily on-site, monthly off-site
             b) Configuration data: daily on-site, monthly off-site
             c) Log data: weekly on-site, monthly off-site
             d) System data: monthly on-site and off-site

SPEC.5.7.5.1.5 System level backups must include all required data for system recovery, including, if
applicable, system state.

SPEC.5.7.5.1.6    Appliances must be treated as servers for this backup strategy.

SPEC.5.7.5.1.7    Media and technologies used for off-site storage must have a minimum of a 7 year
lifespan.

SPEC.5.7.5.1.8 From the time the media is inserted and the command is given, system level backups must
be capable of being completed within 8 hours.


SPEC.5.7.5.2      Remote Servers

SPEC.5.7.5.2.1 Remote servers must not store management and log data for more than 2.5 minutes
without forwarding data to the centralized server at ZAN ARTCC, except when the remote site has no
communications paths available.

SPEC.5.7.5.2.2    All remote server configurations must be controlled and user configurable from ZAN
ARTCC.

SPEC.5.7.5.2.3    Remote servers must have the capability to be locally imaged for disaster recovery.

10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 97
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


SPEC.5.7.5.2.3.1 Backup/imaging hardware is not required as a permanent part of a remote server, but the
capability to attach hardware, (e.g. LAN, USB, and SCSI) must be available.


SPEC.5.7.5.3     AFSS Hub Servers

SPEC.5.7.5.3.1 AFSS Hubs must not store management and log data for more than 2.5 minutes without
forwarding data to centralized server at ZAN ARTCC, except when the AFSS hub site has no
communications paths available.

SPEC.5.7.5.3.2   All AFSS hub server configurations must be controlled and user configurable from ZAN
ARTCC.

SPEC.5.7.5.3.3   Hub servers must have the capability to be imaged locally for disaster recovery.

SPEC.5.7.5.3.3.1 Backup/imaging hardware must be a component of the NMCS AFSS hub server.

SPEC.5.7.5.3.4   AFSS hub servers must be capable of performing system backups for off-site storage.



SPEC.5.7.5.4     ZAN ARTCC Servers

SPEC.5.7.5.4.1   ZAN ARTCC servers must store all ASTI management data on-line for a minimum of 1
year.

SPEC.5.7.5.4.2   ZAN ARTCC servers must store all ASTI configuration data on-line for a minimum of 1
year.

SPEC.5.7.5.4.3   ZAN ARTCC servers must store all ASTI log data on-line for a minimum of 1 year.

SPEC.5.7.5.4.4   ZAN ARTCC servers must have the capability to be imaged for disaster recovery.

SPEC.5.7.5.4.5   Backup/imaging hardware must be a component of the NMCS at ZAN ARTCC.

SPEC.5.7.5.4.6   System backups for off-site storage must be capable of being performed at ZAN ARTCC.

SPEC.5.7.5.4.7   Data backups for off-site storage must be capable of being performed at ZAN ARTCC.

SPEC.5.7.5.4.8 NMCS must have the capability to read backups of management and log data to
repopulate the data into the database for disaster recovery purposes.

SPEC.5.7.5.4.9 NMCS must have the capability to read backups of management and log data into the
database for analysis and reporting purposes.

SPEC.5.7.5.4.10 A user must have the capability to recreate all NMCS systems from system level backups.

SPEC.5.7.5.4.10.1      Any NMCS component must be capable of being recovered at ZAN ARTCC.

SPEC.5.7.5.4.10.2        Given the proper hardware, any NMCS component must be capable of being
recovered at any location, which may be off-site and off-line from any ASTI location.
10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 98
ASTI                                        Amendment 5                             DTFAWA-10-R-00039




SPEC.5.7.5.5     Alternate Site Centralized On-Line Storage

SPEC.5.7.5.5.1 The NMCS must backup all fault management, configuration, and log data from the
primary storage facility ZAN ARTCC to an alternate geographical AFSS hub site to be specified by the
Government after contract award.

SPEC.5.7.5.5.2   Acceptable backup strategies must consist of either synchronization or replication.

SPEC.5.7.5.5.3 The backup must be user configurable and be set to occur once per hour for fault
management, operational configuration, and log data.

SPEC.5.7.5.5.4 The backup must be user configurable and set to occur once per week for system baseline
configuration data.

SPEC.5.7.5.5.5   The backup schedules must have an option for manual synchronization.



SPEC.5.8         Administrative Management Requirements

The NMCS Administrative Management function must allow a user to administer the ASTI network. This
includes activities such as, but not limited to, account administration, time synchronization, user
permissions, accounting (logging) aggregation and storage, and compliance reporting.


SPEC.5.8.1       Functionality

SPEC.5.8.1.1      Operations Engineering Pre-Provisioning

SPEC.5.8.1.1.1 The NMCS must contain an off-line (not directly connected to the ASTI network) ASTI
engineering database for pre-provisioning planning activities, e.g. available circuit –level components,
available bandwidth (multiplexer and space segment).

SPEC.5.8.1.1.1.1 The ASTI engineering database must have the capability to synchronize with the on-line
ASTI network and associated databases.

SPEC.5.8.1.1.2 The ASTI engineering database must have the capability to pre-provision individual
operational parameters across the ASTI network, e.g. modem transmit and receive frequencies.

SPEC.5.8.1.1.3 The NMCS must have the capability to automate the implementation of pre-provisioned
operational parameters from the ASTI engineering database onto the ASTI network.

SPEC.5.8.1.1.3.1 The NMCS must allow for the automated changes to be individually user approved, on a
per-site, per-parameter basis.

SPEC.5.8.1.1.4 The ASTI engineering database must have the capability to allow for multiple
simultaneous users with record-level locking, error checking, change control management, and logging.


10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 99
ASTI                                             Amendment 5                                  DTFAWA-10-R-00039


SPEC.5.8.1.2       Time-Of-Day (TOD)

SPEC.5.8.1.2.1     The NMCS must provide TOD synchronization to all ASTI NEs.

SPEC.5.8.1.2.1.1 TOD synchronization of NMCS NEs must function according to the Network Time
Protocol (NTP) time-of-day standards to synchronize the clocks of computers over a network. 50

SPEC.5.8.1.2.1.2 TOD synchronization of Telco NEs must function according to either the NTP or Simple
Network Time Protocol (SNTP)51 standards to synchronize the clocks of devices over a network.

SPEC.5.8.1.2.2     For every site, one of the local NMCS NEs must act as the local NTP/SNTP server.

SPEC.5.8.1.2.3     The local NTP server must synchronize with a master NTP server.

SPEC.5.8.1.2.4 The local NTP server must synchronize all local NEs, regardless of NMCS
communications with the master NTP server.

SPEC.5.8.1.2.5     The master NTP server must be located at ZAN ARTCC.

SPEC.5.8.1.2.6     All NMCS TOD formats must be configurable and set to GMT in 24 hr. format.

SPEC.5.8.1.2.7     All NE TOD clocks must be accurate within +/- 0.5 second of the master NTP server.

SPEC.5.8.1.2.8     NE TOD adjustments due to NTP synchronization must be reported as REs.


SPEC.5.8.1.3       Authentication52 and Authorization53

SPEC.5.8.1.3.1 The NMCS must authenticate users via a login process (see Section SPEC.5.10 - Security
Management Requirements).

SPEC.5.8.1.3.2 The NMCS must limit the access of users to management and control functions utilizing
and validating roles, responsibilities, and privileges that are assigned to them. Users will be classified as one
of the following user groups at a minimum,:
             a) Operations Administrator
             b) Security Administrator
             c) Operator
             d) Hub Technician
             e) Technician
             f) Engineer

SPEC.5.8.1.3.3     All users must have unique accounts (i.e. users are uniquely identified).
50
   The current industry daemon uses the Network Time Protocol (NTP) version 4, which retains compatibility with
version 3, as defined by RFC-1305, and version 1 and 2, as defined by RFC-1059 and RFC-1119, respectively.
51
   SNTP, a subset of NTP, is defined in RFC 4330.
52
   Authentication refers to the process of ensuring that the claimed identity of a device or user is valid.
53
   Authorization refers to the act of allowing or disallowing access to certain functions and/or features of the NMCS
based on the user, system, or program.
10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 100
ASTI                                             Amendment 5                                 DTFAWA-10-R-00039


SPEC.5.8.1.3.4 Authentication services must be redundant such that any single ASTI Network failure
does not result in loss of authentication services.

SPEC.5.8.1.3.4.1 When all site communications are down, the NMCS must enable a user to authenticate
uniquely to the remote collector meeting Section SPEC.5.10 - Security Management Requirements (NIST
SP 800-53 and ATO document) using non-static passwords.

SPEC.5.8.1.4      The NMCS must provide a single point of administration for user accounts and user
authorizations network-wide:

SPEC.5.8.1.4.1.1 Single point of administration must be a single user interface accessible from any NMCS
workstation used to manage user accounts, groups, and authorizations without repetition and which are then
implemented network wide.

SPEC.5.8.1.4.1.2 The NMCS must have functions to create, modify, suspend, and delete user accounts,
including temporary accounts.

SPEC.5.8.1.4.1.3 The NMCS must be configurable to create, modify, and delete user groups which are
tailored by, but not limited to the following:
             a) work function,
             b) region,
             c) location or
             d) any combination of the above

SPEC.5.8.1.4.1.4 The NMCS must have functions to unlock suspended user accounts.

SPEC.5.8.1.4.1.5 The NMCS must have functions to create, modify, and delete user authorizations.


SPEC.5.8.1.5       Authorization Control Settings

SPEC.5.8.1.5.1 For each user and user group, authorizations must be configurable for a minimum of each
function defined in Section SPEC.5 - Network Management and Control System (NMCS)
RequirementsNetwork Management and Control System (NMCS) Requirements.

SPEC.5.8.1.5.2 The NMCS must have the capability to independently configure the authorizations for
functional categories (which may contain one or more functions) as listed in Table 5.8.1-1.

                                Sample54 NMCS User Group Authorizations
Management Functional            Independently Configurable Functional                           User Group




54
  Sample default values for each user group authorization are listed in the table. Assignment of actual group
permissions will be finalized after contract award.
10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 101
 ASTI                                    Amendment 5                                     DTFAWA-10-R-00039


            Areas                          Category




                                                                                                               Hub Technician
                                                                         Administrator




                                                                                                                                             Administrator
                                                                         Operations




                                                                                                                                Technician
                                                                                                    Operator
                                                                                         Engineer




                                                                                                                                             Security
                           View ASTI Network or Subnetwork                  X            X          X          X                X               X
                           Locally Manage Remote NEs                        X            X          X          X                X
                           Perform Diagnostics on NEs                       X            X          X          X                X
   Fault Management        Acknowledge REs                                  X                       X          X
                           Modify Event Correlation                         X            X
                           Modify Expert System Rules                       X            X
                           Prepare Standard Reports                         X            X          X          X                                X
                           Prepare Custom Reports                           X            X                                                      X
                           Configure ASTI Network or Subnetwork
                                                                            X            X          X          X
                           NEs
                           Locally Configure Remote NEs                     X            X          X          X                X
                           Modify Polling Rate, Thresholds, Severities      X            X
                           Modify Agents                                                 X
                           Add/Delete NEs                                   X            X
                           Deploying Agent Updates                          X            X
                           Provision Circuits and/or Aggregates             X            X          X
                           Run ASTI NE Auto-Discovery                       X            X
Configuration Management   Access MIB Browser                                            X
                           View NE Configuration                            X            X          X          X                X               X
                           View NMCS NE Configuration                       X            X                                                      X
                           Modify NMCS NE Configuration                     X            X                                                      X
                           Approve NMCS NE Configuration
                                                                            X
                           Modification
                           Update ASTI System Baseline                      X            X                                                      X
                           Backup NMCS NE systems and data                  X            X
                           Prepare Standard Reports                         X            X          X          X                                X
                           Prepare Custom Reports                           X            X                                                      X

                           Access and Authorization Management                                                                                  X
                           Configure Accounting (Log Management)                                                                                X
     Administration        View Log Aggregate                               X            X          X                                           X
      Management           Query Log Aggregate                              X            X                                                      X
                           Prepare Compliance Reports                                                                                           X
                           Prepare Standard Reports                         X            X          X                                           X
                           Prepare Custom Reports                           X            X                                                      X



 10/07/10                                 SECTION J-1: ASTI TECHNICAL SPECIFICATION - 102
ASTI                                          Amendment 5                                      DTFAWA-10-R-00039


                              Sample54 NMCS User Group Authorizations
                                                                                                          User Group




                                                                                                                       Hub Technician
                                                                               Administrator




                                                                                                                                                     Administrator
Management Functional          Independently Configurable Functional




                                                                               Operations




                                                                                                                                        Technician
       Areas                                 Category




                                                                                                            Operator
                                                                                               Engineer




                                                                                                                                                     Security
                              Prepare Standard Reports                              X          X            X          X                                X
                              Prepare Custom Reports                                X          X                                                        X
Performance Management
                              Prepare Security Performance Management
                                                                                                                                                        X
                              Reports (All)
                              View Top-Level Sec Alarms                             X          X            X                                           X
                              View Detail-level Sec Alarms                          X          X                                                        X
                              Modify Sec Event Correlation                                                                                              X
                              Enable/Disable NE Functions                           X                                                                   X
                              Configure Sec Alarms                                                                                                      X
                              Configure IDS/IPS                                                                                                         X
 Security Management
                              Update Virus Signature                                X                                                                   X
                              Audit Network                                         X                                                                   X
                              Audit NMCS NEs                                        X          X                                                        X
                              Audit NEs                                             X          X                                                        X
                              Prepare Standard Reports                              X          X                                                        X
                              Prepare Custom Reports                                X                                                                   X
                                    1Table 5.8.1-1 Access Control Settings

SPEC.5.8.2        Logging

SPEC.5.8.2.1      Security-related reportable events must be considered separate REs, labeled Security
Events (SEs).

SPEC.5.8.2.2      Syslog must be enabled and configurable on all ASTI NMCS NEs.

SPEC.5.8.2.3      All NMCS NEs must syslog SEs.

SPEC.5.8.2.4   Syslog events must utilize TOD date/time stamps as specified in Section SPEC.5.8.1.2 -
Time-Of-Day (TOD)Time-Of-Day (TOD).                                                                                                                                  Formatted: Font: Not Bold

SPEC.5.8.2.5      At a minimum, the following accounting-related events must be sysloged:

             a) Account administration, including additions, deletions, modifications, locks, unlocks,
                password resets, and automatic temporary account deletions.
             b) Account activity, including login, logout, change user (e.g. su).


SPEC.5.8.2.6      Log Aggregation Subsystem
10/07/10                                  SECTION J-1: ASTI TECHNICAL SPECIFICATION - 103
ASTI                                          Amendment 5                             DTFAWA-10-R-00039


SPEC.5.8.2.6.1 The NMCS must contain a log aggregation subsystem, which includes log aggregation
services such that any single log aggregation failure or ASTI Network failure does not result in the loss of
log aggregation.

SPEC.5.8.2.6.2    Log aggregation subsystem must be capable of retaining data on-line for a minimum of
one year.

SPEC.5.8.2.6.3    Log aggregation subsystem must log all REs and SEs in a centralized repository.

SPEC.5.8.2.6.4 NMCS NEs must be user configurable to allow configuration of syslog events, including
format, content, etc.

SPEC.5.8.2.6.5 The NMCS must securely and reliably transmit all selected syslog records to the log
aggregation subsystem.

SPEC.5.8.2.6.6 When transmitting syslog records to the log aggregation subsystem, the NMCS must use
no more than one intermediate syslogging server (i.e., a server acting as both a receiver and sender).

SPEC.5.8.2.6.7    The NMCS log aggregation subsystem must track report generation.

SPEC.5.8.2.6.8    The log aggregation subsystem must be capable of being monitored via SNMP.

SPEC.5.8.2.6.9    The log aggregation subsystem must be capable of forwarding reportable events via
SNMP.

SPEC.5.8.2.6.10 The log aggregation subsystem must be capable of suppressing individual log message
types for both specific NMCS NEs and for all NMCS NEs.

SPEC.5.8.2.6.11 The log aggregation subsystem must be capable of, and user configurable to, forward
selected log messages to third party applications for additional analysis.

SPEC.5.8.2.6.11.1          The log forwarding or routing capability must be based on any user configurable
attribute (e.g. severity, origin of the syslog message, and any regular expression).

SPEC.5.8.2.6.12 The log aggregation subsystem must provide the capability to browse logs in their
original (raw) format.

SPEC.5.8.2.6.13 The log aggregation subsystem must provide ad-hoc query capability for searching
through all logs based on any user configurable attribute (e.g. severity, origin of the syslog message, and
any regular expression).

SPEC.5.8.2.6.13.1        The results of any query must be delivered within 90 seconds.

SPEC.5.8.2.6.13.2      The NMCS must provide flexible searching modes, including regular expression
and Boolean expression, to enable users to quickly obtain results, including the creation of custom search
filters and alerts.


SPEC.5.8.2.7      Transmission Failures

SPEC.5.8.2.7.1    The NEs must ensure that no log data is lost during communication failures.
10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 104
ASTI                                         Amendment 5                                DTFAWA-10-R-00039


SPEC.5.8.2.7.1.1 After communications restoration, missing log data must be transmitted to the log
aggregation subsystem.

SPEC.5.8.2.7.2 The NE remote storage capacity must be sized such that in the event of a NMCS
communications failure with the log aggregation subsystem the NE can store syslog data for one week.

SPEC.5.8.2.7.3    The NMCS must alarm when a “drop message” event occurs.

SPEC.5.8.2.8       The log aggregation subsystem must record all activity regarding any dial backup
activity.



SPEC.5.8.3        Reporting

SPEC.5.8.3.1      The NMCS must include a suite of pre-formatted, user customizable standard reports that
provide the following at a minimum:

             a) Users and their account permissions
             b) Accounts that were created, modified, or deleted
             c) Logins that succeeded and those that failed
             d) Specified files accessed on servers
             e) Escalated privileged activities
             f) Administrative logins
             g) Permission modified

SPEC.5.8.3.2      The NMCS must contain user configurable reports to document FISMA/NIST compliance
based on the log aggregation subsystem, including, but not limited to those in the Table 5.8.3-1:

FISMA Requirement                                     Standard Reports and Alerts

AC2—Account Management                                •    Accounts Created/Deleted
                                                      •    Logins Succeeded, Failed logins

AC-3—Access Enforcement                               •    Firewall Policy Changes
                                                      •    Logins Succeeded, Failed logins

AC-6—Least Privilege                                  •    Files Accessed on Servers
                                                      •    Escalated Privileged Activities

AC-7—Unsuccessful Login Attempts                      •    Logins Succeeded, Failed logins
IA-2—User Identification                              •    Administrative Logins

AC-13—Supervision and Review/Access Control           •    Accounts Created/Deleted on Servers
                                                      •    Permission modified


10/07/10                                          SECTION J-1: ASTI TECHNICAL SPECIFICATION - 105
ASTI                                            Amendment 5                              DTFAWA-10-R-00039


AC17—Remote Access                                     •     VPN User Accessing Network

AU-2/3—Auditable Events/Content of Audit Records       •     Log Sources Status
                                                       •     Audit Logs Cleared

AU-5/6/7—Audit Monitoring and Reporting                •     Periodic Review of Log Reports

CM-3/4—Configuration Change Control/Monitoring         •     Firewall Policy Changes
Configuration Changes
                                                       •     Policy Modified

SC-7—Boundary Protection                               •     Firewall Traffic Considered Risky

                                             Table 5.8.3-1 User Configurable Reports


SPEC.5.9              Performance Management Requirements

The NMCS Performance Management functions must monitor and measure performance requirements such
that overall performance can be maintained at an acceptable level.


SPEC.5.9.1            Functionality

SPEC.5.9.1.1    The NMCS must be user configurable to monitor, log, evaluate and report on the
following ASTI Network and NE attributes to include, but not limited to:

             a) Telecommunications Circuits, Channels, and Aggregates (ADP-ADP)
                 i.     Raw Availability (unadjusted for allowed outages, etc.)
                 ii. Number, duration, frequency, and time of outages
             b) NMCS communications (router-router) circuit-level uptime, statistics, and latency
             c) Individual NEs:
                 i.     NE MIB specific
                 ii. NMCS interface errors
                 iii. Uptime
                 iv. Number and frequency of “no response” and “invalid response”
                 v. NMCS command errors
                 vi. Ping performance
                 vii. Life cycle performance

SPEC.5.9.1.2          The NMCS must track the security management performance of the NMCS.

SPEC.5.9.1.2.1        The NMCS must log report generation.



10/07/10                                         SECTION J-1: ASTI TECHNICAL SPECIFICATION - 106
ASTI                                            Amendment 5                                DTFAWA-10-R-00039


SPEC.5.9.1.2.2     The NMCS must be capable of producing a report on report generation by user, report
title, and date.


SPEC.5.9.1.3       NMCS Availability

SPEC.5.9.1.3.1 The NMCS must accurately provide all fault, log aggregation, and security management
related features and functionality as described in Section SPEC.5 - Network Management and Control
System (NMCS) RequirementsNetwork Management and Control System (NMCS) Requirements with an
availability of .9999 over the latest 12 month sliding window55. 56

SPEC.5.9.1.3.2 The NMCS must accurately provide all other configuration, administration, and
performance management related features and functionality as described in Section SPEC.5 - Network
Management and Control System (NMCS) RequirementsNetwork Management and Control System
(NMCS) Requirements, with an availability of .999 over the latest 12 month sliding window57.58

SPEC.5.9.1.3.3 The failure of a hot swappable NMCS NE is not counted against the availability of the
NMCS, assuming the standby component is fully functional and meets the requirements specified in Section
SPEC.5.5.12 - NMCS Component RedundancyNMCS Component Redundancy.

SPEC.5.9.1.3.4 Scheduled and Unscheduled Outages – The availability requirement for the operation of
the NMCS and its components on a 12 month sliding window, must be achieved under the condition that
both Scheduled Maintenance, including preventive maintenance, are not considered as outage time.
Corrective maintenance is considered outage time.

SPEC.5.9.1.3.4.1 For modeling purposes, the travel allowances must be as follows: 24 hours for remote
sites, 2 hours for hubs, and 0 hours for ZAN ARTCC.

SPEC.5.9.1.3.5 Workstation Availability - The workstations must enable operations personnel to manage
the ASTI network.

SPEC.5.9.1.3.5.1 Each workstation must accurately perform its function 99.8 percent of the time over a 12
month sliding window, i.e. the maximum allowed yearly downtime is less than 17.5 hours.


SPEC.5.9.2         Logging

SPEC.5.9.2.1   Logged items must utilize TOD date/time stamps as specified in Section SPEC.5.8.1.2 -
Time-Of-Day (TOD)Time-Of-Day (TOD).                                                                            Formatted: Font: Not Bold


SPEC.5.9.2.2       The NMCS must log the user name and TOD for each report generated.

SPEC.5.9.2.3      The NMCS must have the capacity to safely store all performance data and logs for a
period of 1 year on-line.



55
   This is a NMCS system-level requirement, not a specific hardware or software requirement.
56
   The maximum 12 month downtime must not exceed 52.56 minutes.
57
   This is a NMCS system-level requirement, not a specific hardware or software requirement.
58
   The maximum 12 month downtime must not exceed 8.76 hours.
10/07/10                                         SECTION J-1: ASTI TECHNICAL SPECIFICATION - 107
ASTI                                            Amendment 5                           DTFAWA-10-R-00039


SPEC.5.9.3             Reporting

SPEC.5.9.3.1      The NMCS must provide response time and raw availability statistics as delineated in
Section SPEC.5.9.1.3 - NMCS AvailabilityNMCS Availability, above, which includes any models for              Formatted: Font: Not Bold
calculating the raw availability.

SPEC.5.9.3.1.1 Raw availability statistics provided must include, but not be limited to total hours
available, average hours available within a specific time period, mean-time-between-failure (MTBF) for the
system and for individual NEs, and mean-time-to-repair (MTTR).

SPEC.5.9.3.2    The NMCS must utilize preset standard reports, which will address Network
Performance, Aggregate Performance and NE Performance as listed in Section SPEC.5.9.1.1.

SPEC.5.9.3.3      Trend Analysis Report(s) – The NMCS must be capable of producing a report(s)
providing details of the following at a minimum:

             a) Poorly performing aggregates, including duplex, by the following:
                  i.     Errored Seconds (ES)
                  ii. Severely Errored Seconds (SES)
                  iii. Consecutive Severely Errored Seconds (CSES)
                  iv. Loss of Signal (LOS)
                  v. Sync failure
             b) Diverse path failure (i.e. both aggregate paths are down)

SPEC.5.9.3.4           ES Waterfall Graph – The NMCS must be capable of producing a visual 3D model of the
following:

             a)    ES by aggregate over time, with options for half or full duplex
             b)    Sortable by aggregate, frequency, and satellite
             c)    Search capability to find frequency and aggregate name
             d)    Drill-down on a data point within the graph to reveal the underlying ES data

SPEC.5.9.3.5    Modem Receive Performance Report – The NMCS must be capable of producing a report
detailing modem performance by modem, with the following minimum details provided:

             a) Receive Frequency
             b) Carrier detect
             c) Raw & Corrected BER
             d) Signal receive level (RXL)
             e) Eb/No
             f) Paired-Carrier Performance (e.g. power ratio)
             g) Loss of Signal (LOS)
             h) Buffer fill level

10/07/10                                         SECTION J-1: ASTI TECHNICAL SPECIFICATION - 108
ASTI                                        Amendment 5                           DTFAWA-10-R-00039


SPEC.5.9.3.6       Multiplexer Performance Report– The NMCS must be capable of producing a report
detailing the following test diagnostics reports:

                  a)    Aggregate BERT
                  b)    Digital Channel BERT

SPEC.5.9.3.7      Switch History Report – The NMCS must be capable of producing a report detailing the
switching activity by diverse path as follows:

            a) Correlation of link performance and switching between primary and alternate paths
            b) Correlation of cause for automatic switching
            c) Identifies manual switching and identifies user


SPEC.5.10        Security Management Requirements

The NMCS Security Management functions must ensure that the Confidentiality, Integrity, and Availability
(CIA) of the ASTI network are maintained. The ASTI network is classified as a medium baseline system
IAW FIPS PUB 199. The ASTI network must meet and be configured to support the requirements of FAA
Order 1370.82A, NIST SP 800-53 moderate baseline, and ATO-ISS-09-01 through ATO-ISS-09-17, ATO
Authorizing Official (AO) Security Implementation Guidance Memorandums, dated November 1, 2008.


SPEC.5.10.1      General Requirements

SPEC.5.10.1.1    When the referenced documentation in Section SPEC.5.10 states users such as “system
owner” or “designee”, the NMCS must be configured to meet the requirement.

SPEC.5.10.1.2     The NMCS must have an integrated security management function.

SPEC.5.10.1.2.1 The NMCS security management function must integrate, correlate, and display security
data from all of the various security NEs (e.g. appliances and applications) within the ASTI Network.

SPEC.5.10.1.2.2 Reserved

SPEC.5.10.1.2.3 The NMCS must be user configurable to automatically identify, correlate, rank and report
the following types of information on the security display of the workstation at a minimum:
            a) Virus threats
            b) Vulnerabilities
            c) Major IDS and/or IPS events
            d) Repeated failures to gain access to the NMCS information, data, appliances and/or
               applications
            e) Reportable event log activity
            f) Physical access to sites and equipment
            g) Communications failures

10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 109
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


            h) Dial backup usage

SPEC.5.10.1.2.4 The NMCS must be capable of analyzing SEs and REs, correlating one or more of them,
and identifying and ranking potential threats.

SPEC.5.10.1.2.5 The NMCS must be capable of displaying a user configurable amount of top level threats.

SPEC.5.10.1.2.6 Threat level and ranking rules must be user configurable.

SPEC.5.10.1.2.7 The thresholds and tolerances of threats must be user configurable.

SPEC.5.10.1.2.8 The NMCS must be capable of displaying and forwarding top level threat data to other
NMCS applications such that non-security user level personnel can have access to top level threat data.

SPEC.5.10.1.2.9 The NMCS security event manager must be capable of forwarding alerts to other NMCS
applications (e.g. fault management application).

SPEC.5.10.1.3   Any equipment other than workstations located at ZAN ARTCC and dedicated to
providing NMCS security functions must be located in a rack(s) dedicated solely to security functions.

SPEC.5.10.1.4     Software updates for security applications, such as anti-virus protection and IDS/IPS
systems, must be:

            a) Downloadable via the Internet to a workstation that is not connected to the NMCS.
            b) Capable of being copied to transport media (e.g. CD ROM drives.)
            c) Loadable into the configuration management and security function via workstations.


SPEC.5.10.2      Access Control

SPEC.5.10.2.1      The NMCS must have the capability to allow a user to manage NMCS accounts
including establishing, activating, modifying, reviewing, disabling, and removing accounts (AC-2, Account
Management).

SPEC.5.10.2.2     The NMCS must automatically terminate temporary and emergency accounts after a user
configurable default value of 24 hours in a maximum of one hour increments (AC-2, Account
Management).

SPEC.5.10.2.3      The NMCS must automatically disable inactive accounts after a user configurable default
value of 30 days in a maximum of one day increments (AC-2, Account Management).

SPEC.5.10.2.3.1 The NMCS must be capable of being user configurable to automatically disable inactive
user accounts after a value of 365 days.

SPEC.5.10.2.4     The NMCS must follow FAA Order 1370.92, Password and PIN Management.

SPEC.5.10.2.4.1 For all NEs that contain SNMP agents, default SNMP community strings such as “public”
and “private” must be replaced with community strings that are equivalent to passwords in strength as
specified in FAA Order 1370.92.

10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 110
ASTI                                         Amendment 5                              DTFAWA-10-R-00039


SPEC.5.10.2.5       For all NEs that contain SNMP agents, ACLs must be used to further limit direct access
to local collector(s).

SPEC.5.10.2.6      The NMCS must be user configurable and set to enforce a minimum limit of three (but
not to exceed five) consecutive invalid access attempts by a user (AC-7, Unsuccessful Login Attempts).

SPEC.5.10.2.7 The NMCS user must be able to configure the time period, with a default value of two
minutes, for invalid access attempts (AC-7, Unsuccessful Login Attempts).

SPEC.5.10.2.8      The NMCS must be user configurable and set to the default value to automatically lock
the account for a minimum of 20 minutes when the maximum number of unsuccessful attempts is exceeded.

SPEC.5.10.2.9       System-Use Notification Banners (AC-8, System Use Notification)

SPEC.5.10.2.9.1 The system use notification message must provide user configurable privacy and security
notices and remains on the screen until the user takes explicit actions to log on to the information system
(System Use Notification). The notification message text must be set to the following default:

                                    **WARNING**WARNING**WARNING**
            This is a U.S. Government protected computer system. Loss of human life may result
            from service interruption. Only authorized users performing authorized activities may
            use this system. Anyone using this system is subject to having their activities
            intercepted, monitored, recorded, captured, audited, and disclosed. Anyone’s activities
            may be intercepted, monitored, recorded, captured, audited, or disclosed in any manner
            by authorized personnel, while reviewing the activities of other users. Anyone using
            this system consents to such interception, monitoring, recording, capturing, auditing,
            and disclosure, for any lawful purpose. All information obtained or disclosed by any of
            the above methods, can be used as evidence for administrative or civil action, and/or
            criminal prosecution.
                                     **WARNING**WARNING**WARNING**

SPEC.5.10.2.9.2 User Agreement and Access through Graphical User Interfaces (GUI)

SPEC.5.10.2.9.2.1       A statement must be included that requires the user to agree to the terms stated
before being allowed to proceed further on the NMCS.

SPEC.5.10.2.9.2.2        If the user disagrees with the terms stated, they must be automatically denied
access from that point forward.

SPEC.5.10.2.9.2.3        The banner must be presented to users in 14-pitch font.

SPEC.5.10.2.9.3 User Agreement and Access through Character User Interfaces (CUI) (also referred to as
Command Line Interface (CLI))

SPEC.5.10.2.9.3.1       A statement must be included that notifies the user that continuing constitutes
agreement to the terms stated before being allowed to proceed further on the NMCS.

SPEC.5.10.2.9.3.2      The banner must be presented to all users until action is taken by the user accessing
the computer through a CUI, such as SSH or a console point.

10/07/10                                       SECTION J-1: ASTI TECHNICAL SPECIFICATION - 111
ASTI                                             Amendment 5                                 DTFAWA-10-R-00039


SPEC.5.10.2.10 The NMCS network must automatically terminate a command-line session (e.g., telnet,
ftp, ssh, slogin) after a user configurable default value of 10 minutes of inactivity (AC-12, Session
Termination).

SPEC.5.10.2.11 The NMCS network must not allow user actions without unique identification or
authentication (i.e., not allow anonymous activity) (defining AC-14, Permitted Actions w/out Identification
or Authentication).

SPEC.5.10.2.12      The NMCS must authorize, monitor, and control all methods of access to the information
system. .

SPEC.5.10.2.13      The NMCS must have automated mechanisms to facilitate the monitoring and control of
access methods.

SPEC.5.10.2.14 The NMCS network must use cryptography to protect the confidentiality and integrity of
remote59 access sessions (AC-17, Remote Access).



SPEC.5.10.3        Audit & Accountability

SPEC.5.10.3.1      The NMCS must have sufficient audit record storage capacity, for the auditing capability
described, to ensure that such capacity will not be exceeded (AU-4, AU-11 Audit Storage Capacity and
Audit Record Retention).

SPEC.5.10.3.1.1 The NMCS must be configurable, when primary online audit storage capacity is
exhausted or a failure of storage media/mechanism occurs, to ensure that audit records will be maintained
with the following default values:
             a) A user configurable minimum of 15 days locally
             b) A user configurable 1 year in a centralized aggregated archive (centralized, online
                backup/aggregation)

SPEC.5.10.3.1.2 The NMCS backup data must be capable of being produced such that it can be relocated
to a secure off-site facility with environmental controls sufficient to ensure data integrity and usability for
seven years.

SPEC.5.10.3.1.3 Chain of custody60 rules for evidence and evidence preservation must be enforced
throughout this time interval. (Audit Storage Capacity and Audit Record Retention).

SPEC.5.10.3.1.4 In the event of audit storage capacity is exceeded, the NMCS must overwrite oldest audit
records first. The information must be forwarded and stored on a log aggregation subsystem, and in the
event of a failure, overwrite oldest aggregated logs first.




59
   Remote access is defined as stated in ATO-ISS-09-01 ATO Authorizing Official (AO) Security Implementation
Guidance Memorandum – Access Control dated November 1, 2008.
60
   Chain of custody is a process that tracks the movement of evidence through its collection, safeguarding, and analysis
lifecycle by documenting each person who handled the evidence, the date/time it was collected or transferred, and the
purpose for the transfer. See NIST SP 800-86 for guidance.
10/07/10                                           SECTION J-1: ASTI TECHNICAL SPECIFICATION - 112
ASTI                                              Amendment 5                                 DTFAWA-10-R-00039


SPEC.5.10.4         Identification & Authentication

SPEC.5.10.4.1     The NMCS must employ closed network, multifactor authentication for system access
that is NIST SP 800-63 level 3 compliant using a hardware authentication device (IA-2, User ID &
Authentication).

SPEC.5.10.4.1.1 Multifactor authentication must function locally even when site communications are
down for a minimum of one week.

SPEC.5.10.4.1.2 Dial backup, where employed, must use the same two form factor authentication.

SPEC.5.10.4.2       The NMCS user must have the capability to disable any device and any connection to a
device.



SPEC.5.10.5         Risk Assessment

SPEC.5.10.5.1      The NMCS must have the capability to both authoritatively as well as non-authoritatively
scan for vulnerabilities (Vulnerability Scanning).

SPEC.5.10.5.2     All NMCS components must be scanned for vulnerabilities prior to the component being
attached to the NMCS (RA-5, Vulnerability Scanning).

SPEC.5.10.5.2.1 Any vulnerability found must be resolved prior to the component being attached to the
NMCS (RA-5, Vulnerability Scanning).


SPEC.5.10.6         System & Communication Protection

SPEC.5.10.6.1       The NMCS must identify and either protect against or limit the effects of denial of
service attacks, including at a minimum the following (SC-5 and SC-7, Denial of Service Protection and
Boundary Protection):

             a) Denial of service attacks
             b) Distributed denial of service attacks
             c) Insider attacks
             d) Unauthorized or unexpected user actions
             e) Unauthorized intrusions
             f) External attacks
             g) Content-based attacks
             h) Zero day61 attacks

SPEC.5.10.6.1.1 The identification mechanism(s) for detection (e.g. rules, learned behavior, signatures,
etc.) must be configurable by a user.

61
  Vulnerabilities that are either unknown to others, undisclosed to the software vendor, or for which no security fix is
available.
10/07/10                                            SECTION J-1: ASTI TECHNICAL SPECIFICATION - 113
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


SPEC.5.10.6.1.2 The NMCS must have intrusion detection and prevention capability in-line between
WAN routers and switches at each hub where information enters and/or leaves control of the ASTI network
(i.e. satellite, dial-backup, other service provider).

SPEC.5.10.6.1.3 Intrusion detection and prevention capability at the hubs must be manageable from any
workstation through the security management interface.

SPEC.5.10.6.1.4 Intrusion prevention must be capable of being manually approved by a user prior to the
preventative action being applied to the NMCS.

SPEC.5.10.6.1.4.1       The NMCS must allow different users to approve preventative actions.

SPEC.5.10.6.1.4.2       The NMCS must allow for a user to easily transition approval responsibility to
another user.

SPEC.5.10.6.1.4.3       The NMCS must be capable of automatic transition of approval responsibility to
another user.

SPEC.5.10.6.1.5 Intrusion detection and prevention technologies as defined in NIST SP 800-94 must be
aligned with the type, characteristics, and trends of network data found in the NMCS.

SPEC.5.10.6.1.6 Intrusion detection and prevention capability must be configurable by a user to fail open
(denies all traffic) and closed (allows all traffic).

SPEC.5.10.6.2      The NMCS must be user configurable to deny network traffic by default and allow
network traffic by exception (i.e., deny all, permit by exception) (SC-7, Boundary Protection).

SPEC.5.10.6.3     The NMCS must use cryptography to protect the integrity and confidentiality of
transmitted NMCS information between sites using FIPS-validated, NSA-approved cryptography (e.g.,
Advanced Encryption Standard (AES) 256 bit encryption) IAW FIPS Standards Publication 197 (SC-23,
Session Authenticity).

SPEC.5.10.6.4     The NMCS must terminate a network connection at the end of a session or after a user
configurable default value of 10 minutes of inactivity (SC-10, Network Disconnect).



SPEC.5.10.7      System & Information Integrity

SPEC.5.10.7.1       The NMCS must centrally manage an enterprise flaw remediation process and have the
capability to install updates automatically after user initiation or acceptance (SI-2, Flaw Remediation).

SPEC.5.10.7.2     The NMCS must manually update the malicious code and flaw remediation protection
software through removable media such as CD ROM (SI-2 and SI-3, Flaw Remediation and Malicious
Code Protection).

SPEC.5.10.7.2.1 The NMCS must centrally control the enterprise malicious code protection software so
that it can be downloaded to the various components over the NMCS network from one central location.(SI-
3, Malicious Code Protection).



10/07/10                                     SECTION J-1: ASTI TECHNICAL SPECIFICATION - 114
ASTI                                        Amendment 5                             DTFAWA-10-R-00039


SPEC.5.10.7.3      The NMCS must use user configurable tools to monitor events on the information
system, detect attacks, and provide identification of unauthorized use of the system as described for
Enterprise solutions in FAA Memorandum ATO-ISS-09-17 ATO Authorizing Official (AO) Security
Implementation Guidance Memorandum dated November 1, 2008 (System and Information Integrity) SI-4
(Information System Monitoring Tools & Techniques).

SPEC.5.10.7.4     The NMCS must be configurable to monitor inbound and outbound communications for
unusual or unauthorized activities or conditions (Information System Monitoring Tools & Techniques).



SPEC.5.10.8      Logging

SPEC.5.10.8.1  Logged items must utilize TOD date/time stamps as specified in Section SPEC.5.8.1.2 -
Time-Of-Day (TOD)Time-Of-Day (TOD).                                                                           Formatted: Font: Not Bold


SPEC.5.10.8.2   The NMCS must log all SEs in the functional requirements of Section SPEC.5.10 -
Security Management Requirements.



SPEC.5.10.9      Reporting

SPEC.5.10.9.1 High Severity Threat Report – The NMCS must provide a report detailing any high
severity threats and their acknowledgement and disposition for a user specified time period.

SPEC.5.10.9.2       Threat Report – The NMCS must provide a report detailing any severity threats and their
disposition (if any) for a user specified time period.



SPEC.5.10.10     Workstations

SPEC.5.10.10.1 The NMCS must provide a graphical user interface implemented on a workstation to
enable the NMCS security administrator to secure the ASTI Network IAW Section SPEC.5.10 - Security
Management Requirements of this specification.

SPEC.5.10.10.2 The NMCS must have the capability to specify the workstations where the security
management interface is displayed and to authenticate the user who is requesting to have access to the
security data and other logged data.




10/07/10                                      SECTION J-1: ASTI TECHNICAL SPECIFICATION - 115

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:0
posted:2/7/2013
language:Unknown
pages:117