Incorporate maintenance dates in the `Sign Assets` GIS dataset

[atdservicebot]

What application are you using?

SMD Data Tracker

Describe the problem.

Signs Dataset Enhancements - With the RAS signs data collection complete, we have identified 2 necessary enhancements to keep the RAS data accurate and up to date. 1) Update signs data flow. Looking to explore options to find the best solution to maintaining the RAS dataset against the signs work that is performed daily and tracked in Data Tracker.

• 15008 was created and will be used to track this ask in more detail as we explore options.

• This will become a project so I created #17301. Completing this project will address request 2 👇🏼 2) Address maintenance work. New/Removed signs assets are currently being reconciled between Data Tracker work orders and the RAS dataset but maintenance work is not. Until there is a new signs data workflow that can account for maintenance work, we need to find a solution to reconcile maintenance work.

Describe the outcome you'd like to see when this feature is implemented.

SMD will have a signs data flow that ensures accurate and up to date information for all signs work types is being captured in the RAS dataset.

Describe any workarounds you currently have in place or alternative solutions you've considered.

Manual reconciliation process for New/Removed signs between Data Tracker and RAS. No current process for maintenance reconciliation. For our FY24 signs maintenance plan, we did a quick spatial analysis to account for maintenance work as best as we could but we need a more accurate and long term solution.

Requested By Kati C.

Request ID: DTS23-111600

[ChristinaTremel]

@susannegov and @andrewshensky assigning y'all because we've been discussing this in the SMD GIS QA Check-Ins. I believe we already have issues for these items so I'll associate them to this issue as well.

It sounds like SMD is wanting to elevate the priority of request 2, but I think the solution Andrew suggested of updating signs with maintenance dates based on a buffer around the RAS data is going to be the quickest way to give SMD some maintenance data on their sign assets.

[ChristinaTremel]

Use Case

• SMD will be using this for creating their annual maintenance plan

Plan

• Only filter maintenance records from October 2021 to current date
• Only filter for specifications Install - Replace
• Plan to create a separate dataset with the data and do some QC on the output
• If everything looks good, we can bring this maintenance date data into the sign_assets dataset.

Biggest concern and question:

• @ChristinaTremel discuss the concerns and assumptions we'll make throughout this process
  • Not a good way to tie back the actual stop sign record that was actually maintained. If one is replaced, then likely all are replaced.
  • What would be easier is take the maintenance record and tie it back to the closest location. A stop sign was maintained, so there was maintenance at that location.
    • Need to confirm that the level of accuracy is okay for the SMD team
    • If they went out there and there's 5 signs and they replace one of those signs, the most straight forward way of addressing these is to give all of those 5 signs the same maintenance record. This would make sense to me because technicians wouldn't maintain one sign and keep the others in poor condition, so the assumption that those signs are in good condition seems valid.