Review Overlay Milling Hierarchy for Independent Service Plans for Risk

[rebekkabry]

Background

Pavement has requested the Overlay and Milling hierarchy be removed to allow for independent work order handling within the Pavement Service Plan

Reasons for Requests: Overlay and Milling are dependant upon the status of the other workorder before being able to go out and complete the work. They will like to be able to complete the work, regardless if the Parent has been completed. We need to ensure the Parent does not have any required conditions needed for the Child, which is why currently dependant.

Desired Completion: In preparation for FY25 Service Plan Upload

Stakeholders to Sign Off and Approve Before Any Changes are Made

• Pavement Leadership
• Data Owners (CTE)
• Reza and Team
• DM and Lead Techs (to understand how the change impacts their day to day)

Concerns to Investigate

• Hierarchy Relationship Dependencies
  • Ops Handling
  • Reporting
  • Data Back End for Historically Records
• Work Order and Investigation Prompts Losts?

• Scoping Plan

• work with Reza and team to map out current/proposed/risks states
• present to requesters

CURRENT

PROPOSED

[rebekkabry]

Notes from 7/17/24

Attendees: Ron, Reza, Rebekka, Binaya, Ambarish

TPW Roles: Reza - planning Andre - ops/ specifications and status updates

Currently vs Proposed by Stakeholders

Concern: lost visibility of complete project completion (MILL and OVER)

Proposed

Considers:

• [ ] Should we just change the name of the children workorders?
• [ ] How will they track what has been milled?

  Concerns:

• [ ] Adds extra steps for work order handlers. (at 3)

Dependiences:

Milling is first. Pavement is last. Is there other work in between.

Want:

MIll and Over separate, not as the dependent child of the work order.

✔️ ACTION ITEMS

• [x] schedule meeting so Andre can attend and speak to concerns.

[rebekkabry]

Notes 7/18/24

Attendees:

• [x] go through checklist topics above

[rebekkabry]

Goal: split the team into 2: milling and paving team

Current: the way we have the two crews we cant

Milling can do more than paving, currenting cant completel milling becuae have to wait for overlay.

Can you not change the status the parent without the child being complete? we can 4qa the child, but we cant get credit for the overall work order until the pavig is done. doesnt show up on completed lane miles report.

could we run a report on the milling children? as an option. ---the concern: one report that would show them stand alone.

paving and milling children of the parent work order = not want they wont.

if we can report indentpendly doesnt need to change.

[rebekkabry]

Builder Notes

@GaneshKamarapu - can we discuss the efforts on this? and how much it may align with this request #14546

• [ ] Service Plans:

  SP24-SLCT1 
  SP24-SLCT2

• [ ] Workgroup

  Overlay

• [ ] Separate by Work Order Children

  Milling: -MILL
  Pavement: -OVL

• [ ] Status

  any 4

• [ ] Metrics and Parimeters

• by week; (daily and previous 7 days possible) able to run daily but see the count of the last 7 days

• Count of completed WO by (MILL, OVL, PROJECT WO)

• Count of miles by (MILL, OVL, PROJECT WO)

[rebekkabry]

@GaneshKamarapu we can add to the upoming August 7th sprint.

[rebekkabry]

[rebekkabry]

BUILD followup Pg 1: Total Graph - with data (current phase) Pg 2: Mill ONLY Graph with data Pg 3: OVRLAY ONLY Graph with data * may be best to use the WorkGroup as the Work Orders do not specify the OVL Children Work Orders

[rebekkabry]

@GaneshKamarapu Lets put this on hold per Ron pending Andre's return and rescoping.

[rebekkabry]

9/12/24

• worked with team to create a milling portlet in PAVEMENT start center.
• team will follow up on further report or dashboard needs.
• https://github.com/cityofaustin/atd-data-tech/issues/19011