Vision & roadmap
One careful pass through the drawings, shared by everyone on the job.
Here is the problem we are solving, what works today, and where we are headed next.
The problem
Days of matching, done more than once
Before a controls contractor can bid, someone checks the mechanical drawings by hand. Every tag, point and damper gets matched against a points list that may not agree with the drawings. That takes days.
Then the design engineer and the field crew rebuild much of the same information on their own. The same careful work gets done again and again.
The product today
Send in a mechanical set. Get four things back.
Marked-up set
Your drawings back, showing where each piece of equipment sits.
Equipment spreadsheet
Every unit we found, in one sheet you can sort and edit.
Points list
A starting points list built from the same pass.
Could-not-find list
Anything we looked for and could not place, so nothing hides.
The bidder, the design engineer and the field crew can all reuse that one pass instead of starting over.
It is a coworker, not autopilot. An engineer still reviews the work and signs off. Drawings are read by our own parsing engine, and it works with any controls brand.
Roadmap
What comes next
01
Sequence check
A gap report on the sequence of operations. It raises questions for the design engineer, not accusations.
02
Shop-drawing vetting
Every point accounted for, and enough inputs and outputs on every controller. It looks for functional gaps, not style.
03
Point-to-point checkout scripts
Checkout scripts written for you, with a person approving each one before it is used.
Business model
How we plan to charge Planned
- Pay per drawing set, with optional add-on layers.
- Your data clock starts when a job closes, not when you upload.
- Before anything is purged, you get a warning that names the job, plus a one-click way to email the files to yourself.
Status
Where things stand
The drawing engine is coming soon. We're finishing real runs before we open uploads, and payments stay parked until then.
Want early access, or want to tell us what we got wrong? Email help@bmscoworker.ai. A person reads every message.