Custom parts · cost and sourcing
Every cost line points to the drawing.
An operator reads the drawing, prices it from your own rates and drafts the RFQ. Your buyer approves before anything reaches a supplier.
RFQ drafted · 3 approved suppliersWaits for a person's yes
Enterprises running operators on Alomana
- Under 24 hfrom RFQ to quote, down from days
- Up to 30%lower cost on custom parts
- Up to 75%less buyer time per RFQ
Six moves on every custom part
Each one used to wait for the estimator who knows where everything is.
- 01
A drawing arrives
Reads the title block and notes: material, tolerances, finish, quantity
- 02
Something is missing
Flags it and drafts the question to the engineer
- 03
It looks familiar
Finds the same or a similar part in your order history
- 04
No price yet
Builds a should-cost from your rates, line by line
- 05
Ready to source
Drafts the RFQ package for your approved suppliers
- 06
Quotes come back
Lines them up against the should-cost and drafts the negotiation note
How the operator costs a custom part
- Step 1
Connect
Drawings folder, order history, your rates.
- Step 2
Cost the part
Reads the drawing. Builds the should-cost.
- Step 3
Approve the move
You say yes. It acts and logs it.
Nothing reaches a supplier without a yes.
- Approval before every send or write
- Your rates and rules, in plain words
- Every run logged: input, output, tools, user
Approval · BRK-2207
RFQ package drafted
- Ostrova Precision
- Valtorta Meccanica
- Kessmark Fertigung
Nothing has been sent.
Run record · Illustrative data
- input
- Drawing BRK-2207 rev C, RFQ
- tools
- Read drawing, order history, cost model
- output
- Should-cost €28.88 · RFQ drafted
- user
- L. Moretti · awaiting yes
- Measured on
- Quote vs should-cost gap
- RFQ turnaround
- Estimator hours per part
- Duplicate parts avoided
- Works with
- SharePoint
- Google Drive
- Google Sheets
- Snowflake
- PostgreSQL
- Coupa
- Slack
- Your ERP or PLM via MCP
- Trusted for
- ISO 27001
- GDPR
- Never trains on your data
- Single-tenant for enterprise
A custom operator typically goes live in up to 4 weeks.
Questions
What is an AI part-costing operator?
An autonomous agent that works your custom-part requests. It reads the drawing and the RFQ, checks your order history for the same or a similar part, builds a should-cost from your own rates, drafts the RFQ package and lines up the quotes. Your buyer approves every send.
Does it read CAD files?
It works from the PDF drawing and the RFQ: the title block, material, tolerances, finish and quantities, each value shown with where it came from. Native CAD files can be attached to the request; the cost is built from the drawing and your rates.
Where does the should-cost come from?
From your own machine rates, material prices and routing rules. The operator writes the cost model as code and runs it, so every line shows its formula and its source, and an estimator can check or change any of them.
Does it contact suppliers without approval?
No. Sending a message or writing to an external system waits for a person's yes, and every run is logged end to end: input, output, tools and user.
Which systems does it connect to?
Alomana has 20+ connectors, including SharePoint, Google Drive, Google Sheets, Snowflake, PostgreSQL, Coupa and Slack, activated per deployment. Your ERP or PLM connects through a remote MCP server.
Are our drawings safe?
Alomana is ISO 27001 certified and GDPR-compliant, and your data is never used to train AI models. Enterprise deployments run single-tenant, in a dedicated instance.
Bring one drawing.
Talk it over with sales: what the operator needs from your systems, and how it goes live.
Alomana is a secure enterprise AI platform where autonomous agents, called operators, run business processes end to end. Every run is fully auditable.