Get a quote

Management Systems · Kartal

Management Systems for Kartal businesses

In any workshop one broken press costs a day. The same dependency hides inside an institution's marking step, where it is harder to see: if assessment runs through a single reader, the day that reader fails is the day results wait. Kartal's manufacturing strip and the training floors near the health campus can both carry that dependency. The tool we wrote for Vipkurum takes the machine out of the middle: marks come off an analysis layer that works on the image of the form.

Management Systems — Kartal

On Kartal's manufacturing belt maintenance is planned around the chance of a breakdown. Where a marking step still runs through one device in one room, paper piles up outside that room when a shift changes, and the day the device is down the queue stops for everyone at once. The closest match in our portfolio is the optical mark reading side of Vipkurum. Its limits belong here: the tool was written for exam marking, so a quality sheet on a production line, a bench schedule and institutional accounting fall outside it and we have nothing to show there. Python and OpenCV resolve the image, Node.js keeps the reading service up, and Laravel with MySQL holds the exam record.

  • Reading depends on an analysis layer working over the image of the form rather than on a piece of hardware, so one failure does not halt the chain.
  • Assessment stays where it happens: the image enters the system from a scanner, and no paper has to reach a particular building.
  • The scope is stated: the tool was written for exam marking, and institutional accounting or staff planning sit outside that line.

Why Algoriel

  • Capacity and credit stay apart

    Pilatesco keeps class capacity and a member's remaining package credit as two different things, so filling one does not quietly consume the other.

  • The same data is entered once

    In AlgoCar service, stock and accounting read the same record, so nothing gets retyped into a second screen.

  • Reports come off the record

    Invoices and reports derive from the work that was logged, so no separate month-end sheet has to be filled in.

  • Sale and use meet on one record

    At Pilatesco an invoice is raised when a package is sold while use is read from a calendar spread over weeks, and both meet on the member's record.

  • The rule is written into the record

    What each situation leads to is defined in advance. At Pilatesco a cancellation, a no-show and a completed session each hit the entitlement differently, and nobody decides on the spot.

  • Capacity is more than a single number

    How many people an hour holds is worked out from the instructor, the equipment and the time together. A one-to-one session and a group class open under their own rules.

  • Where the work stands, on one screen

    At AlgoCar a job moves along one record from the moment it opens to the moment it closes. In the dental clinic the manager sees which step of the plan a patient has reached without leaving that screen.

  • One record, seen to the limit of each role

    Vipkurum keeps timetables, classes, exams and payment records in one place, and a teacher, a guardian and an administrator each reach that record at their own permission level.

  • A report is the same record from another angle

    The month-end picture does not require a second set of books; it is the sum of what was recorded during the day.

  • A team that does the maintenance daily

    AlgoCar and AlgoKlima are our own products and both are live. We do the maintenance on software of this kind every day in our own panels, so it is not a promise we make for after handover.

Work like this

Management Systems · Case study

Vipkurum optical mark reading — no machine stands in the middle of the chain

An optical form reading tool written for Vipkurum's education platform. The marks are pulled out by an OpenCV layer working over the image of the form rather than by a reader's optics. The institutional consequence shows up as a dependency that is no longer there: assessment does not hang on one piece of hardware still being in working order, so the day it fails the whole group does not stop. Forms upload from a scanner, Node.js keeps the reading service running, and Laravel with MySQL holds the exam record. Scope: the tool was written for exam marking, and accounting, collections and staff planning fall outside it.

Read the case study →

Working with Kartal teams, remotely

We have no office, so work for this city runs remotely and we do not offer on-site support. What was done, and why it was done that way, stays in writing. The project pages mark which builds came out of a partnership.

  • The first release ships as a working piece; extras follow later.
  • Every client we know of is in Turkey.
  • Decisions stay in writing; progress shows in working screens.

Frequently asked

  • Our reader works. Why replace it?

    While it works, you do not have to, and we say so plainly. The question is a different one: what stops on the day it fails? Reading from the image takes assessment off any single device being in working order.

  • We run shifts, and marking is tied to the same room every time.

    The image of the form enters the system from a scanner, so the reading step belongs to a service rather than to a room. A shift finishes its own marking in its own hours, and nothing queues behind a door.

  • Is this management software or one narrow tool?

    It describes one step: how marking becomes a record. Accounting, collections and staff planning are not inside this tool. We write down where it ends, because that is where we have nothing to show.

  • Will your team come to our campus site in Kartal to install it?

    No. We keep no office, and nobody is sent out to a site. The first deliverable is written: which field of which form lands on which record. The reading step is built once that text is settled.

Which rule in your business still depends on somebody remembering it?