One major new feature was deployed yesterday - while the rest of our team has been working on optimizing our predicted end-time calculation within Compass for use in Live Production. Here's what we've been working on the past 4 weeks!
Restricting Compass Access by Work Area
We have added an additional layer of access control for your Operators (or anyone using Compass) by way of Work Area specificity if you choose to apply it. When editing a user's profile within HQ, you now have a Work Area Access filter. By default it's set to ALL, but if you wish to restrict a user to specific work areas only here's how you'd do it.

The user above has been granted access to R&D work area stations only. When they attempt to login at a Compass station outside of this work area, they are greeted with the following warning.

This will have no effect on current users and/or new users if they have not had their work area access filtered. It does, however, give you one more way to secure who gains access to which of your stations.
Other Adjustments:
- We mentioned that our team has been working on optimizing our predicted end time calculations. We found that our servers' CPU was being strained in certain instances when attempting to calculate historical job build times for certain units (particularly those with embedded units). So rather than sending separate queries for a specific historical date range of past jobs, we send one query for all of the jobs requested. This allows our system to work on that singular request for however long it may take instead of bogging down the system with 20+ requests at a time. The result is less database chatter and improved performance overall. Early results show a 20-25% reduction in the time it takes to calculate our predicted end time for any job.
Mark Estep
I've spent nearly 20 years working for varying startups. Being COO of Scout Systems is the most rewarding. Traveling the world (whether for work or with my family) is a true passion.