Product · n7kel Atlas
n7kel Atlas — all of a site’s data in one picture
When a company has dozens of sites, hundreds of cameras, checkouts and turnstiles, and several departments, the main problem is not a lack of data but the fact that it is scattered across different systems. n7kel Atlas is n7kel’s own platform for working with very large data sets: it brings together events from all sources, finds links between people, vehicles, events, places and times, and helps divide the work between teams and shifts.
Tasks
New2
- Reconcile Till 1 refunds for the shiftAnalyst 1POS
- Request entry video 10:00–10:20Shift BCameras
In progress1
- Links of 123 ABC 00 to eventsAnalyst 2Vehicles
Done1
- Case report for managementShift leadReport
Activity log
- 10:31Analyst 2 opened the entry video
- 10:29Shift lead assigned a task
- 10:22Analyst 1 exported the refund list
Capabilities
What n7kel Atlas does
Unified event store
Camera events, POS transactions, access control entries, conversation transcripts, data from accounting systems and external databases — in a single data model.
Search
By person, license plate, checkout, site, period or conversation text. Results link to the source events and evidence.
Links
Who was on site together, which events recur for the same cashier across different shifts, which vehicle arrived before an incident.
Timeline
Events in a case on a common timeline and on the site plan: what happened, where and in what order.
Cases and tasks
An investigation is set up as a case. Tasks in a case are distributed between teams, shifts and employees, each with an owner and a deadline.
Roles and log
Everyone sees only their own sites and cases. Every action — search, view, export — is recorded in the log.
How it works
From scattered systems to shared work
Connecting sources
n7kel products connect right away; the client’s other systems connect via API, databases, files or message buses.
A single model
People, vehicles, events, places and times are mapped to common entities, so the same person or license plate does not live in five systems under different records.
Analysis
Search, a link graph, timelines, recurring schemes. n7kel AI suggests related events; the analyst makes the decision.
Cases and tasks
The analyst opens a case, attaches events and distributes tasks: check a checkout, request a recording, interview a shift.
Progress tracking
Task statuses, deadlines, decision history and a final case report.
Scenarios
What it is used for
| Task | What n7kel Atlas does |
|---|---|
| A theft scheme in a fuel station or retail network | Links checkout events, transactions and shifts across the entire network, reveals the recurring scheme, opens a case and distributes checks by region |
| An incident on site | Puts access control entries, camera events, vehicle arrivals and conversations at the desk on a single timeline |
| A wanted-list match | Shows the history of the vehicle’s or person’s appearances at the sites and passes a task to the duty shift — under an agreement with government authorities |
| Discipline audit | Brings together procedure violations by site and unit and shows where changes are needed |
| Several departments working together | Security, occupational safety and operations work in the same data, each with its own permissions |
Data security
Runs within your environment
- n7kel Atlas does not recognize people itself: identity information enters it only from modules enabled on a lawful basis — employees with their written consent, customers and patients with their consent, wanted-list checks under an agreement with government authorities; all other visitors remain anonymous;
- data is used only for the purposes for which it was obtained; the client is the personal data controller; the final legal assessment is made by the client’s lawyer;
- n7kel Atlas is installed on the client’s equipment; a fully autonomous installation with no external connections is available;
- no foreign cloud services or external APIs are used, and no data is transferred abroad;
- access rights by role, site and case; every action is recorded in the log;
- data from external and government databases is connected only if the client has the legal right and an agreement;
- any restrictions you need are put in place at your request; all data stays with the client, is confidential and is not shared with third parties, except where expressly provided for by the agreement and the law.
Integration
Data sources
- n7kel products: Vakhta, Fuel Station Control, Antifraud, Voice, Flow, Access;
- POS systems, ERP and 1C, HR systems;
- access control, security monitoring consoles, video surveillance systems from other manufacturers;
- databases, file exchange, message buses, legacy systems;
- external and government databases — under an agreement;
- export to the client’s BI, service desk and reporting.
Pilot
How we begin
Tasks and sources
We define which questions n7kel Atlas should answer and which systems it needs to include.
Connection
We connect 2–3 key sources for a limited set of sites.
Teamwork
Analysts and the security department work on real cases in the pilot environment.
Scaling
We connect the remaining sites and systems and configure roles and reports.
Questions
Do we need other n7kel products to use n7kel Atlas?
No. n7kel Atlas works with any of the client’s data sources. With n7kel products it connects faster, because they already share the same event model.
How much data can the platform handle?
The platform is designed for large data sets; the hardware configuration is selected during the site survey based on the volume of sources and the retention period.
Does n7kel Atlas make decisions on its own?
No. The platform finds and shows links; a person draws the conclusions and makes the decisions. Every analyst action is recorded in the log.
Let’s bring your data together
Tell us which systems you have and which tasks need to be divided between teams, and we will propose a pilot scope.
The interfaces in the illustrations are schematic mockups with sample data.