Default No-go type automation

(from Mo H)

Use Case

CS mappers use Tycho to configure maps.

To create additional No-Go’s after map upload the mapper will use the create tab to create new No-Go’s.

Problem

Problem: No-Go’s created after initial upload are created by default as Enterable-No-Go, forgetting to change the type of the No-go will result in bots going to undesirable areas of the map.

Impact: This create a deviation from the customer requirements, and might lead to safety issues if the type is not changed, and also add additional re-work effort on the mapper

Solution

Solution: Create all No-go’s as Non-Enterable by default.

Impact:

Most No-Go’s are created to restrict areas from bot navigation, having that by default eliminate a potential deviation and will only demand the use to change the type when it’s needed.

Reduce re-work effort to change the type of the No-go and deviation correction