Material

Vendor MARs, in-house supply MIRs, security delivery notes, and SAP issuance — all on one digital workflow.

What it is

Material flow today runs on three different rails — vendor MAR (Material Approval Request) for vendor-supplied items, MIR (Material Issuance Request) for in-house supply, and SAP for accounting. The platform unifies them. Vendor raises MAR; security records delivery at gate; CM and QAA inspect against spec; SAP issuance auto-recorded on pass. Wastage tracking feeds reconciliation. Quality failures feed Vendor 360.

Inputs

Triggers

·Material requirement raised by Site Engineer against WO
·Vendor delivery notification
·Security gate receipt confirmation
·QAA inspection request
·SAP issuance request
·Wastage threshold breach detected

Data reads

·WO scope and material schedule from M14
·Vendor record from M13
·Spec from M09 for inspection criteria
·Project material stock from SAP
·Wastage benchmarks for the material type

Artefacts consumed

·Vendor delivery challan
·Material approval request (MAR)
·Material inspection request (MIR)
·Security delivery note from gate
·Test certificates and compliance documents

Tools & Techniques

Methods

·Unified MAR + MIR + security delivery workflow — one digital track per material lot
·QAA inspection workflow with test certificate verification
·Mobile-based on-site inspection capture (photo, location, signature)
·SAP issuance automated on QAA pass
·Consumption reconciliation against BOQ at WIR closure
·Wastage detection with vendor and material attribution

Policies

·material policy with inspection criteria per material class
·Test certificate policy by material type
·Wastage tolerance policy with vendor-specific benchmarks
·SAP reconciliation policy with cycle-time targets

Decision rules

·Material rejection auto-flags vendor for repeat-issue pattern
·QAA pass mandatory before SAP issuance
·Wastage above threshold flags package for review
·Consumption reconciliation mandatory at WIR closure

Outputs

Artefacts produced

·Material register per project, per WO, per lot
·QAA inspection report per material lot
·SAP material issuance record
·Wastage report per package and per vendor
·Material rejection log feeding Vendor 360

Data writes

·Material status updated through MAR → MIR → issuance lifecycle
·SAP stock updated on issuance
·Vendor performance updated on rejection events

Downstream triggers

·Material issuance unlocks site activity in M16 schedule
·Quality failure feeds Vendor 360 in M13
·Consumption data feeds bill certification in M21
·Wastage pattern flags vendor performance review

Stakeholders

VendorRaises MAR before material delivery
SecurityGate-level delivery recording
CMPhysical inspection
QAAQuality inspection against spec
CPTSAP issuance for in-house supply materials

The flow

01Material approval request raised by vendor
02Material delivery note at gate (security)
03Auto-link to WO
04Material inspection by CM and QAA against spec
05Pass / fail decision with reasoning
06SAP material issuance for in-house supply
07Reconciliation — material consumed vs issued, with wastage
08Wastage data fed to vendor performance and project cost

State change

Before

Vendor brings material; security signs note; CM inspects; SAP entered next morning by clerk.

After

One digital workflow from gate to issuance; vendor performance updated in real time.

Real-world example

Worli — Mivan panels arrive at gate 14 May 9:42 AM. Vendor MAR auto-linked to WO. Security delivery note recorded. CM + QAA inspect at 10:15 AM; pass. SAP issuance recorded automatically. Vendor performance log notes clean delivery. 74 MARs open portfolio-wide; 18 SAP issuances completed today.

Artefacts

·MAR records
·Delivery notes
·Inspection records (with photo)
·SAP issuance entries
·Wastage reports

Pain today

Vendor MAR, MIR, and SAP issuance run on three different rails. Quality issues discovered after material is consumed. Wastage data is partial and lags. Vendor performance impact captured intermittently.

Integrations

SAP