SOW Compunetix FY24 Draft.docx

ATLANTIC TEST RANGE TEST COMMUNICATIONS BRANCH MISSION VOICE PLATFORM (MVP) SYSTEM HARDWARE AND SOFTWARE ENGINEERING SUPPORT STATEMENT OF WORK

1. BACKGROUND

1.1. Test Communications equipment running Mission Voice Platform (MVP) software, proprietary to Compunetix, is used by the Atlantic Test Range (ATR) at Naval Air Station (NAS) Patuxent River, MD to support real-time voice processing, display, and recording capabilities. Specific systems of interest with respect to this SOW are:

• Mobile systems that deploy outside of ATR’s typical footprint in order to accommodate complete test teams in a mobile environment. Mobile systems can range from 2 to 40 end units required to provide real-time voice as a safety of flight requirement. Furthermore, these mobile systems can be deployed for various lengths of time, and can be required to be standalone systems or connected remotely to get voice back to ATR real-time.

• Remote systems that will require remote control capabilities and connection back to ATR. These remote systems may consist of end unit and/or radio control as a requirement to extend ATR’s footprint permanently, or for single-use purposes.

• Facilities with increase security requirements force ATR to accommodate various programs with specific voice communications that must be isolated from normal operations. These missions are deemed above the collateral secret level of security that is currently used at ATR. As a result, separate facilities must be stood up to accommodate the increased security levels. These facilities will are required to be connected back to the unclassified side of ATR’s voice core to get voice back to ATR in real-time. Additionally, the secure facilities will require an additional core to accommodate a program specific level of classification that is separate from any of ATR’s other voice communications. These two core within the secure facility must connect to each other and share end units so the end users can conduct missions seamlessly without having to switch between two systems.

2. SCOPE

The ATR Range Safety Officer (RSO) requires real-time voice communications to be in place for all live flight tests as a go/no-go requirement. Different test programs demand unique subsets for requirements for internal and air vehicle communications. MVP software must be extremely flexible and able to update to meet new requirements for ATR. Over the next five years, ATR expects to outfit multiple mobile systems, remote systems, and secure facilities with MVP systems in order to meet the ever changing demands from projects.

3. TECHNICAL REQUIREMENTS

3.1. Primary Products.

3.1.1. Core Components –

- 14-Slot with media redundancy – MVP core chassis capable of supporting 2 hub blades and 12 media blades.

- 6-Slot with media redundancy – MVP core chassis capable of supporting 2 hub blades and 4 media blades.

- 2-Slot with media redundancy – MVP core chassis capable of supporting 2 hub/media blades.

- Carrier Modules – MVP blade capable of supporting media and/or hub responsibilities within the core. Upon installation, Carrier Modules will be comprised of varying combinations of internet protocol (IP) rear transmit modules (RTMs), T1 RTMs, DSP modules, and APMs.

3.1.2. End Units

- Digital Analog Processor (DAP) / Secure DAP (SDAP) – Black only and Red/Black processing hardware that is required to connect any user mission instrument back to the MVP core via IP or T1 connections.

- Mission Console (MC) – 3 rack unit (3RU) MC-3RU/MC-3RUII – Black only and Red/Black rack mountable 3RU user mission instrument connected back to MVP core(s) for real-time conference audio. Must be capable of supporting dual push to switch (PTS) LEMO headsets with built in DAP/SDAP.

- MC-2RU/MC-2MUII – Black only and Red/Black rack mountable 2RU user mission instrument connected back to MVP core(s) for real-time conference audio. Must be capable of supporting dual push to switch (PTS) LEMO headsets with built in DAP/SDAP.

- MC-D8 – Black only desktop user mission instrument connected back to MVP core(s) for real-time conference audio. Must be capable of supporting dual push to switch (PTS) LEMO headsets. Must be capable of supporting dual push to switch (PTS) LEMO headsets, and each will require separate DAP/SDAP.

- MC-D10/MC-D10II/MC-D15/MC-D15II – Black only and Red/Black 10” and 15” mission instrument connected back to MVP core(s) for real-time conference audio. Must be capable of supporting dual push to switch (PTS) LEMO headsets, and each will require separate DAP/SDAP.

3.1.3. Data Transport

- 4 Channel Session IP (SIP) to analog router (STAR) 4-STAR – Data transport hardware capable of converting connection types to and from IP and analog. Hardware is used for extending various voice and data components to get all information back to the MVP core.

- Encryption over IP (KYoIP) - Data transport hardware capable of converting cypher text encryption data to and from IP. Hardware is used to extending encrypted voice and data components to get all information back to the MVP core.

3.2. End Unit Functionality The Contractor shall support the current release of the MVP suite software and hardware components. End units are responsible for displaying various options for users to manipulate desire voice traffic. At a minimum, this capability shall include the following functionality:

3.2.1. All end units must be compatible with MVP core software in order to communicate with ATR’s voice switch backbone.

3.2.2. End units must display at least 50 channels, all of which can be configured individually to modify volume, gain, controls, and naming schemes.

3.2.3. End units must accept LEMO connectors for headset bases. Additionally, dual push-to-talk headset bases must be supported.

3.2.4. End units must be capable of red and black audio, including necessary TEMPEST certifications.

3.2.5. End units must be compatible with analog jack boxes, and will accommodate a minimum of 4 headsets.

3.3. Voice Switch Core Functionality Leveraging functions described in Section 4.1, the Contractor shall enhance the current release of the MVP suite with the capability to identify expansion requirements. At a minimum, voice switch core components capabilities shall include the following:

3.3.1. Must be compatible with MVP software in order to expand the current hardware capacity. 3.3.2. Must be fully redundant with the ability to automatically switch over when necessary. 3.3.3. Must have the ability to be hot-swapped during real-time missions without any impact to the test events.

3.3.4. Accept various inputs including: T1 and IP.

4. OTHER REQUIREMENTS

4.1. Technical Interchanges. The Contractor shall conduct Technical Interchange Meetings (TIMs) as required to support development and testing efforts. TIMs will be conducted on an as-needed basis, as agreed upon by the Contractor and the Government, to discuss issues concerning requirements, standards, design alternatives, software, or other topics of importance. These meetings will be conducted at the Contractors site and at times via Telephone Conferences or Web Conferencing.

4.2. Project Status Reporting (A001). The Contractor shall provide a Periodic Status Report (PSR) when addressing issues, concerns, problems, improvements, and upgrades as necessary. The PSR shall be in any format acceptable to the contractor as long as the necessary issues, concerns, problems, improvements, and/or upgrades are addressed appropriately. The PSR shall address performance, schedule, and cost by providing an accumulative project summary of accomplishments, tasks accomplishments for the month along with hours expended, tasks planned for the upcoming month along with a projection of hours to be expended, and a forecast relative to the completion of the work or significant portions thereof identified in this SOW. These PSRs will vary based on priority and importance as a direct result of project impact.

4.3. Testing and Test Documentation. It is planned that the Government will witness/review Contractor testing conducted throughout the development cycle and at various locations. The Government expects that multiple levels of test and integration will be conducted throughout the performance of the work described in this SOW.

4.3.1. Contractor Development Testing The Contractor shall, upon request by the Government, provide opportunity for the Government to observe ongoing development tests, and/or conduct a demonstration either at the Contractor’s facility, or on base.

4.3.2. Site Acceptance/Demonstration Testing of Deliveries When delivering hardware and/or software, the Contractor shall provide support at ATR for Acceptance Tests / Demonstrations for the Government, if requested. The tests shall be conducted by installing the deliverable(s) and then proving the current MVP system is operating in a functional manner with the added capabilities of the new hardware and/or software purchased.

4.3.3. Government-Led MVP Integration Testing The Contractor shall provide support on base for additional MVP system level integration testing to be performed by Government.

4.4. Deliveries

4.4.1. Deliverables will be specified at the delivery order level.

4.4.2 Partial Deliveries In order to support ongoing Government component and MVP test and integration, the Government may request partial deliveries (e.g. individual functions or groups of functions among those described in Section 3 above). Upon request of the Government POC (See Section 7), the Contractor shall coordinate with the Government to make partial delivery in a manner, and at a time mutually agreed upon between the Contractor and the Government. If requested, the Contractor shall support on base installation, integration and acceptance/demonstration testing.

4.4.3. Software User Documentation For each accepted Software upgrade delivery, the Contractor shall deliver software user documentation to call out updates from previous versions of the existing MVP Software User Manual to describe at a level of detail consistent with the existing documentation the functionality added via this SOW. Additionally, the Contractor shall also update online documentation within the MVP Client configuration (e.g. help menus) to describe the functionality added via this SOW.

5. GOVERNMENT FURNISHED ITEMS Software tools and reference applications are available for use if required by the Contractor from https://www.tena-sda.org/display/INET/Home, or via request to the Government POC. These tools are offered in good faith, “as is”, to support interoperability; however, the Government makes no claims or guarantees relative to the use of the tools.