RFI.docx

REQUEST FOR INFORMATION

The Defense Information Systems Agency (DISA) / Program Executive Office (PEO) Services Enterprise Collaboration Services (SD3) is seeking information from industry to assist with the development and planning of a potential new requirement for Video Teleconferencing (VTC) Integration into Department of Defense (DoD) secure internet protocol router (SIPR) Microsoft Teams.

THIS IS A REQUEST FOR INFORMATION (RFI) NOTICE ONLY. THIS IS NOT A REQUEST FOR PROPOSALS (RFP). NO SOLICITATION IS AVAILABLE AT THIS TIME.

1. Overview/Purpose/ Description of Procurement

The purpose of this RFI is to identify a hardware and/or software solution that will integrate traditional video meeting rooms and VTC devices to Microsoft Teams on a secure internet protocol router network (SIPRNet).

2. Technical Characteristics

The VTC bridging hardware and/or software needs to effectively connect Microsoft Teams and various video conferencing platforms, e.g., smartphones, tablets, desktops, laptops, room-based systems. The following technical characteristics need to be considered in vendor responses:

a. Interoperability:

i. Protocol Support: Ability to handle multiple communication protocols (e.g., SIP, H.323, WebRTC, G.722, G. 711) and other latest audio and video protocols.

ii. Cross-Platform Integration: Compatibility with various video conferencing systems and platforms (e.g., Pexip, Enghouse, Cisco, Poly, and HP).

b. Scalability:

i. User Capacity: Support for 1000 simultaneous users and conference rooms per session.

ii. Bandwidth Management: Efficient handling of bandwidth to support multiple connections without degradation of video and audio quality.

c. Video and Audio Quality:

i. Resolution and Frame Rate: Support for high-definition video (up to 4K) and high frame rates (30fps, 60fps).

ii. Audio Quality: Support for high-fidelity audio, noise cancellation, and echo reduction.

d. Security:

i. Encryption: End-to-end encryption for video and audio streams to ensure secure communication.

ii. Authentication and Authorization: Integration with single sign-on (SSO), PKI certifications, and other authentication mechanisms to control access.

iii. Data Protection: Compliance with data protection regulations such as GDPR, HIPAA.

e. User Interface and Experience:

i. Ease of Use: Intuitive interface for scheduling, joining, and managing conferences.

ii. Admin Controls: Administrative features for managing users, permissions, and settings.

iii. Customization: Ability to customize the user experience, including branding and layout.

f. Integration Capabilities:

i. Application Programming Interfaces (APIs) and Software Development Kits (SDKs): Availability of APIs and SDKs for integration with other software and systems.

ii. Calendar Integration: Integration with calendar systems (e.g., Microsoft Outlook, Google Calendar) for easy scheduling.

g. Monitoring and Reporting:

i. Analytics: Tools for monitoring usage statistics, performance metrics, and quality of service.

ii. Reporting: Generation of detailed reports on (e.g., conference activity, user engagement, and system performance).

h. Support and Maintenance:

i. Technical Support: Availability of support services for troubleshooting and resolving issues.

ii. Updates and Upgrades: Regular updates and patches to ensure compatibility and security.

i. Customization and Flexibility:

i. Configuration Options: Flexible configuration options to tailor the bridging solution to specific needs.

ii. Deployment Models: Options for cloud-based, on-premises, or hybrid deployment.

j. Redundancy and Reliability:

i. Failover Mechanisms: Built-in redundancy and failover support to ensure continuous operation.

ii. Service Level Agreements (SLAs): Guarantees for uptime and reliability.

3. Scope of Effort

The vendor shall identify VTC bridging capability that integrates VTC endpoints into the Microsoft Teams provided on the SIPRNet. DISA is requesting a white paper that provides a hardware and/or software solution. Responses should consider the following and fully address the items below.

a. Requirements Gathering and Analysis:

i. Functional Requirements: Provide what features the VTC hardware/software can support (e.g., gatekeeper functions, telephonic protocols interoperability resolution, end point management, call routing).

ii. Compliance Requirements: Hardware and/or software must meet all relevant security and regulatory standards, such as Federal Information Security Management Act, National Institute of Standards and Technology, or other DoD specific guidelines.

b. Compliance and Security:

i. Security Requirements: The VTC bridging hardware and/or software must meet stringent security protocols necessary for defense operations. This includes encryption standards (e.g., AES-256), secure authentication methods, and compliance with regulations such as FIPS 140-2.

ii. Joint Interoperability Test Command (JITC) Approved Product List (APL) Certification: Certifications would be optional depending on the product recommendation. If the product is hardware based and requires certification, then the product must be evaluated by the DoD Joint Interoperability Test command and listed on the APL, with a Military Unique Deployment Guide.

c. Integration Capabilities:

i. Compatibility: VTC bridging capability that can integrate with the Microsoft Teams.

ii. Interoperability: Ensure the hardware and/or software supports interoperability with existing VTC systems, Voice Over Secure Internet Protocol (VOSIP) devices, and mobility devices within the defense enterprise.

d. Functional Requirements:

i. Feature Set: Evaluate the VTC bridging hardware and/or software’s features, such as high-definition video, reliable audio quality, screen sharing, recording capabilities, and meeting scheduling. Provide a bridging hardware and/or software recommendation based on the feature set.

ii. Use Cases: Provide use cases of each products interface, configurations, and data flows.

iii. Scalability: The hardware and/or software should handle varying scales of operations, from small team meetings to large-scale conferences.

e. User Experience and Accessibility:

i. Ease of Use: The hardware and/or software should be intuitive and easy for users across different levels of technical expertise.

ii. Accessibility Features: Ensure that the hardware and/or software includes accessibility features to support all users, including those with disabilities as specified in Section 508 of the Rehabilitation Act of 1973.

f. Support and Maintenance:

i. Vendor Support: Identify the availability of vendor support, including technical assistance, training, and regular updates.

ii. Maintenance: Evaluate the hardware or software's update cycle and determine how it fits with examples of maintenance schedules.

g. Cost and Licensing:

i. Cost Structure: Provide the cost structure via a Rough Order of Magnitude of the VTC bridging hardware and/or software, including licensing fees, subscription models, and any additional costs for extra features or support.

h. User and Deployment Considerations:

i. Deployment: Assess the ability to deploy and integrate into the existing Microsoft Teams environment on SIPRNet

ii. Training: Identify the training requirements for users and administrators to effectively utilize the VTC bridging software.

i. Feedback and Performance Metrics:

i. User Feedback: VTC bridging software user documented experience with video, audio, and presentation quality.

ii. Performance Metrics: Review performance metrics related to system uptime, latency, and user satisfaction.

j. Future Proofing:

i. Upgradability: Ensure the hardware and/or software is adaptable to future upgrades in technology and can integrate with evolving components of Microsoft Teams and other DoD hardware, software, and network components.

ii. Innovation: Provide upcoming industry technological trends of secure video teleconferencing capabilities. For example, what will be the vendors short term (1-2 years) innovation road map look like to enhance the user interface and user experience? What type of actions, e.g., redesign of the user interface to be more intuitive, focusing on ease for all VTC participants? Will there be Artificial Intelligence features to include language translations, and automated meeting summaries?

4. Requested Information

The vendor will provide a white paper that will outline the assessment of the VTC products capabilities, suitability, and compatibility and address each item under Section 3: Scope of Effort while ensuring the response is compatible and compliant with Section 2: Technical Characteristics.

RESPONSE GUIDELINES:

Interested parties are requested to respond to this RFI with a white paper. Submissions cannot exceed 10 pages, single spaced, 12-point type with at least one-inch margins on 8 1/2” X 11” page size. The response should not exceed a 5 MB e-mail limit for all items associated with the RFI response. Responses must specifically describe the contractor’s ideal solution to meet the requirements outlined in this RFI. Oral communications are not permissible.

Companies who wish to respond to this RFI should send responses via email no later than 10:00AM Eastern Standard Time (EST) on October 17, 2024.

INDUSTRY DISCUSSIONS:

DISA representatives may choose to meet with potential offerors and hold one-on-one discussions. Such discussions would only be intended to obtain further clarification of potential capability to meet the requirements, including any development and certification risks.

QUESTIONS:

Questions regarding this announcement shall be submitted in writing by e-mail to michelle.l.rand.civ@mail.mil and michael.e.pirone.civ@mail.mil no later than 4PM EST on October 3, 2024. Verbal questions will NOT be accepted. Answers to questions will be posted to the System for Award Management. The Government does not guarantee that questions received after the close of business on October 3, 2024, will be answered. The Government will not reimburse companies for any costs associated with the submissions of their responses.

DISCLAIMER:

This RFI is not a RFP and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Responses will not be considered as proposals, nor will any award be made as a result of this synopsis.

All information contained in the RFI is preliminary as well as subject to modification and is in no way binding on the Government. FAR clause 52.215-3, “Request for Information or Solicitation for Planning Purposes”, is incorporated by reference in this RFI. The Government does not intend to pay for information received in response to this RFI. Responders to this invitation are solely responsible for all expenses associated with responding to this RFI. This RFI will be the basis for collecting information on capabilities available. This RFI is issued solely for information and planning purposes. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed. In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract.