Metrici Special AI Projects

When standard AI is not enough,
we build what you need.

Custom AI development. Real-world applications. Built around your process.

Metrici develops custom computer vision and AI solutions designed around your specific requirements. From specialised object detection and quality inspection to process monitoring, automated counting and system integration, we turn visual information into data your operation can act on.

Custom detection models Quality inspection Counting and process monitoring Integrated with your systems Developed and run on your infrastructure
CLASS LIST defined with you, not shipped to you present & correctly seated present — misaligned missing component foreign object in frame SEATED MISALIGNED COMPONENT MISSING SEATED Custom object detection and classification Classes defined with you · model trained on your parts · every item labelled
INSPECTION STATION VERDICT OK FLAG image, timestamp and class kept for review LAST FLAGGED review Automated quality inspection Configured criteria · per-item verdict · flagged items kept with their image
COUNTED THIS SHIFT 1 284 1 291 line camera · virtual trip line THROUGHPUT BY HOUR MONITORED ZONE 3 objects · one over the dwell limit TRIP LINE Counting and process monitoring Virtual trip lines · zones and dwell · activity per hour, kept as records not impressions
CAMERAS METRICI ENGINE custom model · rules · events Metrici interface events · images · reports Your systems HTTP POST / JSON · SQL Signage LED display · alarms Equipment controller · relay · line WHAT HAPPENS NEXT configured per project: flag · divert · log · notify Runs on your hardware on-premises, on your network Alerts and integrations, not just detections One detection → interface record, external systems, signage and equipment outputs

Who we build for

Three kinds of people usually land on this page.

All three have hit the same wall: the thing they need detected is not in any product catalogue. What differs is what they have to do with the answer — stop a line, ship a machine, or prove what happened.

Production, quality and process engineers

You know the defect, the component or the condition. You have described it to a vendor and been offered a generic analytics package that cannot see it. You need a detection trained on your parts, in your lighting, at your line speed, with a verdict your line can act on.

Integrators, machine builders and software houses

Your customer wants vision inside a system you already deliver. You need an engine you can configure and talk to — events over HTTP POST / JSON, database views, controller outputs — and an engineering partner who will build the recognition class that does not exist yet.

Operations, safety and logistics managers

Something happens on your site that nobody can prove or count: a load that leaves incomplete, a boundary that is always crossed, a queue nobody can quantify. You need records — image, time, place, count — that survive a dispute.

The problem this page exists for

Your process is unique. Your AI solution should be too.

Off-the-shelf software is built for predefined tasks. It works well — right up to the moment you need something specific to your line detected, a product recognised that is not in any standard model, or a process with its own rules monitored.

Inspections that take time and drift

Manual inspections that take time and produce inconsistent results. Results vary by shift, and the record of what was checked is a clipboard.

Objects standard software cannot see

Your component, packaging, animal, material or defect is simply not a class in a general-purpose model. No amount of threshold tuning teaches a model what it has never been shown.

Processes that need continuous eyes

Conveyors, buffers, docks and lines run for hours. The interesting event lasts two seconds and happens when nobody is watching the right screen.

Quality tied to one operator’s attention

When the check depends on one experienced person, quality leaves with that person — and scales only by hiring more of them.

Data scattered across systems

Cameras in one system, machines in another, business records in a third. The answer exists, but not in any single place someone can query.

Detection that has to reach a machine

Seeing it is not enough. The result has to reach a PLC, a controller, a barrier, a divert gate, a sign or your ERP — within the time the process allows.

So we treat it as an engineering project

Metrici approaches these challenges as individual projects: the detection is defined, trained, tested and integrated against your requirement, your visual data and your operating conditions. That is a different discipline from deploying a standard module — and it is the one this page is about.

Custom model trainingYour existing camerasOn-premises serversInterfaces and outputsDocumented acceptance

The capability set

A custom AI solution, from detection to action.

What the Metrici stack can be asked to do. This is the technology layer: six capabilities a project is assembled from. The concrete applications built from them are in the next section.

01

Custom object detection and classification

Models trained to recognise the specific products, components, materials, vehicles, packaging, equipment or conditions you care about — the classes your industry never supplies to a general model.

Classes are defined with you, annotated on your imagery, and validated against your own acceptance criteria.

Engine: custom DNN recognition · classes per project

02

Automated quality inspection

The model returns a verdict per item — class, confidence, pass or flag — against criteria you set. A missing part, a misaligned lid and a crushed corner are all expressed the same way, which is why one inspection station can carry several checks.

Each item keeps its verdict and image, so a flagged item can be reviewed rather than argued about.

Output: per-item verdict · image · alarm or divert

03

Counting and process monitoring

Virtual trip lines and drawn zones turn a camera into a counter and a presence detector: objects counted, areas watched, dwell measured, activity attributed to a camera and a timestamp.

Counts are records with timestamps and images attached, not a live number that disappears at the end of the shift.

Engines: Area Counter · Line Counter · custom counting

04

Safety and compliance monitoring

People and vehicle analytics run against zones and rules you draw: presence, absence, entry, dwell. Whether a specific vest or helmet counts as compliant is a class definition you set, not a default we ship.

This confirms a configured visual condition — it is not a judgement about a person, and it does not identify who that person is.

Output: real-time alert · image · event log

05

Visual data extraction and recognition

Supported codes, labels, markings, serials and documents read from the image and associated with the operational record: what was read, on which object, at which position and time.

Reading is bounded by print quality, resolution and angle; feasibility is established on your real samples, not on ideal ones.

Engines: OCR · 2D and barcode reading · code verification

06

Automated alerts and integrations

A detection is only useful once something acts on it. Each project configures what follows a detection — flag, divert, log, notify, drive hardware — and Metrici can execute configured actions automatically, while other workflows can flag events for operator review or approval.

The action is configured, not invented at runtime: what happens after a detection is a rule you set and can audit.

Rules: configured per project · logged · auditable

What decides the scope

The exact capabilities are defined by the project, the visual data available, the operating environment and the integration required. Four questions settle most of the scope before anyone writes a line of code: what must be detected, from what camera position and image quality, how fast the answer has to arrive, and what has to happen once it does.

Where a requirement cannot be met from a usable camera position, or the images cannot carry the information needed, Metrici says so at assessment stage — before a licence or a server is bought.

Indicative comparison for planning. Which column you land in depends on whether the classes exist, whether your data can support training, and what the result has to do.
Question Standard Metrici module Standard module + custom training Fully custom development
What is recognisedPlates, people, vehicles, places, codesYour objects, as additional classesWhatever the agreed classes are
Work before go-liveConfigure per positionConfigure, annotate, train, validateDefine, annotate, train, validate, build outputs
Typical trigger for the enquiry“We want this measured”“It must also see our part”“No product sees it at all”
Integration depthMetrici interface, displays, controllersSame, plus event exportSame plus bespoke software, APIs, machine signals
Cost and time shapeLowest — no development phaseDevelopment phase, then deploymentDevelopment phase per subsystem, then deployment

If a standard module answers the requirement, Metrici will point you at that instead. Several of the custom projects further down this page later became standard modules — that is the normal direction of travel, not the goal.

Development domains

What can we develop?

Six areas where custom projects land, with the tasks customers actually bring us. Each bullet is a starting point rather than a specification: scope is set against your images and your conditions. Where these have been delivered is listed at the end of the section.

Quality control and defect detection

Products and components inspected by camera against models trained for your quality requirements.

  • Detecting missing or incorrectly positioned components
  • Identifying visible defects, cracks, deformations, surface irregularities
  • Checking shape, dimensions and selected visual characteristics
  • Verifying packaging, labels and product presentation
  • Flagging items for further inspection, with their images retained.

Real projects cash-handling verification · sofa assembly completeness

Production and process monitoring

Turn camera feeds into information about what is happening on the production floor.

  • Products and components counted
  • Conveyor belts and production areas monitored
  • Selected process conditions detected
  • Activity and exceptions recorded
  • Configured bottlenecks or unusual events identified

Real project overhead cart position and bearing temperature at a soda-ash plant

Logistics and material handling

Monitor the movement, presence and identification of goods, vehicles and materials.

  • Recognising selected packages, containers or materials
  • Read supported QR codes, barcodes and markings
  • Monitoring loading and unloading operations
  • Detections associated with vehicles, locations and records
  • Alerts raised on configured conditions

Real projects container and plate cross-linking at a port · a ferry toll module built for one site

Safety and restricted-area monitoring

Use video analytics to identify defined conditions in operational environments. Applications include:

  • Detecting selected personal protective equipment
  • Monitoring access to configured restricted zones
  • Presence of people or vehicles in designated areas
  • Alerts triggered for predefined events
  • Recording images and event information for review

Protective-equipment detection confirms a configured visual condition. It does not certify that work is safe, and it does not replace the site’s safety procedures.

Agriculture and environmental applications

Develop specialised recognition and monitoring models for visual conditions in natural or agricultural environments.

  • Counting plants or other visible objects
  • Monitor selected crop characteristics
  • Detecting defined visual signs of pests or disease, where image quality and training data support it
  • Monitoring presence of selected animals or objects
  • Identifying specified environmental events visible to cameras

Outdoor work is the least forgiving: weather, growth stage, season and camera reach decide what is possible.

Specialised recognition projects

Some requirements do not fit a category at all: a specific visual pattern, an unusual object, a machine state, or a behaviour defined by your own procedure.

Metrici can assess custom recognition involving specific objects, patterns, equipment, documents or operational scenarios. If the requirement can be described and captured through suitable visual data, we can evaluate whether a computer vision solution is feasible.

The honest answer at the end of an assessment can be “yes”, “yes, if the camera position changes”, or “no, not from images”. All three are deliverables. Where these domains have been delivered is listed at the end of this section.

Where these applications have landed

Custom work crosses industries easily — the engineering is similar even when the objects are not. Metrici has delivered projects across all twelve areas. Eight are backed by a case study or a documented success story on this site; four are delivered work we do have permission to talk about.

Manufacturing and automotive

Component inspection and assembly completeness.

Chemical and heavy industry

Position and temperature on assets you cannot stop.

Transport, ports and logistics

Cargo, container and gate records, bespoke integration.

Pharma, food and packaging

Label and packaging checks on a running line.

Cash handling and secure logistics

Cassette content checked against the record.

Commercial and public venues

Visitor and vehicle counts across a site.

Mining and aggregates

Vehicle and load records in dust and mud.

Document automation

Papers read, structured and filed on a local LLM.

Retail and warehousing

Shelf, packing and movement checks in view of a camera.

Agriculture and horticulture

Plant and livestock monitoring across seasons.

Environmental and wildlife

Species and event models trained and installed.

Construction

Asset presence and configured site conditions.

Further custom work — bakery lines, fuel-filter and car-seat inspection, textile roll counting, bottle packaging, marina berths, waste loads — is listed on Metrici success stories.

How a special project runs

From a specific problem to a working solution.

A special AI project starts with the problem, not with a predefined product. Six steps, in this order — and the first two are the ones that decide whether the other four are worth doing.

01

Define the requirement

We discuss what needs to be detected, counted, inspected or monitored; how the result will be used; who or what has to act on it; and the conditions the system must handle — night, dust, glare, line speed, occlusion, angle.

02

Evaluate the visual data

Camera placement, resolution, lens, lighting, object visibility and the samples you can already provide. This is where most projects are won or lost: a detection is bounded by what a lens can resolve from a position you actually have available.

03

Develop and train the model

Data is prepared and annotated on your imagery, then the appropriate detection model is developed or configured for the agreed classes, conditions and requirements. Standard engines are reused where they already answer part of the task.

04

Test and validate

The model is evaluated against representative data and real operating conditions. Detection performance, known limitations and the acceptance criteria are reviewed with you — before anyone calls it finished.

05

Integrate with the operation

Where required, results are connected to the Metrici interface, databases, external software, LED displays, alarms, controllers or other equipment, using the interface your environment supports.

06

Deploy and improve

The solution is deployed in the agreed environment. Further refinement follows when new data, new product variants, new conditions or new requirements appear — which, in our experience, is when the system meets production rather than the test set.

What the assessment hands you

Before a licence or a server is bought, the assessment produces something you can act on with us or without us:

  1. A feasibility answerYes, yes-if, or no — with the technical reason for it.
  2. A camera planWhere a camera has to sit, at what resolution, to see what you need seen.
  3. A class listThe exact classes the model is trained for and the verdicts it will output.
  4. The known limitsLighting, distance, speed, occlusion, print quality: what will degrade the result.
  5. A written scopeEngines, servers, licences, integrations and the acceptance test we will be measured against.

Sequence and effort follow from scope. A project that needs one custom class on existing cameras is not the same job as one that needs three new engines talking to a line controller — which is why we do not quote a special project from a price list.

What this page does not promise

No accuracy figure is quoted here for a project that is not yours. Performance on your line depends on your imagery, your lighting and your definition of the defect — so it is established on your data and written into the acceptance criteria, not promised in advance.

Custom training is per project: a model trained for one customer’s parts, packaging or environment is not transferred to another as a ready-made detector. And these projects detect configured visual conditions. They are not identity surveillance; monitoring of people is limited to what your own lawful basis and data-retention rules allow.

Evidence, not scenarios

Real projects. Specific problems. Tailored solutions.

Four projects that off-the-shelf software could not solve, each documented in its own case study with its own photographs and interface screens. The figures below are quoted from those pages.

Cash handling Metrici interface showing custom-object counting events beside a live camera view of cash-handling tables, where cassettes, banknote stacks and labels are inside detection boxes.

Every ATM cassette checked before it leaves the dock

Brink's, a global cash-in-transit company, had to verify cassette content at every loading position — a check that depended entirely on the person at the table. Metrici ran a dedicated DNN training covering more than 31 object classes: every Romanian banknote denomination, the cassettes themselves, their lids, the label type used for each denomination, and euro banknotes. Each dock gets its own camera and detection engine, and the alarm sounds at the dock, not in a report the next morning.

31+ AI classes trained18 loading docks per locationCamera and engine per dock
Read the cash-handling case study →
Assembly quality Metrici counting-events screen listing custom-object detections from the sofa production camera, beside a live view of a padded component being handled on the line.

AI checks sofa components before boxing

At the Aramis Group works in Baia Mare, the check before boxing and shipping was a human one. Metrici was trained on the components of a two-person sofa — 10 object classes — and on fiducial markers that tell the system which product is on the line and which operator or supervisor is standing at it: one marker per product, ten for operators, ten for supervisors. If any component is missing, an alarm is raised and a production supervisor must check the product before it moves.

10 component classes2 cameras + 2 engines per line10+ products to be added
Read the furniture assembly case study →
Heavy industry Aerial photograph of a large chemical plant with cooling towers, chimneys, process buildings and overhead conveyor lines.

Catching an overhead cart bearing before it jams

At Solvay Sodi's Devnya soda-ash plant, a jammed bearing on the overhead cart line meant pulling the cart out of service at considerable cost. Metrici reads bearing temperatures from a thermal camera, checks each cart's position on the line, and reads the cart's serial number by OCR — including when the cart is upside down and the number is not where a reader expects it. Every alert carries a photo, a timestamp, a cart number and a temperature, in real time.

1 thermal + 1 IP cameraDedicated AI training1 server
Read the chemical plant case study →
Bespoke module Metrici LPR toll station live view showing two ferry loading cameras, each with a recognised heavy-vehicle plate and direction of travel.

A toll module that did not exist, built for one ferry

The Călărași Danube ferry crossing had to be automated without ever stopping the boats. The recognition existed; the toll logic did not — so Metrici developed the Toll Station module specifically for this project, integrated the operator's tariff categories and cash registers, and installed it live with zero downtime. Once manual ticketing was removed, revenue tripled. The module was later released to all Metrici LPR users.

Revenue tripled13 tariff categories162 vehicles per crossing
Read the Danube ferry case study →

Also documented, also custom

How to read these numbers

Each figure above is quoted from the linked case study, which carries the site, the installed hardware and the interface screenshots. They describe what those projects were built to do. They are not an estimate of what yours will achieve — that estimate can only come from your images and your criteria, which is why step 02 exists.

A further set of custom projects — bakery lines counted per operator, textile roll counting, glass pallet and shrink-wrap checks, marina berth occupancy, waste loads classified with location — is listed on the Metrici success stories page, where several are documented without naming the customer.

Architecture

Built to work with your existing environment.

A custom AI model is only one part of a complete solution. It has to work with the cameras, the equipment and the software already in your operation — or nobody will use it after week two.

Video sources

Metrici works with compatible IP cameras using supported video streams and interfaces. Existing installations may provide a starting point, subject to resolution, lens, positioning, lighting and the requirements of the detection task.

Detection engines

Metrici standard modules and custom-trained recognition models, running side by side on the same servers. Several engines can work the same site: plates in one lane, containers in another, your own object classes at the dock.

Metrici interface

Event monitoring with the image attached, statistics, reports, exports and role-based user access. Every detection is a row you can filter, export and argue from — which is what makes a custom detection auditable a year later.

Hardware and outputs

Supported controllers, barriers, LED displays, audible alarms and other connected equipment, including tailored controller firmware where a site’s traffic logic is not standard. Detections can drive hardware, not only dashboards.

Software integrations

APIs, HTTP POST / JSON event export, direct database access and scheduled exports, plus bespoke interfaces where the target system has no standard one. The integration method is chosen against your environment, not ours.

Deployment options

On-premises installations and other supported infrastructure configurations. Where required, applications, models, interface and outputs run entirely inside your own network, with no third-party hosting in the path.

Why build it with Metrici

Detection is the easy half. We also deliver the half that has to run.

Train a model on a clean dataset. What a plant manager is buying is a system that still reports correctly every time.

A solution built around your requirements

The detection model and the workflow are designed for the objects, conditions and operating rules of your project — not adapted from a feature list you have to work around.

Computer vision and integration in one project

Metrici carries the detection, the servers, the interface, the controller outputs and the software integration. You are not coordinating three suppliers to make one function work.

Experience across different applications

Our work spans license plate recognition, counting, parking, industrial automation, document processing and custom recognition projects. Patterns cross over in ways a single-industry vendor never sees.

A practical route from concept to deployment

Assess the data, define the scope, test against agreed criteria, integrate, then refine on live data. Each step has an output, so you can stop at any of them.

Control over your deployment environment

Architecture, data handling and access arrangements follow your requirements. On-site servers with no third-party hosting in the path are options we have delivered, not brochure lines.

We tell you when software is the wrong answer

Some requirements are a lighting problem, a conveyor problem or a process problem wearing a software costume. Saying so at assessment stage is cheaper for you than a failed pilot, and it keeps the projects we do take on honest.

Founded 2010Metrici AI Solutions SRL, Bucharest — video analytics and AI from the start.
31+ classestrained for one project: banknotes, cassettes, lids and labels at cash-loading docks.
14 enginesrunning on one site, across 14 cameras, at a port handling around 100,000 TEU a year.
Since 2013a plate-recognition and weighing integration into SAP still running at a steel plant.

Questions engineers actually ask

Before you send the enquiry.

01Is this page only for problems no standard Metrici product can solve?

Mostly, yes. If a standard module already answers the requirement, Metrici will tell you to deploy that instead — it is cheaper and faster. What this page covers is the other case: a detection class that does not exist, a verdict that has to reach a machine, or a workflow that needs software built around it. Several projects that started exactly there later became standard modules, including the toll module built for the Danube ferry.

02Do we need cameras, images or video ready before the first conversation?

No, but it changes the quality of the answer. With ten or fifteen minutes of footage from the actual position, an assessment moves from a reasonable guess to a defensible yes or no. If the cameras do not exist yet, tell us where the position would be and what has to be seen from it — we can say whether the task is plausible at that distance and resolution.

03Whose data trains the model, and where does it run?

The training data comes from the project: imagery of your parts, packaging, vehicles or environment, annotated against the classes you agreed. Where a customer requires it, the whole system — applications, models, interface and outputs — runs on a server inside their own network, with nothing shared with third parties. That is how the certificate-automation project at Certind was built. Data handling and access arrangements are defined per project.

04How long does a special AI project take, and what does it cost?

It depends on how many classes must be trained, how much representative data exists, how strict the acceptance criteria are and how deep the integration goes. One custom class on existing cameras is not the same job as three engines wired into a line controller. That is why the first step is an assessment that produces a written scope and an acceptance test, rather than a number taken from a price list.

05Can the detection stop a machine, divert an item or open a barrier?

Yes. On projects Metrici has delivered, detection results drive controller outputs, relays, LED displays, audible alarms and barriers, and results also leave the platform as HTTP POST events or database records for your own systems to act on. One boundary: where a function is a safety function under your machine-safety obligations, it must be engineered and certified to that standard. Video detection is an inspection and process-control tool, not a safety certification.

06Do you work with integrators and machine builders, or only with end customers?

Both. Several of the projects linked on this page were delivered with a partner in front: a systems house for the cash-handling deployment, regional integration partners for the port and factory installations. Integrators usually consume detection events over HTTP POST or JSON, read them from a database view, or use controller outputs directly, and keep their own application layer above Metrici's detection.

Something more specific? Write to sales@metrici.ro and say what needs to be seen, or request a software demo first.

Start with the problem

Tell us what you need to detect.

You do not need an AI model or a complete technical specification. Start with the operational problem — the five answers below are enough to begin an assessment.

What to detect

What needs to be detected, counted, inspected or recognised? Describe the condition in the words your operators use.

Where

Where does the process take place, and what already covers that position: a camera, a window, a lamp, nothing at all?

Your data

Do you already have cameras, images or video samples showing the condition — including the bad cases, not only the clean ones?

The action

What should happen the moment the system detects it: an alarm, a flag, a record, a divert, a stop, a message to another system?

Integration

Does the result need to reach another application, machine or controller — and who owns that interface today?

What happens next

Our team can review the scenario and discuss the technical feasibility, potential solution and next steps.

Have a challenge that standard software cannot solve? Let’s discuss it.

Then what happens

You send the description

By email, with text, photos or a phone video of the position — whatever you have. No template and no specification required.

Then what happens

We assess feasibility

Classes, camera position, image quality, limits. You get a yes, a yes-if or a no, with the reason.

Then what happens

You get a written scope

Engines, servers, licences, integrations and the acceptance test the finished system is measured against.