Questions, answered.

Most tools stop at the alert. Camnitive detects forklift near-misses, blocked exits and dock exceptions, measures them, scores them against your packs and seals them as evidence. Then it shows what to change next.

No. FloFrame works with the RTSP and ONVIF cameras you already own, mixed brands included. Each site adds one FloFrame box with an NVIDIA GPU.

A pilot of 10–50 cameras usually goes live in days. People, forklifts, PPE, spills and blocked exits are standard detections, so there is no training on your footage.

On your sites. FloFrame processes video where it is recorded; only alerts, chosen evidence and measurements leave. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

Forklift and pedestrian proximity, blocked exits and aisle safety to detect; dock dwell and congestion to measure. Packs score the safety side, and the trends point to the layout or shift change worth making.

Yes. FloFusion policies are versioned and roll out to a pilot site first, then the network, with zones adjusted per layout. Every site reports against the same standard.

Scores and sealed evidence per site, shift and zone become proof of duty of care. Share scores with a client by consent, or give an insurer a link to the signed record.

Detection, rules and outputs on site keep running. Alerts wait on the device and go up when the link returns, over outbound HTTPS on port 443.

Yes, that is the default. FloFrame processes video inside the estate; only alerts and sealed evidence go to FloFusion, over outbound HTTPS. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

The detections are built for outdoor industrial CCTV. During the pilot we tune zones, thresholds and cooldowns against your real lighting, weather and container shadows before scaling.

Perimeter, restricted-area and access events are recorded with sealed, time-stamped evidence. That gives ISPS reviews and port-authority reports a continuous record instead of a logbook.

Yes. The cameras that watch safety at the gates also measure queues, turn time and gate flow in Insights.

Quay and yard proximity, restricted berth zones and PPE at the riskiest points. Then gate flow, container dwell and perimeter security on the same cameras.

Barely. FloFrame reads existing camera streams, so there is no crane downtime and no new cabling on the quay. Zones and rules change in minutes as operations do.

The pilot covers depots, yards and gates on the fixed cameras you already own. In-cab driver safety comes with FloFleet, on the same platform.

Every yard incident, near-miss and gate event is sealed with its clip, so disputes are settled on facts. Insurers see measured trends, not promises.

Yes. Bay rules cover dwell time, unsafe loading and walkway discipline, so operations get throughput data from the same cameras.

Yes. Every rule takes schedules and shift windows: peak-hour yard rules, maintenance windows and after-hours security, changed in minutes.

At each depot. FloFrame processes video locally and sends only alerts, chosen evidence and measurements. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

10–50 cameras at one depot, covering crossings, bays, gates and walkways. It is measured on conflict reduction and evidence quality, then rolled out with the same policies.

No. Camnitive works with the RTSP and ONVIF cameras you already own and runs alongside your current VMS or NVR. Each site adds one FloFrame box: an x86 server with an NVIDIA GPU.

A pilot of 10–50 cameras usually goes live in days. People, vehicles, PPE, line stoppages, fire and smoke are standard detections, so there is no training data to collect. You set the rules, and they run from day one.

Yes. Rules are set per camera and per zone, with their own thresholds, cooldowns and shift schedules. PPE, restricted-zone and packaging rules can differ by line.

Zones, schedules and minimum durations decide what fires. A vision-language model then checks each alert, and your team marks it valid, false positive, invalid or repeated, so the noise is measured and tuned out.

Every alert is sealed on the device and verified when it reaches FloFusion. Regulation packs score your clauses continuously, and each score is a signed, hash-chained snapshot anyone can verify. You share a link to the record instead of a binder.

Yes. Video is processed on site and stays there. FloFrame only connects out, over HTTPS on port 443, so no inbound ports or VPN are needed. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

Detect PPE, restricted-zone entries and line stoppages on a few lines. Then measure stoppage time and repeat zones in Insights, score them in a pack such as ISO 45001, and use the trends to decide what to fix next.

You bring measured trends and sealed evidence to insurer reviews and audits, instead of self-reported checklists. Lower incident rates are a pilot target, set with you before it starts.

Yes. FloFrame drives outputs on site: HTTP relays, Modbus TCP, ONVIF relays and MQTT, for a beacon, a horn or a PLC signal. It is an aid next to your certified safety systems, never a replacement.

No. Camnitive is an aid next to certified safety systems. It covers gaps in guarding, records what happened, and can drive a relay, Modbus TCP or MQTT signal as an extra warning.

Line stoppage is a standard detection. A station left without an operator past its takt time, or a conveyor that goes still, raises an alert with the clip, and Insights measures the lost time.

Posture rules run on marked steps and ladders. We check them on your own cameras during the pilot before they go into routine use.

Yes. FloFusion groups sites by organisation and region, and Insights and Control Tower compare them on the same measures.

Packs score your clauses continuously, and each score is a signed, hash-chained snapshot. Share a link with an auditor, or share scores with a buyer by consent. Links carry records, not video.

No. It works with your existing RTSP or ONVIF cameras. People, vehicles, PPE and line stoppages are standard detections, with no training on your site.

Yes. FloFrame sits beside your infrastructure without touching validated equipment. Rules are explicit and versioned, so your quality team can document exactly what fires and why.

Cameras at gowning areas check gowns, gloves, masks and goggles as people pass. Nothing blocks the door: an exception creates an alert with its clip.

Yes. Each alert is sealed on the device, verified on arrival, and carries its clip, rule and review. You can export it for CAPA, QA review and inspections.

No identification is involved: rules ask whether a person is gowned or a zone is over its limit, not who it is. Video is processed on site and stays inside your network.

Gowning at cleanroom entries and line clearance on one or two packaging lines. Then measure the trend, score it in a pack such as ISO 13485, and add zone occupancy and material flow on the same cameras.

The install takes days; change control takes most of the calendar. We provide the architecture, data flows and rule definitions your IT, QA and compliance teams need.

Evidence is sealed on the device and checked when it arrives. Compliance scores are signed, hash-chained snapshots, so anyone can verify that a record is unchanged.

Yes, where a camera sees the staging lane. Dwell rules time each load outside the cold room and alert past your limit. The site survey confirms which lanes can be timed reliably.

No. Rules apply to zones, not named people, and Camnitive identifies no one. New crews are covered from their first shift.

It works wherever your cameras give a usable picture. The FloFrame box sits in a plant room or office, not on the floor.

Yes. Rules flag entry to poultry houses, livestock sheds or chemical stores outside permitted hours, with the clip, so checks happen from the office.

No. FloFrame processes everything on site and keeps working offline. It needs only an outbound connection on port 443 to send alerts when the link is up.

Yes. FloFrame runs detection and rules on site and keeps working offline. Alerts go up to FloFusion when the link returns, over an outbound HTTPS connection on port 443.

No. Video is processed on site; only alerts, chosen evidence and measurements are sent. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

Restricted zones, PPE, smoke and fire, leaks and spills, blocked exits, perimeter intrusion and people near vehicles. All are standard detections on your existing fixed cameras.

Regulation packs score your clauses continuously from real events. Evidence is sealed on the device, and every score is a signed, hash-chained snapshot an auditor can verify without trusting us.

Each site gets a FloFrame box that enrols remotely with a code. Policies roll out from FloFusion to a pilot group first, then to every site, and updates install remotely with rollback.

Yes. FloFusion connects to ticketing, maintenance and incident tools through webhooks, integrations and automations. A leak can open a work order; a zone breach can start a permit review.

No. They are an aid next to your certified fire and gas systems, adding eyes where detectors are sparse and a clip with every alert.

It does not need to. The FloFrame box sits in a control or server room and reads the streams of your existing cameras, including certified cameras already in hazardous areas.

Yes. Smoke, flame, leaks and spills are standard detections on your existing cameras, alerting the control room with the clip. They are an aid next to your certified gas and fire systems.

Rules follow zones and time windows. Set the headcount and hours a permit allows, and Camnitive alerts when a zone has too many people or people outside the window.

Camnitive does not measure temperature or health. It times how long people stay in exposed zones during the hours you set, so supervisors can enforce your work-rest schedule.

FloFrame only connects out, over HTTPS on port 443, to FloFusion. Nothing crosses your perimeter inbound, and no VPN is needed. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

Examples include OSHA process-safety and PPE duties, the EU OSH Framework Directive and UK HSE expectations. Your HSE team decides which apply; where a pack covers them, Camnitive scores the clauses continuously with sealed evidence.

Your existing fixed cameras work, including those on haul roads, crushers and conveyors, as long as they stream RTSP or ONVIF. The only new hardware is a FloFrame box with an NVIDIA GPU in a site room.

No. Detection, rules and on-site outputs keep running offline. Alerts and evidence wait on the device and go up to FloFusion when the link returns.

Yes. Every rule takes schedules and site calendars, so an exclusion zone can be enforced during blast windows and relaxed for planned maintenance.

It adds the fixed-camera view: walkways, conveyors and interaction zones that vehicle-mounted systems cannot see. It is an aid next to your certified systems, and every event becomes sealed, reviewable evidence.

Each event has its clip, the rule that fired and its review, sealed on the device and verified on arrival. Pack scores are signed and hash-chained, so an investigator can check that nothing changed.

Nowhere. Video is processed on site and stays there; only alerts, chosen evidence and measurements leave. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

Its configuration is kept as a sealed backup, so a replacement box enrols remotely and picks up the same cameras, zones and rules. Updates also install remotely, with rollback.

It watches tipping floors, bunkers and piles for visible smoke and flame and alerts the control room with the clip, while suppression is still simple. It is an aid next to your certified fire detection.

Yes. FloFrame works on modest links and keeps running offline, sending alerts when the link returns. Camera and network health, with history, shows when a remote site needs a visit.

You draw separation zones and set minimum distances. Rules enforce them continuously, with schedules for receiving hours and cooldowns for busy periods.

Yes. After-hours and boundary rules flag dumping with sealed, time-stamped evidence you can use for enforcement and to show duty of care.

Records by site and period for fire watch, separation, PPE and environmental exceptions, each backed by sealed evidence. Pack scores are signed and hash-chained, so they can be verified.

No. Camnitive works with your existing RTSP or ONVIF cameras, including older ones at remote sites.

On a FloFrame box (an x86 server with an NVIDIA GPU) at the site or a nearby hub. Footage stays local; alerts and evidence go up over outbound HTTPS on port 443, and wait on the device if the link drops.

Rules fire only in the zones and hours you set, with minimum dwell times. A vision-language model checks each alert first, so the NOC sees fewer, better alerts.

Rules follow visit windows, and alerts carry people and vehicle counts. Camnitive does not identify anyone; it tells you someone is on site outside the window, with the clip.

Yes. Each alert is sealed on the device and verified on arrival, so you can show when the clip was recorded and that it has not changed. Bystanders are blurred on the copies you share.

Yes. Store cameras measure queues and wait times, and Insights compares stores side by side, in the same FloFusion organisation as your network sites.

No. Camnitive works with RTSP and ONVIF cameras, including the ones already on your masts and shelters. A site survey confirms coverage.

Yes, with a full on-premises deployment: FloFusion runs inside your network and FloFrame connects only to it, so video, events and metadata stay inside your boundary.

Badge logs show one credential per entry; cameras show how many people walked through. Tailgating is a standard detection at mantraps and secure doors, and each exception is sealed with its clip.

Yes. Escort rules check that visitors stay accompanied through defined zones, and every deviation is a sealed, time-stamped record.

FloFusion exports physical-access events, exceptions and perimeter alerts with their sealed evidence. Your team files them against your own controls instead of hunting for clips.

Very little. FloFrame processes streams on its own GPU; only small alert records and chosen evidence cross the network, outbound on port 443.

Tailgating at mantraps, escorts on visitor routes and perimeter intrusion: the controls auditors check first. Restricted aisles and maintenance safety usually follow.

Most customers start with the fixed cameras they already own at depots, yards and gates. In-cab driver safety comes with FloFleet.

A pilot of 10–50 cameras usually goes live in days. People, vehicles and PPE are standard detections, so there is no training data to collect.

Yes. Rules are set per site, zone and schedule, so gate, yard and dock rules can differ by location and between peak and after-hours.

Zones, minimum durations and cooldowns decide what fires. A vision-language model checks each alert, and your team marks it valid, false positive, invalid or repeated.

Time, camera, the rule that fired, the clip and the model check with its reason. It is sealed on the device and verified on arrival, so it holds up when someone asks for proof.

FloFrame detects on site, so alerts at crossings and conflict points arrive within seconds and can drive a light or horn on site. What it can catch depends on camera placement, and it is an aid next to certified safety systems.

On site. FloFrame processes video where it is recorded; only alerts, chosen evidence and measurements leave. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

Yes. The cameras that run safety rules at docks, gates and yards also measure dwell and turnaround, so the same deployment pays back in throughput.

Yes. Camnitive works with your existing RTSP or ONVIF station, platform and depot cameras. FloFrame processes video inside your network and only connects out.

Detection runs on site, so person-on-track and platform-edge alerts reach station control in seconds, with a frame attached so controllers can check before acting.

Yes. Rules take schedules and calendars: enforce track beds in service hours, relax them during authorised possessions, and change them in minutes.

Density rules run per platform and concourse zone, giving staff live occupancy and early warning. It is anonymous: no facial recognition.

Each event has its clip, rule and review, sealed on the device and verified on arrival. You can export it for investigations, regulator reports and police requests.

Yes. PPE checks and exclusion zones run on depot and worksite cameras during possessions, and every exception is recorded with evidence.

Yes. FloFrame processes video inside your network, and FloFusion can be deployed privately in your own data centre or cloud. FloFrame only ever connects out to FloFusion.

FOD is a standard detection on the cameras already covering stands and taxi-lane edges. Zones and size thresholds are tuned in the pilot, and each alert carries a frame so ops can check before sending a sweep.

No. Camnitive reads camera streams beside your VMS. FloFusion connects to your operations, safety-reporting and ticketing tools through webhooks and integrations.

Yes. Stand occupancy and turnaround milestones such as on-block, ground equipment arrival and pushback are measured from the same cameras, per stand.

Queue and flow analytics are anonymous. Facial recognition and biometric identification are not part of the platform.

Usually 20–50 cameras across a few stands, one checkpoint and key airside boundaries. It runs for a few weeks against criteria agreed up front: alert precision, time to awareness and evidence quality.

Yes. Zone occupancy and line counts update live, and rules alert when a zone passes your limit. The control room sees every zone in Control Tower.

No. Camnitive counts people anonymously; it does not use face recognition or biometrics.

No. It gives your safety officer live numbers and alerts to act on. Decisions stay with your team and your event safety plan.

Yes. Insights keeps arrival curves, peak density and queue times per event, so you can see whether a gate change made a difference.

Density and counts are measured per camera and zone, then combined across the venue. The pilot sizes the FloFrame hardware to your camera count.

No. Camnitive works with RTSP and ONVIF cameras, including the ones already covering your gates and concourses.

You choose where everything runs. FloFrame processes video in your jurisdiction, and FloFusion can be deployed privately inside your own infrastructure, so no video, events or metadata need to cross a border.

Density and flow analytics are aggregate and anonymous. Facial recognition and biometric identification are not part of the platform.

Yes. Policies are versioned and roll out to a pilot site first, then the network, with zones adjusted per site. Every site keeps the same evidence standard.

Each intrusion, vandalism or safety event is sealed on the device with its clip and verified on arrival. That record supports enforcement, claims and public reporting.

Rules on existing cameras flag debris, obstructions, leaks and spills on stations and public assets between inspections, so crews go where the evidence points.

2–3 representative sites and 20–50 cameras, measured over an agreed period on detection precision, evidence quality and data handling. Architecture documents come up front for security review.

No. Camnitive works with the RTSP and ONVIF cameras your stores already have. FloFrame detects on site, in the store or at a nearby hub.

Days. Rules for queues, footfall, store checks and after-hours intrusion are set once and applied across stores, with no model training.

Alerts stop at the event. Camnitive measures each one, compares stores in Insights, scores the checks that matter and keeps sealed evidence for auditors and insurers.

No. Facial recognition, biometrics and emotion recognition are not part of the platform. Footfall, queue and compliance analytics are anonymous.

In your stores. FloFrame processes video on site; only alerts, chosen evidence and measurements leave. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

Most retailers start with 10–50 cameras in a few stores. Then they add store operations, loss prevention and compliance packs across the estate, and use the measured trends to decide what to change.

Yes. After-hours intrusion, stockroom and till-area zone rules and delivery-door monitoring run on your existing cameras. Every event is sealed evidence for case files, and nothing identifies anyone.

A vision-language model checks each alert first. Your team then marks it valid, false positive, invalid or repeated, and those reviews show which rules need tuning.

Yes. Hair nets, gloves and aprons are standard checks in prep zones, by shift and station, alongside sequence rules such as handwash before prep. Exceptions come with a sealed clip.

Lines and zones in the lane track each vehicle from the order point to the window. Insights shows time per vehicle and queue length by daypart.

No. Rules apply to zones and sequences, not named people, and Camnitive does not use face recognition.

It gives you evidence: sealed records of exceptions and how they trend, scored in a pack where one fits. Your food-safety team decides how that fits your HACCP plan.

Small sites can stream to a FloFrame at a nearby hub where bandwidth allows, or share one box per cluster. Boxes enrol and update remotely, so no one visits each site.

No. Camnitive detects people anonymously; it does not recognise faces or identify anyone. Bystanders are blurred on evidence copies shared outside the security team.

A count rule watches the room while it is open. If one person is inside alone for more than a few seconds, it alerts with the clip and logs the event.

No. FloFrame processes video at the branch or a regional hub, and footage stays there. Only alerts and short evidence clips go to FloFusion, hosted by Camnitive or deployed privately in your own cloud or data centre.

Loitering rules use a minimum dwell time and run only in the zones and hours you set. A vision-language model checks each alert before it reaches security.

Yes. Camnitive applies your retention policy automatically, seals evidence on the device, and keeps signed, hash-chained score snapshots. Where card data is handled, sealed access records support PCI DSS physical-security reviews.

Yes. Insights and Control Tower compare wait times, occupancy and alerts by branch, and Home shows the network at a glance.

No. Camnitive runs on the cameras already installed, and nothing identifies guests: no facial recognition, no biometrics.

Rules check uniforms, hygiene wear and safe practice on existing kitchen cameras, by shift and station. Exceptions reach the F&B lead with a clip, and Insights shows the trend.

Falls in lobbies, pools and corridors raise an immediate alert, and each incident is sealed with its clip. Genuine claims resolve faster and false ones are easier to contest.

Policies roll out across properties, piloted first, with zones adjusted per property. FloFusion compares service levels, compliance and incidents property by property.

Video is processed on the property, and analytics count people without identifying them. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

Queues at the front desk and F&B, kitchen hygiene, and back-of-house security. Then housekeeping checks and portfolio views on the same cameras.

It counts, and more: the same cameras measure occupancy and time in use, run safety and security rules, and keep sealed evidence. No new hardware goes on the camera side.

No. Camnitive counts people anonymously and does not use face recognition. Bystanders are blurred on evidence copies.

Yes. Insights shows occupancy and amenity use by floor and hour, so space decisions rest on measured use.

Yes. FloFusion groups sites by organisation and region, and Insights and Home compare buildings on the same measures.

Nowhere. It stays on site; FloFrame sends only alerts and chosen evidence, outbound on port 443. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

Yes. Camnitive works with whatever RTSP or ONVIF cameras each building has, and FloFusion brings them into one view.

Perimeters, falls, after-hours presence, occupancy limits and exit routes are watched continuously. Every event is sealed evidence, so the care you deliver is on record.

Yes, every day, not just at inspection. Blocked exits and routes raise an alert with a clip for facilities to act on and auditors to see.

Occupancy and surge rules run per hall, giving security live density and early warning at peaks. It is anonymous: no facial recognition, no tracking of individuals.

Video is processed on site, analytics are anonymous, and biometric identification is not part of the platform. Access to evidence is role-based and logged.

Perimeter and after-hours rules, car-park safety and exit checks. Then occupancy and incident detection across halls and event spaces.

No. Camnitive detects people anonymously; it does not use face recognition or biometrics. Bystanders are blurred on evidence copies shared outside the security team.

Footage stays on site. Access to alerts and evidence is role-based, every view is logged, and retention follows your policy.

No. Camnitive does not offer weapons or violence detection. It covers entrances, perimeters, crowding, drop-off traffic and after-hours movement.

Yes. Speed and zone rules flag vehicles moving too fast in drop-off lanes and car parks, and Insights shows when and where.

It is built to support them: processing on site, no identification, purpose-limited rules, automatic retention and logged access. Your data-protection officer decides how each law applies.

Video is processed on site and stays there. There is no facial recognition or biometric identification; rules describe events, such as a fall or a zone entry, and access to evidence is role-based and logged.

Yes. Falls and man-down are standard detections on existing cameras, alerting the nearest nursing station or security desk in seconds. They are an aid next to your clinical systems, not a replacement.

Yes. Zone rules check what happens at the door and inside: tailgating, propped doors, entry outside hours and time spent inside. Each exception is sealed with its clip.

It is built to support them: processing on site, no identification, and FloFusion hosted by Camnitive or deployed privately in your own cloud or data centre. Your data-protection officer decides how each law applies.

Yes. Waiting-room occupancy and queues are measured anonymously on the same cameras, for staffing and flow decisions.

Falls in busy corridors and waiting areas, restricted zones on pharmacies and labs, and after-hours security. Waiting-room occupancy usually follows.

Yes. FloFrame runs on site, and FloFusion can be deployed privately in your own cloud or data centre. FloFrame only connects out to FloFusion, so nothing needs to reach the public internet.

Evidence is sealed on the device and checked when it arrives. Score snapshots are signed and hash-chained, so any change breaks the chain. Auditor links carry records, not video.

No. Camnitive detects people, vehicles and PPE; it does not use face recognition or biometrics. Bystanders are blurred on evidence copies.

Yes. Camnitive has SOC 2 Type I and SOC 2 Type II reports, is ISO/IEC 27001 certified and has completed an independent penetration test. We also share our architecture and data flows for your own review and accreditation. Ask us for the reports.

Yes. It works with RTSP and ONVIF cameras and runs alongside your existing VMS.

Updates install remotely, with rollback. Device configuration is kept as a sealed backup, so a replacement takes over the same cameras and rules.

Alerts stop at the event. Camnitive goes on: it measures each one, scores it against the packs you choose, and seals it as evidence, so the same alert serves the site team, the client and the auditor.

Neither. FloFrame works with the site cameras you already have, and PPE, falls, edges and plant proximity are standard detections. A pilot of 10–50 cameras usually goes live in days.

Zones and rules are settings, not training. Redraw a zone or change a rule in minutes as work areas, perimeters and crews move.

On your sites. FloFrame processes video where it is recorded; only alerts, chosen evidence and measurements leave. FloFusion is hosted by Camnitive, or deployed privately in your own cloud or data centre.

PPE, falls and man-down, unprotected edges and plant proximity. Then they measure trends by zone and subcontractor, score them in a safety pack, and act on the repeat hotspots.

Trends by zone, shift and subcontractor, plus sealed evidence for every event and signed, hash-chained score snapshots. Safety meetings, client reports and audits work from the same record.

No. FloFrame works over 4G, 5G or a temporary link, and keeps detecting through outages. It only needs an outbound connection on port 443 to send alerts when the link is up.

Yes. FloFrame drives outputs on site, such as HTTP or ONVIF relays, Modbus TCP and MQTT. It is an aid next to your certified safety systems.