search

cityofaustin / atd-data-tech

Austin Transportation Data & Technology Services
17 stars 2 forks source link

[Enhancement] AMD Cabinet Assets Refactoring #8032

Open johnclary opened 2 years ago

johnclary commented 2 years ago
amenity commented 2 years ago

@johnclary @dianamartin - who's assigned to this one?

dianamartin commented 2 years ago

@amenity I defer to John, I don't recognize this one.

johnclary commented 2 years ago

my bad, forgot to assign myself. last communication to Brian C below. we're meeting on 1/14 to discuss.

The attached workbook has one row per signal, with the last set of columns (highlighted in blue) being pulled from the related cabinet record.

A cabinet may be listed twice because one cabinet relates to many signals.

This includes signals of all status (turned on, construction etc).

Some of the issues I've identified: Not all signals have a cabinet. Many of these are secondary signals. TODO: if you want to track secondary signals' cabinets (seems like a good idea?) our GIS folks can probably help associate them with the right cabinet. Some secondary signals link to a cabinet that is different from their primary (at a quick glance there are only a handful of these). TODO: review these for accuracy. The Controller IP field on the signals table appears to be the same field as the Controller IP Cabinet field on the cabinet table. They are largely, but not always, identical. TODO: review these for accuracy For reference, I've updated the signal asset map so that the cabinet's are labeled with the signal ID(s) they're connected to.

As it relates to the device status log, we have these IP fields that need to be cleaned up/condensed.

signals - SWITCH_IP signals - CONTROLLER_IP cabinets - Controller IP Cabinet cabinets - Monitor IP cabinets - Switch IP

johnclary commented 2 years ago

I'm waiting for Brian C. to send me a list of cabinet updates to import.

ChristinaTremel commented 9 months ago

Notes from Issue 12/21/2021

Commented by John