Hi everyone,
I’m looking for a few beta testers to try out the new AAO Designer and give me honest, constructive feedback.
The AAO Designer is a tool that lets you build and simulate your alarm and dispatch procedures step by step (units, dispatch groups, areas, keywords, simulation, and validation). Before we release this to everyone, I want to make sure it works reliably and is logically sound.
Please note beforehand
Areas aren’t functioning yet because the API doesn’t support it at the moment. This is known and doesn’t need to be reported. Everything related to areas is not part of the testing scope.
What matters to me when testing
It’s important that you test constructively and objectively. Specifically, that means:
Please pay attention to:
- actual errors and bugs (things don’t work, crash, or show wrong values)
- logic errors in the AAO itself (an alert doesn’t make professional sense, wrong units are suggested, sequences are incorrect)
- contradictions between what you enter and what the simulation outputs
- unclear or ambiguous spots where users get stuck
Please don’t focus on:
- personal preferences or matters of taste (colors, terminology, layout, because you’d do it differently)
- how your own dispatch center structured its AAO specifically, as long as it doesn’t violate any general rules
- requests for additional features that go beyond actual testing
In short: I’m not looking for opinions on how the Designer should look, but for feedback on where it doesn’t work correctly or leads to wrong AAO results.
How to give feedback
It’s most helpful if you briefly describe a bug like this:
- what you did (which steps),
- what you expected,
- what happened instead.
Feel free to include a screenshot—that really helps me reproduce the issue.
If you’d like to participate, just reply in this thread or send me a message.
I’m grateful for every helping hand.
Thanks so much in advance.
Pat
