Please enable JavaScript.
Coggle requires JavaScript to display documents.
Zara IT for Fast Fashion - Coggle Diagram
Zara IT for Fast Fashion
Integration: How solution addresses problems and enables operations
Requirements
Training and updated SOPs for store staff.
Security and device management for transactions over Wi‑Fi.
Staged rollout with pilot stores, QA, and developer support.
Component Interactions
Handhelds: PDAs/handhelds connect locally for ordering and stock checks.
POS-Wi‑Fi: Linux POS uses Wi‑Fi for real-time inventory and device access.
Central systems: Continuous telemetry replaces floppy/modem batch uploads.
Proposed Solution: Phased migration and network enablement
Proposed Solution: Phased Porting to Linux with Wireless Network
Cost/feasibility: Estimated ~€5.65M covering development, hardware, and rollout.
Benefits: Reduces vendor lock-in, lowers license costs, enables real-time inventory and new features.
Strategy: Port POS to Linux and deploy in-store Wi‑Fi via phased pilots.
Technical changes: Replace DOS dependencies with POSIX-compatible code, add Wi‑Fi, VPN, and device provisioning.
Risks: Significant development effort, migration disruption, requires pilots and rollback plans.
Discussion Focus: Group agenda and next steps
Implementation details
Assign roles: project lead, dev/QA, store ops liaison, security owner.
Run phased pilots with incremental features and feedback loops.
Plan stakeholder communication, vendor talks, and training schedules.
Purpose and Function
Validate the €5.65M estimate, timeline, and feasibility.
Select pilot stores and define rollback contingencies.
Define success metrics: uptime, inventory accuracy, and time-to-shelf.
Key Problems: IT/technical and operational issues
Problem 3: Inefficient Data Collection
Characteristics: Floppy/modem-based manual uploads.
Impact: Error-prone, non-scalable reporting.
Root cause: Legacy practices & underinvestment in networking.
Problem 1: IT/Technological Obsolescence
Characteristics: Obsolete DOS and aging hardware.
Root cause: Uptime-first culture, costly porting & expansion risk.
Impact: Increased maintenance, vendor lock-in, limited upgrades.
Problem 2: Lack of Real-Time In-Store Data
Impact: Slower, suboptimal replenishment and sales decisions.
Root cause: Transaction-focused legacy POS forces manual workarounds.
Characteristics: POS lacks live inventory; managers lack visibility.
Preparation & Context: Core strategy and environment
Timeline: Key milestones and debates
1995: PDAs replaced fax for in-store ordering.
2003: POS upgrade debate highlighted resistance to change.
1975: First store; origin of Zara's speed model.
Purpose and Function
Store autonomy: Managers set local assortments and replenishment.
Core Strategy: Fast, frequent design-to-shelf cycles and decentralized store decisions.
Vertical integration: Controls design, manufacturing, and retail.
Relevant Facts: Current in-store systems and practices
No real-time inventory lookup; PDAs used for ordering.
Manual daily reporting via floppy/modem, limited network infrastructure.
Legacy POS: DOS-based system prioritizes stability over features and change.