Questions_and_Answers_for_Radio_Automation_Solicitation.pdf

RADIO AUTOMATION QUESTIONS AND ANSWERS

1. Are any additional Wheatstone AOIP blades required? If so How many and what type?

AFN Response: The Vendor should provide a turn-key solution. It is preferred that Wheatstone blade drivers are provided and utilized, but in situations where audio cards/wiring is necessary, blades shall be provided by the Vendor. We currently have a mix of Blade series 2 and 3. Specific firmware versions to ensure compatibility can be discussed in the design reviews with the successful Vendor.

2. Just to be clear is it 24 Stations originating content at this location? Or is it one studio that is acting as a master control to 24 Channels? If there are additional stations involved do we need to procure additional Wheatstone consoles? Blades? Or any other studio equipment?

AFN Response: Yes, all 24 originate from the AFNBC (Network). The 24 stations are automated playout channels. In a typical environment, the existing studios/consoles are not part of the signal path. No other studio equipment required.

3. Do we need to procure any equipment for the 10 Post Production Edit Bays? Are there already built and in use? If so can we get a rough description of the workflow and equipment currently installed and any additional equipment you'd like us to procure? Are they being used for Vocal tracking and if so do they have acoustic treatment or do they need acoustic treatment?

AFN Response: No additional production equipment required.

4. 6.1.7 - Recording automatic background audio, Do you plan on using your Wheatnet drivers or did you want a relay closure tied to a server to control the automatic recording function?

AFN Response: This section refers to automated ingest, where record schedules capture incoming programming by a timed schedule. Recordings shall also be initiated by an incoming provider relay, which would be provided to the proposed system via existing Wheatnet SLIO (Wheatstone’s term for software logic). In this case, the provided solution shall have network connectivity to the existing Wheatstone network and have the capability to react to SLIO’s.

5. Is it our responsibility to procure rack(s), rack hardware and install? If so is it AFN's wishes that we procure a certain type of rack so their rack room keeps a consistent aesthetic look? Also can we get a QTY of racks they would like us to procure?

AFN Response: No, racks are already in place.

6. Are we going to be responsible for any cable path installation? I.e. conduit or cable tray installation? If not, what is the cable path method through the facility? Conduit or Cable Tray and conduit?

AFN Response: No. The cable tray is existing, we use trays not conduit.

7. Do any of the cable paths require the cable to be plenum rated cable?

AFN Response: All cable shall be plenum rated. If it wasn’t sufficiently clear in the RFP, cables shall be custom lengths, i.e. no lengthy coils in the racks, trays or raised floor. Cables shall be of professional grade, Belden or equivalent, professionally dressed with cable management and properly labeled. These sort of details can be further discussed in the design reviews with the successful Vendor.

8. How many Computers are going to be required to be on the KVM? How many sources vs. how many destinations?

AFN Response: All computers provided shall be accessible via the KVM system, both at a local console or via the network.

9. With regards to the automatic recording of the Alibi Logging system, do we need to provide a plan for capture of all 24 channels or only some? If only some, how many? Is that 24/7 recording and for how long?

AFN Response: Per the PWS, the Alibi system shall record 30 channels. The recordings are 24x7 continuous and shall be maintained for 60 days. Each hour of each day shall be a separate file, stored as an mp3, tagged with the channel name, date and time for ease of retrieval.

10. In the Diagram on page 29 it shows two AFN-BC Firewalls. Are we responsible for procuring these firewalls or are they already existing and we just need to connect into them?

AFN Response: No. The diagram was to give an overview of the network/affiliate topology. The proposed network system shall come with its own network hardware and shall be connected to an existing B Net switch.

11. How many audio Automatic Fail Over channels should we plan for? All or only 1 or somewhere in between?

AFN Response: Each of the AFN Network channels shall have a primary and backup automation playout as described in the PWS.

12. Do we need to procure 4 PC(s) per format? Or are they already existing and only in need of drivers and KVM units?

AFN Response: If individual PCs were proposed, then yes, it would be 4 (For example, Country Atlantic primary/backup, Country Pacific primary/backup). However, the desire is for the successful vendor to utilize virtual technology.

13. Do we need to procure any additional video Monitors and mounts? Or are they already existing? If Not How many?

AFN Response: Yes, professional grade desktop monitors shall be provided for the Production PCs and rack mount type for any server room rack locations.

14. Does AFN wish to have physical Count Up/Down timers or do they prefer software based Count Up/Down Timers?

AFN Response: Software.

15. Can we put the UPS budget into an ECP (engineering Change Proposal) under 16.1 until after we have the design phase finished to appropriately spec and price the high voltage power?

AFN Response: The proposed system shall connect to existing facility UPS systems which provide redundant power to the existing racks. The Vendor shall to provide load calculations for the proposed system components. Further power related discussions can occur in the design reviews with the successful Vendor.

16. How many logs, stations will need to be licensed for the ERAS? Since the main site in Riverside has 24 stations plus the two “evergreen” stations, is the total then 26? There is a question since the RFP mentions 30 “Alibi” channels for background records. Also, is the ERAS to background record those “Alibi” channels?

AFN Response: The ERAS shall be responsible for 26 logs for automated station playout, 30 24x7 Alibi record and 24 content ingest record lists.

17. Since Wheatstone/WheatNet AOIP is to be used by the ERAS, how many WheatNet Channels are used, needed by each of the 24 full-time stations? And, by other stations?

AFN Response: AFN would need more detail to accurately answer.

18. With regards to 6.2.1.8 can we get clarification as to admin created profiles for watching internal and external audio file folders automatically ingesting the files into their respective categories in storage. Does this mean AFN would like Profiles for different Admin Users to have different file paths for ingesting audio to those file paths on the shared storage platform?

AFN Response: No. It means the system shall provide the ability to require an administrator level account to create workflow profiles.

19. With regards to 6.2.1.9 if the IP import program / application freezes or stops, it shall be easily restarted and quickly rescan watch folders to pick up where it left off. Can we get clarification on this topic as it pertains to watch folders... Currently our solution to this will start where it left off, but I want to verify that we aren't over looking the details of "watch" folders so we can get AFN the correct solution.

AFN Response: Should a situation arise where an automated import in progress is interrupted (e.g.

network connection loss), when the cause is fixed, the system shall be aware the import did not successfully complete and automatically take action to ensure the request completes.

20. Does the RFP include, want the contractor to provide, replace an existing Traffic system for spots; or, will this be done by the music scheduling system? Please provide an explanation of what is included in

“traffic”.

AFN Response: Please refer to PWS section 6.2.5 for the details on the Traffic requirement.

1. Section B ‐ Supplies or Services and Prices; Items 0007: Please confirm that this CLIN is in fact an Option.

AFN Response: Yes, CLIN0007 is a Government Option.

2. Section B ‐ Supplies or Services and Prices; Items 0008, 0009, 1001, 2001, 2002, 3001, 3002, 4001, & 4002: Should the quotation value be for a single system or service, or for the NTE quantity?

AFN Response: The quotation value should contain both the unit price and the extended amount based upon the NTE quantity. If the Vendor offers a price break for any specific quantities, that should be stated in the response.

3. Section B ‐ Supplies or Services and Prices; Item 1005: We believe this should read Year

AFN Response: Item 1005 should read Year 4.

4. Section C ‐ Descriptions and Specifications; Item 4 Scope, paragraph 1, and Item 6 Performance Requirements state: The Affiliate/DINFOS systems will be separated as Government Optional which may or may not be exercised all or in part at a later date. Will any of the affiliate systems be purchased with the initial AFN‐BC Network contract?

AFN Response: AFN does not anticipate optioning Affiliate or DINFOS systems along with the Network system at AFN-BC.

5. Item 6.1.9 Time Synchronization: Please describe any time synchronization challenges and/or difficulties AFN and affiliates currently are experiencing or have experienced in the past.

AFN Response: As described in 6.1.9, AFN-BC synchronizes the current system via an existing NTP clock. The proposed system shall be capable of automatically update during daylight/standard time changes and ensure schedules stay on time.

Regarding any challenges, the Network provides a sub-audible tone embedded in program audio to synchronize the affiliate clocks. As stated elsewhere in the PWS, the desire is to move away from sub audible tones for time synchronizing and affiliate automation cueing.

6. Item 6.1.14: Please provide details of the existing automation system, schedule creation software, file transfer of existing media method, and time synchronization method.

AFN Response: The current on air automation in use at the Network is OMT iMediaTouch v4.x.

Schedules are created by a combination of PowerGold and the OMT Log Tools Module. Media is transferred by a variety of methods, typically managed by iMediaTouch Import. Time is synchronized by a network connection to a house NTP clock.

7. Item 6.2.1.1: Please provide a list of those sources currently being used, as well as examples of type of programs, IE entertainment, news, sports, etc.

AFN Response: AFN acquires programming from a variety of providers to include most major networks and independent program producers. For example, AFN employs the use of satellite receivers (XDS, Wegener iPump, etc) to acquire programming from Westwood One and Premiere.

8. Item 6.2.1.5: Please indicate if this requirement refers to content in the process of being ingested, or only content to be ingested at a future time.

AFN Response: The desire is for while content is being ingested.

9. Item 6.2.2.2: Is this a functional requirement that is separate from Audition (or any proposed alternative)?

AFN Response: It is a functional requirement of the production product contained within the proposed automation system, not external, i.e.Audition.

10. Item 6.2.2.21: Please define “Normalize”.

AFN Response: To automatically adjust the audio level of a file’s audio content at a predetermined level.

11. Item 6.2.2.25: Please define customizable: A: Customizable by a user.

B: Customizable by AFN technical management. C: Customizable by the ERAS supplier.

AFN Response: An Operator or Tech with Admin defined permissions, shall have the ability to edit the metadata associated with any audio file.

12. Item 6.2.2.33: Please detail the challenges mentioned.

AFN Response. Operations has worked through any previous challenges. However the requirement stated in 6.2.2.33 remains.

13. Item 6.2.6.1: Please list the type and format of Satellite programs to be played back.

AFN Response: AFN On Air program schedules utilize various sources to produce a 24x7 voice or music format. Satellite receivers output AES digital audio and relays closures.

14. Item 6.2.6.25: Please define “dynamic media asset management”.

Please also provide more detail on the required functionality and provide detail on what is referred to by satellite in the phrase “file transfer via LAN/WAN or satellite”

AFN Response: The proposed system shall dynamically manage all assets in its storage database.

In some cases, providers will deliver a program as a file over satellite instead of streaming AES, (e.g.

NPR Content Depot) where the automation import schedule shall be able to monitor the receivers “hot folder” and based upon a rule, deliver the file to storage for later use.

15. Item 6.2.7.5: Please detail this requirement: loop which audio? How is the loop specified?

AFN Response: During a live event, the host could put a song intro in a loop while they are talking, then allow the song to continue playing from that point.

16. Item 6.2.7.8: Please explain what is meant by drag and drop from external feeds.

AFN Response: Should a talent have an audio file on an external drive, desktop, etc, they shall have the ability to grab the file and drop it into the on air schedule on the fly so it plays as an upcoming event.

17. Item 7.2: This section indicates the contractor shall deliver a Turnkey System with connectivity to the demarcation point: Should the supplied

ERAS system be self‐contained in its own rack enclosure(s), or will rack space be provided at AFN‐BC Riverside for ERAS equipment.

AFN Response: AFN will provide rack space at the AFN-BC for the proposed system.

18. Item 8.1: Will an area be provided for the ERAS installation separate from the existing AFN‐BC automation system so that parallel operation of, and orderly transition between, the two systems is possible?

AFN Response: Yes.

19. Item 11.8: Please indicate what types of remote access are acceptable.

AFN Response: Typically remote access by methods such as Teamviewer are acceptable. The Vendor shall describe their proposed methods in their response.

20. Please supply a floorplan of the AFN‐BC Riverside with room names and dimensions.

AFN Response:

6.1.3 Will the affiliates need to create complete new schedules or would they simply need to modify schedules that are supplied by the network?

AFN Response: Both.

6.1.4 Is it permissible for the system to use an alternate internet connection using a separate VPN?

AFN Response: The connectivity and circuit availability at each affiliate varies greatly. Worldwide connectivity can be discussed further during the design review with the successful vendor.

6.1.8 If the system is capable of fully supporting graphic display, keyboard and mouse control with a thin client without the need for KVM units in the control room, would that meet the requirement? | KVM units can be used in production facilities if needed. |

AFN Response: The studio shall have access to their client and the display, keyboard and mouse control shall also be on a KVM for access to that client elsewhere on the network. A thin client in the studio is acceptable, so long as fan noise is not audible through the studio mic.

6.1.13 Provided the system will display multiple languages, can AFN assist by providing the appropriate terms for use by the affiliate locations?

AFN Response: The desire is for the software to convert all onscreen text into foreign languages, Japanese, Korean, Italian and German for example.

6.1.14 What is the file format for the existing files, eg., linear uncompressed .wav, MP2, MP3, etc?

AFN Response: Current files are stored in .wav and mp3.

6.1.15 Will AFN staff members be working with the vendor to assist in the integration of previously existing system components that will continue to be used?

AFN Response: Yes. The successful Vendor will, in most cases, wire to a predetermined demarcation point. AFN will have staff to assist with the integration of existing systems, however if assistance is required from the existing automation manufacturer, it is the Vendors responsibility to seek that assistance and provide payment as required.

6.2.1.1 Will this capability be needed in both the network and affiliate locations?

6.2.1.7 If very granular user rights are employed in the for virtually every functionality, is Active Directory required if all other requirements of this section are met?

AFN Response: At the Affiliate locations, the Automation systems are connected to a larger Government network where Active Directory is required. Granular User privileges would suffice for the AFN-BC Network system.

6.2.1.8 What is the purpose of the different profiles? What functionality do you expect it to enable? What does Internet Protocol mean in this context? Is this for automatically importing files that come in via IP or are stored on remote files?

AFN Response: When a file is to be imported via SFTP, for example, a profile would have been created by an Admin, which tells the system at minimum where to look for the file, how levels should be normalized, file runtime adjusted, the file format, what category it should be placed in and what folder in storage it needs to be transferred into.

6.2.1.15 With regard to the playing within one second of record start, are the record and play locations within the same facility and LAN?

6.2.1.25 Is the record schedule meant to describe the list of elements that are set to be recorded and is the execution log a record of what has been recorded?

AFN Response: Yes and Yes.

6.2.2.3 Can you explain this in more detail? Where would the files and directories be located for import and what might be their ultimate use?

AFN Response: This refers to Production, when a file is being imported from any available source, (CD, local drive, etc) the Operator has the option to cancel the import while it is in progress.

6.2.2.4 Can this functionality be used with the Adobe Audition integration function?

AFN Response: The functionality shall be available in the Production application included in the automation suite.

6.2.2.7 Is this requirement different from the multi-track functionality for 'undo' that is included in the session file process in recent versions of Adobe Audition?

AFN Response: It is not different. The functionality shall be available in the Production application included in the automation suite.

6.2.2.14 Please describe the programming content in the four-hour file and what is the origin. Would it be acceptable to record in 1 hour segments?

AFN Response: The full file would be preferred. An example would be a four hour music countdown program, Operations desires the ability to bring in the entire file into Production, scrub the file for any necessary edits and save the file in its entirety for later airing.

6.2.2.15 What is meant by user-definable prompts?

AFN Response: Typical Windows-type save/save as prompts…Where to save, file name, etc. Also prompting the User that they are about to overwrite a file.

6.2.2.18 Is there a particular challenge with your existing system that is creating a problem that needs to be solved? What problems do you expect to prevent by a category name greater than 3 chars? Can you send a screen grab of the limitation?

AFN Response: The current system allows for three character categories for cataloging content. For example, Classic Rock News is the “CRN” category, which could also be Country Radio News. It would be desirable to have more than three letters to identify categories.

6.2.2.19 If the system can do this forwarding by user-defined rules and standards, would that suffice in lieu of a professional, enterprise-grade file sync program?

AFN Response: AFN would need to see the capabilities of the proposed solution before accepting.

6.2.2.20 What type of automation/ integration is required for the XDS receiver? Can you provide a sample use case?

AFN Response: None directly. The Automation solution shall communicate with the Wheatstone router to route audio and react to relays.

6.2.2.28 Can this ripper be considered as a part of the Adobe Audition integration?

AFN Response: No, an integrated solution within the proposed production module is desired.

6.2.2.33 What are the challenges using rotations for news?

AFN Response: Operations has worked through any previous challenges. However the requirement stated in 6.2.2.33 remains.

6.2.2.34 Would an automatically refreshing database be acceptable if it acts on any update to metadata, log ingest or audio file ingest, category change or user log-on?

AFN Response: AFN would need to see how quickly the database automatically refreshes before accepting. Today an Operator does an import, selects refresh and has the updated database immediately available.

6.2.3.12 Can you further define 'announcer stack'?

AFN Response: AFN requires the system to be able to schedule changes in the cart wall at any time during any hour by time or event sequence with no effect on the program audio.

6.2.3.13 Can this be displayed in the daily playlist in the user interface screen, a playlist editor or in the music scheduler that has previously ingested the traffic information?

AFN Response: Automation shall keep tally of an hour while programming a station. The system shall provide feedback as to the current schedule while it is being worked, whether the hour is short or over for that hour and for the full day’s schedule.

6.2.3.15 Can you describe more fully your expectations for this functionality? Would this be more specific than a break entry liner? What is first position break relay?

AFN Response: AFN cannot air commercial content and not all suppliers provide a relay at the start of the affiliates break. In cases where that “first position” break relay is not provided, AFN breaks away using a previous liner or ID relay plus a timer to execute the break.

6.2.3.17 While most systems already have some sort of interaction with Triton and other providers, it appears that the requirements for AFN 360 may be more rigorous. How might we get more details on the specifications that are used or needed but not being handled by the current system?

AFN Response: The key point is the proposed system shall provide customizable XML now playing data across a network as UDP to the existing stream servers, and the data stream shall remain following an automatic failover to a station’s backup play server.

6.2.3.18 Is there a particular reason for pre-loading 40 events? Is it possible to provide a sample of the file specifications and what other changes might be anticipated?

AFN Response: The 40 event number was to cover an hour, as the STB middleware provider will pick up the data file once an hour. The exact requirements can be discussed with the successful Vendor during the design reviews, however for informational purposes only, a sample of what the STB middleware provider requires is as follows:

<?xml version="1.0" encoding="UTF-8"?>

-<divitech_epg version="3.6"> -<schedule utc_offset="-08:00" channel_id="Ch132: Contingency"> -<event production_year="1111" genre_level="0:0" end_time="2019-02-15 09:00:00" actual_time="2019- 02-14 09:00:00" event_id="6"> <description title="Contingency Radio Service" long_synopsis="" short_synopsis="Contingency - Radio Service Test Channel - 1" language_code="eng"/> </event> -<event production_year="1111" genre_level="0:0" end_time="2019-02-16 09:00:00" actual_time="2019- 02-15 09:00:00" event_id="7"> <description title="Contingency Radio Service" long_synopsis="" short_synopsis="Contingency - Radio Service Test Channel - 2" language_code="eng"/> </event> </schedule> </divitech_epg>

6.2.3.19 XML commands are very commonly used for this same purpose. Are there conditions at AFN that make this difficult that you wish to resolve or improve?

AFN Response: The current XML output containing the now playing data is also where the affiliate availability stream splice occurs. Today those splice commands are a silent audio event, it is desirable to program the command as a secondary event, not a silent audio file that adds to the hour.

6.2.3.20 Would it be acceptable to have a default display when there is no appropriate audio present?

AFN Response: Yes assuming the display is customizable by AFN on a per station basis.

6.2.3.21 Is there a particular problem that is to be solved by stopping the playback at program rejoin? Is there a problem with timing or fill for the stopset?

AFN Response: The current XML output containing the now playing data is also where the affiliate rejoin command occurs. Today those commands are a silent audio event, it is desirable to program the command as a secondary event, not a silent audio file that adds to the hour.

6.2.4.1 Considering that all 24 channels (expandable) will have Music Scheduling capabilities, is there a number of seats for scheduling personnel that will be optimal for flexibility?

AFN Response: Eight seats for AFNBC Network scheduling would be sufficient at this time, with the ability to expand or decrease at a later date. Also, as the Network provides one each playlist file for the Affiliate stations, we are not aware whether each of those locations would need a license to import the schedule into their existing AudioVault machines while they remain on their legacy system.

6.2.4.4 Can you more fully define schedule conflicts?

AFN Response: This isn’t necessarily a “conflict” rather the music scheduling application having the ability to scan the days log and distributing content so there is adequate separation.

6.2.6.24 Is this to look for discrepancies or exceptions? If yes, will you entertain other approaches? If not, what is the business case behind this requirement?

AFN Response: Yes. The desire is to view the schedule and the as-run side by side.

6.2.6.25 Please provide complete requirements or more fully describe use case.

AFN Response: The desire is for the capability to create automated workflows to push or pull content between the Network and Affiliates to/from a shared storage location. Administrative permissions would apply.

6.2.7.8 Please provide a user case of how drag-and-drop would be used with an external feed

AFN Response: Should a talent have an audio file on an external drive, desktop, etc, they shall have the ability to grab the file and drop it into the on air schedule on the fly so it plays as an upcoming event.

6.2.7.9 Please define cart wall. Is this the audio file library?

AFN Response: The definition would be a customizable group of instant audio playback files displayed on a grid on the On Air display screen for quick on-demand play while live.

6.2.7.10 Is mixing on a sound card required for single channel output? Are Wheatstone Blades not available at these locations?

AFN Response: Wheatstone Blades would satisfy this requirement.

6.2.8.4 What is the use case for this? Is this an automated solution or something manually manipulated by staff?

AFN Response: The use may grow over time, however the initial desire is a central location for archiving and sharing of media assets among the Network and Affiliates. Automated workflows would be desired, however staff shall have the ability to manually share files and create folders depending on their privileges. The cloud requirements are spread throughout the PWS, please do a search for “cloud” on the document.

6.4.1 Is a full-time WAN available between the head end and all affiliates? if yes, please provide details.

AFN Response: There is a full time connection, however the connection isn’t reliable enough for day to day on air operations.