HQ0516-19-R-0007_Radio_Automation_System_RFP.pdf

SEE ADDENDUM

(No Collect Calls)

HQ051619R0007 19-Apr-2019

b. TELEPHONE NUMBER

951-413-2634

8. OFFER DUE DATE/LOCAL TIME

10:00 AM 20 May 2019

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

HQ05169. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

SHEVONN MOORE

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

HQ0516914522

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED OR X

SMALL BUSINESSX

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

HQ0516 DMA CONTRACTING

SHEVONN MOORE

23755 Z. STREET

RIVERSIDE CA 92518

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: (951) 413-2486

SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

1,250

NAICS:

334220

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF87

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

HQ051619R0007

Section A - Solicitation/Contract Form

CLAUSES INCORPORATED BY REFERENCE

52.203-18 Prohibition on Contracting With Entities That Require Certain

Internal Confidentiality Agreements or Statements--

Representation

JAN 2017

Section B - Supplies or Services and Prices

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

1 Lot

AFN-BC SYSTEM PRELIMINARY DESIGN REVIEW

FFP

Deliverable: Preliminary Design Review Package

IAW PWS PARAGRAPH 7.1 PRELIMINARY DESIGN WILL BE DUE

APPROXIMATELY 30 DAYS AFTER DATE OF AWARD (ACD).

FOB: Destination

PURCHASE REQUEST NUMBER: HQ0516914522

NET AMT

AFN-BC SYSTEM INTERMEDIATE DESIGN REVIEW

FFP

Deliverable: Intermediate Design Review Package

IAW PWS PARAGRAPH 7.1 INTERMEDIATE DESIGN WILL BE DUE

APPROXIMATELY 60 DAYS ACD.

AFN-BC SYSTEM FINAL DESIGN REVIEW

FFP

Deliverable: Final Design Review Package

IAW PWS PARAGRAPH 7.1 FINAL DESIGN WILL BE DUE

APPROXIMATELY 90 DAYS ACD.

AFN-BC SYSTEM EQUIPMENT DELIVERY

FFP

IAW PWS PARAGRAPH 6.0 SYSTEM EQUIPMENT DELIVERY WILL BE

DUE APPROXIMATELY 210 DAYS ACD.

AFN-BC SYSTEM TRAINING

FFP

IAW PWS PARAGRAPH 10.0

AFN-BC SYSTEM COMMISSIONING&INTEGRATION

FFP

IAW PWS PARAGRAPH 4.0, 6.0, 7.0, & 8.0 COMMISSIONING AND

INTEGRATION (TO INCLUDE ACCEPTANCE TESTING)

OPTION

AFN-BC SYSTEM INSTALLATION

FFP

IAW PWS PARAGRAPH 7.2.

AFFILIATE SYSTEM AFN-BC TEST SYSTEM

IAW PWS PARAGRAPH 6.0 & 14.2 NTE 2 SYSTEMS

NETWORK AFN-BC REFRESHER TRAINING

IAW PWS PARAGRAPH 10.2 TRAINING NTE 40HOURS

TRAINING TASA TECHNICIANS AFFILIATE SYS

IAW PWS PARAGRAPH 10.9

1 Years

NETWORK (AFN-BC) SYSTEM

IAW PWS PARAGRAPH 11.0 Network (AFN-BC) System 24x7 Service and

Support Year 2

IAW PWS PARAGRAPH 11.0 Network (AFN-BC) System 24x7 Service and

Support Year 3

IAW PWS PARAGRAPH 11.0 Network (AFN-BC) System 24x7 Service and

Support Year 4

IAW PWS PARAGRAPH 11.0 Network (AFN-BC) System 24x7 Service and

Support Year 5

IAW PWS PARAGRAPH 11.0 Network (AFN-BC) System Licensing Year 2

IAW PWS PARAGRAPH 11.0 Network (AFN-BC) System Licensing Year 3

IAW PWS PARAGRAPH 11.0 Network (AFN-BC) System Licensing Year 4

IAW PWS PARAGRAPH 11.0 Network (AFN-BC) System Licensing Year 5

20 Each

AFFILIATE SYS DINFOS FORT MEADE

IAW PWS PARAGRAPH 6.0 & 14.2 NTE 20 SYSTEMS

DINFOS SYSTEM ONSITE TRAINING

IAW PWS PARAGRAPH 10.0

DINFOS SYSTEMS

IAW PWS PARAGRAPH 11.0 DINFOS SYSTEMS 8X5 SERVICE AND

SUPPORT AND LICENSING YEAR 2

IAW PWS PARAGRAPH 11.0 DINFOS SYSTEMS 8X5 SERVICE AND

SUPPORT AND LICENSING YEAR 3

IAW PWS PARAGRAPH 11.0 DINFOS SYSTEMS 8X5 SERVICE AND

SUPPORT AND LICENSING YEAR 5

IAW PWS PARAGRAPH 11.0 DINFOS SYSTEMS 8X5 SERVICE AND

SUPPORT, LICENSING YEAR 5

20 Each

AFFILIATE SYSTEMS ATLANTIC REGION

IAW PWS PARAGRAPH 6.0 & 14.2 NTE 20 SYSTEMS

6 Job

ATLANTIC REGION ONSITE TRAINING

IAW PWS PARAGRAPH 10.0 NTE 6 Separate On Site Visits for Training

ATLANTIC REGION SYSTEMS

IAW PWS PARAGRAPH 11.0 ATLANTIC REGION SYSTEMS 24X7

SERVICE AND SUPPORT, LICENSING YEAR 2

IAW PWS PARAGRAPH 11.0 ATLANTIC REGION SYSTEMS 24X7

SERVICE AND SUPPORT, LICENSING YEAR 3

IAW PWS PARAGRAPH 11.0 ATLANTIC REGION SYSTEMS 24X7

SERVICE AND SUPPORT, LICENSING YEAR 4

IAW PWS PARAGRAPH 11.0 ATLANTIC REGION SYSTEMS 24X7

SERVICE AND SUPPORT, LICENSING YEAR 5

6 Each

AFFILIATE SYSTEMS KOREA REGION

IAW PWS PARAGRAPH 6.0 & 14.2 NTE 6 SYSTEMS

2 Job

KOREA REGION ONSITE TRAINING

IAW PWS PARAGRAPH 10.0 NTE 2 Separate On Site Visits for Training

KOREA REGION

IAW PWS PARAGRAPH 11.0 KOREA REGION 24X7 SERVICE AND

SUPPORT ,LICENSING YEAR 2

IAW PWS PARAGRAPH 11.0 KOREA REGION 24X7 SERVICE AND

SUPPORT ,LICENSING YEAR 3

IAW PWS PARAGRAPH 11.0 KOREA REGION 24X7 SERVICE AND

SUPPORT ,LICENSING YEAR 4

IAW PWS PARAGRAPH 11.0 KOREA REGION 24X7 SERVICE AND

SUPPORT ,LICENSING YEAR 5

7 Each

AFFILIATE SYSTEMS JAPAN REGION

IAW PWS PARAGRAPH 6.0 & 14.2 NTE 7 SYSTEMS

4 Job

JAPAN REGION ONSITE TRAINING

IAW PWS PARAGRAPH 10.0 NTE 4 Separate On Site Visits for Training

JAPAN REGION

IAW PWS PARAGRAPH 11.0 JAPAN REGION 24X7 SERVICE AND

SUPPORT, LICENSING YEAR 2

IAW PWS PARAGRAPH 11.0 JAPAN REGION 24X7 SERVICE AND

SUPPORT, LICENSING YEAR 3

IAW PWS PARAGRAPH 11.0 JAPAN REGION 24X7 SERVICE AND

SUPPORT, LICENSING YEAR 4

IAW PWS PARAGRAPH 11.0 JAPAN REGION 24X7 SERVICE AND

SUPPORT ,LICENSING YEAR 5

Section C - Descriptions and Specifications

PERFORMANCE WORK STATEMENT

Performance Work Statement

Enterprise Radio Automation System Contract Number:

Solicitation Number: HQ0516-19-R-0007

Tracking Number:

1. Contracting Officer Representative (COR).

1.1 Primary COR.

Name: (completed by the KO at time of contract or TO award) Organization:

Department of Defense

Activity Address Code

(DODAAC):

(refer to the DODAAC web site at https://dodaac.wpafb.af.mil for additional information) Address:

Phone Number:

Fax Number:

E-Mail Address:

1.2 Alternate COR.

Name: (completed by the KO at time of contract or TO award) Organization:

DODAAC: (refer to the DODAAC web site at https://dodaac.wpafb.af.mil for additional information) Address:

Phone Number:

Fax Number:

E-Mail Address:

2. Task Order Title: Enterprise Radio Automation System (ERAS).

3. Background: The Defense Media Activity (DMA) provides comprehensive internal and external information to the entire Department of Defense through all available media. DMA communicates messages and themes to Secretary of Defense, Service Secretary and other

DoD and Military Service through the medium of print, the worldwide web, radio and https://dodaac.wpafb.af.mil/ https://dodaac.wpafb.af.mil/ television in order to support and improve quality of life and morale, situational awareness, and sustain readiness. DMA provides U.S. radio and television news, information and entertainment programming to military service members, DoD civilians and their families overseas, and on board U.S. Navy ships. The DMA, for the purpose of this contract, consist of the following subordinate organizations:

American Forces Network (AFN)

American Forces Network-Broadcast Center (AFN-BC)

Defense Information School (DINFOS)

Station AFN Bahrain

Station AFN Benelux

Station AFN Gitmo

Station AFN Kaiserslautern

Station AFN Rota

Station AFN Sigonella

Station AFN Souda Bay

Station AFN Aviano

Station AFN Incirlik

Station AFN Spangdahlem

Station AFN Stuttgart

Station AFN Vicenza

Station AFN Weisbaden

Superstation AFN Bavaria

Superstation AFN Naples

Superstation – Center AFN Sembach

AFN Headquaters Fort Meade, MD

AFN Broadcast Center Riverside, CA

Superstation – Bureau AFN Humpheys

Station AFN Kunsan

Station AFN Daegu

Station AFN Okinawa

Station AFN Sasebo

Station AFN Misawa

Station AFN Iwakuni

Station AFN Diego Garcia

Station - Center AFN Tokyo

Policy/Guidance

DISA L3VPN Connectivity

Defense Information School

(DINFOS)

Defense Media Activity

(DMA)

The AFN-BC staff performs a wide array of post-production functions on programming acquired from sources including U.S. commercial and public broadcast networks, independent producers, and programming distributors.

Command information, promotional spots, timely news and sports and interstitial materials are assembled for inclusion into each automated radio channel. AFN-Region specific radio services and content are distributed to DMA outlets and authorized users through a global satellite digital network, live web streams, internet file delivery or on duplicated media, whichever is most appropriate. DMA outlets further distribute this programming to their local audiences by means of standard AM, FM, satellite, or cable TV transmission systems.

4. Scope: The contractor shall design, engineer, furnish, install, integrate, test and commission all hardware, software, licensing, ancillary equipment, training, documentation and warranty support to provide an Enterprise Radio Automation System (ERAS) as a replacement to the current Automation System. The ERAS shall provide AFN and their Affiliates the ability to operate as one global network whereas On-Air playlists may be securely administered locally and remotely from the AFN-BC and specific radio content is shareable as administered across the ERAS. The ERAS shall consist of a core (Network) system at the AFN-BC and shall be capable of supporting a minimum of 37 Affiliate systems located worldwide as well as 18 Affiliate training systems located at DINFOS. Vendors are encouraged to demonstrate their proven ability to utilize emerging technologies (e.g. cloud) for any of the following subsystems. The installation requirement applies to only the Network system. Please be advised of the Acceptance Testing requirement detailed in section 8 of this PWS. The

Affiliate/DINFOS systems will be separated as Government Optional CLINs which may or may not be exercised all or in part at a later date.

AFN-BC System

2018/19

Atlantic Region Pacific Region

2021 * 2023 *

* Projections are approximated and not guaranteed to Occur

Network

Enterprise

Affiliates

DINFOS

2020 *

The ERAS functionally consists of the following subsystems. Proposed systems that integrally contain these subsystems without the use of third party applications may be more desirable.

On Air Radio Automated Playout

Automated Satellite Content Acquisition

Local Archive and Play-to-Air Storage

Secure Shared Cloud Based Storage

Multi-Station Traffic

Multi-Station Music Scheduling

Audio Editing Production and Assembly

Live Studio Assist

Alibi Logging

Wheatstone and Axia Router Control

The figure below represents a functional description of the ERAS. This diagram in no way implies a required or suggested architecture for the system but is provided only as a means to assist with an understanding of the scope.

AFN-BC Network SystemOn Air Playout

Edit Production Assembly

Content Acquisition

Studio/Live Assist

Traffic

Music Scheduling

Local Archive Play-To-Air

Storage

On Air Playout

Edit Production Assembly

Studio/Live Assist

Traffic

Music Scheduling

Local Archive Play-To-Air

Storage

AFN Affiliate Systems

Axia RouterWheatstone AoIP Router

Administrative Rules Applied

Alibi Logging Alibi Logging

Content Acquisition

Secure, Shared Cloud Storage

The figure below represents a sample global architecture of the ERAS. This diagram in no way implies a required or suggested architecture for the system but is provided only as a means to assist with an understanding of the scope.

Affiliate A

Affiliate B

DINFOS

DISA Cloud (Existing)

Cloud Storage

AFN-BC A-Net Firewall

AFN-BC B-Net Firewall

AFN-BC B-Net

Field Production

Network System

The contractor shall provide a transition plan that supports minimum interruption to current operations while the ERAS is installed and tested. The contractor shall provide on-site training on all portions of the ERAS to AFN-BC programming, operations and engineering personnel.

5. Purpose: To acquire an ERAS which incorporates a Network System (AFN-BC) and numerous Affiliate systems that function as one geographically separated system. Specific requirements and quantities are detailed later in this PWS.

The ERAS will enable the DMA AFN-BC to meet and support the American Forces Network

(AFN) mission under the DMA Performance Plan: Key initiative 2: “Transform delivery of

Radio Overseas: Retain the ability to deliver both entertainment and command information while exploring cost reductions by adjusting overseas infrastructure, facility footprint, and communications costs.” This mission is to provide a balanced representative selection of popular radio and television information and entertainment programs of particular interest to both the primary AFN audience of DoD personnel stationed overseas and their family members. The Enterprise Radio Automation System shall ensure the accomplishment of the

AFN mission to effectively communicate command information to DoD personnel stationed overseas and their family members, while simultaneously providing the level of entertainment needed to make a positive impact on their morale. It will also provide the most efficient medium to ensure the effective communication of information messages inserted within the program as spot announcements in support of DoD internal information themes, goals and objectives. DMA AFN-BC mission tasking per DoD Instruction 5120.20 is to support the Internal Communications mission of the Department of Defense by providing a broad range of information and entertainment programming to DoD personnel and their family members overseas, thus attracting an audience for Internal Communications messages placed within AFN programming.

6. Performance Requirements:

The Enterprise Automation system shall be scalable. The base requirement includes only the products and services to successfully provide the Network System. The Affiliate systems are separated as Government Options which may or may not be exercised all or in part at a later date.

6.1 General Requirements -The Network: The Contractor shall design, engineer, furnish, configure, integrate, train, test and commission all hardware, software and materials necessary to provide an Enterprise Radio Automation System in accordance with this

Performance Work Statement (PWS). The Network System shall be installed at the

AFN-BC in Riverside California and provide automatic redundant On Air Automated playout; studio live assist; Wheatstone AoIP Router control; content acquisition;

editing, production and assembly; traffic; scheduling; alibi logging, play-to-air and archive storage both locally and shared through a secure cloud based solution.

6.1.1 Cueing. The AFN-BC Radio cueing process uses General Purpose

Interface (GPI) delivered from the Provider and converted to IP through the

Wheatnet IP Routing system. Essentially AFN-BC is an Affiliate to many content providers. AFN-BC also creates cues through sub-audible .wav files and/or XML to control events in affiliate automation playlists and/or the

AFN 360 Streaming Radio services hosted by Triton Digital. A replacement of sub-audible tones with a more elegant and modern solution (for example, digital signaling) is desired, however the sub-audible and proposed replacement shall operate in parallel while the Affiliate stations remain on their legacy systems.

6.1.2 Because this is an Enterprise system, all files and functions shall always be accessible from any workstation at the AFN-BC and remote locations. AFN-BC as the Network, shall have the capability to access, monitor and control Affiliate station automation systems in such a manner that the Network Operator is presented with the same features that the

Affiliate Operator has available. Remote operation shall be inherent to the system, logging in using a remote control application (e.g. Teamviewer, Remote Desktop) is less desirable.

6.1.3 In addition to the Affiliate performing their own Automation scheduling, the AFN-BC shall be able to deliver complete ready-for-air automation logs, should the need arise. Currently AFN-BC delivers logs from a 3rd party scheduling application and those logs are merged into the local standalone automation systems. Administrative rules shall be provided to customize which remote features or capabilities may be enabled or disabled.

6.1.4 It is important to note that the Government plans on using our existing Defense Information Systems Agency (DISA) Virtual Private

Network (VPN) to connect the Network and Affiliates. This connection would enable Network access to each of the Affiliate systems as well as content sharing among the stations, cloud storage of content, and perhaps more as the system evolves. The DISA VPN has proven itself to be fairly unreliable, therefore it is imperative that every system is capable of operating completely on its own; there shall be no reliance on

VPN connectivity for normal operations. Further details on how the

Government networks are configured and the rules in place to segregate those networks would be discussed with the successful Vendor during the design reviews.

6.1.5 The System shall be fully compatible with the existing Triton

Digital AFN 360 internet radio streaming equipment and processes.

Additional information is provided in Section 6.2.3.

6.1.6 The System and its subcomponents shall be compliant with and work within the Security Technical Implementation Guides (STIG) restrictions/requirements as established by DISA and US Cyber Command

(CYBERCOM), ( https://iase.disa.mil/stigs/Pages/index.aspx ) as well as the

Broadcast Network parameters and policies in place at the AFN-BC. Any and all future software updates provided as part of this contract shall be STIG compliant; the Vendor shall provide a fix for any software updates that cause the system to fail a STIG compliance inspection. Proposed Cloud solutions shall also comply with DOD Cloud Computing Security Requirements Guide

(SRG). Network hardware should be on the DISA Approved Product List

(APL) with fully manageable switches supporting 802.1x, port security, and

802.1Q allowing integration into our enterprise network.

6.1.7 The System shall record/ingest audio and metadata into and playback from hard disk drive storage systems (Specific Automation, Storage, and Routing requirements are described in separate sections).

6.1.8 The System shall be designed with redundancy for all subsystems and network appliances to maximize mean-time-between-failures (MTBF) where economically feasible. The System’s architecture may include primary and backup (hot standby) audio servers, primary and backup database servers, primary and backup storage arrays, automatic network reroute feature for port failures, and redundant power supplies. The System shall allow for system updates to be applied to the idle redundant subsystem, monitored for success and placed into the primary air chain while the primary https://iase.disa.mil/stigs/Pages/index.aspx is updated. The Contractor shall determine the LAN/WAN topology and components for the best redundancy throughput. The Servers provided shall make use of the latest hardware and software technologies to limit the footprint of the system while maintaining redundancy. The servers, workstations, and storage arrays shall be connected using the system manufacturer’s LAN/WAN design. The design shall include professional, enterprise-grade Keyboard/Video/Mouse (KVM) units, capable of HD resolution (1920x1080), for accessing all provided computers. All

Workstations (WS) and Servers shall be delivered with the latest Operating

System (OS), Windows 10 and/or Windows Server 2016, with all known OS, software suite and application flaws addressed and corrected. All WS’s and

Servers shall, as a minimum, be delivered with a CD/DVD -Read/-ReadWrite

(-R/-RW) drive. All provided WS’s and applications shall be Windows based. Audio servers shall be capable of simultaneous on-air and production functions with no data throughput degradation. All Enterprise Workstations shall be able to create, schedule, modify, and execute format playlists and have record, edit, and playback production capability.

6.1.9 The local System shall be synchronized to Government provided

Network Time Protocol (NTP) clock for accurate timing. The System shall automatically shift between Daylight and Standard Time in all time zones worldwide and reset Play/Record schedules to the correct time/place. The

Contractor shall explain how they propose to meet this time change requirement.

6.1.10 The System shall include traffic management/scheduling for spots and short-form interstitials. The system shall include music management/scheduling.

6.1.11 The System shall include production functions for record, edit, save, store/forward both internally at the AFN-BC and at all remote affiliate stations.

6.1.12 The System shall include recording scheduling and on-air program log scheduling functions for creating clocks and playlists – both internally at the AFN-BC and at all remote affiliate stations.

6.1.13 It is desirable for the ability to select the language the system displays. The available languages should be those that are common to the

Affiliate locations listed in Section 14.2.

6.1.14 The Contractor shall provide integration services so the ERAS seamlessly replaces the existing Automation system to include, in part, schedule creation, file transfer of existing media and Wheatstone AoIP

Router interfacing.

6.1.15 The Contractor shall supply all hardware, software, Ethernet appliances, custom cabling, installation and integration services to provide a turn-key ERAS.

6.1.16 All hardware provided to satisfy the requirements of this PWS shall be Commercial-off-the-shelf (COTS) equipment and appliances with minor modifications made to satisfy the unique requirements of AFN.

Manufacturers of supplied hardware shall be industry recognizable brands

(e.g. Dell, HP) with an assessable reputation of reliability and sustainability in the United States broadcast and Information Technology (IT) industries.

6.1.17 The Contractor shall understand that the AFN Affiliates located around the world may have differing power supply and connection requirements. Providing equipment with universal power and compatibilities with existing, varying infrastructures is the Contractor’s responsibility.

6.2 Task 1 - Specific Requirements – The Network AFN is responsible for selecting an

ERAS for the creation and broadcast of 24 full-time radio channels over the worldwide AFN satellite and internet streaming networks. Variable approaches are allowed for meeting the requirements of the PWS, but any variances must meet the requirements as functionally described in this PWS.

6.2.1 Subtask 1.1 - Content Acquisition

6.2.1.1 The System shall use commands written in record schedules to acquire radio programming and attendant metadata, digitize as needed, and route signal feeds for automatic and manual recording (user selectable) to storage and/or for direct, simultaneous play out by multiple on-air stations. The Contractor shall provide 24 “record lists”, preferably not consolidated to a single machine. The record/file ingest scheduling function shall be native to the system; no external, third party scheduling software is permitted.

6.2.1.2 The system shall be capable of capturing cues associated with program audio during the program acquisition phase. These cues shall be visible for producers using an editing screen to manually prepare a show for air. They shall also serve as “markers” for the system to automatically build multi-segment programs. Variations are allowed, but two typical approaches are to 1) trim off a user-definable length of audio before the cue or, 2) set a segment End-of-Message

(EOM) at a user-definable point before the cue. In either case, program segments

(without commercials) are saved and staged in pre-existing rotation lists for later playback as complete shows with AFN spots inserted automatically.

6.2.1.3 Should a problem occur or if maintenance is required on any program acquisition WS and/or its corresponding audio server, cabling, etc., this system shall provide for a backup capability, which will allow recordings to be made during the maintenance or error condition. This does not mandate that each auto record channel has two PCs with each running identical record schedules simultaneously. It means that any WS on the LAN is quickly configurable to take over all of the functions in the event a “main” platform component is off line. If a problem occurs in the Main server/storage array during program recording, the

Contractor shall propose a contingency plan – perhaps involving simultaneous recordings to the backup server/storage array.

6.2.1.4 The system shall provide for manual record schedule builds and modifications on any WS connected to the LAN.

6.2.1.5 The system shall allow schedules to be changed and/or reloaded at any time, even while files are recording.

6.2.1.6 Each schedule, whether hourly, or daily, shall automatically chain

(advance) to the next hour or day with no Operator manipulation required.

6.2.1.7 The System shall provide for the automatic and manual recording of background audio programs from several, user-selectable sources including:

satellite receivers; IP (including a Secure File Transfer Protocol (sFTP) capability);

LAN/WAN; fiber; telephony; and in-house, Operator-based input. It shall also be capable of direct ingest from external digital sources. Note: While the system is required to ingest audio files acquired from the Internet, only specific provided “Internet Gateway” WSs shall be configured to reach the public internet. These systems will be required to undergo a Government Security

Technical Implementation Guide (STIG) process before they may be connected to the Government Network. The six (6) required Internet Gateways shall also be fully compliant and configured with Active Directory and shall be configured in a “multi user” design compatible with the Government Common

Access Card (CAC). Users shall have the ability to login with their CAC and maintain their same user experience, preventing a single, shared user account which is in violation of the DOD STIG.

6.2.1.8 The system shall include an IP import program/application with several admin-created profiles for watching internal/external audio file folders and automatically ingesting the files into their respective categories in storage.

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.

6.2.1.10 The IP import program/application shall provide an on-screen status display for quick visual review.

6.2.1.11 The IP import program/application shall create daily logs as .txt files.

6.2.1.12 The system shall fully interface the National Public Radio (NPR)

“Content Depot” process used at the AFN-BC.

6.2.1.13 The system shall be able to record/ingest real time metadata belonging to an audio file and store the related data for call up in-house and/or for distribution to affiliates.

6.2.1.14 Recordings must be made without adversely affecting each other, any On-Air play out, or overall system performance. They shall be capable of recording through a rollover through midnight, i.e. a program that starts recording at 11:50 p.m. on one day’s schedule should keep recording even after the next day’s record schedule loads.

6.2.1.15 The system shall allow any file to play to air while it’s recording within a second after the record start command. Files coded as “play while record” shall remain available to any/all formats i.e. they shall not be restricted for “local use only” by one format’s PC.

6.2.1.16 Recorded files shall be mapped to their respective locations in the storage array(s) with user-definable overwrite permissions as granted by the system administrator.

6.2.1.17 The system shall be capable of encoding incoming audio in mono or stereo as MPEG 1, Layer 1, Layer 2, or Layer 3 as well as PCM, and WMA.

The available sample rate range shall be 8 to 48kHz and the available bitrate range shall be 5 kbps to 320 kbps. The encoding function shall be able to be applied globally, by category, or on a file-by-file basis.

6.2.1.18 The system shall not require that all files be of the same compression/sample rate in order for the files to play out.

6.2.1.19 All stored audio files shall be available to all WS all of the time for play out/edit, etc.

6.2.1.20 The system shall create execution logs for each record channel to accurately account for all events in a channel’s recording day – including but not limited to: audio and control (cueing, relay closures) routes; macro switches; start, stop, record commands; and errors encountered before, during, and after recordings.

6.2.1.21 Logs shall provide easy-to-read diagnostics to help System administrators and/or maintenance identify malfunctions and failures.

6.2.1.22 Logged events for each record channel shall be displayed by date and time for each day and each day’s log will be a separate file.

6.2.1.23 Logs shall be kept in their directories indefinitely until purged manually by a system administrator and/or automatically using administrator authorized user-defined parameters.

6.2.1.24 Execution log files shall be written to either a local or network hard drive and shall be exportable to a printer, portable media as ASCII text or convertible to ASCII text for viewing/printing on equipment not attached to the

LAN.

6.2.1.25 The system shall be capable of displaying a record schedule and its execution log(s) on one screen at the same time.

6.2.1.26 The system shall include a method for capturing and storing on-air confidence return (Alibi) audio for all formats. Each shall be recorded 24/7 in one-hour increments. The recordings shall be MP3, 44.1Hz, 16 bit, stereo, 128kbps.

Each hour-long file shall be easily exportable for review and/or, editing. There shall be a shortcut created for each unit that can be put on any PC desktop on the

ERAS LAN/WAN. File sets for each format shall be stored for 60 days. Operators shall be able to “Save”/Save As” each hour-long file to a location so they can open it for review. Files shall be playable with WMA, and shall be editable with the

System’s internal editor and/or programs like Adobe Audition.

6.2.2 Subtask 1.2 - Production, Edit, and Assembly

6.2.2.1 AFN currently utilizes Adobe Audition for Audio Production, Edit, and Assembly under an existing enterprise software license; no additional licenses are required. The proposed system shall include an interface to ensure complete interoperability between Audition and the ERAS.

Continuing to utilize Audition is highly desired; however proposed

Production, Edit, and Assembly alternatives shall detail specific advantages so an informed decision can be made during the proposal review. Alternative

Production, Edit, and Assembly functions shall be native to the system; no external, third party software is permitted for this requirement. The Adobe

Audition interface or proposed alternatives shall provide AFN Radio

Operations the following capabilities at a quantity of 10 “seats” for Audio

Production, Edit, and Assembly.

6.2.2.2 The system shall provide an on-board basic production/editing capability that allows producers to record audio media and meta-data from multiple sources into storage, browse all files in storage, edit audio files, and assemble shows with standard cut, paste, insert, gain adjust, EOM set/adjust, time squeeze expand.

6.2.2.3 The system shall provide a file and directory import feature with

“start/go” and “cancel” import functions.

6.2.2.4 The system shall provide an import CD feature with “track select,”

“start/go,” and “cancel” import functions.

6.2.2.5 The system shall be capable of encoding incoming audio in a multitude of selectable formats to include mono or stereo, MPEG 1, Layer 1, Layer 2, or Layer 3 as well as PCM, and WMA. The available sample rate range shall be 8 to 48kHz and the available bitrate range shall be 5 kbps to

320 kbps. AFN currently stores audio in the existing system as MPEG 1, Layer 3 - 44.1kHz sample rate, 256 kbps bit rate, stereo. Should the proposed

System require a new standard, the new pros/cons of the new standard should be described as part of the response to this PWS and shall be compatible with existing AFN systems. In addition, any necessary file conversion of the existing AFN stored content would be the Contractor’s responsibility.

6.2.2.6 All parameters shall be system administrator-definable. An integrated transcoding/format converting solution shall be offered to ensure all audio recorded into the system complies with the sample/compression requirement.

6.2.2.7 Editors shall be able to mark in and out points of file segments for cut, paste, move, replace, insert, delete, etc. with at least 20 levels of “undo.”

Editors need the ability to preview changes they’ve made to projects without having to take extra steps, i.e. saving the project under a new name so it can be played back to hear the edit(s) then resaving again to hear the next edit, etc.

6.2.2.8 Once a segment is marked for removal, Editors shall be able to insert another audio file (such as a spot) in the segment’s place. To do this, Editors shall be able to see a list of audio files from which they can select a replacement element.

6.2.2.9 A program timer shall help the Editor monitor the project’s runtime by automatically tracking the runtimes of all project-related audio file elements as they’re deleted, inserted, etc. File runtime length is depending on the material being worked.

6.2.2.10 The System shall offer a “squeeze/expand” function with automatic pitch adjustment to make projects fit their required maximum runtimes.

6.2.2.11 The “squeeze/expand” function shall provide adjustments by -hour:minute:second.100s of second.

6.2.2.12 The “squeeze/expand” function shall executable globally, in a break-by-break and/or a file-by-file basis and shall not introduce discernable artifacts or distortion to the audio during playback.

6.2.2.13 The System shall allow any file to play to air while it’s being recorded, edited, or assembled.

6.2.2.14 This function shall provide an integrated audible “scrub” utility capable of accessing files of up to four hours in length.

6.2.2.15 This function shall allow an Editor to save a program’s audio and

Edit Decision List (EDL) elements as a new file or as an overwrite of an existing file with the same name (with user-definable prompts). The save window shall allow for “Save” or “Save As.” The System shall also allow for the creation of programs and/or program categories that are “write protected” to prevent accidental deletion or overwrite.

6.2.2.16 The ERAS shall provide several techniques for researching and retrieving media assets in the audio database. File information shall include:

AFN generated house numbers, file name, file category (music, spots, jingles, liners, music, program, temporary files, test tones, etc.) description, duration, default [total project duration], out cue, start/kill date, and other metadata info. Fields requiring exact entry (time, date, etc.) shall be user-definable.

All other fields shall allow for at least 40 characters of information. The database search shall be by all categories or by individual category.

6.2.2.17 Non-audio files such as screen configurations, daily record/play lists, logs, etc. shall - with proper administrative permissions - be quickly and easily retrieved from any WS on the system LAN/WAN.

6.2.2.18 The system shall allow for Category Names longer than 3 characters.

6.2.2.19 To automatically forward completed audio projects to local and/or cloud storage, the system shall include professional, enterprise-grade file sync and backup software, fully customizable with administrator permissions.

6.2.2.20 The system shall be compatible with automation/XDS/RX feeds.

6.2.2.21 The system shall auto-normalize audio levels on audio import.

6.2.2.22 The system shall automatically set trim-in, trim-out, segue (EOM) and intro during import.

6.2.2.23 The system shall use embedded tags in the audio file to populate title and artist fields during media file import.

6.2.2.24 The system shall include a metadata/tag editor.

6.2.2.25 The system shall provide customizable media info fields.

6.2.2.26 The system shall provide enterprise connectivity, enabling immediate updates of edited products to all stations across enterprise.

6.2.2.27 The system shall allow for customizable categories.

6.2.2.28 The system shall include an music ripper to ingest songs in definable format & import metadata.

6.2.2.29 The system shall provide option of viewing media as a waveform.

6.2.2.30 The system shall allow moving and/or copying audio files between categories.

6.2.2.31 The system shall allow Editors to play, edit, export, or remove any file directly from its Category list.

6.2.2.32 The system shall allow setting a file’s Active and Expire date/time.

6.2.2.33 The system shall allow files to be saved as an individual cut or as a

“rotation” (used for jingles, liners, IDs, promos). Currently, there are challenges with using rotations for military news files. The new system shall address these challenges and correct them.

6.2.2.34 The system shall provide a one-button database refresh function.

6.2.2.35 The system shall provide a manual record function with stop, pause, play, and save, controls.

6.2.3 Subtask 1.3 - Show/Satellite Scheduling

Deliverable: Show/Satellite Scheduling System

6.2.3.1 Scheduling shall be done with an integrated or 3rd party traffic/scheduling program.

6.2.3.2 The system shall also allow for creating schedules manually with an integrated log building application or similar.

6.2.3.3 When manual programming mode is used, all feeds (network satellite, streamed feeds) shall be available on screen for click/replace or drag/drop.

6.2.3.4 When manual programming mode is used, all audio files shall be available on screen for click/replace or drag/drop. Audio files shall be sortable/searchable through a multiple level custom sort by “All,” “Start,”

“Length,” “Artist,” “Title,” “Category,” “Cut #.”

6.2.3.5 Once put in a schedule, all events shall be moveable by drag/drop.

6.2.3.6 All files shall be playable from the files field for audition purposes.

6.2.3.7 All files shall be playable from the schedule being built so an

Operator is able to hear the event sequence.

6.2.3.8 All events shall be drag & drop within the schedule being built with “Overwrite,” “Insert Above,” “Insert Below.”

6.2.3.9 All schedules shall show files that are expired, inactive, or missing from database as well as the when the events are scheduled so they can be easily found/replaced.

6.2.3.10 Schedules shall be searchable by “All,” “Start,” “Length,” “Artist,”

“Title,” “Category,” “Cut #”

6.2.3.11 All automation commands shall be available on the same screen – event start time, event duration, available feeds, hard starts, fade starts, announcer stack load commands, and memo.

6.2.3.12 Changing announcer stack within an hour shall be allowed as a timed event with no effect on audio.

6.2.3.13 Log duration shall be displayed – both for the current hour being scheduled and the current day that contains the hour.

6.2.3.14 The system shall provide a way to fade out of all audio events – external (network satellite, streamed feeds) or internal (audio files).

6.2.3.15 Because we don’t always get a dedicated first-position break relay from Providers, the system shall provide a method to start our breaks using pre-break liner/ID relays.

6.2.3.16 25/35 Hz sub-audible cues shall (ultimately) not be used for

Affiliate automation breakaway cues. See Paragraph 6.1.1.

6.2.3.17 The system shall interface completely with the “AFN 360” internet streaming function, currently Triton Digital, thereby providing audio and data to the existing 360 systems. Currently On Air formats are routed via the

Wheatstone AoIP Router to satellite encryption systems and Government-owned Triton Stream Servers. Those stream servers also receive Automation metadata for affiliate cueing and Album/Artist/Song Now Playing Data as

XML data over UDP. Certain user defined parameters are required, such as what data is included; the number of instances the data is resent during the event and which IP Addresses the XML data is delivered to. The data shall remain intact during the failover to a redundant automation server.

6.2.3.18 The system shall also provide a separate output file which shall contain at least the current event and the following 40 events and provide at minimum Artist, Song Title, Start Time and Duration. This file is handed off to another AFN Contactor where is reformatted and delivered to AFN satellite Set-top-Boxes (STB). The Vendor shall be prepared to customize this output file to meet the specifications of the STB middleware provider at no additional cost the Government. The specifics of how the file must be formatted will be discussed further with the successful Vendor during the

Design Reviews.

6.2.3.19 AFN 360 affiliate spot breaks shall be started by XML simultaneous with affiliate automation breakaway command.

6.2.3.20 AFN 360 Display Commands (station/channel ID, show title) shall not be executed with an audio file (silent file with a short EOM).

6.2.3.21 AFN 360 Rejoin Commands (stop affiliate spot playback at program rejoin) shall not be executed with an audio file (silent file with a short EOM).

6.2.3.22 The system shall provide various ways to start events – network relay, sequential, hard start by time, hard start following fade. Fade duration shall be user-definable.

6.2.3.23 The system shall allow use of informational “Memo” lines in schedules.

6.2.3.24 The system shall provide a “find/replace” capability to make quick changes to existing schedules without having to unschedule/reschedule them or having to export them to another computer.

6.2.3.25 Schedules currently on air sometimes need to be changed “on the fly.” The System shall provide a means for making these changes without taking the schedule(s) offline and format audio off air.

6.2.3.26 Schedules shall be exportable to common word processing and spreadsheet programs.

6.2.3.27 When filling a break segment with program elements, only an exactly timed set of files shall be allowed. Entering anything more or less than the preset runtime definition shall result in a visual alert to add or remove audio files to match the correct time setting.

6.2.3.28 The system shall provide log “back time” capability.

6.2.4 Subtask 1.4 - Music Scheduling

6.2.4.1 The system shall provide centralized management of music scheduling for multiple formats at individual local, and global (network) broadcast stations across multiple time-zones. For the AFN-BC Network system, all 24 On Air stations shall have these Music Scheduling

Capabilities. Note: The proposed Music Scheduling solution shall be compatible with Affiliate stations as they remain on their legacy automation systems. For example, logs generated by the proposed system shall also have the option to automatically export in a format that can be used by the existing

Affiliate AudioVault playout systems.

6.2.4.2 The system shall have customizable music coding and fillable fields.

6.2.4.3 The system shall have a method to control cross-station song separation to prevent same song airplay over a given timeframe across multiple stations and time zones.

6.2.4.4 The system shall have automatic error detection and correction to identify and repair schedule conflicts on each station.

6.2.4.5 The system shall fully integrate with traffic management system and digital media storage library.

6.2.4.6 The system shall provide a centralized digital media library and media database that is shared by multiple affiliate stations, multiple formats.

6.2.4.7 The system shall provide for instant global updates that reflect added, deleted, moved, or edited media and schedule changes.

6.2.4.8 The system shall provide ability to view and edit multiple affiliate stations at any time.

6.2.4.9 The system shall have definable and scalable user access to the music management/ scheduling system.

6.2.4.10 The system shall have the ability to define day-parts to digital media (songs, spots, etc.) for different affiliate stations across multiple time-zones.

6.2.4.11 The system shall have definable start, move, and rest dates for long-term scheduling

6.2.4.12 The system shall have integrated automation commands in schedule to switch from live or pre-recorded XDS/RX feed to studio.

6.2.4.13 The system shall be able to automatically adjust schedule to fit within the hour, or between “hard-starts” (auto-backtime).

6.2.5 Subtask 1.5 – Traffic

6.2.5.1 The system shall provide centralized management of traffic for individual local, regional, and global (network) broadcast stations across multiple time-zones.

6.2.5.2 The system shall integrate with music scheduling system and digital media storage library.

6.2.5.3 The system shall provide instant global/ enterprise updates to reflect added, deleted, or edited spots and/or schedules.

6.2.5.4 The system shall have the ability to view and edit multiple affiliate stations and/or days at any time.

6.2.5.5 The system shall have the ability to create, schedule, and track local, regional, and global (network) live copy/ in-studio content or

“readers”.

6.2.5.6 The system shall be able to define day parts to spots to target various times for different affiliate stations across multiple time-zones.

6.2.5.7 The system shall provide user-definable start, kill, and rest dates for long-term scheduling

6.2.5.8 The system shall provide user-definable spot rotation and separation criteria- title, artist, topic, client, producer, etc.

6.2.5.9 The system shall provide customizable reports to track as-run info for individual spots, spot groups (topic), client, producer

6.2.5.10 The system shall provide automatic error detection and correction to identify and repair schedule conflicts on each station

6.2.5.11 The system shall provide a database to maintain and manage client information, orders, invoices, and history.

6.2.5.12 The system shall provide user-definable and scalable user access to the traffic management system.

6.2.5.13 The system shall provide secure login to the system via internet and be compliant with DISA requirements. Ideally, a vendor provided secure web login page whereby specific AFN public IP addresses would be whitelisted.

6.2.5.14 The system shall provide global/ enterprise updates to reflect added, deleted, or edited material.

6.2.6 Subtask 1.6 - Automated On Air

6.2.6.1 Based on commands from daily play out schedules, assembled by

AFN Radio personnel, the system shall air programming from satellite receivers, compatible external devices (PC, digital audio device) as well as audio from the System’s hard drive storage in support of an initial cadre of

24 full-time format channels, with future expansion capabilities to at least 30 format channels.

6.2.6.2 The on air play out function(s) shall be native to the system.

6.2.6.3 The System shall duplicate each format’s play out schedules simultaneously on main and backup playout WSs. When there’s an automatic (silence sense, hardware or software failure, network connectivity loss, etc.) or manual switch to/from the main and backup WSs, all incoming/outgoing audio and incoming/outgoing cue control follows this switch and any on-air audio dropouts that occur during the switch shall be less than 3 seconds long. The Contractor shall address their method for keeping formats on the air when these “switch” events occur.

6.2.6.4 Announcer stack configurations shall be synchronized between the workstations so IDs, liners, jingles, etc. continue to play normally even when a switch occurs.

6.2.6.5 The system shall provide for manual play out schedule builds and modifications on any WS connected to the LAN based on administrator-assigned user rights.