System connections
Use the right record from the system that owns it.
Connect employee, machine and site information to the safety workflow that needs it. First agree the source and purpose of the data, then verify the proposed connection with representative records and clear responsibilities.
Existing platform relationships
Company, workplace and employee records support training, documents and permit workflows inside the platform. These relationships do not automatically connect an external HR or ERP application. External identifiers, fields and update rules need to be mapped.
Eye and site devices
Eye provides device pairing, camera configuration, connection-status and observation-transfer workflows. Use requires the appropriate licence and installed site device. Camera connection methods, image quality, coverage and network access are assessed before confirming the proposed setup.
HR, ERP and other devices
HR discovery covers employee identifiers, workplace assignments and status updates. ERP or maintenance discovery covers asset identity, location and the relevant records. Other IoT connections require review of the protocol, units, timestamps, update frequency and failure handling. There is no blanket promise of a ready-made connector or compatibility with every version.
Acceptance means more than a successful connection
Compare transferred fields with the source record and check that they belong to the correct workplace. Try missing fields, repeat submissions, conflicting updates and interruptions, then agree who handles errors and how to recover. Document the production scope and any custom development or third-party licences before rollout.
What should we share first?
The product or device name, version, intended process, approximate record volume and public documentation are sufficient for an initial discussion. Keep passwords, API keys, camera access details and real employee files out of the public contact form.