DSU/DSAN Replacement

CAC2S Request for Information (RFI) TOPIC: CAC2S Voice Network Solutions This Request for Information (RFI) briefly describes the current Common Aviation Command and Control System (CAC2S) program/acquisition approach, identifies key events in the acquisition program schedule, and requests information to assess industry's capability to provide a materiel solution that will meet portions of the current CAC2S voice network requirements. The information provided in this RFI is notional and may change. The Government is under no obligation to revise any aspect of this RFI should any information provided herein change. The Government will provide any additional information and issue any additional requests for information at its sole discretion via the Fedbizopps website only. Description: The CAC2S program is exploring potential hardware and software solutions to replace the aging voice network system to minimize increasing obsolescence issues. CAC2S is employing an evolutionary acquisition strategy utilizing an incremental (two increments) and phased (two phases defined within increment one) approach for development and fielding of the CAC2S. Limited Deployment Capability (LDC) was achieved 2nd Qtr FY12 with the fielding of the first Phase 1 CAC2S. Phase 1 is structured to accommodate rapid fielding of operationally relevant capabilities to include mobility, situational awareness, tactical communications, information dissemination and operational flexibility that will establish the baseline CAC2S capabilities for the Marine Air Command and Control System (MACCS) and improve overall Air Command and Control (AC2) performance and effectiveness. Phase 2 completion will result in the delivery of the full CAC2S Increment I capabilities where Full Deployment is currently planned to commence in 3rd Qtr FY16. Currently, CAC2S voice communications take place over the voice and radio Virtual Local Area Networks (VLANs) of a dedicated IP network that is logically and physically isolated from the CAC2S data network (and from the Secret Internet Protocol Router Network (SIPRNET)). The CAC2S voice network is a scalable, configurable Voice Over Internet Protocol (VoIP) communications system that can support a wide range of communications needs. Specifically, it must provide integrated intercom, radio, audio conferencing, and (optionally) plain old telephone service (POTS) communications to all users through a single user interface. The system must provide both VoIP soft-switch and radio interface capabilities. The voice network must also support remote monitoring and control of attached radio systems. Finally, the voice network must consist of workstations which provide user interfaces for joining or monitoring radio nets, controlling AN/PRC-117F, AN/PRC-117G, and AN/PRC-150 military radios, and initiating or answering intra-CAC2S intercom or conference calls. Refer to Annex A for a depiction of the current CAC2S configuration. The first sheet of Annex A is a physical architectural representation of the AN/MRQ-13 Communication System (CS) vehicle utilized in CAC2S. It basically consists of two 48 port Cisco 3560 network switches, 2 Digital Switching Units (DSU), Keyboard Video Mouse (KVM), and multiple Radio Terminals. The DSU's, along with DSAN/LongArm software, provide the push to talk (PTT) and RS 232 remote radio control capabilities. The second sheet of ANNEX A represents a basic CAC2S Operation Facility (OPFAC) architecture. Each table consists of a Universal Serial Bus Audio Adapter (UAA). The UAA provides the network interface for the Voice Terminal Workstations (Panasonic Toughbooks), Foot Switches, PTTs, and headsets. The tent switches are 48 port Cisco 3560Gs. Requested Information: Respondents are requested to provide information on the following capability statements: 1) Describe the number of operational users that can be supported at any given time. 2) Describe the number of operational radios that can be supported at any given time. 3) Describe covered and uncovered radio configurations. 4) Describe the approach taken regarding an Internal Communication System (ICS), along with the high level capabilities it will provide. 5) Describe the ability to provide secure and non-secure use of standard military telephone capabilities. 6) Describe the ability to monitor an ICS conversation while actively talking on a radio. 7) Describe the ability to monitor various radio nets while still actively talking on another net. 8) Describe how PTT and remote radio control is provided for military radios. Also provide a list of military radios in which the system supports these functions. 9) Describe the modularity and scalability of the system. 10) List the recommended hardware and software for the voice network solution. Along with the recommended hardware solution, provide the minimum hardware requirements. 11) Describe the system requirements necessary to maintain operation under high load (RAM, CPU, etc). 12) Describe the ability to perform given a large number of intercom or radio net participants. Indicate whether the system is capable of handling 206+ users and up to 48 radio nets. Identify known performance limitations based on existing test data. 13) Identify the recommended operating system(s) for the voice network solution. 14) Describe any known Diminishing Manufacturing Sources and Material Shortages issues with the voice network solution. 15) Describe system component Technology Readiness Levels and where the system is currently in use. 16) Describe all licensing requirements, if any, associated with the voice network solution. 17) Describe any Information Assurance (IA) accreditation that has been completed on the voice network solution. 18) Describe the ability to monitor a classified net while talking on an unclassified net. 19) Describe how your system impacts the current CAC2S network architecture (i.e. can it utilize current switches and existing Panasonic Toughbook workstations). 20) Describe the Open Architecture Assessment of the voice network solution. Responses: This RFI is for informational purposes only, and does not constitute a solicitation for proposals or otherwise obligate the Government to issue any solicitation for proposals. Pursuant to FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. Vendors/interested parties are solely responsible for all costs and expenses associated with their respective response to this RFI. The Government will not reimburse vendors/interested parties for any costs associated with their respective response to this RFI, including, but not limited to any cost associated with any submission or information provided to the Government. Response Format: Interested firms who believe they are capable of providing a voice network solution as described above are invited to express their interest by responding to the Requested Information in this RFI with a white paper in Microsoft Word for Office 2007-compatible format. RFI responses are limited to 40 pages, including cover and administrative pages, and shall be delivered using 10 point font or larger. The paper size shall be 8.5 x 11 for text and 11 x 17 for diagrams. Please be advised that any vendor proprietary information must be marked as such on a page-by-page basis. The Government will not assume that any of the information provided by a respondent is proprietary unless it is conspicuously marked on a page-by-page basis. Moreover, the Government does not assume any duty to contact a respondent and inquire whether any unmarked information submitted in response to this RFI is proprietary. Additionally, interested firms are requested to provide the following information in their RFI response: (a) company name, company address, overnight delivery address (if different from mailing address), cage code, point of contact, e-mail address, telephone number, fax number; and (b) indicate business size (i.e., large, foreign, small disadvantaged, veteran owned, minority owned, etc) to the Government representative listed below. Response Deadline and Submissions: Responses are requested no later than 08 March 2013 at 16:00 EDT. Responses shall ONLY be submitted on CD's via mail to Natasha Jones in accordance with the addresses below. Please be advised that any submissions received will not be returned. It should be noted that telephone replies will not be accepted. For FEDEX, UPS or similar deliveries, use the following address: Commander Marine Corps Systems Command Attn: Natasha Jones, PEO-LS AC2SN Material Management 2201 A Willis Street Quantico, VA 22134-6050 For US Postal Service use: Commander Marine Corps Systems Command Attn: Natasha Jones, PEO-LS AC2SN Material Management 2200 Lester Street Quantico, VA 22134-6050