Skip to content
Arjava

Home / Blog / Case study

S.S. Engineering Works

How S.S. Engineering Works caught a tender rejection before it happened

Tender extraction: dates, eligibility criteria and required documents identified
Arjava ERP command dashboard with revenue, receivables, tender pipeline and pending actions
Case Study
Arjava TeamAug 22, 20266 min read

Quick answer

A corrigendum pushed a tender deadline back 8 days. Arjava's validity alerts caught that the bank guarantee's 180 day window no longer covered it, before submission, and cut tender document review from 2 to 3 hours down to 3 to 4 minutes.

S.S. Engineering Works Limited is an integrated water, wastewater, and environmental engineering company: STPs, ETPs, MBR/MBBR systems, water treatment, filtration, desalination, and solid waste management, serving government, municipal, industrial, and commercial clients. 25+ years in water treatment, 400+ projects delivered. Their operations now run on Arjava.

The situation

An established STP/ETP contractor running multiple concurrent projects, with procurement, stores, site execution, and billing all coordinated over Excel, phone calls, and WhatsApp. That's not unusual, it's how most contractors of their size operate. The problem isn't the tools individually. It's what happens when nobody can see across all of them at once.

The problem

There was no live view of stock or project cost. Approvals happened over chat, which meant no consistent record of who approved what and when. Discrepancies between what was planned and what actually happened stayed invisible until year-end reconciliation, by which point there was nothing left to do but note them down. And because none of this was systemized, almost every decision routed back through the owner.

The intervention

Arjava mapped the tender-to-billing lifecycle end to end, then rolled it out module by module: procurement, inventory, projects, approvals, and dashboards, deployed on the client's own infrastructure.

The results

A bank guarantee validity alert caught a submission before it went out invalid. After a corrigendum pushed the submission date back by 8 days, the system flagged that the BG's 180 day validity window no longer covered the new deadline, catching it before the tender was filed.

Purchase approvals dropped from 3 days to same-day, once the workflow moved off chat threads and into a system with an actual approval chain.

Zero new hires. One existing coordinator absorbed a growing project load, capacity added without adding payroll.

Tender document review dropped from 2 to 3 hours to 3 to 4 minutes. Scope of work, contractual terms, the structure register, the equipment register, and key milestones used to need a senior resource's focused attention to read through. Now that analysis happens in the system and is available on demand.

Platform adoption is running at roughly 88% at S.S. Engineering Works and roughly 96% at Shanti Infraconstruct.


These figures are reported by the client from their own platform records. They have not been independently audited. Baselines and methodology are available on request.

What the system checks for you

  • Minutes

    not days

    Tender document reading

    Dates, fees, eligibility and required documents pulled into structured fields

  • Every PO

    checked on rate

    Vendor rate history

    Quotes compared against past rates before an order is approved

  • Before

    submission

    Validity and compliance checks

    EMD and document validity checked against the latest corrigendum

Checks run inside the system; your team reviews every flag before acting.

Next step: a discussion, then six clear stages

  1. 01

    Discover

    Map your workflows

  2. 02

    Define

    Agree scope & goals

  3. 03

    Design

    Plan screens & data

  4. 04

    Develop

    Build & configure

  5. 05

    Deploy

    Go live with training

  6. 06

    Support

    Improve continuously

Human-in-the-loop AI. AI reads documents, compares data and flags risks; your team reviews and decides.