We’ve been going around the houses trying to decide how to explain the Eclipse Scopes and, more importantly, how to do it without boring you to death. We also need to get across how Scopes are different to Permissions, and how they’re different to Department access.
So, you’ve guessed it, Scopes are similar to both Department and Permissions access, but they have more flexibility allowing for data to be throttled at those levels too.
We originally created Scopes so that Contractors can add or upload their data directly into Eclipse and then make use of the tools for cross-checking and visualising inputs, but without seeing the data of other contractors or machines and locations not relevant to them.
This is achieved by allowing access to specific modules, plant and locations and filters all the way through to the reports that they can access. Admin for “satellite” Scopes also share those restrictions.
This separation leads to significantly less errors and helps in cross-checking of data because the data is summarized per shift collectively on the homepage and per operating section.
So, the secret to keeping this from being deathly boring was to keep it short and simple. It definitely is not small and simple.