Software

AIMSOC®

Software for automatic identification in business processes

The AIMSOC® logo: a solid dark blue disc carrying a white mark made of round nodes joined by thick lines. An arch rises over the centre, each of its ends turning down and outward to a node at the lower left and the lower right, and a straight vertical line runs down the middle from a node at the top to a node at the bottom.

Overview

AIMSOC® brings automatic identification into the processes a company already runs. Work is recorded right where it happens: at the workbench, at the welding station or in the warehouse.

The software knows a company’s physical items, the people who work with them, and the identifiers that make each item recognisable. Every change is kept, so any record can be read as it stood at an earlier point in time.

Modules extend AIMSOC® for particular business processes, such as production.

Features

  • A screenshot of an asset list in the software. The table columns are primary identifier, asset type, current location and primary serial number. Each row shows an asset (head unit, instrument panel, centre console, control unit), most of them with a GS1-SGTIN or Steel-STL identifier, some with a location such as a production area or a store, and some with the fields still empty. Above the table sit a filter and a search box.

    Keep a record of every physical item

    AIMSOC® keeps each physical item as a record of its own, recognisable by one or more identifiers. Every change is recorded as an event: when it happened, who made it, where, and what changed. In the software, these items are called assets.

  • A screenshot of the identifiers held against a single asset, one per row. Each row carries a badge naming the scheme the identifier belongs to (GS1-SGTIN, GS1-GIAISPLIT, Identech-article-sn, Steel-STL), with the identifier itself printed beneath it. The four values are formatted differently from one another; the second row is highlighted.

    Keep using the identifiers already in place

    Items are recognised by their identifiers, and AIMSOC® uses several kinds of identifier side by side. These can be standards such as GS1, or a company's own internal numbering schemes.

  • A pencil sketch of five devices drawn on a blank surface: a pistol-grip handheld reader with a screen, a row of buttons and a squat antenna seated on top; a rugged handheld the shape of a phone, held in a protective bumper; a small hand-sized reader with one large and three smaller buttons; a flat desk reader with a large panel across its top face; and a plain square antenna plate standing on edge.

    Connect different hardware

    AIMSOC® is not tied to any one device. RFID readers, mobile RFID handhelds, barcode scanners and touchscreens can be connected. Several devices can be grouped into a station, where they work together.

  • A pencil sketch of a person in safety glasses standing at a workbench in a workshop, holding an identity card flat above a reader plate set into the bench. The card and the plate beneath it glow blue. A metal housing lies on the bench beside them, and trolleys carrying crates stand in the background.

    Roles and permissions

    Roles define who may do what in the system. Each person is given the roles their work requires.

  • A screenshot of a list of held qualifications, one per row. The columns are person, qualification, expiry date and valid-from date. Two people, Hans Muster and Fritz Meier, hold qualifications such as an electrical specialist for high-voltage systems and non-destructive testing level 2. Each expiry date carries a mark: green with a check where the date is still ahead, red with a cross where it has passed. Above the table a filter limits the list to those two people.

    Qualifications and certifications

    Certifications record who can demonstrate which skills. Particular tasks can then be restricted to the people qualified to carry them out.

  • A screenshot of a spreadsheet holding rows of parts to be imported. One column names the part (wheel bearing, complete wheel, bracket, screws in three colours, nuts, washers, a fin), a second gives a size for some of them, long, medium or short, and a further column holds the identifier, mostly a GS1-LGTIN or GS1-SGTIN with its number, the last row a FALCON-SN. The header row is cut off above the top edge.

    Import data from files

    Master data and order data can be imported in bulk from a file. Each row of the file becomes a record of its own in the system.

  • A screenshot of a printed report headed Seriennummern – Bericht, with Serialnumber Report beneath it and the AIMSOC® logo in the top corner. Every label is given in German with the English under it: order, asset type, serial number and identifier, each with its value in a bordered box. Below them a table lists two positions, each an asset type Cockpit with a planned amount of one, and under each position an identifier with its serial number, lot, employee, workspace and the time it was recorded.

    Create reports

    Reports are built from a company's own templates. A template arranges predefined blocks of data into a document.

  • A screenshot of an API reference on a dark background, headed Assets. Four rows list one endpoint each, every row beginning with a coloured badge naming the method: GET on /api/repository/assets/{id}, get asset by id; PUT on the same path, update an asset; GET on /api/repository/assets, get list of assets; POST on that same path, create a new asset.

    Connect other systems

    Other systems can pass data to AIMSOC® and retrieve it through interfaces. An ERP system, for example, can create orders directly in AIMSOC®.

  • A pencil sketch of a person in safety glasses at a workbench, holding a small handheld reader against a metal housing. A glowing blue line runs from the reader up to a server cabinet, and from that cabinet three dashed blue arcs curve on to three further cabinets standing behind it.

    Notify other systems

    When AIMSOC® records a particular event, it can notify other systems automatically. Which events trigger a notification is set in the system.

Modules

A closer look

  • A screenshot of the asset list in the AIMSOC® dashboard, in English. Seven rows, each with a creation date, a primary identifier labelled with its scheme (GS1 or a company's own serial numbers) and an asset type such as a rudder or an aircraft.
    Every recorded item can be viewed in the system.
  • A screenshot of one asset's detail page, in English: its current location, its asset type, a note that it is the product of a production order, and a table of its identifiers with one marked as primary.
    An item's detail view lists all the information available on it, including its location, type and identifiers.
  • A screenshot of an asset's detail page with a German interface. A hierarchy shows a rudder with two components beneath it, one of them highlighted. Below, an events table lists two changes to the highlighted component, each with its time, the person, the location and the kind of change.
    The detail view also shows the item's hierarchy, and every event that concerns the item.
  • A screenshot of an event details dialog over an asset page, German interface. It shows version 2 of the record, the time, the person and the location, and the change itself: the component was assigned to a parent asset, named by its serial number.
    Opening an event shows exactly what changed, next to who changed it, where and when.
  • A screenshot of the asset type list, in English: 45 kinds of component, such as struts, plates, screws and nuts, each with a reference number and the GS1 identifier scheme its items carry.
    Each kind of item states which identifier its items carry, so a scan is recognised as the right kind of item.
  • A screenshot of the device sessions list, German interface. Nine sessions, one active and eight ended, each with the device, its start and stop time, the connection type and the client version.
    Which devices are connected at any moment can always be seen.
  • A screenshot of the qualifications list, in English: eight qualifications such as first aid, certified welder and forklift operator licence, each with the organisation behind it.
    A qualification is recorded once and can then be assigned to people as a certification.
  • A screenshot of the certifications list, in English: fifty entries, each linking a person to a qualification, with issue, effective and expiry dates and a certificate ID.
    A certification records which person holds which qualification, and that is what a step can be restricted by.

Where this product helps

Tell us about your use case

Together, we work out whether and how your process can be digitized.