Local Deployment Options for KodeGEM Intelligence
KodeGEM Intelligence runs alongside the Tool Control Software as a separate local software layer. It can preserve the existing control-software deployment when compatible interfaces are available.
Deploy on the existing Tool PC, a computer beside the tool, or customer-approved dedicated local hardware. No cloud service is required for core operation.
- On-prem
- No cloud required
- Compatible interfaces can preserve existing software
- Windows equipment-software scope
- Customer-controlled local data
Choose your deployment model
On the Tool PC
Run KodeGEM on an existing Tool Control PC when the available resources and interfaces meet project requirements.
Computer Beside the Tool
Use a separate local computer beside the equipment when software separation or dedicated resources are preferred.
Dedicated Local Hardware
Use customer-approved dedicated hardware, including a Pi 5 where appropriate, when the project needs a compact local node.
Project-specific combinations
A project can combine local deployment locations when the equipment architecture, available resources, network boundaries, and customer security controls support that design.
GEMObserver architecture
GEMObserver can receive configured SECS/GEM activity and provide GEM with approved equipment context, including alarms, events, and equipment state.
A deployment may require an adapter, configuration change, network tap, GEM interface, log export, or API. Resource placement and traffic behavior are validated for the specific equipment environment.
