Facility map
Arrange rooms and zones, walls, doors, windows, equipment and checkpoints. Move and scale elements, use a grid and labels, and save the plan. It is an operational map for the team, not a certified architectural model.
Spaces · equipment · recorded work
Every asset has
a place and a history.
Map your spaces, place equipment and checkpoints, collect readings and record inspections. Photographs, a checklist, a drawn signature and a manager's decision stay connected to the relevant asset instead of getting lost in a separate chat.
Working data requires an account, permissions and relevant connections.
- 01Define the space
- 02Set up a checkpoint
- 03Record the work
- 04Review and follow up
Place → asset
Location, zone, equipment and checkpoint
Inspection → record
A reading, checklist and required evidence
History → decision
Manager review and a corrective action
01 / A clear workflow
From a facility map to a reviewable result
Suppose a restaurant needs refrigerator inspections. The record should identify the equipment, who measured the temperature, the evidence provided and whether follow-up is needed.
- 01
Define the space
Choose a location, create zones and place equipment on the map. Add the asset details, instructions and responsible manager.
- 02
Set up a checkpoint
Set the checklist in the equipment record. In the checkpoint, define a reading, unit, acceptable range and requirements for photographs, a signature or manager review.
- 03
Record the work
An employee opens the checkpoint, for example through its QR code, enters a value, checks the items and adds the required evidence. Opening the link does not itself complete the inspection.
- 04
Review and follow up
A manager reviews the record and, when needed, records a corrective action. Filter the history by asset, period and status.
02 / Working tools
Equipment is more than a row in a list
Equipment details
Keep the type, model, serial number, location, photographs and video instructions together. Add a manager, checklist and maintenance or cleaning intervals. A colleague can identify the actual asset instead of guessing from an isolated photograph.
Readings and work evidence
A record can include a value and unit, a comment, checklist items, photographs and a drawn signature. The log keeps available context: asset, time, employee, the range at recording and subsequent review.
Manager review
Assign an equipment manager and require checkpoint review. The manager can approve an observation or record a completed corrective action with a comment. This is an operational review, not automatic certification of safety.
QR and compatible NFC
Generate a checkpoint QR code and download its image for a label. NFC is available where the browser supports it, with QR as the fallback. The link opens the relevant authenticated form, but does not prove the employee's physical presence.
History and maintenance
Filter the log by zone, equipment, checkpoint, status and period, then export selected records to CSV. Intervals and completed events help calculate maintenance, inspection and cleaning dates. A displayed date does not itself mean a notification was sent or a repair completed.
From an inspection to the next step
Connected actions.
Not hidden side effects.
How QR/NFC checkpoints workAn appropriate checkpoint can have configured consumables and an existing Flow. The observation form lets the user select these actions separately: deduct the configured materials or request the linked Flow. Availability depends on permissions, storage, location and configuration.
- Scanning a QR does not itself deduct inventory
- The linked Flow is selected from available scenarios
- Sensor integration is checked for the specific equipment
03 / Illustrative scenarios
Three workflows that belong with an asset
Refrigerator temperature
Create a kitchen zone, refrigerator record and temperature checkpoint. An employee records a manual value, or available readings come from a compatible connected sensor. The photo, range and reviewer's decision stay with the record.
Room cleaning
Set the checklist in the equipment record for the relevant room, and the photo, signature and review requirements in its linked checkpoint. The employee saves the result; configured consumables are deducted only through a separate authorized selection in the form.
Equipment maintenance
Place assets on the map and save models, instructions and intervals. Review calculated dates and completed-work history to identify the next step and find information about the specific asset.
These are workflow examples, not customer case studies or promised outcomes.
Requirements and boundaries
Compatibility is checked for your equipment
The interface includes Tuya / Smart Life, Home Assistant and a limited SmartThings connection option. Compatible devices, a prepared hub or project and appropriate access are required. This is not universal support for every brand, Matter or Zigbee, nor a promise of reachable control for every switch. Device does not replace a regulatory audit, qualified maintenance or a safety assessment.
FAQ
The important
questions.
Is this a hardware catalog or a working application?
SABSUS Device is a software workspace for spaces, equipment, checkpoints, readings and inspection history. Hardware selection and supply are separate tasks; the Hardware page explains the wider SABSUS device context.
Can we start without sensors?
Yes. An employee can enter readings, complete a checklist and attach the required evidence manually. External sensors are connected separately, subject to equipment and hub compatibility.
Does a QR code prove the employee was on site?
No. A QR identifies the checkpoint and opens its authenticated form. Scanning alone does not prove presence, complete the inspection or automatically trigger all linked actions.
Will any smart sensor work immediately?
No. Check the model, available provider or compatible hub, connection setup and readings. A protocol or brand name in an ecosystem does not establish direct universal SABSUS support.
Do records and signatures guarantee compliance?
No. The log and a drawn signature help document a process, but do not guarantee HACCP, ISO or other regulatory compliance. Requirements, qualified signatures and safety controls must be determined separately for your operation.
Start with your task.
Not another interface.
Explore the right workflow, required connections and access boundaries for your scenario.