SOURCES SOUGHT
20 -- Moriah Wind System (MWS)
- Notice Date
- 1/30/2019
- Notice Type
- Synopsis
- NAICS
- 334519
— Other Measuring and Controlling Device Manufacturing
- Contracting Office
- Contracts Department Hwy. 547 Attn:B562-3C Lakehurst NJ 08733-5083
- ZIP Code
- 08733-5083
- Solicitation Number
- N6833519R0161
- Response Due
- 2/4/2019
- Point of Contact
- William T. Hemhauser, Contract Specialsit
- E-Mail Address
-
william.hemhauser@navy.mil
- Small Business Set-Aside
- N/A
- Description
- THIS IS A REQUEST FOR INFORMATION ONLY. It is not a Request for Proposal, a Request for Quotation, an Invitation for Bids, a solicitation, or an indication that the PMA-251 Program Office or NAVAIR will contract for the items contained in this RFI. The Naval Air Warfare Center Aircraft Division Lakehurst (NAWCADLKE) is seeking to continue the production of Moriah Wind Systems for US Navy, Military Sealift Command, US Coast Guard and other ships. A description of the Moriah Wind System (MWS) follows: MWS provides digital wind speed and direction information, including crosswind and headwind, to support decision making for air operations, combat, navigation, tactical planning and firefighting. The MWS replaces legacy Type F Wind Measuring and Indicating System, providing a single wind measuring system consistent across all ship classes and shore stations. MWS consists of 4 main parts: 1. Wind sensor unit (WSU) with non-moving parts 2. Wind Processing Unit (WPU) consisting of dual redundant sub-processors, capable of interfacing with legacy wind and ship systems and Local Area Networks (LANs) 3. High-End Display (HED) with full range of available wind information and ship speed/ course data, including the display of Aircraft Recovery Bulletins (ARBs), Launch and Recovery Envelopes (LREs) and Final Course data. The HED is hardwired to one of the WSUs in a safety critical configuration to enable the display of wind data when the WPU or other connecting network is not functioning. The HED fits inside an envelope no larger than 11.50" high by 18.00" wide by 9.53" deep. This does not include maintenance access, connector access or environmental excursions. 4. Low-End Display (LED) with basic wind information and ship speed/course data. LED fits inside an envelope no larger than 7.36" high by 11.10" wide by 6.06" deep. This does not include maintenance access, connector access or environmental excursions. 5. The WSUs, HEDs and LEDs are uniform across ship classes and shore stations, with the quantity of each item dependent upon ship class/shore location. Every MWS has one WPU with dual- redundant sub-processors, which will differ depending upon ship class and shore station either of which can individually perform all the functions necessary to keep MWS running. The sub-processors communicate with each other directly and periodically to determine functional status and to allow changes in control when a failure is detected. MWS accesses unclassified data only. 6. There is a degree of system-to-system information exchange in MWS. Neither MWS nor its components are connected to the Global Information Grid (GIG). MWS data is output from the WPU's sub-processor in several ways: 1) synchro interfaces to provide wind information to legacy systems (SLQ-32, SPN-46, Integrated Launch and Recovery Television System (ILARTS), and Arresting Gear Crosscheck System); 2) serial and network interfaces for output of wind, navigational and system information to displays; and 3) network interfaces to communicate wind information to other ship and shore station systems and displays. Currently, MWS will communicate over Aviation Data Management and Control System (ADMACS) on CVNs, through Digital Multiplex System (DMS) on DDGs and on a Moriah controlled network on all other ship classes. 7. Wind data is transmitted in the OD19 data format and the National Marine Electronics Association (NMEA) data format. 8. MWS receives the ARBs it displays through ADMACS via Network File System (NFS). 9. MWS displays LREs that are programmed into the HEDs. 10. In order to display ship's speed and direction, calculate true wind speed and direction as well as pitch and roll, MWS receives a data packet from onboard ship's navigation systems such as Navigation Sensor System Interface (NAVSSI). This data packet is governed by an interface requirements specification (IRS) and contains a host of navigational data, including ship's positional information. MWS is not using all of this information, although it must read the entire NAVSSI data packet prior to extracting the data required. The information in this packet is not sensitive unless the information is to be transmitted off the ship. However, MWS has no mechanism for transmitting data off the ship, nor any requirement to do so. MWS uses strictly defined data types for transmission into and out of the system. This information is limited to either NMEA ASCII strings using checksums to determine data integrity, structured binary data format using checksums to determine data integrity, proprietary DMS Light Internet Protocol (DLIP), and analog synchro resolver output to other ship's systems. The data items themselves are confined to information from known systems (as defined in the relevant IRS) or is confined to IP addresses and ports specified in the Interface Design Documents (IDD) and the network architecture (ADMACS, DMS or other network). The components contain no TELNET or File Transfer Protocol (FTP) capability. Configuration is done via a manual procedure where a laptop is attached to the system components using a serial cable (RS-422) and programming is done via contractor supplied software applications. A government specified and supplied laptop, configured by contractor graphical user interface software and centrally managed by the US Navy is utilized for this function." The processor software was written to run under a tailored Linux Operating System with minimal functionality on an Intel platform. This operating system consists of a Linux kernel that has been built specifically for use in this environment that will aid security. It contains only those device drivers and services that are relevant to this embedded environment. Software design protects system integrity by the fact that unauthorized personnel do not have the ability to modify the software configuration, data or application. MWS is not designed for use or visibility on the internet and there is no access to the internet. MWS uses UDP/IP & TCP/IP for unicast and multicast communication protocols. NAWCADLKE is requesting information from industry for the purpose of identifying qualified contractors interested in bidding on the possible competition of the expiring production contract of the Moriah Wind System (MWS). The objective of the new contract is to continue production of the following MWS parts, which establish the current MWS configuration baseline: NOTE: THIS NOTICE WAS NOT POSTED TO FEDBIZOPPS ON THE DATE INDICATED IN THE NOTICE ITSELF (30-JAN-2019); HOWEVER, IT DID APPEAR IN THE FEDBIZOPPS FTP FEED ON THIS DATE. PLEASE CONTACT 877-472-3779 or fbo.support@gsa.gov REGARDING THIS ISSUE.
- Web Link
-
Link To Document
(https://www.fbo.gov/spg/DON/NAVAIR/N68335/N6833519R0161/listing.html)
- Record
- SN05206861-F 20190201/190130230017 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |