NAVO_Modem_Requirements_v1_1_WRW_rev 1 .pdf
PDF 225 KB Posted
- Attached to
- Satellite Modem IDIQ Supply
- Solicitation number
- N6426714R0008
About this file
Specifications for RFP - N64267-14-R-0008.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Q__A_Mod_-_12_Dec.pdf | ||
| NAVO_Modem_Requirements_v1_2_HV_As_of_12_Dec_13.pdf | ||
| Past_Performance_Questionaire.docx | DOCX document | |
| Q_and_A_MOD_-_5_Dec_13.pdf | ||
| MOD_1_to_RFP.pdf | ||
| SATCOM_Modem_IDIQ_-_RFP_FINAL.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Naval Oceanographic Office Modem Specification
***NSWC-CORONA-RS10-SPEC-20130126-001***
V1.1
Prepared by
Naval Surface Warfare Center – Corona Division Telecommunications Engineering (RS10)
P.O. Box 5000 Corona, CA 92878-5000
This page intentionally left blank.
i
Table of Contents
1.0 SCOPE......................................................................................................................... 1-1
2.0 Requirements ............................................................................................................... 2-1
2.1 Shipboard Modem..................................................................................................... 2-1
2.2 Earth Station Gateway Hub ....................................................................................... 2-3
2.3 Management/Security ................................................... Error! Bookmark not defined.
2.4 Management: ............................................................................................................ 2-4
2.5 Security: .................................................................................................................... 2-5
2.6 Certification: .............................................................................................................. 2-5
2.7 Training ..................................................................................................................... 2-5 Formal training shall be provided with the goal of teaching a technician how to operate, manage, and troubleshoot modem equipment. .................................................................... 2-5
2.8 Shipping .................................................................................................................... 2-5
1-1
1.0 SCOPE
The intent of this document is to provide the minimum requirements for a satellite based data communications system capable of meeting the needs of the Naval Oceanographic Command
(NAVO).
This system will replace the current Frequency Division Multiple Access (FDMA) components that are in use today. The current FDMA system does not allow for automatic region switchover, take advantage of bandwidth sharing, or utilize priority. The new solution needs to meet all of these requirements.
The NAVO network will consist of seven ships, three hubs sites (one for each ocean region), and NAVO headquarters (HQ) on Stennis Space Center in Mississippi as shown in Figure 1.
Connectivity between the hub sites and the ships will be over C-band satellite and between the hub sites and NAVO HQ via terrestrial connectivity. The Atlantic Ocean Region (AOR) and Pacific Ocean Region (POR) hub sites are shown notionally located on the east and west coast of the United States. The Indian Ocean Region (IOR) is shown notionally located in Europe.
The NAVO fleet consists of seven ships that dynamically transition between ocean regions as dictated by operational requirements. Seven ships, up to four of which can be co-located in the same ocean region at the same time, pass real-time data to and from NAVO HQ via the hub sites. Remote operations and maintenance will be done from NAVO HQ on all equipment including hubs and shipboard modems.
Figure 1. Typical NAVO Network Requirements
1-2
This page intentionally left blank.
2-1
2.0 Requirements
The following sections describe the requirements for this system.
2.1 Shipboard Modem
The shipboard modem shall be referred to as “the modem” for the remainder of this document.
2.1.1 Size
2.1.1.1 The modem shall be rack mountable in a standard 19 inch equipment rack.
2.1.1.2 The modem shall fit in a maximum of 3 rack units.
2.1.2 The modem shall support 100-240 VAC (50-60Hz) power input utilizing standard three-conductor, detachable power cord.
2.1.3 Network Access
2.1.3.1 The modem shall utilize Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or a combination of these two access schemes.
2.1.3.2 The modem shall be deigned to receive a signal from the hub and extract only the information destined for its own use.
2.1.3.3 The modem shall be designed to transmit its information back to the hub without interfering with other modems on the network.
2.1.3.4 The network access scheme and modem shall be approved for use with both Intelsat and Defense Information’s Systems Agency (DISA) operated Earth Stations. (Prior installations at these facilities are acceptable.)
2.1.4 Intermediate Frequency (IF)
2.1.4.1 The modem shall transmit using L Band frequencies (950- 1450 MHz) via the transmit IF port.
2.1.4.2 The modem shall receive using L Band frequencies (950-1450 MHz) via the receive IF port.
2.1.4.3 The modem shall support receive standard and inverse
spectrums as required for proper operation.
2-2
2.1.5 Modulator/Demodulator
2.1.5.1 The modem shall support the following digital modulation schemes: BPSK, QPSK, 8PSK and 16QAM or 16APSK.
2.1.5.2 The modem shall support either Turbo or LDPC Forward Error Coding (FEC) at standard FEC rates (1/2, 3/4, 7/8 etc…).
2.1.5.3 The modem shall be capable of receiving speeds of 500 kbps to 2.5Mbps from the hub site.
2.1.5.4 The modem shall be capable of transmitting speeds of 500 kbps to 1.5 Mbps to the hub.
2.1.6 Physical Interfaces
2.1.6.1 Ethernet interface port for terrestrial IP network connection.
2.1.6.2 Type F or Type N interface IF ports (RX and TX) for satellite network. Preferred 50 Ohm interface but 75 Ohm is acceptable.
2.1.6.3 Console interface port (for local control of the modem)
2.1.6.4 Antenna control port (for pointing of the satellite antenna)
Location interface port (for ship latitude/longitude). If a port is not available for the unit the system shall be capable of monitoring and acting upon GPS coordinates through any other protocol with a SEATEL terminal.
2.1.7 The modem shall support star (hub to ship) and mesh (ship to ship) networks.
2.1.8 The modem shall support the minimum Ethernet protocols: TCP/IP, UDP/IP, ICMP, and IGMP.
2-3
2.1.9 Antenna Control/Region Switchover
2.1.9.1 The modem shall support automatic region switchover where region switchover is defined as a ship transiting from one ocean region to another one. Hysteresis shall be designed into the system such that once a region switchover has occurred; the modem will not switch back to the original region until necessary.
2.1.9.2 The modem once configured from the management system
shall provide pointing instructions to the satellite antenna via the antenna control port.
2.1.9.3 The antenna control port shall support either RS232 or RS422 signals.
2.1.9.4 The modem shall provide pointing instructions to a SEATEL antenna control unit via the OpenAMIP protocol, ROAM protocol, or any other protocol that has been proven to work with SEATEL terminals.
2.1.9.5 The modem shall support ship location (latitude and longitude) via the location interface port for determining appropriate satellite pointing and Modem configuration.
2.1.9.6 Region switchover shall not require modification of the terrestrial network IP addresses.
2.1.9.7 Region switchover shall not require calling the service provider to bring up a carrier in a new region in which bandwidth is already being leased on a predetermine satellite.
2.1.10 The modem shall meet MIL-STD-810F, Method 514.5, Procedure I, Category 4 Table 514.5C-VII (Exposure C1) for vibration. The modem shall meet MIL-STD-810F, Method 516.5 (terminal peak sawtooth exposure) for shock.
2.2 Earth Station Gateway Hub
The earth station gateway hub (the “hub”) shall be comprised of a single chassis which houses multiple cards (with ancillary equipment), a single individual unit, or multiple pieces of equipment.
2.2.1 Design
2.2.1.1 The hub shall support an operational and a hot stand-by unit.
2.2.1.2 The hub shall support L-Band (950 – 1450 MHz) input/output to connect to a single satellites region.
2.2.1.3 The hub shall be rack mountable in a standard 19 inch equipment rack.
2.2.1.4 The hub and all ancillary equipment shall be no greater than
15 rack units.
2-4
2.2.2 The hub shall support two 100-240 VAC (50-60Hz) power inputs utilizing standard three-conductor, detachable power cords. One for main power and the other will be for fail over.
2.2.3 The hub shall operate in the L Band frequency (950-1450 MHz).
2.2.4 Modulation:
2.2.4.1 Frequency: The hub shall use Time Division Multiple Access
(TDMA).
2.2.4.2 The modem shall support the following digital modulation schemes: BPSK, QPSK, 8PSK, and 16QAM or 16APSK.
2.2.4.3 The hub shall support either Turbo or LDPC Forward Error
Coding (FEC) at standard FEC rates (1/2, 3/4, 7/8 etc…).
2.2.5 Interface:
2.2.5.1 Gigabit Ethernet interface port for terrestrial network at the
Earth station.
2.2.5.2 Type F or Type N interface IF ports (RX and TX) for satellite network. Preferred 50 Ohm interface but 75 Ohm is acceptable.
2.2.6 Topology:
The hub shall support star (hub to ship) and mesh (ship to ship) topologies.
2.2.7 Operation:
Unit shall support point to multipoint communications in order to give network access for up to 5 ships within the same ocean region.
2.3 Management:
2.3.1 Each Modem shall be able to be managed locally.
2.3.2 All modems across all ocean regions shall be able to be managed at a central location.
2.3.3 Management shall have the option to configure profiles to automatically provide dynamic bandwidth allocation as remote units come online or offline or move into different ocean regions.
2.3.4 Management shall be capable of being located at a different location other than the Earth station.
2.3.5 Management system shall have redundancy so that if one management system becomes non-operational another system can take over.
2-5
2.3.6 Status of all link connections will all be displayed by management software to include
2.3.6.1 Signal strength
2.3.6.2 Uplink/Downlink rates
2.3.6.3 Current modulation and coding scheme
2.3.6.4 Signal to noise ratio
2.3.7 Management system shall provide QoS adjustable controls.
2.3.8 It would be preferred if the management system can automatically change modulation and coding to adapt to environmental challenges (rain fade, fog, etc) but not required.
2.4 Security:
2.4.1 All units shall support at least 3xDES encryption.
2.5 Certification:
Manufacturer/Vendor must be able to show proof that system that is being submitted for award has been tested on commercial satellite carriers (NSS, IntelSat, etc.) and has been approved to operate in automated bandwidth/power mode by the satellite providers.
2.6 Training
Formal training shall be provided with the goal of teaching a technician how to operate, manage, and troubleshoot modem equipment.
2.7 Shipping
The government will be responsible for transporting material to the point of installation.
The contractor will be responsible for transporting material to NSWC Corona.
| 1.0 SCOPE |
| 2.0 Requirements |
| 2.1 Shipboard Modem |
| 2.1.1 Size |
| 2.1.1.1 The modem shall be rack mountable in a standard 19 inch equipment rack. |
| 2.1.1.2 The modem shall fit in a maximum of 3 rack units. |
| 2.1.2 The modem shall support 100-240 VAC (50-60Hz) power input utilizing standard three-conductor, detachable power cord. |
| 2.1.3 Network Access |
| 2.1.3.1 The modem shall utilize Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or a combination of these two access schemes. |
| 2.1.3.2 The modem shall be deigned to receive a signal from the hub and extract only the information destined for its own use. |
| 2.1.3.3 The modem shall be designed to transmit its information back to the hub without interfering with other modems on the network. |
| 2.1.3.4 The network access scheme and modem shall be approved for use with both Intelsat and Defense Information’s Systems Agency (DISA) operated Earth Stations. (Prior installations at these facilities are acceptable.) |
| 2.1.4 Intermediate Frequency (IF) |
| 2.1.4.1 The modem shall transmit using L Band frequencies (950-1450 MHz) via the transmit IF port. |
| 2.1.4.2 The modem shall receive using L Band frequencies (950-1450 MHz) via the receive IF port. |
| 2.1.4.3 The modem shall support receive standard and inverse spectrums as required for proper operation. |
| 2.1.5 Modulator/Demodulator |
| 2.1.5.1 The modem shall support the following digital modulation schemes: BPSK, QPSK, 8PSK and 16QAM or 16APSK. |
| 2.1.5.2 The modem shall support either Turbo or LDPC Forward Error Coding (FEC) at standard FEC rates (1/2, 3/4, 7/8 etc…). |
| 2.1.5.3 The modem shall be capable of receiving speeds of 500 kbps to 2.5Mbps from the hub site. |
| 2.1.5.4 The modem shall be capable of transmitting speeds of 500 kbps to 1.5 Mbps to the hub. |
| 2.1.6 Physical Interfaces |
| 2.1.6.1 Ethernet interface port for terrestrial IP network connection. |
| 2.1.6.2 Type F or Type N interface IF ports (RX and TX) for satellite network. Preferred 50 Ohm interface but 75 Ohm is acceptable. |
| 2.1.6.3 Console interface port (for local control of the modem) |
| 2.1.6.4 Antenna control port (for pointing of the satellite antenna) |
| 2.1.7 The modem shall support star (hub to ship) and mesh (ship to ship) networks. |
| 2.1.8 The modem shall support the minimum Ethernet protocols: TCP/IP, UDP/IP, ICMP, and IGMP. |
| 2.1.9 Antenna Control/Region Switchover |
| 2.1.9.1 The modem shall support automatic region switchover where region switchover is defined as a ship transiting from one ocean region to another one. Hysteresis shall be designed into the system such that once a region switchover has occurred; th... |
| 2.1.9.2 The modem once configured from the management system shall provide pointing instructions to the satellite antenna via the antenna control port. |
| 2.1.9.3 The antenna control port shall support either RS232 or RS422 signals. |
| 2.1.9.4 The modem shall provide pointing instructions to a SEATEL antenna control unit via the OpenAMIP protocol, ROAM protocol, or any other protocol that has been proven to work with SEATEL terminals. |
| 2.1.9.5 The modem shall support ship location (latitude and longitude) via the location interface port for determining appropriate satellite pointing and Modem configuration. |
| 2.1.9.6 Region switchover shall not require modification of the terrestrial network IP addresses. |
| 2.1.9.7 Region switchover shall not require calling the service provider to bring up a carrier in a new region in which bandwidth is already being leased on a predetermine satellite. |
2.1.10 The modem shall meet MIL-STD-810F, Method 514.5, Procedure I, Category 4 Table 514.5C-VII (Exposure C1) for vibration. The modem shall meet MIL-STD-810F, Method 516.5 (terminal peak sawtooth exposure) for shock.
| 2.2 Earth Station Gateway Hub |
| 2.2.1 Design |
| 2.2.1.1 The hub shall support an operational and a hot stand-by unit. |
| 2.2.1.2 The hub shall support L-Band (950 – 1450 MHz) input/output to connect to a single satellites region. |
| 2.2.1.3 The hub shall be rack mountable in a standard 19 inch equipment rack. |
| 2.2.1.4 The hub and all ancillary equipment shall be no greater than 15 rack units. |
| 2.2.2 The hub shall support two 100-240 VAC (50-60Hz) power inputs utilizing standard three-conductor, detachable power cords. One for main power and the other will be for fail over. |
| 2.2.3 The hub shall operate in the L Band frequency (950-1450 MHz). |
| 2.2.4 Modulation: |
| 2.2.4.1 Frequency: The hub shall use Time Division Multiple Access (TDMA). |
| 2.2.4.2 The modem shall support the following digital modulation schemes: BPSK, QPSK, 8PSK, and 16QAM or 16APSK. |
| 2.2.4.3 The hub shall support either Turbo or LDPC Forward Error Coding (FEC) at standard FEC rates (1/2, 3/4, 7/8 etc…). |
| 2.2.5 Interface: |
| 2.2.5.1 Gigabit Ethernet interface port for terrestrial network at the Earth station. |
| 2.2.5.2 Type F or Type N interface IF ports (RX and TX) for satellite network. Preferred 50 Ohm interface but 75 Ohm is acceptable. |
| 2.2.6 Topology: |
| The hub shall support star (hub to ship) and mesh (ship to ship) topologies. |
| 2.2.7 Operation: |
| Unit shall support point to multipoint communications in order to give network access for up to 5 ships within the same ocean region. |
| 2.3 Management: |
| 2.3.1 Each Modem shall be able to be managed locally. |
| 2.3.2 All modems across all ocean regions shall be able to be managed at a central location. |
| 2.3.3 Management shall have the option to configure profiles to automatically provide dynamic bandwidth allocation as remote units come online or offline or move into different ocean regions. |
| 2.3.4 Management shall be capable of being located at a different location other than the Earth station. |
| 2.3.5 Management system shall have redundancy so that if one management system becomes non-operational another system can take over. |
| 2.3.6 Status of all link connections will all be displayed by management software to include |
| 2.3.6.1 Signal strength |
| 2.3.6.2 Uplink/Downlink rates |
| 2.3.6.3 Current modulation and coding scheme |
| 2.3.6.4 Signal to noise ratio |
| 2.3.7 Management system shall provide QoS adjustable controls. |
| 2.3.8 It would be preferred if the management system can automatically change modulation and coding to adapt to environmental challenges (rain fade, fog, etc) but not required. |
| 2.4 Security: |
| 2.4.1 All units shall support at least 3xDES encryption. |
| 2.5 Certification: |
| 2.6 Training |
| 2.7 Shipping |
File details come from the government source that posted it. Updated .