Valves, actuators, pumps, flow control and process equipment
Sized to the duty. Coded to the part number. Built from one model.
Process equipment is sold on application data: pressure, temperature, flow, media, connection. The outcome is a coded part number that encodes dozens of selections, a configured BOM, and often an engineered exception. Manufacts carries the whole chain, from typed inputs and sizing tables to the part, its variants and the drawing package.
Constraint propagation
v7 · frozen Every fire is explainable, versioned, and frozen per quote.
What changes for an equipment manufacturer
Application engineering becomes a rule set the whole sales channel can run.
Application data in, configuration out
Typed inputs with units and ranges. Sizing rules look up the tables and select body, trim and actuator. Invalid combinations never reach a quote.
The part number is a first-class object
Each position of a coded part number maps to a choice. The code resolves to a part and a variant with its own attributes, cost and revision.
CTO for the standard, ETO for the exception
The catalog configuration ships in days. The special alloy or non-standard connection goes to a governed engineering queue and comes back as a reusable option.
Sizing and selection
Enter the duty. The configuration selects itself.
Application inputs are typed: a pressure has a unit and a range, a medium is a choice from a list, a temperature is checked against the material. Selection rules read sizing tables and pick the body size, trim characteristic and actuator that meet the duty. What the engineer used to do with a slide rule and a catalog, every salesperson now does in the configurator.
- Typed inputs with units, ranges and dependencies
- Lookup tables for sizing, Cv and torque, maintained as data
- Constraint propagation blocks impossible combinations and explains why
- Rule sets versioned and frozen per quote
Constraint propagation
v7 · frozen Every fire is explainable, versioned, and frozen per quote.
Coded part numbers
A structured code that means something
Your part numbers already encode the product: type, size, rating, material, trim, actuation, options. Manufacts models that structure. Each code position is a choice with its own rules, the full code resolves to a part plus a variant, and the variant carries attributes, approved sources, cost and revision history. The code on the quote is the code on the nameplate.
- Position-by-position decoding into choices and attributes
- Part plus variant model: one part, many coded variants
- Per-variant cost ledger and approved manufacturer parts
- Where-used and change impact across every coded variant
Internal part
PT-3401 · 30A Receptacle
Engineered exceptions
Say yes to the special, without a side project
Some orders need a non-catalog alloy, an unusual connection or a customer-specified test. Sales submits it from the same quote, engineering picks it up in a governed queue, designs it inside the same model with the same parts and rules, and releases it through normal approvals. The next customer who wants it configures it.
- ETO requests tracked, costed and owned from intake
- AI BOM helper drafts the assembly from the request text
- Change notices and approvals before release
- The special becomes a priced, reusable option
AI BOM Helper
Proposed assembly · resolved against your catalog
Governance
Revisions and approvals your quality system can audit
Every part, variant, rule and document follows a lifecycle. Releases happen under a change notice with impacted items, sequential approvals and a full audit trail. Sold orders stay pinned to the revision they were quoted on, so a design change never silently alters an open order.
- Lifecycles and gates on parts, BOMs, rules and documents
- Change notices with impact analysis and approvals
- Release pinning per order
- Audit trail on every change, attributed and reversible
Part lifecycle
server-enforcedBuilt for process equipment
The details that make or break an equipment BOM
Typed inputs and sizing tables
Application data with units and ranges; selection rules read tables that engineering maintains as data.
Coded part number model
Structured codes decoded into choices; part plus variant with attributes, cost and revision.
Approved vendor lists per plant
Manufacturer parts linked to engineering parts, with plant-specific sourcing and alternates.
Drawing packages
General-arrangement and detail drawings generated from the configuration. DXF export is on the roadmap.
ERP feeds and API
Resolved BOMs and orders flow to your ERP through an outbox with retries and a versioned API.
Import from legacy PLM
Bulk import of parts, BOMs and options from Windchill, Teamcenter or spreadsheet extracts.
Start with these capabilities
Rule & Constraint Engine
Capture your best engineer’s judgment once, and enforce it on every order forever.
Product Data & Attributes
Model any product, any attribute, any revision, without waiting on a schema migration.
Engineer-to-Order Queue
Sell the one-off no template covers, then turn it into a reusable, priced option.
Bring a sizing sheet and a part number scheme.
In a 30-minute walkthrough we'll show how one of your product lines would be modeled, sized from application data, and resolved into a coded part number and its BOM.
No rip-and-replace: Manufacts runs alongside your ERP and CAD. Prefer email? hello@manufacts.ai