Uploaded image for project: 'MAEviz'
  1. MAEviz
  2. MAE-340

Analysis - 2.2 issues from annual meeting

XMLWordPrintableJSON

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • 2.2
    • 2.0.annualmeeting
    • None
    • None

      1) When selecting one building to retrofit, it seems to recalculate for all buildings (taking too much computational and real time)

        • Calculate based on the selection and modify the baseline

      2) On retrofit wizard, needs to have a field telling you what building it is, not just the building value.

        • "Can show multiple fields...I don't know which field defines ""what building it is""
      • Data issue not MAEviz UI issue"

      3) Decision support tools could help streamline time to get needed data and allocate resources

        • decision support in 2.1 will streamline the process users went through in annual meeting exercises

      4) We do not know if multiple selections (specific buildings and then classes of buildings) will override the prior selections. It should be possible to retrofit a class of buildings and then individual buildings too, and merge the results without double counting financial resources to do that.
      **retrofit a class of buildings,(ie. C1), and adding or removing additional buildings (ie. Select and/or deselect all C1 and individual structures)

      5)Algorithms for optimal retrofit plans - users provide constraints (budget, etc.) and MAEviz automatically find the optimal retrofit plan. Users can also make modifications from the optimal retrofit plan found by MAEviz.

        • Someone in MAE must define what criteria MAEviz will use for optimization and this can then be added to the decision support system.

      6) Under aggregate to polygon, user should not be allowed to aggregate in inappropriate ways (e.g., median value allowed to sum).
      **This issue ties with metadata

      7) Low retrofit option did not have a cost or seem to have an impact on damage ratio in some cases

        • This probably resulted in cases where the "non retrofit" and the "low" key pointed to the same fragility curve because the structure was at "low" code. We will need a use case in order to determine if this is truly a bug
          ****Bill asked to provide input 3/29/07

      8) When selecting to do the retrofit, provide a check mark box in the wizard that tells program to automatically re-estimate the damage (this time for retrofitted buildings). One only wants to retrofit to test economic impact.

        • workflow issues w.r.t. recalculate. Some type of dependency monitor.

      9) Add context sensitive analysis selection. For example, for bridge damage analysis, only bridge relevant items should be displayed.

              cnavarro Christopher Navarro
              tmclaren Terry McLaren (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: