Software for Twin Cities shops and offices
A medical device maker that buys from a Twin Cities machine shop judges the shop on its records as much as its parts. Its auditor wants to see which job a part came from, who inspected it, against which drawing revision, and what changed between the quote and the shipment. The auditor asks for the record itself and expects it to agree with the one beside it.
Behind that customer is a shop of a few dozen people where traceability often lives in a binder, a spreadsheet and one person's memory. What the auditor needs from such a shop is not a factory system. It is a job record that follows the part from quote to shipment, an inspection log that cannot lose a page, or a connection between the quoting spreadsheet and the accounting package. The customer's audit list decides the design: with the quality lead, we write down which records are audited, the rules each must follow and who in the shop may see it, before anything is built. The quality lead decides what counts as a finished record, and anything the tool cannot tie to a job waits for that person. Work starts from a brief that fixes the scope and price of the build, then one release the shop can try, after we check whether a product it already owns can do part of the job. An office near the plants gets the same approach for the two systems someone now bridges by retyping.
Today the shop's parts travel across the metro, to a customer close enough to visit. Its records can be read much farther away. A buyer in Milwaukee or Chicago, or at a device company on either coast, asks for the same proof the current customer does. That buyer can receive it with the quote, drawn straight from the job record, without making the trip. A binder cannot be sent that way. A customer won at that distance adds jobs to the system, and the tool is built so the office's paperwork does not grow at the same rate.



