The usual questions, answered once and for all.

Yes. IRIS can be deployed fully on site and work with no internet connection. Video, models, searches and rules can all run inside the customer's own infrastructure.

Not necessarily. IRIS is designed to use the video infrastructure you already have, where the integration and available streams allow it.

No. Your organisation sets the rules and the limits. IRIS automates their repetitive application and brings people the situations that need human judgement.

An NVMS is a Neural Video Management System: a video management system that also understands what is happening in the scene. It interprets objects, zones, timings and context, applies the organisation's rules and turns video into metrics and evidence.

It depends on the site and how many cameras are integrated, so we do not quote a generic timeline. The usual path is to start with a few cameras and one or two rules, check it detects what you expect, and grow from there.

It depends on the site. IRIS can work as a complete video management system or sit alongside the one you already have, and that is decided after looking at your camera network, not before. We would rather go camera by camera and tell you what can be done today and what cannot, than promise it fits everything.

The price depends on three things: how many cameras come in, how many detections you want on each one, and where the video is processed. We do not publish a fixed price list, because a twelve-camera site and a six-hundred-camera site have nothing in common. Tell us your case and we give you a real figure, not a range.

Yes, and it is one of the reasons it gets installed. Classic motion detection goes off with rain, a branch or a cat; IRIS looks at the scene and works out what is there, where it is and how long it has been there before it alerts. We do not promise an alert will never fire needlessly again, because that does not exist: we promise the noise stops reaching the operator, and that when an alert does arrive, it is worth looking at.

No. Your organisation defines the rules and the limits, and IRIS takes care of applying them over and over across every camera. Situations that call for human judgement reach a person together with the footage, the context and the history, so the decision is made with everything in view.

Not necessarily. IRIS is designed to make use of existing video infrastructure where the integration and the available streams allow it. A survey beforehand goes camera by camera: which ones work as they are, which are worth re-aiming, and which do not give the image quality the detection you want requires.

IRIS differs from video analytics in what it does after detecting. Analytics spots an isolated fact: there is a person, a line was crossed, twelve vehicles went past. IRIS links that fact to the zone, the elapsed time and the context, checks the rule your organisation set, and carries out what should happen next. Detection is the beginning, not the end.

No, and this is one of the most confused points. Looking is three different things. The first FINDS: it knows there is a person there and at exactly which point of the image; it is fast and always gives the same result on the same image, which is why it is the only one you can count with and have a number come out the same twice. The second NAMES: it tells a van from a car, a hard hat from a cap; it works with a list, and what is not on the list it does not see. The third UNDERSTANDS: it reads the whole scene and how things relate — not «a person» and «a car», but «a person on the ground beside a car stopped in the middle of the junction» —, it needs no list and answers a sentence written in your own words, but it is not the one you count with. IRIS carries all three as standard, not as separate add-ons: on the same camera you usually need them at once. That is why we say asking is for searching and counting is for measuring, and that they are not done the same way.

Yes. A part made only here, a movement done only in this trade, a defect that only shows up with this material: none of that is on any list, and it is not going to be. A model of your own is trained on images from your cameras and on your cases, and it becomes one more detection inside IRIS, written into a rule like all the others. And that model is yours: it is trained on your images and on the judgement of your people, so it remains your property. It is not reused with another customer, it is not folded into a product sold to your competition, and you do not have to remain a customer to keep using it. What it takes to train it: images of that happening — real ones, not staged — and someone on your team who can say which is right and which is not. If the thing you want to detect cannot be seen in the image, no model will pull it out.

IRIS includes capabilities you would expect from a VMS — taking in cameras, recording, playback and export — but what it offers goes beyond that. IRIS understands what happens in the image, applies the organisation's rules, turns video into metrics and lets you investigate without reviewing hours of footage.

Not necessarily. Depending on the project, IRIS can act as the complete platform or live alongside the existing video infrastructure, using the available streams and integrations. The sensible thing is to review it case by case: which cameras, which recording and which systems can be reused.

NVMS stands for Neural Video Management System: a video management system that also understands what is happening inside the images. The difference from a VMS is at the centre of the model: a VMS revolves around the screen and the operator; an NVMS revolves around the decision.

Yes. A detection is worth little if it ends up on a screen nobody looks at, so usually something is needed around it: a screen built for how your team works, a report in your format and with your names, a calculation that only makes sense in your operation. That gets built. What we will not tell you is that it all fits in the same budget: some things are solved in an afternoon and others are a project, and which is which gets said at the start, while there is still time to change the plan, not after signing.

Yes, and that is the norm: almost nobody starts from scratch. The alert can land where your team already works, the number can end up in the dashboard you already read, and what IRIS decides can lean on something your system already knows. What we will not tell you is that we fit with everything. What gets integrated and how is decided by looking at your actual system, not before: some connections take an afternoon and others depend on whether the other side lets you in, and that sometimes depends on neither of us. It is checked at the start, with your system in front of us, and if something is not going to be possible, that is said then.

No. Rules are described in ordinary sentences — what to watch, where, for how long and what to do — and IRIS shows how it has read each part before switching it on. The technical team is still needed for commissioning and integrations, but not for changing a threshold.

No. Some situations a given camera cannot resolve because of its position, image quality or lighting, and some details are too small or too far away for any camera at that framing. The way to find out is not to argue about it: it is to test the description on that camera's real footage and look at the result before counting on it.

Yes. Besides defining rules for the future, you can describe something that already happened — ‘white van parked for more than ten minutes at dock 4’ — and IRIS returns the candidates with their camera, time and image. Stop looking for the minute; look for what happened.

It costs nothing. IRIS does not charge per query: there is no meter on phrasings, searches or trials. Write a rule, test it against video from that camera, change it and test it again as many times as you need; one trial and a million trials cost the same. That is deliberate, because a sentence gets sharpened by trying it, and a system that charges per attempt ends up with rules written in one go and written badly.

Yes, IRIS can work without an internet connection, and the nuance matters: it is not that it survives a line outage, it is that in the on-site mode it does not use the line to work at all. The servers sit in your building, video comes in over your network, and the models run on your hardware without calling any outside service. You can unplug the cable and the system keeps detecting, alerting, measuring and recording exactly the same.

The video lives where you decide, and only the people you authorise can reach it. In the on-site mode it lives on the disks in your building and no third party sees it. In our data centre it lives on our own dedicated infrastructure, located where we agree, and the contract sets who may get in, with what permissions and how long each thing is kept. In both modes communications are encrypted and access is logged.

Yes, you can start with one mode and switch to the other later on. It is the same system in both places: what changes is where the analysis runs, not what it can do, nor the rules you drew over your cameras, nor how your operators work. The whole organisation does not have to move at once either: each site can have its own mode and they are all seen from the same place. What does change is who buys the hardware and how it is billed, and that gets discussed before signing, not after.

If the link goes down, analysis in our data centre stops until the line comes back. We say it plainly because it is the real limit of that mode: with no link, nothing arrives to be analysed at the other end, and during that time you will not get alerts. Your cameras keep recording wherever they do today, and as soon as the line is restored the analysis resumes. If there is a spot where that gap is not acceptable — a control room, a treatment plant, a prison — that spot goes on-site. The two modes can be mixed in the same organisation.

No. IRIS is not billed by usage: there is no meter on queries, searches, alerts or open cameras. One query and a million queries cost the same. That is deliberate, because a system that charges per question ends up barely used: the operator hesitates before searching and the tool sits idle. What does change the price is the size of the installation and the deployment mode, and that is agreed before signing, not after.

No. IRIS is also used to measure the operation: headcounts, waiting times, zone occupancy, queues and flows of people or vehicles. In many sites that is the most common use, because not everything that matters is an alarm: sometimes what matters is a number. That is not asked for in words: you draw a line or an area on the image, because a line has to be drawn. And people counting is type-approved by the Spanish Metrology Centre through NeuralPax: what is approved is that measurement, counting people, and nothing else.

No. It is the same platform in every environment; what changes is the configuration: which objects matter, which zones are watched and which rules apply. An organisation with very different environments works with one system, one history and one trained team.

Yes, as long as the camera has power and a route to reach the IRIS server. The analysis runs inside the site itself, so on a remote perimeter or in a closed network IRIS still understands the scene even with no internet connection.

No. IRIS works with the cameras that are already installed, and the operator drives everything from the browser, with no program to install on each desk. What changes is not the hardware out on the poles: it is that the layout is built in two clicks, saved, and comes back identical tomorrow, and that the room's wall is driven from the desk.

Up to 64 tiles per screen, with twenty grid shapes or free placement by hand. Separately there is a limit, configurable per server, on how many of those tiles carry live video at once, so neither the workstation nor the network is choked. Tiles beyond that limit do not go black: they show a refreshing still image, and the tile itself says this is a system decision and not a fault.

Viewing, moving and configuring are separate permissions, and on top of that each camera can have its own access list, person by person. Privacy-masked areas cannot be uncovered from a view: it takes a written reason, a limited duration and, where the organisation requires it, a supervisor's approval. And yes, there is a record: every viewing, every camera movement, every unmasking and every access to a published wall is logged with who, when, from where and by which route.

Because the tile says so. IRIS tells three reasons apart and names them: the limit on simultaneous live video has been reached — a decision of the system, not a fault — the camera is down, or the stream has stalled. In the first case the tile switches to a refreshing still image and stays useful; in the other two it reconnects by itself and says so while it does. An operator can also insist that their tiles never fall back to a still image. And if a tile is black because you have no access to that camera, it says that too: a black square with no explanation is the worst possible answer in a control room.

A screen with a browser — a television, a monitor or a video cube — and its connection to the server over the same secure port as everything else. Nothing to install on that screen and no configuration file to edit: the shape of the wall, the content of each tile, the bezel compensation and even the scrolling text bar are all set from the web interface. The screen opens the published link without typing a password, and that link carries a PIN, an expiry date and a list of allowed addresses. What you do need is the one thing no vendor sells: deciding what gets seen. That part is the control room's work, and everything else exists so that it only has to be done once.

IRIS ships with 41 ready-made behaviours — intrusion, line crossing, dwell time, loitering, abandoned or removed object, occupancy, queues, crowding with density, bay taken, wrong way, speed, distance between people, movement between zones — on top of a catalogue of 94 object classes grouped into 12 families. If what you need is none of them, a fine filter compares each object against eleven fields — confidence, tracking age, speed, direction, size, class stability — with eight comparators and conditions grouped by ‘and’ and ‘or’.

Not to get started. Every class in the catalogue carries its real average height — 1.70 m for a person, 1.50 m for a car — and that alone yields metres per second and kilometres per hour with nothing to set up. For a real measurement on the ground, you mark four points on the image and state their true distances: from then on, distances, paths and speeds are in metres. IRIS always tells measured speed from estimated speed, and a rule can demand that only the measured one counts; the estimated one falls short, which is exactly why it is labelled for what it is.

That is the first thing you tackle. You can mark areas where nothing is detected at all — a road in the background, a poster with photographs of people — require that an object has been tracked for a while before anything fires, set a double threshold so the alert does not flicker at the edge of a zone, restrict the behaviour to a schedule, and add waiting time, a cooldown and a cap on alerts per minute. Before anything is published you see on the live image what the rule really produces, including the discarded objects and the reason each was discarded.

With less light there is less to detect, and the system says so instead of covering it up. Every camera carries an image-quality reading that works as a gate: if it is out of focus, dirty or fogged, the rules that depend on it are not run blind. There is also a detection health score per camera, built on six signals, which does not stop at the diagnosis and says what to do: check the optics, check the focus, check the night infrared. The limit, stated up front: at night, in infrared, the image loses colour, so the colour reading is flagged as unreliable rather than claiming the van was white. And schedules understand sunrise and sunset, so watching at night keeps meaning the same thing in June and in December.

The identity is held for a few seconds, and when it cannot be, that is said. When something hides an object — a pillar, another vehicle, an awning — the system does not extrapolate blindly: it damps the speed the object was carrying and loosens the criterion for picking it up again, in proportion to how long it has been out of sight. Each object also keeps a small history of its classes, so a car that flickers to lorry in the distance does not make the rule flicker, and the tracking parameters are tuned per class, because a lorry and a person do not move alike. The limit, stated up front: if the occlusion lasts too long the track dies, that object's life summary is closed, and what reappears afterwards is a new object. Recognising it again by its appearance is a different thing, and it still does not know who anyone is.

Yes — that is what the fifteen filters are for. You narrow it down by date range, cameras, object type, up to four colours, a specific part of the frame and one of nine behaviours, and they all combine. You can also just write the sentence in plain language and the system turns it into those filters, showing what it understood first. And if the range is still long, the summary skips the dead time and turns eight hours into a few minutes of review.

Because they check it themselves. The exported package includes a fingerprint for each clip, one for the whole package, a digital signature and a checker that opens in any browser. That checker works offline: it calls no server, ours or anyone else’s. If anything has been changed — a frame, a byte, the manifest — the check fails and says so. And before being handed over, the package verifies itself; if it does not pass its own check, it is not delivered.

It is not deleted. A locked stretch sits outside recycling, and the disk rule cannot override it. If the only old material left is locked, the system stops, writes it into the log in plain words and raises a warning, instead of sacrificing protected material to gain space. The check runs three times before anything is deleted; if any one of the three cannot be carried out, nothing is deleted — it is never assumed there were no locks when the truth is that nobody could look. The screen also shows how much disk is tied up by locks and how many of those have no expiry date.

Retention is decided by the customer, camera by camera, and it overrides the server default; it can be left with no limit so nothing is deleted for being old. The real ceiling is not the software, it is the disk: that is why the screen does not just show the configured retention but the days actually on disk right now, and warns when there are fewer because the disk fills up first. Recording spreads across as many servers and sites as needed, so growing means adding disk where it is short. And the decision is not taken at our end: the material lives inside the customer’s installation.

They cannot, and the attempt is written down. Locked material sits outside automatic deletion, and deleting by hand needs its own permission plus having that camera assigned. Lifting a lock requires the reinforced permission — the same one that governs erasure requests — and a written reason; the lock record does not disappear, it is marked as released with who, when and why, and the lock history is permanent. And every deletion, every export and every release lands in the audit log with the state before and after, chained so that an altered or removed entry shows up.

The product includes face recognition, it ships switched off, and it is not offered in the European Union. Where the law allows it, turning it on means reading nine legal warnings and declaring a legal basis, a purpose and a retention period: without those three it does not run, and withdrawing them stops it there and then, with nothing to restart. Each site decides; it never arrives switched on, and who switched it on and when is on record. In the zones this site shows, IRIS identifies nobody, because on those cameras the function is not switched on. Almost every real search does without it: type, colour, route, dwell time, zone and hour are enough.

Yes, and it is the normal way to work. IRIS keeps a record of what each object looked like — type, colour, size, route, speed, dwell time and zone — and that is enough to find it again on another camera on another day without ever naming it. When it proposes that two sightings are the same object, it says so as a confidence level, not as an identity: the screen warns that this is a possible match by appearance, that it is no proof of identity and that it needs human review. A person confirms or rejects each proposal, and that decision is stored with a name and a time.

Searching requires permission to view recordings, and on top of that each user only finds objects on the cameras they may see: a camera without permission does not break the search, it simply contributes nothing, and the screen says so. Every search records who ran it, when, over which cameras and with what criteria. Sensitive areas can be covered with privacy masks, and uncovering one requires a stated reason and, if the organisation demands it, a second supervisor’s approval. How long each kind of data is kept is set separately. And it all happens inside the customer’s own site: the models and the maps are our own and work with no internet, so not one image goes out to a third party. And everything — interface, video, thumbnails and queries — travels over a single port, 443: not one more port to open on the firewall.

Then the appearance trail breaks, and that has to be said plainly. A person’s fingerprint rests on colour, shape and build: change the clothes and the fingerprint changes, so IRIS stops proposing that person on later cameras. What it does not do is invent a match: it says nobody reaches the threshold, and states the threshold it used. What still stands is the route up to the change — where the person was last seen and at what time — a search by other criteria in that zone and that time span, and the vehicle if there is one. This is exactly why the route is built from sightings a person confirms, and not from an automatic chain nobody ever looked at.

Each site sets it, separately for people, vehicles, faces and number plates, anywhere from zero to 3,650 days. Zero does not mean delete: it means keep indefinitely, and the screen flags it in red so nobody picks it by accident. Deletion is carried out by a nightly sweep, and if that sweep is not armed the screen says so instead of assuming the deadline is being met; you can also see how many live fingerprints exist per modality and how many are past their deadline. Querying them requires permission to view recordings, and it only reaches the cameras that user is allowed to see. Changing retention requires its own permission, and every search and every change is recorded with who and when.

Both are true, and the camera is the difference. Plate reading is a feature switched on camera by camera, and it ships switched off. Where it is not switched on — a school playground, a prison wing, a construction site perimeter — IRIS sees “a vehicle” and that is the end of it: it does not read the number, does not store it and does not compare it with anything. That is why those pages say it does not read plates: on those cameras it is literal. Where it is needed — a car park barrier, the gate of a lorry yard — it is switched on, because that is exactly what the customer came to buy. Who switched it on, on which cameras and when stays in the audit trail, so the answer to “where are plates read on this site?” can always be looked up, and it is always a short list somebody can check. And switching it on is not only a technical decision: a number plate is personal data, so it is switched on where it is permitted and for a stated purpose, and what is kept is kept accordingly — with a retention period, with who may see it, and with a record of who has looked.

No. IRIS reads the number on the plate and compares it with the lists the customer has loaded, and that is where it ends. There is no vehicle registry behind it: it queries no official database, does not know the owner's name and cannot find it out. It does not read make or model either. What it does know is what the camera saw — the vehicle type and the colour — and when it did not see them properly it says so, instead of filling the gap with a guess. A plate only means something if the customer has put it on a list; and every list states what it is for, on what legal basis, and how many days its data is kept — from one day to ten years — with deletion when the term runs out.

IRIS decides, records and keeps count of who is inside. What physically moves the barrier is a sequence the customer builds from the web, step by step, and which can be tested before anything real happens: “what would you do with this plate, at this gate, at this hour?” — and the screen answers through the very same path the live engine uses. Opening by hand is a different matter with a permission of its own, separate from all the rest: you tick a box, write a reason, and it stays in your name. If the sequence fails halfway, it says at which step it failed and that something may have been left open, instead of calling an unconfirmed opening a success. And the credentials that open the barrier never leave the server: they do not reach the browser, because on many controllers that address is the key.

With mud, a bad angle or poor light it usually manages, because one pass leaves dozens of readings and only one of them has to come out well. With a plate that simply is not legible, no: there is no reading, and the system does not invent one. What it does is count the discard with its reason, so you can see how many are being lost on that camera. If it is losing one in three, software will not fix that: moving the post, changing the angle or adding light will — and we say so before selling, not after. At an access point, a plate that cannot be read comes out as “not on any list”, is logged with its image, and the barrier does not open by itself: a person opens it by hand, with a written reason, in their own name. And note this is a different thing altogether: noticing that a vehicle is driving with no legible plate requires no reading at all, and that is done on cameras where plate reading is switched off.

It happens, and it is planned for. When matching against a list there are three criteria: exact, known confusions only — the factory setting — and approximate. The middle one allows a difference only in characters that genuinely get confused, and only in the pairs that are switched on; not in any character, which is exactly what makes a loose comparison end up opening the barrier for the car next door. For a barrier you can demand the exact criterion, zero characters of difference, and if that access point ends up looser than the general rule, the screen says so in red before saving. Then there are two details that only show up once somebody has actually built one of these: the alert silence and the who-is-inside state are keyed to the plate on the list, not the plate as read, so a wobbly letter neither slips past its own silence nor counts as a second entry. And when two variants of a plate have shared the same track, that is no longer a resemblance: it is proof it was the same car, and the screen marks it as such.

It climbs. Every alert enters a ladder with its own waiting times: if the first one expires and nobody has answered, the next rung is alerted, and so on upwards. Answering means taking it, validating it, closing it or commenting on it; that stops the climb, even if it does not solve the case. If a rota has been left with nobody on call, the alert jumps to the next rung instead of falling silent. And when rungs and repeats run out, a last-resort destination is alerted. It never ends in silence.

Three things. Repeats from the same camera fold into a single row with a counter, without deleting any of them: the detail is still stored and the count always adds up. The queue filters by 27 combinable criteria, and each operator saves their own view and shares it with the team. And a panel measures how many alerts each person receives per hour and points at the camera and the rule producing them, so they can be tuned rather than switched off. On top of that, there is a record of who muted what.

Yes. Every incident keeps its whole timeline: who opened it, who looked at it, what changed, what was written and when it was closed. The log only accepts additions, is cryptographically chained and can be verified on demand; if anything had been touched, it names the exact entry where the chain breaks. The case file downloads as a signed package with the fingerprint of every file and a page that checks it offline, with nothing to install. And whatever existed before chaining was switched on is declared as not verifiable, rather than passed off as verified.

An escalation that fails silently is worse than no escalation at all, so it is measured and shown. A panel says whether it is running, running but with alerts not getting through, or stopped, and gives the reason in plain words: switched off, never run, the last pass errored, it has not run for so many minutes. It also flags what nobody looks at until it is too late: that there is no active channel to go out through, or how many people on the team have no way of receiving an alert. And you can see, over the last 24 hours, how many escalations ended up with no recipient and how many times the last resort had to be used. On top of that, a fresh install starts disarmed on purpose: it only simulates and writes down the plan, and someone has to arm it server by server. A deployment must not start calling people on its own.

They see each other. The record says, by name, who else is looking at it right now; and if you are alone, it says that too. Taking it means claiming ownership, and that gesture is stamped with its time: it is also what stops the escalation, even though it does not solve anything yet. States cannot jump from any one to any other: the server checks every change and rejects the ones that do not belong, saying which state it tried to go from and to, so two people cannot leave the same incident in two different places. And everything both of them did stays on the same timeline: who opened it, who looked at it, who changed it and what each of them wrote.

No. You drag blocks onto a canvas and join them with cables, the way you would sketch a diagram on a whiteboard. If two pieces do not fit, the editor rejects the link there and then and names both, so the mistake does not surface once the site is live. And if you do not even want to draw, there are 23 ready-made recipes: pick one, fill in four fields over the camera live image, and it works on day one. For the control room operator there is also a mode with six plain-language questions and no canvas at all.

That is the real fear of anyone who automates something, which is why there are four brakes before you ever get there. Before publishing, the simulator runs the flow against the camera latest real image and tells you whether it would have fired and what it would have done, without sending a single alert. Once published, you can leave it muted: the flow runs and computes but executes no action, so you can validate it for days without bothering anyone. If something looks wrong, pause it for an hour, four hours, a day, or until any date you choose, and it comes back by itself. And a flow that fails several times in a row switches itself off and leaves the reason in writing.

Yes. An automation is defined once and applied to one camera, a group, a whole server, or the entire site. Exclusions are written with their reason: every camera on the server except the changing room and the server room is a single statement, not a list somebody has to maintain. Each place can carry its own thresholds and its own schedule without duplicating the flow. And one camera takes several configurations at the same time: one in production counting for real, another in validation with the new thresholds, and a third in design while it is being drawn, without touching the one that is running.

It fails where it fails, and exactly where is written down. Besides its normal outputs, every block has a failure output, so the error is routed somewhere useful — alert maintenance, log it, retry — instead of being lost on the way. The history records the stage where it broke, whether that was the camera, the model, the condition or the action, along with the attempt number, so the fault is located without opening a single video. Two principles are worth stating plainly. If an alert cannot be sent because the channel is off or misconfigured, it is not lost in silence: it is recorded as deferred, with the reason. And if a value cannot be read, none is invented: it says why it is missing, and it never shows a zero as if it were a measurement. What we do not promise is undoing what already happened: if the incident was created before the failure, the incident exists. What we do promise is that you know how far it got and why it stopped there.

Only whoever holds write permission. Reading and writing are separate rights, so an operator can open the flow, understand all of it, and change nothing. Above that, an administrator decides which blocks each role may use: a blocked block still shows in grey, so people know it exists and can ask for it, and the automations already published that use it keep running, because blocking breaks nothing. Who blocked what and when is recorded, and it is lifted in one click. Every change leaves a trail too: each published version is kept, renamed and restored as a draft, and the comparator shows on the drawing what was added, removed and changed between two publications. Nor can you delete an automation that starts another one down the chain: you unhook it first.

No. The artificial intelligence that answers is our own and runs on the server in your own installation, and so do the speech transcription, the reading aloud and the maps. Not one image, not one frame and not one sentence of the conversation travels to an outside provider, because there is no call to a third party at any point along the way. It works with the internet cable unplugged, and that is a design requirement, not a happy accident. The data stays in the customer's own database, with its time and its origin.

This one reaches the controls. An ordinary chat answers with what it knows; the IRIS assistant has 95 tools wired into the system, and uses them to go and fetch the answer: it looks through a camera, opens a recording, aggregates statistics, draws the map, puts the report together. And if the person asking has the right, it acts on the system: it opens or closes a case, aims a moving camera, sends an alert. Every one of those actions is logged with the name of whoever triggered it, and the ones that touch the installation ask for an explicit confirmation first.

No, and the difference matters. Asking is how you search and how you describe a situation: that part is done by talking, and the assistant is good at it. Counting is how you measure, and measuring means knowing exactly where the line runs and in which direction. A line cannot be described in a sentence: it has to be drawn on the image. That is why counting is set up by drawing, and why the number is repeatable and can still be audited a year later.

It says so, and that is the part that took the most work. If there is no recording at the moment you asked for, it says so instead of showing you something else. If it runs out of room to think or to write, it says so and suggests moving up a level, rather than handing over a truncated answer without warning. At the higher levels it lists what cannot be determined from the evidence in front of it and what would be needed to know, instead of filling the gap with a guess. Errors are explained with their actual cause — a missing permission, an expired session — rather than failing in silence. And every answer arrives with the tools it used and what they returned, so it can be checked instead of believed. The decision still belongs to the person: this is a tool for whoever is on duty, not a replacement for them.

No, and that is not a promise: it is how it is built. The assistant only sees the tools the person asking is entitled to use, so the same chat offers an operator and an administrator different powers. Ten permissions govern the chat itself — using it, sharing a conversation, creating or moderating shared threads, reading other people's, configuring the service, managing behaviours and managing tools — and on top of that each tool can demand one of its own. The ones that modify data are flagged as such and do not run without that permission, and publishing an automation asks for an explicit confirmation. Everything is logged: who asked, with what role at that moment, with what arguments, what came back, how long it took and whether it succeeded; denied access attempts are logged too. Conversations are private by default, and shared threads only admit people from the same organisation.

No. There is no meter: not on questions, not on messages, not on words. You can have a two-line conversation or spend the whole shift asking, and it costs the same. We say it because it changes how the thing gets used: when every message has a price on it, the operator holds back, asks less than they need and ends up going back to the old system. Here there is nothing to ration.

Yes. The mapping is installed on the customer's server, country by country, and stays there: drawing the map, searching an address and turning a coordinate into a postal address are all resolved against that data. The interface says so on screen — «local map, no internet» — so the operator knows what they are working with. No query leaves the site, so nobody outside can infer which area is being watched.

Yes. PDF, TIFF, JPG and PNG are accepted. In the wizard you draw a rectangle around the parts of the document that matter, and a project PDF with twenty storeys becomes twenty separate plans in a single pass. Folders are organised however each site prefers — country, site, building, storey or anything else — and every plan keeps its real date, which is almost never the day it was uploaded.

No, and it is better said before the demo than during it. The IRIS heat map is drawn over the camera image, not over the mapping. Density on the ground is obtained today by aggregating over drawn zones, site perimeters and measurement spaces, not as a continuous heat layer on top of the map. It is a real gap, and it is stated here because an integrator will check it in five minutes.

It takes up whatever the installed countries take up, because they are installed and removed one by one: the whole world is never installed, and almost nobody needs it. Of the 185 in the catalogue, a reference installation works with 65. On the administration screen each country shows its size in storage and its install date, so sizing is not a brochure estimate: it is a figure you see before and after. Updating is a data load launched by the administrator, with a job queue stating the type, the status, the progress, the current step and the error if something fails. There is no automatic trickle from the internet, because there is no internet: the map changes when someone in the building decides it should, and every dataset keeps its version and its load date so you always know which edition you are working with.

It happens constantly and it blocks nothing. The floor plan does not depend on the street data: you upload the project plan, anchor it to the map with one click, and the building exists in the system before it exists in any mapping. A site perimeter accepts five origins — taken from the cartographic reference, drawn by hand, imported from the customer's own file, worked out by wrapping the cameras, or flagged as an orphaned reference when the outline it came from is no longer in the current dataset — and that last label exists precisely so the system says so instead of keeping quiet. Reverse lookup still answers even when the doorway does not exist: it gives the nearest one that does, with its distance in metres. And if the point falls outside the area with terrain data, it says there is no data there rather than inventing an altitude.

No. The room lives inside IRIS and opens from the camera wall or from the map. There is nothing else to install or to buy, and there is no need to take video out of the site in order to talk about it: the camera comes into the call, live, and everyone sees the same thing while they talk.

Yes. The host generates a link with a QR code that is scanned with a phone. The link expires, has a number of uses, can be voided at once and defines what whoever opens it may do: speak, see the cameras on the wall, write in the chat, or only watch. Every use is logged.

Yes. The room connection, the audio, the video of the people and the video of the cameras all travel over port 443 inside the customer's own network. There is no third-party server anywhere along the way, so a plant cut off from the outside holds the meeting just like any other site.

No. You join from the browser you are already using, and someone coming from outside joins by scanning a code with their phone. Before going in there is a lobby: you type your name, you see how you will look on camera and you decide whether to switch the camera and the microphone on. Browser permissions are asked for there, once, and are not asked again inside. And if the room records, the notice appears in that same lobby and has to be accepted to go through.

They join with a link, without an account, and the host decides how it is protected: open to anyone holding it, restricted to people with a session in the system, or guarded by a PIN. The host also decides how long it lasts — a few hours, until a set date, or with no limit — how many times it can be used and what its holder may do. The link also fixes the language it opens in, so a contractor or an assessor reads it in their own without configuring anything. And it is voided the moment it is no longer needed.

One: 443. The interface, live video, recordings, maps, artificial intelligence, conferencing and the programming interface all travel over it, encrypted. The system listens on fourteen ports in total, but the other thirteen are reachable only inside the machine and never cross the network. For the network team that is thirteen exceptions nobody has to open, justify or maintain, and a single check when something goes wrong.

The site keeps running. Each location captures its cameras, detects, applies its rules, records and drives its relays locally; only events and measurements travel to the centre, never frames. An outage leaves the centre without a live view of that site, but it stops neither the surveillance nor the recording, and when the link returns the site publishes everything it stored. That is why bandwidth between sites is sized by events, and why video only crosses the network when somebody asks for it.

The product states more than one hundred thousand servers and more than five million cameras, but what lets you check it are the eight published limits, each with the unit it is shared out by: three are solved by adding machines and five are a hard wall. For example, sixty-four cameras fit per capture process, so five thousand cameras are seventy-nine processes spread over as many machines as needed. The calculator built into the product does that arithmetic from twelve questions, says which resource runs out first, and declares a sizing unfeasible when it crosses a limit that cannot be shared out.

You add a machine and nothing gets redone. You generate a registration code from the central interface, install the service on the new machine and give it that code: the machine enrols itself, with its own identity, and shows up in the fleet. Then you declare what kinds of work it can take and tag cameras with them; until it declares at least one it receives no work, and the interface says so out loud instead of leaving it silent. Routing adjusts by itself and only the cameras that change machine actually move: the whole installation is not reshuffled. What does have to be recalculated is the sizing, if the growth crosses one of the five limits that do not share out, and the calculator says so before anything is bought.

Every server publishes its version, its build identifier and its start time, so version drift across the fleet is visible on screen instead of being discovered the day something breaks. Updating goes machine by machine, not as a general blackout: while one site updates, the others keep capturing, detecting and recording locally, because none of them needs another to work. And there are no configuration files to reconcile server by server: everything lives in the system and is edited from the web, so an update does not drag a trail of local tweaks behind it. If a service is missing something after an update, it does not half-start: it waits with the port closed and writes down exactly what is missing. What we will not promise is a schedule: the calendar of a distributed installation is set by the customer and their maintenance window, not by us.

No, and no piece of software can be certified on your behalf: it is the organisation running the system that gets certified, with its own processes, staff and premises. What IRIS does is arrive designed to help you meet those frameworks with the groundwork already done: the 79 controls of the Spanish national security framework at its high level and the 93 of annex A of ISO 27001, each with its status, its evidence and its review date, cross-referenced so the same task is not done twice. We say it that way instead of showing you a badge: the difference shows up in the first audit. The one third-party approval we do hold is for people counting, granted by the Spanish Centre for Metrology.

No. The audit log only accepts additions, and that rule is not enforced by the program but by the data store itself: any attempt to change or delete an entry by hand is refused, whatever permissions the person holds. The only thing that deletes is the retention policy the organisation has declared, and that purge is logged too, with the policy applied, how many entries went and who triggered it. On top of that, each entry carries the fingerprint of the previous one: if somebody reached underneath and touched the data, the chain would break, and the verification screen would name the entry and the date it happened.

Yes, and that is the normal case. Access is granted per camera, per site — with everything below it or without — or per investigation, always with an expiry date; the screen warns on its own about grants running out in the next seven days. On top of that you can add a time window: outside it the person gets a plain message and does not get in. Revoking requires a reason, and the grant keeps who gave it, when, why, who took it away and for what reason. That is how a temporary access closes instead of staying open forever because nobody remembered.

The account is deactivated, and that is reversible in case they come back. Their open sessions are revoked at once: credentials already in circulation stop working without waiting to expire, so nobody stays inside until some record runs out. The grants they held over sites or cameras are revoked with a mandatory reason, and the access keys their programs used are cut off, keeping who removed them. What does not leave with the person is their trail: the log still shows what they did while they were there. And if they also exercise their right to erasure, the deletion is handled as a request, with a grace period before it becomes final, and anonymisation replaces the personal data inside the entries, leaving the chain intact and counting how many were anonymised: the log goes on proving what happened without keeping who it was.

With three things you can hand over. The first is the integrity check: it walks the whole chain and answers intact, or points at the exact entry and date where it breaks. The second is the signed export — spreadsheet, interchange file or report — which carries the signature inside the file itself, so whoever receives it checks for themselves that nothing was touched, without trusting us or you. The third are the anchors and the period seals, which fix the state of the log on a given date so it can be checked against years later. And it comes with a warning we put in writing on the screen itself: entries written before chaining was switched on are declared as such, with how many there are and why they cannot be verified. We would rather say it ourselves than have the expert witness find it.

No, you do not have to replace the cameras you already have on the street. IRIS connects to the feed of the IP cameras that are already installed and analyses it: what changes is not the sensor, it is what gets understood from the picture. During the project we check camera by camera whether the framing and quality are good enough for what you want to detect at that spot, and we tell you plainly which ones fall short. Replacing a camera is the exception, not the starting point.

IRIS analyses at once every camera your installation has, including the thousands across an entire municipality. This demo shows twenty-three because twenty-three fit on a screen, not because that is a ceiling. Real capacity is set by the hardware behind it, not by the software, and it is sized during the project according to how many cameras there are and what each one is analysing.

The video leaves or stays inside depending on the deployment you choose, and there are two of them. In the on-site mode it does not leave: the servers sit in your building, the video comes in over your network, is analysed in there, and the system does not need internet to work. In the other one it is processed in our data centre — which is our cloud, not somebody else's — and then it does leave, encrypted and under the terms set in the contract. Most organisations mix the two: sensitive sites stay in, the rest goes out.

No, IRIS does not identify people and does not recognise faces. It detects objects, behaviours and situations: a car parked on the pavement, a fall, a crowd building up, rubbish left outside the bin. It puts no name to anyone and compares no face against any database. Counting by time slot is aggregated and anonymous: it says how many people passed through an area, never who they were. A counted person is a one: nothing else of them is kept.

You stop the control room ignoring alerts by tuning the rules with your operators, street by street, over the first few weeks. Let us start with the awkward part: yes, the system gets it wrong sometimes. Every detection system does, and anyone who says otherwise has never installed one. That is why a rule is never a single condition: it combines what is seen, where it is seen and how long it has been there. Those three values are tuned with you until what reaches the screen is what your team wants to receive. An alert nobody acts on is a badly configured alert, and that can be fixed.

How long it takes depends on the size of the installation, and we are not going to give you a date we cannot yet control. The work has three clear phases: connecting the cameras that already exist, drawing on each image the zones and rules that matter, and tuning those rules against what actually happens on the street. The first detections show up early; the fine tuning takes longer. Specific dates go in the proposal, once we know how many cameras there are and what you want to detect on each one.

No, IRIS does not replace your control room or your guards: it changes what they look at. Today one person sits in front of dozens of screens and cannot watch them all at once. With IRIS they stop watching everything and watch what matters, when it matters. The decision stays theirs: IRIS opens the camera, shows what it saw and waits. Who decides what to do is a person, always.

Yes, you can use IRIS if you already have a VMS recording: it lives alongside it instead of replacing it. IRIS is an NVMS, that is, the layer you are missing today: understanding what happens in front of the cameras and applying your rules. You can carry on recording and managing video where you do it now. What gets integrated, and how, is decided by looking at your actual system, not by promising up front that we fit with everything.

You can, but compliance does not depend on the software alone: it also depends on how you deploy it and what you decide to process, and that is signed off by your organisation, not by us. What we can tell you is that the processing is configurable piece by piece: what is kept, for how long, who can access it and from where. And that our way of working is certified for information security and for privacy by an external auditing body. That paper is not signed by a salesperson: it is signed by an auditor, and you can ask us for it before you sign anything.

The cost is worked out from three things: how many cameras are analysed, which deployment mode you choose, and whether the hardware is yours or ours. There is no single price list that fits everyone, because analysing twenty cameras in a park does not cost the same as two thousand across a whole municipality. Tell us how many cameras you have and what you want to detect, and we will give you a figure. The number is +34 902 02 70 91.

Yes, IRIS works with the cameras you already have out on the road. It connects to the feed of the IP cameras already mounted on gantries, poles and columns and analyses it as it arrives: what changes is not the kit on the pole, it is what gets understood from the picture. During the project we check camera by camera whether the framing and the reach are enough for what you want to detect on that stretch — a hard shoulder fifty metres away is not the same as a lane at the back of the frame — and we tell you plainly which ones fall short. Replacing a camera is the exception, not the starting point.

IRIS works at night and in the rain, with one caveat we would rather say before signing: heavy rain, thick fog and glare cut down what any camera can see, and what cannot be seen cannot be detected. That is why IRIS also detects the drop in visibility itself: when a stretch stops being clear, the control room knows and can warn drivers, lower the speed limit or send a patrol. At night it works with the lighting the road already has and with what headlights give it; on unlit stretches we check point by point what can be detected and what cannot.

IRIS flags an incident the moment the rule you defined is met, with nobody having to phone in. That is the real change: today the clock starts when a driver calls 112 or when someone in the control room happens to land on that camera. With IRIS it starts when the scene happens in front of the lens. We will not give you a number of seconds, because it depends on your network, your cameras and the hardware behind them; what we will tell you is that finding out stops depending on somebody watching the right screen at the right moment.

IRIS does not replace an officially approved traffic count, but it counts what a few days of counting cannot: every day, at every hour, on every camera. A one-off count gives you a snapshot of one week; a camera with IRIS gives you the whole year, split by vehicle type — car, lorry, bus, motorcycle — and without closing a lane to install anything. If you need a figure with legal metrological standing for vehicles, that is a different matter and we are not going to claim we provide it: our approval from the Spanish Metrology Centre covers the counting of people. For deciding where the surface needs work or where another lane is needed, continuous data is usually worth more than a few days' snapshot.

Yes, IRIS detects a vehicle stopped on the hard shoulder, and also what usually comes next. The rule is not just «there is a car»: it is a vehicle stopped inside the area you marked as hard shoulder, for longer than the time you set. And if somebody gets out and walks along the shoulder or onto the carriageway, that is a separate detection and it can raise the level of the alert. A breakdown is an incident; a breakdown with a person outside the car is an emergency, and the system tells the two apart.

Yes, IRIS checks that variable message signs are working, with one limit we would rather state plainly. IRIS reads what is on the sign, so it spots that it is off, that it has dead LEDs or that the message has stopped being readable: it sees that from the camera, without depending on anybody. What it cannot know on its own is whether the sign is showing the wrong message, because that means comparing what is displayed with what was ordered, and that requires the system sending the orders to be connected. IRIS can also send orders out to the signs and to whatever systems are connected: what gets connected is reviewed during the project, before signing, and we tell you what fits and what does not.

The video leaves or stays inside depending on the option you choose, and there are exactly two. In the on-site option it does not leave: the servers are in your own facilities, the video comes in over your network, it is analysed there and the system does not need the internet to work. In the other one it is processed in our data centre, which is our own cloud and not a third party's. In both, communications are encrypted and the terms are set out in the contract. It is worth deciding early, because it drives how the network and the servers are sized.

No, IRIS does not identify number plates and does not identify people. It detects objects, behaviours and situations: a stopped vehicle, a person walking on the carriageway, an object in a lane, material fallen from a slope, a closed lane. It does not read plates, it does not compare faces against any database and it does not put a name to anybody. When it counts vehicles it counts them by type — car, lorry, bus, motorcycle — and the result is an aggregate number, never a list of who went past.

False alarms exist, and anyone who tells you otherwise has never put a detection system on an open road. Long shadows at dawn, oncoming headlights, a bag blowing across a lane: all of that looks like something. That is why a rule is never a single condition, but what is seen, where it is seen and how long it has been there. Those three values get tuned with your operators over the first few weeks, stretch by stretch, until what reaches the control room is what the control room wants to get. An alert the night shift learns to ignore is a badly tuned alert, and that can be fixed.

The cost is worked out from how many cameras are analysed, what is detected on each one, which deployment option you choose and whether the hardware is yours or we supply it. There is no single price list, because analysing the cameras of one stretch does not cost the same as analysing a whole route with its junctions, tunnels and service areas. Tell us how many cameras you have and what you want to detect on each, and we will give you a number. The phone number is +34 902 02 70 91.

Yes, IRIS works with the cameras you already have in the station. It connects to the feed of the IP cameras on platforms, in the concourse, in corridors, at the gatelines and at the entrances, and analyses it as it arrives: what changes is not the camera on the ceiling, it is what gets understood from the picture. During the project we check camera by camera whether the framing is enough for what you want to detect at that spot — a camera looking along the platform is not the same as one looking across it — and we tell you plainly which ones fall short. Replacing a camera is the exception, not the starting point.

No, IRIS does not identify passengers. It detects objects, behaviours and situations: a person down on the track, a person on the ground, a platform filling up, an open gate, a machine that is off, a stopped escalator. It does not recognise faces, it does not compare them against any database and it does not store who anybody is. When it counts people, the result is a number — how many people are in an area or how many go past a point — never a list of who went through. And what is stored, for how long and who may see it is your decision: the system can run entirely inside the station, without a single image leaving it.

Yes, IRIS detects a person falling onto the track, because the track is an area drawn on the image and a person inside that area is a rule that triggers by itself. The alert goes out with the camera and the time, and the control room has the picture open without waiting for a passenger to hit the emergency button or use the intercom. The honest part: the detection depends on that camera actually seeing the track, and not all of them do. During the project we review platform by platform what framing is needed and tell you which ones fall short.

IRIS works when the platform is packed, with one caveat we would rather say before signing: when people block each other, some things stop being visible. Somebody who falls to the ground behind a tight group can be hidden from that camera, and what cannot be seen cannot be detected. Occupancy, on the other hand, is still measured just the same: telling how full a platform is getting does not require telling one person from another. That is why platforms are best covered with more than one framing: two perspectives of the same platform block each other far less than one.

The alert is sent to whoever you decide, over the channel you decide. Every rule carries its recipient: the control room position, the station manager, the maintenance team, the security detail. On screen it opens the camera with what was seen, the time and the video of the moment, so that the person deciding sees exactly what the system saw and not a bare label. And a person on the track does not have to travel the same route as a broken ticket machine: each alert goes to whoever can deal with it. Who decides what to do is always a person: IRIS opens the camera, shows it and waits.

IRIS can replace the passenger counts you do today, and it does what they cannot: count every day of the year, at every hour, at every point you care about. A three-day count gives you a snapshot of three days; a camera with IRIS gives you the whole season, showing which way people come in, how long they wait at the security check and how many are left behind at a stop. And for people counting, our system is type-approved by the Spanish Metrology Centre: that is the guarantee that the figure you present is the right one, because the one who checked it is a third party and not us. Worth putting precisely: that approval covers people counting, not the whole product.

The video leaves the station or stays inside depending on the option you choose, and there are exactly two. In the on-site option it does not leave: the servers are in your own facilities, the video comes in over your network, it is analysed there and the system does not need the internet to work. In the other one it is processed in our data centre, which is our own cloud and not a third party's. In both, communications are encrypted and the terms are set out in the contract. It is worth deciding early, because it drives how the station's network and servers are sized.

Data protection is handled by configuring the processing piece by piece: what is stored, for how long, who can access it and from where. That is the starting point, and above it sits the part that weighs most: IRIS does not identify anyone, so there are no identities to protect. Compliance, though, does not depend on the software alone: it also depends on how you deploy it and what you decide to process, and that is signed off by your organisation, not by us. What we can put on the table is that our way of working is certified for information security and for privacy by an external auditing body. That paper is not signed by a salesperson: it is signed by an auditor, and you can ask us for it before you sign anything.

False alarms exist in a busy station, and anyone who tells you otherwise has never put a detection system in front of that many people. An emotional goodbye looks like a scuffle. A rucksack on the floor looks like an abandoned bag. A reflection on a wet floor looks like anything at all. That is why a rule is never a single condition, but what is seen, where it is seen and how long it has been there. Those three values get tuned with your operators over the first few weeks, platform by platform and entrance by entrance, until what reaches the control room is what the control room wants to get. An alert the afternoon shift learns to ignore is a badly tuned alert, and that can be fixed.

The cost is worked out from how many cameras are analysed, what is detected or measured on each one, which deployment option you choose and whether the hardware is yours or we supply it. There is no single price list, because analysing the platforms of a small station does not cost the same as a whole station with concourse, gatelines, bus bays, taxi rank and car park, and neither costs the same as a network of twenty stations. Tell us how many cameras you have and what you want to detect on each, and we will give you a number. The phone number is +34 902 02 70 91.

No, IRIS does not identify your customers: it detects objects, behaviours and situations. It does not recognise faces, does not compare them against any database, does not store who anybody is, does not follow a person from one store to another and is not cross-referenced with your loyalty programme. What it sees is «a person», «a trolley», «an empty shelf», where it is and how long it has been there. That is why a store's counting never says who came in: it says how many, through which door and at what time. If somebody ever offers you the opposite, know that we do not do it, and that this is not an oversight: it is a decision.

Yes, IRIS works with the cameras you already have in the store. It connects to the feed of the ceiling IP cameras and analyses it as it arrives: what changes is not the hardware, it is what gets understood from the picture. During the project we check camera by camera whether the framing is enough for what you want to see there — a camera set up to watch the door may not reach the shelf at the back — and we tell you plainly which ones fall short and which just need turning a few degrees. Adding a new camera is the exception, not the starting point.

No, this is not for catching shoplifters, and we would rather say so before it comes up in a meeting. None of the ten cameras on this page does that, and it is not because it never occurred to us: detecting theft means judging the intent of one particular person, and IRIS does not look at particular people. What it does do is what you have on this page: flag a gap on the shelf, something spilled on the floor, an area left in the dark or a shop floor busier than the shift can handle; and measure queues, fitting rooms, trolleys, how people spread across the floor and what the promotional display actually achieves. In other words: sell better and keep the store in the state it should be in. If what you need is loss prevention, you will need something else, and we will tell you that in the first meeting rather than the last.

You know how many people give up on the queue because IRIS counts two things separately: how many people enter the waiting area at the tills and how many reach the point of payment. The difference is the people who left before their turn came. Two more clues get added to that: the average wait in that queue, and the trolleys left abandoned in an aisle or beside the tills, which nearly always belong to someone who got tired of waiting. And all of it carries a timestamp, so it can be cross-referenced with how many tills were open at that moment. We are not going to tell you how much money that is — we do not know, it never went through your till — but we will tell you what time it happens and with how many tills open it stops happening.

IRIS can tell you whether a promotion is working in the part you can see from a camera: how many people walk past the display, how many stop and how long they stay. The sale itself is in your till, and we do not go in there. But putting the two halves together changes the diagnosis: if a lot of people walk past and almost nobody stops, the problem is where the display sits or how it looks. If a lot of people stop and it still does not sell, the problem is the price or the product. Today those two situations look identical in the sales report — it sold badly — and they are two different problems with two different fixes. The same works for comparing the same display in two stores, or the same spot in two different weeks.

IRIS works when the store is packed, with one caveat we would rather say before signing: when a lot of people are close together, some block others and a camera stops telling them apart one by one. That happens to any vision system, ours included, and anyone who tells you otherwise has never tried it on a Saturday afternoon. What does not get lost is exactly what matters most at that moment: occupancy. Measuring how many people are in an area and how they spread across the floor does not require telling each person apart, so it keeps working, and detecting that the store is overwhelmed works precisely because it is full. What does degrade is counting people one by one through a narrow, crowded gap; in that case the counting is moved to the entrance, where people go through in single file, and occupancy is left to cover the shop floor.

The video leaves the store or stays inside depending on the option you choose, and there are exactly two. In the on-site option it does not leave: the servers are in your own facilities — in the store or at head office —, the video comes in over your network, it is analysed there and the system does not need the internet to work. In the other one it is processed in our data centre, which is our own cloud and not a third party's. In both, communications are encrypted and the terms are set out in the contract. In a chain it is worth deciding early, because a server per store is not the same as bringing the analysis to one single place: it drives the network in every branch.

Data protection is handled by configuring the processing piece by piece: what is stored, for how long, who can access it and from where. And above all of that sits the part that weighs most in a shop: IRIS does not identify anyone, so there are no identities to protect and no customer profiles to build. Compliance, though, does not depend on the software alone: it also depends on how you deploy it and what you decide to process, and that is signed off by your organisation, not by us. What we can put on the table is that our way of working is certified for information security and for privacy by an external auditing body. That paper is not signed by a salesperson: it is signed by an auditor, and you can ask us for it before you sign anything.

IRIS works for a single store and for a chain alike; what changes is not the system, it is what you do with the data. In one store it helps you decide your store: when to open the third till, where to put the promotional table, whether the back of the shop gets visited at all or needs a reason to walk to. In a chain something appears that a single store does not have: comparison. The same promotion set up in forty stores and measured the same way in all of them. The store where the queue spikes half an hour earlier than the rest. The one that is the same size and has half as many people at the back. Starting with one store, seeing what comes out and deciding afterwards is the normal way in, and it is what we usually recommend.

The cost is worked out from how many cameras are analysed, what is detected or measured on each one, how many stores are included, which deployment option you choose and whether the hardware is yours or we supply it. There is no single price list, because measuring the tills and the entrance of a corner shop does not cost the same as covering the whole floor of a large supermarket, and one store does not cost the same as forty. Tell us how many stores you have, how many cameras are in each and what you want to see, and we will give you a figure. The phone number is +34 902 02 70 91.

No, this is not here to keep watch on your workers, and it needs saying in plain words. IRIS does not identify anyone: it detects that a person is not wearing a helmet, it does not detect who that person is. It does not recognise faces, does not compare them against any database, does not store who anybody is, is not there to clock people in, is not there to discipline a particular worker and does not replace the site's access control. What it sees is «a person without a helmet in the plant area», where they are and since when, and that is what the alert carries. If the site has a works council, this is the first thing you should be able to show them: a system that looks at situations, not at people.

No, IRIS does not stop the crane. It touches no machine, cuts no control and does not replace the safety officer on site, the banksman or the site safety plan. What it does is flag a risky situation while it is happening — with the camera, the time and the video — so that whoever is directing the manoeuvre can stop it. The decision stays with a person, and it has to: on a building site, the judgement of whoever is standing there is worth more than any automation. What IRIS adds is what that person is missing, which is a pair of eyes on the spot where, right now, nobody is looking.

You will get the alerts your rule asks for, and tuning that rule is the work of the first month. A system that fires a hundred alerts a day gets switched off within a week; we know that, which is why a rule is never «alert if someone has no helmet». It is «alert if someone without a helmet is inside the plant area, during working hours, for more than a few seconds». You bound the zone on the image, the hours, how long the situation has to last and who the alert goes to. You start with what really matters on that site, review a week of alerts with your own team and adjust. The goal is not to alert about everything: it is to alert about what makes you look up, and stay quiet about the rest.

Yes, IRIS works with the cameras you already have on site, including the ones that go up and come down as the job moves on. It connects to the feed and analyses it as it arrives: what changes is not the hardware, it is what gets understood from the picture. During the project we check camera by camera whether the framing is enough for what you want to see there — a camera put up to watch the laydown area at night may not be able to make out a helmet on the far side of the plot — and we tell you plainly which ones fall short and which just need moving or lowering. Dust, backlight and rain get checked on the spot, because a building site is not a corridor with fixed lighting. Adding a new camera is the exception, not the starting point.

The site changes every few weeks, and that is exactly why the system is built so that changing it costs little time. When a camera moves or a zone is redrawn, you mark the zone on the image again and carry on: nothing to order in, nobody to wait for. Alert rules are written in words, so a rule for the phase that is starting is written in a while and tested the same day. That is the difference between a system that is useful for the first month and one that is still useful at fit-out, when the site looks nothing like it did at setting-out.

Yes, you can know how many people are inside each work area, and that is one of the two cameras on this page that alert nobody: they only measure. You draw the zone on the image and IRIS counts who comes in and who goes out, never saying who they are. It serves the moment — how many people are in the basement right now — and it serves the record, showing at what time everybody ends up in the same place. Asking is for searching and counting is for measuring, and they are not done the same way: a line cannot be described in a sentence, it has to be traced. For people counting our system is type-approved by the Spanish Metrology Centre, so the figure you see has been verified by a third party, not by us. Worth putting precisely: that approval covers people counting, not the whole product.

The video gets processed wherever you decide, and on a building site that matters because connectivity is not always there. There are two options and only two. The first is inside the site itself: a unit in the site office analyses the cameras right there and works with no internet, so if the line drops the system keeps seeing and keeps alerting. The second is our own data centre, which is our cloud: the video is processed there and the site only needs a connection. You can start with one and move to the other, and in a contractor with many sites the two live side by side.

The works council gets told exactly this, and the sooner the better: what the system looks at, what it does not look at and who receives the alerts. IRIS detects situations, not people: it does not recognise faces, does not identify anyone and is not there to discipline a particular worker. What is processed, how long it is kept and who can see it is configured, and it is configured with you. And we say it without dressing it up: data protection compliance is signed off by your organisation, not by a salesperson of ours; we hand over the tool and the documentation of how it processes data. A site where the workforce's representatives understand what the system is for works; a site where they do not, does not.

This works for a single site and takes on another meaning across all the company's sites. On one site, the value is the alert: somebody finds out about the situation while it is happening. In a contractor with dozens of sites at once, something appears that a single site does not have — comparison with the same yardstick: the same rule, written the same way, applied everywhere. Then you can see which site piles up more risky situations in the same kind of work, which one fixed them after a toolbox talk and which one is worth a visit. Today that is decided by the gut feeling of whoever walks the most sites. With the numbers in front of you it is decided better, and it can be explained.

It costs according to how many cameras get analysed, what each one is asked to do and where the video is processed. We do not publish a price list because it would not be honest: a site with six cameras and two rules and a contractor with twenty sites open are not the same project. What you can do is start small: a couple of points on one site, the two or three rules that really matter there, and look at the alerts and the numbers with your own team before deciding anything. Write to us and we will go through it with your drawings and your cameras in front of us.

No, this is not here to classify the people held here, and it needs saying in plain words. IRIS identifies nobody: it recognises no faces, compares them against no database, stores who nobody is, keeps a file on nobody and does not follow any particular person around the facility. Nor does it predict or judge: it does not say who is going to do what, it scores nobody, it grades nobody by their behaviour and it reads nobody's mood. What it detects are situations the facility itself defined: «there is a person on the floor on wing three», «there is a group gathered in a corridor at an hour when nobody should be there». What is happening, where and since when. That is everything the alert carries, and it is the first thing you should be able to show the governor, the staff representatives and whoever has to sign this off.

No, IRIS opens and closes no door, triggers no automatic alarm standing in for a decision and replaces no officer. Nor does it replace the official count or any of the facility's prevention protocols: those carry on exactly as they are, done by the same people and by the same procedure. What IRIS does is give warning earlier — with the camera, the time and the video — so that a person gets there. Who goes, when they go and what they do is decided by whoever is on duty, and it has to stay that way: inside a prison, the judgement of someone who knows that wing and the people on it is worth more than any automation. What IRIS adds is what that person is missing, which is a pair of eyes on the screen nobody is looking at right now.

You are going to get the alerts you decide on, because the rule is narrowed down: area, hours and duration. A system that throws two hundred alerts a shift is switched off within a week, and rightly so: when everything alerts, nothing alerts. That is why a rule is not «tell me if there are people in the corridor» but «tell me if three or more people are standing still in this corridor, between ten and seven, for more than a minute». Change the area, the time band and the minimum duration and the same detector goes from firing a hundred times a day to firing when it really matters. And it gets tuned afterwards, with whatever came out over the first fortnight: rules are sharpened on what happens in your facility, not on what happens in general.

The facility decides, not IRIS. Which area, at what hours, how many people and for how long: the institution writes that, and it stays written as a sentence anybody can read and anybody can change. IRIS applies what it has been told, the same way every time and without tiring. It does not ship with a list of «suspicious» behaviours and it does not decide on its own what counts as normal in your yard: what is normal in one prison is not normal in another, and the people who work there know it. If the dining hall hours change tomorrow, a wing closes for works or a new block opens, the rule gets rewritten in a while and nothing has to be ordered in. And because it is written as a sentence, you can show it exactly as it is to anyone who asks what that camera is actually looking for.

The rights of the people inside and of the staff are protected by deciding what gets looked at and what does not, and here the answer is short: what gets looked at are situations in common areas the facility has defined — a yard, a corridor, a loading dock — and who anybody is does not get looked at. There is no facial recognition, no number-plate reading, no file on any prisoner and no file on any member of staff. IRIS cannot tell you «this person has come through here six times», because it does not know who they are: the alert says what situation, on which camera and at what time. And the rest is not signed off by a salesperson of ours: the legal footing, the information given to staff and to the people inside, and the decision on where there is a camera and where there is not are signed by the administration that installs it, with its own legal service and with the staff representatives in the room. Be wary of anyone who tells you otherwise.

Yes, it works with the cameras you already have, and that is exactly the point: a prison already has hundreds, and what is missing is not cameras, it is somebody to watch them. IRIS analyses the video signal those cameras are already producing. What does shape the result is where each one is mounted and what can be seen from there: a camera looking down the yard head-on from above gives far more than one placed so the whole wall fits in frame. Before promising anything we would rather look at your drawings and a few real frames, and tell you which cameras this makes sense on and which it does not. Sometimes the answer is to move one camera two metres, and that is cheaper than buying anything.

The video leaves the facility only if you want it to, and in a prison the normal answer is that it does not. IRIS can run inside the facility itself, on your own hardware and with no internet connection: the images go nowhere and the analysis keeps working even if the line drops. It can also run in our data centre or in the cloud if that suits you better, but that is your decision and not a condition of ours. Wherever it runs, an alert always keeps the same things: the camera, the time, the situation detected and the clip of video, so that the incident report can rest on something more than a memory afterwards.

The headcount by area is reliable because it is not set up by talking, it is set up by drawing: you trace a line or an area on the image and count who crosses it and how many people are inside. A line cannot be described in a sentence; it has to be traced. That is why the number is worked out the same way every day, can be repeated and can be audited. And on people counting you do not have to take our word for it: our system is type-approved by the Spanish Metrology Centre, an independent third party that has verified that the figure is the right one. Put precisely: that approval covers people counting, not the whole product. And one more thing, because it matters: this does not replace the official count. It is knowing how many people are in the yard right now, which is a different question and is answered a different way.

What IRIS does not see is real, and it is worth saying before anything gets signed. A camera only understands what falls inside its frame: if something happens off camera, behind a pillar, between two bodies or in an area with no camera at all, IRIS does not see it — no more than a person watching that same screen would. In poor light, in heavy rain or with a dirty lens, it sees worse. And some situations look a lot like each other: two people hugging and two people grappling can be confused for a second, which is why an alert is always closed by a person looking at the video. IRIS is not infallible and we are not going to sell it to you as if it were. It is a system that watches, every hour, the cameras nobody is watching right now.

It costs according to how many cameras get analysed, what each one is asked to do and where the video is processed. We do not publish a price list because it would not be honest: one block with twelve cameras and three rules and a whole facility with hundreds are not the same project. What you can do is start small: one yard and one wing, the two or three rules that really matter there, and look at the alerts and the numbers with your own team before deciding anything. Write to us and we will go through it with your drawings and your cameras in front of us.

No, we are not going to put cameras in the rooms, and this comes before anything else. There is no camera in a room, none in a bathroom, none in an examination room and none anywhere a patient is treated or examined. IRIS looks at common areas: corridors, waiting rooms, lobbies and entrances, which is where almost any hospital already has cameras today. And in those areas it identifies nobody: it recognises no faces, compares them against no database, does not know who any patient or member of staff is, keeps a file on nobody, has no access to medical records and is not cross-referenced with any medical data or with the hospital's systems. What it sees is «there is a person on the floor in the third-floor corridor»: what is happening, where and since when. That is everything the alert carries, and it is the first thing you should be able to show the board, the clinical staff and whoever has to sign this off.

No, IRIS does not diagnose and does not decide who gets seen first. It does not say what is wrong with anybody, it assesses nobody's state of health, does no triage and prioritises no patient: clinical judgement belongs to a professional and IRIS takes no part in it. Nor does it access medical records or any medical data, and it does not connect to the hospital's systems to find out who anybody is. And it replaces neither clinical observation nor any member of staff: the ward's protocols carry on exactly as they are, done by the same people and by the same procedure. IRIS also calls nobody on its own account and triggers nothing in place of a decision. What it does is give warning earlier — with the camera, the time and the video — so that a person gets there, and that person is the one who looks, assesses and decides.

You are going to get the alerts you decide on, because the rule is narrowed down: area, hours and duration. A system that throws a hundred alerts a shift is switched off within a week, and rightly so: when everything alerts, nothing alerts. That is why a rule is not «tell me if somebody is standing in the corridor» but «tell me if a person is on the floor in this corridor for more than twenty seconds», or «tell me if somebody has been motionless in this waiting room for more than fifteen minutes, between ten at night and seven». Change the area, the time band and the minimum duration and the same detector goes from firing a hundred times a day to firing when it really matters. And it gets tuned afterwards, with whatever came out over the first fortnight: rules are sharpened on what happens in your hospital, not on what happens in general.

The hospital decides, not IRIS. Which area, at what hours and how long counts as «a long time»: the hospital writes that with its own clinical staff, and it stays written as a sentence anybody can read and anybody can change. A quarter of an hour without moving in the emergency waiting room does not mean the same as a quarter of an hour without moving in a ward corridor at four in the morning, and the people who work there know that difference, not a supplier. IRIS applies what it has been told, the same way every time and without tiring. It does not ship with any list of what is «normal» in your corridors. If visiting hours change tomorrow, a wing closes for works or a new floor opens, the rule gets rewritten in a while and nothing has to be ordered in. And because it is written as a sentence, you can show it exactly as it is to anyone who asks what that camera is actually looking for.

The works council and the staff get told everything, and before anything is installed, not afterwards. There is one camera that looks at whether an area has somebody staffing it, and it is the one that raises a hand in any meeting, so it gets explained straight: that is not time-and-attendance, it is not clocking in and it grades nobody. IRIS does not know who is at that station, does not store how long anybody has been anywhere and cannot tell you «this person arrived late» or «this person left early». It tells a member of staff apart by clothing — a coat, a uniform — and not by who they are. What it says is «this area has gone half an hour with nobody in it», which is a question about the area and not about the person. And the rest is not signed off by a salesperson of ours: who sees the alerts, what they are used for and what may not be done with them is written by the hospital with staff representatives in the room, and in writing. A system like this only works if the staff know what it looks at and what it does not.

Yes, it works with the cameras you already have, and that is exactly the point: a hospital already has hundreds in corridors, lobbies and entrances, and what is missing is not cameras, it is somebody to watch them. IRIS analyses the video signal those cameras are already producing. What does shape the result is where each one is mounted and what can be seen from there: a camera looking down the length of a corridor from above gives far more than one placed to get the whole doorway in. Before promising anything we would rather look at your plans and a few real frames, and tell you which cameras this makes sense on and which it does not. Sometimes the answer is to move a camera two metres, and that is cheaper than buying anything.

The video leaves the hospital only if you want it to, and in a hospital it normally does not. IRIS can run inside the hospital itself, on your own hardware and with no internet connection: the images go nowhere and the analysis keeps working even if the line drops. It can also run in our data centre or in the cloud if that suits you, but that is your decision and not a condition of ours. Wherever it runs, an alert always stores the same thing: the camera, the time, the situation detected and the clip of video, and nothing else. No name, no record number, no medical data, because IRIS neither has them nor asks for them.

The figure for how many are waiting in A&E is reliable because it is not set up by talking, it is set up by drawing: you trace a line or an area on the image and count who crosses it and how many people are inside. A line cannot be described in a sentence; it has to be traced. That is why the number is worked out the same way every day, can be repeated and can be audited. And on people counting you do not have to take our word for it: our system is type-approved by the Spanish Metrology Centre, an independent third party that has verified the figure is the right one. Put precisely: that approval covers people counting, not the whole product. And one more thing, because it matters: that number says how many people there are and since when, so you can reinforce the shift or open another desk. It does not say who anybody is and it does not decide who gets seen first.

What IRIS does not see exists, and it is worth saying before anything gets signed. A camera only understands what falls inside its frame: if something happens inside a room, in a bathroom, behind a closed door or in a corridor with no camera, IRIS does not see it, just as a person watching that same screen would not. In low light or with a dirty lens it sees worse. And some situations look very much alike: somebody bending down to pick something up and somebody who has lost their balance can be confused for a second, which is why an alert is always closed by a person looking at the video. And the whole sentence has to be said: IRIS prevents no fall. The fall has already happened by the time IRIS sees it. What changes is how long that person is on the floor before somebody arrives. We are not going to sell you an infallible system, because it is not one. It is a system that watches, every hour, the corridors nobody is watching right now.

It costs according to how many cameras are analysed, what each one is asked to do and where the video is processed. We do not publish a price list because it would not be honest: a ward with twelve cameras and three rules and a whole hospital with hundreds are not the same project. What can be done is to start small: one corridor and the emergency waiting room, the two or three rules that really matter there, and see the alerts and the numbers with your own team before deciding anything. Write to us and we will look at it with your plans and your cameras in front of us.

No, we are not going to recognise any pupil, and this comes before anything else. IRIS does not recognise faces, does not compare them against any database, does not know who any child is, keeps no face, follows no minor and holds a file on nobody. It does not read number plates either: in a school that function is not switched on. And there are places with no camera: not in the toilets and not in the changing rooms. IRIS looks at common areas — the playground, the entrances, the shared corridors and the street outside the gate — which is where almost every school already has cameras today. What it sees is «there is a child on the ground on the back court and they have not got up for three minutes»: what is happening, where and since when. That is everything the alert contains, and that is the first thing you have to be able to show the staff, the parents' association and the families.

No, IRIS does not detect bullying, and anyone telling you otherwise is not being straight with you. Bullying is a pattern a trained professional assesses, looking at many things that never happen in front of a camera. A camera sees something else: it sees a closed ring that forms in the same corner at the same time, or a child who has spent the whole break alone. That is a fact you can check, not a diagnosis. IRIS does not say who bullies, does not say who is difficult, does not say who is sad and puts a label on no child. It does not diagnose and it does not predict. What it does is show the school team where and when to look, with the video in front of them. What that means is decided by a trained person — the class teacher, the school counsellor, the team — and IRIS does not touch that part.

No, IRIS opens no door and calls nobody of its own accord. It does not open or close the school gate, it sets off no siren, it alerts nobody outside the school and it takes no decision in place of a person. It does not replace the teacher on duty either: the playground is still watched by whoever watches it today, on the same rota and with the same judgement. It does not monitor the staff — it is not time-keeping, it is not clocking in and it appraises nobody — and it issues no fines to any car. All it does is raise an alert early, with the camera, the time and the video, so an adult from the school walks over. Who goes, what they do and what gets written down stays exactly as it is now.

You are going to get the alerts you decide on, because the rule is bounded: area, time of day and duration. A system that fires fifty alerts in one break is switched off within a week, and rightly so: when everything alerts, nothing does. That is why a rule is not «tell me if there is a child on the ground», which in a playground happens constantly and almost always because they are playing, but «tell me if there is a child on the ground on this court for more than two minutes», or «tell me if this area has had no adult in it for ten minutes between eleven and half past». By changing the area, the time window and the minimum duration, the same detector goes from sounding all the time to sounding when it really matters. And the rule is written by the school with its team and its counsellor, not by a supplier: how long is «a long time» and which corner matters is known by the people who are there every day. It is then tuned with what came out in the first two weeks.

The staff, the parents' association and the families are told everything, and before anything is installed, not afterwards. You show them what is watched: the playground, the entrances, the shared corridors and the street outside the gate. And what is not watched: the toilets and the changing rooms, where there is no camera. You tell them in these words that there is no facial recognition, that there is no file on any minor and that IRIS labels no child. And you explain the camera that counts how many people are still in each space, because that is the one that raises a hand in any meeting: it is there to know how many people have yet to get out if the building has to be evacuated, and it is not taking the register, because it counts people and does not know who they are. The rest is not signed off by a salesperson of ours: the legal framing and the information given to families are signed by the school and its governing body, who are the ones answerable for it. A system like this only works if the staff and the families know exactly what it looks at and what it does not.

Yes, it works with the cameras you already have, and that is exactly the point: a school usually already has cameras at the gate, in the playground and in the corridors, and what is missing is not cameras, it is somebody to watch them. IRIS analyses the video signal those cameras are already producing. What does affect the result is where each one is mounted and what can be seen from there: a camera that covers the playground lengthways and from above gives far more than one placed so the whole gate fits in frame. Before promising anything we would rather look at your plans and a few real images and tell you which cameras this makes sense on and which it does not. Sometimes the answer is to move one camera two metres, and that is cheaper than buying anything.

The video leaves the school only if you want it to, and in a school the normal thing is that it does not. IRIS can run inside the school itself, on your own machine and with no internet connection: the images go nowhere and the analysis keeps working even if the line goes down. It can also run in our data centre or in the cloud if that suits you better, but that is your decision and not a condition of ours. Wherever it runs, an alert always keeps the same things: the camera, the time, the situation detected and the clip of video, and nothing else. No name, no class, no stored face, because IRIS neither has them nor asks for them.

The figure for how many people are still inside is reliable because it is not set up by talking, it is set up by drawing: you trace a line or an area over the image and count who crosses it and how many people are inside. A line cannot be described in a sentence; it has to be drawn. That is why the number is worked out the same way every day, can be repeated and can be audited. And on people counting you do not have to take our word for it: our system is certified by the Spanish Metrology Centre, an independent third party that has verified the figure is the right one. Said precisely: that certification covers people counting, not the whole product. And one more thing, because it matters: that number says how many people are still in a space and since when, so that in a drill or in a real evacuation you know where people have yet to get out. It does not say who anybody is and it is not taking the register.

What IRIS does not see is real, and it is worth saying before anything is signed. A camera only understands what falls inside its frame: there is no camera in the toilets or the changing rooms, and whatever happens there IRIS does not see and will not see. It does not see behind a closed door either, nor in the corner a tree hides, nor outside the hours the school has decided it should watch. In poor light or with a dirty lens it sees worse. And some situations look very much alike: a pile of children throwing themselves on each other in play and a fight can be confused for a second, which is why an alert is always closed by a person looking at the video. And the whole sentence has to be said: IRIS prevents no fight and prevents no road accident. By the time IRIS sees it, it is already happening. What changes is how long it takes before an adult gets there. We are not going to sell you an infallible system, because it is not one. It is a system that watches, all day long, the playground nobody is watching right now.

It costs according to how many cameras are analysed, what each one is asked to do and where the video is processed. We do not publish a price list because it would not be honest: a playground with four cameras and two rules and a whole school with the gate, the corridors and the street are not the same project. What you can do is start small: the playground and the gate, the two or three rules that really matter there, and look at the alerts with your team before deciding anything. Write to us and we will go through it with your plans and your cameras in front of us.

No, IRIS does not identify anyone: it does not read number plates and does not recognise faces. What it sees is «a person on the dam crest» or «a vehicle stopped at the access», where they are and since when. It compares nothing against any database and stores nobody's identity. If what you need is to know whose car that is or who came in, this does not do it, and we would rather say so now than later.

No, IRIS does not predict a flood, a breakdown or a fire. IRIS predicts nothing. It flags what is happening in front of the camera and is already visible: water that has already gone past a reference mark, logs already piling up in front of the spillway, smoke already coming off a heap. That arrives before the damage does, which is why it is worth having; but it is the warning of something under way, not a forecast. With a camera nothing else can honestly be promised.

No, IRIS opens and closes no gate, stops no pump and triggers no operation. Nor does it replace the site's instrumentation: not a level sensor, not the electrical protection, not a fire suppression system, and not any flood warning system. It is a layer that watches the cameras and gives warning earlier, so that a person decides. Everything that operates the site stays yours, and it stays decided by whoever decides it today.

IRIS knows the water has risen because it sees it above a physical reference that is there in the image: a painted gauge, a step, the edge of a chamber, an embankment. That reference is not described in a sentence, it is traced on the image: that is why the reading comes out the same way every day and can be audited. And it needs saying plainly: that is not a water level gauge. It gives no height in metres and replaces no instrumentation. It says «the water has gone past this line», which is very often exactly what nobody is watching.

A camera can see what is visible and cannot see what is not, and being clear about that before writing a rule saves trouble later. IRIS sees a gate in a position, and reads no telemetry and does not know whether the command got through. It sees a flooded pump room with the pumps still, and does not know whether a pump is running. It reads a level against a visible physical reference, and it is not a water level gauge. Those are observable signals, not process measurements: they are there to warn with margin, not to replace your sensors. That said, if the camera is a thermal one then temperature is visible, because there the temperature is the image: IRIS finds the hot spot before there is any smoke. In a waste heap the fire starts inside and by the time smoke shows it has been going for hours; in a substation, a connection heating up shows before anything burns. And there is nothing new to buy: IRIS watches the thermal cameras you already have exactly as it watches the rest.

You will get the alerts your rule asks for, and bounding that rule is the work of the first month. At a site with no staff this matters more than anywhere else: a badly bounded rule fires a hundred alerts nobody reads, and within a week the system is switched off. That is why a rule is not «tell me if there is somebody». It is «tell me if there is a person inside the fenced compound, between ten at night and six, for more than twenty seconds». Zone, hours and duration. With those three, most nights nothing goes off — and the night it does, somebody looks.

The video can be processed inside the site itself, with no route out to the internet. It is the mode that defines the product, and this is where it shows most: a local machine analyses the cameras and applies the rules right there, and the images never leave your network. If there is a connection, the alert also reaches the control room or the phone of whoever is on call; if it drops, IRIS keeps watching and keeps storing what it has seen. It can also be processed in our own data centre or in the cloud. You choose, site by site.

The alert reaches whoever you decide, because at four in the morning there is nobody in front of the cameras and that is precisely the problem. It can go to the control room, to the phone of the person on call, to the security company you have under contract, or to all three at once. And it arrives with the camera, the time and the video of that moment, so that whoever receives it can decide without getting up: this can wait until morning, or somebody has to go and look now. It is all stored, so the next day nothing has to be reconstructed out of hours of recording.

The operator of the site decides, not IRIS. You write the rules, in your own words and in one sentence, because you are the ones who know what is normal at your plant and what is not: whether authorised vehicles use that service track every day, whether that door may be open during working hours, past which line the water stops being normal. IRIS brings no factory criterion and does not decide on its own what matters. It applies yours, the same way every time, every hour of the year. And when the operation changes, you change the sentence.

A dam and a landfill have nothing in common, and you do not need a system for each: it is the same one. This page shows seven types of site — a dam, a treatment plant, a substation, a storm tank, a riverbed, a landfill and a tunnel — with the same rules, written the same way and in one sentence. That is why it also works when you have not one site but hundreds, spread across a whole province and of seven different kinds: one way of writing rules, one place the alerts arrive, one thing to learn.

Yes, it works with the cameras you already have in the plant. IRIS connects to the feed of the IP cameras already installed and analyses it as it arrives: what changes is not the equipment, it is what gets understood from the picture. Now the uncomfortable part: a factory floor is not a corridor with steady light. Dust from a crusher, steam from a cooking room and the backlight of an open bay door all degrade what can be seen, and some framings simply fall short. During the project we check camera by camera and tell you plainly which ones work, which would only need moving a few degrees, and which are not good enough for what you want to see there.

No, this is not for keeping an eye on the operators, and that has to be said in plain words. IRIS does not identify anybody: it detects that there are hands inside an open machine guard, not whose hands they are. It does not recognise faces, does not compare them against any database, is not a time clock and cannot be used to discipline a particular person. What reaches the alert is the situation, where it is and since when. If the plant has a works council, this is the first thing you should be able to show them, and the sooner the better: a system that looks at situations, not at people.

No, IRIS does not stop the machine and does not connect to the PLC. It touches no control, cuts no line, and does not replace the interlock, the lockout-tagout procedure or the safety plan. What it does is flag the situation while it is happening — with the camera, the time and the video — so that whoever is in charge of that area can decide. The decision stays with a person, and it has to: on a plant floor, the judgement of the person standing there is worth more than any automation. IRIS adds what that person is missing, which is a pair of eyes where nobody is looking right now.

You will get the alerts your rule asks for, and tuning that rule is the work of the first month. A system that throws a hundred alerts a shift gets switched off within a week; we know that, which is why a rule is never «alert if someone is near the forklift». It is «alert if a person on foot is inside the forklift aisle, during production hours, for more than a few seconds». You bound the zone on the image, the hours, how long the situation has to last and who receives it. You start with what really matters in that building, review a week of alerts with your team and adjust. An alert nobody attends to is a badly configured alert, and that gets fixed.

The video leaves the factory or stays inside depending on the mode you choose, and there are two modes. In local mode it does not leave: the servers are on your premises, the video comes in over your network, it is analysed there and the system does not need internet to work. That matters in a plant where the line drops or where the connection is poor. In the other, it is processed in our data centre — which is our own cloud, not a third party’s — and then it does leave, encrypted and under the terms signed in the contract. In an industrial group the usual answer is a mix: sensitive inside, the rest outside.

You do not need a separate system for each plant: it is the same system, and what changes is what you ask of it. A pharmaceutical airlock, a chemical bund and a recycling belt are very different scenes, but underneath they are the same thing: a zone drawn on the image and a rule written in words. That is why a new plant does not start from scratch, and why a steel works and a food factory can share the same way of working. And something appears that a single plant does not have: comparison with the same yardstick. The same rule, written the same, applied everywhere, so you can see where the situation repeats and which plant is worth visiting.

IRIS does not see what does not fit in a picture, and in a plant that list matters. It does not read a sensor or a PLC: it does not know the temperature of a furnace, the pressure in a line or the concentration of a gas. It does not see inside a closed machine, a vessel or a pipe. A colourless gas is invisible, and very thin smoke is not seen early either. That is why IRIS is not fire detection nor gas detection, and replaces neither: those installations stay where they are. What IRIS sees is what can be seen: flame, smoke once it is visible, liquid on the floor, an open door, a person where they should not be.

No, it does not replace your sensors, your safety installation or your prevention plan: it lives alongside all of them. A sensor measures one quantity at one point; IRIS understands a whole scene. They are different things and you need both. What IRIS adds is the layer you are missing today: watching every camera at once and telling you what is happening in front of them. You can keep recording and managing video where you do it now, because IRIS is an NVMS and sits on top. What gets integrated and how is decided by looking at your actual system, not by promising in advance that we fit with everything.

Yes, besides alerting it can measure, and the two are not configured the same way. An alert is written with a sentence. A measurement is drawn: a line that gets crossed, a zone that gets occupied. Out of that comes a figure per hour, per shift and per season: how many people are inside an area, how many pallets pass a point, how long a line has been stopped. Asking is for searching. Counting is for measuring. And they are not done the same way: a line cannot be described in a sentence, it has to be traced. For people counting our system is type-approved by the Spanish Metrology Centre, so that figure has been verified by a third party and not by us. Worth putting precisely: that approval covers people counting, not the whole product.

It costs according to how many cameras are analysed, what is asked of each one, how many plants are included, which deployment mode you choose and whether the hardware is yours or ours. We do not publish a price list because it would not be honest: a building with eight cameras and three rules and a group with twelve factories are not the same project. What you can do is start small: two or three spots in one plant, the rules that really matter there, and look at the alerts and the figures with your team before deciding anything. Tell us how many cameras you have and what you want to see, and we will give you a figure. The number is +34 902 02 70 91.

No, you do not need a sensor in every bay. The figure comes from looking at the bays with the cameras the car park already has: you draw on the image which patch of floor each bay is, and IRIS looks at whether there is a car on it or not. One aisle camera covers dozens of bays at once, and it also tells the type apart: reserved, accessible, motorcycle or charging. No digging up the asphalt, no cabling floor by floor, and nothing that already works has to be moved.

It does work with the cameras you already have, and it is worth saying where it falls short. The mouth of a backlit ramp burns out the image at midday. A floor with the bare minimum of lighting leaves aisles where a plate cannot be read. A corner dome fitted to watch the door will not tell the far bays apart. During the project we check camera by camera what can genuinely be detected in that frame, and we tell you plainly which ones fall short, which would only need tilting a few degrees, and which are best left for plain watching. Replacing a camera is the exception, not the starting point.

The number on the sign is reliable because it does not come from subtracting entries and exits: it comes from looking at the bays. Counting cars at the barrier piles up the whole day’s error, which is why by mid-afternoon the sign says «full» with forty free bays on level four. Here every bay is checked one by one, and the number corrects itself. Now the awkward part: if a column hides half a bay, or an aisle has no light, that particular bay reads worse. That shows up during commissioning, bay by bay, and you decide which camera moves and which area stays out of the count.

Yes, IRIS reads number plates, and yes, a plate is personal data. We say it plainly because that is what the law says and because it is worth knowing before signing. That is why reading is your decision, camera by camera: you can switch it on at the barrier for season tickets and leave it off in the aisles. And you configure what is kept, for how long and who can look it up. What IRIS does not do is tell you whose car that is: it queries no vehicle register and no database of people. Matching a plate to an owner is a matter for your season-ticket system and your organisation, not for us.

No, IRIS does not identify people or drivers. It does not recognise faces, does not compare them against any database and does not store who anyone is. What it sees is «a person crossing the walkway», «a car going up the ramp», where it is and since when. In the blocked fire-exit alert, what arrives is that there is someone on the floor and a car in front of the door: never who that person is. And counting is aggregated and anonymous: it says how many cars and how many people went through an area and at what time, never who they were. A counted person is a one, and nothing else remains of them.

You will get the alerts your rule asks for, and tuning that rule is the work of the first few weeks. A system that fires two hundred alerts a day gets ignored within four, and in a car park that happens fast because there is movement all the time. That is why a rule is never «alert if a car is stopped». It is «alert if a car has been stopped outside a bay on level four for more than a few minutes, during opening hours». You bound the area on the image, the hours, how long it has to last and who receives it. Then you review a week of alerts with your team and adjust. An alert nobody attends to is a badly configured alert, and that gets fixed.

The video leaves the car park or stays inside depending on the mode you choose, and there are two modes. In local mode it does not leave: the server sits in your own building, the video comes in over your network, it is analysed there and the system does not need internet to work. That is the usual choice in an underground car park, where coverage is poor anyway. In the other one it is processed in our data centre — which is our own cloud, not a third party’s — and then it does leave, encrypted and under the terms set in the contract. With several car parks it is worth deciding early, because one server per building is not the same as bringing everything to a single place.

No, it does not replace the barriers, the ticketing system or the fire protection system: it lives alongside all three. IRIS opens and closes nothing, takes no payment, validates no season ticket and cuts no charger’s power. What it does is see what is happening and alert whoever can go down there. And here is the important part, said plainly: when it sees smoke or flame at the foot of a plugged-in car, it raises an alert, but it is not a type-approved fire detector and it does not replace the detection and suppression system the regulations require. It is an extra pair of eyes, before the ceiling detector goes off. Never instead of it.

IRIS does not know plenty of things about a car park, and they are better said early than late. It does not know whether someone has paid: that lives in your ticketing system, not in the image. It does not know whose car that is. It does not know whether the person parked in the reserved bay is entitled to be there — it only sees that a car is there and that no authorisation is on record. It does not know what is inside a closed vehicle. And it sees nothing that is not in a frame: if there is no camera on that corner, there is no data there. What it does know is what happens in front of the cameras you already have, and today nobody knows that until somebody complains.

The cost is worked out from how many cameras are analysed, what is detected or measured on each, how many car parks are included, which deployment mode you choose and whether the hardware is yours or ours. We do not publish a single price list because it would not be honest: measuring the bays on one level does not cost the same as covering six levels, two ramps and the barrier. What you can do is start small: one level, two or three rules and free-bay counting, and look at the alerts and the figures with your team before deciding anything more. Tell us how many bays and how many cameras you have and we will give you a figure. The number is +34 902 02 70 91.

Yes, it works with the cameras you already have in the venue. IRIS connects to the feed of the IP cameras that are already installed and analyses it as it arrives: what changes is not the equipment, it is what gets understood from the picture. During the project we check camera by camera whether the framing is good enough for what you want to see there. And we tell you plainly which ones fall short: the stand camera cannot make out a face from the far side of the pitch, and it does not need to, because what it has to see is how many people there are per square metre and whether the line is moving.

No, IRIS does not identify people and does not recognise faces in the stands. It compares nobody against any list, any banning register or any database, and it keeps no record of who anyone is. What it sees are facts: a ring closing around two people, somebody climbing a fence, a lit flare and which row it is in, a density that climbs and a walkway that stops moving. That reaches the screen with the camera and the time. The person who watches the video and concludes what happened is a human being, always.

Yes, you can know how many people are in each area and run capacity from that. You trace a line on the image of each door and IRIS counts who comes in and who goes out, never saying who they are. You draw the zone of a vomitory or a concourse and you know how many people are inside right now. Asking is for searching. Counting is for measuring. And they are not done the same way: a line cannot be described in a sentence, it has to be traced. For people counting our system is type-approved by the Spanish Metrology Centre, so the figure has been verified by a third party, not by us. Worth putting precisely: that approval covers people counting, not the whole product.

IRIS works when the venue is full, with one caveat we prefer to say before signing: when a lot of people come together, some block others and a camera stops telling them apart one by one. That happens to any vision system, ours included. What is not lost is exactly what you need at that moment: how many people there are per square metre in that area and whether the group is moving or has stopped. Measuring density and flow does not require telling each person apart. Where counting one by one does belong is at doors and turnstiles, because there people pass in single file.

IRIS warns about a crowd build-up as soon as the two signals that announce it appear, and it is worth saying what it does not do: it does not see the future and it predicts nothing. What it measures is how many people there are per square metre in that area and how fast they are moving. When density climbs and flow drops at the same time, that is a funnel forming, and it shows up in the alert before anyone notices it from the control room. How much margin you get depends on the spot: on a wide ramp you see it coming with more time than at the mouth of a vomitory. The alert arrives with the camera, the area and the time, and the person on the ground decides the move.

No, this does not replace the stewards, the safety plan or access control: it changes what they look at. Today one person has dozens of screens in front of them and, on a full house, cannot attend to them all. With IRIS they stop watching everything and watch what matters, when it matters. IRIS does not open or close a door, does not stop a turnstile and does not send anyone anywhere: it opens the camera, shows what it saw and waits. The plan stays yours and so does the decision. What it adds is a pair of eyes at the spot where nobody is looking right now.

You get the alerts your rule asks for, and tuning that rule is the work of the first few events. A system that throws a hundred alerts in one match gets switched off by the second; we know that. So a rule is not «alert if there are a lot of people». It is «alert if the density in this area goes above this value and flow drops, for longer than these seconds, during doors-open hours». You bound the area on the image, the threshold, how long it has to last and who receives it. And the alert does not go to an inbox: it goes to the radio and to the phone of whoever is on that gate, with the camera already open. You review a whole event with your team and adjust.

The video leaves the venue or stays inside depending on the mode you choose, and there are two modes. In the local mode it does not leave: the servers are on your premises, the video comes in over your network, it is analysed there and the system needs no internet to work. In a venue that matters a lot, because on a full house the connection is the first thing to saturate, and the system has to keep seeing precisely then. In the other mode it is processed in our data centre, which is our own cloud and not a third party’s. In both, communications are encrypted and the terms are signed in the contract.

A match and a concert are nothing alike, and that is why the system is built so that changing the set-up costs little time. Areas are redrawn on the image: if the stage covers half a stand and a front pit appears, you mark the pit and carry on. Alert rules are written in words, so a rule for tonight’s set-up is written in a short while and tested the same day. And you do not have to redo it every time: you save one configuration per event type — match, standing concert, seated concert — and load the one you need. That is the difference between a system that works for the first match and one that still works during the summer tour.

The cost is worked out from how many cameras are analysed, what is detected or measured on each one, which deployment mode you choose and whether the hardware is yours or ours. We do not publish a price list because it would not be honest: covering the five entrance doors of an arena does not cost the same as the stands, the vomitories and the bars of a whole stadium. What you can do is start small: the two doors that always jam, the capacity counting, and then look at the alerts and the figures with your team after a couple of events. Tell us how many cameras there are and what you want to see, and we will give you a figure. The number is +34 902 02 70 91.

No, there are no cameras in the rooms. None in the bathrooms or in the staff changing rooms either. There is nothing to measure there, because there is no camera there and there will not be one. The cameras this page talks about are at reception, in the lounge, in the dining room, in the kitchen, at the door and in the service area: shared spaces, where cameras already hang today. If anyone offers you analysis inside a guest room, know that we do not do it, and that it is not an oversight: it is a decision.

No, this is not for keeping tabs on your staff, and it needs saying plainly. IRIS measures the situation, never the person: it sees “a table uncleared for eight minutes”, not who was meant to clear it. The alert is there so you open another desk or send someone to the pass, not to single out a waiter or score a receptionist. It identifies nobody, it is no time clock and it is no basis for discipline. If there is a works council, this is the first thing to be able to show them, and the sooner the better.

No, IRIS does not identify guests and does not recognise faces. It detects objects, behaviours and situations: a queue building up, a suitcase alone in the lounge, an empty tray, a person on the floor. It compares no face against any database, it follows nobody from one room to another and it is never cross-referenced with the loyalty programme or the booking record. Counting is aggregated and anonymous: it says how many people are in the dining room at half past nine, never who they were. A counted person is a one: nothing else of them is kept.

Yes, it works with the cameras you already have in the hotel. IRIS connects to the feed of the installed IP cameras and analyses it as it arrives: what changes is not the equipment, it is what gets understood from the picture. Now the uncomfortable part: not all of them are good enough. A camera hung to watch the door may not tell whether a buffet tray is empty, and the reception camera facing a glass façade at midday gives a burnt-out picture where counting goes wrong. During the project we look camera by camera, and we tell you plainly which ones fall short and which would only need moving a few degrees.

Yes, it really measures how long people wait at reception, and it is done by drawing, not by talking. You trace the waiting area and the desk line onto the image. IRIS counts how many people enter the area and how many get served: the difference is whoever gave up and left. Asking is for searching. Counting is for measuring. And they are not done the same way: a line cannot be described in a sentence, it has to be traced. For people counting our system is type-approved by the Spanish Metrology Centre, so that figure has been verified by a third party, not by us. Worth putting precisely: that approval covers people counting, not the whole product.

It works in the kitchen with one caveat we would rather state before signing. A flare-up over the pan shows clearly: it is big, it is bright and it appears all at once. So does a puddle on the floor. What shows badly is thin smoke, and steam from a dishwasher or a stockpot can cover half the picture and pass for smoke. Grease also builds up on the lens and blurs the framing, so the kitchen camera has to be cleaned. And the important part: IRIS is not a type-approved fire detector and does not replace the kitchen suppression system. It warns; it does not put anything out.

You will get the alerts your rule asks for, and tuning that rule is the work of the first month. A system that fires a hundred alerts a day gets switched off within a week. That is why a rule is not “alert if there is a queue”: it is “alert if more than ten people are waiting at reception for more than five minutes with fewer than three desks open”. You set the area on the image, the time band, how long the situation must last and who receives it. And they land on the duty manager’s or the director’s phone, not on a back-office screen nobody watches. You review a week of alerts with your team and adjust.

The video leaves the hotel or stays inside depending on the mode you choose, and there are two modes. In the local mode it does not leave: the servers are on your premises, the video comes in over your network, it is analysed there and the system needs no internet to work. In the other, it is processed in our data centre, which is our cloud and not a third party’s. In both, communications are encrypted and the terms are signed in the contract. In a chain it is worth deciding early, because a server per hotel is not the same as taking the analysis to one place: it shapes the network of every property.

It works for a single hotel and it works for a chain; what changes is not the system, it is what you do with the data. In a single hotel it helps you decide your hotel: when to open the second desk, when to reinforce breakfast, whether the dining room is really full or only looks it. In a chain something appears that one hotel cannot have: comparison against the same yardstick. The same rule, written the same, measured the same across forty properties. The hotel where the queue spikes half an hour earlier than everywhere else. Starting with one, seeing what comes out and deciding afterwards is perfectly normal, and it is what we usually recommend.

The cost is worked out from how many cameras are analysed, what is detected or measured on each one, how many properties are included, which deployment mode you choose and whether the hardware is yours or ours. We publish no single price list, because it would not be honest: measuring reception and the dining room of a sixty-room hotel does not cost the same as covering a whole resort, nor does one property cost the same as forty. What you can do is start small: reception and the dining room, the two or three rules that really matter there, and look at the alerts and the figures with your team before deciding anything. The number is +34 902 02 70 91.

Yes, IRIS works with the cameras the terminal already has. It connects to the feed of the installed IP cameras and analyses it as it arrives: what changes is not the equipment, it is what gets understood from the picture. Now the uncomfortable part. A yard is long, and a camera put up years ago to watch a gate will not make out a person two hundred metres away. Salt and dust leave the lens hazy, and a dirty camera sees less every week. During the project we go through camera by camera and say plainly which ones reach, which ones only need moving or cleaning, and which ones fall short for what you want to see there. Adding a new camera is the exception, not the starting point.

Yes, it works if the line goes down, and at a terminal that is no small matter. There are two modes and only two. The first is local: the servers sit inside the terminal, the video comes in over your network, it is analysed right there and the system needs no internet to run. If the line drops, IRIS keeps seeing and keeps alerting, because the operation does not stop either. The second is our data centre, which is our cloud and not a third party’s: the video then leaves encrypted and under the terms set in the contract. You can start with one and move to the other, and in a port with several terminals both live side by side.

No, this is not for keeping an eye on the dockers, and it needs saying in plain words. IRIS identifies nobody: it sees that a person has crossed the fence or is walking under a suspended load, not who that person is. It does not recognise faces, does not compare them against any database, is not a time clock and cannot be used to discipline one specific worker. What reaches the alert is the situation, where it is and since when. The works council gets shown exactly this, and the sooner the better: what the system looks at, what it does not, and who receives the alerts. A terminal where the council understands what the system is for works; one where it does not, does not.

No, IRIS does not stop the crane. It touches no machine, cuts no control and replaces neither the banksman nor the terminal’s safety plan. What it does is flag the situation while it is happening — with the camera, the time and the video — so that whoever is running the move can stop it. The decision stays with a person, and it has to: on a quay, the judgement of whoever is standing there is worth more than any automation. IRIS adds what that person is missing, which is a pair of eyes at the spot nobody is watching right now.

It sees at night, in fog and in rain depending on how much picture is left, and here we would rather be unpleasant than agreeable. At night it depends on how the quay is lit and on whether that camera is thermal: with light or with thermal you still see a person; with neither, you do not. In rain you lose sharpness but you keep working. In thick fog the picture is gone, and no vision system fixes that: anyone who tells you otherwise has not spent a foggy night on a quay. That is why the project states point by point which ones hold up at night and which do not, before signing and not after.

You will get the alerts your rule asks for, and tuning that rule is the work of the first few weeks. A system that fires a hundred alerts a shift gets switched off in three days; we know that. That is why a rule is never a single condition: it combines what is seen, where it is seen and how long it has been there. «Somebody standing inside the mooring snapback zone, during the operation, for more than a few seconds» is not the same as «somebody standing». You bound the zone on the image, the hours, the duration and who it reaches. A week of alerts is reviewed with your quay supervisors and adjusted. An alert nobody attends to is a badly configured alert, and that gets corrected.

This counts towards the port security plan as one more tool, not as the plan. What it brings is evidence: every detection is kept with the camera, the time and the video sequence, so a fence crossing or a barrier with two trucks and a single opening stops being somebody’s recollection and becomes a record that can be consulted and audited. And it serves equally to back up whoever acted and to contradict them. Now what we will not dress up: the plan is approved by the authority, and it is signed by your organisation. We supply the tool and the documentation on how it processes data, not the stamp.

No, IRIS does not replace the fence, the perimeter sensors or the guards. The fence is still needed: a fence stops somebody, a camera stops nobody. The perimeter sensors stay where they are, and IRIS works alongside them: where a sensor says something touched the fence, IRIS says what can be seen there and shows the picture, which is what you need in order to decide whether to send anybody. With the guards it is the same as in any control room: they are not replaced, what they look at changes. Today they face far more cameras than eyes. With IRIS they stop watching everything and watch what matters, when it matters.

It is for a single terminal and it takes on another meaning across the whole port. At one terminal, the value is the alert: somebody learns of the situation while it is happening and gets there in time to stop it. In a port with several terminals something appears that one alone does not have, which is comparison against the same yardstick: the same rule, written the same, applied everywhere. Then you can see which quay racks up the most walks under a load, which has fixed it after a toolbox talk and which one is worth a visit. Today that is decided on the gut feeling of whoever walks the most quays. With the figures in front of you it is decided better, and it can be explained. Starting with one terminal, seeing what comes out and deciding afterwards is the normal thing.

It costs according to how many cameras are analysed, what each one is asked for, where the video is processed and whether the hardware is yours or ours. We do not publish a price list because it would not be honest: a terminal with twelve cameras on the gate and the quay is not the same project as a port with several concessions. What you can do is start small: a couple of points at one terminal, the two or three rules that really matter there, and look at the alerts with your quay supervisors before deciding anything. Tell us how many cameras you have and what you want to detect on each, and we will give you a figure. The number is +34 902 02 70 91.

No, IRIS does not identify your customers and does not recognise faces. It compares no face against any list or any database, it builds no profile of anyone, and it is not cross-referenced with your customer systems. What it sees are facts: two bodies through a door on a single release, someone who stays put in the ATM lobby, a package that does not move. Each fact arrives with its camera and its minute. The person who looks at that and decides what it means works for you, always.

No, this does not detect a robbery before it happens, and we would rather say so before it comes up in a meeting. IRIS does not guess anyone’s intent and does not predict what a person is about to do; anyone promising you that is selling smoke. What it does see are checkable facts, while they are happening: someone coming in with a helmet on and the visor down, a large package that comes in and stays put, a strongroom door that has been open for twenty minutes. That arrives with the camera and the minute, and a person decides.

Yes, IRIS works with the cameras the branches already have. It connects to the feed of the installed IP cameras and analyses it as it comes: what changes is not the kit, it is what gets understood from the picture. And we will say it plainly: mid-afternoon glare through the shop window and an ATM lobby in the dark ruin any image, ours included. So we check camera by camera whether the framing is good enough for what you want to see there, and tell you which ones fall short and which would only need moving a few degrees.

The video leaves the branch or stays inside depending on the mode you choose, and there are two modes. In the local one it does not leave: the servers sit on your premises — in the branch or in your own data centre — the video comes in over your network, it is analysed right there, and the system needs no internet to work. In the other it is processed in our data centre, which is our own cloud and not a third party’s, encrypted and on the terms set out in the contract. Across a branch network it is worth deciding early, because it shapes each site’s network.

Data protection is handled by configuring the processing piece by piece: what is kept, for how long, who can access it and from where. And on top of all that sits what matters most in a branch: IRIS identifies nobody, so there are no identities to protect and no customer profiles to build. Compliance, mind you, does not depend on the software alone: it also depends on how you deploy it and what you decide to process, and that is signed off by your organisation, not by us. What we can put on the table is that our way of working is certified for information security and for privacy by an external auditing body. That paper is not signed by a salesperson: it is signed by an auditor, and you can ask us for it before you sign anything.

No, IRIS does not replace the monitored alarm, the guards or the access control: it lives alongside all three and changes what they look at. The alarm keeps doing its job and access control keeps deciding who opens a door. What you are missing today is the layer that understands the picture: that the door released once and two people went through, that it has been open for twenty minutes, that the cash room has one person on an operation that calls for two. No card reader sees that, because a reader counts releases, not bodies.

Yes, this helps find the moment behind a complaint from two weeks ago, and that is one of the things that gives the most time back. Today someone sits down and works through hours of recording looking for four minutes. With IRIS you describe in one sentence what you are after — a person on the floor by the entrance, a package that stays put in the lobby — and the sequence comes up, with its camera and its minute. And the other half is worth saying: that same sequence works just as well to back the person who served as to contradict them. That is exactly what makes it worth anything as evidence.

You will get the alerts your rule asks for, and tuning that rule is the work of the first month. A rule is never «alert if someone is in the ATM lobby». It is «alert if someone has been in the lobby for more than so many minutes, outside branch hours». You bound the zone on the image, the time band, how long the situation has to last and who it reaches. And the alert goes to someone who can act — the branch manager, the control room, the phone of whoever is on shift — not to a screen nobody watches. An alert nobody attends to is a badly configured alert, and that gets fixed.

Yes, the same rule can be applied across hundreds of branches, and that is where this stops being a single-branch tool. In one branch the value is the alert: someone finds out while it is happening. Across a network something appears that one branch cannot have, which is comparison by the same yardstick: the same rule, written the same, measured the same everywhere. Then you can see which branches pile up doors left open, which one queues at the same hour every day and which one is worth a visit. And you do not have to start with all of them: you start with a few and decide afterwards.

The cost is worked out from how many cameras are analysed, what is detected or measured on each, how many branches are involved, which deployment mode you choose and whether the hardware is yours or ours. We publish no price list because it would not be honest: one branch with six cameras and three rules and a network of three hundred are not the same project. What you can do is start small: a few branches, the rules that genuinely matter there, and look at the alerts and the figures with your team before deciding anything. The number is +34 902 02 70 91.

Yes, it works with the cameras you already have over the tables. IRIS connects to the feed of the installed IP cameras and analyses it as it arrives: what changes is not the equipment, it is what gets understood from the picture. During the project we check camera by camera whether the framing is good enough for what you want to see there — a camera placed to cover the aisle may not reach the baize — and we tell you plainly which ones fall short and which would only need turning a few degrees. Fitting a new camera is the exception, not the starting point.

No, IRIS does not recognise faces, does not enforce self-exclusion and does not spot minors. It identifies nobody: it compares no face against any database, keeps no record of who anyone is, does not follow a player around the floor and is not cross-referenced with your loyalty programme. And here is the line, said before you have to ask: self-exclusion and age control require knowing who a specific person is, and that can only be done with a legal basis and an authorised identification system. That is not IRIS, and we are not going to sell it to you as if it were. What IRIS sees is a table, a queue, a machine, a situation and how long it has been there.

The video leaves the premises or stays inside depending on the deployment you choose, and there are two. In the on-site mode it does not leave: the servers sit in your building, the video comes in over your network, it is analysed in there, and the system does not need internet to work. In the other one it is processed in our data centre, which is our cloud and not somebody else’s. In both, communications are encrypted and the terms are set in the contract. In a gaming venue it is usual to keep everything around the cage and the count room inside, and decide the rest calmly.

Finding a hand from two hours ago stops being an afternoon in the recording room. Today somebody goes down, picks four cameras and rewinds. With IRIS you describe in one sentence what can be seen — which table, roughly what time, what happened — and you land on the minute. What you get is the camera, the time and the clip as it is: nothing is retouched and nothing is hidden. And there IRIS stops. A person draws the conclusion, the venue settles the claim, and what counts for compliance or for the regulator is set by your procedure and by whoever has to approve it. We do not sign that for you.

The floor numbers are reliable because they are not set up by talking, they are set up by drawing. Asking is for searching; counting is for measuring, and they are not done the same way. A line cannot be described in a sentence: it has to be drawn on the image. You draw a line across the threshold or a zone over the baize, and from then on the figure is worked out the same way every day, it can be repeated and it can be audited. That is how you measure how long people stand waiting for a seat, how long a hand lasts or how long the cage takes. And on people counting you do not have to take our word for it: it is certified by the Spanish Metrology Centre, an independent third party. To be precise: that certification covers people counting, not the whole product.

You will get the alerts you decide on, because a rule is bounded: area, time slot and duration. A system that throws out two hundred alerts a shift is switched off within a week, and rightly so: when everything alerts, nothing alerts. That is why a rule is not «tell me if there are people standing by a table», but «tell me if three or more people are standing by this table for more than four minutes while another one is open and empty». By changing the area, the time slot and the minimum duration, the same detector goes from firing a hundred times to firing when it really matters. And it is tuned afterwards, with what comes out of your floor in the first two weeks, not with what happens in general.

The venue decides, not IRIS. Which table, at what time, how many people and for how long: your team writes that, and it ends up as a sentence anyone can read and anyone can change. IRIS applies what it has been told, always the same way and without getting tired. It brings no factory list of behaviours and does not decide on its own what is normal on your baize: what is normal in one room is not normal in another, and the people who work there know it. If tomorrow you change the opening hours, close a table or open a new area, the rule is rewritten in a few minutes and nothing has to be ordered. And since it is written as a sentence, you can show it exactly as it is to compliance, to the committee or to anyone who asks what that camera is watching.

What IRIS does not see is real, and it is worth saying before anything gets signed. A camera only understands what falls inside its frame: a hand covers some chips, one body hides another, and a full table hides half the surface. In the low light of a gaming room it sees worse, and with a dirty lens too. And some movements look very much alike: picking up a chip and moving a chip look the same for a second. That is why an alert is always closed by a person watching the video, and why IRIS judges nobody’s intent and never says who cheated. IRIS is not infallible and we are not going to sell it to you as if it were. It is a system that watches, every hour, the cameras nobody is watching right now.

How long it takes depends on the size of the installation, and we are not going to give you a date we cannot yet control. The work has three clear phases: connecting the cameras that already exist, drawing the zones on each image and writing the rules that matter, and tuning those rules against what actually happens on your floor. The first detections show up early; the fine tuning takes longer. Specific dates go in the proposal, once we know how many cameras there are and what you want to see on each one.

The cost is worked out from how many cameras are analysed, what is detected or measured on each one, which deployment mode you choose and whether the hardware is yours or ours. We do not publish a single price list because it would not be honest: twelve cameras over tables and the cage is not the same project as a whole venue with its entrances, service corridors and count room. And you can start small: a few tables and the cage, the three rules that really matter there, and see the alerts and the figures with your team before deciding anything. Tell us how many cameras you have and what you want to see, and we will give you a figure. The number is +34 902 02 70 91.

Yes, it works with the cameras the centre already has. IRIS connects to the feed of the installed IP cameras and analyses it as it arrives: what changes is not the equipment, it is what gets understood from the picture. During the project we go camera by camera to see whether the framing is enough for what you want to measure there — a camera hung to watch an entrance may not reach far enough to count in the corridor at the back — and we tell you plainly which ones fall short and which only need turning a few degrees. Adding a new camera is the exception, not the starting point.

No, IRIS does not identify visitors and does not recognise faces. It compares them against no database, keeps nobody’s identity, does not follow a person from one shop to the next and is not crossed with any loyalty programme. A counted person is a one: nothing else of them is kept. And because this comes up in every meeting, we say it plainly about the lost child: IRIS can flag that a child is alone in an area, but it does not search for a child by their face and does not know who they are. What it does is narrow down cameras and minutes so a person can look, and it is that person who finds them.

The video leaves the centre or stays inside depending on the mode you choose, and there are two. In the on-site mode it does not leave: the servers sit in your building, the video comes in over your network, it is analysed in there, and the system does not need internet to work. In the other one it is processed in our data centre, which is our cloud and not somebody else’s. In both, the links are encrypted and the terms are set in the contract. It is worth deciding early, because putting a server in the building is not the same as taking the analysis outside: it shapes the centre’s network.

The difference is that the counter at the door says how many people came, and this says what happened inside: which entrance they came through, which floors they stayed on, which corridors they avoided and what changed the day you launched the campaign. And there are two ways of asking for things, because they are two different things. What is watched is described by speaking: one sentence, and IRIS warns you when it happens. What is measured is drawn: a line across the threshold, a zone on the floor. A line does not fit in a sentence, you have to trace it, and that is why the number is worked out the same way every day, can be repeated and can be audited. On people counting you do not have to take our word for it: our system is certified by the Spanish Metrology Centre, an independent third party. To be precise: that certification covers people counting, not the whole product.

Yes, you can hand those numbers to your tenants, and it is one of the reasons the system gets installed: they are anonymous, aggregated figures, so they are shared without passing on anybody’s data. How many people walk past each unit, at what time, and which entrance they came from. What is not here is the sale: that sits in the tenant’s till and we do not go there. But putting the two halves together changes the diagnosis: if plenty of people walk past and almost nobody comes in, the problem is the shopfront or the sign. If nobody walks past, the problem is the corridor and not the shop. Today those two situations look the same in the report — it sold little — and they are two different problems with two different fixes.

You are going to get the alerts you decide on, because a rule is narrowed down: area, time band and duration. A system that fires two hundred times a day is switched off within a week, and rightly so: when everything alerts, nothing does. That is why a rule is not «tell me if someone is standing on the escalator», but «tell me if someone is standing at the foot of this escalator for more than a minute, between ten and half past ten». Change the area, the band and the minimum time, and the same detector goes from ringing a hundred times a day to ringing when it really matters. And it is tuned afterwards, with whatever comes out in the first two weeks in your centre, not in some centre in general.

The centre decides, not IRIS. A rule is written as one sentence anyone can read and anyone can change; a measurement is drawn on the image, as a line or a zone. IRIS applies what you told it, always the same way and without getting tired. It brings no factory list of behaviours and does not decide on its own what is normal in your corridor: normal in a neighbourhood centre is not normal in a three-floor one with a food court, and the people who work there know it. If the opening hours change tomorrow, a unit closes or the seasonal campaign goes up in the atrium, the rule is rewritten in a few minutes and nothing has to be ordered.

On a busy Saturday afternoon IRIS stops telling one person from another when they cover each other up, and we would rather say so before anything is signed. It happens to every vision system, ours included, and anyone who says otherwise has not tried it with the centre full. What is not lost is exactly what is needed most at that moment: occupancy. Measuring how many people are in an area and how they spread across the floors does not require telling each person apart. What does degrade is counting one by one in a narrow, heavily loaded passage; there the count is moved to the entrance, where people go through in single file. And whatever happens outside the frame, behind a column or in an area with no camera, nobody sees: IRIS neither.

How long it takes depends on the size of the centre, and we are not going to give you a date we do not yet control. The work has three clear phases: connecting the cameras that already exist, drawing the zones on each image and writing the rules that matter, and tuning those rules against what actually happens in the centre. The first measurements and the first alerts show up early; the fine tuning takes longer, because a quiet day, a Saturday and a campaign day all have to go by. Specific dates go in the proposal, once we know how many cameras there are and what you want to measure on each one.

The cost is worked out from how many cameras are analysed, what is measured or detected on each one, which deployment mode you choose and whether the hardware is yours or ours. There is no single price list that fits everyone, because measuring two entrances and one floor does not cost the same as covering three floors, the food court and the car park ramps. And you can start small: the entrances and one floor, look at the numbers with your team, and decide afterwards. Tell us how many cameras you have and what you want to measure, and we will give you a figure. The number is +34 902 02 70 91.

Yes, it works with the cameras the terminal already has. IRIS connects to the feed of the IP cameras that are already installed and analyses it as it arrives: what changes is not the equipment, it is what gets understood from the picture. During the project we check camera by camera whether the framing is good enough for what you want to measure there — a camera set up to cover the whole hall may not reach far enough to count the mouth of a queue — and we tell you plainly which ones fall short and which would only need turning a few degrees. Adding a new camera is the exception, not the starting point.

No, IRIS does not identify passengers and does not recognise faces. It compares them against no database, keeps no record of who anyone is, does not follow a person through the terminal and is not cross-referenced with any passenger list or boarding pass. And it is worth saying where the line runs: IRIS does no document control, verifies no documents, replaces neither the scanner nor the officer and touches none of the airport security systems. What it does is measure flows and report operational facts: a queue growing, a desk open and empty, a belt at a standstill. A counted passenger is a one: nothing else of them is kept.

The video leaves the airport or stays inside depending on the deployment you choose, and there are two of them. In the on-site mode it does not leave: the servers sit in your own facilities, the video comes in over your network, is analysed in there, and the system does not need internet to work. In the other one it is processed in our data centre — which is our cloud, not somebody else’s — and then it does leave, encrypted and under the terms set in the contract. At an airport the usual thing is to mix the two: the sensitive stays in, the rest goes out.

The security queue wait is a reliable number because it is not set up by talking, it is set up by drawing: a line at the mouth of the queue, another at the point where people pass through, an area on the floor. A line does not fit in a sentence, you have to trace it, and that is why the figure comes out the same way every day, can be repeated, compared week to week and audited. And it is not only the wait that gets measured: also how many desks were open while people waited, which is the missing half of the explanation for opening another one. On people counting you do not have to take our word for it: it is certified by the Spanish Metrology Centre, an independent third party. To be precise: that certification covers people counting, not the whole product.

IRIS detects abandoned luggage in the literal sense of what a camera sees: an object that has been on the floor for a while with nobody beside it, inside an area you drew and for a length of time you set. That is all it knows. It does not say whose it is, does not say what is inside, looks for nobody and decides nothing: the alert arrives with the camera, the time and the video, and who decides what to do is the person on duty, with the airport protocol in front of them. And this has to be said before anyone signs: in a crowded hall an object can be hidden by the people walking past, and then the camera does not see it.

You will get the alerts you decide on, because a rule is bounded: area, time band and duration. A system that fires two hundred times a shift is switched off within a week, and rightly so: when everything alerts, nothing does. That is why a rule is not «tell me if there is a queue» but «tell me if this queue goes over twenty minutes between six and nine». By changing the area, the time band and the minimum duration, the same detector goes from ringing all day to ringing when it really matters. And it is adjusted afterwards, with what came out in the first two weeks in your terminal, not in a generic one.

The airport decides, not IRIS. What is watched is written by talking: a sentence anyone can read and anyone can change. What is measured is drawn: a line on the floor, an area over a hall. They are two different things and they are not set up the same way, which is why both have to be decided. IRIS ships with no list of behaviours and does not decide what is normal in your hall at six in the morning: the person who has worked there for twenty years knows that. And if a night flight moves, a corridor closes for works or a new gate opens, the rule is rewritten in a few minutes and nothing has to be ordered.

What IRIS does not see is real, and it is better said before anything gets signed. A camera only understands what falls inside its frame: with the hall full, some people block others and it stops telling them apart one by one. That happens to any vision system, ours included, and anyone who says otherwise has not tried it on a Sunday afternoon. What is not lost is occupancy, which is exactly what is needed most when it is full: measuring how many people are in an area does not require telling each person apart. What does degrade is counting one by one in a narrow, heavily loaded passage, and there the counting is moved to where people walk in single file. Against the backlight of a big glass front, with a dirty lens or a badly aimed camera, it sees worse. And where there is no camera, it sees nothing.

How long it takes depends on the size of the installation, and we are not going to give you a date we cannot yet control. The work has three clear phases: connecting the cameras that already exist, drawing on each image the areas to be measured and writing the rules to be watched, and tuning those rules against what actually happens in the terminal at six in the morning and at eleven at night, which look nothing alike. The first measurements and the first detections show up early; the fine tuning takes longer. Specific dates go in the proposal, once we know how many cameras there are and what you want to see on each one.

The cost is worked out from how many cameras are analysed, what is measured or detected on each one, which deployment mode you choose and whether the hardware is yours or ours. There is no single price list, because measuring the security filter and the baggage reclaim hall does not cost the same as covering a whole terminal with its shops, its corridors and its basement. And you can start small: the filter and the baggage hall, look at the numbers with your own team and decide afterwards. Tell us how many cameras you have and what you want to see, and we will give you a figure. The number is +34 902 02 70 91.

Yes, it works with the cameras you already have up, and that is exactly the point: a territory is not short of cameras, it is short of someone watching them around the clock. IRIS analyses the feed of the IP cameras that already exist; what changes is not the sensor, it is what gets understood from the picture. What does shape the result is where each one is mounted and what can be seen from there: a camera placed so the whole access fits in frame gives less than one pointed straight at the spot that matters to you. Before promising anything we would rather look at real images from your cameras and tell you which ones this makes sense on and which ones it does not. Sometimes the answer is to move a camera two metres, and that is cheaper than buying anything.

No, IRIS does not identify people, does not recognise faces and does not follow anyone across the territory, and that has to be said plainly. It compares no face against any database, keeps no record of who anyone is and holds a file on nobody. Nor does it predict, score anyone, classify anyone by their behaviour, or read anyone’s intentions or mood. What it detects are facts defined by the authority itself: a vehicle stopped where stopping is not allowed, a blocked exit, smoke rising from the hillside, a stain spreading on the water, a crowd that keeps growing. What is happening, where, and since when: that is everything the alert carries. And on number plates, the honest answer: IRIS can read plates when the camera is installed for that and whoever operates it has a legal basis to do so, but that is another camera and another decision, and it is not what the cameras on this page do.

The video leaves your premises only if you want it to, and in this sector the norm is that it does not. In the on-site mode the servers sit in your building, the video comes in over your network, is analysed in there, and the system does not need internet to work: if the line drops, the analysis carries on. In the other mode it is processed in our data centre — which is our cloud, not somebody else’s — encrypted and under the terms signed in the contract. Either way, an alert always keeps the same things: the camera, the time, the fact detected and the clip of video, so the report can later rest on more than a memory.

An IRIS alert brings a time-stamped fact with its video, no more and no less: it does not retouch the image, hides nothing and does not interpret what can be seen. Whether that fact counts as evidence is decided by the procedure that applies and by whoever has to weigh it up — not by us and not by a salesperson of ours. What we can tell you is what makes that sequence useful: it is exactly the same for both sides. It works just as well to back up whoever acted as to contradict them, which is why it is worth having before anyone needs it. Seeing a fact is not accusing anyone.

Where a camera does not go is worth answering before anyone asks: nothing is watched inside a home, in a changing room, in a toilet, or in an office where someone is being attended to. And in public space, where there is a camera and where there is not is decided by the authority, with its legal framework, its lawyers and whatever public notice applies. That is signed by whoever installs it, not by us; be wary of anyone who tells you otherwise. What does depend on the software is that the processing is configurable piece by piece: what is kept, for how long, who can access it and from where. And that our way of working is certified for information security and for privacy by an external auditing body. That paper is not signed by a salesperson: it is signed by an auditor, and you can ask us for it before you sign anything.

The control room will get the alerts you decide on, because a rule is bounded: area, time window and duration. A system that throws two hundred alerts a shift is switched off within a week, and rightly so: when everything alerts, nothing does. That is why a rule is never “tell me if a vehicle is stopped”, but “tell me if a vehicle is stopped on this hard shoulder, between ten at night and six in the morning, for more than three minutes”. Change the area, the window and the minimum time, and the same detector goes from firing a hundred times a day to firing when it really matters. And it is tuned afterwards, with what actually came out in the first two weeks in your territory and not in somebody else’s.

The authority decides, not IRIS. Which area, at what time, for how long and under what conditions: that is written by whoever operates the system, and it stays written as a sentence anyone can read and anyone can change. IRIS applies what it has been told, always the same way and without getting tired. It ships with no list of behaviours and does not decide on its own what is normal in your territory: what is normal on a stretch of coast is not what is normal on an industrial estate, and the people who work there know that. If tomorrow a lane closes, an access opens or the hours of a crossing point change, the rule is rewritten in a short while and nothing has to be ordered. And because it is written as a sentence, it can be shown exactly as it is to anyone who asks what that camera is actually watching.

What IRIS does not see is real, and it is worth saying before anything is signed. A camera only understands what falls inside its frame: if something happens off camera, behind a wall, between two vehicles or in an area with no camera at all, IRIS does not see it — just as a person watching that same screen would not. At night, in fog, in heavy rain or with a dirty lens it sees worse, and on a hillside against the light at dawn it sees worse still. And some situations look a great deal like others: dust thrown up by a lorry and smoke can be confused for a few seconds, which is why an alert is always closed by a person looking at the video. Detecting is not deciding. IRIS is not infallible and we are not going to sell it to you as if it were: it is a system that watches, at every hour, the cameras nobody is watching right now.

How long it takes depends on the size of the deployment, and we are not going to give you a date we do not yet control. The work has three clear phases: connecting the cameras that already exist, drawing the areas on each image and writing the rules that matter at that spot, and tuning those rules against what actually happens. The first detections show up early; the fine tuning takes longer, because it depends on what happens in front of those cameras and not on us. Specific dates go in the proposal, once we know how many cameras there are and what you want to detect on each one.

The cost is worked out from how many cameras are analysed, what each one is asked to do, which deployment mode you choose and whether the hardware is yours or ours. We do not publish a price list because it would not be honest: a stretch of coast with twelve cameras and three rules is not the same project as a whole territory with hundreds. What can be done is to start small: one access point, one stretch of hill road, the two or three rules that really matter there, and see the alerts with your own team before deciding anything. Tell us how many cameras you have and what you want to detect, and we will give you a figure. The number is +34 902 02 70 91.

Yes, it works with the cameras you already have in the centre. IRIS connects to the feed of the IP cameras that are already installed and analyses it exactly as it arrives: what changes is not the equipment, it is what gets understood from the picture. During the project we look camera by camera at whether the framing is good enough for what you want to see there — a camera placed to cover a whole aisle may not reach far enough to tell whether a rack was left open — and we tell you plainly which ones fall short and which would only need turning a few degrees. Adding a new camera is the exception, not the starting point.

No, IRIS does not identify staff and does not recognise faces. It compares no face against any database, keeps no record of who anyone is and does not follow a person around the centre. We say this inwards too, because it is the first thing the staff representatives ask: this is not for checking anyone’s hours, or measuring one person’s performance, or knowing how long somebody stood in an aisle. What it sees is «there is one person», «there are two», «this door has been open this long», «this rack is open with nobody in front of it». The name, if you need one, comes afterwards from your access control, and that cross-check is your decision.

The video leaves the centre or stays inside depending on the deployment you choose, and there are two. In the on-site mode it does not leave: the servers sit in your own facilities, the video comes in over your network, it is analysed in there and the system does not need internet to work. In the other one it is processed in our data centre — our cloud, not somebody else’s — encrypted and under the terms set in the contract. In this sector staying inside is the usual choice, and that is fine by us: it is your decision, not a condition of ours.

IRIS detects that two people went through that door, and at what time. What it does not know is how many authorisations there were: that lives in your access control, not in the picture. Your system does the cross-check using the fact the camera supplies — two bodies and a single authorised entry, or a technician in an aisle that is not the one on the work order — and that is where an ordinary walk-through turns into a problem. The split is deliberate: the camera supplies the fact, the meaning comes from whoever holds the rest of the information. And the fact is kept with its camera, its time and its clip of video, which is exactly what you need the day you have to reconstruct what happened or show it to whoever comes to audit.

Yes, IRIS alerts on water on the raised floor, on smoke in an aisle and on a door wedged open, and also on a rack left open or a tool forgotten inside the room. Now the limit, because it matters: this does not replace fire detection, water sensors or plant monitoring. Those systems have their own regulations and their own maintenance, and they stay exactly where they are. What the camera adds is something else: it reaches places where there is no sensor, and it shows the picture of the moment, so the person on duty can see what it is without having to walk down and look.

You will get the alerts you decide on, because a rule is bounded: which door, which time band and for how long. A system that fires two hundred alerts a shift is switched off within a week, and rightly so: when everything alerts, nothing does. That is why a rule is never «tell me if this door opens», but «tell me if this door has been open for more than two minutes outside maintenance hours». By changing the zone, the time band and the minimum duration, the same detector goes from ringing all day to ringing when it actually matters. And it is tuned afterwards with what comes out in the first couple of weeks in your centre, not in general.

The centre decides, not IRIS. Which door, at what time, how many people and for how long: your team writes that, and it stays written in a sentence anyone can read and anyone can change. IRIS applies what it has been told, the same way every time and without getting tired. It ships with no list of behaviours and does not decide on its own what is normal in your aisles: what is normal in an operations room is not what is normal on a loading dock, and the people who work there know that. If a procedure changes tomorrow, a new room opens or an aisle is closed for works, the rule is rewritten in a few minutes and nothing has to be ordered.

What IRIS does not see is real, and it is better said before anything is signed. A camera only understands what falls inside its frame: a rack hides what is behind it, one body hides another, and in a narrow aisle the angle leaves blind spots. With little light, a dirty lens or harsh light straight into it, it sees worse. And some situations look a lot like each other: somebody leaning on a door and somebody wedging it open can be confused for a second. That is why a person always closes the alert after looking at the video. IRIS is not infallible and we are not going to sell it to you as if it were. It is a system that watches, at every hour, the cameras nobody is watching right now.

How long it takes depends on the size of the installation, and we are not going to give you a date we cannot yet control. The work has three clear phases: connecting the cameras that already exist, drawing the zones on each image and writing the rules that matter — this door, this aisle, this rack — and tuning those rules against what actually happens on your shifts. The first detections show up early; the fine tuning takes longer. Specific dates go in the proposal, once we know how many cameras there are, which rooms are included and what you want to detect on each one.

The cost is worked out from how many cameras are analysed, what each one is asked to do, which deployment mode you choose and whether the hardware is yours or ours. We do not publish a single price list because it would not be honest: covering the entry airlock and the loading dock does not cost the same as putting rules on every aisle of every room. And you can start small: the critical access points, the two or three rules that really matter there, and see the alerts with your own team before deciding anything else. Tell us how many cameras you have and what you want to see, and we will give you a figure. The number is +34 902 02 70 91.

With the ones you already have, whoever made them. IRIS asks the camera nothing and does not depend on it being able to report that it is broken: it looks at the picture that arrives, the same way it looks at a person or a lorry. A twelve-year-old camera produces a picture, and that is enough. Nothing to replace, no extra box, no new cable.

No, and that is precisely the design. Everything carries its own threshold and its own time: a raindrop has to stay a good while, dirt has to get worse over several days, the framing has to have really changed and not just caught a gust of wind. Only three things alert immediately: the camera being covered, being turned, or losing the stream. Everything else interrupts nobody — it waits for the day’s report.

Because it keeps a record. On day one IRIS notes how that camera looks when it is fine — its framing, its sharpness, its colour, how much light it gives at night — and that becomes its reference. It belongs to that camera and no other: one on the loading dock and one in a lobby have nothing in common, and comparing them would say nothing. From then on it compares each day against its own reference, not against an ideal.

You decide. You schedule an audit — every day, every Sunday, the first of every month — and at the appointed hour IRIS looks at every camera in the installation one by one, without anybody having to ask and whoever happens to be at the screen. When it finishes there is a report of which are fine, which have got worse and which cannot see, each with its image and its time. It exports to a spreadsheet.

No. The IRIS licence is per camera, not per question. Asking it to alert you when somebody falls and asking it whether that same camera is dirty cost exactly the same, because what you pay for is the camera. There is no separate maintenance module and no price per thing you want to watch: if the camera is already in IRIS, you already have this.

Somebody has to climb, and IRIS does not pretend otherwise: it repairs nothing, reboots nothing and cleans no domes. What it does is let whoever climbs go up knowing what for, and in the right order. The difference is not small: you go from a calendar round — walking four hundred cameras because it is that time of year — to a list of the eleven that actually have something, with the picture in front of you. And some of those eleven get sorted from the ground.