The detail your controls, IT and security people will ask about. The administrator’s manual has the rest.
Playbooks, the model of your plant, how a finding is made and where the results go.
The checks, the baselines per running state and product, and how a confirmed anomaly becomes an alarm you import.
The six kinds of alarm problem, the thresholds, the proposed changes and the KPIs.
The prerequisites, what an Artek engineer does with your team, and what you have afterwards.
What it reads, what leaves the gateway, permissions, spend caps and the record of every call.
The gateway’s Status page shows eight setup steps judged from the gateway’s real state: database tables, a connection and secret, the license or trial, the module, configuration, the views pack, playbooks and the optional incident trigger. In the four hours included, an Artek engineer installs it with your gateway admin, drafts the model for your first area with your controls engineer, sets the schedules, runs the first reports with you and sits with your supervisors in Ask. Most teams use them across two or three remote sessions in the first two weeks.
You pay your model provider directly, with daily caps per provider, per run and per user. On our acceptance run, against a 125,000-event alarm journal and a 19,900-tag provider:
A gateway producing 30 to 50 alarm candidates a day runs about $15 to $24 a month in model calls; a small gateway a few dollars. A model on your own network costs nothing per call.
A member of our team reads every message and replies, usually the same day.
Contact us →