Q_and_A.pdf

Questions and Answers

1. Question: Live radio streaming for no less than 25 local stations and seven network stations

Is there a special requirement you need? Is the question about capacity to be able to handle your global users?

Response:

Yes, the requirement refers to the capacity to handle global users, ensuring high reliability with 99.99% uptime for streaming services. Additionally, the system must support metadata integration, including low/no latency “Now Playing” data, and redundant streams with automatic failover capabilities. Geo-filtering and IP whitelisting are also critical to ensure secure content delivery to authorized users only.

Network station streams must be capable of having local station and/or geographically targeted spots inserted.

2. Question: On-Demand Audio

Can you clarify what you are looking for in this question? Are we talking about the ability to publish content as you do today such as podcasts? Or something else?

Response:

This refers to the ability to host and publish content for on-demand access, similar to podcast functionality. The solution should allow the AFN team to store, manage, and deliver audio content that can be replayed or downloaded by users on demand. This includes replays of live shows, curated playlists, and other supplemental audio content, integrated seamlessly into the app.

3. Question: User-Customizable Playlists

It is not clear if in this case user is the Publisher or the Listener. Can you please clarify? As an example, as a Publisher you can create the programing of a live stations using the Radio Automation System (RAS). The capability will depend on the RAS used.

Response:

In this case, the term “user” refers to listeners. The functionality should enable end users to create, customize, and save their own playlists based on their preferences. This could include selecting favorite songs, skipping tracks, and organizing playlists by genre, mood, or activity. Administrative playlist control is also relevant but addressed separately under content management requirements.

4. Question: Intuitive, seamless, responsive, and visually appealing user interface and experience

Can you confirm you are referring as the user the Publisher and not the listener? The difference is as a Publisher, yes, you do have access to the different platforms UI (metrics, ad server, monitoring, podcasting, etc). As a listener it would depend on your website, mobile apps which usually are developed by your team.

Response:

The requirement applies primarily to the listener interface developed and delivered by the vendor. The app’s design must be visually appealing, user-friendly, and responsive across platforms (web, iOS, Android, smart speakers, Android Auto, Apple Car Play, etc.). However, the publisher interfaces provided by the vendor for content management and analytics must also be intuitive and seamless to support efficient operations.

5. Question: Enhanced Music Customization and Command Integration that delivers a personalized, dynamic listening experience while ensuring users remain connected to mission-critical updates

Can you please clarify this question, because we are not sure if you are referring to the programming of the stations, quality of sound, stability of the network et al.

Response:

This requirement combines music personalization with the ability to integrate mission-critical updates into the listening experience. Personalization includes curated playlists and dynamic music recommendations based on user preferences. Command integration refers to inserting critical updates (e.g., PSAs or alerts) into the audio stream or app interface without disrupting the overall listening experience.

6. Question: Adjust for hits, deep cuts, or emerging tracks

This requirement is not clear, it seems this is more related to a Radio Automation System and programming than the streaming services. Please clarify so we can provide you with the correct information.

Response:

This requirement is listener-focused and refers to providing users with options to customize their listening experience by adjusting the content mix. For example, users should be able to select preferences for popular hits, lesser-known deep cuts, or emerging tracks. This can be implemented through user-side customization features in the app.

7. Question: Command Interstitial Integration

It is not clear what is the requirement you are looking for with this question. Can you please clarify?

Response:

This refers to the ability to insert PSAs, mission updates, and other command messaging seamlessly into audio streams. These interstitials should be dynamically integrated between songs or segments, with customizable frequency and placement. The goal is to ensure minimal disruption to the listening experience while delivering critical updates. Dynamic ad insertion on live streams and on-demand audio.

8. Question: Rotate seamlessly between music and command messaging

It seems that this question is more related to the Radio Automation System (programming of the station) than to the streaming services. Can you please clarify what you require?

Response:

This requirement pertains to dynamic scheduling of music and command messages within the programming. It should allow for smooth transitions between music content and mission-critical updates. This feature requires tight integration with a Radio Automation System (RAS) or dynamic scheduling tools to ensure consistent audio quality and timing.

9. Question: Receive real-time updates and alerts (Push Notifications) from command sources

Is this related to the different alerts that can be configured regarding the health of the different radio stations (disconnection, dead air, etc)? or is it related to something else? Please clarify.

Response:

This requirement involves delivering real-time updates and alerts to listeners via the app. These updates should be configurable by the command, with options for geo-targeted or universal delivery. The functionality may also include backend notifications for publishers (e.g., stream health monitoring, silence detection).

10. Question: Documentation for Cybersecurity approval as required

Can you please clarify the request? We are not sure what you are requiring.

Response:

The requirement refers to documentation demonstrating compliance with DISA and DMUC cybersecurity standards. This includes submitting System Security Plans (SSPs), meeting NIST Risk Management Framework (RMF) requirements, and ensuring the vendor has an Information System Security Officer (ISSO) to manage and maintain compliance throughout the contract lifecycle.