| Ignition |
8.3.8. The module loads on 8.3.4 and later; 8.3.8 is the verified platform. Ignition 8.1 is not supported. |
| Modules |
Perspective for the views pack and the Ask panel. Optional: Reporting for the PDF Alarm Health report; the Artek MQTT suite (Artek-MQTT-Common and Artek-MQTT-Pub) for MQTT output. Without either, the rest of Artekis runs unchanged. |
| Database |
One database per gateway (a redundant pair counts as one) on SQL Server, MariaDB / MySQL or PostgreSQL, reachable through a gateway database connection. The Artekis tables (Appendix A) are applied by your DBA. Verified on SQL Server 2022, MariaDB, MySQL 8.4 and PostgreSQL 17. |
| Model provider |
An Anthropic API key, or an OpenAI-compatible endpoint (a hosted service or a local server such as Ollama). The key is stored in an Ignition Secret Provider and referenced by name — Artekis never stores or shows it. The provider must support tool calling for Ask; Anthropic does, and an OpenAI-compatible endpoint is checked once with a tiny call. |
| Licence |
An Artekis licence key activated on the gateway through Ignition's own licensing, or the platform's 2-hour trial while you evaluate. Free on Maker Edition under Maker's non-commercial terms (section 5). |
| Alarm journal |
For Alarm Health and Incident, an alarm journal profile that holds the alarms you want analysed. Anomaly Watch reads it too, for the fires of detectors you have imported (section 8.5); without one, Artekis checks those detectors itself. |
| Tag history |
For Anomaly Watch, the screened tags must keep history, at least baselineDays (default 30) of it before the first useful run. |
| Email profile |
For the email digest, a gateway email profile. |
| Gateway memory |
Model answers and evidence bundles are small. The in-memory document index costs about 5.7 MB of heap per 100 documents of 20 KB. |