AI Roadway and ROW Monitoring Services

The vendor required to provide artificial intelligence (AI) solution to monitor and assess roadway and right-of-way (ROW) conditions, including asset and property conditions that are visible from the roadway and right-of-way areas, and create, process, and track related internal work orders and cases.
- Work requirements
1. Adherence to existing and future related city policies and procedures
•    Ability to conduct and lead discovery with the relevant internal city agencies and potential external city agencies and deliver a product and suite of products that interact seamlessly to address existing and future departmental processes 
•    Ability to provide access to system software for a number of pre-determined users across multiple departments and relevant internal and external agencies. 
•    Cloud storage is required for all data and system processing, with on-premise storage and processing offered as an added option. 
•    No storage or processing shall take place outside of the country. 
•    A data backup is required, and the data obtained from utilization of such products shall be solely owned by the city of myrtle beach and in the public domain. 
•    Both hardware and software should be provided by the offeror. 
•    Any hardware proposed to be used on city infrastructure or assets should allow for the temporary (non-permanent) retrofitting of existing infrastructure and assets, without reducing the expected useful life or negatively impacting the functionality of the infrastructure or asset. 
•    Retrofitting must not permanently and physically alter the city infrastructure or city asset. 
•    Ability and agreement to segregate collected and provided city information, with a non-sharing clause, to protect city and public data from unauthorized use. 
•    This requirement includes the segregation of provided data from the city, collected data from the offeror and offeror’s products, and data provided to the offeror’s affiliated contractors and their products and solutions, so that the data does not train non-local large language models (LLMS), i.e., data acquired under the duration of the awarded contract terms cannot be used to train LLMS or other solutions of the offeror or their affiliates without express and written authorization from the city, especially for LLMS or other solutions utilized outside of the sole purposes of the awarded contract and the city of myrtle beach.
2. Condition monitoring and assessment
•    Pavement and sidewalk variations such as cracks, faults, holes, potholes, etc.
•    documentation of pavement condition index (PCI) ratings, by local, state, and federal standards 
•    Traffic and other city signage conditions such as degradation, defacement, blockage and impairment, and damage 
•    Street and pavement marking conditions such as degradation, defacement, disappearance, and damage 
•    Traffic and other city roadway and right-of-way asset conditions. 
•    Assets can include, but are not limited to: fire hydrants, medians, streetlights, utility boxes, poles, pumps, etc. 
•    Vegetation conditions and variations, such as overgrowth, disease, roadway and ROW obstruction, grass height, etc. 
•    Accumulation of trash and garbage on private and public property 
•    Structural, building, and aesthetic (including graffiti) damage and degradation that is in violation of city standards, zoning and nuisance code, the international property maintenance code (IPMC), international building code (IBC), and the international fire code (IFC) 
•    Illegal encampments of persons or things in the city ROW, on public property, or visible from the roadway or right-of-way 
•    Inventorying of traffic, other city signage, and city assets in the roadway or ROW 
•    HIL verification and edit rights, post inspection and detection 
•    Monitoring and assessment must include documentation (written, video, and photographic) and reporting functionality, filtered by asset, roadway, property, and ROW type, location and mapping (integrated with ArcGIS), names, and ownership 
•    Ideal detection parameters are within no less than twelve (12) inches and at least thirty (30) feet out, with the ability to capture up to three (3) stories of a building. 
•    Pictorial and video documentation should have a resolution of at least 1920 x 1080 p, or 300ppi in print/72 PPI in digital. 
•    Any processing required by the AI system, shall occur at the edge prior to the data being transferred to the cloud or on-premise servers, including the removal of all protected personal or private information (PPI) captured by the system software or hardware (ex: license plates, individual faces, etc.) such PPI is strictly prohibited from storage or use in all circumstances. 
•    Non-duplication of conditions and assessments previously documented within the system, whether it was automatically documented or entered by a human-in-the-loop (HIL). 
•    Ability to have conditions and assessments automatically updated by the system, with optional manual updates entered by designated staff.
3. Creation, processing, tracking of work orders and cases
•    Integration with existing and future city internet of things (IOT) infrastructure and devices, such as cell phones, tablets, drones, cameras, sensors, networks, data processing platforms, work order systems, on-premise and cloud-based servers, etc. 
•    The systems deployed from the offeror should cover the creation, process of resolution (cost, time, labor responsible party, etc.), and close out of any cases or work orders that are the direct result of a detection or assessment by the solution(s) provided, or added into the system via manual entry by staff. 
•    This should include a minimum of a web-based and mobile (cellular and accessible inf the field) platform that is easy to navigate and easy to search cases and work orders, with metrics displayed on a dashboard with filtering by status, asset, roadway, property, ROW type, names, and ownership.
•    Cases and work orders shall provide the minimum documentation noted above, as well as department owners, staff member assignments (including auto and manual assignments), escalation protocols, and integration with existing work order and case management systems the city has. 
•    System should have the ability to share all information via API calls or direct data links, to a number of systems (existing and future.) such data sharing should be in real time as is feasible.
4. AI risk mitigation
•    An “AI incident” is an alleged harm or near harm event to people, property, reputation, or technical integrity of the environment where an AI system is implicated. 
•    AI incidents include, but are not limited to: false information, copyright infringement, generating harmful bias, system misuse, exposure of sensitive information, and liability risk. 
•    The event of an AI incident, at the request of the city of myrtle beach, the offeror shall promptly and thoroughly investigate their system of any suspected AI incident and report the findings to the city. 
•    The city’s request, the contractor will immediately discontinue the use of any AI system involved in providing services to the city.

- Contract Period/Term: 1 year
- Questions/Inquires Deadline: November 10, 2025