RFP 1214 - IDPTV Transmission Encoder System Administrative Document - Amendment One (1).docx

STATE OF IDAHO

DIVISION OF PURCHASING

FOR

Idaho Public Television

Request For Proposal

Transmission Encoder System

RFP Number: 1214 Amendment One (1)

Table of Contents

Section 1 Administrative Information and Overview

1.1 Purpose

The State of Idaho’s (“State”) Division of Purchasing (“DOP”), on behalf of Idaho Public Television (IDPTV) is issuing this Request For Proposal (“RFP”) to solicit Proposals from qualified and experienced firms (“Offerors”), that can supply an Advanced Television Systems Committee (ATSC 1.0) compliant Encoding System with a minimum one (1) year of service and support maintenance agreement, minimum of eight (8) years of parts availability and telephone support, one (1) year of standard manufacturer warranty and required on-site training. Background information is provided in Exhibit 1. General requirements are set forth in Exhibit 2. The complete scope of work is provided in Exhibit 3.

1.2 Procurement Schedule

Pre-Proposal Meeting:

Deadline to submit questions:

Closing Date (deadline to submit Proposal):

Public Opening Date:

Bid Opening Link:

The State will make every effort to adhere to the schedule below, but reserves the right, at its sole discretion, to adjust the schedule.

Thursday, July 9, 2026 @ 1:30 pm MT Thursday, July 16, 2026 @ 11:59 pm MT See IPRO Event Main Page for current closing date and time.

August 12, 2026 @ 10:30 am MT RFP 1214 Public Opening | Meeting-Join | Microsoft Teams

1.3 RFP Lead

Name:

Title & Agency:

Email:

The individual listed below (referred to as “RFP Lead”) is responsible for the conduct of this procurement. From the issue date of this RFP, until a contract is awarded, or the RFP is cancelled, Offerors are prohibited from communicating with any State employee, Official, or Evaluators regarding this RFP or procurement.

Mack DeYoung Buyer, Idaho Division of Purchasing Mack.DeYoung@adm.Idaho.gov

1.4 Pre-Proposal Conference

Link:

A non-mandatory pre-proposal conference will be held to provide an overview of the RFP process, the scope of work, and submission requirements. While attendance is highly encouraged, it is not mandatory. The meeting will be conducted virtually, with the access link provided below. To inform the State of your planned interest and attendance, please complete and submit Exhibit 4.

RFP 1214 Pre-Proposal Conference Meeting LINK

1.5 IPRO eProcurement System

This Solicitation is issued by the State via the State’s eProcurement system, IPRO. It is the Offeror’s responsibility to monitor IPRO for any updates or amendments.

Link: IPRO POWERED BY LUMA

1.7 Questions

The Offeror must review this entire RFP solicitation, including associated documents. All questions, requests for clarification, or other correspondence must be submitted in writing via email to the RFP Lead. See Exhibit 5 for additional instructions. Questions must be submitted using the table provided within Exhibit 5.

1.8 Modifications and Exceptions to Requirements, Terms, and Conditions

1.

0.

0.

0.

0.

0.

0.

0.

0.

7. Vendors are strongly encouraged to submit any proposed modifications to the requirements, terms, or conditions of the RFP on Exhibit 6 – Contract Modifications and Exceptions prior to the deadline to submit questions. Questions regarding these requirements must contain the following:

0. The rationale for the specific requirement being unacceptable to the party submitting the question (define the deficiency).

0. Recommended verbiage for the State’s consideration that is consistent in content, context, and form with the State’s requirement that is being questioned.

0. Explanation of how the State’s acceptance of the recommended verbiage is fair and equitable to both the State and to the party submitting the question.

7. In the event that a Proposal contains modifications or exceptions to any Solicitation requirements, terms, or conditions which are not addressed during the question and answer period, they must be identified and submitted on Exhibit 6 - Modification and Exception Form and must contain the same information outlined in Section 1.8, above. The State will not consider any modifications or exceptions that are not identified specifically on Exhibit 6.

7. The State has sole discretion to determine if the modifications or exceptions submitted by an Offeror would result in a material change or otherwise threaten the integrity of the procurement process. See Appendix A - Idaho Terms and Conditions Background and Limitations. Pursuant to IDAPA 38.05.01.084.e, the State may only negotiate non-material modifications or exceptions. Modifications or exceptions which the State determines to be material, or which otherwise threaten the integrity of the procurement process, will not be accepted or negotiated. If the Offeror has conditioned its Proposal on the State’s acceptance or negotiation of its proposed modifications or exceptions, and the modifications or exceptions are deemed material, the Offeror will be given the opportunity to retract the proposed modifications or exceptions from its Proposal. Failure to do so will result in the Offeror’s Proposal being found non-responsive, after which it will receive no further consideration.

7. Non-material modifications or exceptions may be discussed with the apparent successful Offeror, at the discretion of the State; however, the State shall have the right to reject any and all such modifications and/or exceptions, or to call an end to such discussions, and to instruct the Offeror to amend its Proposal and remove the modifications and/or exceptions. Failure to do so may result in the State finding the Proposal non-responsive.

Except as otherwise provided within the Solicitation, the State will not consider modifications or exceptions to the requirements, terms, or conditions which are proposed after the RFP Closing Date.

1.9 Amendments

The State may issue amendments to make changes to the RFP, or to respond to any questions. Amendments will be posted on IPRO. Offerors are responsible for monitoring IPRO for updates and amendments. All published amendments must become part of this RFP, and must be considered by the Offeror in its Proposal. Oral interpretations or clarifications of this RFP are not binding and should not be relied upon. Any verbal responses or informal communications from the State regarding this RFP are considered unofficial and will not be binding.

1.10 Authority

This procurement is conducted in accordance with IDAPA 38.05.01 and pursuant to Title 67, Chapter 92 of the Idaho Code.

Section 2 Format & Submission Requirements

2.1 Adherence to Requirements

The Proposal must be submitted in accordance with the requirements set forth in this document. Any Proposal that does not adhere to the requirements may be deemed non-responsive and rejected. The State reserves the right, in its sole discretion, to waive any minor informalities or immaterial non-compliance.

2.2 Deadline to Submit

All Proposals are due at the date and time specified in the Procurement Schedule (Section 1.2). Late Proposals must not be accepted or considered. The State must not be responsible for any technical issues, difficulties, or delays. Offerors are strongly encouraged to begin the process of submitting the Proposal response far enough in advance of the Closing Date/Time to allow for resolution of any technical difficulties.

2.3 Submittal Form Templates

The Offeror must ensure that their response meets all requirements detailed within this RFP. This RFP contains Submittal Forms, which must be used by the Offeror to submit their Proposal. Offerors must not re-create these Submittal Forms, create their own Submittal Forms, or edit the format structure of the Submittal Forms. An electronic copy of each Submittal Form is posted along with this RFP. The Offeror must download, complete, and submit each Submittal Form in their response.

2.4 General Format Requirements

The Proposal response must meet the following requirements:

2.4.1 The Offeror must not embed information, embed files, or embed any links within the Submittals.

2.4.2 Be made on standard 8.5” x 11” paper size.

2.4.3 Use a minimum font size of ten (10) (images, figures, graphs, charts, are excluded from this font size).

2.4.4 Use a font style such as: Calibri, Arial, New Times Roman, or similar.

2.4.5 The Offeror must not attach additional information to any Submittal Form (unless it has been explicitly requested). Any additional attachments submitted will not be considered in the evaluation process.

2.4.6 Cost information must only be contained within the Pricing Schedule Submittal Form. No other document or Submittal Form may contain cost or pricing information.

2.5 Page Limits

The Submittal Forms have maximum page limit requirements, as shown in the table below. The Offeror must ensure that their Proposal meets these page limit requirements. Offerors must not exceed the maximum page limits. Please note that the page limit applies exclusively to the front side of a page only (i.e. a ‘1 Page’ implies that the Offeror can only provide a response on one side of a piece of paper). Additional text will be removed or redacted before being provided to evaluators; only the text within the page limit will be evaluated. Offerors may add a cover page and table of contents which will not affect the Maximum Page Limits and this information will not be used for evaluating Offerors Proposal. Any substantive content added to the cover page or table of contents will be removed or redacted before being provided to evaluators.

2.6 Electronic Submission Instructions

The Offeror must submit the Proposal as follows:

1.

2.

2.1.

2.2.

2.3.

2.4.

2.5.

2.6.

2.6.1. The Proposal must be submitted electronically through IPRO POWERED BY LUMA. The State will not accept Proposals in any other manner (i.e. facsimile, email, or hardcopy submissions). All Offerors participating in this Solicitation must establish an account in the IPRO system, as it is necessary in order to process and/or award the resulting Contract(s). Establishing an account is free.

Link: IPRO POWERED BY LUMA

Please make sure that the entity profile under which the Proposal is submitted in IPRO, is the same legal entity presented in the uploaded response materials. If there are any discrepancies, the entity information provided within Submittal Form A prevails.

2.6.2. The Proposal must be submitted in the following forms:

* If applicable. Applies to Proposals with trade secrets as discussed below.

2.6.3. All electronic files must be in Adobe PDF, Microsoft Word, or Microsoft Excel format as noted in the table above.

2.6.4. The Proposal file(s) must not be password protected or locked in any way.

2.6.5. All submission materials must be submitted at the same time. If multiple submissions are received, only the latest timely submission will be considered.

2.6.6. Alternate Proposals are not allowed.

2.6.7. Note: When submitting through IPRO, enter your Cost in IPRO as “$0.01”.

2.6.8. If your Proposal contains trade secrets (see Section 2.7), submit an additional redacted version. This submittal must have 'Redacted' in the file name.

2.7 Trade Secrets and Non-Public Information

The Idaho Public Records Act, Idaho Code title 74, chapter 1 (the “Act”) defines trade secrets to “include a formula, pattern, compilation, program, computer program, device, method, technique or process that derives economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by other persons and is subject to the efforts that are reasonable under the circumstances to maintain its secrecy.” The Act also defines other records that may be exempt from public disclosure.

In addition to marking each page of the document with a trade secret or other exemption notation (as applicable; and as provided in Paragraph 28 of the Solicitation Instructions to Vendors), Offerors must also:

1.

2.

2.1.

2.2.

2.3.

2.4.

2.5.

2.6.

2.7.

2.7.1. Identify with particularity the precise text, illustration, or other information contained within each page marked “trade secret” or “exempt from disclosure” (it is not sufficient to simply mark the entire page). The specific information you deem “trade secret” or “exempt” within each noted page must be highlighted, italicized, identified by asterisks, contained within a text border, or otherwise clearly delineated from other text/information and specifically identified as a “trade secret” or “exempt from disclosure.”

2.7.2. Provide a separate document entitled “List of Redacted Trade Secret and Exempt Information” which provides a succinct list of all trade secret and exempt information noted in your Proposal; listed in the order it appears in your submittal documents, identified by Page #, Section #/Paragraph #, Title of Section/Paragraph, specific portions of text/illustrations; or in a manner otherwise sufficient to allow the State’s procurement personnel to determine the precise text/material subject to the notation. Additionally, this list must identify with each notation the specific basis for your position that the material be treated as exempt from disclosure and how the exempting the material complies with the Act.

2.7.3. Submit a redacted copy of any Proposal response document (e.g. Scope of Work Response) with all trade secret and exempt information removed or blacked out. The redacted copy must be submitted electronically in the Supplier Attachments section of IPRO, with the word “redacted” in the file name.

Section 3 Proposal Contents

3.1 Background, Declarations, and Certifications (Submittal Form A) The Offeror must complete and submit all information requested in this Submittal Form. An Offerors failure to complete and submit Submittal Form A may be found non-responsive and given no further consideration.

3.2 Technical Proposal (Submittal Form B)

The Offeror must complete and submit all information requested in Submittal Form B. An Offerors failure to complete and submit Submittal Form B may be found non-responsive and given no further consideration. The Technical Proposal consists of three (3) parts, as described below:

3.2.1 Part 1 - Qualifications and Experience: The Offeror must summarize their experience and qualifications as it relates to the scope of work being requested in this RFP. The Offeror must also outline the experience and qualification of the key personnel that will be assigned to this Contract. The Offeror must highlight any unique attributes that make the team especially qualified for the scope of services. If specifically asked for in this RFP please provide your resumes, otherwise resumes are not required, and should not be provided.

3.2.2 Part 2 - Approach: The Offeror must provide a brief overview of the approach that will be taken to successfully deliver this project/service. This must include a brief roadmap, which describes the general approach (major activities or tasks), which will be utilized to successfully deliver the Project/Service and to meet the Agency’s expectations (cost, time, quality, etc.). This must also include a high-level schedule of major activities or tasks that will be performed.

3.2.3 Part 3 - Obstacles, Challenges, & Risks: The Offeror must identify and address issues, concerns, challenges, obstacles, or risks that may impact the successful delivery of this project or service. This includes areas that may cause the project to not be completed on time, not finished within budget, generate any change orders, or may be a source of dissatisfaction for the Agency. The Offeror must rely on and use their past experience and knowledge of completing similar projects to identify these potential risks, issues, or challenges.

Each item should contain enough information to describe to a reader why the item is a valid risk/concern. The Offeror should also explain how it will avoid or minimize the risks from occurring. The Offeror should consider:

3.2.3.1 Controllable Items: This includes risks, activities, or tasks that are controllable by the Offeror, or by entities/individuals that are contracted to by the Offeror. This includes things that are part of the technical scope of what the Offeror is being hired to do. This may also include risks that have already been minimized before the project begins due to the Offeror’s expertise (i.e. risks that are no longer risks due to the Offeror’s expertise in delivering this type of project). All controllable risks and strategies to mitigate them MUST be included in the Offeror’s base Proposal cost and schedule (if there are any impacts at all).

3.2.3.2 Non-Controllable Items: This includes risks, activities, or tasks that are not controllable by the Offeror. This may include risks, issues, challenges, or obstacles attributed by the Agency, Agency personnel, parties hired by Agency, risks that are caused by other agencies, or completely uncontrollable risks. These can also be areas/risks that can contribute to contingency. Although these risks may not be controlled by the Offeror, the Offeror must identify a strategy that can be followed or used to mitigate these risks. All non-controllable risks and strategies to mitigate them must not be included in the Offeror’s base Proposal cost or schedule.

Provide a brief description of each item (background of how the concern/issue may impact the project or service if it occurs), and a strategy to prevent/minimize the issue/concern from occurring, or strategy to minimize the impact of the risk if it does occur.

3.3 Pricing Schedule (Submittal Form C)

The Offeror must complete and submit all information requested in Submittal Form C. The Offeror is not permitted to adjust or modify this form, and may not include additional rates, amounts, costs, information, exceptions, or limitations to their cost proposal. An Offerors failure to meet these requirements may be found non-responsive and given no further consideration.

Section 4 Evaluation & Award Procedures

4.1 Mandatory Submission Requirements

All Proposals will be reviewed on a "pass" or "fail" basis to ensure compliance with all mandatory submission requirements. Proposals determined by the State, at its sole discretion, to be responsive in this regard will proceed to the evaluation process outlined in this Section. Proposals that do not meet the mandatory submission requirements will be deemed non-responsive. Mandatory submission requirements include, but are not limited to, the following:

1.

2.

3.

4.

4.1.

4.1.1. The Proposal was submitted prior to the specified Closing Date and Time.

4.1.2. The Proposal complies with the submission instructions detailed in Section 2.6.

4.1.3. The Proposal includes a fully completed and signed Submittal Form A.

4.1.4. The Proposal includes all required Submittal Forms listed in Section 3.

4.2 Evaluation Criteria

The objective of the State in soliciting and evaluating Proposals is to ensure the selection of a firm or individual that will produce the best possible results for the funds expended. Responsive Proposals will be evaluated as described in the table below.

4.3 Evaluation Committee

The Technical Proposal will be evaluated and scored utilizing one (1) or more Technical Proposal Evaluation Committee(s). The scores for the Technical Proposal will be normalized as described in Section 4.4.

4.4 Calculations

The following approach will be used to normalize and calculate scores:

Written Proposal Calculations

For each document that is evaluated and scored by the evaluation committee, the RFP Lead will:

4.4.1 Average evaluator scores for each Proposal.

4.4.2 Identify the highest raw average score among all Proposals.

4.4.3 Assign normalized points as follows:

4.4.3.1 The Proposal with the highest raw score will receive the maximum available points for Submittal B.

4.4.3.2 All other Proposals will receive a proportional share of the available points using the formula:

Demonstration Calculations

The RFP Lead will average all evaluator scores for each Interview, Presentation, or Demonstration element. The averaged score will then be normalized as follows:

4.4.4 The Offeror receiving the highest raw average score for an element will be awarded the maximum available points for that element.

4.4.5 All remaining Offerors will receive a proportional share of the available points using the following formula:

Cost Calculations

Points for the Cost Proposal will be normalized as follows:

4.4.6 The Proposal with the lowest total evaluated cost will receive the maximum available points.

4.4.7 All remaining Proposals will receive a proportional share of the available points using the following formula:

4.5 Candidate Selection

The RFP Lead may select up to the top three (3) highest technical scoring Offerors to be invited to participate in demonstrations. The State intends to only open Cost Proposals for these selected Offerors.

4.6 Demonstrations

The finalist Offerors as selected in Section 4.5 will be required to have their technical solutions tested in person by IDPTV at IDPTV’s office located at 1455 N Orchard Street in Boise, Idaho. The Public Broadcasting Service (PBS) has provided IDPTV with a testing environment to evaluate the performance of an Offeror’s solution.

The demonstration will not exceed sixty (60) minutes. A demonstration script will be provided, including estimated time durations for each required scenario. Offerors are responsible for managing their time to ensure all required items are demonstrated within the allotted period.

Only the exact product, system, and version proposed in the Offeror’s submission may be demonstrated. Demonstrations must include only those functions included in the Offeror’s proposal. Optional features, unproposed functionality, or capabilities not fully developed and implemented for existing clients are not allowed. Offerors are prohibited from referencing cost or fees during the demonstration.

4.6.1 On-site Setup

4.6.1.1 IDPTV will provide a video clip on site for testing.

4.6.1.2 The Offeror will be allotted thirty (30) minutes to set up their equipment and adjust outputs prior to the start of testing.

4.6.2 Test Configuration

IDPTV will evaluate each proposed solution using the following configuration:

4.6.2.1 Input Source - The HD/SD‑SDI output sources from an video clarity ClearView analysis system IDPTV in‑house file server will serve as the input to the encoder system under test.

4.6.3 Technical Testing Evaluation Scoring

4.6.3.1 During each test, the SDI output of the THOR will be recorded on the Clarity RTM-CV analyzer along with the identical output from the house file server. The analyzer will perform a frame by frame quantitative analysis of two video samples.

4.6.3.2 The PSNR algorithm measures differences between the two samples in absolute terms but does not distinguish between differences that may or may not be perceived by a viewer. A value of 35 dB is generally considered good; the higher number generally indicates better performance.

4.6.3.3 Forty (40) points maximum points are assigned for evaluating PSNR values. The Offeror with the highest scoring PSNR measurement will receive the maximum points.

4.6.3.4 The JND and DMOS measurements use two different techniques for identifying and quantifying video differences that a viewer would be expected to notice and find objectionable; and

4.6.3.4.1 For JND and DMOS measurements, lower numbers indicate better performance.

4.6.3.5 The JND and DMOS will be worth eighty (80) points each. The following table is the guide for associating JND and DMOS measurements with perceived video quality. Scores will be distributed according to the below scale:

DESCRIPTION

Unwatchable

Annoying

Broadcast Quality

Production Quality

No Defects

4.7 Clarification Discussions

The RFP Lead may, in the State’s sole discretion, perform clarification discussions with the Offeror(s) to verify and validate that the Proposal will meet the needs of the Agency. At any time during this period, if it is discovered that the Offeror has not met a mandatory requirement, or has failed to adequately respond to an item below, the State may find the Offeror non-responsive.

4.7.1 The Offeror may be required to provide documentation to demonstrate its responsibility. Failure to provide the requested documentation may result in the Offeror being deemed non-responsible. IDAPA 38.05.01.81.

4.7.2 If requested, provide any additional documentation that may be requested, which may include a detailed project/work plan, testing and commissioning plan, training, change management plan, safety plan, staffing plan, operational plan, maintenance plans, warranties, bonding and insurance, background checks, etc.

4.7.3 The clarification discussion cannot materially alter the Proposal. The State does not expect to negotiate any terms or conditions requested by the Offeror, unless they were submitted by the Offeror prior to the deadline for submitting questions (see Section 1.8), or they provide the State an opportunity to secure more advantageous terms or pricing.

4.8 Best-And-Final-Offer (BAFO)

The State reserves the right to request Best and Final Offers (BAFOs) from Offerors. If BAFOs are requested, the State will issue written instructions to the selected Offerors identifying the scope of the BAFO request and the deadline for submission. Offerors must not modify any aspect of their Proposal except as specifically requested by the State. BAFO responses must be submitted in accordance with the instructions provided. Failure to submit a BAFO, if requested, may result in the Offeror’s original Proposal being considered as its final offer.

4.9 Award

Award of Contract will be made to the responsive, responsible Offeror whose Proposal receives the highest number of total normalized points.

4.10 Resulting Contract

If the State awards Contract(s) from this solicitation, it will do so by issuing a Contract Purchase Order (CPO) document from Luma, the State’s ERP system. The State anticipates issuing a single contract from this solicitation, incorporating the Terms and Conditions, Scope of Work, Appendices, and some or all of the Offeror’s Technical Proposal.

EXHIBIT 1

Background Information

1. About The Department / Agency IDPTV is a statewide, non-commercial broadcast telecommunication system and media provider based in the capital city of Boise with additional staffed facilities in Moscow and Pocatello.

We harness the power of public media to encourage lifelong learning, connect our communities, and enrich the lives of all Idahoans. We tell Idaho's stories.

2. Background Information IDPTV is preparing to upgrade its existing ATSC 1.0 MPEG-2 Encoding system to a more flexible and robust next generation encoding platform to use the EAS NET or Stream MPEG IP output standard from Digital Alert Systems, or a newer IP standard.

IDPTV currently has an IP Network between its Network Operations Center (NOC) and each primary transmission site. This network spans the state of Idaho and runs through a service provider for some parts of the network connection. The network traffic is blind to the service provider.

Emergency Alerting, also referred to as EAS, is decoded and encoded using Digital Alert Systems Dasdec III units for the four (4) main market transmission facilities, KAID, KIPT, KUID, and KISU. IDPTV expects to upgrade our system to use the EAS NET or Stream MPEG IP output standard from Digital Alert System, or Newer IP Standard.

The Guide Builder main and backup units are the only PSIP source equipment currently in use. After commissioning the new system, the FTP standard will become the primary source and the Guide Builders will only be used as an emergency backup or possibly decommissioned.

IDPTV’s CABLE output does not require PSIP and does not broadcast over the air and is set to 85mbps, but remains adjustable if needed. The CABLE feed only needs video and audio encoded services with basic PSIP, No Guide, as the end user will re-encode to their standard. IDPTV desires that the current service channel numbers on CABLE remain the same so end user does not need to make changes as the new system is commissioned.

The IDPTVHD channel and PLUS channel for all markets will continue to use both Stereo 2.0 and 5.1 up-mixing in English only. All other channels use only Stereo 2.0 in English.

IDPTV utilizes six (6) SD channels that are presented to the system as HD-SDI.

IDPTV currently uses Myers ProTrack as the traffic system. ProTrack generates a daily file containing all required PSIP data. This file is ingested into Triveni GuideBuilder systems to generate the PSIP framework and output signals.

Current PSIP infrastructure includes:

One (1) primary Triveni GuideBuilder server One (1) backup Triveni GuideBuilder server

Each server has two (2) licensed outputs:

Output 1: KAID, KIPT, KISU Guide Data Output 2: KCDT/KUID Guide Data

3. Summary of Scope The desired system will allow flexible encoding for use now in the ATSC 1.0 environment and simple migration via software updates to the ATSC 3.0 platform and Over the Top (OTT) content delivery as well.

4. Objectives and Expectations

4.1. All equipment offered to be of the latest (most recent) design of its manufacturer to assure longest service life;

4.2. Accommodate all the current IDPTV TS needs as outlined in Exhibit 3;

4.3. Include room for expanding opportunities such as additional channels or TS inputs/outputs;

4.4. Include redundancies in multiplexers and encoders to allow for seamless program delivery even when any portions of the system may fail;

4.5. Provide management and control functionality in a client/server type of architecture that can easily leverage TCP/IP LAN/WAN technologies; and

4.6. Provide the ability to add, remove or reconfigure encoded services easily via pre-configured templates. In this environment, multi-level security is a requirement for any management and control functions.

4.6.1. IDPTV is currently using the Harmonic NMX Operator software for the monitoring and management functions.

5. Existing Data IDPTV operates a central casting facility for our Statewide network. There are four (4) distinct service areas and five (5) full-power transmitter facilities as well as one (1) output stream for Cable and Satellite Service Providers. To allow for discreet interstitial material for each service area a Transport Stream (TS) must be assembled for each area in the Boise NOC and then sent out via independent IP Multicast connections with Forward Error Correction (FEC). All market outputs operate twenty-four (24) hours a day, seven (7) days a week, three hundred sixty-five (365) days a year.

6. Current Challenges The existing alerting system does not consistently trigger alarms when system issues occur. Additionally, there is no effective mechanism for notifying engineering staff when alerts are generated. IDPTV’s Master Control team cannot reliably monitor all events.

7. Unique Considerations Responsive Proposers must, at their own expense, provide to IDPTV in Boise, Idaho, their proposed products for testing. Proposer’s solution will be tested in accordance with the specifications of this solicitation.

8. Reference Documents Exhibit 8 – Encoding and Multiplexing Architecture This illustrates a typical encoding system with full redundancy for both encoders and multiplexers.

Hardware components may be combined or deployed as separate devices; however, the encoding and multiplexing functions must maintain physically independent redundancy at all times.

The Contractor must provide the complete hardware and software solution for all components identified within the purple box in Exhibit 8.

EXHIBIT 2

General Requirements In the event of conflict with the State’s Standard Terms and Conditions, or other terms, conditions or requirements contained in this RFP, the following provisions will take precedence:

1. Installation and Acceptance The Contractor may build the Transmission Encoder System off-site from the IDPTV site and deliver as a fully-functional system, or the Contractor may build the Transmission Encoder System on-site at IDPTV.

1.1 IDPTV Commissioning for Service, and start of production service must be accomplished within ninety (90) calendar days after system delivery.

1.2 For commissioning, IDPTV will provide the following:

1.2.1 New Juniper EX3400-48T Switches for system configuration and control.

1.2.2 Interconnection Cabling, (SDI over Coax using BNC connectors), for the six (6) listed input sources from our Utah Video Router.

1.2.3 Existing Juniper and Cisco Network switch for IP network outputs for five (5) Encoded Markets.

1.2.4 Existing IP network connection for the ATSC Guide Data and WARN Data.

1.3 Any issues identified within thirty (30) days post commissioning must be resolved by the Contractor. All issues will be considered emergent and must be addressed immediately due to the system being active and in live/in-broadcast use at this stage of existence.

1.4 IDPTV requires the vendor to use the current cabling numbering system for all internal cabling within the system. These numbers will be provided before commissioning is completed.

2. Training Technical maintenance training must be provided on-site at IDPTV for the system supplied. The training will be for at least five (5) members of IDPTV’s engineering staff. All training and attached expenses must be included as part of the Offeror’s fully burdened offer.

3. Warranty, Service and Support, Maintenance, Parts, etc.

3.1 The Contractor must provide a minimum one (1) year service and support maintenance agreement that includes remote telephone support twenty-four (24) hours a day, seven (7) days a week, three hundred sixty-five (365) days per year (24/7/365);

3.2 Workmanship must be warrantied for one (1) year, beginning after system commissioning and IDPTV acceptance.

3.3 The Contractor must provide system replacement parts for a minimum of eight (8) years after the commissioning of the Transmission Encoder System;

3.3.1 Individual active devices used in the system and its associated components must also be available for eight (8) years or replacement equipment with the same functionality must be provided at cost.

3.4 All warranty and support must be included as part of the Offeror’s fully burdened Proposal; and

3.5 The State shall have the option, at its sole discretion, to extend support and maintenance services for up to an additional five (5) years beyond the initial term.

3.5.1 The Contractor agrees to provide such extended services under the same terms, conditions, and pricing structure, unless otherwise mutually agreed to in writing.

4. Delivery

4.1. The Contractor must deliver the specified equipment within eight (8) weeks after receipt of order to IDPTV. If the Contractor cannot meet the agreed-upon timeline, the Contractor must, upon written mutual agreement with IDPTV, develop a revised delivery solution that aligns with the State’s best interests.

4.2. Deliveries must be made FOB Destination, freight prepaid and allowed to the following location:

Idaho Public Television

1455 N Orchard Street

Boise, ID 83706

4.3 Due to the following restrictions, the Offeror must consider the delivery logistics and costs (such as a pallet jack) as part of their fully burdened Proposal:

4.3.1 The delivery location does not have a freight dock;

4.3.2 Inside delivery is required; and

4.3.3 Due to limited site clearance, delivery by a full size semitruck is not recommended.

5. Licensing and Regulations

5.1. The Contractor’s system must be manufactured under a registered ISO 9001 Quality system.

5.2. The Contractor must procure all licenses required to enable both the EAS capabilities and Forward Error Correction (FEC);

5.2.1. IDPTV Currently uses a digital alert systems Dasdec III for EAS;

5.2.1.1. EAS ET (Includes DVS168);

5.2.1.2. Stream MPEG-1 and MPEG-2 (the KUID Dasdec III does not have this license, If needed it will need to be acquired); and

5.2.1.3. The FEC must be compatible with VX8000e units from Path1, GigaCaster II units from Enensys, and Gates Air transmitter IP inputs.

5.3. The Contractor must supply any licensing required to enable both of the following systems currently in use by IDPTV: ProTrack(Myers) FTP output, and Triveni GuideBuilder system with IP outputs (IDPTV currently uses Triveni with outputs from both primary and backup systems).

5.4. The Contractor’s system must be supplied with licenses to encode all video services using MPEG 2, MPEG 4 AVC or the newest HEVC codec to allow operation with current ATSC 1.0 and ATSC 3.0 standards.

5.5. A Dasdec III license is required where applicable.

6. Records Maintenance Contractor must maintain or supervise the maintenance of all records necessary to properly account for all payments made to the Contractor pursuant to the Contract. These records must be retained by the Contractor for at least three (3) years after the Contract terminates, or until all audits initiated within the three (3) years have been completed, whichever is later.

7. Audit Rights The Contractor agrees to allow State and Federal auditors and State purchasing staff access to all the records relating to this Contract, for audit, inspection, and monitoring of services or performance. Such access will be during normal business hours or by appointment.

8. Milestone-based Payment Schedule Payments to the Contractor will follow the two (2) phase milestone-based payment schedule shown here:

9. Billing Procedure The Contractor must provide a signed invoice upon the successful completion of each required Milestone as written within this Administrative Document. The invoice must be submitted no later thirty (30) calendar days after said completion. No invoice will be accepted or paid without receipt of required documentation as noted below. Invoices submitted without the required documentation will be returned to the Contractor for resubmission.

9.1. The Contractor must provide the following information with each invoice:

9.1.1. IPRO contract number (and name of project/product, if appropriate) and Agency PO number;

9.1.2. Identification of billing period;

9.1.3. Total amount billed for the billing period;

9.1.4. Detailed description of services/products provided and associated # of hours/$ amounts, as appropriate; and

9.1.5. Name of authorized individual and contact information for Contractor.

9.2. Invoices and reports are to be submitted by standard US mail at:

Idaho Public Television

1455 N Orchard Street

Boise, ID 83706

9.2.1. Or by email: accounting@idahoptv.org

EXHIBIT 3

Specifications

1. Schedule

1.1. The Contractor’s system must be delivered to IDPTV within eight (8) weeks after Contractor receipt of order;

1.2. The Contractor must complete commissioning of the equipment within ninety (90) days of acceptance by IDPTV; and

1.3. The Contractor’s system must have thirty (30) days of successful operation post-commission.

1.4. Failure to complete any of the above requirements as listed may result in the State taking corrective action up to and including options specified in Section 1.4 of the State of Idaho Contract Terms & Conditions.

2. Requirements

2.1. IDPTV needs to output five (5) discreet IP Multicast output feeds, each with FEC, Identified by these market call letters, KAID, KIPT, KCDT, KISU, and CABLE.

2.1.1. The KUID and KCDT markets are in the Pacific Time Zone. All other markets are in the Mountain Time Zone.

2.1.2. The first four (4) feeds, KAID, KIPT, KUID, and KISU are discreet market feeds that consist of the following services:

2.1.2.1. IDPTVHD Channel in High-Definition (HD);

2.1.2.2. PLUS Channel in HD;

2.1.2.3. CREATE Channel in 16x9 Widescreen Standard Definition (SD);

2.1.2.4. WORLD Channel in 16x9 Widescreen SD; and

2.1.2.5. KIDS Channel in 16x9 Widescreen SD.

2.1.3. Each discreet stream must also be embedded with the following:

2.1.3.1. ATSC 1.0 PSIP & Guide; IP Sourced from ProTrack (Myers) and Triveni GuideBuilder

2.1.3.2. KCDT & KUID markets must utilize the separate Pacific Time Guide Data from ProTrack (Myers) and Triveni GuideBuilder, the other markets utilize the Mountain Time Guide Data PSIP Data.

2.1.3.3. Discreet Nielsen Watermarking for all five (5) identified channels (markets KUID and CABLE do not utilize Nielsen Watermarking).

2.1.3.4. Audio Loudness Controls for all services in all markets.

2.1.3.5. WARN Data stream in IP for all markets except CABLE (this may be present, but not required).

2.1.3.6. Discreet EAS encoding from Digital Alert Systems Dasdec III Units via the IP Streaming MPEG ½ OR newer Dasdec III Supported EAS output format.

2.1.3.6.1. If a newer format is available, licenses will be required (one additional license is required for the Streaming MPEG ½ format on the KUID Dasdec III).

2.2. The final IP Multicast output feed IDPTV needs is named CABLE, with FEC, for IDPTV’s Cable and Satellite service providers.

2.2.1. This output is not broadcast Over the Air (OTA), but basic PSIP data without Guide is used to identify the included streams;

2.2.2. All the services included in this output feed will be sourced from the previous four (4) market output feeds listed in Section 2.1.2 of this Exhibit, totaling twenty (20) services combined into one (1) output stream;

2.2.3. These services may be separately encoded from their original source, or they may be acquired directly from the four (4) already encoded service market output streams.

2.2.4. This output stream must also include the discreet EAS Encoding for each market and utilize FEC.

2.3. The current NMX Operator software must be isolated from the internet to maintain security on IDPTV’s internal network.

2.3.1. The Contractor must provide a management solution that can remain secure while connected to an internet enabled network and can receive regular IP security updates.

2.4. Video, Audio & Other Encoding Specifications:

The system must utilize statistical multiplexing within each market’s encoder to be incorporated into all transport streams being assembled (the "Cable" output stream is exempt from this and may use pre-stat muxed sources).

2.4.1. The following Codecs are the minimum required:

2.4.1.1. MPEG-2 MP @ ML;

2.4.1.2. MPEG-2 MP @ HL;

2.4.1.3. MPEG-4 AVC MP @ L3;

2.4.1.4. MPEG-4 AVC HP @ L4; and

2.4.1.5. HEVC MAIN 10.

2.4.2. The following resolutions and frame rates must be supported:

2.4.2.1. (HD) 1920x1080i @ 29.97/59.94fps and 30fps; and

2.4.2.2. (SD) 720x480i @ 29.97/59.94fps and 30fps.

2.4.3. The following resolutions and frame rates are optional:

2.4.3.1. (SD) 576i @ 25fps;

2.4.3.2. (HD) 720p @ 50fps;

2.4.3.3. 1080i @ 25fps and 29.97fps; and

2.4.3.4. 1080p @ 24fps, and 50fps.

2.4.4. The encoding system as delivered must be capable of real time Up/Down and Cross conversion of the following resolutions and frame rates to the desired encoded service output:

2.4.4.1. 480i @ 29.97fps;

2.4.4.2. 720p @ 59.94fps, and 1080i @ 29.97fps;

2.4.4.3. 576i @ 25fps;

2.4.4.4. 720p @ 50fps, and 1080i @ 25fps; and

2.4.4.5. 720p @ 59.94fps and 1080i @ 29.97fps or 1080i @ 29.97fps and 720p @ 59.94fps.

2.5. Audio Encoding Specifications:

Audio input must be an embedded SDI source. The supplied system must provide a CALM Act compliant level control mechanism.

2.5.1. The following codecs are the minimum required:

2.5.1.1. AC-3;

2.5.1.2. E-AC-3;

2.5.1.3. MPEG-2/4 AAC LC (ADTS/LATM); and

2.5.1.4. MPEG-4 HE-AAC v1/2 (ADTS/LATM) (stereo and 5.1 surround).

2.5.2. The following codecs must be supported by the provided hardware:

2.5.2.1. MPEG-H (ISO/IEC 23008-3);

2.5.2.2. Dolby AC-4 (ETSI TS 103 190-2; and

2.5.2.3. MPEG-4 AAC (xHE-AAC).

2.6. Ancillary Data Capabilities:

The system management interfaces must comply with the most current industry-recognized network security standards, including but not limited to NIST guidance (e.g., NIST SP 800-53, NIST Cybersecurity Framework), modern TLS versions (TLS 1.2 or higher), and secure remote access protocols, or any newer versions in effect at the time of system acceptance.

2.6.1. For closed captions, the following standards must be supported on all markets:

2.6.1.1. EIA-608;

2.6.1.2. EIA-708; and

2.6.1.3. ATSC A/53.

2.6.1.4. Units must also provide 608/708 real time conversion if needed or one is missing.

2.6.2. For VANC data the following must be supported:

2.6.2.1. AFD

2.7. External Data Capabilities

2.7.1. The system must support the PBS Warning, Alert, and Response Network (PBS WARN) datacasting data insertion over IP;

2.7.2. Preferred PID 0x911; and

2.7.3. The system must support the insertion of Nielsen Audio Watermarking for all channels.

2.7.3.1. The CABLE and KUID output streams are exempt from this requirement.

2.8. The system must support the following EAS insertion protocols:

2.8.1. EAS Alert insertion via IP Streaming MPEG ½, or newer IP standard supported by Dasdec III Systems.

2.8.2. IDPTV employs a Digital Alert Systems Dasdec III unit that outputs an IP stream for insertion (KUID does not currently have a license for Streaming MPEG-1 and MPEG-2, and must be provided if utilized).

2.8.3. Each unique encoded output stream must support a unique EAS Alert IP stream insertion according to the associated Market;

2.8.4. There are four (4) Unique EAS markets for IDPTV - KAID, KIPT, KUID, and KISU; and

2.8.4.1. All five (5) channels in each market must have EAS insertion.

2.8.5. EAS insertion must support the EAS NET insertion protocol or the Streaming MPEG ½ protocol from Digital Alert Systems, or newer format (licenses are required if utilizing a newer format).

2.9. Power

2.9.1. Standard NEMA-5-15R outlet strips are currently used inside racks;

2.9.2. Dual Power supplies that are hot swappable are required; and

2.9.3. The input voltage available at the site is 120VAC, and is the specified line voltage for the proposed system.

3. System Inputs/Outputs

3.1. The Contractor must provide an ATSC 1.0 compliant encoding system capable of accepting six (6) live SDI (video/audio) feeds from IDPTV’s Utah Scientific video router.

3.2. Each transport stream must carry five (5) ATSC 1.0 program services, consisting of two (2) HD services and three (3) SD services, as specified Scope of Work Section 2.1.2.

3.3. All market-specific transport streams must include Emergency Alert System (EAS) capabilities and Forward Error Correction (FEC). Any licenses to enable these features between both vendors must be included as specified in Exhibit 2 – General Requirements, Section 5.

3.4. The system must generate a twenty (20)-service IP output transport stream named CABLE.

3.5. The system must provide n+1 redundancy at a transport stream encoder level and for the output MUX functions. For example: If one service encoder fails, a backup encoder must automatically configure itself and take control to ensure seamless output streams with minimal interruptions.

3.5.1. A separately built, standalone hardware component for the…