How ESAAB goes live

An operational layer over the existing systems

ESAAB is not a system that replaces the ERP or the logistics operator: it is the operational layer that sits on top of them and keeps them aligned. That defines how it is deployed.

• A web platform, no per-seat installation ESAAB runs from the browser on workstations and from handheld scanners on the warehouse floor. It requires no software install on each user's machine; access is managed centrally.
• A layer over the existing systems ESAAB connects to the ERP, the logistics operator (3PL) and suppliers, and becomes the single operational source of truth for consumption, replenishment and reception. Purchasing processes and accounting close stay in the institutional systems.
• Multi-warehouse and multi-organization from the start The platform segregates data by warehouse and by company or organization. A health network or a lab with several sites can run all its warehouses on a single instance, with consolidated visibility and isolation per unit.

Discovery, pilot and go-live

The operation is not switched on all at once. Implementation advances in phases to lower risk and validate each step with the client's team before scaling.

• 01 Discovery The real operation is surveyed: warehouses, consumption and replenishment flows, critical supplies, minimum-stock rules and the connection points with the ERP and the 3PL. The output is an agreed scope and a master-data map.
• 02 Pilot ESAAB is enabled on a contained scope —one warehouse, one area or one supply line— with real data. This is where rules, locations, roles and the handheld workflow are tuned before extending to the rest.
• 03 Go-live (rollout) Once the pilot is validated, it scales to the remaining warehouses and organizations. Each onboarding reuses the configuration proven in the pilot, so the rollout is incremental and predictable.
• 04 Stabilization After the rollout the first operating cycles are accompanied, alerts and minimums are fine-tuned against real behavior, and the team's adoption is consolidated.

What it takes to get started

A good implementation depends as much on the platform as on the inputs the client's team provides. Here is what is asked for a solid go-live:

• Master data The product and supply catalog, the warehouse and location structure, and users with their roles. This data can be loaded in an assisted way —including file import— so there is no dependence on bulk manual entry.
• Access to ERP and logistics operator (3PL) The connection points with the ERP and the 3PL to align catalogs, reconcile inventory and coordinate orders and dispatches. Where no API exists, an assisted file-load mechanism is provided.
• Business rules: minimums and criteria The rules that define replenishment —minimum stock per item, priorities, expiration criteria and cross-catalog equivalences— so that ESAAB turns consumption into correct requirements from the start.

How success is measured

Success is not switching the system on, but the team using it and the operation improving. The implementation is accompanied with indicators and ongoing support.

• Adoption indicators Real usage is tracked: consumption recorded at the point of use, replenishment generated from the system and reconciled receptions. Team adoption is the first sign that the implementation is paying off.
• Post-implementation support After go-live, support and fine-tuning are maintained —rules, alerts, reports and new users or warehouses— so the platform evolves with the operation, not against it.

An implementation proven in real operations

ESAAB is not implemented for the first time on every project: its engine has been in production for years across mining, agribusiness, logistics and healthcare companies in Chile, Bolivia, Argentina and Colombia. That multi-warehouse, multi-organization deployment experience is what is applied in each new go-live — including the clinical edition ESAAB SmartLab for labs and health networks.