Introducing AI without documents leaving the network
An industrial company with high protection requirements wants its employees to use AI in their daily work. The condition set by information security for operation: no confidential document leaves the company network, and every use is traceable. This is the way there, in four steps.
Four steps to operation
1. Test days
Selected employees work for five days in our environment, only with documents released for the test that may leave the organisation. Confidential material only comes in with the pilot, inside the company network. The test days end with a report with measured values.
2. Pilot
The platform runs on hardware in the company's network, connected to the existing user directory. A small group of key users from a few departments starts.
3. Rules and training
Data classes, the operations manual and training are in place before the user group grows.
4. Production
The expansion runs on dedicated production hardware, for the entire intended user group.
Frequently asked questions about the rollout
- Do confidential documents leave the organisation during the test days?
- No. During the test days employees only work with documents released for the test that may leave the organisation. Confidential material only comes in with the pilot, once the platform runs inside the company network.
- When does the platform run inside the company network?
- From the pilot onwards. OdyControl then runs on hardware in the company's network and is connected to the existing user directory.
- What has to be in place before more employees join?
- Data classes, the operations manual and training. Only then does the user group grow beyond the key users.
What would the way look like for you?
Order and scope depend on your documents, your network and your user group. In an initial call we clarify what your test days would start with.
