CapabilitiesSecurity, data control and authorised actions
Security, data control and authorised actions
Define who can see plant information, where it may be processed and which actions a user or service can perform. Agree these boundaries with plant IT, OT and enterprise-system owners before activating an integration.
Product documentation · Updated 15 November 2026
- Who uses it
- Plant IT and OT administrators, security owners and system owners
#Separate the permissions
Identify who may read machine data, inspect maintenance records, update mappings, propose an ERP change, approve it and execute it. Scope access by organisation, plant and task. In a multi-plant deployment, make the list of shared objects and fields explicit, including any restrictions on downstream use.
#Document the AI data path
The customer controls its plant servers and source data. GRAYLOCK is designed to retrieve approved evidence from those sources and use external frontier-model services selected by OSWAR teck. No retention of customer data by OSWAR teck or its model providers is a design and contractual requirement. Verify provider terms, settings, logging and the permitted data path for the actual deployment.
#Retain the right operational evidence
Agree where the customer keeps action acknowledgements, access reviews and maintenance history. Specify who can examine an audit record and which fields may appear in it. The plant’s required operational history and an AI provider’s prompt-retention policy address different records and must be documented separately.
#Outcome and verification
- What the team gets
- A site-specific access matrix, approved data-flow description, retention agreement and evidence of an authorised action.
- How to verify it
- Test a permitted read, a denied cross-site read and an attempted write by a read-only user. Confirm that the customer can trace a successful action without exposing restricted content.