Kavalife ERP

Problem

Before writing software, the manufacturing process itself had to be understood.

The biggest challenge was not technology.

It was understanding how material actually moved through the factory.

Observation

Raw material enters the facility.

It gets inspected.

It becomes officially received inventory.

It passes QA/QC.

It enters production.

It moves through multiple manufacturing stages.

It eventually becomes finished output.

Lesson

ERP systems should model business reality before they model screens.

Architectural Impact

This phase established the core language of the system:

• VIR
• GRN
• QA/QC
• Batch
• Lot
• Workflow
• Process Execution

Problem

The business needed visibility into material entering the factory.

Solution

Introduced:

• VIR creation
• VIR verification
• GRN creation
• GRN approval workflows
• QA/QC validation

Result

The system could now answer:

• What material arrived?
• Who supplied it?
• Was it approved?
• Can it enter production?

Lesson

Received material is not inventory until it has passed verification and quality checks.

Problem

Approved material needed to become a manufacturing job.

Solution

Introduced the Batch model.

Initial business rule:

One GRN
→ One Batch

Result

Production could now be tracked independently from receiving operations.

Lesson

Receiving and manufacturing are separate lifecycles.

Problem

Different products follow different manufacturing processes.

Solution

Introduced:

• Products
• Process Definitions
• Product Workflows
• Workflow Steps

Example:

Extraction
→ Stripping
→ Purification
→ Decolorisation

Result

The ERP gained the concept of manufacturing recipes.

Lesson

The system needs to know what should happen before it can track what is happening.

Problem

Workflow templates alone were not enough.

The business needed visibility into real production.

Solution

Introduced:

• Lots
• Runtime Process Steps
• Active Process Tracking

Important distinction:

Workflow Step
= Template

Runtime Process Step
= Real execution state

Result

The ERP became capable of tracking actual production progress.

Lesson

Templates describe intent.

Runtime state describes reality.

Problem

Operators needed a way to record actual manufacturing activity.

Solution

Introduced Process Executions.

Execution records capture:

• Quantity In
• Quantity Out
• Yield
• Loss
• Equipment Used
• Operator Notes
• Supervisor Notes

Result

The system gained traceability and operational evidence.

Lesson

Manufacturing systems require more than status updates.

They require records of what actually happened.

Problem

Every manufacturing stage required different information.

Extraction does not require the same data as Purification.

Solution

Introduced metadata-driven form schemas.

Process Definitions could now define their own execution forms.

Result

Frontend forms became configurable instead of hardcoded.

Lesson

Metadata-driven systems scale better than process-specific implementations.

Problem

Certain manufacturing outputs required quality approval before production could continue.

Solution

QA/QC became a runtime workflow gate.

Process execution now follows:

Process
→ Awaiting QA/QC
→ Approved
→ Next Process Activated

Result

The ERP began controlling manufacturing flow rather than simply recording it.

Lesson

Quality control is not a separate module.

It is part of the production state machine.

Problem

The entire manufacturing lifecycle needed validation.

Solution

Created a full end-to-end testing path.

Login
→ VIR
→ GRN
→ QA/QC
→ Batch
→ Lot
→ Extraction
→ QA/QC
→ Stripping
→ QA/QC
→ Purification
→ QA/QC
→ Decolorisation

Result

The complete manufacturing flow could be executed and validated.

Lesson

Before automation, prove the workflow manually.

Problem

The happy path worked.

Now edge cases and operational reliability became important.

Focus Areas

• Batch closure
• Lot closure
• Error handling
• State validation
• Better API consistency
• Automated testing
• Schema completion

Result

The project entered a hardening phase.

Lesson

Happy paths prove capability.

Edge cases prove maturity.