Sama
sama - evenness, things brought into balance
Engineering, manufacturing, service, and software BOMs kept in step as designs move.
Sama is a command centre for keeping bills of materials aligned across a programme. It brings engineering, manufacturing, service, and software BOMs into one dashboard, tracks discrepancies, visualizes dependencies, and keeps every downstream BOM in step as designs evolve. It is built for fast navigation across complex, multi-domain parts data, and it removes the manual reconciliation work that usually causes costly mismatches between engineering intent and what actually ships.
Workflow
Problem
Each function keeps its own bill of materials, so engineering intent and what actually ships drift apart, and the mismatch is discovered on the line or in the field.
Outcome
Every downstream BOM held in sync with engineering as designs evolve, with discrepancies surfaced rather than reconciled by hand.
01
Bring the BOMs together
Each domain BOM is read from its own system of record into one comparable structure.
02
Detect divergence
Differences between domains are surfaced continuously rather than found at a build or a warranty claim.
03
Trace the cause
Each discrepancy is linked back to the design change or plant variation that produced it.
04
Propagate the change
Approved changes are pushed downstream so service and software stay aligned with engineering.
Modules
Multi-Domain Dashboard
Engineering, manufacturing, service, and software BOMs brought into one comparable view.
Discrepancy Tracking
Mismatches between domains surfaced with the change that caused them.
Dependency Visualization
How a part change propagates across variants, plants, and downstream BOMs.
Variant & Option Governance
Configuration and option complexity managed without a separate BOM per permutation.
Representative use cases
Harmonizing EBOM to MBOM Discrepancies During Electric Vehicle Ramp
An Electric Vehicle (EV) original equipment manufacturer ramping up a new dual motor SUV platform across two high volume vehicle assembly plants.
Aligning Hardware EBOM and Embedded Firmware Software BOM
A smart automotive Tier 1 supplier producing Advanced Driver Assistance System (ADAS) domain controllers integrating radar sensors, cameras, and microcontrollers.
Field Service BOM Alignment for Warranty & Aftermarket Operations
A commercial bus and truck manufacturer with a global dealer network managing 150,000 active fleet vehicles across 25 international markets.
Multi Factory Plant Specific MBOM Reconciliation in Automotive Assembly
A global automotive conglomerate producing a high volume crossover vehicle across 4 assembly plants in North America, Europe, and Asia.
Complex Configuration & Option Variant BOM Governance
A luxury commercial coach and specialized vehicle builder offering over 2,500 customizable options, seating layouts, powertrain configurations, and interior trims.
Closed Loop Product Lifecycle Sama & Digital Twin Alignment
An aerospace and defense contractor manufacturing satellite systems, avionics enclosures, and unmanned aerial vehicles.
Evidence
What Wayam can show for this entry
Curated solution design with an owner and a review date. No performance or production claim.
Allowed claims at this tier: Possible workflow, typical stack, prerequisites.
- Evidence tier
- T4 · Reference pattern
- Integration status
- Typical enterprise system
- Metric status
- Scenario only
- Evidence owner
- Not yet attached
- Validated
- Not yet attached
- Valid until
- —
- Content version
- 2026.09
Pending evidence attachment
This entry represents an enterprise architectural reference pattern. Customer benchmarks, run replays, and metric verifications are established during technical discovery.
Limitations
- Headline metrics are representative until a customer result is attached.
Representative metrics · Reference · scenario only
Four domains
engineering, manufacturing, service, software
Surfaced
not reconciled by hand
These describe the intended outcome of the design. They are not measured customer results until a validated case is attached above.
Architecture & controls
Composed across the operating loop
Ingest
Connect the systems of record and read the signals the work already produces.
Covered by the platform
Reason
Ground context, score options against policy and the stated goal, draft the next step.
6 agent roles
Act
Execute an approved step in the system of record and keep the evidence.
4 agent roles
Govern
Set policy, gate consequential actions on a named approver, and audit what ran.
Covered by the platform
Pack Architecture & Agent Composition Graph
10 Composed Agents- AGT-0237
CI/CD Build Failure Diagnosis Agent
Software Engineering
- AGT-0250
Code Completion Agent
Software Engineering
- AGT-0251
Code Review Agent
Software Engineering
- AGT-0100
Close Acceleration Agent
Finance
- AGT-0101
AP Invoice Processing Agent
Finance
- AGT-0102
AR Collections Agent
Finance
- AGT-0345
Quality Inspection Reporting Agent
Quality
- AGT-0348
Scrap and Rework Analysis Agent
Quality
Control gates
- A named approver on every consequential write-back
- Evidence and audit trail kept with every run
Capability atoms
- system-connectors
- anomaly-detection
- root-cause-reasoning
- workflow-orchestration
- evidence-audit-trail
Typical enterprise systems
Typical stack for solution design; compatibility is validated during discovery.
- ServiceNow ITSM
- Datadog
- PagerDuty
- Kubernetes
- GitHub
- Cursor
- Anthropic Claude Code
- SAP S/4HANA
Designed for
automotive, manufacturing, technology
Business case
Model a Sama scenario with your own baseline
Three scenarios from the numbers you enter. Capacity released is time; it becomes a saving only when roles or costs are actually removed or avoided.
| Scenario | Improvement | Capacity released | Cashable savings | Net annual | Payback |
|---|---|---|---|---|---|
| Conservative | 9% | — | — | — | — |
| Expected | 18% | — | — | — | — |
| Upside | 24% | — | — | — | — |
Enter an annual volume and a baseline cost to see figures.
Illustrative planning scenario, not a guarantee. Results depend on process baseline, adoption, data quality, integration scope, controls, and deployment costs.
Pilot this
From solution design to a bounded pilot
Step 1 · 3–4 weeks
Discovery Sprint
Validate the workflow, data, controls, baseline and business case before anything is built.
Gate: Blueprint and pilot plan signed by the business owner, technical owner and Wayam.
Step 2 · 6–10 weeks
Bounded Pilot
Prove quality and value on agreed data against agreed acceptance tests.
Gate: Acceptance thresholds met on the evaluation set; go/no-go decision recorded.
Agrani · evidence pending1 Agrani candidate in this solution: Defect Root Cause Analysis AgentPairs well with