Change Requester name from "SIGNS AND MARKINGS" to "SMD MAINTENANCE PLAN"

[atdservicebot]

What application are you using?

Signs & Markings Operations

Describe the problem.

Add "SMD Maintenance Plan" as REQUESTER option for Signs | Work Orders, Markings | Work Orders, and Contractor | Work Orders

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

Signs and Markings will have data to inform on how many work orders have been completed and the status based on this REQUESTER type.

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

Possible to do it based on Created By/Created Date but it requires knowing specifically when work order is created and possible that there were multiple creations by different people. Also possible to filter by a list of Work Order IDs, but difficult if there is a large amount of work orders.

Is there anything else we should know?

Before April 1st for implementation

Requested By Susanne G.

Request ID: DTS23-106680

[susannegov]

Talking to Lauren/Cathy this morning, they requested to rename SIGNS AND MARKINGS requester type to SMD PLANNED MAINTENANCE? Also, rename MAINTENANCE to TECHNICIAN for clarity.

This also means renaming previous work order that were MAINTENANCE/SIGNS AND MARKINGS to those fields.

Question for @ChristinaTremel - is the SMD technician is able to change their requester type or is it auto populated based on user role?

[ChristinaTremel]

@susannegov the SMD technician can't change their requester type, it's auto populated to Maintenance based on their user role.

@dianamartin will changing an attribute within the "REQUESTER" field cause any scripts to break to AGOL or ODP? I know scripts will break if field names or updated, but I just wanted to make sure before bringing this request to sprint planning!

[dianamartin]

@ChristinaTremel this may break scripts I think. The one the identifies the user automatically when creating the a new work order. We'll have to ask John or one of the devs to confirm.

[ChristinaTremel]

Discussed in Sprint Planning and we don't think it'll break scripts, but build notes includes:

• [x] Add SMD MAINTENANCE PLAN Requester Option
• [x] Update Sign Work Orders that were batch loaded into Knack #11507
• [ ] Check ODP dataset to confirm nothing broke with this Requester Name change.

[dianamartin]

@susannegov coordinate with @ChristinaTremel and me on when you're planning on doing this.

[susannegov]

5/8

Export

• [x] work_order_signs (29145 records)
  • 198 SIGNS AND MARKINGS records
  • In G:\ATD\ATD_GIS\02_ENT_APPLICATIONS\app_Signs_and_Markings\SIGNS\archive called 20230508_work_orders_signs_SIGNS_AND_MARKINGS
• [x] work_order_markings (29145 records)
  • 73 SIGNS AND MARKINGS records
  • In G:\ATD\ATD_GIS\02_ENT_APPLICATIONS\app_Signs_and_Markings\MARKINGS\archive called 20230508_work_orders_markings_SIGNS_AND_MARKINGS
• [x] Add new requester type SIGNS AND MARKINGS - MAINTENANCE PLAN
• [x] Batch update 198 records SIGNS AND MARKINGS
  • [x] 149 work orders updated to SIGNS AND MARKINGS - MAINTENANCE PLAN if created after 01/01/2021 to specify this is planned maintenance
  • [x] 49 work order updated to SIGNS AND MARKINGS - SPECIAL PROJECT if created before 01/01/2021 because these are the trailblazing project
• [x] Delete 198 SIGNS AND MARKINGS records
• [x] Check ODP/AGOL tomorrow to see if it broke

[ChristinaTremel]

Emailed Lauren, Cathy, Ramona, Kenny and Kati:

Hi everyone, We've updated the Requester option from "Signs and Markings" to "Signs and Markings - Maintenance Plan". We used that naming structure so it matches the other requester type "Signs and Markings - Special Projects". We updated the work orders that Susanne batch loaded as well as other work orders related to the maintenance plan to this new naming structure. Let me know if y'all have any questions!

[susannegov]

So I took a look at the Open Data Portal (ODP) and ArcGIS Online (AGOL):

• ODP
  • Roadway Markings Work Orders: The SIGNS AND MARKINGS value did not change to SIGNS AND MARKINGS - MAINTENANCE. However, it was able to run the script with new records today as normal
  • Street Sign Work Orders: The SIGNS AND MARKINGS value did not change to SIGNS AND MARKINGS - MAINTENANCE. However, it was able to run the script with new records today as normal
• AGOL
  • Street Sign Work Orders: The SIGNS AND MARKINGS value did not change to SIGNS AND MARKINGS - MAINTENANCE. However, it was able to run the script with new records today as normal
  • Pavement markings Work Orders: The SIGNS AND MARKINGS value did not change to SIGNS AND MARKINGS - MAINTENANCE. However, it was able to run the script with new records today as normal

I think the REQUESTER field for ODP/AGOL is operating under the same guidelines as the UNIT PRICE column in materials/specifications table in AGOL, where if the UNIT PRICE value changes the old price is still visible in AGOL, whereas in Knack the UNIT PRICE values is changed. Not an issue if filtering by Requester type in Knack app, but might be a problem if using it through ODP/AGOL.

[susannegov]

Emailed Lauren, Cathy, Ramona, Kenny and Kati:

Hi everyone, We've updated the Requester option from "Signs and Markings" to "Signs and Markings - Maintenance Plan". We used that naming structure so it matches the other requester type "Signs and Markings - Special Projects". We updated the work orders that Susanne batch loaded as well as other work orders related to the maintenance plan to this new naming structure. Let me know if y'all have any questions!

@ChristinaTremel is it okay to close this ticket out? The ODP/AGOL values did not update the new REQUESTER (similar to UNIT PRICE) but the script is running new work orders as expected. As long as filtering work orders is done on knack side should not pose an issue

[susannegov]

Actually after talking to @dianamartin in app sync this will require coordination with the Dev team for a fix on ODP/AGOL

[dianamartin]

@ChristinaTremel reminder that we need to talk to Dev team in Dev & Product sync as this isn't appearing on ODP/AGOL

[ChristinaTremel]

@susannegov I was bringing this to the Dev team, but noticed that old work orders were updated with the SIGNS AND MARKINGS - MAINTENANCE PLAN Requester. Found out from John that on the 15th of every month, the work order ODP datasets are completed replaced so I think this actually resolved the issue!

[susannegov]

Re-look at ODP and AGOL:

• [x] Roadway Markings Work Orders: The SIGNS AND MARKINGS - MAINTENANCE and SIGNS AND MARKINGS - SPECIAL PROJECTS are updated
• [x] Street Sign Work Orders: The SIGNS AND MARKINGS value did not change for work orders that are all ON HOLD status to SIGNS AND MARKINGS - MAINTENANCE. However, the replacement of requester types for when the work order is completed will resolve the requester types so it should be fine.

@ChristinaTremel @dianamartin This looks good to close.