Solutions

Solution area 04

Shared devices, individual accountability.
Nobody loses the day logging in and out.

A kiosk on the loading dock or a register on the shop floor stays signed in under one generic SAP ID. Each action is confirmed with a fingerprint and recorded against the human who took it.

The kiosk stays signed in. The action still belongs to a named human.

Shared machines leave two bad options.

On a factory floor, in a warehouse, at a service counter or behind a register, people share machines. They move between locations, between shifts and between registers, often several times a day.

Everyone logs in and out

Accountability is intact and the day is lost. Logging in and out of SAP dozens of times does not survive contact with the shift.

Everyone shares a generic account

The work moves quickly and nothing is traceable. Every goods receipt and every register transaction belongs to an account rather than to a human.

The screen is left open

An unattended session is an open door to anyone who walks past, including people who do not work there.

Where standard SAP security stops

SAP can give a shared device a generic account, and it can give every human their own account.

SAP answers this

Which account is this device signed in as?

bioLock answers this

Which human took this particular action on it?

The choice between speed and accountability is exactly the choice bioLock removes.

Your SAP system Goods, orders, time data
The generic account What the kiosk is allowed to do
bioLock Who is at the shared device

A layer inside SAP, not a product beside it

How bioLock closes it

The device stays signed in. The identity arrives at each action.

01

The device stays signed in

Under a generic SAP profile, so nobody waits for a logon.

02

Individual biometric profiles are associated with it

The account belongs to the kiosk. The identity belongs to the human.

03

Each protected action asks for a fingerprint

And takes about a second. Post the goods movement, create the sales order, confirm the maintenance step: verification happens at the action, not at the door.

04

Anyone not enrolled can do nothing

A visiting driver at an unattended screen is refused, whatever is already open on it.

05

Every action is logged against the identified human

Which makes reconciliation possible down to shift, location, device and individual.

bioLock · shared kiosk

Signed in as the kiosk

One generic account, so nobody waits.

WAREHOUSE_KIOSK01Generic accountSigned in

Identities linked to it

The account belongs to the kiosk, the identity to the human.

Thomas SmithShift AEnrolled
Amanda JonesShift BEnrolled

A second at the action

Not a logon. A confirmation.

Confirm operationPalm verified1 second

The visiting driver

The screen is open. The answer is still no.

Not enrolledAt an open sessionRefused

Reconciled to the human

By shift, location, device and individual.

Thomas SmithDepot 14 · 06:12Allowed
Amanda JonesDepot 14 · 14:03Allowed
Not enrolledDepot 14 · 15:41Refused

What you can protect

Anything that can be reached from a shared device.

  • Goods receipt and release, inbound and outbound
  • Movement of inventory, work in process and raw materials
  • Bills of materials, scheduling, planning and maintenance steps
  • Sales order creation at the register, for example VA01
  • Credits, discounts and merchandise returns
  • Time and attendance entries
  • Employee self-service: pay slips, vacation requests, personal data

Verification methods

  • Palm vein
  • Fingerprint
  • Face recognition
  • Smart card
  • Biometric NFC band
  • PIN
  • Password
  • IP address
  • Nationality

Any combination can be required, and which one is used is recorded with the event.

In practice

Transnet, South Africa

The largest part of the country's freight logistics chain, 55,500 employees, and a Transnet Engineering division running 7 factories and 150 depots. Plant maintenance and shop-floor processes happen on shared devices, often with users who have limited computer or SAP experience, and in several languages.

“Users are authenticated biometrically before they can access SAP systems via shared access kiosks. We no longer have to worry about password fraud from these users at all.”

Mapula Mano, SAP Specialist: Plant Maintenance, Sales and Distribution, Transnet SOC Ltd

Read the full case study

A national retail chain

More than 200 stores, 300 cash registers and over 800 cashiers, with staff who are not tied to a single store and switch places frequently. Each sale carries a logged re-authentication, the cashier's name is printed on the receipt, and register activity reconciles back to SAP ERP financials by individual cashier.

Read the full case study

The Ohlthaver and List Group, Namibia

Namibia's largest privately held group of companies, employing 5,568 people. A paper-based vacation request process was replaced with a real-time electronic one at shared kiosks, with simplified screens for staff who are not SAP specialists and support for local languages.

Read the full case study

What it proves

Full workplace flexibility and full accountability, at the same time.

01

Full workplace flexibility with full accountability, at the same time.

02

Unattended screens stop being a risk, because the screen is not what grants access.

03

Activity reconciles to the human, which is what makes shrinkage, register differences and inventory losses investigable rather than merely visible.

Questions people ask

“Will this slow the shift down?”

A verification takes about a second, against the several seconds and several keystrokes of a logon, repeated all day. Customers adopt it because it is faster than what they were doing, not in spite of it.

“Our staff are not SAP users in the normal sense.”

That is the common case here. The interface can be simplified so only the task at hand is shown, which is how Transnet and the Ohlthaver and List Group use it.

“We have gloves, or dust, or cold.”

Fingerprint is one option among several. Palm vein, face recognition, smart cards and biometric NFC bands cover environments where a fingertip is not practical.

“What happens to the generic account in the audit?”

It stays, and it stops mattering. The log records the verified human beside it, so the generic ID is no longer the end of the trail.

See it in your own SAP system.

A 15-minute briefing, a 60-minute technical presentation for your team, or a proof-of-concept installation running against your own data and functions.

bioLock runs inside SAP ERP and the S/4HANA platform. It does not replace your security stack. It closes the gap between access and action.