One platform to run warehouse operations across all six HIRA plants.
An interactive walkthrough of the Warehouse Management System Silwatech has designed for HIRA Industries. It moves through the architecture, integrations, security, delivery plan and cost in the order your engineering team reviews them, with the working product one click away.
A warehouse platform, engineered for how HIRA actually operates.
HIRA Industries runs one of the region’s largest insulation and MEP manufacturing operations, with brands such as Aerofoam, Aeroduct and Rubtech produced across more than sixteen facilities worldwide. This programme targets the six UAE plants, replacing manual and disconnected warehouse steps with one scan-driven platform while SAP remains the system of record.
Every stage of the material lifecycle is brought into a single flow: supplier deliveries are received and verified against purchase orders, quality holds are managed, stock is put away by bin, production is issued and received, and finished goods are picked, dispatched and returned. Each movement is tracked by QR and LPN so inventory stays accurate and fully traceable across all six sites.
The result is real-time visibility for managers, guided tasks for supervisors and operators, and clean, reconciled data flowing back to SAP without re-keying.
Delivered by Silwatech
Enterprise software engineering for mission-critical operations, with more than two decades of delivery across the UAE, GCC, Europe and Africa.
Three surfaces, one system of record.
The platform spans a web portal, a supervisor tablet app and an operator handheld app. All three write to one NestJS backend that stays continuously in step with SAP, so the floor and the ERP never drift apart.
Web Portal
Super Admin, Warehouse Manager and Supervisor
Administration, inventory monitoring, master data, configuration and reporting across every plant.
Supervisor Tablet
Supervisor on the floor
Plan, assign, monitor and close warehouse operations, from receiving through dispatch.
Operator Handheld
Operator executing tasks
Simple, scan-driven execution of assigned work with confirmation at every step.
One continuous, scan-driven lifecycle from the receiving dock to outbound dispatch and returns.
Manages the WMS across all companies and warehouses.
Oversees operations, inventory and approvals.
Creates transactions, assigns and reviews work.
Executes assigned tasks with QR and LPN scanning.
Ten operational domains, one coherent system.
Scope is organised into functional domains that map directly to warehouse activity. Select a domain to see what it covers and where it runs.
Inbound Operations
Receive supplier deliveries, verify incoming materials against purchase orders, and handle partial, damaged or excess goods.
The whole solution, on one diagram.
Three applications, one NestJS backend, one PostgreSQL database, and every external system it touches — all hosted on AWS. Select any block to see what it does and the technology behind it.
Select any block on the diagram
Every component above is explained here: what it does, why it is there and the technology behind it. The flow reads left to right — devices, the AWS entry path, the application core, the data it owns, and the systems it integrates with.
Three applications, three architectures.
The portal, the tablet and the handheld are separate products with separate constraints, so each one gets its own architecture rather than a shared summary. Select an application to open its stack.
Web Portal Architecture
The control tower. Fifteen module areas covering administration, master data, monitoring and reporting across all six plants, server-rendered so heavy management screens open fast.
Every screen area this application exposes, straight from the approved sitemap.
One design system
Web, tablet and handheld are built from the same Figma design system and component vocabulary, so the platform reads as one product.
One API contract
All three clients consume the same versioned REST contract and the same socket events, so behaviour never diverges between screens.
Role-shaped surfaces
Each application exposes only what its roles need, which keeps the operator app simple without limiting the portal.
Modular NestJS services, and a movement that cannot post twice.
Every request follows the same guarded path: gateway, validation, guards, domain rules, then one atomic transaction. Thirteen isolated modules mirror the warehouse domains, and SAP, GPS and printing stay behind an integration boundary so external systems never leak into business code.
Each operational domain is an isolated NestJS module with its own controllers, services and rules. Modules talk through explicit interfaces, never through shared state, which keeps the system straightforward to test, extend and reason about.
Each external system sits behind its own adapter with its own contract, retry policy and failure handling. SAP posts go out through the outbox with backoff and a dead-letter queue that can be replayed, so a BTP outage delays a sync without ever losing a movement.
Idempotent by design
Every write carries an idempotency key, so a retry after a dropped connection can never post the same movement twice.
Stateless services
No session state lives in the application, so instances scale out horizontally behind the load balancer without sticky routing.
SAP stays the system of record
The WMS writes movements back and reads master data, but never overrides SAP financial truth.
Failure is contained
An external system going quiet degrades one adapter, not the warehouse floor. Work queues and replays when it returns.
Connected to SAP, without becoming SAP.
SAP remains the system of record. The WMS synchronises master data and transactions through SAP Integration Suite (BTP), layers in live GPS tracking from Smarttech, and prints labels directly to network printers. Nothing is re-keyed.
rHIRA WMS
Master data in, transactions back, continuously reconciled
Data exchange is grouped into five areas, covering the full inbound to outbound cycle.
Master Data
Inbound
Production
Inventory
Outbound
Integration assumes HIRA provides SAP Integration Suite (BTP) connectivity and that the required SAP business objects are available through standard APIs. Any custom SAP development is assessed during the integration discovery phase.
Defence in depth, then everything we add on top.
The AWS layers below are the baseline: network isolation, a firewall at the edge and encryption in transit. What matters more for a warehouse record is what sits above them — the access, application and audit controls written specifically against HIRA's roles, plants and workflows.
Designed to stay fast as volume grows.
Performance is engineered across the whole path: rendering and caching at the front, a load balancer and stateless services in the middle, live sockets for instant updates, and continuous monitoring with load testing before go-live.
Fast dashboards
Server-side rendering and edge caching keep management views quick to load.
Responsive APIs
Stateless services and tuned queries keep interactions snappy under load.
Real-time updates
Task assignment and alerts push instantly to tablets and handhelds.
Scales on demand
Horizontal scaling behind the load balancer absorbs peak-hour volume.
The techniques behind the targets.
Targets above are design goals, confirmed and tuned during the performance and load testing phase, which is a formal deliverable of the project.
AWS foundations, deployed to HIRA’s account.
Production runs in HIRA’s own AWS account, so ownership and data residency stay with the business. Silwatech maintains dedicated development and QA environments throughout delivery. Beneath the applications sit the AWS building blocks: EC2 compute for the backend services, a managed PostgreSQL database, and the isolation, security, delivery and recovery services around them.
Development
Active build and continuous integration during each sprint.
QA / Staging
Controlled pre-production testing and release validation.
Production
Multi-AZ, high availability, monitored and backed up.
HIRA provides the production AWS account, the production application and database servers, domain and DNS, SSL certificate, SMTP, and the backup, disaster-recovery and cloud security policies, along with recurring cloud costs. Silwatech provides application deployment, environment configuration and release support.
Planned like Waterfall, delivered like Agile.
High-level phases are planned up front for predictability, then execution runs in short sprints with QA built into each one. HIRA sees working software early and often, and change is absorbed without derailing the plan. Select a phase to see its deliverables.
Discovery
Validate business requirements and technical foundations before building.
AI accelerates the build. Engineers own the outcome.
Silwatech uses AI across the delivery lifecycle to move faster and hold patterns consistent, with human review, security scanning and IP-safe practices wrapped around everything that ships. It compresses timelines without touching the continuous QA that protects quality.
Scaffolding and boilerplate
NestJS modules, Flutter widgets and Next.js pages generated to the team’s own standards, so engineers start from structure, not a blank file.
Test generation
Draft unit and integration tests produced alongside features, lifting coverage without slowing the sprint.
Code review assist
AI-assisted static analysis flags issues and inconsistencies before they reach human review.
Integration mapping
Faster mapping of SAP business objects and adapter stubs, reviewed and hardened by the integration team.
Documentation
Functional specs, API references and release notes drafted directly from the codebase and kept current.
Requirements to backlog
Discovery notes turned into structured, estimable backlog items for the team to refine.
Shorter timelines, steadier quality.
Routine work is accelerated so senior engineers spend their time on architecture, integration and the edge cases that actually carry risk. Delivery speeds up while QA stays continuous.
Twenty-six weeks, five milestones, one go-live.
A hybrid plan with overlapping workstreams and UAT checkpoints along the way. Fifteen specialists run requirement analysis, web and tablet development, integration, hardware installation, QA and deployment in parallel wherever it is safe to do so. Hover any bar for its timing.
A dedicated fifteen-person team across engineering, design, QA and DevOps.
Schedule and milestone dates are indicative and refined during the Discovery phase.
Where the platform goes once the data is flowing.
Once the core is live and SAP-synced data is stable, the same platform becomes the foundation for AI that removes manual decisions on the floor. These are future ideas, sequenced after go-live and refined with HIRA, not part of the current scope.
A warehouse platform now, an intelligent one next.
The architecture, data model and integrations in this walkthrough are built so these capabilities can be added without re-platforming.
See the working product, not just diagrams.
The interactive demo puts the actual interface in front of the team: the web control tower, the supervisor tablet and the operator handheld, driven by realistic warehouse data.
Launch the interactive demo
Opens the clickable prototype in a new tab so the team can move through the real screens at their own pace during the meeting.