Appendix E

Appendix E: Information Needs of SDOT Functions

As SDOT TRAFFIC MANAGERS AND TRAFFIC CONTROL PLANNERS, we need …

  1. …near-term (next day and day after) notice of scheduled road closures or road work on arterials
  2. …advance notice (30 minutes to one hour) of emergency road maintenance work on arterials
  3. …real-time information on pedestrians, cyclist and vehicle volumes and speeds on arterials
  4. …historical and predicted data on volumes and speeds on arterials
  5. …historical and predicted data on high-crash and near-miss locations on arterials
  6. …real-time information on sudden volume spikes or unexpected congestion on non-arterials
  7. …real-time information on the status of locations, routes and schedules of high-capacity transit (buses and trains)
  8. …historic speed and reliability data on high-capacity transit (buses and trains)
  9. …real-time information on re-routes
  10. …reports and real-time information on incidents and emergencies on arterials and non-arterials
  11. …near-term (next day and day after) predicted routes for freight deliveries (commercial and residential)
  12. …to be able to trust (verified and validated) the information and the sources of the information above
  13. …to be able to differentiate the above information into data about arterials and non-arterials
  14. …a way to inform users of the status of incidents and road closures (real-time and future)
  15. …a way to inform decision makers and city leaders on current state of the system, particularly of emergencies or unexpected congestion
  16. …information about permitted road closures, including schedule and impact
  17. …information about submitted requests for permits for road closures, including schedule and impact
  18. …information about traffic control plans (TCPs) for events and road closures
  19. …to know future plans for streets and corridors
  20. …all the above information in open standard, interoperable, and usable data formats that don’t tie us down to any single software service or platform

As SDOT MAINTENANCE MANAGERS, we need …

  1. …a warehouse inventory system so we can track in real-time the status of all our supplies, equipment, and materials and to geolocate all our fixed and non-fixed assets
  2. …to create work orders, with exact locations geolocated, and send them out digitally to work crews
  3. …to get automatically geolocated asset serial numbers attached to work orders
  4. …the ability to close a work order, with exact locations geolocated, from the site upon the completion of the job (this includes updating the asset inventory upon job completion)
  5. …to send out geolocated information automatically on current and future planned maintenance work (including urban forestry work)
  6. …to send out geolocated information automatically on sidewalk and road closures for emergency maintenance work (including urban forestry work)
  7. …to get accurate and verified information on the location and condition of assets and repair needs, including trees and sidewalks (and sidewalk elements)
  8. …to receive geolocated customer complaints and requests (tied to physical asset inventories)
  9. …to send back responses and status updates to customer complaints and requests
  10. …to get real-time information on pedestrians, cyclist and vehicle volumes and speeds and speeds in areas where repair and maintenance work is scheduled
  11. …to get information about current and future permitted road closures, including schedule and impact
  12. …to receive information on prioritization of maintenance work/projects
  13. …to receive and send out notifications on emergency and incident response and status
  14. …to report in real-time the completion of maintenance work and resumption of traffic flow or opening of sidewalk
  15. …to send/record time-stamped, geolocated information on the work completed (what was done to which asset, where)
  16. …to get annual (or even monthly) pedestrian volume counts along all (or most) sidewalks, to help inform the prioritization of sidewalk maintenance where pedestrian volumes are higher
  17. …to be able to issue a citation from the field, with the ability to attach photos and have the document geolocated, for violation of street tree ordinance or permit requirements
  18. …all the above information in open standard, interoperable, geolocated, and usable data formats that don’t tie us down to any single software service or platform

As SDOT CURB AND PARKING MANAGERS, we need …

  1. …to send current curb, load zone and parking information to operators and the traveling public
  2. …to send out new curb, parking and load zone rates, rules and schedules, automatically and geolocated
  3. …to receive real-time location and use data from mobility service operators (e.g., TNCs)
  4. …to send out geolocated information on fees and charges, with schedules and rates
  5. …to receive information on parking or load zone violations
  6. …to receive customer inquiries, complaints or reports
  7. …to receive aggregated data on use of curb, parking and load zones
  8. …to send updates regarding our on-street assets like pay stations and signs
  9. …all the above information in open standard, interoperable, and usable data formats that don’t tie us down to any single software service or platform

As SDOT TRANSPORTATION PLANNERS AND MOBILITY PROGRAM MANAGERS, we need …

  1. …aggregated, anonymized, and validated historical performance data on all SDOT and other government transportation assets (roads, bridges, bike lanes, etc.) and should include curb uses, public life, pedestrian counts, etc.
  2. …the predicted usage growth rates for all SDOT and other government transportation assets
  3. …the predicted growth rates and conditions of existing and new SDOT and other government transportation assets based on funding trends and current conditions
  4. …current and predicted development patterns, including building and demographic data
  5. …aggregated, anonymized, and validated historical performance data from all mobility service operators (Sound Transit, KC Metro, bike-share, TNCs, etc.)
  6. …predicted growth rates and use of all mobility service operators by geographic area
  7. …reports on equity outcomes and current conditions for key SDOT and other government transportation assets
  8. …reports on carbon generated (historic and current) for all SDOT and other government transportation assets
  9. …reports on carbon generated (historic and current) for mobility service operators
  10. …infrastructure and investment plans from other government transportation agencies (Sound Transit, KC Metro, WSDOT, etc.)
  11. …post-project completion performance data for all SDOT and other government transportation assets[4]
  12. …to publish and disseminate to the public draft and final plans
  13. …to receive questions and comments from public and stakeholders on plans

As SDOT PROJECT AND CONSTRUCTION MANAGERS, we need …

  1. …to receive validated current-state and historical performance data on SDOT assets (roads, bridges, bike lanes, curb uses, public life, pedestrian counts, etc.)
  2. …to automatically input project schedules and impacts to publicly accessible map based system (such as dotMaps)  -this data should integrate with our other information systems
  3. …to publish draft and final plans for each project
  4. …to receive questions and comments on draft and final plans
  5. …to notify other SDOT divisions of project schedules, timing and impacts
  6. …to submit proposed TCPs (mapped and geolocated)
  7. …to receive approval of proposed TCPs (mapped and geolocated)
  8. …to receive information on TCPs and re-routes
  9. …to receive schedules and locations of planned road closures and other events that will affect construction
  10. …to send out real-time or near real-time (one-hour delay) notifications on the status of construction projects, including traffic impacts
  11. …to receive short-term notifications of maintenance work
  12. …to notify the public and adjacent property owners in real-time of project schedules, road closures, re-routes and other impacts
  13. …to release above information in multiple languages
  14. …to receive and respond to questions, reports and complaints
  15. …to report job completion to relevant project managers and update construction coordination and asset inventory systems
  16. …to report project delivery status, accomplishments and performance data
  17. …to share network files and access across other city departments
  18. …to share software/system licensing across city departments
  19. …to receive information monthly on actual expenditures for projects
  20. …to be able to stay up to date with project management software technology
  21. …to be able to submit work orders with a tracking system for work on capital projects that is to be performed by city crews
  22. …to be able to prepare a single update report instead of reporting updates multiple times through multiple channels
  23. …to have our project management systems build in the conditions and reminders about the specifics of each grant used on a project
  24. …to report project status to financial managers and grant sources (if relevant)

As SDOT STREET USE MANAGERS, we need …

  1. …to send out permitting rules and fee schedules
  2. …to receive permit requests and plans
  3. Including predicted transportation impacts (road and sidewalk closures, etc.)
  4. …to send out real-time status of permit requests to applicants
  5. …to determine conflicts in permits, activities, and events automatically
  6. …to send out approved/permitted requests and plans
  7. Including approved TCPs and re-routes
  8. …to send out geolocated and mapped information about requests
  9. Including approved TCPs and re-routes
  10. …to send out geolocated and mapped information about permitted activity
  11. …to receive questions, reports and complaints
  12. …information on the status of the response to questions, reports and complaints
  13. …to report and validate violations (mapped and geolocated) and to identify code and permit violations in the field in real-time
  14. …to notify the public of schedules, road closures, and re-routes
  15. …to update the system of record automatically
  16. …to update asset infrastructure when changes are made by private development[5]
  17. …to receive and validate payments
  18. …to report remotely on inspections of permitted work
  19. …to route plans electronically for review by secondary reviewers inside and outside the city firewall
  20. …to understand the allowed uses of the right of way in real-time, including temporary closures (TCPs). This should include the locations of all permitted encroachments (and ideally unpermitted encroachments as well).
  21. …to know the location of all infrastructure buried in the right of way and above it; including information about that infrastructure (voltage of power lines in conduits, etc.)
  22. …to provide estimated timeframes for review
  23. …to send out inspection reports electronically
  24. …to record and manage time spent at any one job site
  25. …to update the future inspection schedule based on inspection results and inform contractors of upcoming inspections
  26. …to track final inspections and notify affected partners of asset improvements and changes

As SDOT ASSET MANAGERS, we need…

  1. …an updated and validated list of assets in the right of way[6]
  2. …a process to update the inventory with assets that are in the right of way but not in the database
  3. …a process to make sure all new assets are included correctly, with location data, in the asset inventory database
  4. …a process or systems to allow us to update the asset inventory from the field, with geolocation
  5. …a regular audit of assets to make sure our inventory is trustworthy

Footnotes:

[4] This may initially start with equipment but should grow to include assessing embodied carbon in construction and capital projects. Carbon cost should always be presented in tandem with dollar cost to incentivize lower carbon or zero carbon alternatives in process and materials.

[5] To protect existing SDOT assets and features during ROW construction, to represent the city’s best interest in row jurisdictional permitting authority

[6] And accurate attributes required for decision making (condition when needed, category, ownership, dates, etc.)

Need More Information?

This is a draft plan. It was developed by Benjamin de la Pena, Mary Alyce Eugene, Alex Hagenah, and Sam Marshall along with their colleagues from across the Seattle Department of Transportation (SDOT).

If you have questions about this plan, please send us email via draft_tiip@seattle.gov.

If you have questions about SDOT, please visit our website at www.seattle.gov/transporation.

Designed by Story 2 Designs

Privacy Policy