Time records and an organized shift

Yes: from transferring selected lines into production to routes, stages and recorded results. Record good output, scrap and quantities awaiting review; a responsible person decides quality and rework. A stage’s output does not itself fulfill the customer order.

An authorized person records the reason and confirms a transfer within the site. Shift parts stay linked and time remains attributed to its workplace. The continuation keeps source pay terms and pins its own checklist. Active production participation must end first; permanent personnel placement stays unchanged.

Yes, in the separate Salary section. Approved rates and recorded paid time feed the period calculation. Record payments that happened and review balances and history. Recording a payment does not transfer money; statutory taxes and banking remain in accounting.

A maintenance plan links equipment, an assignee and materials. Mechanics see their work in Telegram and submit results. An authorized person reviews completion in the panel; returning equipment to service requires their decision.

Import structure and employees from XLSX or CSV. Map fields and review the result before confirming. Each file has one site and effective date. Historical time records, payroll migration and live ERP synchronization are outside this import.

Explain procedures using the documentation. It cannot inspect company records, change data or make management decisions. Generated answers depend on a connected AI service; common answers and the Learning Center help explain panel actions.

It combines prevention and response: schedules expose staffing gaps, checklists define preparation standards, handovers preserve zone condition, notifications bring in the responsible person, and reports reveal recurring reasons. Results depend on team action and are evaluated in a pilot.

Shift-based production where attendance, work-zone readiness, a master’s response and handover matter. A pilot can focus on one unit, zone and specific process.

The kiosk displays a QR for arrival and departure. Workers confirm actions and manage their shift in Telegram. Masters use the same records in the web panel for attendance, incidents, reports and decisions.

Workers manage shifts, view personal schedules and open slots, report problems and submit requests. Their specialty can also provide maintenance work, checklists and help. Actions depend on state, access and configuration.

Yes, when this shift has no pinned required checklist. Telegram closes the shift and records departure and the time summary. With a required checklist, the worker completes cleaning and submits the report, then closes through the exit QR. The obligation belongs to the session; later configuration changes do not remove it. Supervisor closure with a comment and rule-based automatic closure remain available.

Plans and alternatives, zones, several shifts per day, absences, coverage, open slots and offers to workers. Check availability and skills before selecting a person. Publishing notifies workers of plan changes. A schedule does not replace actual time records.

A worker reports it through the bot and the responsible person is notified. The panel shows the state, reason and response history. Configured reminders and escalation rules apply to overdue responses.

Workers prepare the zone, complete their position’s checklist and add required photos. A master reviews the material and approves or records a concern. The next shift sees the handover and records zone acceptance.

Yes. Administrators define items, required photos and review rules, then link a checklist to a position. Versions preserve the requirements used for earlier reports.

Photo-review results assist review. The master remains responsible for the report decision and observations. We do not promise infallible automated cleanliness detection.

Losses, people, money and data completeness within your authorized scope. Open unit, worker or shift drilldowns and use the available export. Missing evidence is separate. Output and quality live in the production module and do not establish automatic OEE.

Bonus covers points and scoring history. Salary covers approved terms, recorded time, period calculations and payment records. Your company defines cash-bonus rules. Recording a payment does not transfer money, and the system does not calculate taxes.

Workers submit requests such as leave or corrections in Telegram. Responsible people review them through approval stages in the panel, recording decisions and comments with history.

Yes. Select recipients, prepare text, add supported attachments or a questionnaire, and send through Telegram. Sent messages can be reviewed.

Access depends on assigned roles and responsibility scope. Administration manages people, roles and terminals; audit records help inspect changes. We will review permissions for your structure during the demo.

The kiosk is a web page on a prepared browser-equipped screen; workers use Telegram and managers use a browser. Device compatibility is checked before a pilot. Machine connections, ERP/MES integrations and automatic OEE are not advertised as ready capabilities.

Telegram, current QR codes and communication with the panel require connectivity. We do not promise a full offline mode. A fallback workflow and permitted master actions are agreed for the pilot.

The interfaces are illustrations with fictional data. They explain Vakhta workflows; the real interface evolves and may differ. Factory scenes are licensed footage. They are not customer testimonials or evidence of measured savings.

Select a process and zone, record the baseline and agree success criteria. Review record completeness, response time, recurring incidents and handovers. No downtime-reduction percentage is promised in advance.