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.
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.
DEMO_URL in src/data/content.ts.One request path, from rugged device to SAP.
Everything runs on AWS. Clients reach the platform through CloudFront, WAF, a load balancer and an API gateway, in front of modular NestJS services that own the business logic and talk to PostgreSQL, S3 and the integration layer. Select any component to see its role.
Explore the architecture
Select any component above to see what it does and the technology behind it. The flow reads left to right: client devices, edge and delivery, application services, data stores, and the external systems they integrate with.
A fast web portal and two field apps, from one design language.
Next.js powers a server-rendered portal built for speed and secure data access. Flutter powers the tablet and handheld apps from a single codebase, tuned for rugged Android devices and scan-first workflows. Both draw from the same Figma design system, so the platform feels like one product.
Web Portal
Tablet & Handheld
Built for speed
Server-side rendering and edge delivery keep the portal responsive even over plant networks.
One design system
Shared components and Figma handoff keep web, tablet and handheld visually and behaviourally consistent.
Field-ready
Large targets, minimal steps and scan-driven confirmation designed for gloved, one-hand operation.
Modular NestJS services with SAP-safe transactions.
The backend is a modular NestJS application whose modules mirror the warehouse domains. Every stock movement is processed as a consistent, auditable transaction against PostgreSQL, and integration is isolated behind its own layer so SAP and GPS never leak into business code.
Each domain is an isolated NestJS module with its own controllers, services and rules, which keeps the system easy to test, extend and reason about.
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, from the edge to the record.
Security is layered rather than bolted on. Network isolation and a firewall sit at the edge, transport is encrypted end to end, the application enforces JWT and role-based access, and the infrastructure runs on least-privilege IAM. Silwatech operates an ISO 27001 certified information security programme.
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 for isolation, security, delivery and recovery.
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, domain and DNS, SSL certificate, SMTP, and backup and disaster-recovery policy, along with recurring cloud costs. Silwatech provides deployment, environment configuration and release support.
An indicative monthly AWS run rate.
A model to frame budgeting, based on the proposed AWS services in the UAE region. Production runs Multi-AZ for high availability and non-production is lighter. Adjust the workload to see how the run rate moves. Final figures are confirmed during infrastructure sizing.
Development + QA
HIRA AWS account
USD, UAE region, on-demand pricing. Reserved commitments can reduce production compute and database costs materially.
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. Eleven 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 eleven-person team across engineering, design, QA and DevOps.
Schedule and milestone dates are indicative and refined during the Discovery phase.
The questions a technical team tends to ask.
Direct answers to the topics that usually come up in an architecture review. The live discussion goes wherever your team wants to take it.
SAP remains the system of record. Master data and transactions synchronise through SAP Integration Suite (BTP) on a mix of scheduled and event-based flows. The WMS reads what it needs and writes movements back, but it never overrides SAP financial truth.
The scan-first workflows are built to tolerate brief connectivity gaps. Actions queue on the device and confirm on reconnect, and critical confirmations are idempotent, so a retry never double-posts a movement.
The web portal needs server-side rendering, fast first load and a rich admin interface, which is where Next.js is strong. The tablet and handheld apps need native-grade performance on rugged Android from a single codebase, which is where Flutter is strong. A shared design system keeps all three consistent.
JWT authentication with role-based access control for Super Admin, Warehouse Manager, Supervisor and Operator. Accounts lock after repeated failed logins, sessions are managed centrally, and infrastructure access runs on least-privilege IAM under an ISO 27001 programme.
Backend services are stateless and scale horizontally behind the load balancer. PostgreSQL runs Multi-AZ in production, CloudFront serves assets at the edge, and the whole path is validated under typical and peak load before go-live.
Production is deployed to HIRA’s own AWS account, so data ownership and residency stay with the business. Silwatech maintains the development and QA environments and handles deployment and release support.
Integration assumes BTP connectivity and that the listed SAP business objects are reachable through standard APIs. Any custom SAP development or unavailable interface is assessed during the integration discovery phase.
Every AI-assisted change goes through human review, security and licence scanning, and no HIRA data or secrets are shared with external tools. SAP integration and production logic are always human-validated, and continuous QA runs exactly as it would without AI.
Two months of complimentary bug support follow go-live, with monitoring and stabilisation. A separate twelve-month Annual Maintenance Contract is available if HIRA wants ongoing support beyond that.
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.