Q A_FINAL.xlsx

XLSX spreadsheet 27 KB Posted May 19, 2015

Attached to: DVB-S2 Transmission System Federal contract opportunity
Solicitation number: 15-233-SOL-00119
Issued by: Department of Health and Human Services Program Support Center

About this file

From the source

Q A FINAL

View the file

Other files for this federal contract opportunity

Other files attached to DVB-S2 Transmission System, newest first.
File	Type	Posted
15-233-SOL-00119_000002.PDF	PDF	May 19, 2015
15-233-SOL-00119_000001.PDF	PDF	May 8, 2015
Past_Performance_Questionnaire.docx	DOCX document	Mar 23, 2015
15-233-SOL-00119_BASE.PDF	PDF	Mar 23, 2015
Questions_and_Answers_Template.xlsx	XLSX spreadsheet	Mar 23, 2015

On GovTribe

Work with this file on GovTribe

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

Sheet1

No.	Question	Solicitation Reference	Answer
1	Is it required only one Central CAS Platform controlling the four transmission systems or Is it required one CAS Platform per transmission system?	4.1.4	A Single CAS system. A central CAS system containing the complete decoder database is required.
2	• Related to IP Multi-Protocol Data Encapsulated streams

o Is Scrambling required for those items?

o Are those streams intended to be used in STBs ? What purpose?

o Are those streams intended to be used in other devices than STBs?

3.1	Not encrypted. Scrambling of the Data streams is desired. AFN currently uses Kencast and DCB systems connected to the existing PowerVu System. Serial data is received by a decoder and handed off to a data terminal for display and/or print. Streams currently include the Stars and Stripes Newspaper and Burli Newsroom data. AFN understands serial is a thing of the past but maintains a requirement to deliver these data streams. Streams are for use at the Affiliate level, not headends or DTH.
3	Is AFN aware that they need to coordinate directly with Cisco all required work/modifications in order to assure that complete platform / decoders are in 100% DVB Simulcrypt compliance mode?	4.1.1	AFN requires a complete system to include coordination and integration with the existing system manufacturer to provide a solution which maintains deliery of the complete suite of AFN content to the currently fielded MPEG4 Compliant decoders.
4	What is the estimated number of STB per year until reach 300K?	4.2.1	Estimates: 65,000 Cisco set tops deployed which are DVB-S2 compatible. AFN anticipates 2,000 to 3,000 decoders per year growth, on average, following the initial spike when we switch to DVBS-2.
5	For Push VOD, OTT services, addressable ads and cloud DVR, does AFN want this now from the start? Or it is planned to be added at later stages?	4.2.3	System deployed should provide path to these services. No plans for service at this time. Said services are desired at a later date, however shall be demonstated as current technology.
6	For OTT services: what features (like live, catchup, EPG, VOD etc…) and to what devices (like Android Tablets, iOS Phones etc..) are required.	4.2.3	System deployed should provide path to these services. No plans for service at this time. Features shall include a catchup service, push VOD and be available at the STB. Delivery to devices like Android Tablets, iOS Phones etc.., is also desired. These services are desired at a later date, however shall be demonstated as current technology.
7	Related to Cloud DVR, could you provide more details on what is expected here?	4.2.3	System deployed should provide path to these services. No plans for service at this time. The ability to view programming available in a cloud enviornment is a desired feature. These services are desired at a later date, however shall be demonstated as current technology.
8	Could you please clarify/give more details of following items?

• Control of channel information being received by all supported decoders in the field

• Full control over all decoder management operations

• Scheduled CA/Cue signal trigger capability

• Channel Service Replacement

4.2.3 Refer to section 4.3.6 for reporting needs.

Desire to know status of decoder - active, connected to the network? The ability to: force tune a decoder or group of decoders to a specific channel, receive feedback from the decoder as to which channels are being watched (metrics), receive an acknowlegement from the decoder that it is active, change decoder receive parameters remotely, change or blackout programming on a decoder or group of decoders and force the decoder to alternate programming on a scheduled basis.

9	Is the intention of AFN, develop their own APPs and install those APPs into the STBs ??	4.3.7	Yes, anticipate applications to be created. Will need the ability to download apps to the set top. The desire is for the STB be compatible with popular existing APPS such as Netflix, Hulu, Amazon, etc and for the capability to conveniently add customizible APPS that are created for AFN use, AFN360 streaming radio, for example. The development of those APPs is to be determined.
10	For AFN and DTS system, it is mentionned respectively 12 and 4 channels, SD or HD. We understood that all channels needs to be configurable in HD or SD. At launch, what are the specific number of HD and SD channels for each system?	3.0 / 4.1.2 / 4.1.3	Four unique systems. DTS is SD only. Sat Net all HD.

DTS should be upgradeable to HD.

H.264 will be utilized encoding. AFN DTS 4 channel systems would be solely SD at launch. Content for the AFN 12 channel systems is currently migrating to HD and we intend for the those systems to be fully HD at launch, however the potential exists for some channels to remain SD.

	11	There is no SD resolution specified (480i or 576i)	4.1.1	480i
	12	Could you detail the RDS "data pass through" need ? What is the exact workflow ? Do you have already some RDS equipment, if yes, what kind of equipment ?	4.1.2	RDS is not DVB-S2 compatible. Desire to have artist, title and album cover displayed for music channels. Utilized technology which is compatible with DVB-S2 AFN will provide Artist and Song title data in a combination of serial and XML form originating from our content providers and Radio Automation. Should our FM stations desire to push that data to a recieve device, the decoder shall be able to deliver that data to the station. No equipment on the receive end exists at this time and is not a requirement of this RFP.
	13	What is the exact need for the 128 GPIO contact closure ? What kind of interface do you require with the automation systems ?	4.1.2	The GPI/O requirment is to trigger automated commercial break insertion at the affiliate level. The automation systems (TV and Radio) have the ability to provide dry contact closures. Trigger utilized to identify spots for Ad / program insertion. Downstream network is configured for GPI trigger and will not be able to utilize SCTE-104 or SCTE-35 messaging initially.
	14	You require in the CA part OTT, Push VOD and Cloud DVR, but there is no specification about that in the Headend part. Do you require such service from Day 1 ? And If yes, what are the specification for the Headend portion?	4.2.3	Said services are desired at a later date, however shall be demonstated as current technology. These technologies are desired at the DTH level and are not expected at the headend level at this time.
	15	There are specs related to SCTE35 and SCTE104, and your existing system performs a kind of ad replacement. There is no specification about this Ad replacement. Do you require such service from day 1 ? If yes, could you detail the need ?	4.1.2 / 4.1.3	See item 13 above. STB Ad Replacement is a service desired at a later date, however shall be demonstated as current technology.
	16	The specification for audio only stream requires "visual data, including album art, artist and song. Such metadata are not part of the DVB-SI tables, so on the headend part, there is not the possibility to send such data as "generic data". This could be achieved by kind of "private data" to be managed by the STB middleware, but this requires integration. Could you explain this requirement further ?	4.1.2	See item 12 above. AFN will provide Artist and Song title data in a combination of serial and XML form originating from our content providers and Radio Automation. AFN desires that data be displayed on a television when a DTH customer tunes to the audio only (radio) channels in a format similar to those currently available with major content providers in the US.
	17	Please confirm that the Headend electronics for all four systems will be deployed at your Riverside, CA location.
If not, which gear will be deployed at which location?	4.0.2	All four systems will be installed at Riverside CA
	18	For the deployment, do you expect that the Headend electronics for all four systems will be deployed at the same time (i.e., a single continuous project)?
If not, what is your expected deployment schedule for each system?	4.0.2	Continuous project. One system to be lit at a time. PWS Para 5.2.3 says we want them staggered in this order: Atlantic, Pacific, DTS Pacific, DTS Atlantic. ..."Each system is required to pass full acceptance prior to scheduling of the next system installation phase"
	19	Are these currently under warranty/SmartNet services?	3.0 Scope: 65,000 existing Cisco decoders consisting of D928, D9854, D9865H decoders	No.
	20	In 3.0 it is stated that the contractor shall furnish four systems “replacing” both the two AFN SATNET systems and the two DTS systems, While in section 4.0 the RFP states that the existing CA system will need to be maintained as “the secondary CA solution”. Is this limited to the CAS (authorizations, rights, entitlements etc.) or will this require a parallel operation of the transmission systems? We would interpret this to be the reason for the SimulCrypt requirement.	3.0 Scope: furnish four systems. Two systems will replace the existing AFN Atlantic and AFN Pacific SATNET PowerVu transmission systems. Two additional systems will replace the existing Direct-To-Sailors (DTS) Atlantic and Pacific PowerVu transmission systems	The requirement is to replace the four systems, however the solution shall also contain the ability to Simulcrypt the existing PowerVu CA, which maintains delivery of the complete suite of AFN content to the currently fielded MPEG4 Compliant decoders. The solution shall not require a parallel operation of transmission systems.
	21	What is the nature of the data steams? Type of data, purpose etc. We interpret the data (since it is a push and there is a VOD requirement for the STB’s) as VOD information. Is this the case?	3.0 Scope:IP Multi-Protocol Data Encapsulated streams	The Data streams in use at this time do not relate to VOD. AFN currently uses Kencast and DCB systems connected to the existing PowerVu System. Serial data is received by a decoder and handed off to a data terminal for display and/or print. Streams currently include the Stars and Stripes Newspaper and Burli Newsroom data. AFN understands serial is a thing of the past but maintains a requirement to deliver these data streams. Streams are for use at the Affiliate level, not headends or DTH.
	22	Is there a requirement for EPG?	3.0 Scope	Yes. (Please see Para. 4.3.8) AFN currently uses a Divitech EPG, the proposed system shall be compatible with that system or offer an alternative.
	23	will DMA provide visibility to the existing architecture of the 4 transmission systems?	3.0 Scope	AFN will provide information unless considered proprietary to the current system manufacturer.
	24	Is the intent to match the existing channel structure (TV, Music, Data) or is the stream requirement different from the existing system?	3.0 Scope:Contractor shall plan to support the

following inputs to each system:

• 12 input channels, consisting as a combination of SD-SDI, HD-SDI, AVC, 1080i and/or 720p format video with embedded audio @44.1 or 48 KHz AES/EBU Audio

• 36 each stereo radio services 44.1/48 KHz (selectable) AES/EBU selectable Audio

• 6 discrete IP Multi-Protocol Data Encapsulated streams	Yes, the intent is to match the existing channel structure.
	25	Should we consider capability for expansion on any of the channel compliments? I.E. are there plans to add additional TV, Radio or Data channels in the future?	3.0 Scope	There are no plans at this time, however the proposed systems shall be capable of expansion.
	26	Are all four models of the 65,000 existing decoders spread across both AFN and DTS or are they specific to one system or the other?	3.0 Scope:This includes the full suite of
DVB-S2/MPEG-4 compliant decoders and 65,000 existing Cisco decoders consisting of D9824, D9854, D9858 and D9865H decoders	They are spread across all systems.
	27	Are all four existing cisco models “MPE” capable?	3.0 Scope: 65,000 existing Cisco decoders consisting of D9824, D9854, D9858 and D9865H decoders	AFN does not believe our models are MPE capable, but would prefer each vendor perform their own research so we do not mistakenly provide inaccurate information on this topic.
	28	Are both required or is this the vendors choice?	4.1.2 bullet 2 "embedded audio @ 44.1 or 48kHz	Both are required.
	29	Are both required or is this the vendors choice?	4.1.2 bullet 3 "user selection of joint or discrete stereo operation"	Both are preferred.
	30	Please define scope of Device Management in bullet 13	4.1.2 bullet 13 "Web-based GUI for device management"	A central GUI for managing the operation and monitoring the status of all software and devices within the system.
	31	Is this the video that is displayed with the audio channel selection. What is the source and nature of this visual data? Does this also get picked up at the D-Marc	4.1.2 bullet 15 "Audio only stream visual data, including album art, artist and song
information"	AFN will provide data in a combination of serial and XML form originating from our content providers and Radio Automation. AFN desires that data be displayed on a television when a DTH customer tunes to the audio only (radio) channels in a format similar to those currently available with major content providers in the US.
	32	Please define level of redundancy required	4.1.2 bullet 19 "Built-in redundancy for all major equipment and support items required
for on-air operation"	Vendors are encouraged to propose a level of redundancy necessary to meet the criteria detailed in Para 4.1.6.
	33	is there a 1+1 requirement for the modulator chain or is chain redundancy sufficient	4.1.2 bullet 21 "Primary and hot back-up DVB-S2 Variable Rate IF Modulators Distributing QPSK, 8PSK, 30MBaud w/ network redundancy switches.
Outputs required are L-Band, and 70 MHz with extended L-Band and L-Band monitoring desired"	AFN desires a primary and backup Modultor with a manual and automatic failover capability.
	34	is fixed monitoring sufficient or are both fixed and agile monitoring required	4.1.2 bullet 21 "Primary and hot back-up DVB-S2 Variable Rate IF Modulators Distributing QPSK, 8PSK, 30MBaud w/ network redundancy switches.
Outputs required are L-Band, and 70 MHz with extended L-Band and L-Band monitoring desired"	Regarding monitoring of the modulated output, we intend on connecting the L Band to a decoder for confidence monitoring of all channels.
	35	Is the closed captioning currently outsourced and should we assume that replacement of the current CC hardware is required or can the existing system be repurposed	4.1.3 DTS System: Closed Captioning compatible supporting SMPTE-334M and EIA-608	AFN requires the proposed systems to be compatible with the stated Closed Caption standards. All captioning is provided by our content providers or created locally upstream from the transmission systems. The proposed transmission systems shall pass closed captioning and the proposed STBs shall support closed captioning such that the information is available through both digital (HDMI) and analog ports.
	36	Captioning for the SATNET system states the requirement as “(analog and digital)”…Captioning for the DTS systems states the requirement as both SMPTE-334M and EIA-608. This appears to “effectively” be the same requirement…is there a difference in the compatibility and delivery requirement for captioning between SATNET and DTS?	4.1.2 SATNET System, 4.1.3 DTS System	There is no difference in the requirements.
	37	What are their requirements for Serial Data, is this for transmission if so under which standard	4.1.2 STANET Systems: Serial and IP Data transmission	AFN currently uses Kencast and DCB systems connected to the existing PowerVu System. Serial data is received by a decoder and handed off to a data terminal for display and/or print. Streams currently include the Stars and Stripes Newspaper and Burli Newsroom data. AFN understands serial is a thing of the past but maintains a requirement to deliver these data streams. Streams are for use at the Affiliate level, not headends or DTH.
	38	Please provide detail of “RDS Pass-Through	4.1.2 SATNET Systems:RDS Data pass through for end-to-end radio transmitter support of RDS to vehicles	AFN will provide Artist and Song title data in a combination of serial and XML form originating from our content providers and Radio Automation. Should our FM stations desire to push that data to a recieve device, the decoder shall be able to deliver that data to the station. No equipment on the receive end exists at this time and is not a requirement of this RFP.
	39	What is the intended use of the “128 GPIO”?	4.1.2 SATNET System: 128 GPIO contact closures are required for control of TV and Radio automation systems	AFN desires the ability to provide contact closures to the transmission system. At the receive end the STB would be required to output the closures to trigger the affiliate automation systems to play local content. Currently this is accomplished using sub-audible tones which are embedded in the audio upstream to the transmission system. The hardware associated with sub-audible encoding is outdated and utilizing contact closures is an option.
	40	Define the nature of “control of TV and Radio automations systems”? What automations system/s? what are they automating? What device control is necessary?	4.1.2 SATNET Systems:128 GPIO contact closures are required for control of TV and Radio automation systems	AFN desires the ability to provide contact closures to the transmission system. At the receive end the STB would be required to output the closures to trigger the affiliate automation systems to play local content. Currently this is accomplished using sub-audible tones which are embedded in the audio upstream to the transmission system. The hardware associated with sub-audible encoding is outdated and utilizing contact closures is an option.
	41	RFP notes that vendor will “provide connectivity from the D-Marc to the transmissions systems”…Is there documentation available for the D-Marc	4.1.5 Contractor shall assure the technical reliability of the service from the demarcation point (government provided HD, SD and data) to the output of the

modulators. This includes the encoders, multiplexers, modulators, content network management devices, associated hardware, software and ancillary equipment required to provide complete AFN Network transmission outputs delivered as ASI to

feed DVB-S2 modulators.	We may need more specifics as to what type of documentation is required. To perhaps clarify the requirement, AFN Television and Radio signals connect to the existing transmission systems' interconnect panels. Those panels are considered the demarcation point with AFN providing the input signals and the Vendor distributing those signals throughout the transmission system as needed. Television is currently terminated with BNC and Radio is XLR. Generally, specific details regarding the demarcation wiring is discussed with the successful Vendor during the design reviews.
	42	What are the requirements for SimulCrypt, do they require an encrypting multiplexer or will the Cisco DCM do that for PowerVu and the new CA system	4.2.1: Contractor provided Transmission Systems shall provide a central Network Security and Conditional Access Manager to control the
encryption/decryption of up to 300,000 individual STB’s and shall support DVB Simulcrypt.	AFN requires a complete system to include coordination and integration with the existing system manufacturer to provide a solution which maintains deliery of the complete suite of AFN content to the currently fielded MPEG4 Compliant decoders.
	43	Please describe intended use of VOD, OTT, Addressable ads and Cloud DVR services that are requested to be available with the CA system software and hardware…Are these all intended to be delivered via push via the data streams aggregated into the Mux output? Does this represent additional services not outlined in the other requirements within the RFP?	4.2.3: proposed CA System shall contain the necessary hardware and software to provide AFN the opportunity to take advantage of Push VOD, OTT services,
addressable ads and cloud DVR capabilities	AFN desires a solution that is capable of delivering these services at a later date, however they shall be demonstated as current technology. How these services integrate within the transmission system would be the responsibility of the Vendor.
	44	Is this a hybrid manual and automated authorization process? What is the required workflow?	4.2.4: AFN Connect is an internally developed customer portal and decoder authorization system to provide customers the ability to request decoder authorizations via the Internet and allow our Technologist staff the ability to receive, review and approve the requests.	AFN Connect is both automatic and manual; decoder action requests are created by multiple methods. The request generated by AFN Connect is delivered to the transmission system and the system is required to activate or deactivate the subject decoder or decoders accordingly. Please also refer to Para 4.2.5.
	45	define scope of integration with AFN Connect	4.2.4 and 4.2.5: Contractor shall provide systems integration with AFN Connect	AFN's software development department would require access to the proposed system API structure so the current AFN Connect software can be altered to communicate with the new transmission system. AFN Connect will generate a request across a wired network to the transmission system. The proposed system is required to perform the action requested.
	46	Are there existing apps that need to be considered	4.3.7 Apps:Proposed CA and accompanying compatible suite of STBs shall be capable of allowing remote installation of a variety of Apps	AFN has an App for Streaming Radio, AFN360. It is desired for proposed STB's with internet connectivity to have access to this app for streaming radio.
	47	What Traffic System/s are in use?	4.3.8	Broadview…(I didn't catch this.
	48	What Automation Systems are in use?	3.0	Imagine/Harris ADC
	49	What Equipment will require 3rd party control?		No list given…Will be addressed in design review should a tender be awarded.
	50	is the integrator responsible for generating Cue Tones (or their SCTE Equivalents) or just embedding in the SDI or Radio?	4.1.2	While there is no actual commercial insertion or DPI required, the proposed systems will need to support the unaltered passing of both SCTE 104 and SCTE 35 messaging as VANC Data. SCTE Message insertion (via GPI) is however desired and integrator should include in their proposal. There would be a requirement for 1 channel of insertion per video and radio stream.
	51	Does AFN specifically require MPEG 4 H.264 or will they consider HEVC for better bandwidth management?	4.1	MPEG 4 H.264 is required
	52	Define selectable as it pertains to statistical multiplexing	4.1.2	Enabling/Disabling of Statistical Multiplexing and Establish Statistical Multiplexing (I.E. bandwidth and priority).
	53	Define selectable as it pertains to HD/SD and/or 1080i and 720P	4.1.2	All encoders should support 480i, 720P and 1080i and allow selection between these frame rates either manually or via auto sensing
	54	Is the closed captioning currently a manual service or electronically generated and inserted?	4.1.2	Closed captioning currently outsourced and is inserted prior to hand off to integrator
	55	Can you provide detail regarding the usage of the 128 GPI/O?	4.1.2	128 GPI/O not actually needed. Currently less than 10 in use. Plan for 10
	56	SCTE 104 VANC messaging is presumably to be embedded in line with both the SDI and Radio paths?	4.1.3	Correct. 1 Channel of insertion per channel and radio stream as per question 4
	57	It appears that AFN connect will serve as the SMS for both the primary and secondary CA’s, is that Correct?	4.2.5	Correct. AFN Connect will be the subscriber management system (SMS) for all CASs in the SimulCrypt configuration
	58	Please describe the D-Marc and how the individual signal types are handed off?	4.1.5	BNC for Video / Either XLR or RJ-45 for AES (Integrators Choice) / Data is in serial form
	59	Can we see diagrams for the existing D-Marc?	4.1.5	Please issue a written request to contracting officer
	60	Can we see diagrams of the existing encode mux and air stages?	4.2.1	Please issue a written request to contracting officer
	61	Is a site survey possible?	5.1	No Site Survey is planned at this time
	62	Are the racks for installation of the new systems in the integrators scope?	5.1	With respect to racks…AFN will acquire racks and ship to integrator…Subsequently integrator will populate, configure, test, ship to site and finally install and connect to D-Marc.
	63	Where would they be installed?	5.1	Space provided by AFN to be discussed at design review should a tender be awarded
	64	Who is subsequently responsible for power and HVAC requirements?	5.5	Power and HVAC out of integrator scope with the exception that integrator will supply load requirements
	65	Can you define the programming that is in within each service…The RFP says the content is disparate…How so?		While there are some differences in some programs within each service. The difference by an large is only one of time delay.
	66	Please define the new schedule for completion and an idea of implementation requirements.	5.3.1	To be annouced at a later date on FedBizOps. Proposal dead line however is expected to be end of May or beginning of June
	67	What are the IT infrastructure requirements of the integrator?	5.1	Limited to only that which is required to support the design
	68	There is no mention of network infrastructure; security requirements, firewalls etc…Are there corporate LAN users that will need access to whatever broadcast infrastructure is implemented?	5.2	No requirement within the scope of the integrator expected
	69	Is there WAN connectivity required?	5.2	No
	70	Where will the traffic and automation users located?		Traffic and all other systems and people are located within the Riverside Facility
	71	1. What are the monitoring requirements? a. Stream? First priority as per ESTI TR 101 290? b. Closed Caption Insertion? c. Caption positioning d. SCTE messaging?	4.1.2 & 4.1.3	Did not address…We will need to submit this in writing
	72	Is SCTE 35 required as well as SCTE 104?	4.1.2 & 4.1.3	Yes
	73	Who will integrator personnel work with as well as manufacturer representative for API development as it relates to AFN connect?		AFN have developers on staff that will interface with integrator and manufacturer for required API development
	74	How is software and/or firmware updating of STB’s to be handled…I don’t believe I saw this mentioned in the RFP?	4.3.6	Integrator to propose solution
	75	Will the above require a DVB Streamer?	4.2.3	Integrator to propose solution
	76	Please define the current workflow for VOD material a. Is there a push server for content? b. Are the IP Encapsulated data streams the VOD only or are there other functions in the data streams? c. What are the content management requirements? d. Is there a server or servers for splicing required?	4.2.3	A. No push server for VOD content B. Encapsulated Data streams are PDF files of Newspapers (Kencast) and low data rate AP News Wires C. No Content Management requirement within the scope of integrator however CAS should have the ability to interface with CMS D. No splicing server for commercial insertion is required. This may be a future need and integrator can suggest this if thought to be a value add
	77	Does the monitor and control system need to control both the power view and new systems as well?	4.2.1	Yes…it needs to control all proposed system components
	78	Is there a commercial storage server or is this in the scope of the integrator?	4.3.5	No
	79	Is there a MAM system for content management?		No
	80	What Dolby needs to be passed?	4.1.2 & 4.1.3	Support for all iterations listed in RFP are required
	81	Are the SCTE 35 messages mentioned PID based along with Splicing information?	4.1.2 & 4,1,3	Yes
	82	Is there a requirement for redundant SDI and/or audio feeds?	4.1.2 & 4.1.3	No…AFN have a router upstream and will be responsible for redundancy up to the input of the encoders. Integrator is responsible for redundancy encoder redundancy and everything after.
	83	Is there a requirement for failover for SCTE messaging?	4.1.2 & 4.1.3	No
	84	I assume that the integrator is responsible for the splicing hardware?	4.1.4	No splicing hardware required.
	85	Is serial communication from automation to SCTE insertion acceptable or does it have to be done via GPI?	4.1.2 & 4.1.3	GPI
	86	4.3.3 STBs shall support addressable ads to insert targeted assets stored locally within the STB to seamlessly cover the incoming bit stream content upon receiving a digital cue message and seamlessly return to the bit stream following the local insertion. What about the Head End Side?	4.3.3	Only pass through of DPI messaging required at headend
	87	What is the workflow for captioning?	4.1.2 & 4.1.3	Closed captioning currently outsourced and is inserted prior to hand off to integrator
	88	Is there a need for live captions?	4.1.2 & 4.1.3	Closed captioning currently outsourced and is inserted prior to hand off to integrator
	89	Is there a difference in the captioning workflow between AFN and DTS? DTS appears to specify captioning as VANC is that correct?	4.1.2 & 4.1.3	Closed captioning currently outsourced and is inserted prior to hand off to integrator
	90	What is the look ahead window for programming…Can captioning be file based in advance of playout…I.E. requirement for support of SMPTE 334M?	4.1.2 & 4.1.3	Closed captioning currently outsourced and is inserted prior to hand off to integrator. Only support of 334M required here and STB will need to have captioning from all available outputs
	91	Is there a need to maintain the analog channels in the DTS AOR/POR services?	4.1.2 & 4.1.3	All DTS Video Channels are to be SD 480i
	92	RDS support?		***As per previous submittal question 12. AFN will provide Artist and Song title data in a combination of serial and XML form originating from our content providers and Radio Automation. Should our FM stations desire to push that data to a recieve device, the decoder shall be able to deliver that data to the station. No equipment on the receive end exists at this time and is not a requirement of this RFP.
	93	What is the intended channel configuration day 1?	4.2.3	AFN is to be all HD 720P Video and DTS is to be all SD 480i
	94	What is the nature and purpose of RDS?	4.1.2 & 4.1.3	***As per previous submittal question 12. AFN will provide Artist and Song title data in a combination of serial and XML form originating from our content providers and Radio Automation. Should our FM stations desire to push that data to a recieve device, the decoder shall be able to deliver that data to the station. No equipment on the receive end exists at this time and is not a requirement of this RFP.
	95	Does the integrator need to provide the encapsulation method and hardware for the IP Data Streams or are they provide in encapsulated form?	4.2	There is both an IP and a Serial Data component. Encoders need to support both. If an encoder that supports Serial Data cannot be found, then integrator should propose a solution for encapsulating serial data.
	96	OTT?	4.2.3	OTT in this contect refers to the ability for end user to access content across networks. Systems and/or hardware (that are applicable) need to support this. This is not however in the scope of this RFP
	97	Explain 4 systems vs 5 transponders	4.1.4 & 4.1.5	There are only feeds to 4 transponders. The IOR footprint for DTS is served by a turnaround.
	98	What specific SCTE insertion messages are required?		To be addressed in design review should a tender be awarded.

Sheet2

Sheet3

File details come from the government source that posted it. Updated Nov 14, 2017.