[Feature] Extend work orders for MMC work

[johnclary]

See also https://github.com/cityofaustin/atd-data-tech/issues/5125

How might we...

• increase operational efficiency and quality service delivery?
• increase visibility into our performance metrics?
• provide insight into resource allocation?

Provide Work Order Process for

• Mobility Management Center Staff Lance: I would like to discuss adding the ability to assign SRs & Work Orders to the MMC and/or MMC staff as we begin to consider Corridor Management responsibilities for our operators. Our current practice doesn’t really have us doing that even though the functionality appears to be available within Data Tracker. I’d like to discuss this potential workflow change, our motivations for it within the MMC, and the potential implications for other groups.
• Signal Engineers Tracking of ad-hoc signal retimings and misc engineering work in the Data Tracker, as well as updates to the signal retiming dashboard to incorporate this info.
• Communications Technicians

[johnclary]

@amenity This is a new feature to the data tracker.

[johnclary]

@dianamartin would you add your notes from recent conversation w/ Jonathan?

[dianamartin]

Notes from 9/12 Signal Re-Timing

For FY2019

• Update "Signals Re-Timed" (Corridor Signals Re-Timed)
• Add report widget: Number manually entered for FY 2019 (Individual Signals Re-timed)
  (Completed by mid October and presented on the dashboard)

Data and Performance Hub

Action Items:

• Jonathan will submit some information to remove duplicates/incorrect on the signal retiming pages
• Try the "issues" on the Transportation Management Center page

For FY2020:

• Corridor Signals Re-timed – Work Orders for Signal Engineers (Would not include work orders)
• Corridor Travel Time Reduced
• Individual Signals Re-timed (Non-corridor) – CSR or other signals re-timed (Would not include CSRs)

Performance Metric Retimed 1/3 signals ~ 340 signals

Update Signal Re-Timing Details page Modify Engineer Note field on Data Tracker to say (Public Facing)

Proposed Signal Re-Timing Work Order Signal ID Corridor – Which corridor? Created By – Engineer Created Date: Type of Work

• Re-timing
• Equipment Modification
• Field Check/Evaluation
  • Notes/Comment: Description of work completed
  • Inventory/Materials: controller, communications modules

Process for updating Re-timing

• Provide documentation to Markus and he enters the Re-timing Details (Before/After)
• Get credit for re-timing a corridor, which shows up on the dashboard

[dianamartin]

Talked/Emailed Jonathan

Told him that I talked with John about our approach to this and our suggestion of adding a "Non-Corridor" on the Corridor Re-Timing Management module of Data Tracker cityofaustin/atd-knack-data-tracker#216 and then associating the ad hoc signals to it.

Next Steps:

• [ ] Create new widget on the Signal Timing dashboard "Individual Signals Re-timed (Non-corridor)" to show the new Non-Corridor and their associated signals.

@johnclary So how often does the Signal Timing dashboard update the data? Jonathan's concerned that I had deleted the records he wanted me to in the Data Tracker, but it's not reflective on the dashboard.

[amenity]

@dianamartin - Can you add a link to the workflow diagram you just shared in our call here?

[dianamartin]

@amenity This is an example of a work flow diagram I made when we thought we were going to implement markings into Maximo. I probably need to update these to reflect their current state in Knack. I thought I made them already, but I could have been only in my brain.

ATD_Markings_Future_20170919.pdf

[amenity]

This is awesome, @dianamartin. We can update to reflect Knack stuff and use as a reference for discussions during discovery.

[amenity]

Met on this today; @dianamartin is going to:

• Add high-level next-steps as a comment here
• Modify this epic to include the meetings we've had thus far

[amenity]

During a meeting with Lewis yesterday, he mentioned that the folks they're working with at Toole Design said that Seattle's asset management data is incredible; "all work captured in the field by technicians, updated nightly for everyone in the organization to see" ... Does sound a lot like Data Tracker. ;) It might be worth reaching out to them and learning about their approach, @dianamartin @johnclary.

[dianamartin]

@amenity I found this map, I have a feeling they use CityWorks

[johnclary]

nice find @dianamartin! super impressive. and I think we're making a lot of progress towards this! sloww progress.

@amenity i know some good transportation folks in Seattle. but who has the time?

[johnclary]

Todo:

• Meet with MMC to understand their tracking needs
• Add a "Work Type - MCC" multiple choice field that will be used by MMC to identify the type of work they're doing
• Add a new "MMC" workrgroup option to the work order's Workgroup field
• Revisit the "Work Orders (Non-Technicians)" module and identify any changes needed to accommodate the MMC (or build a separate module for them)

[amenity]

@ChristinaTremel @dianamartin - shall we close this epic?

[dianamartin]

No, we're refactoring Signal Inspectors. We might need to circle back on this.

[ChristinaTremel]

• All of the work requested for the MMC has been completed. We will be working on signal inspector work orders, but those issues will be tracked on #15962