In engineering companies, a quote isn't complete when the price is ready.
It's complete when the customer has everything they need to say "Approved."
That usually means submittals: datasheets, scope-of-supply, option lists, compliance statements, sometimes drawings or test requirements. And in many organizations, producing those documents is still a manual, fragile process—copy/paste from old projects, spreadsheets with unit conversions, Word templates that only one person knows how to update.
BC Engineering introduces a new feature designed specifically for that reality:
Smart Submittals — structured, revision-aware submittal packs generated directly from your quote/order lines and engineering data.
The Real Problem: Approvals Are Won (or Lost) in Documentation
Engineering sales workflows often bottleneck here:
- The quote is technically complex (flow/head/temperature/media/materials/standards)
- The customer asks for a formal datasheet and compliance confirmation
- Engineering needs to verify values and options
- Someone assembles the pack manually
- A change comes in ("head is now 72 m, not 68 m") and nobody is sure which PDF was sent
The outcome is predictable:
- delays
- inconsistent datasheets
- missing fields
- and the worst case: the customer approves one revision, production delivers another
Smart Submittals is built to eliminate that gap between engineering truth and customer-facing truth.
What Are Smart Submittals?
A Smart Submittal Pack is a structured set of documents tied to a specific quote/order line (or project scope), generated from your data in BC Engineering.
It's "smart" because it is:
- template-driven
- unit-aware
- revision-aware
- approval-ready
- traceable
Instead of assembling documents as loose files, you create and manage a pack with a clear status and history.
What's Inside a Submittal Pack?
Every company structures this slightly differently, but typical engineering submittals include:
- Cover page (customer, project, tag number, revision, date)
- Technical datasheet (requested vs selected values)
- Scope of supply / options list
- Compliance statements (e.g., ATEX, material cert expectations, industry standards)
- Notes & assumptions (installation, medium, operating limits)
- Optional add-ons: selection summary, test plan outline, commissioning checklist, GA reference list
Smart Submittals lets you define these once—then generate consistently.
How It Works in BC Engineering
1) Generate from Structured Engineering Data
Smart Submittals is designed to pull from what you already control in BC Engineering:
- Sales line: commercial intent (qty, delivery, pricing, references)
- Technical Context: engineering intent (requested flow/head/temperature/media/etc.)
- Configuration/selection results (if you store them): selected model, speed, materials, options
This means your datasheet is not "typed by someone." It's produced from the same data that drives your internal decisions.
2) Template-Driven Output for Every Product Family
You define templates per:
- product family (pump, motor, skid, spare kit…)
- market/customer type (different compliance language)
- language/region (formats, decimal separators, units)
Then you simply choose:
- Pack Type (e.g., "Pump Submittal – Standard")
- Output format (PDF, internal draft, customer version)
No rework. No hunting for the "right" old file.
3) Units and Formatting Handled Consistently
Engineering submittals fail in small, painful ways:
- values shown in the wrong unit
- inconsistent rounding
- missing unit labels
- mixed conventions across teams
Smart Submittals enforces consistency:
- controlled units per attribute
- standardized formatting
- predictable rounding rules
- clear "requested vs selected" presentation (where applicable)
4) Built-in Revision Awareness
This is the feature that stops the "approved A, delivered B" problem.
A submittal pack is always tied to the underlying data state. If a relevant value changes—like requested head, material selection, or option scope—the pack can be flagged as:
- Outdated
- Needs review
- Requires re-approval (based on your rules)
You can regenerate a clean revision in seconds, with a clear revision history.
5) Engineering Review Before Sending
Submittals are not just documents—they are commitments.
Smart Submittals supports a simple but practical workflow:
Draft → Engineering Review → Approved → Sent
You can implement lightweight controls such as:
- review required for specific pack types
- sign-off required if certain attributes changed
- optional "lock" of the Technical Context once approved (so downstream processes stay aligned)
This keeps speed without sacrificing engineering governance.
A Practical Example: Pump Duty Point + Options
A customer requests a pump for a duty point and operating envelope. The sales line is created. Engineering defines the technical context:
- requested flow
- requested head
- medium
- temperature
- solids content
- installation constraints
- applicable standards
Then selection/configuration defines:
- chosen pump model
- speed / impeller / stages
- elastomer/material options
- motor and accessories
With Smart Submittals, you generate:
- a datasheet that shows requested vs selected
- an option list that reflects the real configuration
- a consistent compliance section
- a pack revision stamped and traceable to the quote line
If the customer changes head or temperature later, the system can immediately show:
- which packs are outdated
- which need re-approval
- what changed since the last sent revision
Why Smart Submittals Matters
Faster Quotes Without Sacrificing Quality
- datasheets stop being a bottleneck
- less manual assembly work
- faster response to changes
Fewer Engineering Errors
- no copy/paste drift
- fewer missing fields
- consistent units and formatting
Better Project Execution Downstream
- what was promised is clearly recorded
- revisions are traceable
- approvals are tied to real data, not detached PDFs
Professional Customer Experience
- uniform, branded, readable submittals
- clear revision control
- fewer clarification loops
The Bigger Idea: "Engineering Truth Becomes Customer Truth"
Smart Submittals is not a "document feature." It's a reliability feature.
Engineering organizations win trust when they can consistently answer:
- What did we propose?
- What did the customer approve?
- What changed afterwards?
- Which revision is binding?
With Smart Submittals in BC Engineering, that chain becomes natural—because your documents come from structured data, and your approvals are tied to real revisions.
Closing
If your team is still building approval packs through copy/paste and scattered templates, you're relying on heroics—when you should be relying on process.
Smart Submittals turns the work you already do in BC Engineering into customer-ready output:
- faster
- consistent
- revision-safe
- engineered for real projects