Good morning, Sarah.
Tata Commercial Vehicles · Service parts network · all authorised service centres
Operational View
Vehicles waiting for parts
27
across 9 service centres
Open service jobs
214
with active parts demand · of 1,246 total cases
Parts in fulfilment
38
PDC → dealer → workshop
Jobs requiring intervention
5
1 critical · 1 high
Customer promises at risk
8
4h to 27h breach window
Jobs impacted by inventory discrepancies
9
relying on unverified stock
Revenue at risk
₹6.46L
today's 27 open jobs
Vehicles VOR > 24h
6
off road, awaiting parts
Parts unavailable
14
SKUs at zero across network
Stock under PI reconciliation
34
18 with a discrepancy
Customer updates pending
7
promise changed, not yet told
Sales & fulfilment overviewtoday's 27 open vehicles · illustrative values
Revenue at risk, by driver
Total revenue at risk₹6.46L
Fulfilment health — today's 27
70%
Promise accuracy
10.9h
Avg VOR
40h
Longest VOR
19
On track / pending
Top parts at riskView all →
Alternator Assembly1.2d cover
Clutch Plate Assembly2.6d cover
Suspension Bush Kit4.0d cover
Turbocharger Unit7.1d cover
Vehicles waiting for parts
Full service job list →
| Service job | Vehicle / VIN | Service centre | Customer | VOR | Part needed | Inventory confidence | Promise risk |
|---|
Requires attention5
JOB-18472 · Alternator Assembly stuck — Chennai inventory cannot be trusted
Coimbatore · 19h VOR · predicted promise miss +4.5h · 45m action window
JOB-18522 · Clutch Plate Assembly — variant needs confirmation
Delhi · 27h VOR · already past promise
Hyderabad PDC · fuel injector stock count short — preventive hold
−5 variance · re-verify before next 2 reservations
Inventory confidence distributionnetwork-wide, all open PIDs
16
Counted, clear
6
Count pending
12
Variance open
Of 34 open physical inventory documents affecting service parts, 18 show a stock discrepancy and 6 are still awaiting a difference posting. 9 open VOR jobs are relying on stock that has not been physically verified.
Customer promise snapshotView all →
Vehicles with an active promise27
Promises at risk8
Not yet notified7
Priority fleet accounts affected4
Service jobs
Every vehicle currently waiting on a part · Vehicle → Service Job → Part → Availability → Promise
| Service job | Vehicle / VIN | Service centre | Customer | Part needed | VOR | Inventory confidence | Promise risk |
|---|
Parts availability
Network-wide stock, velocity, and shortage intelligence for every SKU with open service demand
SKUs tracked
16
across the PDC network
Critical — under 7 days cover
4
immediate action needed
Watch — 7 to 15 days cover
6
monitor closely
Fast-moving SKUs
7
of 16 tracked parts
Alternator Assembly (ALT-750) — example drill-downChennai stock untrusted
| Location | System stock | Service ATP | Physical inventory | Confidence | ETA to Coimbatore |
|---|---|---|---|---|---|
| Coimbatore Dealer | 0 | 0 | Clear | High | — |
| Chennai PDC | 2 | 2 | Variance open | Low | 7h |
| Bengaluru PDC | 6 | 4 | Clear | High | 9h |
| Hyderabad PDC | 11 | 8 | Clear | High | 15h |
Parts catalog — network intelligence
| Part | SAP material | Category | Velocity | Monthly demand | Network stock | Service ATP | Cover | Status | Linked jobs |
|---|
Inventory truth
Where SAP stock, physical count, and service demand disagree
Open physical inventory documents
34
affecting service parts
Stock discrepancies
18
Open VOR jobs affected
9
Demand relying on unverified stock
₹12.4L
Differences awaiting posting
6
Stock vs physical count, by service jobsorted by VOR urgency
| Job | Material | Location | SAP stock | Physical count | Variance | PID | Status | Promise impact |
|---|---|---|---|---|---|---|---|---|
| JOB-18472 | ALT-750 | Chennai PDC | 2 | 0 | −2 | 49001821 | Pending | Critical |
| JOB-18510 | FIP-330 | Hyderabad PDC | 11 | 6 | −5 | 49001889 | Count pending | Watch |
| JOB-18504 | RAD-410 | Bengaluru PDC | 8 | 8 | 0 | 49001842 | Counted | None |
| JOB-18481 | ALT-750 | Pune Components Hub | 14 | 16 | +2 | 49001905 | Difference pending | Opportunity |
Recommended responseNeeds approval
SAP shows 2 units of ALT-750 at Chennai PDC, but the open physical inventory document 49001821 counted 0. The difference has not been posted. Do not allocate against Chennai until this is resolved — source JOB-18472 from Bengaluru PDC instead, where 4 units are trusted and available-to-promise.
Customer promise centre
What was promised, what is actually true, and who has not been told yet
Vehicles with an active promise
27
Promises at risk
8
Customers not yet notified
7
Priority fleet accounts affected
4
| VIN | Customer | Service job | Part | Tier | Promise status | Inventory confidence | Customer updated |
|---|
Demand & revenue
Where service parts revenue is protected, and where it leaks · illustrative values
Illustrative values
Open service-parts demand
₹4.8 Cr
Revenue blocked by availability
₹32L
Enquiry → order conversion
71%
Potential lost sales
₹18L
Substitution opportunities
12
Dealers with repeated stockouts
4
Revenue leakage waterfalldemand identified → fulfilled, illustrative scenario
Service demand identified₹4.80 Cr
− No inventory−₹32L
− Inventory discrepancy−₹11L
− Customer cancelled−₹7L
− Competitor / aftermarket leakage−₹5L
= Fulfilled₹4.25 Cr
Revenue blocked, by part
| Part | Blocked demand | Root cause | Affected service jobs | Substitution available |
|---|---|---|---|---|
| Alternator Assembly (ALT-750) | ₹9.2L | Inventory variance — Chennai | JOB-18472 | Yes — ALT-750A |
| Clutch Plate Assembly (CP-410) | ₹8.6L | Part variant unconfirmed — Delhi | JOB-18522 | Pending confirmation |
| Radiator Core Assembly | ₹6.1L | Transfer distance — Pune | JOB-18504 | No |
| Turbocharger Unit | ₹4.4L | Zero stock — Guwahati, Nagpur | 2 jobs | No |
Dealer & service centre performance
Fill rate, VOR average, and repeat stockouts across the authorised network
Service centres monitored
9
Avg VOR (network)
13.4h
Avg fill rate
86%
Avg stock accuracy
92%
Centres with repeat stockouts
4
| Service centre | Open jobs | Avg VOR | Fill rate | Stock accuracy | PI exceptions | Promise accuracy | Status |
|---|---|---|---|---|---|---|---|
| Coimbatore | 3 | 16.0h | 68% | 91% | 1 | 74% | Needs attention |
| Jaipur | 3 | 15.7h | 77% | 89% | 3 | 80% | Watch |
| Nagpur | 3 | 15.7h | 81% | 95% | 1 | 83% | Watch |
| Ahmedabad | 3 | 13.0h | 85% | 96% | 1 | 88% | Healthy |
| Mumbai | 3 | 11.7h | 87% | 96% | 1 | 89% | Healthy |
| Delhi | 3 | 10.3h | 79% | 96% | 1 | 82% | Watch |
| Pune | 3 | 10.0h | 88% | 97% | 0 | 93% | Healthy |
| Guwahati | 3 | 3.7h | 95% | 99% | 1 | 96% | Healthy |
| Kolkata | 3 | 2.3h | 96% | 99% | 0 | 98% | Healthy |
Exceptions & interventions
Business event → Risk detected → Decision required → Action executed · every intervention tied to a vehicle and a service job
Operational View
Pending approval
5
1 critical · 4 high
In progress
3
Executing now
Automated (30d)
47
Zero human touch
Resolved (30d)
61
avg 34min response
VOR hours avoided
312
this month
Critical
Prima 5530.S waiting at Coimbatore — Chennai inventory cannot be trusted
1
Do this now
Source ALT-750 from Bengaluru PDC instead of Chennai, and place the Chennai stock discrepancy into priority reconciliation
Coimbatore stock = 0 · Chennai system stock = 2, physical count = 0 · Bengaluru trusted ATP = 4 · Customer promise breach in 45m
Why this is happening
SAP shows 2 units of ALT-750 at Chennai PDC, which looks like the fastest option at 7 hours. But there is an open physical inventory document against that material and location — the physical count came back 0, and the difference has not been posted. Allocating against Chennai risks promising a part that is not actually there. Bengaluru is 2 hours further but its stock is verified.
Also worth doing
2Trigger the priority transfer from Bengaluru PDC to Coimbatore Service Centre
3Escalate PID 49001821 for difference confirmation and posting
4Recalculate the vehicle-ready ETA once the Bengaluru transfer is confirmed
5Update the service adviser and revise the Siebel customer promise
Signals behind this
Chennai variance: −2
PID 49001821 · pending
Bengaluru ATP: 4 · trusted
Priority fleet account
Confidence in this recommendation
88% — Bengaluru gives the fastest vehicle-ready time among verified stock
High
Hyderabad PDC stock count is short — verify before the next allocation
1
Do this now
Hold the remaining 6 units at Hyderabad as provisionally trusted only — re-verify before committing the next 2 reservations against this material
Hyderabad PDC system stock = 11 · physical count = 6 · variance = −5 · PID 49001889 count pending confirmation
Why this is happening
A cycle count at Hyderabad PDC came back 5 units short of what SAP shows for this fuel injector pump. JOB-18510 was already fulfilled from this location and is unaffected. The remaining 6 units are provisionally trusted, but any further demand against this material here should be verified first — this is preventive, not a reaction to a missed promise.
Also worth doing
2Escalate PID 49001889 for difference confirmation and posting
3Flag Hyderabad PDC for a cycle-count review — this is the second short count this month
Signals behind this
Variance: −5
PID 49001889 · count pending
6 units provisionally trusted
Confidence in this recommendation
81% — provisional trust pending count reconciliation
High
Signa 3118.T at Delhi — clutch part variant needs confirmation
1
Do this now
Confirm whether this vehicle needs CP-410 or CP-410R before allocating — two clutch variants fit this platform
CP-410 and CP-410R both fit the Signa platform depending on transmission variant, which is not recorded on this vehicle's service record
Why this is happening
Two clutch plate variants share overlapping fitment data for the Signa platform. The transmission variant is not recorded on this vehicle's service record, so the correct material cannot be confirmed automatically — this needs a quick check at the service centre before parts are allocated.
Also worth doing
2Once confirmed, allocate from Chennai PDC — 4 units available, 18h transfer to Delhi
Signals behind this
2 candidate variantsTransmission variant not recordedChennai PDC: 4 units, 18h
Confidence in this recommendation
62% — needs human confirmation before allocation
Predictive insights
Where the network is heading, not just where it stands today · illustrative model, to be validated against actual SAP/Siebel history
Parts predicted to stock out
4
within 7 days
Emerging promise risk
5
on track today, predicted to tip within 48h
Reorder recommendations
4
SKUs, generated from demand trend
Forecast confidence
82%
avg across active predictions
Parts predicted to stock out — next 7 daysranked by days of cover remaining
| Part | SAP material | Current cover | Predicted stockout | Monthly demand | Recommended reorder | Linked jobs |
|---|---|---|---|---|---|---|
| Alternator Assembly | ALT-750 | 1.2d | ~1 day | 340/mo | 320 units | 3 jobs |
| Clutch Plate Assembly | CP-410 | 2.6d | ~3 days | 210/mo | 190 units | 2 jobs |
| Suspension Bush Kit | SBK-410 | 4.0d | ~4 days | 310/mo | 250 units | 3 jobs |
| Propeller Shaft Assembly | PSA-720 | 6.8d | ~7 days | 22/mo | 14 units | — |
Emerging promise risk — next 48 hourson track today, predicted to tip based on part and inventory signals
| Service job | Customer | Part | Status today | Predictive signal | Predicted risk |
|---|---|---|---|---|---|
| JOB-18646 | Highway Logistics | Turbocharger Unit | On track, −1h | Watch inventory confidence + part-level cover 7.1d | High |
| JOB-18609 | United Carriers | Clutch Plate Assembly | On track, −1h | Part-level cover 2.6d — Critical network-wide | High |
| JOB-18571 | Apex Movers | Suspension Bush Kit | On track, −2h | Part-level cover 4.0d · vehicle already 25h VOR | Medium |
| JOB-18601 | Prime Haulage | Leaf Spring Set | On track, −2h | Watch inventory confidence on last count | Medium |
| JOB-18481 | XYZ Transport | Brake Pad Set | On track, −2h | Part-level cover 12.2d and trending down | Medium |
Network demand vs fulfilment capacitynext 4 weeks, forecast
How this model works
Stockout prediction: days-of-cover trend against monthly demand velocity, independent of whether a job has claimed the stock yet.
Promise-risk prediction: combines part-level shortage signals with inventory confidence to flag jobs before their own promise clock shows red.
Still to validate with Tata: real demand seasonality, service-centre-level lead times, and historical accuracy against actual SAP/Siebel outcomes — this model is illustrative until back-tested on real data.
Service parts performance
Illustrative values — network-level performance across the service parts operation
First-time fill rate
86%
↑ +2.1% vs last month
Customer-promise accuracy
94%
Avg parts-driven VOR
12.8h
↑ +0.6h vs target
Identity resolution within SLA
92%
First-time fill rate — weekly
Customer-promise accuracy — trend
Performance by service centre
| Service centre | First-time fill | Promise accuracy | Avg parts VOR | Identity resolution SLA |
|---|---|---|---|---|
| Coimbatore | 68% | 81% | 21.2h | 76% |
| Delhi | 79% | 85% | 18.6h | 88% |
| Pune | 88% | 93% | 12.1h | 91% |
| Nagpur | 93% | 97% | 8.4h | 95% |
| Guwahati | 95% | 98% | 6.9h | 96% |
Audit
Full traceability of identity resolutions, human approvals, and automated actions
Total actions logged
12,847
Automated actions
9,234
Human approvals
3,613
Open compliance items
2
Audit log
| Timestamp | Type | Triggered by | Event / job | User | Detail |
|---|---|---|---|---|---|
| 2026-05-07 09:14:18 | Inventory reconciliation | Inventory Truth Engine | JOB-18472 · PID 49001821 | System | Variance detected · Bengaluru PDC recommended instead |
| 2026-05-07 09:10:44 | Human approval | Sarah Chen | JOB-18472 · Bengaluru allocation approved | S.Chen | 4 units reserved, priority transfer triggered |
| 2026-05-07 09:08:02 | Intervention executed | Service Desk — Coimbatore | JOB-18472 · alternator transfer | System | Bengaluru PDC allocation confirmed |
| 2026-05-07 08:55:31 | Inventory reconciliation | Inventory Truth Engine | Hyderabad PDC · PID 49001889 | System | Variance −5 · routed to review queue |
| 2026-05-07 08:42:19 | User login | SSO | — | S.Chen | Google SSO · IP 10.0.1.44 |
Network Map
Illustrative geospatial view across vendors, CDCs, distributors, and fulfilment lanes
Operational View
Legend
Vendor
CDC
Channel partner — healthy
Channel partner — at risk
Lane at risk
Service Centre — CoimbatoreAt risk
Live node status
Active service jobJOB-18472 at risk
Inbound lanes1 of 1 active
Nearest PDC ETA7h — Chennai PDC
Last signal2 min ago
Integrations
Blueprints does not replace these systems. It creates the operational thread across them.
SAP SD
Customer demand · sales order · delivery — exact objects to be validated
Sync cadence to be confirmed with Tata IT
SAP MM / Inventory Management
Material · plant · storage location · stock · reservations · physical inventory · differences — exact scope to be validated
Sync cadence to be confirmed with Tata IT
Oracle Siebel
Customer · service case · vehicle · service interaction
Sync cadence to be confirmed with Tata IT
Amazon S3
Consolidated / historical data layer
Current cadence: batch, not real time
Service Centre / Dealer Data
Interface to be confirmed
Pending scope with Tata IT
What changes, and what does not
SAP remains the system of record for the part and the fulfilment. Siebel remains the system of record for the customer and the service interaction. The S3 layer today is a consolidated dump feeding dashboards — useful for reporting, not built to carry an operational decision.
Current
SAP / Siebel
↓
S3 batch dumps
↓
Dashboard
↓
Human discovers issue
↓
Phone / email / escalation
Service demand is visible. Inventory is visible. Physical inventory exists. But the relationship and confidence between them are not operationalised.
Proposed
Siebel — customer, vehicle, service job
↓
Service requirement
↓
SAP — material, order, reservation
↓
Inventory position — system stock ↔ physical inventory
↓
Inventory truth
↓
Availability decision → allocation → fulfilment
↓
Customer promise
Blueprints sits across the middle as the Operational Response Layer — not another database, and not a replacement for SAP or Siebel.
Why PID belongs on the inventory side, not the identity side
A Physical Inventory Document answers "can we trust the system stock?" — not "which part does this vehicle need?". Those are different questions, and putting PID in the wrong place breaks the logic: a missing or open PID should never block knowing what part is required, only whether the stock behind it can be trusted.
Customer / vehicle
↓
Siebel service case → service job
↓
Part requirement → SAP material
↓
Order / reservation / allocation
↓
Inventory node — plant / PDC / dealer / storage location
↓
Stock position
↓
Physical inventory document — book qty, counted qty, difference, reconciliation status
↓
Trusted availability → fulfilment → fitment → vehicle ready
The relationships are not always 1:1 — one service job can need several parts, a material can have a superseding material, and one physical inventory document can affect several open jobs at once. The exact relationship between a PID and a Job ID (direct field, or indirect through material / plant / storage location / reservation) is still to be validated with Tata.