The blueprint we received describes a private AI platform for J.M. Field. It is a good direction. But it was written as if we are starting from nothing, and we are not. This plan grounds the vision against the stack we already run, then starts with the work that pays back fastest and carries the least risk.
Most of the blueprint's "data" and "automation" layers are already running here. The right move is to integrate, not rebuild, and to spend effort where there is a real gap.
This is the stack the AI layer plugs into. None of it gets thrown away.
A separate server running its own Proxmox: 16 cores, 256 GB RAM, all-SSD, sitting idle today. This one box runs the AI layer. The production servers are not part of it and are not touched.
Live on a Windows server with about 14 daily users, with data already syncing to the NAS. Stays untouched.
A server that already downloads UPS, FedEx, 4over, Comcast and more every night and files them into Accounts Payable.
Active Directory and Exchange 2019, synced to Microsoft 365. The AI layer authenticates against this.
An AI assistant already running for the website. We extend this rather than stand up a second system.
Temperature sensors and cameras already wired in, ready to grow into operations alerting.
One card per department you asked about. Open each to see what fills the gap, the first step, and what to deliberately skip.
We pulled the live hardware report from the R740 itself. The compute, memory and storage are already strong. The only real blockers are the power supplies and the GPU mounting kit. And the GPU the blueprint recommended will not physically fit this chassis.
Nothing internet-facing until the old, unsupported servers are dealt with. The early phases need little or no GPU and carry no risk to the accounting system.
Confirm the R740 has room, capture the Sage version, and decide how financial data comes out. Done already for the hardware. Read-only, no changes.
No cost · No riskRead-only Sage financial dashboards, a unified "ready to enter" view across the invoice robots, and internal document search through the existing AnythingLLM. All on the hardware we own.
Little/no GPU · Zero Sage write riskLive financial dashboards, an executive KPI view, and document search widened to marketing and operations. GPUs land here and start doing real work.
GPUs onlineArtwork preflight that explains errors in plain English, plus multi-step automations: invoice arrives, gets checked against the order, flagged for approval.
Department workflowsOnly after the old servers are retired and a proper isolated network is built: a single, locked-down outside service such as order status. Never a full company-data portal on the open internet.
After security hardeningThe fastest way to waste this budget is to build the impressive-sounding parts first. Here is the split.
Rather than trust one opinion, we checked the plan against three independent AI systems from different vendors. They agreed on every major call: read-only for Sage, deterministic tools for print preflight, retire the old servers first, and the 3090 is wrong for this chassis.
Mapped each department gap to what already exists and flagged the chatbot-per-department idea as overbuilt.
Confirmed deterministic prepress tools beat a vision model for technical artwork checks, and that the public portal is the top risk.
Surfaced the one thing the blueprint forgets: a governance plan for who owns the data and how wrong answers are handled.
It is a list of technology, not an operating plan. Before any of this goes live we name who curates the data, what happens when the AI is wrong, who maintains the models, and how the knowledge base gets backed up. Skip that and you have built a fast, unmanaged liability.
Three moves get us a real return without betting the business or spending much capital.
Get one financial report out of Sage so the read-only dashboard can be built against the real numbers. No risk to the live system.
Two A5000 GPUs, the Dell mounting kit and bigger power supplies, mostly from the used market, so the AI node is ready when the software is.
Plan the retirement of the unsupported old servers. Highest-value risk reduction in the plan, and the gate to anything customer-facing.