How to Structure OTserver Sites for Plants and Production Lines
Site model
Use the smallest site that has a clear operational owner and network boundary. A practical tree is organization → plant → area → production line → cell, but OTserver does not hard-code those names or depth. Stop at the production line or cell when that is the smallest safe scanner scope.
Keep each scanner configuration’s target list aligned with one site, and use that site’s document ID for direct upload. One scanner host may run several named configurations sequentially, but each needs a unique output path and destination site. The scanner does not create duplicate assets when an IP changes because it correlates assets by normalized MAC address.
Procedure
- Create the plant and its child areas under Sites.
- Add production lines or cells where ownership, network scope, or risk changes.
- Give each scanner configuration only the target networks for its assigned site.
- Import a baseline and check that assets appear beneath the intended site.
- Add asset classes and manufacturer/model rules after the baseline is visible.
Verify the result
Open a representative asset and confirm its site, observations, topology, and audit history. Move a test user through the hierarchy and verify that descendant access follows the intended boundary.