Walk through a working copy with sample data for Acme Boilers, a made-up company: four orders at design, procurement, production and dispatch. Click anything; changes reset every night.
One system, from inquiry to commissioning: CRM, Design, Procurement, Stores, Production, QC, Shipping, Service, Accounts and HR on one set of records.
SB Ops is an ERP built for boiler and pressure-vessel manufacturers: one set of records from the first inquiry to commissioning and service. Every feature below runs in the live demo above with sample data.
ASME record package generated from the job
The Manufacturer's Data Report (Form P-2 for a firetube boiler under Section I, Form U-1A for a Section VIII Div. 1 vessel) is filled in from the job's own records instead of being typed for every unit, with the shop and inspection certificates for the Authorized Inspector to sign.
Behind it come the records an inspector asks for: a weld map with each seam, its WPS and PQR and the stamps of the welders who made it; welder continuity under QW-322, six months per process, with the lapse date for each; mill test reports by heat number traced to the parts made from them; NDE reports; postweld heat treatment or the exemption that applies; and the hydrostatic test. Matching a mill test report to the part it covers is suggested, then confirmed by a person.
Most boiler makers keep a master BOM workbook per project: one sheet per subsystem, one row per material, with columns each department fills in. Upload that workbook and it becomes a structured BOM tree with categories and links to the item catalog.
The importer copes with hand-made layouts, including two-row headers and split "PO No. | Date" columns. Nothing is written until someone checks a preview of each sheet: rows found, columns ignored and rows skipped. The original file is kept as the revision record, and a spelling corrected once is remembered for the next import. From then on, departments update the BOM in the app instead of passing the spreadsheet around.
Material traceability from test certificate to finished part
Each mill test certificate is identified by certificate, cast and plate number together. The heat number and certificate are recorded once, when a plate is received, and every piece cut from it inherits them, so nobody re-types them at the cutting table.
When a plate is cut, every used piece, usable remnant and scrap piece is chained to the plate it came from, with weights derived from its dimensions. Remnants go back into stock as real pieces with sizes, and when a BOM is released a fitting remnant is reserved before new plate is bought. The owner sees how much steel was reused.
Each customer gets a read-only portal: every order as a stepper from order received to startup, overall progress, estimated ship date, and the quality records and packing lists filed under the stage they belong to. After startup, service visits appear there too. A customer only ever sees their own orders.
A 2.75 x 1.5 in QR sticker for the boiler nameplate is printed from the job, one per unit when an order covers several boilers. Scanning it opens that order in the portal after the customer signs in, so plant staff can find documents and service history from the boiler itself.
Sales tax and the general ledger in the same system
The system is the book of record for each company entity: ledger, receivables and payables, sales tax on invoices, fixed assets, bank reconciliation, financial statements, a books lock and an audit log. The books run on the calendar year.
Sales tax is set per line, so an in-state customer is charged the local rate and an out-of-state or exempt customer is not.
Alerts each person chooses, and a morning brief for the owner
Every alert in the system is grouped by department, and each person chooses, alert by alert, whether it shows in the bell, arrives by email straight away, comes in a daily email, or stays off. Alerts meant for department heads only ever reach heads.
The owner can also get a morning brief by email once a day: how many projects are on track, at risk or late, the ones slipping most, dispatches due this week, money outstanding and approvals waiting. Heads get a brief about their own team's work. It is written straight from the data, with no AI involved.
An estimate goes to the customer, and a request for quote goes to suppliers, by WhatsApp or email in one click. Messages go from the company's own number through WhatsApp's official Cloud API, and a click-to-send link is the fallback when the number is not connected.
Incoming conversations land in the sales inquiries inbox, linked to the lead or customer, and an alert goes to the person who owns them.
The executive view puts every project's milestone status (on track, at risk or late) next to cash outstanding by customer, approvals waiting on the owner and this month's numbers, including how much steel was reused from remnants.
Each figure comes from the same records the departments work in, so it is current without anyone preparing a report.
A small agent on office PCs keeps USB drives, CDs and DVDs, phones and chosen websites blocked by default. When an employee tries to use one, a request is filed; a manager approves it with a one-time code, and access opens for a short window, 15 minutes by default.
Every request, approval and expiry is written to an audit log, so the owner can see who opened what, when, and who allowed it.
Leads from the company website and email arrive as inquiries in Sales, assigned to salespeople in turn, with the source recorded. The same lead arriving twice is skipped, and a new inquiry from a known contact is added to that customer's history.
Inquiries move through funnel stages with a follow-up diary, estimates are priced from the company's price lists, and a won estimate becomes a sales order and a job. Payments are tracked against each order by stage, from deposit to the last payment.
WhatsApp
Gmail
Zoho Mail
Gemini AI
Cloudflare storage