Creating and managing sites - Amazon Monitron

Creating and managing sites

After setting up a project, you can organize it into sites to make it easier to manage. A site is a collection of assets, gateways, and sensors that share a purpose. Organizing a project into sites is helpful if your project has a large pool of assets, gateways, and sensors. You can use sites to control access and permissions to specific parts of that pool.

You can create up to 50 sites within a project, and add up to 100 assets and 200 gateways to each site.

Organizing a Project into Sites

You can organize a project into sites based on your business needs. For example, you can organize a project in one of the following ways:

  • No sites at all. Everything is contained in a project, without any sites. This option is best for projects with a few assets and users that you can easily keep track of because it provides the greatest simplicity. .

  • Sites based on geography. Group resources and users by locale, such as by city, building, or areas within a building. For example, you might set up a site for the equipment in a factory test lab.

  • Sites based on function. Group resources and users by functionality, either by machine functionality or by how they're used in your factory. For example, you might set up a site for all of the conveyor belts involved in moving an item from one side of the factory to the other.

  • Sites based on organization. Sites represent a specific organizational structure in the company or factory. For example, you might want a single site that includes resources and users assigned to the shipping department.

Controlling Access to Projects and Sites

To give a user access to all of the resources in a project, including those in all of the project's sites, you add the user to the project. To give a user access to only the resources in a site, add the user to the site. Similarly, to make an asset or sensor available to all of the users who have access to an entire project, add it to the project. To make an asset or sensor available only to a specific site, add it to the only that site. Gateways are always accessible to anyone or any sensor in the project.

For example: Olga is an admin user added to the project. As a project-level admin user, she can manage users and resources anywhere within the project, including those within sites A, B, and C. Sam is an admin user added to Site B. As a site-level admin user, he can manage users and resources within Site B but can't see or manage those within sites A and C. Sensors within Site B can use any gateway within the project.

Similarly, if Ed is a project-level technician, he can monitor any sensor in the project. However, Tom, who is a site-level technician for Site C, can see and monitor only sensors within that site.