Attachment H -Commonwealth's Response to Vendors' Written Questions.xlsx
XLSX spreadsheet 21 KB Posted
- Solicitation number
- RFP-758-2400000268-2
- Issued by
- Franklin County, Kentucky
About this file
This document is the Commonwealth's Response to Vendors' Written Questions regarding RFP 758 2400000268 for an ADS-B Aircraft Surveillance and Reporting Tool System (ADS-B & RTS) for the Kentucky Department of Aviation (KDA). The RFP seeks to obtain a statewide operational data system on airport operations to improve allocation of funds and obtain other benefits such as noise complaint management and noise abatement procedures across 54 non-commercial Kentucky airports, with the potential to add 3 commercial service airports. The mandatory requirements include the ability to detect commercial service gate arrivals and pushbacks, record and store specific events, and have experience with statewide contracts similar to this scope. The Commonwealth clarifies and revises certain requirements in response to vendor questions.
The revised RFP clarifies that the focus is on non-commercial airports, with noise abatement procedures as a requirement, not just a value-add option. The Commonwealth indicates it has existing cloud platform contracts that vendors can leverage. Specific details on KITS and COT IT standards are provided, and the Commonwealth reiterates that proprietary customer information will be protected.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| RFP 758 2400000268 - ADS-B Aircraft surveilance and RTS |
| Attachment H - Commonwealth's Response to Vendors' Written Questions |
| RFP Section / Requirement Number | Document | Document Page Number | Vendor Questions | Commonwealth Response |
| Section 3.1.A.2. | RFP Attachment A - Terms and Conditions | 5 | Is the mandatory requirement for MLAT for passive MLAT or a MLAT solution with an interregator (to come closer to, but still not achieving the stated mandatory accuracy) as most of the Kentucy airports do not have Radar on site ? | See revised Section 3.1.A.2 in Attachment A. |
| Section 3.1.A.2. | RFP Attachment A - Terms and Conditions | 5 | As MLAT requires at least 3 to 4 receivers located at least tens of miles from the airport, does KDA wish to provide any guidance with respect to site identification and installation? | No, this information is not available. |
| Section 3.1.A.2. | RFP Attachment A - Terms and Conditions | 5 | Requested minimum capabilities include accuracy within one to three feet of aircraft position. These systems receive positional data from equipment on board aircraft and are dependent on aircraft avionics for accuracy and those avionics depend on external sources including GPS and WAAS. The avionics onboard the aircraft and external sources are not guaranteed the requested accuracy and they are the source for posiional data received by the surveillance systems. Suggest removing/restating this requirement. | KDA recognizes system latency issues. Vendors' response should explain it's ability to meet the requirements of this RFP. |
| Section 3.1.A.4. and Section 3.1.A.5. | RFP Attachment A - Terms and Conditions | 5 | Section 2.2 Background indicates the purpose of this procurement is to obtain state-wide operational data on airport operations to improve allocation of funds and to obtain other unanticipated benefits. Mandatory requirements 4 and 5 address noise compliants and noise abatement procedures. Noise complaint management and tracking noise abatelent procedures are curiously not included in the list of what appears to be the top three unanticipated benefits. We can see how addressing noise complaints and noise abatement may be Value-Add options proposed, but why are they required to meet the objectives of this procurement ? Suggest they get removed and considered under Value-Add. | See revised Section 2.2 and 3.1 in Attachment A. Noise abatement procedures/complaints is one of the requirements of this RFP and It is an anticpated benefit of the system. |
| Section 3.1.A.8. | RFP Attachment A - Terms and Conditions | 5 | Section 3.1 states "awarded contract shall provide an ADS-b Airport Surveillance and RTS for all fifty-four (54) Non-Commercial KY Airports." and that KDA may add three commercial services airports. It seems that any vendor that can support flexible geofence configurations can meet this requirement. Why would the ability to detect commercial service gate arrivals and pushbacks be a mandatory requirement when the focus seems clearly to be on non-commercial airports ? Why was this requirement worded this way versus KDA using a more competition favorable generic approach this type of capability ? | See revised Section 2.2 and Section 3.1. |
| Section 3.1.C.3 | RFP Attachment A - Terms and Conditions | 6 | Could KDA specify desired events to by recorded and stored ? | See revised Section 3.1.C.3. in Attachment A. |
| Section 3.1.E.1.a. | RFP Attachment A - Terms and Conditions | 6 | To our knowledge there have been three statewide contracts issued to two vendors. Is the intent of this mandatory requirement to limit the competition to these two vendors and not consider others ? | See revised Section 2.2 in Attachment A. |
| Section 3.1.E.1.c. | RFP Attachment A - Terms and Conditions | 6 | Customer list is proprietary and competition sensitive information. What is KDA's objective in obtaining this information? It seems KDA would be concerned about a vendors ability to install, support and maintain an infrastructure at least as large as the 57 KDA contemplates. Could that objective be achieved another way ? | See Sections 5.7 and 6.6 in Attachment A regarding proprietary information. |
See revised Section 3.1 in Attachment A.
Section 3.1.E.2.b. RFP Attachment A - Terms and Conditions 6 This is curiously worded, includes some requirements and is silent on others. Would a more appropriate mandatory requirement be worded something like "Vendor must comploy with FAA, State and Airport regulations, policy and guidance when operating on an airport" ? See revised Section 3.1.E.2.b. in Attachment A.
| Section 4.1. | RFP Attachment A - Terms and Conditions | 7 | Does the Commonweath have existing contracts in place with AWS and/or Azure governement cloud platforms so KDA can take advantage of potential pricing advantages and address security requirements/concerns in a more streamlined approach ? | See Section 4.10, "Any third-party software licenses and cloud resources necessary for the proposed solution may be procured via the Commonwealth’s existing contracts." |
| Section 4.1.6 | RFP Attachment A - Terms and Conditions | 13 | Can KDA provide more information on KITS and COT Information Technology Standards Policy currently CIO-051. | Section 4.1.6 does not exist. Section 4.3 includes a link to the KITS which includes additional information regarding KITS. See Section 4.2 for the link to COT policies. Then click 'Policies and Procedures' for COT policies including CIO-051. |
RFP 758 2400000268
RDS-B Aircraft Surveillance & RTS
File details come from the government source that posted it. Updated .