Project: Inspector Prioritization Automation

[TracyLinder]

The Inspector Prioritization Automation Project focuses on creating tools to allow Right of Way Management traffic control inspectors to better prioritize their inspection workload based on priorities identified by the division and department.

Background

An internal city audit performed in 2018 identified the need for ROW’s traffic control inspection group to better prioritize the inspections they perform. On an average day there are over 4,000 active Right-of-Way permits that are eligible for a traffic control inspection. This number far outweighs ATD’s available resources to provide inspections, resulting in a need to prioritize the inspections we choose to perform.

Right of Way Management has identified key metrics that will allow us to rate inspection priorities based on things such as location, proximity to critical infrastructure, project impact, and the contractor’s history of traffic control violations.

Scope & Deliverables

The scope includes developing automated tools that will score permits based on key metrics, and provide the traffic control inspections group with a prioritized list of inspections. Phase 2 of this project may include a dashboard for the inspectors.

Desired Outcomes

Success for this project means the traffic control inspectors are better able to identify the highest priority inspections, resulting in our ability to correct deficiencies in our highest impact areas. Deficiency correction provides safer roadways, and better traffic flow.

---

This Github issue represents a project of Austin Transportation's Data & Technology Services team. Project status is documented regularly in the comments below.

Resources

Configuration Information SharePoint Site Folder of weekly lists

[TracyLinder]

Update

All future phases of this project are on hold. We are however continuing to work on automating the portion of work done to-date. See the epic for this portion here.

[TracyLinder]

10/28/19 - R. Ward asked if the output can be pushed to KNACK, instead of an excel file in SharePoint.

[amenity]

@johnclary - putting this in the backlog until we have more PM capacity.

[TracyLinder]

Note to Self: If we rely on open data for this solution, we won't be able to include franchised information as it will not be published. @johnclary FYI

[johnclary]

Fair point. This adds quite a bit to the level of effort. TBH when we talked about the legal concerns I thought we kinda decided that it was OK for us to publish the street segments for franchise permits 🤔. Let's talk about this during 1:1

[johnclary]

We delivered an initial, manual prototype of this solution and need to re-prioritize further development. Since we last visited this work we have gained programmatic access to AMANDA, so we are essentially unblocked.

[TracyLinder]

Update Oct 25, 2023

ROW Management supervisors confirmed recently that their inspection group still needs a solution for prioritizing their work. I've closed all of the current issues related to this project as they represented tasks from the work we did in 2021. I do not anticipate that DTS will build on what we created in 2021; it's more likely we will build a new solution from scratch. (TBD) Next steps will be to meet with Darren U. to discuss priority, and then put it on the DTS Product Sync agenda. I also plan to discuss this need with DTS's Data Science team during our planning session tomorrow 10/26.

[TracyLinder]

Update Nov 1, 2023

After feedback from the Data Science team I combed the archives looking for all existing documentation; I added the resources I found to this project index description. I scheduled a meeting for 11/13/2023 with Darren, Charlie and Rebekka to discuss the following:

• Quick background overview
• Clarify the business need (use cases)
• Look at existing project documentation together
• Next steps and timeline

[TracyLinder]

Update Aug 2024

During ROW Project prioritization with ROW, this is still a need. We should determine the effort involved with creating a KNACK site as part of the solution; it could be small project sized or even epic sized. If PowerBi is the fastest solution, ROW would like to start there.

[TracyLinder]

Data Science Planning 10/30/24

• We've decided to move forward with deploying John's old code and going from there.

Next Steps:

1. Create ETL (Charlie) 3
2. Create PBI Report with the data (New space, not adding to ROW's existing performance measure dashboard) 2
3. Begin stakeholder review

[TracyLinder]

Project Update Nov 2024

I officially moved this project index to In Progress today. It's important to note that DTS doesn't have the PM capacity to apply our full project methodology to this project, however we recognize that this is a high priority for ROW and that we (DTS) have a data science resource to perform this work incrementally in two week sprints.

Charlie is currently working on setting up the ETL that will be used for the PowerBI dashboard.