Request_for_Proposals_for_PON_Network_Equipment.pdf

Request for Proposals for PON Network Equipment

No. 2026-GSCA-RFP-002

Issued by:

Golden State Connect Authority

1215 K Street, Suite 1650

Sacramento, CA 95814

RESPONSES DUE ON OR BEFORE:

Wednesday, August 19, 2026, at 11:59 pm

Table of Contents

1. INTRODUCTION

1.1. BACKGROUND

1.2. KEY INFORMATION

1.3. PROCEDURE

2. DELIVERABLES

2.1. ADMINISTRATIVE REQUIREMENTS

2.2. TECHNICAL REQUIREMENTS

2.3. OTHER REQUIREMENTS

3. EVALUATION

3.1. SELECTION CRITERIA

3.2. SUBMISSION AND ACKNOWLEDGEMENTS

4. ATTACHMENTS

4.1. ATTACHMENTS

1. INTRODUCTION

1.1. BACKGROUND

1.1.1. The Entity

Golden State Fiber ("GSF"), a division of the Golden State Connect Authority (“GSCA”), exists to connect residents and businesses to their choice of internet service provider (ISP) on an open-access network backed by infrastructure GSF owns and operates. GSF's network allows customers to choose an ISP and service plan that best suits their needs.

GSCA is a joint powers authority and public agency organized and existing under Chapter 5

(Section 6500 et seq.) of Division 7 of Title 1 of the California Government Code. GSCA’s objective is to increase access to reliable, affordable high-speed internet for the residents and businesses of our member counties. GSCA’s membership represents 40 of California’s 58 counties, 14.7% of the California population, and 61% of the California land mass.

GSCA’s member California counties are: Alpine, Amador, Butte, Calaveras, Colusa, Del Norte, El Dorado, Glenn, Humboldt, Imperial, Inyo, Kings, Lake, Lassen, Madera, Mariposa, Mendocino, Merced, Modoc, Mono, Monterey, Napa, Nevada, Placer, Plumas, Santa Barbara, San Benito, San Luis Obispo, Shasta, Sierra, Siskiyou, Solano, Sonoma, Sutter, Tehama, Trinity, Tulare, Tuolumne, Yolo, and Yuba.

1.1.2. The Network

GSCA is in the process of constructing a wholesale, advanced communications network. The network is being constructed at the time of this RFP.

The network will use fiber optic technology, which provides transmission of voice, data and video at speeds that are significantly faster than existing copper, cable, or satellite systems. Fiber is currently used for the backbone of the internet and other high demand applications but has not been widely implemented over “the last mile” into homes and businesses. GSCA will lay the fiber optic cable necessary to connect homes and businesses to the network. The fiber optic cable is being laid both underground and overhead aerial.

The network is divided into service areas or footprints. The network will use a passive optical network (PON) system. The Optical Line Terminal (OLT) network equipment will be placed in non-climate-controlled environments that are constantly monitored by GSCA. The Optical

Network Terminal/Optical Network Units (ONT/ONU) will be installed at customer premises.

GSCA is seeking qualified vendors to provide the PON network equipment and supporting systems and services to deploy and operate the fiber to the premise network.

Network Development Timeline

The network consists of seven projects across three service areas (Northern, Central, and

Southern California), totaling approximately 1,065 route miles and 31,427 homes passed.

Construction will begin in June 2026 in Glenn County, with a second project area anticipated to start in Q3 or Q4 of 2026. The remaining projects will follow as permitting and other conditions allow, with full deployment expected to be completed within approximately 18 - 24 months from the start of construction. GSCA expects to begin active customer onboarding in Q1, 2027.

Project Service Areas

Network electronics will be installed in approximately 37 hut/cabinet locations throughout seven project areas in California, as shown in the table below. At these locations, it is anticipated to have a distributed split design, but some locations will have a centralized split. All needed OLT ports installed are planned to be connected and lit to all splitter paths. It is anticipated that a

~50% take rate will be attained.

Project Service Area Planned Miles Homes Passed

Amador Central 283.64 2,706

Alpine Central 37.19 1,063

Town of Mammoth Lakes Central 96.04 12,300

Mono Central 36.54 1,085

Glenn North 106.68 2,089

Tehama North 426.78 9,479

Imperial South 78.21 2,705

Additional detail is included in Appendix B – GSF Estimated Forecast and Cost Template, which can be found in the ATTACHMENTS.

1.1.3. Philosophy and Goals

The Golden State Fiber network will be Open Access, and is designed for use by several service and content providers. Content and service providers will have unique Virtual Local Area

Networks (VLANs) that house their customers and will be separated from other providers.

Customer may be further separated into IEEE 802.1Q-in-802.1Q encapsulation, sometimes referred to as Q in Q or VLAN double tagging. This will further keep customers isolated from each other.

1.1.4. Funding

The purchase of PON network equipment contemplated under this RFP is sponsored by the

Golden State Connect Authority (GSCA) and are funded through a combination of grant awards from the California Public Utilities Commission (CPUC) Federal Funding Account (FFA) and bond financing. CPUC FFA grant funds are used to support the planning, design, and construction of open-access broadband infrastructure, while bond proceeds are used to supplement grant funding and support project delivery, capital financing, and long-term network sustainability, all subject to applicable state and federal requirements and GSCA approvals.

https://procurement.opengov.com/portal/goldenstateconnect/projects/283944/document?section=2737696

1.2. KEY INFORMATION

1.2.1. Guidance

The requirements and recommendations included in this RFP are created to provide interested parties and those who submit proposals (“respondents”) with enough information to readily understand the nature of the project and the information required in a complete proposal. This

RFP is not intended to limit proposal content or to exclude any potential respondent from submitting a proposal. Respondents who do not meet certain requirements may still submit proposals so long as they include supporting documentation and/or information on why and how they may work to fulfill those requirements.

Respondents are reminded that they have the following responsibilities:

• Carefully read the entire RFP.

• Carefully review all RFP requirements prior to submitting a proposal.

• Submit questions in a timely manner.

• Abide by all procedures and requirements of the RFP.

• Not include conditional statements, assumptions, or exception language with a proposal.

Before submitting a proposal, the respondent shall understand all contract conditions referred to in this document, and any addenda issued before the RFP submission date. It shall be the respondent’s responsibility to ensure that their final proposal, including all supporting documentation, is submitted by the final RFP submission date. By submitting a proposal, the respondent acknowledges and accepts the Terms and Conditions described herein.

1.2.2. Confidentiality

All proposals, including all supporting documentation, become public after contracts are awarded. GSF reserves the right to delay release of these records to other respondents or the public until the contract award date.

GSF is subject to the California Public Records Act (Government Code section 7920.000 et seq.), which provides public access to all records in GSF's possession – including submissions for this RFP. Everything submitted to GSF is presumptively a public record. Such disclosure may be made regardless of whether the proposal (or portions thereof) is marked

“confidential,” "trade secret," “proprietary,” or otherwise, and regardless of any statement in the proposal (a) purporting to limit the GSF’s right to disclose information in the proposal, or (b) requiring GSCA to inform or obtain the consent of the Proposer prior to the disclosure of the proposal (or portions thereof).

Exceptions to disclosure are those parts or portions of a proposal that are justifiably defined as business or trade secrets, as determined by GSF in its sole discretion, and are plainly marked by the respondent as “confidential,” "trade secret," or “proprietary.”

GSF will not, in any way, be liable or responsible for the disclosure of any such record or any parts thereof, if disclosure is required or permitted under the California Public Records Act or otherwise by law, as determined by GSF in its sole discretion. A blanket statement of confidentiality or the marking of each page of the proposal as confidential will not be deemed sufficient notice of exception. The Proposers must specifically label only those provisions of their respective proposal which are “confidential,” "trade secret," or “proprietary” in nature.

In the event GSF is required to defend an action on a Public Records Act request for any of the aforementioned documents, information, books, records, and/or contents of a proposal marked

“confidential,” "trade secret," or “proprietary,” Proposer agrees to defend and indemnify GSF from all costs and expenses, including reasonable attorneys' fees, incurred in connection with any action, proceedings, or liability arising in connection with the Public Records Act request.

Respondents should be aware that marking a document “confidential,” “proprietary,” or “trade secret” in a proposal may exclude it from consideration for award and will not keep that document from being released after notice of award as part of the public record unless a court has ordered GSF not to release the document. The content of all working papers and discussions relating to any proposal shall be held in confidence indefinitely, unless the public interest is best served by an item’s disclosure because of its direct pertinence to a decision, agreement, or the evaluation of the proposal.

Any disclosure of confidential information by a respondent is a basis for rejecting a proposal and ruling the respondent ineligible to further participate.

1.2.3. Proposal Preparation Costs

GSF is not liable for any cost incurred by a respondent associated with the preparation of their

Proposal nor the negotiation of a contract prior to the issuing of the contract.

1.2.4. Proposal Terms

Submission of a proposal shall constitute acceptance of all terms and conditions in this RFP.

Conditional proposals may be rejected.

The issuance of this RFP does not constitute an assurance that GSF will enter into a contract with any respondent. GSF expressly reserves the right to:

• Reject any and/or all proposals.

• Adjust or change requirements within the RFP.

• Reissue the RFP.

• Adjust or extend any due dates in the RFP process without advance warning.

GSF reserves the unequivocal right to decline awarding a contract to any of the participants at its sole discretion, without being bound to provide any justification or compensation for such decisions.

1.3. PROCEDURE

1.3.1. Overview

GSF has established a Procurement Portal which includes this complete RFP. GSF requires electronic submission of proposals through the Procurement Portal. All questions must be submitted through the Procurement Portal and all question responses and addenda will be hosted exclusively in the Procurement Portal.

The submission deadline is Wednesday, August 19, 2026 at 11:59 pm. The Procurement Portal clock is the official clock for the determination of all deadline dates and times. Without exception, responses will not be accepted after the submission deadline regardless of any technical difficulties such as poor internet connections. GSF strongly recommends respondents complete their response well ahead of the deadline.

1.3.2. Pre-Response Meeting

A Non-Mandatory pre-response meeting will be held virtually on Monday, July 27, 2026 at

2:00 pm using the following meeting information:

Zoom Meeting: https://rcrcnet.zoom.us/j/85780798188 Meeting ID: 857 8079 8188 Passcode:

GSFRFP

1.3.3. Questions

Respondents are required to register for an account via the Procurement Portal in order to submit and receive answers to questions. Once the respondent has completed registration, they will receive addenda notifications to their email by clicking “Follow” on this project. It is the sole responsibility of each respondent to check the site for any question responses and addenda.

Respondents requiring clarification on the intent, terms and conditions, content of this RFP, or on procedural matters regarding the competitive award process may request clarification by submitting questions in writing to GSF via the Procurement Portal. Only questions submitted in writing in this manner shall be binding and official.

If a respondent who desires clarification or further information on the content of the solicitation, but whose questions relate to the proprietary aspect of its proposal and disclosure exposes its proposal to other respondents, the question may be submitted using the same criteria above with the notation “CONFIDENTIAL”. The respondent must explain why the question is sensitive in nature. If GSF, in its sole discretion, concurs that the disclosure of the question or answer would expose the proprietary nature of the Proposal, the question will be answered, and both the question and answer will be confidentially maintained. If GSF does not concur with the proprietary aspect of the question, the question and answer will not be confidentially maintained, and the respondent will be so notified.

Respondents are solely and exclusively responsible for submitting such inquiries or clarification requests not less than five (5) calendar days prior to the scheduled closing date for the receipt of proposals. GSF will only respond to respondent inquiries or clarification requests submitted timely and by this method. Responses, and any addenda to the RFP, shall be posted in the

Procurement Portal and made available to all potential respondents. Responses may be provided on a flow basis, but will be posted no later than Tuesday, August 11, 2026.

1.3.4. Form of Submission

It is each respondent’s responsibility to ensure its proposal is submitted in a manner that enables

GSF to easily locate all requirements stated in this RFP Packet. A respondent is responsible for ensuring all submission material is submitted by the deadline.

Final submissions must be signed by an individual authorized to bind the respondent’s organization contractually, if applicable. An unsigned final proposal may be rejected. A proposal must include a Company Profile that includes, at a minimum, the Business Name, Address, Contact Information, Type, State of Organization, and Names and Titles of all officers.

1.3.5. Irrevocable Offer

A Respondent may withdraw its proposal at any time prior to the submission deadline by using the withdrawal feature in the Procurement Portal. The Respondent may thereafter submit a new or modified proposal prior to the respective submission deadline. Modification offered in any other manner, oral or written, will not be considered.

Other than as allowed by law, final Proposals cannot be changed or withdrawn after the submission deadline date and time. A respondent’s final submission is an irrevocable offer for

180 days from the submission deadline, and after that period respondents may still contract for services under this RFP but will not be required to. Respondents may, but will not be required to, accept a contract award after this 180 day period.

1.3.6. Additional Information Requests

Prior to the award of a contract, GSF must be assured that a selected Respondent has the resources to successfully perform under the contract. This includes, but is not limited to, personnel in number and requisite skill; equipment of appropriate type and quantity; financial resources sufficient to complete performance under the contract; and experience in similar endeavors. If, during the evaluation process, GSF is unable to assure itself of the Respondent’s ability to perform under the contract if awarded, GSF has the option of requesting from the

Respondent any information that GSF deems necessary to determine the Respondent’s responsibility. If such information is required, the Respondent will be so notified and will be permitted five (5) business days to submit the information requested in writing.

2. DELIVERABLES

2.1. ADMINISTRATIVE REQUIREMENTS

Proposals must address each of the requirements in the Deliverables and include all requested information. Narrative descriptions must be clear and apply directly to the solicitation requirements. Any documentation necessary to support narrative descriptions must be included in the submission. Any conflicting information may result in the proposal being deemed non-responsive and may result in the respondent being disqualified.

GSF may reject any or all proposals and may waive any immaterial deviation or defect in a proposal. GSF's waiver of any immaterial deviation or defect shall in no way modify the solicitation documents or excuse the respondent from full compliance with the solicitation specifications if awarded the contract.

2.1.1. Legal Requirements and Attestations

Respondents must attest and confirm their participation and agreement to the following:

• They are following all federal, state, and local regulations.

• They understand they are subject to the PRA when communicating with GSF and will comply with PRA requests.

• They will cooperate with all legal subpoenas received and are responsible for their own legal fees incurred in doing so.

2.1.2. License Required

Each respondent must have all requisite licenses, in active status, necessary to provide the

Deliverables. The proposal must include sufficient information and supporting document to confirm that it meets this requirement.

2.1.3. Financial Security and Stability

Respondents must provide financial statements for the past fiscal year. These include at minimum: Income Statement, Balance Sheet, and Statement of Cash Flow. Tax returns or other similar tax documents will not be accepted. Respondents who provide audited financial statements must provide, to the extent they exist, an Auditor’s Opinion or Notes. Financial statements meeting these requirements provided by any external accounting firm are acceptable.

2.1.4. References

Respondents must provide a minimum of three references where their equipment has been used in a production network.

2.2. TECHNICAL REQUIREMENTS

2.2.1. Technology

Respondents will be scored on their ability to meet the technical requirements listed below. Note that no device (except for ONTs with silk screening) should have a minimum order quantity.

ONTs should have an option for a default vendor silk-screened image that can be ordered without a minimum order quantity.

General Qualifications

• All proposed components must not be listed on the FCC’s Covered List for telecommunications equipment, or it must have a conditional approval from the FCC.

• Please provide any relevant training/courses/certifications for any proposed PON platforms

• While only XGS-PON is required, please include how your proposed solution can be upgraded to 25G or 50G PON in the future

• Please provide references to customers in the US who are using the same platforms. We would need the reference to hop on a 30-minute call or an email chain to tell us about their experiences with your platform.

Quoted Design

• Default design will use 1:32 split

• We have provided a data sheet listing all sites and customer counts. Please select the best

OLT for the location customer count. Please include all necessary optics for that footprint. Assume a 1x 10G LR uplink handoff for each device. Assume N2 XGS-PON optics.

• Control and line card redundancy are optional.

• If you have other features that we have not listed that help differentiate your platform from other vendors, please note them in your documentation

• Please specify if your platform allows for third-party optics or requires vendor coded optics.

OLT

• PON optics will be considered as a part of the OLT equipment proposal. At this time, we are not separating OLT optics out.

• The following features are required:

o Must support XGS-PON o Uplinks must support 10GE with an option to go to 100GE o Support –48v DC power o Optional support for standardized PON protection mechanisms o Certified to operate in non-air-conditioned environments o Offer some SFP+ ports for additional ethernet connectivity o Support for IPTV multicast service delivery without the use of RFOG

▪ A bridged IPTV service would be used to connect customers as needed. (Other methods for providing this service can also be recommended)

▪ IGMP snooping is required for this functionality o Support for provisioning the following kinds of layer 2 services o A VLAN between customers on the same PON or cross PON ports. That would allow for communication between sites.

o An ONU port untagged towards the customer and pushing two vlan tags on traffic up through the OLT.

o A shared VLAN amongst local customers that provides isolation between customer interfaces. Traffic should only be able to talk to the uplink. This shared vlan could be tagged or untagged on the ONU port.

o Provide average power consumption for the device. For chassis-based solutions, all line card slots are filled with XGS-PON cards. The device would be in a non-air-conditioned environment with heat exchangers o Optics should be N2 XGS-PON optics. You can include multi-PON optics if desired but only XGS-PON is required at this time.

o Support for initial boot-up provisioning so that an install tech does not need to console into the device to configure it o Support for Layer 2 and Layer 3 filtering on OLT ports and/or ONT customer ports o Support for downstream encryption so that a neighboring ONT can’t decipher traffic that is destined to other ONTs on the same PON o Support for protecting MAC addresses learned on a port. So that if an untrusted port sends a frame containing the source MAC address of the protected MAC, the frame is dropped o Include any documentation on how to accomplish remote packet captures back to a central datacenter o Devices should have the ability to provide layer 2 isolation of customers on the same

VLAN bridge

▪ Have support for either SNMP, NETCONF, RESTCONF, SSH to interact with the device o NETCONF/RESTCONF and YANG based data models are preferred o Devices and transceivers should follow any existing ITU standards available to ensure compatibility o LACP link aggregation o The OLT must provide a method of remote packet capture and the ability to filter the packet capture to provide traffic data for troubleshooting

• The following features are optional but desired.

o OAM functionality such as TWAMP-Light to monitor a segment of the network and provide loss, latency and connection disruption data to an NMS or user o DHCP Option 82 and similar DHCPv6 functionality.

o Layer 2 Cross-Connect. Be able to identify a customer connection by both S-VID and

C-VID and keep each customer vlan pair isolated.

ONT

• We are looking for ONTs with the following configurations o Propose devices that cover any indoor and outdoor solutions you have o All device costs should include any mounting hardware or brackets o 1 Port 1/2/5/10 GE o 1 Port 1/2/5/10 GE and 1 GE o 2 Port 1/2/5/10 GE o Business/MDU ONTs where 4-8 ports are available for customer connections

• If silk screening services are available for branding, please provide a separate cost to silk screen a company logo and/or a telephone number o If a minimum order quantity is required for silk screening, please note this

• We will primarily use Bridged ONTs (only VLAN bridges, not IP gateway functionality) o You may include layer 3 gateway and Wi-Fi options in your proposal.

• The ONT must be able to be monitored via the OLT, controller software, or via

SNMP/API endpoints on the device o The ONT must provide methods of remote speed testing o We intend to offer 300Mbps services up to 8Gbps. The ONT must be able to support these speeds

• The ONT should support TR069/TR369 with a management IP.

• The ONT must support rate limiting the customer port.

• The ONT must support QinQ interfaces that allow for a transparent bridge of customer vlans and apply a service provider vlan tag on top of the customer vlan.

• The ONT must support basic tagged and untagged interfaces as well.

• When considering costs, we will group similar ONU port layouts together for average cost scoring.

• The ONT must be able to be used on other vendor OLT hardware.

Software Controller/Support

• Please state if a controller software is required, recommended, or not provided for the platform

• If a controller is not required, please state what licensing is required for the OLT/ONTs and what licensing is required for a controller. We would want to carry 24/7 technical support of OLT and ONT hardware, overnight replacement of OLT parts, and any software update costs to maintain the network

• Additional features may be considered outside of the RFP process if GSCA determines there is a need for a licensed feature

• The controller must have a REST-based HTTP API to allow us to integrate it into other internal systems

• If no controller is required and the OLT has a HTTP API or NETCONF API, then YANG models must be provided upon request

• Controllers should include 24/7 technical support and software update costs

• If a controller can be cloud-hosted, provide on-cloud and on-prem costs for the software

• For all devices, you must have a US-based customer contingent and active deployments that utilize the equipment. Vendors who own the manufacturing of their equipment are preferred. White labeled solutions may be considered but have lower preference

• Include a model of costs for a total cost of ownership of the platform o We have included Appendix B - GSF Estimated Forecast and Cost Template (see

ATTACHMENTS), that includes estimated locations passed and customers activated by time and project area.

• This OPEX model of costs for licensing should illustrate a 5-year run time

• If a controller is not required for the operation and management of the shelf, please include in your TCO just the costs for OLT, support, and software updates

2.2.2. Emergency Software Fixes

Please describe how you would respond to an incident where a software fix is needed to address the issue. How quickly would you be able to issue a software patched version that could be installed on production hardware? How often do emergency fixes get merged into a normal minor/major release.

2.2.3. Proposed Provisioning Design

As stated previously, the current plan for open access is to use a Q in Q design where an ONT has an outer tag and each ONT port has an inner tag. All ONTs must support Q in Q encapsulation and have an MTU high enough to accommodate the tags while still allowing for an

IP MTU of 1500 to a customer.

An OLT must accommodate the following scaling guidelines

• VLAN/VPLS services cover 3 services per customer x number of OLT ports on the device

• MAC Address Table size that allows for at least 30,000 learned entries.

2.2.4. ONT Interoperability

The OLT should support third party ONTs. Please provide examples of third party ONTs that you have integrated into the control software and OLT. Please answer the following questions:

• Were these examples full integrations or just “data-only”?

• Are there defined layers of interoperability support and other documentation you can provide on this subject?

2.2.5. United States Based Manufacturing

While not required, present options on how you could comply with the US government’s requirements in BEAD or similar projects that required made in the US devices.

2.2.6. Technical Support

Provide information regarding any technical support and hardware replacement options. Also provide details on the general location of where technical support is located during North

America business hours and off hours. Please also provide the technical support escalation path.

Hardware replacement should include options for advance replacement with overnight shipping.

2.3. OTHER REQUIREMENTS

2.3.1. Indemnification

Respondent must agree that all losses or liabilities incurred by a party shall not be shared pro rata. Instead, the respondent must agree to hold harmless, defend, and indemnify GSF, its agents, officers, and employees, against all claims, suits, actions, costs, expenses (including but not limited to reasonable attorney's fees, expert fees, litigation costs, and investigation costs), damages, judgments or decrees by reason of any person’s or persons’ bodily injury, including death, or property (including respondent’s property) being damaged by the negligent acts, willful acts, or errors or omissions of respondent, or any person employed by or under respondent in any capacity, during the provision of services, except when the injury or loss is caused by the sole negligence or intentional wrongdoing of GSF.

2.3.2. Business Hours

GSF's normal business hours are from 7:00AM to 5:00PM Pacific Time. Respondents will be responsible to coordinate with GSF during these times.

2.3.3. Technical Onboarding

Respondents who are awarded a contract under this RFP are expected to meet with GSF technical representatives for a “technical onboarding” where the different organizations can establish a comprehensive, mutual understanding of technical requirements, expectations, and preferences.

3. EVALUATION

3.1. SELECTION CRITERIA

The evaluation process is designed to select one or more qualified network systems vendors to provide the equipment, software, and services necessary to support the Golden State Fiber (GSF) network. GSF is seeking vendors that, in GSF's judgment, best meet the requirements of this

RFP and provide the best combination of technical capability, value, and cost efficiency.

3.1.1. Scoring

GSF will review each proposal in detail to determine its compliance with the solicitation requirements. GSF reserves the right to use multiple means to validate and determine the respondent’s response to a requirement. This may be through details in its description and/or supporting documentation provided or material that is publicly available, that may either support or contradict the respondent’s claim of intended compliance.

OLT and ONU hardware may be selected from different vendors. Vendors may submit OLT only or ONU only proposals.

This is a best-value request and shall not be determined solely based on price. Proposals will be scored according to how each Respondent will meet the above requirements, as follows:

Technical Scoring

Respondents will gain points on each proposed device based on the following criteria.

• OLT and ONT o Supports required features (highest weight)

• OLT

o S-VID and C-VID based isolation/layer 2 cross-connect support (weighted heavily) o Vendor equipment is OEM and not white labelled (weighed heavily) o OAM Support (Y.1731) (weighed lightly) o Good client references (weighed heavily) o DHCP Option 82 support (weighed lightly)

Cost Scoring

OLT

Given the location and subscriber data attached in this RFP, make a proposal on the best OLT device with enough optics for each location, and any other costs associated with servicing the location. The proposals will be scored based on the following criteria.

• Initial CAPEX costs

• Ongoing yearly costs

*See “Vendor TCO Form” on “Appendix B - GSF Estimated Forecast and Cost Template in the

ATTACHMENTS

ONU

Scoring will be done on the following criteria

• Per unit costs

3.1.2. Scoring Announcement

Scores for all proposals will be posted in the Procurement Portal. Respondents will receive electronic communication on award status.

3.1.3. Contract Award

GSF may choose multiple vendors. Contract(s) shall be awarded by the GSF Executive Director, consistent with scoring determined by a team of evaluators. Respondents may opt not to accept the award at that time.

GSF may choose to not award the contract to the next highest scored proposal, and so on; reject all remaining proposals; or reissue the RFP. An award does not guarantee a purchase of equipment and/or services. GSF will place orders based on need, current availability, lead-times, and other factors as needed.

3.1.4. Appeals

An unsuccessful respondent shall have the right to appeal any scoring decision or contract award decision to GSF's Executive Director. The Executive Director, at their sole discretion, may award a contract notwithstanding the scoring process. In exercising this discretion, the Executive

Director may request to confer with a respondent and/or request additional information or documentation. Should a respondent fail to confer or provide such information or documentation, the Executive Director may decline to consider the appeal. The Executive Director shall have an unlimited amount of time to make any such decisions.

3.1.5. Protests

This procurement process does not include any additional provision beyond the aforementioned appeal to protest either the process or resulting contract award(s).

3.2. SUBMISSION AND ACKNOWLEDGEMENTS

All acknowledgments must be confirmed as a precondition to submitting any proposal. Proposal narratives shall be submitted as a file upload. Some information is requested by text field entry or separate file upload for ease of identification by the scoring team. However, in the event that a respondent includes that information in the uploaded narrative, they may indicate "See

Narrative" in those fields.

Electronic submissions should be submitted in a searchable portable document file (PDF) format, though files may also be submitted in their native format for readability, such as Microsoft Excel files for data tables. Respondents submitting multiple files may do so in a compressed archive format (e.g. a .zip file).

1. Acknowledgements*

In submitting this proposal, respondent declares each of the following:

• Respondent has thoroughly examined all of the contract documents including those contained in the addenda.

• Respondent is following all federal, state, and local regulations.

• Respondent declares that they have fully informed themself as to the conditions, requirements, and specifications of the work.

• Respondent will meet with GSCA technical representatives for a “technical onboarding” if awarded a contract.

• Respondent is familiar with and has satisfied itself as to all State and local laws and regulations and permits required for offering the scope of services.

• Respondent understands that they are subject to the PRA when communicating with GSF and will comply with PRA requests.

• Respondent will cooperate with all legal subpoenas received and are responsible for their own legal fees incurred in doing so.

GSF reserves the right to reject any and all proposals and/or waive any irregularity in any proposal received.

☐ Please confirm

*Response required

2. License Required*

Each respondent must have all requisite licenses, in active status, necessary to provide the

Deliverables. The proposal must include sufficient information and supporting document to confirm that it meets this requirement.

*Response required

3. Financial Security and Stability*

Provide financial statements for the past fiscal year. These include at minimum: Income

Statement, Balance Sheet, and Statement of Cash Flow. Tax returns or other similar tax documents will not be accepted. Respondents who provide audited financial statements must provide, to the extent they exist, an Auditor’s Opinion or Notes. Financial statements meeting these requirements provided by any external accounting firm are acceptable.

*Response required

4. References*

Respondent must include a minimum of three (3) business references to vouch for their financial stability, customer service, and/or character.

Provide the following for each reference:

Company Name and Address:

Contact Person and Phone Number:

*Response required

5. Indemnification

Respondent must agree that all losses or liabilities incurred by a party shall not be shared pro rata. Instead, the respondent must agree to hold harmless, defend, and indemnify GSF, its agents, officers, and employees, against all claims, suits, actions, costs, expenses (including but not limited to reasonable attorney's fees, expert fees, litigation costs, and investigation costs), damages, judgments or decrees by reason of any person’s or persons’ bodily injury, including death, or property (including respondent’s property) being damaged by the negligent acts, willful acts, or errors or omissions of respondent, or any person employed by or under respondent in any capacity, during the provision of services, except when the injury or loss is caused by the sole negligence or intentional wrongdoing of GSF.

☐ Please confirm

6. PROPOSAL UPLOAD*

Describe how you will provide all Deliverables. Please clearly label your responses to ensure all requested technical requirements can be met:

• Technical Criteria:

o General Qualifications o Quoted Design o OLT o ONT o Software Controller/Support

• Emergency Software Fixes

• Proposed Provisioning Design

• ONT Interoperability

• United States Based Manufacturing

• Technical Support

• Cost:

o OLT o ONU

*Response required

4. ATTACHMENTS

A - Overall PON Network Intial DesignB - GSF Estimated Forecast and Cost Template

4. ATTACHMENTS