Skip to content

The product

What it does on the line.

Ulark5 is the unit between the instruments and the record. Everything below describes what that changes for the people working a position.

Capabilities

Six things it does, stated plainly.

Each removes a specific piece of friction that inspection stations put up with because the equipment was never designed to work together.

  • 01

    Manages any manufacturer’s equipment

    The instruments on the line keep working as they are. Replacing one later is a driver change, not a rebuild of the station.

  • 02

    Fast, centralised data collection

    Readings leave the instrument as they are produced and land in one database, with nothing re-typed in between.

  • 03

    Continuous and secure transfer

    The line keeps running if a link drops; data is carried through and reconciled rather than lost.

  • 04

    Measurement equipment management

    The handheld drives the bench directly — start a test, read the result, move on — instead of walking to each console.

  • 05

    Uniform procedures

    Every inspector follows the same sequence on the same screens, which is what makes results comparable between shifts and between stations.

  • 06

    Full internal control

    The record shows who performed which step and when, so quality checks are a query rather than an investigation.

Line workflow

From the gate to the register.

The documented order of work. Select a step to see what the system is doing at that point.

Step 01 of 06

Registration

The vehicle is registered at the entry lane, at reception or through online booking. If it has been inspected before, the registration number is enough.

Inspection lane layoutA vehicle enters at registration, stops in turn at the brake, emissions, lights and visual inspection positions, and leaves once the report is printed and the result filed.EntryRegistration1BrakesRoller bench2EmissionsGas · opacity · OBD3LightsIntensity · alignment4VisualGuided checklistExitReport filed
The inspector carries one handheld along the lane. Every position reports into the same record.

Two applications

One at the desk. One in your hand.

The station and the line need different screens. They share one record.

DVS.WEB

Station application

The desk side of the station: queue, vehicle records, results, reports, staff, permissions and station configuration.

  • Queue and line flow across every position
  • Vehicle history and measurement archive
  • Report generation and printing
  • Staff accounts and permission levels
  • Station and equipment configuration

DVS.MOBILE

Handheld application

What the inspector actually holds. Drives the benches, walks through the inspection guide and captures visual findings at the vehicle.

  • Controls the connected test equipment
  • Guided visual inspection points
  • Live measurement readout at the vehicle
  • Works on the line, not at a desk

What it removes

The five things stations stop living with.

None of these are software problems. They are what happens when instruments from different decades and different manufacturers end up on one line.

  • 01 A different console and a different interface for every brand of equipment
  • 02 A separate computer added beside each instrument
  • 03 Time lost carrying results from one system to another by hand
  • 04 Mismatched screens that make procedures differ between positions
  • 05 Weak internal control over how an inspection was actually performed

Modules

What can be connected to a position.

Hardware modules the system drives directly, each recording the parameters the inspection has to prove.

  • Brakes

    Checks brake condition against the permitted parameters and stores the result.

    • Vehicle mass
    • Brake effectiveness
    • Difference between wheels
    • Roll resistance
    • Tyre pressure
  • Emission — diesel

    Measures diesel exhaust and compares it with the permitted parameters.

    • Exhaust opacity
    • Engine speed
    • Particle number
  • Emission — petrol

    Measures petrol exhaust and compares it with the permitted parameters.

    • CO
    • CH
    • CO₂
    • O₂
    • Lambda
  • Lights

    Checks the vehicle headlights and stores the result.

    • Intensity of illumination
    • Angle of alignment
  • On-board diagnostics

    Reads the vehicle’s own systems as part of the inspection.

    • OBD fault memory
    • Readiness status
    • OBFCM consumption data
  • Video system

    Captures the visual inspection data for the vehicle.

    • Position of the vehicle
    • Colour code
    • Measurements
  • Line flow control

    Shows inspection data for every vehicle and which devices are free, and moves a vehicle to any inspection point.

    • Per-vehicle inspection data
    • Device availability
    • Position reassignment
  • Surveillance

    Monitors the work environment and stores the recording for later use.

    • Work environment recording
  • Gate control

    Controls the line at the gate from a mobile device.

    • Gate operation from mobile

Operational properties

How it behaves once it is installed.

The things that matter on a Tuesday morning, two years after commissioning.

  • Adaptable to the station

    Configured around the procedure the station already runs.

  • Unlimited lines and clients

    One system covers a single lane or a whole network.

  • Runs on Linux

    A predictable, long-lived base for an industrial unit.

  • Keeps the archive

    Inspected vehicles stay retrievable for later reference.

  • Vehicle import from file

    Bulk data goes in without manual entry.

  • Automatic updates

    Units move to the current version without a site visit.

  • PDF reporting

    Reports are generated and printed at the line.

  • No internet required

    A disconnected station runs exactly the same way.

Universal monitoring system

USS.EYE

Ulark is the inspection-line member of a wider family. USS.EYE receives and processes data from sensors, measurement devices and control equipment, archives the result, hands it on to other systems and controls the connected equipment centrally — without depending on the manufacturer or type of that equipment.

  • Data from sensors, measurement devices and control equipment is received and processed
  • Information is archived and transferred to other systems
  • Centralised control of connected equipment
  • Independent of equipment manufacturer and type
  • LARK

    This product

    PTI Business

    The subsystem Ulark5 runs. Automates periodic technical inspection: the queue, the equipment, the procedure and the record of what each measurement produced.

    • Automation of technical inspection processes
    • Guaranteed precision of the performed measurements and procedures
    • Interface options including mobile, web, WRP and APK clients
    • Applicable to various line modifications
  • TAURUS

    Company operations

    Resource Management

    Plans and accounts for the work itself — which jobs are running, what they consume, and what the company has left to commit.

    • Monitoring and control of ongoing processes
    • Automatic planning and accounting of work and required resources
    • Customised to the way the company operates
    • Connects to systems the company already runs
  • OWL

    Visual evidence

    Image Processing

    Ties recorded images to the measurement output, so a stored result can be looked at as well as read.

    • Synchronises image with output data
    • Indexes the video system against defined criteria
    • Object recognition
    • Number recognition
    • Finds and previews records by selected criteria

Planning a line, or replacing what runs one?

Tell us how many positions, which instruments and which country's register. That is enough to scope it.

Talk to us