| Acknowledge | Mark an event as seen and handled. Its status changes from New to Acknowledged. |
| Admin console | The part of ANSCMS where organisation admins manage members, devices, sites, pages, branding and security. |
| ANSMIND | The ANSCENTER app for setting up boxes, cameras and AI tasks, and the name of the camera-events application in ANSCMS. |
| ANSVIS box | A Windows box running ANSVIS. It often sends general event types such as vision.vehicle. |
| App role | A member's role inside one application, for example teacher or security. Pages can be limited to some app roles. |
| Application | A product enabled for an organisation, such as ANSMIND or ANS Campus. Pages, dashboards and reports live inside an application. |
| Box | The AI computer at your site. It runs the AI tasks on the camera streams and pushes events to the cloud. |
| Cloud event push | The box setting (in ANSMIND) that sends the box's events to ANSCMS. |
| Dashboard | A page of live numbers and charts built from widgets. |
| Data page | A page that shows your own data: a list, a board (such as attendance), a record table or a calendar. |
| Data type | A kind of item you keep a list of, such as Student or Class, with its fields. |
| Detection box | The rectangle the AI drew around what it detected, shown on the event's picture. |
| Draft | Unpublished changes to the data model and rules. Users see them only after you publish. |
| Engine box | A Linux box running the ANS Vision engine. It sends specific event types such as lpr.detected. |
| Event | One detection sent by a box: time, camera, type, severity, subject and picture. |
| Event type | The kind of event, written as a key such as lpr.detected (plate) or fire.detected. Types ending in "(general)" in ANSCMS, such as vision.vehicle, are broad categories. |
| Event view | A page that lists the events of the event types you choose. |
| Ingest key | The secret a box uses to send events to one organisation. Shown once when created. |
| Member | A person with access to an organisation. Can be limited to one site. |
| Module | A ready-made package of data types, rules, pages and menu entries, such as School or Plate watchlist. |
| Organisation | Your customer account. Everything in ANSCMS belongs to one organisation. |
| Organisation admin | A member who may open the Admin console for the organisation. |
| Org builder | An organisation admin who may also change the data model and rules. |
| Publish | Make the draft live for everyone, as a new version. |
| Report | A table of events or statistics that you export to CSV, Excel or PDF. |
| Retention | How long events are kept before they are deleted. |
| Rule | An automatic reaction: when something happens, if a condition holds, then do something (mark a record, notify people, raise an alert). |
| Runtime off | A feature is not enabled for your organisation on the server. Contact ANSCENTER. |
| Severity | How serious an event is: Info, Warning or Critical. |
| Site | A place inside the organisation, such as a campus or a building. Each box is placed in one site. |
| Solution template | A ready-made set of pages, dashboards, reports and menu, such as Smart ward or Smart school. |
| Staged rollout | Publishing a change on a few sites first, then promoting or reverting it. |
| Subject | What an event is about, for example the plate number or the person's code. |
| Test on my data | Replaying past days with a draft rule to see what it would do, without changing anything. |
| Version | Every save of a page and every publish of the data model is kept as a version you can go back to. |
| Webhook | An HTTPS address in another system that rules can send data to. |
| Workspace | The organisation, application and site you are working in, shown in the header. |