Business Requirements Document · Post-Implementation
Cutting Traceability
System
End-to-end QR traceability across all cutting operations at 2 factories and 11 cutting floors. Replaced manual tracking with real-time roll-level, operator-level, and process-level visibility.
Organization
Snowtex Group
Scope
2 Factories · 11 Floors
Start Date
January 2025
Duration
4 Months
FRAMING · This document covers the traceability design, deployment challenges, and outcome assessment for the Cutting Section QR project. The core deliverable was traceability: the shift from no fabric visibility to full roll-level accountability at every stage of the cutting lifecycle. Production figures and volume data are directional. Operator-level personal data is withheld per company policy.
SUSTAINING
CS-CT-002 · v1.0 · FINAL
§1
Project Context & Problem Statement
The Baseline Problem

The organization had an OEE framework for machine-level performance, but the cutting department had no process traceability. Operational data was recorded by hand and scattered across multiple process points. Fabric consumption could not be checked against marker requirements. End-bit generation had no accountability structure. WIP movement between stages was invisible in real time. Operator productivity was estimated manually and assessed subjectively.

The project mandate was to implement a fully digital traceability system across all cutting operations, establishing end-to-end visibility for every fabric roll throughout the cutting lifecycle and capturing process-level production data in real time.

2
Manufacturing factories covered
Full deployment scope
11
Cutting floors across 2 factories
All floors in scope
4 mo
Kickoff to go-live, full end-to-end implementation
2 factories · 11 floors · 7 report types
7
Automated report types replacing manual consolidation
Daily, real-time, per-style
Before / After. The Traceability Transformation
Operational AreaBeforeAfter
Fabric Traceability Zero, no roll-level visibility at any stage of the cutting process Full end-to-end, every roll tracked from store entry through relaxation, spreading, cutting, bundling, and QC
Consumption Visibility Not visible, actual fabric usage against CAD marker requirements could not be measured Visible, style-wise actual vs theoretical consumption tracked at roll level per lay
End-bit Accountability Untracked, residual fabric lengths disposed of or reused without records Tracked, every residual length digitally allocated, recovery purpose recorded, utilization history maintained
WIP Visibility Not available in real time, bundle status known only at end-of-shift reconciliation Live, bundle status, stage location, and throughput visible across all 11 floors in real time
Operator Performance Subjective, productivity assessed by supervisor estimation without objective measurement Objective, individual input minutes, process output, and efficiency percentage captured per activity
Production Reporting Manual, significant consolidation effort per floor before management visibility was available Automated, all 7 report types generated directly from scan data with zero manual consolidation
Operational Challenges. Pre-System
Challenge AreaOperational ImpactRoot Cause
Fabric ConsumptionCould not validate actual usage against CAD marker requirementsNo roll-level data capture at spreading stage
End-bit ManagementHidden wastage and fabric leakage from untracked residual lengthsNo accountability system for end-bit generation or reuse
WIP VisibilityNo real-time view of material movement between cutting stagesManual recording only, delayed and incomplete
Operator ProductivitySubjective, unreliable efficiency measurementNo individual-level digital activity capture
Daily ReportingExtensive manual consolidation required before management visibilityNo automated data aggregation capability
Consumption VarianceCould not isolate variance to specific process points or stylesNo style-wise or stage-wise consumption tracking
Planning CoordinationStore and planning teams lacked live production visibilityNo integration between floor operations and planning systems
Stated Objectives
  • Establish end-to-end visibility for every fabric roll throughout the cutting lifecycle
  • Capture process-level production data in real time via QR scanning at every operational stage
  • Measure actual fabric usage against CAD marker requirements and surface variance by style
  • Track operator-level productivity and efficiency objectively across all processes
  • Enable structured end-bit management and measurable wastage recovery
  • Automate production reporting and real-time WIP visibility with zero manual consolidation
  • Provide reliable, traceable data inputs for Performance Incentive Bonus (PIB) calculation
  • Standardize operational discipline through mandatory digital process checkpoints
§2
System Architecture & Process Design
System Architecture. End-to-End Flow
📦
Store → Cutting
Roll scanned at entry. Identity and specs transferred.
🛏️
Relaxation
Roll scanned to table. Duration and location tracked.
📐
Spreading
Per-roll scan in every lay. Actual vs marker consumption captured.
✂️
Cutting
Operator and machine linked. Input minutes and output recorded.
🗂️
Bundling
Bundles digitally created and tagged for downstream WIP traceability.
🔍
QC
Bundle compliance verified. Defect linkage and output approval recorded.
Process Flowchart
Cutting Process Flowchart
QR-Tagged Production Entities
Fabric Rolls Operators Cutting Tables Machines CAD Markers Bundles Process Stations
Roll QR — Data Structure

Each QR code on a fabric roll carried structured production data needed at the point of scan. Every field was agreed through requirements sessions with warehouse management, cutting supervisors, and QA. Nothing was included unless a specific downstream workflow required it.

Roll Length Width Shade Fabric Construction Identification References
Process Traceability Framework. Data Captured at Each Stage
📦
Store → Cutting Entry
  • Roll identity
  • Fabric width & roll length
  • Shade information
  • Fabric construction
  • Entry timestamp
🛏️
Relaxation
  • Table assignment
  • Roll location
  • Entry time
  • Process duration
📐
Spreading (Auto & Manual)
  • Roll usage by lay
  • Marker association
  • Actual fabric length consumed
  • End-bit length per roll
  • Operator involvement
  • Machine association
✂️
Cutting (Auto & Manual)
  • Operator identification
  • Machine identity
  • Input minutes
  • Production output
  • Timestamp records
🗂️
Bundling & Numbering
  • Bundle identity
  • Style information
  • Quantity
  • Process linkage
  • WIP status
🔍
Quality Verification
  • Bundle compliance status
  • QC verification records
  • Defect linkage
  • Output approval

End-bit Management: Residual fabric lengths digitally tracked and allocated for reject panel replacement or short-marker production. Reallocation purpose, utilization history, and recovery tracked per roll, eliminating previously untraceable end-bit loss and establishing measurable wastage recovery control.

Design Decisions. With Rationale
D1
Mobile application as the primary operational interface A purpose-built mobile application was developed to minimize disruption to production flow while maintaining mandatory data capture at every stage. The interface was designed for low operational complexity and high scan compliance, prioritizing usability for floor operatives over feature richness. Minimal manual input was required at any scan point.
D2
Mandatory scan compliance as a process control mechanism Each stage of the cutting lifecycle was designed as a mandatory digital checkpoint. Scanning was not optional, it was embedded as the operational action itself. This design decision ensured traceability data was collected as a byproduct of normal work rather than as an additional administrative task, which was critical to achieving sustained compliance across all 11 floors.
D3
Roll-level granularity for consumption and end-bit tracking Consumption analysis was designed at roll level, every roll used in every lay was individually scanned and linked to a specific CAD marker. This enabled style-wise actual versus theoretical consumption comparison at a granularity that batch or shift-level tracking could not provide. End-bit generation was captured per roll, enabling recovery allocation rather than untracked disposal.
D4
Operator-level data capture to enable objective performance management Individual input minutes and process output were captured at operator level across all cutting activities. This was a deliberate design choice, not just for operational visibility, but to establish the data infrastructure required for fair PIB calculation. Replacing supervisor estimation with measurable productivity records improved both accuracy and workforce acceptance of performance evaluation.
Technology Stack
ComponentDescriptionBA Contribution
Mobile ApplicationPurpose-built for cutting floor operatives. Handles all QR scanning, data capture, and process stage transitions.Workflow and UX requirements elicited through floor observation and specified as developer build spec
Centralized Production DatabaseReceives timestamped scan transactions from all stages. Real-time data availability across all floors.Data model and transaction logic specified and handed to developers as formal requirements
CAD Marker IntegrationLinks spreading consumption data to marker specifications for actual vs theoretical comparison.Integration requirements and data mapping defined through elicitation with CAD and warehouse teams
Digital Reporting EngineGenerates all 7 operational and management reports automatically with zero manual consolidation.Report structure and output format designed and specified as build requirements
Real-Time Monitoring DisplaysLive dashboards surfacing production status, WIP, and operator performance to supervisors and management.Dashboard layout and KPI selection designed through elicitation with supervisors and management

BA Deliverables. Designed and produced across the project lifecycle: end-to-end process maps for all 6 cutting stages (developed through direct floor observation); QR data structures for roll identity and scan transactions at every stage; Standard Operating Procedures (SOPs) for scanning compliance embedded into each operational stage; report and dashboard layouts handed to developers as formal build specifications; and UAT coordination across all cutting floors and both factories.

§3
Challenges & Resolution

Two problems emerged during implementation. One hit adoption from the start of deployment. The other appeared as a network infrastructure gap after go-live. Neither was resolved by communication or instruction alone; both needed structural changes.

CHALLENGE 01 · Operator Adoption. Field-Level Workforce Without Mobile Device Access

Challenge: The cutting floor workforce operates at field level, physically handling fabric rolls, operating spreading machines, managing lays, and processing bundles. These are not desk-based or administrative roles. Expecting operatives to carry and manage personal smartphones during production introduced an adoption barrier that had nothing to do with willingness or capability. Staff did not have devices, had no natural place to charge them during a shift, and the physical demands of cutting floor work made personal device management impractical. Initial adoption resistance was observed across multiple floors in the early deployment phase.

Diagnosis: The implementation team identified that resistance was not a change management problem, it was an infrastructure problem. The system was correctly designed, but the deployment model assumed device access that floor staff did not have. Solving it with training or communication would have failed. The correct response was to remove the barrier entirely.

Action: Two dedicated mobile phones were deployed on every cutting floor, owned and managed by the operation, not by individual staff. Charging ports were installed at every production table, ensuring devices were always powered and available at the point of work. This eliminated every physical barrier to adoption: staff no longer needed personal devices, no longer needed to manage charging, and no longer needed to carry anything beyond their normal workflow.

Resolution: Adoption improved materially once the infrastructure barrier was removed. The key diagnostic contribution was correctly identifying the root cause as a deployment design gap rather than a behavioral problem. Responding to a device access problem with change communications would have failed. Providing the infrastructure resolved it.
CHALLENGE 02 · Network Coverage. Connectivity Gaps Identified Post Go-Live

Challenge: Network connectivity gaps were identified across parts of the cutting floors after system go-live. The warehouse and cutting floor environment, large floor plates, structural elements, and equipment density, created areas where mobile data connectivity was insufficient for reliable scan transactions. This was not identified during the requirements phase and surfaced only through operational use after deployment.

Action: Connectivity gaps were logged against specific scan failure locations to map coverage against floor geography. IT infrastructure and floor supervisors were coordinated to prioritise remediation by affected area, ensuring the highest-impact zones were addressed first. IT was engaged to assess and deploy additional network infrastructure to close the identified gaps.

Resolution: Network coverage was improved through targeted infrastructure remediation. This challenge reinforced the value of continued floor observation beyond the requirements phase, the same GEMBA principle that applies in warehouse implementations applies equally in cutting floor deployments. Infrastructure constraints in physical environments cannot always be fully anticipated from planning documents alone.

Both challenges shared the same diagnostic structure: a legitimate operational barrier that could not be resolved through instruction. Each required identifying the structural gap first, a device access gap, a network coverage gap, and closing it with the appropriate physical or infrastructure response.

§4
Reporting & Performance Management

Every operational and management report was generated from live scan data. Manual consolidation was eliminated. No report required any manual input after the point of capture.

Automated Report Suite
ReportFrequencyPurpose
Daily Production ReportDailyAutomated production visibility, replaces manual end-of-shift consolidation
Table Utilization ReportReal-timeResource optimization, identifies underutilized spreading stations
Fabric Compliance ReportPer StyleActual vs theoretical consumption control per CAD marker
Operator Performance ReportDailyIndividual efficiency monitoring and PIB input data
Style-wise Consumption ReportPer OrderFull actual vs theoretical comparison for order-level fabric accountability
WIP and Stock ReportReal-timeLive planning coordination, visibility of bundles in-process and completed
End-bit Utilization ReportPer StyleWastage recovery management, tracks residual length allocation and reuse
Performance Incentive Bonus (PIB) — Data Infrastructure

One lasting outcome was objective, measurable operator performance tracking as the data foundation for PIB calculation. Before the system, incentive decisions relied on supervisor estimates. That introduced inconsistency and eroded workforce confidence in how evaluations were made.

⏱️
Captured
Input Minutes
📊
Measured
Process Output
📈
Calculated
Efficiency %
🗒️
Logged
Activity Records
💰
Output
PIB Calculation

Outcome: The traceability system became both an operational control platform and a workforce performance management infrastructure. Objective productivity tracking improved transparency and increased workforce acceptance of performance-based evaluation systems.

§5
Outcomes & Gaps
Key Achievements
Operational
  • Full roll-level traceability across all cutting floors
  • Manual production recording dependency eliminated
  • Real-time WIP visibility established
  • Daily production reporting automated
  • Style-wise consumption accountability created
  • End-bit recovery and redeployment tracking improved
  • Process compliance standardized through scan checkpoints
Management
  • Objective operator performance evaluation enabled
  • Data foundation for PIB implementation established
  • Planning coordination improved through live WIP visibility
  • Management response speed increased via real-time dashboards
Digital Transformation
  • Scalable digital infrastructure across 2 factories and 11 floors
  • Production data integrated across all cutting stages
  • Sustainable operational digitization standards established
  • Scalable model for future manufacturing digitization initiatives
Sustainability Measures
MeasureImplementationStatus
SOP IntegrationScanning compliance embedded as standard operating procedure across all stagesACTIVE
Ownership TransferProduction and IT functions hold operational and technical ownershipACTIVE
Automated ReportingAll 7 management reports generated automatically, no manual intervention requiredACTIVE
Real-time MonitoringLive dashboards embedded in daily operational management routinesACTIVE
Scalable ArchitectureSystem architecture supports additional floors and factory expansionACTIVE
Known Gaps. Documented at Project Closure

Gap 01 — Network coverage gaps remain an ongoing infrastructure management item. Despite IT remediation following the post-go-live connectivity issues, network coverage across large cutting floor environments is subject to ongoing variability. Structural conditions, equipment repositioning, and floor layout changes can reintroduce coverage gaps. This is not a system design flaw, it is a physical environment constraint. Periodic network audits against scan reliability data are recommended as a standing operational practice rather than a one-time fix.

Gap 02 — Continuous 10-hour device operation accelerates battery degradation and requires active hardware lifecycle management. Dedicated phones deployed on cutting floors operate continuously across full production shifts. This usage pattern degrades battery capacity faster than standard device lifecycles account for. No software mitigation fully resolves this, it is a hardware constraint. A planned device replacement cycle, sized against observed degradation rates per floor, is required to prevent scan reliability from declining as devices age. This should be treated as a recurring operational cost, not a one-time capital item.

§6
Key Learnings

Five lessons from this implementation apply across similar digital transformation projects in high-volume garment production.

1
Traceability must precede consumption control Accurate style-wise consumption analysis is impossible without roll-level process visibility. Attempting to measure fabric variance at a higher level of aggregation produced numbers that could not be interrogated or acted upon. The decision to build traceability first, and derive reporting from it, was the correct sequencing. Reporting built on traceability is reliable. Reporting built on manual records is not.
2
Adoption resistance in field environments is usually an infrastructure problem, not a people problem Cutting floor operatives resisted the system in early deployment. The correct diagnosis was not change aversion, it was that the deployment model assumed device access field-level workers did not have. Providing dedicated phones and table-level charging removed the barrier entirely. The principle generalises: in field and production environments, adoption failures are more likely to be physical access problems than behavioral ones. Diagnosing correctly before responding is the BA's most important contribution during an implementation crisis.
3
Process discipline is more important than technology alone The system's success depended equally on SOP enforcement, scan compliance, and accountability structures, not just the technical implementation. A well-designed mobile application installed on a floor without disciplined scanning protocols would have produced incomplete data. Technology provides the infrastructure; process discipline provides the data quality that makes it useful.
4
Real-time visibility changes operational behavior Live production monitoring significantly improved process ownership and response speed at floor level. When supervisors could see WIP status and operator performance in real time, intervention moved from reactive (end-of-shift reporting) to proactive (intra-shift correction). The behavioral change driven by visibility was as significant as the data accuracy improvement itself.
5
Operator-level data enables fair performance management Objective productivity tracking improved transparency and workforce acceptance of performance-based evaluation. When PIB calculation moved from supervisor estimation to system-recorded input minutes and output, resistance to the incentive structure decreased. Data-driven evaluation is perceived as fair precisely because it removes subjective judgment from the process, even when the outcomes are numerically the same.