Close
Contacts
Find out how we can help you. Fill out the form to start a new project or email us at info@halikov-studio.ru
Close
Tell us
about your project
Attach file
Client:  Semya Shopping Mall · Launch year: 2017 · Type:  Enterprise / B2B web-system · In industrial operation 8 years

FSM system for electronic approvals
at a major shopping mall in Ufa

We developed a Field Service Management platform for Semya Shopping Mall. It replaced paper-based work permits, automated contractor access through security checkpoints, and brought communication with 80+ tenants into one interface. The system has operated continuously for eight years.

In use
8  years
from June 2017 to present
Role model
10+ roles
with its own set of rights and conditions
Applications per year
3 200+
permits for work
Uptime
99.98%
for last 12 months of work
01 · Client

Semya Shopping Mall is one of the largest shopping and entertainment complexes in the Republic of Bashkortostan

Works in Ufa since 2003  . Three floors of retail, tens of thousand square meters, a cinema, a food court and a children's center. Every day there are thousands of visitors and dozens of contractor teams working for tenants.

Opening of the shopping center2003
Square45,000 m²
Tenants80+
checkpoint4 points
LocationUfa, Oktyabrya Ave. 34
Websitesemya.shop
02 · Task

From paper chaos to a transparent workflow

Until 2017, approval of any work on the territory of the shopping and entertainment complex was carried out on paper. The application went through 7–10   approvers - was searched manually, got lost, got stuck for week. What was needed was a system that would cover the entire process in one circuit and would not require IT training from users.

● It was

Before: paper-based approvals

  • The application was carried from office to office physically - from 3 to 10 days
  • There is no history of - it is not clear who has the document now and why it is
  • Applications were lost, versions were confused, copies multiplied
  • checkpoint passed on paper sheet - fakes, outdated passes
  • Communication with tenants - by telephone, without fixation
  • No reporting - it is impossible to understand how much work was completed in month
● Became

After: the FSM platform

  • The application is approved within 4–24 hours (previously 3–10 days)
  • Full history and event log for each application
  • Single source of truth - versions, copies, drafts eliminated
  • checkpoint checks permission by number - impossible to fake
  • Communication with tenants within the system - everything is recorded
  • Analytics in real time - reports, dashboards, export
03 · Role architecture

Three user groups, more than ten roles

The role model is built around the central object - “Permission to work”. Each role has its own set of rights that are valid under certain conditions (document status, authorship, workflow stage).

How roles interact in the FSM system

single permit route
Initiators
Tenant
80+ users
Contractor
200+ contracting organizations
Technical department
12 engineers
create
application
Coordinating
Core · Workflow
Permit for work
Landlord
Management company
Ch. engineer
Technical approvals
Deputy Director of Security
+ issue of checkpoint number
Firefighter inspector
Fire work
transmit
permission
Performers and control
Security service / checkpoint staff
Pass to territory
  site engineer
Control in process
Receiver
Acceptance of completed work
  System Administrator
Full access, audit
Initiators create application Coordinating is checked one by one Performers supervise the work Workflow stores status, history and permissions
04 · Approval workflow

Every request follows a defined approval path

The requisition can be created by a tenant, contractor, or technical department. Next, is sequential coordination along the chain of roles. Any participant can send a revision of to - the author receives a notification and edits.

STEP · 01
Request creation
The author fills in the type of work, area, dates, crew composition, PPE
Tenant / Contractor
STEP · 02
Initial review
Management company checks the completeness and correctness of the data
Landlord
STEP · 03
Technical review
Ch. the engineer coordinates the impact of the work on communications of the fuel dispenser
Ch. engineer
STEP · 04
Security and access
The Deputy Director of Security determines and records the checkpoint number
Deputy Director of Security
STEP · 05
Hot-work approval
Fire inspector - optional, for relevant types of work
Fire inspector
STEP · 06
Final approval
The permit is issued, the author receives a notification, security sees the document at checkpoint
Ready
Any approver can return the application for revision - it goes to the author in status"for revision" Average timepassing the full route —18 hours
05 · Permissions matrix

Who can do what in the system

Each right is checked at two levels - user role and object state (application status, authorship). Below is the basic matrix for 3 main roles.

Role
Create
Edit.
Delete
Approve
Print/PDF
Activity log
AAdministrator
L Landlord
T Tenant
S Deputy Director of Security
EChief Engineer
Full access Conditional access (by status or authorship) No access
06 · Key roles

Three roles, three levels of responsibility

Below is an excerpt from terms of reference, implemented 1 in 1 in production since 2017  .

A
Administrator
FULL_ACCESS system
  • Creating permits for work
  • Editing permissions (all)
  • Remove permission (all)
  • Negotiate permissions (all)
  • Viewing the Event Log
  • View created permissions (full list)
  • Print and save permission to PDF
Restrictions: Users:3
L
Landlord
MANAGEMENT management company
  • Creating permits for work
  • Removing permission only unapproved and created by the user himself
  • Permission Negotiation if the algorithm requires approval from the user
  • View created permissions (full list)
  • Print and save permission to PDF
Restrictions:by status and authorship Users:12
T
Tenant
SELF_SERVICE · external user
  • Creating permits for work
  • Editing Permissions only unapproved in status"for revision", created by the user himself
  • Removing permission only unapproved and created by the user himself
  • View permissions only created by the user himself
  • Print and save permission to PDF
Restrictions:only your documents Users:80+
Key workflow rule

The Deputy Director of Security assigns the access checkpoint during approval

This is not a technical parameter - it is the decision of the person in charge. The system strictly links the contractor's pass to a specific entry point, time and crew. The security service at the checkpoint sees the permit number and does not let anyone through without a valid document.

Active passes now · checkpoint online
Checkpoint No. 1 · October Avenue
Passes: 4
Active
Checkpoint No. 2 Service
Passes: 12
Active
Checkpoint No. 3 Landing stage
Passes: 8
Active
Checkpoint No. 4 Technical
Passes: 2
Active
07 · Capabilities

What the system can do

A complete set of functions for permission lifecycle management from creation to archive.

/ 01

Create work permits

Form with 30+ fields: type of work, area, dates, crew composition, personal protective equipment, hot work, noisy work.

POST /permits
/ 02

Editing

Edits only while document is in status"for revision". After approval - only through the administrator.

PATCH /permits/:id
/ 03

Controlled deletion

Unapproved permissions only and by author or administrator only. Completely removed from the system.

DELETE /permits/:id
/ 04

Sequential approval

Each role sees only those requests that are awaiting its approval. One click - “agree / on revision.”

POST /permits/:id/approve
/ 05

Print and PDF

Printed form according to fuel dispenser standard. Saving in PDF - for archives, lawyers, security.

GET /permits/:id/pdf
/ 06

Activity log

Full history of each permit: who created  , who approved  , who sent for revision. With timestamps.

GET /permits/:id/audit
/ 07

Communication with tenants

Built-in chat for each application. Notifications in email and in interface when status changes.

WebSocket
/ 08

Operations dashboard

Dashboard with active applications awaiting approval, and progress statistics for roles.

/dashboard
/ 09

Roles and rights

Fine-tuning rights: role + conditions (application status, authorship, stage). Check on backend.

RBAC
08 · Technology stack

A proven enterprise technology stack

A stack running for 8 years without a single downtime. Supported, updated, without exotics.

Frontend
  • Vue.jsSPA
  • Vuexstate
  • Vue Routerrouting
  • AxiosHTTP
  • Element UIcomponents
Backend
  • PHPruntime
  • Laravelframework
  • Eloquent ORMdata
  • PassportOAuth 2
  • QueueRedis
Data and storage
  • MySQL 8main database
  • Rediscache + queues
  • S3-jointfiles
  • ElasticSearchfull text
Infrastructure
  • Dockercontainers
  • Nginxreverse proxy
  • Let's EncryptSSL
  • Zabbixmonitoring
  • Daily backupoff-site
09 · Results

Eight years in production, measured in results

The system was launched in June 2017 and operates on today. Below are key metrics for the operating period.

Approval time
−92%
It was 3–10 days, now it is 4–24 hours. Acceleration on average 12 times.
Requests processed
25 600+
Permits for work went through the system for 8 years.
Uptime
99.98%
Downtime for year - less than 2 hours, always according to scheduled regulations.
Paper saved
180 000  sheets
Applications are printed only for checkpoint - the rest is electronic.

Before FSM, had accumulated folders with paper applications, some were lost, some were forgotten. Now the process is 100% transparent: any request is visible to everyone, the history is saved, security at the checkpoint allows only with valid permission.

Operation service of the shopping and entertainment complex "Family"
· Ufa, semya.shop

Need a similar system for your business?

We develop internal automation systems for shopping centers, factories, distributors and developers. We design, implement and support.