Workflow Automation for Manufacturers in Western New York

Western New York still makes things. From the machine shops around Rochester to the plants along the Buffalo waterfront and the manufacturers spread across Central New York, there are hundreds of companies with twenty to two hundred people, a shop floor, an ERP that was installed a decade ago, and an office where a surprising amount of the work is still done by re-typing.

That office work is where workflow automation pays back fastest, and it is where most manufacturers have not looked, because "automation" on a plant floor means robots and PLCs. This post is about the other kind.

What manufacturers here actually automate

The processes that come up again and again, in roughly the order they pay back.

• Quoting. A request arrives by email, someone opens a spreadsheet, looks up material and labor, types a quote into a template, and emails it back. Two days later they do it again for a revision. Intake, lookup, and document assembly can all be automated while a person still decides the price.
• Order entry and acknowledgments. A PO in the inbox becomes a sales order in the ERP by hand, with the acknowledgment typed by hand. The ERP has an import. Almost nobody uses it.
• Certifications and compliance documents. Certs of conformance, material certs, first-article reports, assembled per shipment from data that already exists in three systems.
• Schedule and delivery communication. The weekly "where is my order" cycle with key customers, answered from the schedule automatically.
• Reporting. The Monday production report and the month-end margin report, assembled from exports by someone who would rather be doing anything else.

None of these touch the machines. All of them touch the people who keep the machines fed with work.

The constraints that shape the work

NIST SP 800-171, CUI, and ITAR

If you are in the defense supply chain, controlled unclassified information changes what tools you may use and what data may leave your network. This is not a reason to avoid automation. It is a reason to design for it from the first day: which data classes may go where, which AI providers are under contract terms that prohibit training on your data, which automations run entirely inside your own systems. The acceptable use policy for a defense supplier has one sentence that matters, and it is "no CUI in any AI tool."

The ERP nobody may touch

Most shops run an ERP that was configured by someone who has since left, and the working rule is: do not poke it. Good. Automation does not need to change the ERP. It needs to read from it and write to it through the doors it already has (imports, exports, reports, an API if you are lucky). The first weeks of any engagement here are spent mapping those doors, not proposing a new system.

Shop-floor bandwidth

The people who know the processes best are the ones with the least time. Any program that asks them for a full day a week will fail. The shape has to be short, in-person bursts followed by weekly check-ins that fit around production.

A twelve-week program built for a manufacturer

This is the cohort design we built for a western New York manufacturer with defense customers. The client is not named; the shape is the point.

Weeks 1 to 4: four full training days, on site. Mornings are workshops for the whole cohort: how the tools work, a waste walk through the company's own processes, a project charter and a measured baseline for each participant. Afternoons are one-on-one sessions, an hour per person, on their specific process and their own uses of the tools.

Weeks 5 to 11: applied build. Each participant builds their automation in the company's real systems, with a weekly remote check-in. A mid-program tollgate review keeps every project on scope and on its numbers. Every project runs one Define, Measure, Analyze, Improve, Control cycle, because that is the discipline the quality team already speaks.

Week 12: demo day. Each project is presented to leadership with its baseline, its result, and a control plan: an owner, a monitoring method, and a shared knowledge file so a colleague can support it. About thirty-one instructor-led hours per participant, spread so production never stops.

Paying for it

New York State's Employee Training Incentive Program, run through Empire State Development, can recover a share of eligible training costs for manufacturers and other employers. Eligibility depends on the company and the program; we will tell you what applies on the first call rather than promise a percentage here. The larger offset is the baselines themselves: a cohort of six people each automating a process worth several thousand dollars a year in office time pays for itself within the year, and demo day shows whether it did.

Where we work

Civic Dialog is based in Rochester and works on site across Rochester, Buffalo, Syracuse, and the Finger Lakes, with remote check-ins in between. For a manufacturer that wants the automations built rather than taught, CoBuild starts with a fixed-fee scoping sprint that maps the office processes and the ERP's doors. For a team that wants to learn to build, the cohort above is the shape.

The easiest first step is a free Lunch & Learn at your plant. Bring the quoting process. We will baseline it in the room.