RFQ_80NSSC18Q0923.docx

National Aeronautics and Space Administration NASA Shared Services Center Stennis Space Center, MS 39529-6000

8/3/2018

SUBJECT: Request for Quotation (RFQ) 80NSSC18Q0923, LMRS Console

This solicitation includes the following sections:

1. Statement of Work/Bid Schedule – Section 1

2. Instructions to Offerors – Section 2

3. Solicitation Provisions/Representations and Certifications – Section 3

4. Clauses/Terms and Conditions – Section 4

5. Quote Evaluation Criteria – Section 5

SECTION 1

STATEMENT OF WORK/BID SCHEDULE

STATEMENT OF WORK (SOW) FOR THE John C. Stennis Space Center

LAND MOBILE RADIO (LMR)

Dispatch Console System

Table of Contents

1. Introduction

1.1 Overview

General The National Aeronautics and Space Administration (NASA) John C. Stennis Space Center (SSC) requires an IP based Stand-alone Dispatch console, Radio Gateways, Base radios, and associated cables and hardware that will communicate on NASA’s currently installed Auxiliary 400 MHz Trunked Radio Site and a future (2019) Project 25 (P25) Trunked Land Mobile Radio (LMR) communications system based within the Mississippi Wireless Information Network (MSWIN).

SSC intends to purchase a modern, state-of-the-art system consisting of (2) full featured IP based Stand-alone Dispatch consoles, associated Gateways and radios for use throughout the Center, using VHF, 400 Megahertz (MHz) and 700/800 (MHz) radio channels. The system shall be a highly reliable, fault tolerant design that is supportable, will meet current needs and provides a growth path for future expansion.

Figure 1 Conceptual block diagram

Current Trunked Radio System

· The current system is a 400 MHz Motorola SmartNet 3.0 system that provides two (2) full featured dispatch consoles at the Security Dispatch station and Emergency Operations Center (EOC) locations in Building 8000 at SSC. The system also supports communications with Motorola Consolettes with digital remotes, and Motorola Mobile Control Stations (mobile radio with A/C power supply). The system also uses a Raven Vox Audio Switch providing Test Channel intercom to radio patches. This equipment provides intercom users access to the trunking radio system.

· SSC subscriber units total approximately 650, which are Motorola MTS 2000, XTS 2500, XTS 3000, XTS 5000, and APX 4000 portables, Motorola XTL5000 Astro Spectra Consolettes and base stations. The portable subscribers are certified intrinsically safe (IS) units.

Future system (FY2019)

· SSC is proposing the purchase of two (2) full featured IP based Stand-alone Dispatch Consoles to provide Security Dispatch operations and EOC Dispatch operations in Building 8000.

· SSC is working with the Mississippi Wireless Information Network (MSWIN) with the intention of having a MSWIN P25 700/800 MHz LMR system installed at a location provided by SSC.

· MSWIN is a statewide interoperable emergency communication voice and data network.

· SSC plans to migrate all of the 400 MHz Trunked Radio services to the MSWIN radio system.

The Offeror shall propose an IP based Stand-alone Dispatch Console system design that will best meet SSC’s requirements. The Stand-alone Dispatch Console system shall be proposed as a complete system with firm fixed prices for all of the equipment, installation, project management, software and services required by these specifications and this Statement of Work.

2. Console System Requirements

2.1 Console System Architecture

The console system shall be an Internet Protocol (IP) based system, which utilizes an IP network as the backbone to transport system messages and media.

The fundamental architecture of the system shall allow for console system devices (e.g. console positions, interface gateways) to be placed in multiple geographic locations. Dispersed system devices shall be capable of utilizing the same feature set as if they were co-located in the equipment room. The architecture shall also allow for related, independently managed console systems within the radio network to communicate with one another and control radio resources at all locations.

As part of the console architecture, the system shall provide an option to connect remote console system devices and multiple site locations via a multicast to unicast translation application. This removes the need to transport multicast traffic across the span between the dispersed console system devices and/or locations. Therefore, conventional IP networking (including Virtual Private Network or “VPN” technologies) may be used for such remote connections without concern for multicast routing and transport issues.

Maintenance and system software upgrades shall be handled by dealers or qualified end users. Factory support shall be available on an as needed basis.

A single console system architecture shall support as a minimum:

· Consoles: 2

· Radio lines: 30 Auxiliary Input/Output (AUX I/O) points: 10 per AUX I/O service, multiple AUX I/O services shall be allowed to extend this capacity.

2.2 Console Equipment

· Consoles shall be PC-based and the console software application shall support Windows 10 - 64-bit operating systems. Console PCs shall support network teaming (network interface card (NIC) Bonding) and support dual display monitors.

· A widescreen monitor shall be utilized to display the console user interface and shall support a minimum resolution of 1920x1080. The dispatcher shall be able to perform all dispatch operations by using the combination of the display screen and a mouse.

· The following items shall be offered as options for dispatch operation:

1. Footswitch The footswitch shall be used by the dispatcher to key the selected radio channel(s).

2. Maximum of 8 speakers Each speaker shall be in an individual enclosure and have separate volume control knob. Speakers shall also have a minimum volume level and be equipped with Light Emitting Diodes (LEDs) indicating power to the device and receive voice activity.

3. Desk microphone The desk microphone shall have a physical button that when pressed shall cause the microphone to be live on the selected radio channel(s) and a button to monitor select radio channels.

4. Headset Jackbox The Jackbox shall be compatible with either 4 or 6 wire headsets. Inserting the headset plug into the Jackbox shall automatically route the select audio to the headset and mute the select speaker. If an external telephone system is utilized and connected to the console system such that the dispatcher can use one headset to operate both, separate volume knobs shall be provided on the Jackbox to control radio volume and telephone volume.

5. Laptop Operation The console software shall run on a laptop that complies with the specifications of the desktop PC position. This option shall allow the dispatcher to use only the console software and a USB headset to perform their dispatching functions.

2.3 High Availability through Redundancy

· All console system hardware and software shall support NIC Bonding for redundancy, allowing two Ethernet connections with only one active at a given time.

· The architecture of the console system shall support optional redundancy of critical components and/or application services such that a failure in the component shall not cause disruption of service to the system as a whole.

2.4 Interface and control requirements

2.4.1 Remote Control of Radios

The console shall be capable of controlling radios using radio gateway interface boxes such as those listed below under ‘Radio Gateway Interfaces’ in section 3.

2.4.2 Project P25 Console SubSystem Interface (CSSI Per TIA.102-BACA) The Console shall be capable of interfacing to an Association of Public Safety Communications Officials (APCO) P25 Console Subsystem Interface (CSSI). The interface shall be compliant per TIA.102-BACB and shall support, as a minimum, the following features over the CSSI interface:

· Unit ID Display

· Talkgroup selection

· Group calls (incoming/outgoing)

· Incoming emergency group call

· Individual calls (incoming/outgoing

· Incoming emergency individual call

· Incoming emergency alert

· Incoming call alert

· Emergency Acknowledgement

· Advanced Encryption Standard (AES) and Data Encryption Standard (DES) Encryption

· Manual encryption key load

· Key Variable Loader (KVL) encryption key load support

· Long term voice logging support for voice and associated metadata

· Patching of talkgroups by operator

· Consistent visual user interface (UI) indications for transmit, receive, audio routing, and call state

· Instant Recall Recording (IRR) playback for all voice transmission with currnet implementation will no change

· Console preempt

2.4.3 Tone Signaling

· The console shall be capable of supporting the following tone signaling formats:

1. Motorola Two-Tone

2. Motorola Quick-Call 2 (1+1)

3. GE® Two-Tone

4. Reach Two-Tone

5. Plectron (Two-Tone w/ non-standard frequencies, durations, and gaps)

6. Dual-tone multi-frequency (DTMF)

7. Knox DTMF

8. 5/6 Tone

· To avoid tone distortion due to IP related issues, selective calling/paging tones used for signaling devices shall be generated and/or decoded at the radio interface device and not transported through the system as Voice Over Internet Protocol (VoIP) audio.

2.4.4 MDC 1200/Fleetsync Signaling

The system shall support encode and decode of the Motorola Data Communications (MDC) 1200 and Fleetsync. The interface to MDC 1200 or Fleetsync radios shall use a 4W analog interface and tone remote signaling. The following features shall be supported: Push-to-Talk (PTT) ID for individual radios and groups, Emergency alert, call alert, selective call, status request/report, radio availability check, radio enable/disable, and remote radio monitor.

2.4.5 Time Sync Input

The console system shall have the capability to accept a master clock data input which utilizes Network Time Protocol (NTP). The master clock source shall be used to keep all displayed time/date fields synchronized.

2.5 Functional requirements

2.5.1 General User Interface

· The user interface shall support the configuration of multiple workspaces for a dispatch screen. Workspaces shall allow for “on the fly” configuration by dispatch personnel such that they may add and delete resources to and from the workspace, move resources around within the workspace and resize certain resources.

· There shall be an option provided to a technician or system administrator level to lock each individual workspace such that nothing may be moved, added or deleted from the workspace. There shall also be an option to lock each visual control and system resource displayed on the screen such that a workspace that is unlocked may have locked items on it to prevent a dispatcher from changing them while the console is running.

· The user interface shall have the ability to support multiple roles each with a different screen layout and radio resource list. The role-based configuration shall be made available at every console workstation such that a user may log in at any workstation and begin using the layout appropriate for their role.

· In order to minimize visual distractions to the dispatcher, the user interface shall be capable of being configured such that information and indications appear only when applicable to an event. It shall not be necessary to have every indication constantly visible on the screen regardless of its state in order for the dispatcher to access it.

· The dispatcher shall have access to system resources in the system that may not be permanently displayed on their screen including:

1. Adding a radio channel to their workspace for as long as the dispatcher requires.

2. Allowing for an instant transmit or access to receive notifications for radio channels that they do not add to the workspace.

3. Adding Aux I/O sensors and controls to their workspace for as long as the dispatcher requires.

· The user interface shall allow the ability to associate individual, customized images to represent each entity stored in the console system data repository.

· The console software shall allow for the ability to display the dispatch center’s name, logo, or other graphic icon on all screens.

· The console software shall allow the selection of at least 100 different colors for channel modules, allowing quick identification of the function by the dispatcher.

2.5.2 Aux I/O

· The console system shall support connection to auxiliary digital inputs (for receiving status from external equipment) and digital outputs (for external device control).

· Input shall be capable of showing at least two indication states within the same indicator on the console screen in order to reflect different status levels.

· Output controls shall be available in latching and momentary operation. The output control shall be capable of showing at least two indication states.

· A combined input and output control shall be available such that the dispatcher views the input status and controls the output from a single visual control. Activation of the output would send activation but only change the indication based on state of input.

2.5.3 Radio Control

· Select - The dispatcher shall have the ability to place a channel into the selected state via a single operation. When a radio channel is placed into the selected state, that audio is routed to the appropriate device, either the select speaker or the headset or both. Microphone audio is routed to either the headset microphone or a desk microphone depending on the console configuration. There shall be a visual indication that the dispatcher has placed a channel into the selected state.

· Transmit - The system shall support the ability to transmit on a selected channel or channels. The user interface shall provide visual feedback to the dispatcher that the transmission is either successful or blocked. When transmitting on multiple selected channels, if any channel is busy or unavailable, this shall not prevent transmission on non-busy channels.

· Instant Transmit - The system shall allow the dispatcher to perform an instant transmit on a radio channel without the need to place the channel into a selected state. An instant transmit on a channel shall not result in a transmission on currently selected radio channels.

· Receive - The user interface shall provide a visual indication that there is incoming audio traffic on a radio channel. If the channel is selected, the audio is routed to the applicable device (headset or select speaker).

The user interface shall provide a method for dispatchers to see that there is an incoming call on a channel(s) that is not visible in their primary workspace. This method shall allow the dispatcher to interact (select and/or transmit) with that radio channel if necessary. Which channels appear to the dispatcher via this method shall be configurable by a technician or system administrator.

· Monitor, Idle States - The user interface shall allow the dispatcher to place audio from a specified radio in a monitor speaker. The user interface shall be capable of allowing the dispatcher to change which monitor speaker the audio is routed to at any time.

The user interface shall allow the dispatcher to view activity and visual indications on a radio channel on their screen without requiring the audio to be present in the select or monitor speakers.

· Radio ID & Alias - When available, the PTT ID shall be displayed on the user interface for an incoming radio transmission. When available, the contact entry name shall be displayed for the matching PTT ID from the console system’s data repository

· Time Stamp - The user interface shall display the time that an incoming or outgoing radio transmission occurs.

· Alert tone - The system shall be capable of transmitting a predefined alert tone on the selected channel(s).

· Multi-select (Simulselect) - The user interface shall support multi-channel selection where selecting a channel does not change the state of a previously selected channel. The user interface shall support this without requiring the dispatcher to change modes or screens. Multi select shall be activated by a single mouse click or touch.

While multi-selected, a dispatcher shall be able to instant transmit to a group or individual in the multi-select with a single mouse click or touch. The user interface shall allow the dispatcher to see who is in the Multi-Select and add or remove entities with a single mouse click or touch.

· Frequency/Talkgroup Change - The system shall allow the dispatcher to change the frequency or talkgroup on a radio channel if allowed by the base station. The system shall support the ability for a technician or administrator to label the radio frequencies/talkgroups to a desired name. When the dispatcher changes the frequency on a radio channel, the change shall be reflected on all consoles.

· Patch - The system shall support the ability to connect two or more channels together such that the receive audio of one channel is repeated on all other channels who are members of the patch. Each radio channel that is a member of a patch shall clearly display that they are in a patch and of which patch they are a member. This indication shall be shown on all consoles displaying that channel.

Dispatchers shall have the ability to add and delete individual radio channels to and from an active patch. They shall also have the ability to tear down the entire patch all at once. Dispatchers shall have the ability to become active members of the patch or remove themselves from the member list. Dispatchers shall have the ability to instant transmit on a group or individual within the patch by a single mouse click or touch.

The user interface shall provide a list of the patch members. The dispatcher shall be able to view the members in all system patches.

· Permanent groups - The console system shall allow a pre-defined group of radio channels to be established and saved permanently in the system. This group shall be represented on the user interface via a single visual element. Selecting and transmitting on the visual control operates the same as if the dispatcher had individually selected each channel.

· Dynamic groups - The console system shall allow a dispatcher to create a group of radio channels dynamically during their console session.

· Priority/Channel Marker - The system shall allow a priority marker to be placed on all analog channels in the system as desired on a channel-by-channel basis. The frequency, duration, interval, and amplitude of the priority marker shall be adjustable in software.

2.6 Paging Control

2.6.1 Instant Call Page

The system shall provide the ability to initiate a paging alert through activation of a single action. Instant calls may be pre-programmed with one or more pages with differing formats.

2.6.2 Page Steering

Instant call pages may be programmed to go out on pre-defined channels or programmed to go out on the selected channel(s).

2.6.3 Page Transmission

The console shall provide both audible and visual cues of the progress of the paging process. The dispatcher shall have the ability to stop the page transmission after initiation. There shall be an indication to the dispatcher if a page was transmitted successfully or not.

The system shall support the ability to simultaneously send different pages on multiple channels.

2.7 General Controls & System Functions

2.7.1 Volume – individual / master

The user interface shall have increase/decrease volume controls that are adjustable by the dispatcher. There shall be controls to change the volume level on each individual channel independently from one another and controls to change volume level on all channels routed to a particular speaker.

2.7.2 Volume Boost

The user interface shall allow the dispatcher to boost the volume to a pre-defined level for each channel independently and for any speaker. A visual indication shall appear when that item is placed into the boosted state.

2.7.3 Mute

The user interface shall allow the dispatcher to mute the volume to a pre-defined level for each channel independently and for any speaker. However, muting of the selected channel(s) shall not be allowed.

A visual indication shall appear when that item is placed into the muted state.

2.7.4 All Mute

The user interface shall allow the dispatcher to mute all monitored channels (anything not selected) simultaneously to a pre-defined level. There shall be an indication on the screen that channels are in a muted state. The all-mute function may be removed either by the dispatcher invoking the action or via a timer. The timer length shall be adjustable by a technician or administrator.

2.7.5 Console Voice Intercom

The system shall allow a console dispatcher to talk directly to one or more dispatchers within the console system. The user interface shall allow the dispatcher to select the destination console(s) from a list of logged in users.

2.7.6 Console Text Messaging

The system shall allow a console dispatcher to communicate with one or more dispatchers within the console system via freeform text messaging.

The user interface shall provide an indication that the dispatcher has an incoming and/or unread text message. In order to not disrupt the dispatcher from their current tasks, the dispatcher shall have the ability to read that message when desired versus immediately upon receipt.

For outgoing text messages, the user interface shall allow the dispatcher to select the destination console(s) from a list of logged in users or modify the destination console(s) when replying.

2.7.7 Call History

The system shall provide a history of all radio transmissions, incoming and outgoing, for each channel displayed on the screen regardless of its selected state. The dispatcher shall be able to perform an instant transmit to a caller from the activity entry. The following information shall be displayed for each transmission: time, Mobile ID or contact alias (when available), and status. The dispatcher shall have access to the transmission recording from the activity history. The dispatcher shall be able to sort by various type of calls and channels of the call. History shall allow saving for up to 24 hours.

2.7.8 Event Replay

The system shall provide short-term recording/instant playback functionality for transmissions. The dispatcher shall have access to the individual transmission playback via the history window. The system shall also support the ability to playback recordings on a particular channel in succession without needing the dispatcher to individually initiate the playback of each recording. Event replay shall allow saving for up to 24 hours.

2.7.9 Parallel Status

The status of any system resource (e.g. Radio, Phone, Aux I/O) shall be indicated at all consoles where the resource is displayed.

The user interface shall display visual indication on a radio channel of transmissions from other dispatchers on the console system.

2.7.10 Console Cross Mute

The system shall provide a means of muting the transmit audio from one or more other consoles within the system on a console that is monitoring the channel on which the transmission occurred.

2.7.11 Channel Cross Mute

The system shall provide a means of muting incoming audio (both transmit monitor and receive) on one or more channels when the system is transmitting on a given channel and frequency.

2.8 Contact-Based Dispatching

In addition to supporting traditional resource-based dispatching (where the dispatcher focus is on the gateway radios), the console shall also support contact-based dispatching that allows a dispatcher to instead focus on whom they wish to speak to, rather than the radio network, channel or media needed to contact the person or group. In support of this the console shall be capable of presenting icons for field units (both individual field users, as well as groups of field users) and those icons shall indicate the presence of traffic associated with the field unit (including talker ID and alias) and those icons shall allow the dispatcher to initiate transmissions to the field unit. This is desired in order to avoid the necessity of training dispatchers on the details of each radio network interfaced to their console.

3. Radio Gateway Interfaces Requirements Offeror shall provide Radio Gateway Interface boxes and radio interface cables for the Stand-alone Dispatch Console system. The Radio Gateway Interface boxes shall facilitate interfacing non-VoIP radios to an Ethernet network for audio transport and remote control. The Radio Gateway Interface should be a full-featured VoIP Base Station controller. The Radio Gateway Interface converts audio coming from the phone or radio to packet voice and sends it to the console. In reverse, it takes packet voice from the console and converts it to analog audio, and sends it to the phone or radio. The Radio Gateway Interface boxes shall meet one or more of the following requirements:

3. Local/E&M control The consoles, using a radio gateway, shall be capable of controlling radios using local and E&M methods compliant with TIA.102-BAHA Fixed Station Interface Messages & Procedures, Section 7.1. To support this, the console system shall provide, on a channel-by-channel basis, a “normally open” output capable of being wired in support of an E&M “M-lead”. In addition, console circuits that use E&M control shall also support the use of an optically isolated incoming receive indication signal, which can be wired in support of an E&M “E-lead”.

3.1 JVCKenwood Mobile Radio Interface

The consoles, using a radio gateway, shall be capable of controlling the following JVCKenwood mobile radios for specific interface needs: TK-x180 for analog/conventional systems, TK-5x10 for P25 CAI conventional and trunking systems, and NX-700/800/900 for NEXEDGE® systems, and NX-5x00 for P25 and NEXEDGE® systems and VM-5x00 for P25 systems. The following functions shall be available through the console interface: channel/talkgroup select, group call, individual call, emergency call, PTT-ID, scan, and receipt of status messages.

3.2 Motorola Mobile Radio Interface

The consoles, using a radio gateway, shall be capable of controlling the following Motorola mobile radios for specific interface needs: XTL-5000, XTL-2500, APX-7500 and APX-6000 supporting Analog FM (with MDC or DTMF signaling), P25 trunked and conventional, and SmartNet/SmartZone trunking modes. The following functions shall be available through the console interface: channel/talkgroup select, group call, individual call, emergency call, PTT-ID, scan, and coded/clear.

3.3 Harris Radio Interface

The consoles, using a radio gateway, shall be capable of controlling the Harris M7300, XG75 and XG100 radios via Controller Area Network (CAN) Bus translation for specific interface needs: for analog/conventional systems, for P25 Common Air Interface (CAI) conventional and trunking systems, and for Enhanced Digital Access Communications Systems (EDACS) and EDACS Pro-Voice Systems. The following functions shall be available through the console interface: channel/talkgroup select, group call, individual call, emergency call, PTT‐ID, scan, and receipt of status messages.

3.4 DMR Application Interface Specification (AIS)

· The consoles, using a radio gateway, shall be capable of interfacing to and controlling the following Digital Mobile Radio (DMR) systems using the open DMR Association, Application Interface Specification (AIS) interface:

1. DMR Tier III (Trunking)

2. DMR Tier II (Conventional)

· The following functions shall be available through the console interface: all call (conventional), broadcast call (trunking), call alert, channel select, emergency call, group call, individual call, PTT ID, radio check, radio inhibit, radio uninhibit.

4. Base Radios Requirements (VIKING VM5000 or approved equal) Offeror shall provide Radios for use by the Stand-alone Dispatch Console system connected via the radios gateways to meet SSC’s requirements as described above. The Radios shall meet, at a minimum, the following requirements:

· Mixed protocol operation (P25 Phase 1 & 2 Trunking, P25 Conventional, SN/SZ, FM Analog)

· 256 channels

· Mixed protocol zones

· P25 Authentication (Link Layer Authentication)

· P25 IP packet data

· GPS Automatic Vehicle Location (AVL) data (built in GPS)

· MDC-1200 & GE-Star signaling

· Analog & P25 Conventional vote scan

· Internal or external speaker

· Fixed control station

· Encryption P25/TIA defined: AES-256

· Radio must be capable of control and interfacing to gateway via an accessory jack

· Compatible with VK5000 or Motorola KVL3000/KVL4000 Keyloader

5. Implementation Requirements

The system shall be proposed as a complete system with final prices for all of the equipment listed in Appendix A, and software and services required by these specifications. The new system shall be installed to minimize the impact to operations of the current radio system and dispatch operations. The implementation will be proposed in the following phases:

· Phase 1: Site Visits, Kickoff Meetings to inspect installation sites (Equipment area, and Dispatch console area). Vendor Design and site meeting for Authority to Proceed (ATP).

· Phase 2: Shipment to SSC Logistics for receipt and processing for the SSC NASA Property Control System. (tagged)

· Phase 3: Schedule and install dispatch console equipment and subsystem at designated locations. Test network connectivity to check out console interface in accordance with acceptance test plan.

· Phase 4: Perform operational readiness review including documentation and training.

· Phase 5: Final Acceptance Testing.

The Offeror shall provide an implementation plan in accordance with the phased plan defined above.

5.1 Installation Plan

The Offeror shall provide details on the planned installation, schedule, operational training, and procedures to ensure that equipment is installed in a logical sequence and in a workmanship like manner. All work will be complete within 60 days.

SSC will provide:

· Communications rooms for Radios and gateways

· Rooms for Operator position

· All associated power and AC for equipment

· All grounding terminals

· All interconnecting fiber Optic cable between buildings and inter building network cable

· Equipment racks

· All cable pathways (i.e. wall penetration, conduit and or cable trays)

· Personnel access to SSC base on vendor information

· NASA will be responsible for disabling current console equipment

· NASA will coordinate all NASA Radio Frequency Licenses

5.2 Acceptance Test Plan

The Offeror shall provide and execute the Acceptance test plan with NASA personnel and contract staff at SSC. Acceptance testing will comprise, at a minimum, Operational Performance and system compatibility testing.

Final Acceptance of the Systems is considered complete when all deliverable products have been successfully received, installed, tested, and all open issues/discrepancies resolved and the System has been fully operational for a minimum of thirty (30) contiguous days. At such time, the Offeror shall provide a letter of Final Acceptance, which must be approved by SSC.

5.3 Training

The Offeror shall provide a description of the proposed training on the operation, maintenance and administration of all equipment provided with the system. As a minimum, the Offeror shall provide training with all training materials provided by the Offeror for a minimum of two radio technicians and five dispatch console operators.

5.4 Quality

Proposed equipment shall meet or exceed industry standards for quality and reliability. All materials, parts, assemblies, etc. shall be new, and be free of corrosion, blemishes or other cosmetic defects. Design and construction shall be consistent with current best engineering practices.

5.5 Certification and Regulatory Approvals

The equipment provider shall be ISO 9000 certified and shall comply with the applicable US Federal Communications Commission (FCC) rules and regulations for telecommunications equipment.

All equipment proposed in which microprocessors are used shall have undergone comprehensive testing and shall meet 47 Code of Federal Regulations (CFR), Part 15, Subpart “B” of the FCC rules for Class “A” computing devices. All microprocessors must comply with IPV6 requirements.

5.6 RESTRICTION ON FUNDING ACTIVITY WITH CHINA-REPRESENTATION

(a) Definition – “China or Chinese-owned” means the People’s Republic of China, any company owned by the People’s Republic of China or any company incorporated under the laws of the People’s Republic of China.

(b) Public Laws 112-10, Section 1340(a) and 112-55, Section 539, restrict NASA from contracting to participate, collaborate, coordinate bilaterally in any way with China or a Chinese-owned company using funds appropriated on or after April 25, 2011. Contracts for commercial and non-developmental items are exempted from the prohibition because they constitute purchase of goods and services that would not involve participation, collaboration or coordination between the parties

(c) Representation. By submission of its offer, the Offeror represents that the Offeror is not China or a Chinese-owned company

5.7 System documentation

The Offeror shall provide complete operational, technical manuals and maintenance documentation. In addition to user and technical manuals, the Offeror shall a complete system configuration drawing.

A copy of the system documentation shall be provided in electronic format via applicable storage medium.

6. Operation and Maintenance Requirements

6.1 Replacement Part Availability

The manufacturer of the proposed console equipment shall prepare a comprehensive spares listing for delivery with the system and maintain a stock of critical repair components for the system capable of supporting the system for a period of not less than five (5) years after initial delivery. Stocked critical parts shall be available for shipment on an expedited basis.

6.2 System Maintenance

· The console system shall provide a general indication on the dispatch console screen of the health of the IP network on which it resides and allow for a technician to access additional log information to assist in troubleshooting IP network performance issues.

· There shall be a centralized method of device discovery and provisioning of device IP network addresses, and all associated parameters for that device, such that it eliminates the need to access each device separately.

· All primary settings and adjustments on the backroom equipment shall be accomplished via software control.

· It shall be possible to configure the console system from anywhere on the network on which it resides. A technician shall not be required to physically connect to a device in order to perform configuration and maintenance tasks.

6.3 Warranty

Offeror shall warrant all equipment to be free from defects in material and workmanship, and to operate in accordance with these specifications. Software shall have a warranty for a period of not less than one (1) year from date of acceptance, if within three months from the date of shipment. Hardware will have a warranty for a period of not less than three (3) years from the date of acceptance, if within three months from the date of shipment.

Hardware replacement for the first ninety (90) days will be handled by advance shipment of hardware (replacement hardware will be shipped as soon as an agreement is reached that it is faulty).

The Offeror shall provide extended warranty and software subscription service information and cost.

7. APPENDIX A – Equipment List

(14 each) Mobile radio for 700 MHz, P25 Trunking, Phase 2 (TDMA) capabilities (24 each) Switching power supply for each radio Rack hardware for all radios and radio power supplies (8 each (“dual radio input” network gateway devices) MSWIN Compatible Radio to network gateway devices w/ license (13 each) Compatible gateway interface cables (min 10’) for quoted 700 MHz radio (4 each (“dual radio input” network gateway devices) Motorola 400 MHz Radio to network gateway devices w/ license (1 each) (“dual Audio input” network gateway device) 4-wire audio to network gateway device w/ license (8 each) Compatible interface cables (min 10’) for existing SSC Motorola XTL5000 / APX 7500 400 MHz radios (2 each) Network based dispatch radio console (software & hardware) to interface to the radio & audio gateway devices listed above.

To include:

· All power supplies required for console equipment

· Block of 30 channel license shared between 2 console operator positions

· Microphones

· Speakers

· Footswitches

· Headset options

· Network manager server (if required)

· Computer hardware

· Computer LCD/LED Monitor (Min 24” wide screen)

· Wireless headset (1 each) Network manager server (if required) (1 each) 24 port managed gigabit rack mounted network switch (2 each) 100 – 1000 MHz Multi-Band Short Haul Combiner, 16 channels (1 each) 746-869 MHz 3db fiberglass omni directional antenna (1 each) 380-420 MHz 3db omni directional antenna Minimum of 200’ LMR coax cable All RF connecters required for LMR400 coax All network (Cat 6) cables required All power cables required All interconnection cables required Installation Labor System Admin Training Console user training

8. APPENDIX B – Acronyms

Acronym Definition

SECTION 2

INSTRUCTION TO OFFERORS

☒52.212-1 Instructions to Offerors – Commercial Items (Jan 2017) Addendum to 52.212-1

Quotes for the item(s) described in the RFQ are due by 8/10/2018 by 3 p.m. CT to Michael Luhning at Michael.j.luhning@nasa.gov in order to be considered for award. If it is in the best interest of the Government, quotes submitted after the due date may be accepted. Quotes shall remain valid for 30 days unless otherwise expressly stated on the quote. Submitted Quotes shall list two points of contacts including name, phone number, and email address.

All contractual and technical questions must be in writing (e-mail) to Michael Luhning at Michael.j.luhning@nasa.gov no later than 7/16/2018 by 12 p.m. CT. Telephone questions shall not be accepted.

The NAICS Code for this procurement is 334220.

This procurement is set aside for small business.

Offeror’s shall be registered at www.sam.gov in order to be considered for award.

Delivery is FOB Destination.

SECTION 3

SOLICITATION PROVISION/REPRESENTATIONS AND CERTIFICATIONS

☒52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this/these address(es):

FAR http://farsite.hill.af.mil/vffara.htm NFS http://farsite.hill.af.mil/vfnasaa.HTM

FEDERAL ACQUISITIONI REGULATION (FAR) PROVISIONS INCORPORATED BY REFERENCE:

FAR PROVISISIONS IN FULL TEXT:

☒52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS—COMMERCIAL ITEMS (NOV 2017)

The offeror shall complete only paragraphs (b) of this provision if the Offeror has completed the annual representations and certification electronically via the System for Award Management (SAM) Web site located at http://www.sam.gov/portal. If the Offeror has not completed the annual representations and certifications electronically, the Offeror shall complete only paragraphs (c) through (u) of this provision.

(a) Definitions. As used in this provision-- “Economically disadvantaged women-owned small business (EDWOSB) concern” means a small business concern that is at least 51 percent directly and unconditionally owned by, and the management and daily business operations of which are controlled by, one or more women who are citizens of the United States and who are economically disadvantaged in accordance with 13 CFR part 127. It automatically qualifies as a women-owned small business eligible under the WOSB Program.

“Forced or indentured child labor” means all work or service—

(6) Exacted from any person under the age of 18 under the menace of any penalty for its nonperformance and for which the worker does not offer himself voluntarily; or

(7) Performed by any person under the age of 18 pursuant to a contract the enforcement of which can be accomplished by process or penalties.

“Highest-level owner” means the entity that owns or controls an immediate owner of the offeror, or that owns or controls one or more entities that control an immediate owner of the offeror. No entity owns or exercises control of the highest level owner.

“Immediate owner” means an entity, other than the offeror, that has direct control of the offeror. Indicators of control include, but are not limited to, one or more of the following: Ownership or interlocking management, identity of interests among family members, shared facilities and equipment, and the common use of employees.

“Inverted domestic corporation,” means a foreign incorporated entity that meets the definition of an inverted domestic corporation under 6 U.S.C. 395(b), applied in accordance with the rules and definitions of 6 U.S.C. 395(c).

“Manufactured end product” means any end product in product and service codes (PSCs) 1000-9999, except—

(1) PSC 5510, Lumber and Related Basic Wood Materials;

(2) Product or Service Group (PSG) 87, Agricultural Supplies;

(3) PSG 88, Live Animals;

(4) PSG 89, Subsistence;

(5) PSC 9410, Crude Grades of Plant Materials;

(6) PSC 9430, Miscellaneous Crude Animal Products, Inedible;

(7) PSC 9440, Miscellaneous Crude Agricultural and Forestry Products;

(8) PSC 9610, Ores;

(9) PSC 9620, Minerals, Natural and Synthetic; and

(10) PSC 9630, Additive Metal Materials.

“Place of manufacture” means the place where an end product is assembled out of components, or otherwise made or processed from raw materials into the finished product that is to be provided to the Government. If a product is disassembled and reassembled, the place of reassembly is not the place of manufacture.

“Predecessor” means an entity that is replaced by a successor and includes any predecessors of the predecessor.

“Restricted business operations” means business operations in Sudan that include power production activities, mineral extraction activities, oil-related activities, or the production of military equipment, as those terms are defined in the Sudan Accountability and Divestment Act of 2007 (Pub. L. 110-174). Restricted business operations do not include business operations that the person (as that term is defined in Section 2 of the Sudan Accountability and Divestment Act of 2007) conducting the business can demonstrate—

(1) Are conducted under contract directly and exclusively with the regional government of southern Sudan;

(2) Are conducted pursuant to specific authorization from the Office of Foreign Assets Control in the Department of the Treasury, or are expressly exempted under Federal law from the requirement to be conducted under such authorization;

(3) Consist of providing goods or services to marginalized populations of Sudan;

(4) Consist of providing goods or services to an internationally recognized peacekeeping force or humanitarian organization;

(5) Consist of providing goods or services that are used only to promote health or education; or

(6) Have been voluntarily suspended.

Sensitive technology—

(1) Means hardware, software, telecommunications equipment, or any other technology that is to be used specifically—

(i) To restrict the free flow of unbiased information in Iran; or

(ii) To disrupt, monitor, or otherwise restrict speech of the people of Iran; and

(2) Does not include information or informational materials the export of which the President does not have the authority to regulate or prohibit pursuant to section 203(b)(3) of the International Emergency Economic Powers Act (50 U.S.C. 1702(b)(3)).

“Service-disabled veteran-owned small business concern”—

(1) Means a small business concern—

(i) Not less than 51 percent of which is owned by one or more service-disabled veterans or, in the case of any publicly owned business, not less than 51 percent of the stock of which is owned by one or more service-disabled veterans; and

(ii) The management and daily business operations of which are controlled by one or more service-disabled veterans or, in the case of a service-disabled veteran with permanent and severe disability, the spouse or permanent caregiver of such veteran.

(2) Service-disabled veteran means a veteran, as defined in 38 U.S.C. 101(2), with a disability that is service-connected, as defined in 38 U.S.C. 101(16).

“Small business concern” means a concern, including its affiliates, that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the criteria in 13 CFR Part 121 and size standards in this solicitation.

“Small disadvantaged business concern, consistent with 13 CFR 124.1002,” means a small business concern under the size standard applicable to the acquisition, that--

(1) Is at least 51 percent unconditionally and directly owned (as defined at 13 CFR 124.105) by--

(i) One or more socially disadvantaged (as defined at 13 CFR 124.103) and economically disadvantaged (as defined at 13 CFR 124.104) individuals who are citizens of the United States; and

(ii) Each individual claiming economic disadvantage has a net worth not exceeding $750,000 after taking into account the applicable exclusions set forth at 13 CFR 124.104(c)(2); and

(2) The management and daily business operations of which are controlled (as defined at 13.CFR 124.106) by individuals, who meet the criteria in paragraphs (1)(i) and (ii) of this definition.

“Subsidiary” means an entity in which more than 50 percent of the entity is owned—

(1) Directly by a parent corporation; or

(2) Through another subsidiary of a parent corporation.

“Successor” means an entity that has replaced a predecessor by acquiring the assets and carrying out the affairs of the predecessor under a new name (often through acquisition or merger). The term “successor” does not include new offices/divisions of the same company or a company that only changes its name. The extent of the responsibility of the successor for the liabilities of the predecessor may vary, depending on State law and specific circumstances.

“Veteran-owned small business concern” means a small business concern—

(1) Not less than 51 percent of which is owned by one or more veterans(as defined at 38 U.S.C. 101(2)) or, in the case of any publicly owned business, not less than 51 percent of the stock of which is owned by one or more veterans; and

(2) The management and daily business operations of which are controlled by one or more veterans.

“Women-owned business concern” means a concern which is at least 51 percent owned by one or more women; or in the case of any publicly owned business, at least 51 percent of the its stock is owned by one or more women; and whose management and daily business operations are controlled by one or more women.

“Women-owned small business concern” means a small business concern --

(1) That is at least 51 percent owned by one or more women or, in the case of any publicly owned…