Public Building Authority of Knox County and Knoxville Tennessee Sealed Solicitation
Title: RFP 2025.003 Parking Management Services
Deadline: 8/8/2024 12:00 PM (UTC-05:00) Eastern Time (US & Canada)
Status: Awarded
Solicitation Number: RFP 2025.003
Description: RFP 2025.003 Parking Management Services
Pre-Bid Meeting Date: 7/25/2024 10:00 AM
Pre-Bid Meeting Details: A pre-proposal conference/teleconference will be held at 10:00 AM, Eastern Standard Time, on JULY 25, 2024 in the G150 conference room of the SUMMER PLACE building in KNOXVILLE, Tennessee. The purpose of the CONFERENCE /TELECONFERENCE is to discuss the work to be performed with the prospective offerors and allow them to ask questions concerning the RFP. All questions raised during the meeting will be posted along with the answers on the PBA website as an Addendum to the RFP, as soon as possible after the meeting. Offerors with a disability needing accommodation should contact the procurement officer prior to the date set for the pre-proposal conference so that reasonable accommodation can be made. Participants may dial into the meeting using the following number: Microsoft Teams Meeting ID 272 310 532 986 and Passcode is AJYhX4. If you would like an email invitation with the Join the meeting now link, please reach out to the procurement specialist for this solicitation.
Documents:
| Documents as of 7/11/2024 |
|---|
| RFP_2025.003_Parking_Management_Services.pdf |
Addition 1
Posted: 7/18/2024
Type of Addition: Addendum 1
Overview: Addendum Issued- RFP 2025.003 Parking Management Services
Deadline: 8/5/2024 11:00 AM
Pre-Bid Meeting Date: 7/25/2024 10:00 AM
Pre-Bid Meeting Details: See solicitation section 1.12.
Solicitation #: RFP 2025.003
Documents:
Addition 2
Posted: 7/26/2024
Type of Addition: Addendum 2 RFP 2025.003 Parking Management Services
Overview: Addendum 2 RFP 2025.003 Parking Management Services
Deadline: 8/5/2024 11:00 AM
Pre-Bid Meeting Date: 7/25/2024 10:00 AM
Solicitation #: RFP 2025.003
Documents:
Addition 3
Posted: 7/30/2024
Type of Addition: Addendum 3
Overview: RFP 2025.003 Parking Management Services Addendum 3
Deadline: 8/8/2024 12:00 PM
Pre-Bid Meeting Date: 7/25/2024 10:00 AM
Solicitation #: RFP 2025.003
Documents:
Addition 4
Posted: 8/8/2024
Type of Addition: In Review
Overview: Submittals received from: Enforce App LLC; Cardinal Tracking, Inc.; ParkMobile, LLC; IPS Group, Inc.; PayByPhone US, Inc.; AIMS Parking Management Software by EDC Corporation; HotSpot Parking USA, Inc.; Passport Labs, Inc.; and T2 Systems Inc.
Addition 5
Posted: 8/30/2024
Type of Addition: Notice of Intended Award
Overview: Please see attached for the Notice of Intended Award for this RFP.
Documents:
Addition 6
Posted: 9/5/2024
Type of Addition: Revised Notice of Intended Award
Overview: This revision is to correct a clerical error. The Notice of Intended Award was published August 30, 2024 on Vendor Registry but the date on the Notice was incorrect. No other information was modified in this Revised Notice of Intended Award.
Documents:
Addition 7
Posted: 9/19/2024
Type of Addition: Award Information
Overview: Intent to Award issued to AIMS Parking Management Software by EDC Corporation and Parkmobile, LLC.
Question 1
Posted: 7/19/2024
Question: Dear Procurement team, Please see the below questions. - Can the City/PBA provide the total number of parking spaces that they are looking to offer mobile payments for? - Can the City/PBA provide a breakdown of this total amount of spaces based on: on-street spaces, surface lot spaces, and garage spaces - Are your garages gated or un-gated? - If your garages are gated- who is your hardware provider? - Do those garages have LPRs? - Can the City/PBA provide the estimated availability of these spaces? i.e - open 24 hours 7 days a week, or only open during weekdays, etc.. - Can the City/PBA provide the estimated demand for these spaces? i.e - always occupied and hard to find space or rarely occupied and always easy to find a spot. Kind regards.
Response: This confirms receipt of your questions. I will issue the answers in the form of an addendum.
Question 2
Posted: 7/19/2024
Question: Dear Procurement team, Please see the below question. Can the City/PBA provide the estimated number of yearly parking transactions for the past 2-3 years? Kind regards.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.
Question 3
Posted: 7/19/2024
Question: Dear Procurement team, Please see the below question. Can the City/PBA provide the estimated number of yearly parking revenue for the past 2-3 years? Kind regards.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.
Question 4
Posted: 7/19/2024
Question: Dear Procurement team, Please see the below question. Can the City/PBA provide the parking rates they will charge? Kind regards.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.
Question 5
Posted: 7/23/2024
Question: In regard to Scope B: Pay-By-Cell Phone Pricing, pricing for this type of service is generally done on a per transaction basis [both for the convenience/transaction fee and for associated processing fees] therefore, can we restructure the matrix to include per transaction fees for parking transaction and credit card processing instead of annual fees? If it stays as an annual fee, please indicate the anticipated number of transactions and the amount of parking revenue collected, so that we are able to price accurately for both convenience fees and processing.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.
Question 6
Posted: 7/23/2024
Question: For onsite training, could PBA/The City provide how many people would need to be trained? This may impact the length of training, as it may have to be done over several days.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.
Question 7
Posted: 7/24/2024
Question: Hello, please see the below questions. Thank you in advance for any clarifications you can provide. When does the City/PBA intend on launching the system? How many off-street spaces are there? How many on-street spaces are there? What is the average hourly rate for the City/PBA’s off-street spaces? What is the average hourly rate for the City/PBA’s on-street spaces? Are the off-street spaces in surface lots or garages? What is the average parking transaction dollar amount? For the City/PBA’s meters that accept credit card payments, who is paying the merchant processing fees: the City/PBA or the provider? Does the City/PBA act as the Merchant of Record with its payment provider? What is the City/PBA’s current card-not-present payment processing rate? What types of handhelds are the enforcement officers using? Does the City/PBA intend on absorbing the convenience fee of the mobile application or will it be passing the cost on to the parkers? How many days of the week is paid parking enforced? Is the City/PBA open to offering multiple vendors for the Parking Management Services solution? Does the current provider charge a convenience fee for online payments? Will the City/PBA accept pass through fees to the violator, or does the City/PBA need to absorb all costs? If pass-through fees are an option, are there any compliance measures the Vendor must follow? Who is the City/PBA’s current credit card processor? What percentage of citations go uncollected each year? What is the escalation schedule for citations? What percentage of citations are handwritten? How many letters/notices will the City/PBA want to send to collect delinquent payments? What is the average fine for each citation and the penalty fine for each escalation period? Does the City/PBA have a preference for a single unit issuance device to smart phone and Bluetooth printer combination?
Response: This confirms receipt of your questions. I will issue the answers in the form of an addendum for all questions except, "Is the City/PBA open to offering multiple vendors for the Parking Management Services solution?", Section 2 states there is no limit to the number of responses and suppliers may respond to one component of the RFP, more than one component, or partner with another supplier. Update 7/26/24- Please clarify question "Will the City/PBA accept pass through fees to the violator, or does the City/PBA need to absorb all costs?". When you say violator, what are you referring to?
Question 8
Posted: 7/25/2024
Question: What specific data formats and communication protocols does the city require for integration with the existing parking management infrastructure? For instance, does the city prefer JSON for data interchange due to its ease of use with web APIs, or perhaps XML for its extensive support in complex data structures? Moreover ,are RESTful APIs the preferred method for interfacing with the city’s databases, or are there other middleware solutions, such as SOAP, that are currently in operation? Could you list the specific enterprise resource planning (ERP) systems, customer management systems, or other operational databases currently in use that the new handheld enforcement devices will need to interface with? For instance, are they required to connect with SAP ERP for real-time data access or Oracle for complex transaction processing? Is there an existing API framework or middleware, such as IBM WebSphere or Microsoft BizTalk, that these devices should be compatible with for seamless integration? What specific integration requirements does the city have for the pay-by-cell system with current third-party services? Are there particular APIs from vendors like Stripe or PayPal for payment processing, or Salesforce for customer interactions that need direct integration? Furthermore, does the city employ specific data interchange formats, such as EDI or FIX protocols, that the system should support to facilitate these integrations efficiently? What specific security measures and compliance standards are required for the mobile License Plate Recognition (LPR) system concerning the storage and transmission of sensitive data? For instance, does the city mandate encryption standards such as AES-256 for data at rest and TLS 1.3 for data in transit? Are there specific requirements for secure data storage locations, both on-premise and in cloud environments, that need adherence to regional or national data protection regulations? Could you specify the preferred communication technologies for Multi-Space Meter (MSM) systems currently planned or installed within the city? For instance, are the systems expected to utilize existing cellular networks, Wi-Fi, or emerging technologies like LPWAN for long-range communications? Are there specific network infrastructures already in place, such as city-wide fiber networks or dedicated IoT networks, that these MSM systems should integrate with for optimized performance and connectivity? What is the city's envisioned strategy for transitioning from the existing parking management systems to the new solutions detailed in the RFP? Are there particular phases, such as pilot testing specific components or a staged implementation, that the city considers critical for ensuring continuity of services and minimal disruption? Could the city outline the specific technical requirements for the image resolution and metadata that must be captured by enforcement handheld devices for effective violation proof? For example, is there a minimum megapixel resolution and are there particular metadata fields like time-stamp, geo-tag, or device ID that must be embedded within each image to comply with legal and operational standards? Could you provide details on the existing connectivity infrastructure within parking garages and off-street parking lots slated for system expansion? What types of network connections are available—such as fiber optic, broadband, or wireless LTE—and what bandwidth capacities are typically accessible in these areas? Furthermore, are there specific functional modules that need to be developed or adapted to ensure compatibility and performance consistency with the varied connectivity environments compared to existing urban parking systems? Does the city require the new citation management system to integrate with other municipal systems for real-time data sharing related to citation disputes, resolutions, and status updates? If so, could you specify which municipal systems—such as judicial systems, traffic management, or public safety databases—are involved, and what types of data or communication protocols should be supported to facilitate this integration? In aligning with state and federal transportation regulations, how is the parking management system expected to interface with the Motor Vehicle Administration (MVA) or Department of Transportation (DOT) systems? Are there specific data security standards, such as encryption protocols or secure data exchange frameworks, that need to be implemented? Could you also detail any mandated data sharing protocols or compliance checkpoints that must be integrated into the system’s operations to ensure regulatory alignment? Could you specify the functionalities required for the dispute and appeal management module within the parking management system? How should the system facilitate seamless communication between disputants, enforcement agencies, and adjudication authorities? Are there particular features, such as automated notifications, document upload capabilities, or real-time status updates, that the city considers essential for effectively managing and resolving disputes and appeals? Does the city envision a specific workflow within the appeals module that accommodates the integration of multimedia evidence, such as photos or videos, submitted by citizens? What are the requirements for managing and securely storing this type of data? Could you specify how long multimedia evidence should be retained within the system, and under what conditions it may be accessed or shared, to ensure compliance with privacy and data protection laws? Could the city specify its requirements for real-time reporting of citation status changes within the parking management system? What specific statuses and milestones are essential for stakeholders to monitor—such as issuance, payment, dispute initiation, and resolution? Furthermore, how should these status updates be communicated to different stakeholders, including city officials, law enforcement, and the disputing parties? Does the city prefer these notifications via email, SMS, or a dedicated dashboard within the system, and are there particular security protocols that must be followed when transmitting sensitive information? What permissions and controls are designated for enforcement officers within the parking management system regarding the modification or cancellation of issued tickets? Can officers make these changes directly in the field, and if so, what specific audit trails or approval processes must be followed to maintain system integrity and accountability? Are there particular scenarios or conditions, such as system errors or disputed evidence, under which these modifications are permitted? Does the city have specific requirements for audit trails and tracking mechanisms to monitor any alterations made to tickets by enforcement officers within the parking management system? Could you detail the level of granularity expected in these audit logs, such as time stamps, officer IDs, original ticket details, and the nature of the modifications? Moreover, what safeguards or protocols should be in place to ensure these logs are tamper-proof and comply with local governance policies? How does the city intend for the citation management system to manage unpaid citations, particularly in terms of escalating these cases to collection agencies? What data fields and documents must be shared with these agencies, and are there specific formats or secure transmission methods that need to be adhered to? Furthermore, are there predefined thresholds or criteria, such as the amount owed or time elapsed, that trigger the escalation process, and how should these be programmatically managed within the system?
Response: This confirms receipt of your questions. I will issue the answers in the form of an addendum.
Question 9
Posted: 7/25/2024
Question: Are the primary goals of the account based systems around managing permits? Can you tell us where you use PARCS data today and what information you want our system to communicate to the PARCS system? Are you looking for on-street and off-street permits? If yes, do you have a breakdown of the number of permits for those 2 types? Can you confirm that the TN DMV has the ability to do RO holds for parking citations? Does your interest in mobile pay options apply to your on-street and off-street spaces? Thank you!
Response: This confirms receipt of your questions. I will issue the answers in the form of an addendum.
Question 10
Posted: 7/26/2024
Question:
Response: No question submitted.
Question 11
Posted: 7/26/2024
Question: Item 2.2.1 - Historical data will be provided in .csv format. To determine scope of work, please provide information on data to be converted (citation, permit, person, transaction/finance) and the current vendor/system that the data will be exported from.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.
Posted: 7/18/2024
Type of Addition: Addendum 1
Overview: Addendum Issued- RFP 2025.003 Parking Management Services
Deadline: 8/5/2024 11:00 AM
Pre-Bid Meeting Date: 7/25/2024 10:00 AM
Pre-Bid Meeting Details: See solicitation section 1.12.
Solicitation #: RFP 2025.003
Documents:
Posted: 7/26/2024
Type of Addition: Addendum 2 RFP 2025.003 Parking Management Services
Overview: Addendum 2 RFP 2025.003 Parking Management Services
Deadline: 8/5/2024 11:00 AM
Pre-Bid Meeting Date: 7/25/2024 10:00 AM
Solicitation #: RFP 2025.003
Documents:
Posted: 7/30/2024
Type of Addition: Addendum 3
Overview: RFP 2025.003 Parking Management Services Addendum 3
Deadline: 8/8/2024 12:00 PM
Pre-Bid Meeting Date: 7/25/2024 10:00 AM
Solicitation #: RFP 2025.003
Documents:
Posted: 8/8/2024
Type of Addition: In Review
Overview: Submittals received from: Enforce App LLC; Cardinal Tracking, Inc.; ParkMobile, LLC; IPS Group, Inc.; PayByPhone US, Inc.; AIMS Parking Management Software by EDC Corporation; HotSpot Parking USA, Inc.; Passport Labs, Inc.; and T2 Systems Inc.
Posted: 8/30/2024
Type of Addition: Notice of Intended Award
Overview: Please see attached for the Notice of Intended Award for this RFP.
Documents:
Posted: 9/5/2024
Type of Addition: Revised Notice of Intended Award
Overview: This revision is to correct a clerical error. The Notice of Intended Award was published August 30, 2024 on Vendor Registry but the date on the Notice was incorrect. No other information was modified in this Revised Notice of Intended Award.
Documents:
Posted: 9/19/2024
Type of Addition: Award Information
Overview: Intent to Award issued to AIMS Parking Management Software by EDC Corporation and Parkmobile, LLC.
Posted: 7/19/2024
Question: Dear Procurement team, Please see the below questions. - Can the City/PBA provide the total number of parking spaces that they are looking to offer mobile payments for? - Can the City/PBA provide a breakdown of this total amount of spaces based on: on-street spaces, surface lot spaces, and garage spaces - Are your garages gated or un-gated? - If your garages are gated- who is your hardware provider? - Do those garages have LPRs? - Can the City/PBA provide the estimated availability of these spaces? i.e - open 24 hours 7 days a week, or only open during weekdays, etc.. - Can the City/PBA provide the estimated demand for these spaces? i.e - always occupied and hard to find space or rarely occupied and always easy to find a spot. Kind regards.
Response: This confirms receipt of your questions. I will issue the answers in the form of an addendum.
Posted: 7/19/2024
Question: Dear Procurement team, Please see the below question. Can the City/PBA provide the estimated number of yearly parking transactions for the past 2-3 years? Kind regards.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.
Posted: 7/19/2024
Question: Dear Procurement team, Please see the below question. Can the City/PBA provide the estimated number of yearly parking revenue for the past 2-3 years? Kind regards.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.
Posted: 7/19/2024
Question: Dear Procurement team, Please see the below question. Can the City/PBA provide the parking rates they will charge? Kind regards.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.
Posted: 7/23/2024
Question: In regard to Scope B: Pay-By-Cell Phone Pricing, pricing for this type of service is generally done on a per transaction basis [both for the convenience/transaction fee and for associated processing fees] therefore, can we restructure the matrix to include per transaction fees for parking transaction and credit card processing instead of annual fees? If it stays as an annual fee, please indicate the anticipated number of transactions and the amount of parking revenue collected, so that we are able to price accurately for both convenience fees and processing.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.
Posted: 7/23/2024
Question: For onsite training, could PBA/The City provide how many people would need to be trained? This may impact the length of training, as it may have to be done over several days.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.
Posted: 7/24/2024
Question: Hello, please see the below questions. Thank you in advance for any clarifications you can provide. When does the City/PBA intend on launching the system? How many off-street spaces are there? How many on-street spaces are there? What is the average hourly rate for the City/PBA’s off-street spaces? What is the average hourly rate for the City/PBA’s on-street spaces? Are the off-street spaces in surface lots or garages? What is the average parking transaction dollar amount? For the City/PBA’s meters that accept credit card payments, who is paying the merchant processing fees: the City/PBA or the provider? Does the City/PBA act as the Merchant of Record with its payment provider? What is the City/PBA’s current card-not-present payment processing rate? What types of handhelds are the enforcement officers using? Does the City/PBA intend on absorbing the convenience fee of the mobile application or will it be passing the cost on to the parkers? How many days of the week is paid parking enforced? Is the City/PBA open to offering multiple vendors for the Parking Management Services solution? Does the current provider charge a convenience fee for online payments? Will the City/PBA accept pass through fees to the violator, or does the City/PBA need to absorb all costs? If pass-through fees are an option, are there any compliance measures the Vendor must follow? Who is the City/PBA’s current credit card processor? What percentage of citations go uncollected each year? What is the escalation schedule for citations? What percentage of citations are handwritten? How many letters/notices will the City/PBA want to send to collect delinquent payments? What is the average fine for each citation and the penalty fine for each escalation period? Does the City/PBA have a preference for a single unit issuance device to smart phone and Bluetooth printer combination?
Response: This confirms receipt of your questions. I will issue the answers in the form of an addendum for all questions except, "Is the City/PBA open to offering multiple vendors for the Parking Management Services solution?", Section 2 states there is no limit to the number of responses and suppliers may respond to one component of the RFP, more than one component, or partner with another supplier. Update 7/26/24- Please clarify question "Will the City/PBA accept pass through fees to the violator, or does the City/PBA need to absorb all costs?". When you say violator, what are you referring to?
Posted: 7/25/2024
Question: What specific data formats and communication protocols does the city require for integration with the existing parking management infrastructure? For instance, does the city prefer JSON for data interchange due to its ease of use with web APIs, or perhaps XML for its extensive support in complex data structures? Moreover ,are RESTful APIs the preferred method for interfacing with the city’s databases, or are there other middleware solutions, such as SOAP, that are currently in operation? Could you list the specific enterprise resource planning (ERP) systems, customer management systems, or other operational databases currently in use that the new handheld enforcement devices will need to interface with? For instance, are they required to connect with SAP ERP for real-time data access or Oracle for complex transaction processing? Is there an existing API framework or middleware, such as IBM WebSphere or Microsoft BizTalk, that these devices should be compatible with for seamless integration? What specific integration requirements does the city have for the pay-by-cell system with current third-party services? Are there particular APIs from vendors like Stripe or PayPal for payment processing, or Salesforce for customer interactions that need direct integration? Furthermore, does the city employ specific data interchange formats, such as EDI or FIX protocols, that the system should support to facilitate these integrations efficiently? What specific security measures and compliance standards are required for the mobile License Plate Recognition (LPR) system concerning the storage and transmission of sensitive data? For instance, does the city mandate encryption standards such as AES-256 for data at rest and TLS 1.3 for data in transit? Are there specific requirements for secure data storage locations, both on-premise and in cloud environments, that need adherence to regional or national data protection regulations? Could you specify the preferred communication technologies for Multi-Space Meter (MSM) systems currently planned or installed within the city? For instance, are the systems expected to utilize existing cellular networks, Wi-Fi, or emerging technologies like LPWAN for long-range communications? Are there specific network infrastructures already in place, such as city-wide fiber networks or dedicated IoT networks, that these MSM systems should integrate with for optimized performance and connectivity? What is the city's envisioned strategy for transitioning from the existing parking management systems to the new solutions detailed in the RFP? Are there particular phases, such as pilot testing specific components or a staged implementation, that the city considers critical for ensuring continuity of services and minimal disruption? Could the city outline the specific technical requirements for the image resolution and metadata that must be captured by enforcement handheld devices for effective violation proof? For example, is there a minimum megapixel resolution and are there particular metadata fields like time-stamp, geo-tag, or device ID that must be embedded within each image to comply with legal and operational standards? Could you provide details on the existing connectivity infrastructure within parking garages and off-street parking lots slated for system expansion? What types of network connections are available—such as fiber optic, broadband, or wireless LTE—and what bandwidth capacities are typically accessible in these areas? Furthermore, are there specific functional modules that need to be developed or adapted to ensure compatibility and performance consistency with the varied connectivity environments compared to existing urban parking systems? Does the city require the new citation management system to integrate with other municipal systems for real-time data sharing related to citation disputes, resolutions, and status updates? If so, could you specify which municipal systems—such as judicial systems, traffic management, or public safety databases—are involved, and what types of data or communication protocols should be supported to facilitate this integration? In aligning with state and federal transportation regulations, how is the parking management system expected to interface with the Motor Vehicle Administration (MVA) or Department of Transportation (DOT) systems? Are there specific data security standards, such as encryption protocols or secure data exchange frameworks, that need to be implemented? Could you also detail any mandated data sharing protocols or compliance checkpoints that must be integrated into the system’s operations to ensure regulatory alignment? Could you specify the functionalities required for the dispute and appeal management module within the parking management system? How should the system facilitate seamless communication between disputants, enforcement agencies, and adjudication authorities? Are there particular features, such as automated notifications, document upload capabilities, or real-time status updates, that the city considers essential for effectively managing and resolving disputes and appeals? Does the city envision a specific workflow within the appeals module that accommodates the integration of multimedia evidence, such as photos or videos, submitted by citizens? What are the requirements for managing and securely storing this type of data? Could you specify how long multimedia evidence should be retained within the system, and under what conditions it may be accessed or shared, to ensure compliance with privacy and data protection laws? Could the city specify its requirements for real-time reporting of citation status changes within the parking management system? What specific statuses and milestones are essential for stakeholders to monitor—such as issuance, payment, dispute initiation, and resolution? Furthermore, how should these status updates be communicated to different stakeholders, including city officials, law enforcement, and the disputing parties? Does the city prefer these notifications via email, SMS, or a dedicated dashboard within the system, and are there particular security protocols that must be followed when transmitting sensitive information? What permissions and controls are designated for enforcement officers within the parking management system regarding the modification or cancellation of issued tickets? Can officers make these changes directly in the field, and if so, what specific audit trails or approval processes must be followed to maintain system integrity and accountability? Are there particular scenarios or conditions, such as system errors or disputed evidence, under which these modifications are permitted? Does the city have specific requirements for audit trails and tracking mechanisms to monitor any alterations made to tickets by enforcement officers within the parking management system? Could you detail the level of granularity expected in these audit logs, such as time stamps, officer IDs, original ticket details, and the nature of the modifications? Moreover, what safeguards or protocols should be in place to ensure these logs are tamper-proof and comply with local governance policies? How does the city intend for the citation management system to manage unpaid citations, particularly in terms of escalating these cases to collection agencies? What data fields and documents must be shared with these agencies, and are there specific formats or secure transmission methods that need to be adhered to? Furthermore, are there predefined thresholds or criteria, such as the amount owed or time elapsed, that trigger the escalation process, and how should these be programmatically managed within the system?
Response: This confirms receipt of your questions. I will issue the answers in the form of an addendum.
Posted: 7/25/2024
Question: Are the primary goals of the account based systems around managing permits? Can you tell us where you use PARCS data today and what information you want our system to communicate to the PARCS system? Are you looking for on-street and off-street permits? If yes, do you have a breakdown of the number of permits for those 2 types? Can you confirm that the TN DMV has the ability to do RO holds for parking citations? Does your interest in mobile pay options apply to your on-street and off-street spaces? Thank you!
Response: This confirms receipt of your questions. I will issue the answers in the form of an addendum.
Posted: 7/26/2024
Question:
Response: No question submitted.
Posted: 7/26/2024
Question: Item 2.2.1 - Historical data will be provided in .csv format. To determine scope of work, please provide information on data to be converted (citation, permit, person, transaction/finance) and the current vendor/system that the data will be exported from.
Response: This confirms receipt of your question. I will issue the answers in the form of an addendum.